Mexico: MXN

Supported payment rails

Rail	Description	Settlement	Limit
`MX_SPEI`	Sistema de Pagos Electrónicos Interbancarios — Mexico's real-time interbank transfer system. 24/7/365 availability.	Instant	None

For details on rail selection, see Payment rail reference.

Beneficiary identity

When creating a beneficiary identity for MXN payments, provide the following fields. See Create and manage identities for the API workflow.

The required fields depend on whether the beneficiary is a business or an individual.

Business beneficiary

Applies to B2B, B2B2B, and C2B2B use cases. Submit a business identity.

Field	Required	Type	Constraints
`businessName`	Required	STRING	1–140 characters.
`address.streetAddress`	Required	ARRAY of STRING	Each item 1–70 characters.
`address.city`	Required	STRING	1–140 characters.
`address.stateOrProvince`	Required	STRING	1–140 characters.
`address.postalCode`	Required	STRING	3–15 characters.
`address.country`	Required	STRING	Two-letter ISO 3166-1 alpha-2 country code.

Individual beneficiary

Applies to B2C, B2B2C, and C2B2C use cases. Submit an individual identity.

Field	Required	Type	Constraints
`firstName`	Required	STRING	1–140 characters.
`lastName`	Required	STRING	1–140 characters.
`address.streetAddress`	Required	ARRAY of STRING	Each item 1–70 characters.
`address.city`	Required	STRING	1–140 characters.
`address.stateOrProvince`	Required	STRING	1–140 characters.
`address.postalCode`	Required	STRING	3–15 characters.
`address.country`	Required	STRING	Two-letter ISO 3166-1 alpha-2 country code.

Beneficiary financial instrument

When creating a financial instrument for MXN payouts, set financialInstrumentType: MX_SPEI and currency: MXN. Provide the following fields in the mxSpei payment rail object. See Create and manage financial instruments for the API workflow.

Field	Required	Type	Constraints
`bankName`	Required	STRING	2–140 characters.
`clabe`	Required	STRING	Exactly 18 digits. The beneficiary's CLABE (Clave Bancaria Estandarizada) account identification code.

Originator identity

When creating an originator identity for MXN payments, provide the following fields. The required fields depend on whether the originator is a business or an individual.

Business originator

Applies to B2B, B2B2B, B2B2C, and B2C use cases. Submit a business identity.

Field	Required	Type	Constraints
`businessName`	Required	STRING	1–140 characters.
`address.streetAddress`	Required	ARRAY of STRING	Each item 1–70 characters.
`address.city`	Required	STRING	1–140 characters.
`address.stateOrProvince`	Required	STRING	1–140 characters.
`address.postalCode`	Required	STRING	3–15 characters.
`address.country`	Required	STRING	Two-letter ISO 3166-1 alpha-2 country code.

Individual originator

Applies to C2B2B and C2B2C use cases. Submit an individual identity.

Field	Required	Type	Constraints
`firstName`	Required	STRING	1–140 characters.
`lastName`	Required	STRING	1–140 characters.
`address.streetAddress`	Required	ARRAY of STRING	Each item 1–70 characters.
`address.city`	Required	STRING	1–140 characters.
`address.stateOrProvince`	Required	STRING	1–140 characters.
`address.postalCode`	Required	STRING	3–15 characters.
`address.country`	Required	STRING	Two-letter ISO 3166-1 alpha-2 country code.

Transaction fields

No additional transaction-level fields are required for MXN payments beyond the standard payment object (quote ID, payer identity, beneficiary identity, financial instrument). Routing is handled entirely by the beneficiary's 18-digit CLABE, which uniquely identifies the destination bank, branch, and account. See Create a payment for the API workflow.

Verifying requirements for your scenario

For the exact fields required for your specific use case and payment rail, use the Payload Schema Utility.