Inline FX

Inline FX allows you to convert and disburse funds in currencies you do not hold — or do not want to hold — on your Verto wallet. Rather than pre-funding a wallet in the destination currency before making a payout, the FX conversion and payout are executed atomically in a single API call.

This is useful in two scenarios:

• Non-holdable currencies — some currencies cannot be held in a Verto wallet due to regulatory restrictions in the destination market. Examples include INR, EGP, ETB, GHS, BDT, PKR, IDR, and others. For these currencies, Inline FX is the only available payout method.
• Holdable currencies where you prefer not to pre-fund — even where a wallet could be created, you may prefer not to hold a balance in that currency due to FX risk, operational preference, or capital efficiency. Inline FX works for any currency Verto supports for payout, not just non-holdable ones.

How it works

Inline FX uses the single-step Exchange & Payout API — a single API call that combines the FX conversion and the payout to the beneficiary in one atomic operation. There is no separate FX booking step; the rate is quoted, locked, and executed as part of the same request.

See the Single-step flow: Exchange & Payout API guide for full integration details and API reference.

Pre-funded vs post-funded

Inline FX supports both funding models:

Pre-funded (instant) — your source wallet already holds a balance in the sell currency. The FX conversion executes immediately against your existing balance and the payout is initiated straight away. Set paymentMode to immediate in your rate request.

Post-funded (fund later) — you book the rate first to lock the conversion, then fund the trade within 24 hours. Once Verto detects the incoming funds (typically within 15 minutes of receipt), the conversion executes at the locked rate and the payout is initiated automatically. Set paymentMode to later in your rate request.

Payout rail

The payout leg of an Inline FX transaction uses the same rails as any other Verto payout. Depending on the destination market this may be:

• Local payment rails (domestic bank transfer)
• SWIFT (international bank transfer)
• Mobile money (Kenya, Tanzania)

The beneficiary must be created before initiating the payout, with the correct account details for the destination market.

See the Bank codes & market requirements guide for required fields by market, and the Making Payouts guide for full details on supported rails.

Sender object

For fintech and FI clients making Inline FX payouts on behalf of underlying customers from a master wallet, the sender object must be included in the payout request. This is not required for corporate principal-basis payouts or payouts from a sub-account.

See the Sender object guide for full details.

Payout statuses & webhooks

Webhooks are recommended for real-time status updates rather than polling.