How bulk transfers work
-
Prepare your batch
Build an array of transfer instructions (amount, destination account number, bank code, narration, unique reference for each row). -
Validate accounts (optional, recommended)
Optionally run account‑number + bank‑code pairs through the validate‑account endpoint before including them in the batch. -
Call the bulk transfer endpoint
Use the Bulk Transfer operation under Transfers to submit the entire batch in one API call from your business wallet. -
Track batch result
The response returns:- a
batch_reference - counts for
successful_count,failed_count, andtotal_count - the
total_amountprocessed
- a
-
Reconcile individual transfers
Use the transfer‑status and wallet‑transactions endpoints to drill into each transfer in the batch and reconcile them with your internal records.
Best practices
- Batch sizing: start with batches of 50–100 transfers per call to balance speed and observability.
- Idempotent references: ensure each row in a batch has a unique reference so you can safely retry if there is a network error.
- Monitoring: log and alert on high
failed_countfor a batch and surface reasons back to your operations dashboard.
For detailed request/response payloads and code examples, use the Transfers API reference for the bulk‑transfer and transfer‑status endpoints, plus the Wallets API for balance and transactions.
