Hosted checkout
A checkout that offers the payer only the rails that can actually complete their payment, decided at the moment they arrive rather than listed hopefully on a page.
Online shops, marketplaces, billing systems, booking sites and any business sending customers somewhere to pay.
Switched on for this deployment.
The problem
A checkout that lists ten logos and fails on eight of them teaches customers to abandon the page. Worse, it fails after they have committed, which is the most expensive moment to lose them.
How it works
- Create a payment intent or a checkout session with the amount, the currency and your reference.
- Send the customer to the URL it returns, or show the QR payload it returns.
- The page works out which rails can carry this payment, for this payer, right now — and shows only those.
- When it is paid, you get a signed webhook and the customer goes back to your success page.
What you can check
Facts about the running platform rather than adjectives. Each one is visible in the product, the API reference or the ledger.
- The rails offered are computed per payment, from the corridor, the currency, the payer and the live health of each connector.
- A rail whose circuit breaker is open is not offered, so a customer is never sent down a path that is currently failing.
- Under the aggregator perimeter the checkout offers the switch rail alone and refuses the rest, rather than showing options the platform may not operate.
- The session carries line items with VAT where the merchant uses them, so the customer sees what they are being charged for.
What it costs
The hosted checkout is part of the merchant gateway; there is no separate charge for it. You pay the rate for the rail that carries the payment, shown in the dashboard.
Questions
Can I put my own branding on it?
The page carries your business name, your reference and your line items, and returns the customer to your own success and cancel URLs.
What happens if a rail goes down mid-sale?
A connector whose circuit breaker has opened stops being offered, so new customers are routed around it rather than into it. A payment already in flight follows its own state machine and is never marked paid without confirmation.
Do I have to use the hosted page?
No. The same intent can be rendered as a QR payload, embedded with a publishable key, or driven entirely from the API if you want to build the screen yourself.
Read next
BitriQR payments
One printed code that works for a customer with the app, a customer with only a camera, and a customer whose bank has never heard of BitriPay — because the code is EMVCo underneath and signed on top.
Payment links
A link you can paste into WhatsApp that behaves like a full checkout — reusable or single-use, with an expiry, a reference and a webhook when it is paid.
The gateway API
A payments API whose documentation is generated from the same table that serves the requests, so the reference can never describe an endpoint the platform does not have.