Hosted Checkout Scenarios
Learn to Build the Right API Payload for Your Hosted Checkout Scenario
Hosted Checkout supports a wide range of use cases — from simple one-time payments to more advanced recurring payment models using card tokenisation or Variable Recurring Payments (VRPs). Use the matrix below to identify the correct setup for your scenario, then follow the relevant page for detailed integration guidance.
Setup scenarios
| Scenario | Description | Common Use Cases |
|---|---|---|
| One-off payment | Take a single payment from your customer. Card details can optionally be saved for one-click checkout or future recurring use, but this is not required. | eCommerce checkout, bill payment |
| Store credentials only | Save a customer's payment credentials without charging them, for use in future recurring payments. | Lending |
| Charge + store credentials | Accept a payment from your customer as well as saving a customer's payment credentials for future recurring payments | Subscriptions, memberships |
Supported payment methods per scenario
Card Payment, Apple Pay, Google Pay and Pay by Bank are all available in all three scenarios.
Pay by Bank behaves differently in the two credential-storing scenarios. In both Store credentials only and Charge + store credentials, Hosted Checkout creates the VRP mandate but never takes a payment — including the first payment in a Charge + Store flow. All Pay by Bank payments must be initiated separately via Initiate a variable recurring payment. See Pay by Bank in Hosted Checkout.
Updated 20 days ago