Sending transfers

A bank transfer is a payout: money leaves your Mono account and lands in a beneficiary's bank account. Mono routes transfers across three rails — ACH for standard same-day transfers, Transfiya for transfers within a specific bank cluster, and Mono Turbo for real-time transfers to participating banks — and falls back automatically when a rail does not support a destination.

Use this flow for payroll runs, vendor settlements, marketplace seller payouts, refunds, or any case where your business pushes money out to a known bank account.

Before you start

You will need:

• A Mono account with Banking enabled and an API key. See Authentication.
• Sufficient balance in the source account to cover the transfer plus any fees.
• A webhook endpoint that can receive bank-transfer events.
• Familiarity with the transfers concept.
• An idempotency key per transfer to make retries safe.

Sequence overview

1. Prepare the transfer — collect the destination account, amount, currency, and routing preference (turbo, transfiya, or ach). Generate an idempotency key.
2. Submit — call POST /transfers. Mono creates the transfer in created state and groups it into a batch. The response confirms acceptance, not credit.
3. Receive confirmation — Mono fires bank_transfer_approved when the rail credits the destination, or bank_transfer_rejected if it is declined. The terminal transfer states are approved and declined.
4. Handle fallbacks — if the primary rail fails, Mono retries using the fallback_routing you specified and fires bank_transfer_fallback_routing before the final result.

Steps

The full step-by-step (one-off and batch transfers) is pending. Until it is published, see:

• The transfers concept page for routing options, fallbacks, and states.
• The bank-transfer webhook page for the event payloads.

Next steps

• PSE collection — the payin counterpart of this flow.
• Banking webhooks — the events that drive confirmation and fallback handling.
• Idempotency Keys — required for safe retries on every transfer.