Multi-channel Payment Gateway

Multi-channel Payment Gateway

This payment gateway was the second product I led with the same nine-person engineering team, built alongside the remittance platform. The goal was to support multiple payment channels while keeping transaction status, reconciliation, and operational reporting consistent.

Challenge

The business needed a single payment entry point for several providers and channels. Operators had to understand payment status quickly, reconcile settlement data, and keep payment workflows aligned with remittance transfers.

Solution

The gateway was built around two hard problems. First, every payment provider has its own API, its own idea of "success," and its own failure modes. Provider adapters normalized these differences so operators only had to learn one set of statuses. Second, money 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 configure which provider handled which corridor without touching code. Reconciliation was built into the data model from day one, not bolted on at month-end.

Impact

Before the gateway, adding a new payment channel meant weeks of custom integration work. After, it meant configuring a new adapter and routing rule — usually days. The gateway shared the same transaction status model as the remittance platform, so transfers and payments stayed in sync without teams reconciling across two different truths.