Escrow
Protected orders, dispatch confirmation and disputes.
Escrow holds a buyer’s money until delivery is proven, so neither side has to trust the other first. It is the one product with a lifecycle you must follow in order rather than a set of independent calls.
A merchant registers the sellers who receive payouts. Creating a transaction returns the account number the buyer pays into. The seller then marks dispatch, and the buyer confirms delivery with a token — only then is the transaction eligible for release to the seller.
A dispute can interrupt that path at any point, raised by the buyer, the seller or the merchant, with evidence attached as a multipart submission.
Base URL
Escrow operations are documented as paths under /api/merchants, /api/Transaction, /api/Disputes and /api/Payment. The Escrow API host is issued with your sandbox keys.
Operations by area
- Merchants & sellersCreate and authenticate a merchant, and register the sellers who receive payouts.4 endpoints
- Protected ordersCreate protected transactions, look them up, list banks, and cancel orders.5 endpoints
- Dispatch & confirmationRecord and confirm dispatch, and validate the buyer's delivery code.3 endpoints
- DisputesRaise buyer, seller or merchant disputes and attach seller responses.4 endpoints
- Payments & payoutsResolve settlement accounts, handle callbacks, confirm funding, release to seller.4 endpoints