Hosted checkout
Redirect the customer to a payment page we host and maintain. The fastest route to a working flow, with no payment interface to build and nothing sensitive touching your servers.
A named engineer on our side for the duration of the build, and four ways in so the integration fits your stack rather than the other way round: hosted checkout, REST API, webhooks or a CMS plugin. Most merchants start with hosted checkout and move to the API once the flow is proven.
There is no penalty for changing your mind later.
Redirect the customer to a payment page we host and maintain. The fastest route to a working flow, with no payment interface to build and nothing sensitive touching your servers.
Build the payment experience inside your own product. Create orders, quote rates, read status and submit payouts programmatically.
Payment status, payout status and screening outcomes pushed to your endpoint as they change, with signed payloads and retries.
Drop-in modules for common e-commerce platforms when the store is standard and the timeline is short. The list of supported platforms is confirmed during onboarding.
For your engineering team
Hosted checkout and the plugins are the fast path. Underneath, the checkout, the payout queue and the dashboard all call the same REST API.
Create an order, quote a rate and read its status without leaving your own product.
Submit single or batch payouts programmatically, under the same approval and screening rules as the dashboard.
Every status change, payment, payout and screening outcome, pushed to your endpoint with a signed, retried payload.
A fully isolated environment with its own keys and data, so your team can build and test before anything touches a real balance.
Security of the integration
Every API call is authenticated and every webhook payload is signed, so your system can verify what it receives.
Sandbox and production are fully isolated, with separate keys and separate data.
Keys carry only the permissions they need, and can be rotated or revoked without taking the integration down.
IP allowlisting on request, role-based access in the dashboard, and approval thresholds per user.
Yes. Sandbox credentials come before production keys, and the sandbox is fully isolated with its own keys and data, so nothing you build there touches a real balance.
Deliveries are retried, and every payload is signed so you can verify it when it arrives. Status is also readable over the API, so a missed webhook never leaves your system out of sync permanently.
Yes. Most merchants start with hosted checkout and move to the API once the flow is proven, and there is no penalty or re-onboarding for changing your mind either way.
Drop-in modules are available for common e-commerce platforms when the store is standard and the timeline is short. The exact list of supported platforms is confirmed during onboarding.
Yes. IP allowlisting is available on request, alongside role-based access in the dashboard and approval thresholds set per user.
Send us a note as part of your application and we will set up sandbox credentials so your team can build and test the integration before anything is signed.
