Mandates
Signed, single-purpose permission to pay — issued by you, confirmed by your user, verified before money moves.
A mandate is a user's signed agreement that an agent may charge a specific instrument, for a specific payee or budget, within limits. Issue one, have the user confirm it, and you get back an ES256 JWT; verify it against the exact charge before settlement. You call /v1/mandate; we sign, store and check.
Every call needs your API key. See Keys and environments.
Start here
The guides in this section are published by the Mandates API itself and stay in step with it. Read them in order, or jump to the one you need.
Mandates overview
What a mandate is, the lifecycle and statuses, closed versus open mandates, money and time, what the token carries.
Getting started with Mandates
Your first mandate, call by call: issue, confirm, verify the charge, read it back, revoke.
Mandate constraints
Every constraint type, the charge fields they judge, fail-closed rules for unknown and category-scoped constraints.
Checks, results and errors
HTTP statuses versus in-body refusals, every verification check in order, and the audit trail.
API reference
Every endpoint, request and response, with a playground to call it from here.
Accept a card payment with the Payment SDK
The handoff token from prebook, mounting the widget, reading the outcome, completing the booking — plus the SDK's options, methods and error names.
Understand Mandates
Start here: how consent becomes signed payment authority, who owns each step, and when to choose closed or open.