Payment route design
Give customers the right ways to pay.
The method mix is designed around your customers, product, merchant category, checkout, and settlement model. It is confirmed commercially—never assumed from a logo list.
Cards
Card journeys shaped around approval and risk.
Eligible merchants may be configured for card acceptance through an approved acquiring route. The exact coverage can depend on card type, origin, currency, merchant category, customer authentication, and the commercial arrangement.
Operational considerations
- Customer authentication and payment-authorisation outcomes.
- Clear success, pending, failure, reversal, and refund states.
- Dispute exposure, evidence responsibilities, and refund policy.
- Tokenised or partner-hosted handling where the approved setup supports it.
Bank-led journeys
Move from checkout to bank approval and back again.
A bank-led payment journey can take a customer to an approved internet- or mobile-banking environment before returning a usable status to the merchant checkout. The integration needs to handle both the customer return and independent payment confirmation.
Merchant systems should rely on the confirmed gateway status or server-side notification defined for the approved integration.
Digital wallets
Reduce friction for customers who prefer wallet payment.
Eligible wallet routes can add a familiar local checkout path, but named wallet availability is confirmed only when the relevant technical and commercial relationship applies to the merchant setup.
What the merchant still owns
Product description, pricing, customer support, fulfilment, refund policy, and the integrity of the checkout remain merchant responsibilities even when the wallet completes the payment step.
QR-linked payments
Use QR only when the payment state stays connected.
QR can be useful in web, invoice, counter, and assisted-payment scenarios. The setup may use a static, dynamic, or checkout-linked code depending on the route. For online commerce, the important part is not the square itself—it is how the payment reference and final status return to merchant operations.
Availability rules
Every payment method is conditional until approved.
Route availability can vary with business model, merchant category, documentation, technical compatibility, customer location, currency, partner capacity, and the current regulatory environment.
The initial merchant discussion produces a proposed payment mix. Activation follows the required review, agreement, integration, and testing.