Payments / RailsSPEI
SPEI
Mexico's interbank electronic transfer system. Used for pay-in and pay-out in Mexico.
Rail overview
Use SPEI to withdraw MXN from an internal Conomy account to a Mexican bank account.
After capture, Conomy sends the payout through the provider and updates the payment when the bank rail confirms completion or failure.
Validate CLABE and recipient identity data before capture; Mexican bank payouts are sensitive to account-number correctness.
Required fields
Section titled “Required fields”| Field | Type | Description |
|---|---|---|
type | string | Must be "SPEI" |
currency | string | Must be "MXN" |
spei.customer.firstName | string | Customer’s first name |
spei.customer.lastName | string | Customer’s last name |
spei.clabe | string | 18-digit CLABE (required for pay-out) |
spei.bankId | string | Bank identifier code |
Pay-in example
Section titled “Pay-in example”For pay-in, the user sends a transfer to the CLABE generated in the response:
{ "type": "SPEI", "currency": "MXN", "spei": { "customer": { "firstName": "Carlos", "lastName": "Mendoza" } }}Pay-out example
Section titled “Pay-out example”For pay-out, provide the recipient’s CLABE:
{ "type": "SPEI", "currency": "MXN", "spei": { "clabe": "032180000118359719", "customer": { "firstName": "Ana", "lastName": "López" } }}Response fields (pay-in)
Section titled “Response fields (pay-in)”| Field | Description |
|---|---|
clabe | CLABE the payer should transfer to |
bankId | Receiving bank code |
Share the spei.clabe with your user so they can complete the transfer from their banking app.
Object
Section titled “Object”CLABE (18-digit interbank code) of the recipient. Required for pay-out.
Information on who pays the transaction
idstringUnique identifier for the internal service.
firstNamestringrequiredPayer's name
emailstringPayer's email
lastNamestringPayer's last name
phoneNumberstringPayer's phone number without prefix
phoneNumberPrefixstringPhone number prefix (e.g., +57)
documentTypestringDocumeny type of the entity (e.g., RUT, CURP, CURL). Go to the Supported Identity document types page for the complete list of supported values.
documentNumberstringThe document number associated with the documentType
addressobjectThe entity’s address information.
administrativeAreaLevel1stringThe first-level administrative division.
administrativeAreaLevel2stringThe second-level administrative division.
administrativeAreaLevel3stringThe third-level administrative division.
streetstringThe name of the street.
streetNumberstringThe street number.
optionalAddressstringAdditional address details.
countrystringCountry of operations for the entity, specified using the ISO 3166-1 alpha-3 standard (e.g., CHL, USA, MEX). Go to the countries page for the complete list of supported values.
zipcodestringZipcode f the address