Hosted checkout
Redirect to an Orqex-hosted page. Fastest to launch.
Custom (direct API)
Build your own UI and drive the API. Full control.
Comparison
| Hosted checkout | Custom (direct API) | |
|---|---|---|
| You build | A redirect + a return page | The full payment UI |
| Next actions (OTP, redirect, QR, approval) | Handled by Orqex | You render them from next_action |
| Method selection | On the hosted page | In your UI |
| Effort | Low | Higher |
| Control over UX | Limited to theming | Total |
| Best for | Launch fast | Bespoke, embedded checkout |
What both require
- A server-side secret key. See Authentication.
- A webhook to learn the final status. See Webhooks.
- Gateway accounts and routing rules configured in the dashboard.
How to choose
Launch fast or no UI to build?
Use the hosted checkout.
Bespoke, embedded experience?
Initiate a payment directly on the API.