Payments · 2024
One routing layer across many gateways, with smart failover and unified reporting.
Payments
Payment Orchestration
- Role
- Lead backend engineer
- Stack
- Laravel, Redis, Horizon, AWS
- Year
- 2024
The problem
Dozens of gateways, each with its own API, webhooks and failure modes. Every new integration cost weeks and success rates varied by region.
Architecture & decisions
- +Gateway adapter contract with a normalized payment lifecycle
- +Rules-based router: region, amount, cost, live success rate
- +Idempotent webhook ingestion pipeline on queues
- +Ledger-style reconciliation jobs with alerting
12+
Gateways unified
-70%
New integration time
99.9%
Webhook delivery
Next project
Payout, Refund & Dispute Engine →