Skip to main content
Get a token with POST /v3/auth/login. The batch uses the partner balance for each currency and processes payments in the submitted order. This endpoint keeps its fields in snake_case.

Batch API reference

Review the full contract and try the endpoint.

Request

Funding uses the partner balance (balance). The request does not take funding_source, asset_deposit, or blockchain, and the response does not include a crypto deposit address.

Response: HTTP 200

The top-level transaction_id equals external_reference. batch_id identifies the batch at the provider. The transactions results preserve the request order and contain the individual bank identifier for each payment.
HTTP 200 and success: true do not confirm settlement of all payments. success is true when at least one payment was authorized. Always check each transaction status.

Partial authorization due to insufficient funds

The balance is evaluated per currency in the request order. Payments with sufficient funds are sent to the provider with status PENDING; the others return FAILED. If at least one payment is authorized, success remains true:
If no payment has sufficient funds, the response still uses HTTP 200 and returns success: false, batch_id: null, the message Insufficient balance to create ACH payout batch., and all payments with status FAILED.

Retrieve status

Use the batch external_reference as transactionId to retrieve the status of all its payments. You can also use the top-level response transaction_id, which has the same value. This query looks up the batch reference.

Errors

Payments rejected due to insufficient funds are reported inside transactions in the HTTP 200 response.