The real cost of adding a second payment provider
A second connector changes routing, transaction state, support and reconciliation—not only API integration effort.
The first provider can be integrated as a path. The second turns that path into a system. Selection, fallback, state normalisation and financial matching all become explicit platform responsibilities.
Two APIs create one internal language problem
Providers describe similar outcomes with different status codes, identifiers and event timing. The payment platform needs a stable internal transaction model so merchants and operators do not inherit those differences directly.
That model must preserve provider detail for investigation while still producing a consistent merchant-facing result. Without it, every new connector leaks more special cases into the product and support workflows.
Failover is a transaction-state decision
Sending an attempt to the second provider is safe only when the first outcome is understood. A clear decline, a timeout and a late webhook are not equivalent. Cascading rules need idempotency, eligibility and terminal-state handling before they can improve resilience.
This is why routing should be observable. Operations need to see which route was selected, why it changed, what each provider returned and which result became final.
Finance inherits another external truth
The second provider adds a different fee schedule, settlement report, payout timeline and reconciliation format. If those records are handled outside the transaction model, finance has to rebuild the story after processing has finished.
- Normalise transaction identifiers and states
- Map fees and settlement records to internal movements
- Track unmatched and late records as exceptions
- Keep route history available during reconciliation
Treat the connector as an operating capability
The engineering estimate should include certification, monitoring, support tools, reconciliation and ongoing API change—not only the happy-path request. An orchestration layer earns its place when it makes the third and fourth provider more predictable than the second.