Developers
Live in an afternoon, or integrate as deeply as you like.
At a glance
- Protocol
- REST, JSON
- Auth
- Per-account API keys
- Card capture
- Hosted fields, tokenised
- Events
- Signed webhooks, replayable
- Sandbox
- Unlimited, production parity
Three ways in
Pick the one that matches your team.
Hosted checkout
Most merchants
An afternoon, no code
A payment page we host and secure, styled to your brand. Cards, ACH and wallets on one page. You link to it or embed it; we handle the card data, 3-D Secure and the receipt. PCI scope stays at the lightest self-assessment because nothing sensitive ever reaches your systems.
- Brandable — your logo, colours and domain
- Cards, ACH and wallets on one page
- 3-D Secure and fraud rules applied server-side
- Payment links for phone, email and text
Cart plugins
Existing stores
Under an hour
Drop-in support for the major cart platforms, so a store that already exists moves without being rebuilt. The plugin uses hosted fields under the hood, so the PCI position is the same as hosted checkout.
- Major platforms supported
- Keeps your existing catalogue and order flow
- Hosted fields — card data bypasses your server
- Same dashboard and reporting as every other channel
REST API
Teams with engineers
Days, depending on scope
A documented REST API for charges, refunds, customers, subscriptions, payouts and disputes. Hosted fields you embed in your own pages tokenise card data before it touches your code. Signed webhooks for every event, replayable from the dashboard. The sandbox is unlimited and identical to production except for the keys.
- Charges, refunds, customers, subscriptions, payouts, disputes
- Hosted fields for tokenised card capture in your own UI
- Signed webhooks with retry and replay
- Idempotency keys on every write
- Unlimited sandbox, production parity
Webhooks
Every event that matters, delivered to your system.
- payment.succeeded
- A charge was captured and will settle
- payment.failed
- Declined or errored, with the reason code
- refund.completed
- A refund posted back to the customer
- settlement.posted
- A batch settled to your account, with the fee breakdown
- payout.sent
- An outbound payout left the platform
- dispute.opened
- A chargeback or pre-dispute alert was raised
- dispute.resolved
- Won, lost, or refunded before it posted
- reserve.released
- Reserve funds aged past term and released
Event names shown are representative of the categories covered. The exact schema ships with your sandbox credentials.
Questions
From engineers.
How the account itself is underwritten is on what underwriting asks for.
Get sandbox credentials.
Sandbox access is not gated on underwriting. Tell us what you are building and you will have keys, test cards and a webhook endpoint the same day.