Advanced Web Checkout — Payment Method Configuration

Control which payment types show to your customers at checkout, and which gateway account processes them.

Checkout payment method groups let you decide which payment buttons appear on a web checkout form. One group holds one gateway account — so to run several accounts, create a group per account and assign each group to its own cloned checkout template.

Checkout groups require the Checkout — Checkout payment method configuration licence, which activates the ability to configure the types of payment services seen on the checkout form. Once it is active, a Checkout payment method sub-menu appears under Checkout management.

Licence · Paytia portal

Check before you start:

• Licence active — no Checkout payment method sub-menu means the licence is not yet on the account.
• Gateway connected — a gateway and at least one gateway account must exist under Manage payments › Payment gateway setup.

Checkout management › Checkout payment method

Menu path · after licence activation

Payment method configurations let you display different sets of payment methods to customers. Groups created here are associated to, and used by, your Checkout templates — and can also be referenced in Payment rules. A new account shows No record found.

Payment configuration list

The list shows:

• Configuration name — the group name you choose (e.g. Checkout Group - GTW); this is what you pick later in Checkout templates and Payment rules.
• Gateway — the single gateway account this group routes through.
• Created date / Action — audit date, plus edit and delete controls.

Click Add configuration to add a new group.

Click to create a group

→ Plan first: one group per gateway account, named after the account or the flow it serves. Multiple accounts = multiple groups + a cloned checkout template for each.

Each group holds one gateway account and its own set of payment-type switches. Complete the fields, set the switches, then click Save Configuration.

Add checkout payment method

These on/off switches control whether the button for each payment type is shown on the web checkout template your customers use. New configurations start with all three off (red).

• Card — shows the credit and debit card button and the card capture fields.
• Apple Pay — shows the Apple Pay button (supported Apple devices and browsers only).
• Google Pay — shows the Google Pay button.

! Check: Apple Pay and Google Pay must also be enabled on the gateway account itself. If a switch is green but the button does not appear, confirm wallet support on that account with your acquirer.

Once your groups are created, assign them to a checkout template. Find the base template that best suits your use case, click the green clone button, and a copy is made that you can rename and customise. Cloned templates appear under the Cloned Templates tab.

Menu path

Default templates · clone action

→ Multi-account: Clone the template once per gateway account, then assign a different Checkout payment method group to each clone. Each flow then captures to its own account with its own set of payment buttons.

In the web checkout template editor, scroll to Payment method configuration. This dropdown associates the correct group with the template — your saved groups are listed by their configuration name. The live Preview on the right updates to show the buttons customers will see.

Template editor · preview

The dropdown

Order of work:

1. Set Payment method to Show so the selection step appears.
2. Select your configuration from Payment method configuration. Nothing listed? Save the group first.
3. Save the template, then preview and test with a live checkout link.

The template you attach the group to is what ties an incoming request to a gateway account. Paytia resolves it in three moves:

1. Template lookup — the post carries checkout_template_id={template id}. This selects the template branding — and that template is associated to a Payment method group.
2. Payment method group — the group controls which payment gateway types are accepted. Groups are separated out per storeID.
3. Payment routing — routing comes from the storeID specified in the Payment method group — so the group decides both the buttons shown and the account paid into.

Manage payments › Payment rules

Menu path

For advanced control, Payment rules allow overrides based on different data values — specify which payment method buttons are shown, apply a service management charge based on amount, or control which processor each payment type routes through.

Payment rules list

With Select Type: Checkout API, conditions can be built on:

Amount · Account number · Billing country · Shipping country · Payment method selection · Currency Code · MidasTrackingData

Condition values

1. Activate the Checkout payment method configuration licence.
2. Create a group per gateway account and set Card / Apple Pay / Google Pay.
3. Clone a checkout template for each group.
4. Attach the group in Payment method configuration and save.
5. Refine with Payment rules where data-driven overrides are needed.

Need a hand? Paytia support can review your group and template pairings before you go live, and confirm wallet enablement on each gateway account — techsupport@paytia.com.