What is SPID?
SPID (Sistema de Pagos Interbancarios en Dólares) is Banco de México's system for sending US dollars between accounts at two Mexican banks on the same day, without using the international correspondent-banking network. It runs Monday through Friday and moves USD only: for pesos you use SPEI.
Operational since 2016 under Banxico’s Circular 4/2016, SPID runs on banking business days only: customer send requests are accepted until 16:59:59 and operation closes at 17:14:59. It is restricted to legal entities domiciled in Mexico, and serves corporate treasuries, maquilas, USD payroll for executive personnel, and USD commercial settlements between Mexican entities.
How does a SPID transfer work?
A SPID transfer follows the same pattern as a SPEI one, differing in currency, operating window, and the compliance validations specific to dollar operations.
- Origination. The corporate client instructs the payment at their bank, with the destination CLABE and the dollar amount.
- Validation. The sending bank validates the message schema, the CLABE, and the compliance data of the legal entities involved, including RFC (tax registry) and LEI (legal entity identifier).
- Signature and transmission. The message is cryptographically signed and travels to Banxico over the participant's dedicated link.
- Settlement. Banxico settles against the participant's dollar balance and notifies both sender and receiver.
- Receipt and reconciliation. The electronic payment receipt is issued and the operation is reconciled against the banking core.
If an instruction arrives outside the operating window it is not rejected outright: it queues for the next business day. That is the most keenly felt practical difference against SPEI, which runs 24×7. For the full contrast between both schemes, read the guide on the difference between SPEI and SPID.
What is InterPago?
InterPago is the integration layer between your institution’s core banking system and the interbank payment systems. For SPID, we cover the full cycle: message handling, digital signature, personas-morales validation, USD balance management, electronic receipts, and reconciliation. The platform is delivered production-ready and connects to your core without requiring you to rewrite it.
We build on the official specification, not on third-party interpretations. Every component is modular, observable, and audit-ready from day one.
Problems we solve
Mid-day certificate rotation
A certificate expiring during the operating day creates a queue and rejections. We implement overlapping rotation with preload, with no traffic interruption.
Balance race conditions
Peak loads (payroll, end-of-day) can cause projected-balance inconsistencies. Per-shard processing and atomic reservations eliminate the condition.
Receipts out of sync on reversals
Reversing an operation when the receipt was already issued requires careful state handling. Our state engine guarantees consistency between payment, reversal, and receipt.
Late acknowledgments and double charges
An ack outside the window can trigger retry and double charge. Idempotency by tracking key plus persistent dedup eliminates the risk.
Post-deploy payment-flow simulation
Every deployment is validated against the simulator before touching production, synthetic end-to-end payments, and only promotes if all flows pass.
One-click switch between primary and backup
Failover and failback between primary and backup channel from a single button on the operations dashboard, no manual scripts, no cross-team coordination.
Reconciliation with integrated external systems
Cross-reconciliation across the various systems integrated with InterPago, a single dashboard shows breaks by system, counterparty, or transaction type.
Main features
The platform is designed for high volume, high availability, and traceability, these are the architectural components your team will encounter in every implementation.
Authentication & Authorisation
Corporate single sign-on with your identity provider, service identity via mutually authenticated encrypted connections, role-based permissions, and identity propagation across the entire processing chain.
Security & Key Custody
Encryption at rest and in transit. Private keys and secrets protected by hardware, never exposed on disk. Automated secret rotation.
Immutable Logs & Traceability
Immutable logs, structured events, and end-to-end trace per transaction, with full tracing and metrics across the platform.
Reporting & Reconciliation
Pre-built operational and regulatory reports. Multi-source reconciliation engine that identifies breaks by counterparty and transaction type.
Recovery & Resilience
Automated failover, journal replay, idempotent retries. Documented and measurable recovery time objectives, with a zero data loss design.
Multiple Endpoints & Integrations
Simultaneous connection to multiple cores, counterparties, and regulators. Reusable adapters, no bespoke code per new destination.
Message Transformations
Protocol mapping (ISO 20022, legacy and custom formats), schema evolution, and lossless normalisation between formats.
Configurable Validations
Schema, business-rule, compliance, and counterparty validations, all modifiable without touching code.
Circuit Breakers, Throttling & Backpressure
High-volume resilience patterns, circuit breakers per channel and counterparty, adaptive throttling, backpressure to prevent cascading failures.
Dynamic Workflow Orchestrator
Orchestration of payments, validations, retries, and compensations defined as a flow, modifiable hot, no redeploy, with visibility into every step.
Customisable Rule Engine
Business rules configurable by your team: account validation, per-counterparty limits, cut-offs, routing. Production changes without touching code.
Modular Architecture for Distribution
Components independently deployable across data centres or cloud regions, with cross-site replication and consistency for high availability and fault isolation.
Real-Time Analytics
Automated detection of operational anomalies, rising returns/rejections, throughput drop, latency degradation, counterparty pattern deviation. Actionable alerts, not just dashboards.
Compliance & controls
Every component is designed to pass regulatory inspections and internal audits, not as an add-on, but as a core part of the platform.
Per-Transaction Trace and Audit
Immutable log of every operation, structured events, and end-to-end trace, ready to present to auditors.
Regulator-Aligned Retention Policy
Immutable retention per regulator-mandated periods, with automated lifecycle to cold storage.
Maker-Checker
Dual human validation on sensitive operations: operator initiates and reviewer approves before execution.
Dual Key Control
Dual custody of cryptographic keys and critical secrets, no individual has exclusive access.
Secure Sessions and Segregation of Duties
Authenticated sessions with expiry, role-based permissions with clear boundaries between development, operations, treasury, and compliance.
Digital Signature on Every Message
Cryptographic signature on every outbound and inbound message; verification mandatory before any processing.
Restricted Personal Data Access
Personal data masked by default in logs, dashboards, and reports; full access only to authorised roles.
Sanctions and Watch-List Integrations
Pre-built hooks for international watch lists, internal lists, and specialist provider lists, configurable update cadence.
Regulatory Reports on Official Cadence
Automated generation in mandatory format and cadence; direct submission to official platforms.
Incident Reporting, Review and Submissions
Reporting templates, a structured post-incident review process, and on-time submissions per regulatory service commitments.
Regular Business-Continuity Drills
Periodic contingency drills against the simulator, with evidence of results ready for audit.
Frequently asked questions
What is SPID?
SPID (Sistema de Pagos Interbancarios en Dólares) is the dollar settlement system for USD transfers between Mexican bank accounts, bypassing the international correspondent-banking network. It serves corporate treasuries, maquilas, USD payroll, and USD commercial settlements between Mexican entities.
What are SPID's operating hours?
Monday through Friday, 08:00-17:00. SPID is intraday only and does not operate on weekends or holidays.
What currency does SPID handle?
USD only. SPID does not move pesos, for MXN transfers use SPEI.
Who uses SPID?
Corporate and institutional clients of Mexican banks: corporate treasuries, maquilas, USD payroll, and USD commercial settlements between Mexican entities.
How is SPID different from SPEI?
SPEI is for MXN and runs 24/7 with very high volume. SPID is for USD, runs Monday-Friday 08:00-17:00, and handles lower volume but typically higher value per transaction.
How does a SPID transfer work?
The corporate client instructs the payment with the destination CLABE and the dollar amount. The sending bank validates the message and the compliance data (RFC and LEI), signs it cryptographically and transmits to Banxico, which settles against the participant's dollar balance and notifies both parties. The electronic payment receipt is then issued and the operation is reconciled against the banking core.
Can SPID send dollars abroad?
No. SPID moves dollars only between accounts at Mexican banks. A dollar payment to another country still requires the international correspondent-banking network. SPID's value is precisely avoiding that network when sender and receiver are both in Mexico.
Keep reading
- Connecting to SPID with Banxico: requirements, participation and the certification process.
- Difference between SPEI and SPID: full comparison of currency, hours, users and compliance.
- SPEI and SPID audit and compliance: what regulators review and what evidence you must retain.
- Contingency: the backup modes your institution must operate and test.