Multi-channel Payment Gateway

Multi-channel Payment Gateway

Adding a payment channel used to take weeks of custom integration. After this gateway, it took days — just a new adapter and a routing rule. I led the same nine-person team that built the remittance platform. Together we shipped this gateway to support multiple payment channels with one consistent transaction status.

Challenge

The business needed one payment entry point for several providers and channels. Operators had to read payment status fast, reconcile settlement data, and keep payment workflows aligned with remittance transfers.

Solution

Every payment provider has its own API, its own definition of success, and its own failure modes. Provider adapters normalized these differences, so operators learned one set of statuses, not each provider's own.

Money also can't be double-counted. Idempotency keys and strict transaction state tracking meant a retry never created a duplicate charge, even under network instability.

Routing rules let the team assign providers to corridors without touching code. Reconciliation was built into the data model from day one, not bolted on at month-end.

Impact

Adding a channel now takes a new adapter and a routing rule, not weeks of custom integration. The gateway shares the same transaction status model as the remittance platform, so transfers and payments stay in sync. Teams no longer reconcile across two different truths.