Walkthroughs that assume you have other things to do
Each guide is a complete task: what to build, what to watch out for, and what usually goes wrong the first time. Code is runnable against sandbox as written.
Pick a task
Eight guides, ordered by how soon you will need them
Accept your first payment
Create a payment intent, present hosted checkout, and confirm settlement using webhooks rather than a redirect.
Open guideSend a payout batch
Build a batch, dry-run it, dispatch ten thousand legs, and recover the handful that fail without re-running the rest.
Open guideSwap between assets
Quote, lock, and execute a conversion across chains — including how to handle an expired quote gracefully.
Open guideHandle webhooks reliably
Verify signatures before parsing, deduplicate on event ID, and replay a delivery window after an outage.
Open guideReconcile your ledger
Model value movements as entries rather than balances, and join them to your own books on your reference.
Open guideDesign for idempotent retries
Derive idempotency keys from your domain, and understand why deriving them wrongly is worse than not sending one.
Open guideGo live without surprises
The checklist we would want to see completed before anyone points production traffic at a payment provider.
Open guideTest against deterministic fixtures
Trigger any terminal state on demand, simulate slow chains, and force any documented error code in sandbox.
Open guidePrefer reference over narrative?
The API reference documents every endpoint, parameter, status, and event with the same care as the guides, minus the storytelling.
API referenceOr skip straight to code
Typed clients for TypeScript, Go and Python, plus a CLI that tunnels webhooks to localhost and triggers any event on demand.
SDKs and libraries