Delivery Hero · Payment Orchestration · In production
Payment Smart Routing on one screen
Smart Routing excluded underperforming payment providers automatically. I designed the solution and implemented success-rate calculation and rule evaluation.
- Situation
- Delayed success-rate reports and manual intervention slowed payment-provider failover. Failed payments could cause lost orders while Prod-Ops investigated and changed routing.
- Task
- I owned the RFC, technical design, implementation plan, and rollout planning. I also designed production metrics and dashboards.
- Action
- We chose scheduled polling and Redis buckets. I proposed an embedded gateway library. SpEL handled 50 times the expected evaluation workload. We rolled out gradually in Argentina.
- Result
- The solution reached production on PedidosYa Argentina across all payment methods. In one incident, approximately 1,300 orders completed through the backup PSP after automatic failover.
Scheduled polling
We avoided additional event infrastructure costs. Insight collected outcomes and stored one-minute buckets in Redis.
Embedded evaluation
The gateway used a library to avoid another synchronous service call. It still read Redis data and control plane configuration.
Controlled fallback
Low transaction counts left the PSP eligible. Any calculation failure bypassed success-rate evaluation and allowed processing through the selected PSP. Prod-Ops retained a fallback outside automatic exclusion.