Introduction

Build with Xpend B2B

Stablecoin-in, local-settlement-out merchant infrastructure. One API surface for collection, settlement, and reconciliation.

What is Xpend B2B?

Xpend B2B abstracts the complexity of accepting cryptocurrency payments and turning them into balances you can spend or settle locally. Instead of dealing with chains, gas, liquidity quotes, and fiat rails, you integrate one REST API.

For backend engineers

A small, predictable REST surface with HMAC-signed webhooks and explicit error envelopes.

Quickstart

For ops & finance

Reconcile every credit and payout with a deterministic ledger and delivery log.

Balances & ledger

The five primitives

Everything in Xpend B2B is one of these. Master them once, reach across the rest of the API.

Payment intents

Collect funds from customers via hosted link or QR.

POST /v1/payment-intents

Payouts

Send funds to wallets or fiat rails with cancellation safety.

POST /v1/payouts

Balances

Per-asset settlement balances.

GET /v1/balances

Ledger credits

Append-only credit history feeding balances.

GET /v1/ledger/credits

Webhooks

Async events for every state transition.

POST /v1/webhooks/endpoints

Public vs. internal APIs

Only public merchant endpoints are included in this spec. Internal admin and operator endpoints used by Xpend staff are not documented here and are not callable with merchant credentials.

Heads up

Curated by resource. For exhaustive coverage, see the auto-rendered OpenAPI explorer (coming soon to this route).

Ready to build?

Get an API key

Sandbox-only credentials, no card required.

Stuck on something?

Talk to a human

DevRel responds in office hours.

NextQuickstart