Confirm a Validated Batch
Confirm a batch for processing. The state machine is
uploaded → validating → validated → confirmed → processing → completed|partial|failed.
Only batches in validated status may be confirmed; the batch
transitions to confirmed and then processing as payouts are
created from valid rows.
Confirmation is irrevocable — once a batch is confirmed, individual
payouts can still be cancelled (POST /v1/payouts/{id}/cancel) up until
they’re submitted to a rail, but the batch itself proceeds.
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
^bat_[a-zA-Z0-9]+$Body
Override the default funding currency for rows that don't specify one.
^[A-Z]{3}$"USD"
Response
Batch confirmed and queued for processing.
A batch upload. Moves through uploaded -> validating -> validated -> confirmed -> processing -> completed | partial | failed. Can be
cancelled from any pre-processing state.