Telcel · Claro Pay · 2024 — 2025
Designed Telcel's payment orchestration platform end to end: one gateway for every sales channel, many payment engines behind it, with retries, anti-fraud scoring and PCI DSS-compliant tokenization.
- Client
- Telcel · Claro Pay
- Role
- Solution architect · PCI DSS
- Year
- 2024 — 2025
Outcomes
Context
Telcel collects payments through many channels — the self-service portal, Telcel.com, the Claro Pay wallet and partner channels — and each one used to integrate payment providers on its own. I designed the Gestor de Pagos: a single orchestration layer every channel calls, which routes each transaction to the right payment engine, scores it for fraud, keeps card data inside a tokenized vault and retries what fails — while keeping the PCI DSS scope as small as possible.
What I built
- 01
The architecture: an orchestrator/gateway with asynchronous workers in front of 8+ payment engines (banks, card acquirers, cash networks, wallets), exposed to channels through payments, payment-methods, card-management and auth microservices.
- 02
Every kind of payment method behind one contract: cards, bank debits, cash references and wallets — adding a new engine doesn't touch the channels.
- 03
Reliability: retry policies for failed transactions, Kafka-driven payment notifications and scheduled jobs, on a four-node gateway and application cluster behind Nginx.
- 04
Risk: a customer payment profile that feeds scoring, a transaction profiler and an external anti-fraud engine before a charge is authorized.
- 05
PCI DSS by design: card data is tokenized and isolated in a dedicated vault (HashiCorp Vault plus a segregated vault database), so channels never handle it; configuration and secrets live in Consul and Vault.
- 06
Operations: back-offices for transactions and business rules, dashboards, alerts and reports, ELK observability and Jenkins CI/CD — sized as a 34-server production design.