Skip to main content
Control your checkout experience from Dashboard → Checkout. Define which payment methods appear, set their display order, and create conditional display rules—all without code changes. Updates apply immediately when you save.

Payment Method Display

Configure which payment methods customers see at checkout: The preview panel shows exactly how checkout appears to customers in real time.
PayNext automatically detects customer devices and only displays compatible payment methods. Digital wallets appear only on supported devices.

Conditional Rules

Show or hide specific payment methods based on payment context. Select a payment method and click Add condition to open the condition builder.

Available Conditions

Combining Conditions

Conditions are combined with AND logic. A payment method displays only when all conditions are met. Example: Show a payment method only for:
  • Customers in US AND
  • Payments in USD over $50 AND
  • Metadata key customer_type equals vip

Getting Started

1

Open Checkout settings

Go to Dashboard → Checkout
2

Enable payment methods

Toggle on the payment methods you want to offer
3

Set display order

Drag payment methods to arrange their priority
4

Add conditions

Select a payment method and click Add condition to create display rules
5

Save

Click Save to apply your configuration
Test checkout changes in Sandbox before enabling in Production.

Bot Protection

PayNext can check visitors on the card entry form before a card payment is created. Most shoppers see nothing—a visible challenge appears only for visitors the check considers suspicious. This protects checkout against automated card testing. Choose a mode in Dashboard → Checkout → Bot protection:
Start in Shadow to see how your traffic scores, then switch to Enforce.

IP Allowlist

Automated tests cannot pass a bot check. Add the IP addresses your test runners use, and card payments from those addresses skip the check. Your integration needs no changes. Each entry takes an optional note and shows when it last matched, so you can tell which entries are still in use.
1

Open Checkout settings

Go to Dashboard → Checkout and find Bot protection
2

Add an address

Enter the IP address your tests run from, a note describing it, and an expiry date
3

Publish

Click Publish to apply the change
Use IP addresses that only you control. Shared ranges from hosted CI providers cover every customer of that provider, so an entry for one exempts traffic that is not yours. Private and reserved addresses are rejected.
An expired entry stops working and stays in the list, so you can see what lapsed and remove it.

SDK Customization

For advanced styling beyond dashboard settings, use SDK options: