Skip to main content
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.
MXN onramps follow the same flow as standard onramps, but with MXN as the source currency and SPEI as the rail. This guide covers only the differences. Refer to the onramps guide for the full integration flow, managing payment routes, webhooks, and settlement details.

Differences from USD onramps

Create payment route request

When creating an MXN onramp payment route, set source.currency to mxn and source.rail to mx_spei:

Deposit address

The key difference is the deposit address returned in the response. For MXN onramps, the fiat deposit address contains a clabeNumber (CLABE, Clave Bancaria Estandarizada) and a transferMessage reference instead of a US bank account number and routing number:
The user initiates a SPEI transfer to the provided CLABE number, including the transferMessage as the transfer’s concepto so Rain can match the deposit. Once Rain receives the MXN deposit, it converts the funds to the destination stablecoin and delivers them to the specified onchain address.