What is on a checkout page
- The merchant's name, the amount and the currency
- The payment methods available to that buyer
- Card fields, wallet buttons or a bank selector
- A box for saving the method, where offered
- Error messages that say what to do next
How a checkout page is served
With a hosted page, the merchant redirects the buyer to the provider's domain with a payment session, and the buyer returns when done. The page carries the merchant's logo and colours, and sometimes the merchant's own domain name.
With an embedded page, the provider's fields sit in frames inside the merchant's page. The buyer never leaves the shop, and the card number still goes straight to the provider.
The choice decides how much of PCI DSS falls on the merchant. The less the merchant's own systems touch card numbers, the smaller its assessment.
Why the checkout page matters
The page is where sales are completed or lost, so speed, language, the order of payment methods and behaviour on a phone are all measured.
The page is also a target. Scripts injected into a payment page can copy card details as they are typed, which is why providers lock down what may run there.
Checkout page, payment form or payment link?
- Payment form
- The fields themselves, wherever they are shown. A checkout page is the whole page around them.
- Payment link
- A URL that opens a hosted checkout page for a set amount, with no shop integration behind it.
Where a checkout page shows up in a platform
Modules that do the work
- CheckoutA hosted checkout for cards, wallets, bank payments and crypto, routed to the best provider.
- Card acquiringCard acceptance on the phone, in store and online, through the acquirer you choose.
- Fraud & riskReal-time fraud scoring, limits and case management, with the risk engines you already trust.