Cancel a Payout
Cancel a payout that has not yet been submitted to a rail. Cancellation is
only possible from created, pending_screening, pending_approval,
pending_engine_review, or manual_review. Once a payout reaches
processing or beyond, it cannot be cancelled via the API — contact
support if you need to halt a payout in flight.
Any debited source funds (source amount, fee, and cross-currency buffer) are released back to the merchant balance on successful cancellation.
Requires an Idempotency-Key header.
Authorizations
Per-request DPoP proof JWT (RFC 9449). MUST accompany the Authorization: DPoP <access_token> header on every protected operation. The proof is signed by the merchant's private DPoP key and carries htm, htu, iat, jti, and ath claims.
Headers
Unique key identifying this operation. Sending the same key twice returns the original response instead of creating a duplicate. Keys are retained for 24 hours.
255Path Parameters
^pay_[a-zA-Z0-9]+$Body
Response
Payout cancelled.
A single payment from your merchant balance to a beneficiary's instrument. Moves through a 13-state machine — see the How Anton Evaluates Payouts guide.
Rail-specific fields (rail_provider, rail_reference, network,
wallet_address, tx_hash, etc.) populate as the payout moves through
approved -> processing -> sent -> completed.