Endpoint MigrationThe
/v1/automations endpoints have been renamed to /v1/payment-routes. The old /v1/automations paths remain available as deprecated aliases during migration. Update your integrations to use /v1/payment-routes as the deprecated endpoints will be removed in a future release.Differences from USD offramps
Step 1: create a payment account
Before creating an MXN offramp payment route, register the beneficiary’s Mexican bank account as a payment account. The key difference is usingmxn as the currency, mx_spei as the rail, and providing a clabeNumber instead of accountNumber and routingNumber.
Request
Response
Required fields for MXN/SPEI
Beneficiary type and name fieldsSet
beneficiaryType to either individual or business. The name fields you must provide depend on this value:- Individual: provide
beneficiaryFirstNameandbeneficiaryLastName. - Business: provide
beneficiaryBusinessName.
Unlike USD payment accounts, MXN/SPEI accounts only require a
clabeNumber
(18-digit CLABE) and beneficiaryType. They don’t need accountNumber,
routingNumber, bankAccountType, beneficiaryAddress, bankName, or
bankAddress.Step 2: create an offramp payment route
Once you have a payment account, create the offramp payment route. The request and response follow the same structure as the standard offramp, with MXN as the destination:Response
depositAddress triggers a conversion and SPEI transfer of MXN to the user’s bank account.
MXN payment routes can’t be updated after creation. To change one, delete the
route and create a new one.