Payments
Accept card payments through one API.
Create a payment intent, send your customer to a hosted checkout and follow the payment through every state until it succeeds.
How a payment moves
Payment intent
One object holds the amount, currency, description and full lifecycle of the payment.
Authorization
The payment is authorized before funds move, so you can validate the order first.
Capture
Capture automatically at authorization, or manually once you are ready to collect.
Cancellation
Cancel a payment that was never captured, with the state machine enforcing valid transitions.
What you get out of the box
- Strict state machine — no invalid transition is ever persisted
- Idempotency-Key support on every creation call
- Hosted checkout: card data never touches your servers
- Signed webhooks for each payment state change
- Masked payloads in logs, dashboard and notification emails
- Full payment history and event trail per company
Refunds
Refunds are on the roadmap and are not exposed by the API yet. Today a payment that has not been captured can be cancelled. Follow the changelog for availability.
Run your first payment.
Generate a Sandbox key and take a payment through checkout to the webhook in minutes.