Connecting Multiple Payment Services

Connecting Multiple Payment Services

This payment gateway brings several providers into one workflow. I led the nine-person team that also built the cross-border money transfer platform. Adding a payment channel had taken weeks of manual integration; the organized integration workflow reduced that to days.

Challenge

Each provider has its own API, status definitions, and failure handling. Operators need to check payments, reconcile settled funds, and keep payments aligned with money transfers. Retrying requests during network disruption also risks duplicate transactions.

Solution

The team built adapters for each provider and gave transaction status a consistent definition. Operators use one status list without learning each service’s terminology.

Each transaction request receives a unique identifier. The system uses it to recognize retries and avoid duplicate charges. Status history helps teams investigate transactions that have not completed.

Provider selection rules can be configured without changing code for each transfer route. Reconciliation was planned early so teams can compare internal records with provider reports.

Impact

Adding a channel uses a new adapter and a provider selection rule. The gateway shares a status model with the money transfer platform. Operational teams get consistent records for reviewing payments and transfers.