Acme Banco Azteca Mexico Payments (API)
This describes validations / allowed data formats for Acme payments going
through Banco Azteca Mexico (AZTKMXMMXXX) over the Banco Azteca API. These
will be validated by Acme and further validated by the bank. These rules may be
stricter than what the bank requires.
Common Definitions
- All payments must be in MXN.
- CLABE (Clave Bancaria Estandarizad) is the 18-digit standardized Mexican bank account number.
MX_SPEI
SPEI (Sistema de Pagos Electrónicos Interbancarios) for interbank transfers of Mexican Pesos (MXN).
receiver.bankAccountNumberis interpreted by length:- 18 digits: CLABE
- 16 digits: card number
- 10 digits: phone number
customerReferenceis the SPEI numeric reference (referencia numérica). It must be 1 to 7 numeric digits and greater than 0.paymentDetailsis the payment reference (concepto de pago) shown to the receiver.- SPEI payments are expected to be completed within an average of 30 seconds, according to information published by Banco de México.
| field | pattern / charset | max length | mandatory/optional |
|---|---|---|---|
| customerReference | Numeric, 1 to 7 digits, greater than 0 Example: 1234567 | 7 | M |
| paymentDetails | Free text | 30 | M |
| receiver.name | Free text | 60 | M |
| receiver.bankAccountNumber | Numeric: 18 digits (CLABE), 16 digits (card), or 10 digits (phone) | 18 | M |
| receiver.localRoutingIdentifier | Banxico bank code of the beneficiary bank Example: 40128 | M |
Example Request:
{
"type": "MX_SPEI",
"amount": 150000,
"currency": "MXN",
"senderAccountId": "intacc_0H3BQNTQGBW2W",
"customerReference": "1234567",
"paymentDetails": "Payment for invoice 001",
"receiver": {
"name": "Juan Pérez García",
"bankAccountNumber": "012180012345678901",
"localRoutingIdentifier": "40012"
}
}BKTR
In-house book transfer between Banco Azteca (AZTKMXMMXXX) accounts.
paymentDetailsis the debit reference (concepto de pago) shown on the sender's statement.customerReferenceis the payment reference (concepto de pago) shown to the receiver.- If
customerReferenceis omitted, Acme default the mandatorypaymentDetailsvalue in both fields. - The beneficiary account is always treated as a checking account.
- Book transfers (traspasos) and comprobantes are expected to be completed within 1 minute.
| field | pattern / charset | max length | mandatory/optional |
|---|---|---|---|
| customerReference | Free text | 30 | O |
| paymentDetails | Free text | 30 | M |
| receiver.name | Free text | 60 | M |
| receiver.bankAccountNumber | Numeric Banco Azteca account number (14 or 20 digits) | 20 | M |
Example Request:
{
"type": "BKTR",
"amount": 150000,
"currency": "MXN",
"senderAccountId": "intacc_0H3BQNTQGBW2W",
"customerReference": "Pago de servicios",
"paymentDetails": "Payment for invoice 001",
"receiver": {
"name": "Comercializadora Azteca SA de CV",
"bankAccountNumber": "12345678901234"
}
}Bank references
bankReference is Banco Azteca's reference for the payment. bankReferences lists every reference Banco Azteca sent, keyed by Banco Azteca's field name.
| Type | bankReference | Available from |
|---|---|---|
MX_SPEI | claveRastreo, the SPEI tracking key | Banco Azteca accepts the payment |
BKTR | numeroMovimiento, Banco Azteca's movement number | The book transfer completes |
Other keys in bankReferences:
folioOperacion: Banco Azteca's operation folio, sent withbankReference.numeroMovimiento(MX_SPEI): Banco Azteca's movement number, when it sends one. At submit it usually sends0, meaning no movement yet, and Acme leaves that out.fechaOperacion: the operation date. It's a date, not a reference.
Good to know:
- For
MX_SPEI, the references show while the payment is still in progress. - For
BKTR, if Banco Azteca sends anumeroMovimientoof0,bankReferenceisnull. - A rejected payment keeps the references Banco Azteca sent before rejecting it.
- Until Banco Azteca answers,
bankReferenceisnullandbankReferencesis{}.
A completed MX_SPEI payment returns:
{
"bankReference": "210114010000151200I",
"bankReferences": {
"claveRastreo": "210114010000151200I",
"folioOperacion": "44860",
"fechaOperacion": "2026-05-19"
}
}