Banxico Rastreo: A Developer’s Guide to SPEI Payment Tracking
Banxico rastreo refers to the process of tracking the status of a payment made through Mexico’s real-time payment system, SPEI (Sistema de Pagos Electrónicos Interbancarios). Every SPEI transfer generates a unique 30-character tracking key called the clave de rastreo, which allows you to confirm whether the funds reached the beneficiary. For developers building payment flows, reconciliation systems, or compliance pipelines, automating this tracking is essential for reliability, fraud prevention, and audit readiness.
What Is Banxico Tracking?
Banxico tracking is the process of monitoring the lifecycle of a SPEI payment. When a transfer is initiated, the sending bank registers a clave de rastreo with the central bank’s payment system. This key acts as a transaction identifier that can be queried later to determine whether the payment was credited, rejected, or is still pending. Tracking is commonly used to:
- Confirm the successful completion of a payment.
- Detect failed or timed-out transactions.
- Reconcile accounts receivable and payable.
Provide proof of payment for regulatory or user-facing purposes.
Because SPEI is an instant payment system (most transfers settle in under 30 seconds), tracking is often needed in real-time to update user interfaces or trigger downstream actions. Developers who need to integrate this capability programmatically turn to APIs that can query the status of a given clave de rastreo against Banxico’s records.
How Banxico Tracking Works: SPEI and the Clave de Rastreo
The SPEI Payment Flow
SPEI operates as a clearing house managed by the Bank of Mexico (Banxico). When a user initiates a transfer from their bank account, the following steps occur:
- The sending bank deducts the amount and constructs a payment order containing the beneficiary’s CLABE (standardized 18-digit account number), the amount, and a clave de rastreo.
- The payment order is sent to Banxico’s SPEI system, which routes it to the recipient’s bank.
- The recipient’s bank credits the account and returns a confirmation (or a rejection) to Banxico.
Banxico stores the final status of the transaction along with the clave de rastreo.
The clave de rastreo is a 30-character alphanumeric string generated by the sender’s bank. It typically follows a format that includes the date, time, and a sequence number, but the exact structure varies by institution. The key is unique per transaction and is used to query the status.
Manual Tracking via Banxico’s Website
Banxico provides a public web portal where anyone can enter a clave de rastreo and the beneficiary’s CLABE to check the payment status. The portal returns the amount, date, time, and current status (e.g., “Liquidado” – settled, “Devuelto” – returned, “En proceso” – in process). This manual approach is fine for occasional checks, but it doesn’t scale for businesses processing hundreds or thousands of payments per day.
Why Developers Need Automated Banxico Tracking
Reconciliation for Fintechs and Payment Processors
Fintech lenders, payment gateways, and insurance companies rely on automated reconciliation to match outgoing payments with incoming confirmations. For example, a microloan platform that disburses funds via SPEI must verify that each transfer was successfully credited before updating the loan’s status to “active.” Automated Banxico tracking eliminates manual data entry and reduces the risk of errors.
Fraud Detection and Payment Confirmation in Real-Time
Fraudsters often attempt to exploit the time gap between a transfer initiation and its confirmation. By integrating tracking into your onboarding or payment flow, you can detect failures immediately and block further actions. For instance, if a user claims to have paid a registration fee but the tracking key shows a “returned” payment, you can hold the account until the payment clears.
Compliance and Audit Trail Requirements
Regulated entities under the Comisión Nacional Bancaria y de Valores (CNBV) must maintain verifiable transaction records. Automated tracking provides a timestamped, tamper‑evident log of each payment’s status, which can be used during audits. Pairing tracking with AML screening (e.g., checking the beneficiary against sanctions lists) further strengthens your compliance posture.
Integrating Banxico Tracking via APIs
What to Expect from a Banxico Tracking API
A Banxico tracking API accepts a clave de rastreo and optionally the beneficiary’s CLABE, and returns the payment status, amount, timestamps, and any error codes. The integration pattern is straightforward:
- Authentication: Most APIs require an API key or OAuth token.
- Idempotency: For retries, include an idempotency key so the same tracking request does not create duplicate records.
Webhook notifications: For async workflows, the API can send a webhook when the status changes (e.g., from “pending” to “settled”).
Key Endpoints and Data Fields (Conceptual)
Since we do not invent specific endpoints, here is a general representation of what a provider might offer:
| Field | Description |
|---|---|
clave_de_rastreo |
The 30-character tracking key from the sending bank. |
clabe |
The beneficiary’s CLABE (optional, but recommended to avoid ambiguity). |
status |
Possible values: LIQUIDADO, DEVUELTO, EN_PROCESO, NO_ENCONTRADO. |
monto |
Amount transferred (in MXN). |
fecha_operacion |
Date and time of the transaction (ISO 8601). |
fecha_confirmacion |
Date and time when the status was confirmed. |
Using the API Hub to Find Tracking Providers
API Pull does not offer a native Banxico tracking API, but our API Hub aggregates third‑party providers that do. You can browse the hub to find a tracking API that fits your volume, latency, and compliance needs. The hub also provides unified documentation and sandbox environments for testing. For exchange rate data, you can use our Banxico API to pull USD/MXN rates, TIIE, and UDI values.
Link to official Banxico SPEI technical specifications: Banxico – SPEI Technical Documentation (Spanish).
When Banxico Tracking Is the Wrong Tool
Banxico tracking is narrowly focused on payment status. It is not suitable for:
- Real‑time exchange rates: If you need live USD/MXN or TIIE rates, use a dedicated financial data API such as API Pull’s Banxico API or the Economic Indicators API.
Identity verification: Tracking a payment does not confirm the identity of the sender or recipient. For KYC compliance, pair the flow with a CURP compliance API to verify names and demographic data against the national registry.
AML screening beyond payment destinations: While tracking can confirm where money went, it does not indicate whether the beneficiary is a sanctioned person or politically exposed person (PEP). Use a dedicated Mexico AML API (e.g., API Pull’s AML API Mexico) to screen against SAT 69-B, OFAC, and UN lists.
Cross‑border payments: SPEI works only within Mexico’s banking system. For international transfers, you need a different payment rail (e.g., SWIFT, ACH).
Compliance and AML Considerations for Payment Tracking
AML Screening of Beneficiaries
Automated Banxico tracking can be integrated into a broader AML workflow. For example, when a payment is received, you can extract the CLABE (or the beneficiary’s name if available) and run it against an AML screening API. The tracking status confirms that the payment made it to the bank account, but it does not verify that the account holder is the same person you screened. To close this gap, combine tracking with name‑based screening (e.g., using the CURP or RFC) or with a beneficiary verification API.
Record Keeping and Audit Trails
Regulated institutions must retain transaction records for at least five years (per CNBV rules). An automated tracking API returns structured data (JSON) that can be stored in a database or log system. This simplifies audit preparation because you can prove the exact status of each payment at the time of query. Some providers also offer signed responses or hashes for tamper‑proof storage.
Comparing SPEI to ACH for Cross‑Border Payments
US developers may be familiar with ACH (Automated Clearing House) for domestic payments. SPEI is similar but with key differences:
| Feature | SPEI (Mexico) | ACH (US) |
|---|---|---|
| Settlement speed | Real‑time (seconds) | Batched (next day or same‑day) |
| Tracking key | Clave de rastreo (30 characters) | ACH trace number (15 digits) |
| Reversal | Only with beneficiary consent | Limited (NACHA rules) |
| Regulatory body | Banxico | NACHA / Federal Reserve |
Understanding these differences helps developers choose the right integration pattern when building cross‑border payment systems.
Next Steps for Your Integration
To get started with Banxico tracking, follow these steps:
- Explore the API Hub – Visit API Pull and navigate to the “API Hub” section to find tracking providers that offer SPEI status queries. Review their documentation, pricing, and sandbox environments.
Test with a sandbox – Most providers offer a test environment where you can simulate transfers and tracking keys. Use this to validate your integration before going live.
Combine with complementary APIs – If you also need exchange rates, identity verification, or AML screening, check out API Pull’s dedicated APIs:- Banxico API – for USD/MXN, TIIE, and UDI rates.
- CURP Compliance API – for identity verification against RENAPO.
- AML API Mexico – for sanctions and PEP screening.
Contact support – If you have questions about integrating multiple APIs or need guidance on compliance, the API Pull team is available to help. Reach out through the website or check the docs for detailed integration guides.
- Banxico API – for USD/MXN, TIIE, and UDI rates.
Automating Banxico rastreo is a straightforward way to bring reliability and compliance to your SPEI payment flows. By leveraging third‑party APIs through the API Hub, you can focus on your core product while leaving the payment tracking infrastructure to specialists.
This article is intended for informational purposes and does not constitute legal or financial advice. Always consult with a qualified professional for compliance requirements.
FAQ
Question: What is the clave de rastreo?
Answer: The clave de rastreo is a 30-character alphanumeric tracking key generated by the sending bank for every SPEI transfer. It is used to query the payment status through Banxico’s system or third-party APIs.
Question: Can I use Banxico tracking to verify the identity of the payer?
Answer: No. Banxico tracking only confirms the payment status and destination account. For identity verification, you need a separate KYC/AML API.
Question: Does API Pull offer a Banxico tracking API?
Answer: API Pull does not offer a native tracking API, but the API Hub aggregates third-party providers that do. You can browse the hub to find a suitable solution.
Question: How long does SPEI tracking data remain available?
Answer: Banxico retains transaction data for a limited period (typically 90 days). For long-term record keeping, you should store the tracking results in your own database.
Question: What is the difference between SPEI and ACH?
Answer: SPEI settles in real-time, while ACH is batched. SPEI uses a clave de rastreo; ACH uses a trace number. Reversals are also handled differently.