Skip to main content
Errors return a stable machine-readable code. Branch on the code, never on the message or on the HTTP status alone, because several codes share a status.
Every error response echoes the Stableyard-Version header, so a report can be tied to the contract that produced it.
Some errors return conflict at the top level while the specific cause appears in a nested details.code. Read the nested code when it is present.

Request and authentication

Accounts and compliance

Idempotency and concurrency

Payments

Escrow and settlement

Refunds

Infrastructure

Retrying safely

Never create a replacement payment to work around a stuck one. Reuse the original payment and its key. A new payment for the same order is how duplicate payouts happen.

Next

Idempotency

How keys make retries safe.

Status codes

Payment, deposit and refund states.