Checkout
Hosted checkout links, API-created sessions, and what RevKeen supports today
RevKeen checkout is hosted. You send the customer to a RevKeen checkout URL, RevKeen collects payment details securely, runs the required authentication and risk checks, and then returns the customer to your success or cancel destination.
Choose the Right Checkout Flow
| Flow | Best for | Managed from |
|---|---|---|
| Checkout Links | Reusable purchase URLs, no-code sales pages, campaigns, QR codes, simple product sales | Dashboard or API |
| Checkout Sessions | Backend-created one-off checkouts, dynamic pricing, invoice checkout, per-session payment-method control | API |
| Embed | Understanding display modes and current embedding limitations | Dashboard configuration |
| Localization | Localized copy and routing around today's hosted checkout limitations | Dashboard plus your app |
What RevKeen Checkout Supports Today
- Hosted checkout pages served by RevKeen-managed checkout domains.
- Reusable payment links that open a hosted checkout flow.
- API-created checkout sessions for invoices, products, and custom amounts.
- Success and cancel redirects so you can return customers to your own site or app.
- Card payments, with additional in-store session support available on the checkout-session API.
- 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 customer device/browser.
Hosted by Default
RevKeen's supported checkout path is a hosted page, not a fully client-rendered payment component. That keeps card entry and payment authentication inside RevKeen's controlled checkout surface.
If you need a reusable URL, use a checkout link. If you need to create a checkout at the moment of purchase from your backend, use a checkout session and redirect the customer to the returned url.
Returning Customers
When a returning customer reaches checkout and RevKeen detects saved cards on file, RevKeen can offer an express path using those stored cards. Access to saved cards is protected by identity verification, trusted-device checks, and CVV re-entry before payment is confirmed.
Next Pages
- Embed -- What RevKeen supports for inline and overlay presentation today
- Checkout Links -- Shareable hosted checkout URLs
- Checkout Sessions -- API-created hosted checkout flows
- Localization -- What can and cannot be localized today