Allwallex API · v1

Bulk payouts.

One batch, individual payout records. Review recipients, exact costs and original transaction outcomes from a single workspace.

Testnet environment. Transactions use test assets and do not settle real payments.

01Create a batch

Bulk payouts supports up to 50 recipients sharing a ready testnet wallet, network and asset. Each batch has a unique workspace reference; each payout has its own reference and exact decimal recipient amount. Manual entry and CSV import produce the same reviewed instructions. CSV columns are reference,destination,amount, with a 64 KB file limit.

02Review the recipient list

The review separates network, crypto and recipient total. Creation atomically saves the source, full destination addresses, payout references, exact recipient amounts and individual quote requests. It reserves no funds. Addresses are checked on the exact network, including custody-destination restrictions. An invalid row rolls back every instruction and quote request.

03Authorize exact maximum debits

Select currently ready payouts and review each recipient, network, processing fee, network reserve and maximum debit. Recent passkey verification is required. The request binds the batch revision and every selected original quote ID and total debit. Fees cannot be silently changed between review and authorization.

04Keep individual outcomes

Each original withdrawal reservation commits separately with its authorization progress. A later refusal or interruption preserves earlier authorizations. The result distinguishes completed authorization from a paused request; authorization is not a blockchain confirmation. Existing source, custody, gas, balance, incident, signing and finality controls remain authoritative.

05Recover the original request

The dashboard verifies saved request storage before sending. After an interrupted or inconsistent result, recovery keeps the original key and payload. Creation recovery preserves every original recipient and amount without another batch. Check batch status only reads current records. Financial authorization recovery also needs a recent passkey and never duplicates an already recorded reservation. No automatic retry or unattended payout scheduler is implied.

06Refresh remaining quotes

Unused requests are closed and replaced atomically. Every original recipient, exact amount and quote-request version is retained. Any recorded withdrawal keeps its original request and transaction lifecycle. The batch revision advances and unfinished older authorizations are superseded. Interrupted results keep the original request for recovery without another refresh. Refreshing reserves no funds; fresh quotes require review before authorization.

07Close and reconcile

Close remaining payouts closes unused instructions in one atomic change. An interrupted result retains the original request for explicit recovery. It does not cancel, refund or replace an authorized, prepared or uncertain transaction. Payout details link to withdrawal activity, and the batch can be exported as a CSV snapshot. Quote history retains the original request IDs with 20-version pagination. Statements and original withdrawal journals remain the accounting source.

08Read recorded batch activity

Batch lists contain up to 25 retained summaries with an exact workspace cursor. Counts describe recorded authorizations and confirmations; current financial readiness comes from fresh individual payout quotes and receipts. Quote history returns up to 20 original request versions with an integer before cursor. Each retained version stays bound to its original recipient, amount, source and asset. These read-only records cannot reserve funds or authorize delivery.

09Inspect payout origins

Admin withdrawal inspection shows the original batch, source wallet, network, crypto, item position, quote version and up to ten recorded authorization actions. Recorded progress is checked against the original withdrawal receipts. Other recipients and custody credentials are omitted. Owner, Finance, Operations and Security access requires a current operator passkey. Origin inspection cannot authorize, cancel or resend a payout.

10Workspace access

Workspace members can inspect batches; owners and administrators can create or change them. Financial authorization requires a current app session and recent passkey verification. Merchant API keys and SDK 0.2.0 do not grant external bulk payout authority. Mainnet and actual service activation remain unavailable in this release.

GET /v1/workspaces/{workspaceId}/bulk-payouts
POST /v1/workspaces/{workspaceId}/bulk-payouts
GET /v1/workspaces/{workspaceId}/bulk-payouts/{id}
POST /v1/workspaces/{workspaceId}/bulk-payouts/{id}/authorize
POST /v1/workspaces/{workspaceId}/bulk-payouts/{id}/refresh-quotes
POST /v1/workspaces/{workspaceId}/bulk-payouts/{id}/close
GET /v1/workspaces/{workspaceId}/bulk-payouts/{id}/items/{itemId}/quote-history

// Mutations require a persisted Idempotency-Key.
// Authorization binds the reviewed revision and exact quotes.
{
  "expectedRevision": 0,
  "items": [{
    "id": "<payout-item-uuid>",
    "quoteId": "<original-quote-uuid>",
    "totalDebitAtomic": "31300000"
  }]
}

Open your workspace