Service
Checkout and API
In one line
Hosted checkout, plugins, or the API.
What it is
Most merchants go live with hosted checkout — a page we host, styled to your brand, that handles cards and ACH — or a plugin for their cart. Neither needs an engineer. Both keep card data off your systems, which is what keeps your PCI scope at the lightest self-assessment.
If you do have engineers, there is a documented REST API, hosted fields you can embed in your own pages, and signed webhooks for every event that matters. The sandbox is yours as long as you need it, and nothing about the integration changes when you move to production except the keys.
Capabilities
What you get, specifically.
Hosted checkout
A payment page we host and secure, styled to match your site. Cards, ACH and wallets on one page. Live in an afternoon.
Cart plugins
Drop-in support for the major platforms, so an existing store does not need rebuilding to move.
REST API and hosted fields
Tokenised card capture in fields we host inside your page, plus a documented API for charges, refunds, customers and subscriptions.
Webhooks
Signed, retried, and replayable from the dashboard. Every settlement, dispute and payout event, delivered to your system.
Fraud rules and 3-D Secure
3DS2 with configurable exemption logic, plus velocity, geolocation, BIN and blocklist rules tuned per account.
Specification
The detail.
- Integration
- Hosted checkout, cart plugins, REST API, hosted fields
- PCI scope
- SAQ A with hosted checkout or hosted fields
- Tokenisation
- Network and platform tokens
- Webhooks
- Signed, with replay
- Sandbox
- Unlimited
- Platform uptime
- Set at underwriting
Rows reading set at underwriting are not omissions. Those figures are decided per merchant against your vertical, volume and history, and you will see all of them in writing before you sign.
Tell us what you sell.
Before anything sensitive changes hands, we will tell you whether we can underwrite your vertical, roughly what the terms look like, and what underwriting will ask you for.