A REST API over accounts, balances, payments, cards and webhooks. The application is built on it, which is the only real guarantee that it is complete and maintained.
Keys are scoped per environment and per permission. A read-only reporting key cannot move money, regardless of what code holds it.
What it gives you
No second-class API
The endpoints powering the product are the endpoints you get, so nothing is missing because it was never needed internally.
Scoped keys
Permission is a property of the key, not of the code using it.
Webhooks with retries
Events are delivered with signed payloads and a documented retry schedule.
What is included
- REST API over accounts, payments and cards
- Signed webhooks with retry and replay
- Per-environment and per-permission keys
- Idempotency keys on every write
- Sandbox with deterministic test data
- Versioned endpoints with a deprecation policy
Who it is for
Engineering teams embedding payments or reconciliation into their own systems.
Questions
Yes, with deterministic test data so a test suite produces the same result on every run.
Endpoints are versioned and deprecations are announced with a stated window before removal.