Checkout
Hosted multi-rail checkout for card, Direct Debit, and wallets
RevKeen checkout is hosted. You send the customer to a RevKeen checkout URL. RevKeen collects payment details, runs authentication and risk checks, and returns the customer to your success or cancel destination.
Hosted checkout is multi-rail. When those rails are enabled for the merchant, the customer can pay by card, Direct Debit, or a wallet (Apple Pay / Google Pay). Pay by Bank collection is not a live checkout rail. The API refuses pay_by_bank on new checkout selection and configuration.
Choose the right checkout flow
| Flow | Best for | Managed from |
|---|---|---|
| Checkout links | Reusable purchase URLs, campaigns, QR codes | Dashboard or API |
| Cart sessions | Multi-line composition with add-ons and discount codes before convert | API, or embed (developer preview until Products → Embed and publishable-key auth) |
| Checkout sessions | Backend-created one-off checkouts, per-session rail control | API |
| Embed | Hosted checkout iframe, Direct Debit capture, and Cart on your site | checkout.js CDN — developer preview until Products → Embed and Phase 1 auth |
| Localization | Localized copy and routing | Dashboard plus your app |
| Hosted invoice | Paying an existing invoice | /i/{token} — not a checkout link |
What hosted checkout supports today
- Hosted pages on RevKeen-managed checkout domains.
- Reusable checkout links that open hosted checkout.
- API-created checkout sessions.
allowedMethodsmay includecard,direct_debit, andin_store. Values are intersected with merchant capabilities. - Cart sessions that convert atomically into a checkout session.
- Success and cancel redirects.
- Saved-card flows for returning customers, including email verification, trusted devices, and CVV re-entry.
- 3D Secure and gateway-driven card authentication where required.
- Apple Pay and Google Pay when enabled for the merchant account and supported by the device/browser.
- Direct Debit setup and collection when Direct Debit is enabled and a mandate can be used. Checkout V13 tells the customer that card is instant and Direct Debit is a scheduled collection: no money leaves the account today, the collection date is shown when known, and the bank statement name is disclosed.
Card versus Direct Debit on checkout
| Customer choice | Button / tile language | Money movement |
|---|---|---|
| Card | Instant payment. The pay button charges today. | Immediate authorisation and capture. |
| Direct Debit | Scheduled collection under the Direct Debit Guarantee. | After Bacs advance notice, on or after the stated date. |
Do not describe Direct Debit setup as a completed payment. The checkout confirmation for Direct Debit is pending collection, not paid.
What is not live
- Pay by Bank / open banking collection as a customer-facing checkout tile.
- Universal usage-price support across every session-creation path. See usage pricing and checkout for the supported boundary.
- Unrestricted framing on arbitrary origins. The hosted checkout embed requires an approved merchant origin. Card details remain inside the hosted payment surface.
Returning customers
When a returning customer reaches checkout and RevKeen detects saved cards, RevKeen can offer an express path using those stored cards. Access is protected by identity verification, trusted-device checks, and CVV re-entry.
Next pages
- Embed — Direct Debit form and cart drawer
- Checkout links
- Cart sessions
- Checkout sessions
- Direct Debit — mandate setup from a customer, invoice, checkout, or portal; advance notice and collection