Before you start
- Your organization must be enabled for MXN. Until it is, a request in it fails with
403PAYOUT_CURRENCY_NOT_ENABLED. - The recipient’s account needs the Mexican-peso receiving capability, ACTIVE before you pay. Capabilities lists the id, and Be paid in Mexican pesos lists the identity the recipient owes.
- MXN has no sending capability. Don’t send a
senderon a quote or payout, or it fails with422SENDER_NOT_SUPPORTED. - Every
POSTneeds anIdempotency-Keyheader. See Idempotency.
Register the bank account
A Mexican bank account is identified by its CLABE and paid over SPEI, which settles each transfer individually in real time. The recipient owes an RFC or a CURP, or for an organization an RFC. See Be paid in Mexican pesos. Register the account withroutingFamily MX_LOCAL and the CLABE as accountNumber. Send accountHolderName only if the bank holds the account under a different name from the account’s.
cURL
Memos
On SPEI, areceiverMemo is at most 40 letters, digits, and spaces. A memo that is too long or holds any other character fails with 400 RECEIVER_MEMO_INVALID. OpenFX never truncates it.
Track settlement
settlementTraceId on a SPEI payout has the key TRACKING_KEY, the clave de rastreo that the receiving bank uses to find the transfer. Trace a payout with the receiving bank lists the key for every rail.
Common mistakes
- Naming a
sender. MXN has no sending capability. Removesenderfrom the quote and the payout. - Sending
purpose. Only AED takes one. - Treating a pending ownership check as a block. A payout can be created while SPEI_ACCOUNT_OWNERSHIP is still PENDING. A later NO_MATCH still rejects the address.
What’s next
Payout lifecycle
The general payout flow.
Capabilities
The receiving capability and identity each currency needs.
EUR payout integration guide
Paying euro accounts over SEPA or SWIFT.
COP payout integration guide
Paying Colombian bank accounts and Bre-B keys.
AED payout integration guide
Paying UAE bank accounts by IBAN.
Payment Webhooks
Every payout and address event.