Gateway lock-in is the condition where switching payment processors is technically possible but operationally prohibitive. Your payment tokens are gateway-specific. Your custom integration code references gateway-specific APIs. Your reconciliation workflows depend on gateway-specific reporting formats. The result is that when your processor raises rates or a competitor offers better terms, migration costs and operational disruption make switching impractical. Your processor knows this, and your fee structure reflects it.
The direct fee impact of lock-in manifests in four categories. First, interchange markup: single-gateway processors have no incentive to minimize interchange costs because they profit from the markup. A locked-in merchant typically pays 20 to 40 basis points above optimal interchange rates across their transaction mix. On $1 million in monthly card volume, that is $24,000 to $48,000 per year in excess interchange markup alone. Second, processing fees: without competitive leverage, per-transaction fees remain at initial contract rates rather than declining with volume growth. Companies that renegotiate with multi-gateway leverage typically achieve 10 to 25 basis point reductions.
Third, gateway fees: many processors charge monthly gateway fees, batch fees, statement fees, and PCI compliance fees that aggregate to $200 to $800 per month in fixed costs independent of transaction volume. These fees are rarely negotiated because merchants do not perceive them as significant individually — but at $2,400 to $9,600 annually, they are material. Fourth, opportunity cost: single-gateway merchants cannot route transactions to the lowest-cost processor based on card type, transaction amount, or risk profile. Intelligent routing across two or three gateways typically saves an additional 15 to 30 basis points on the overall fee structure by directing each transaction to the processor that offers the best rate for that specific transaction type.
The switching cost calculation explains why lock-in persists. Migrating from one gateway to another requires re-tokenizing stored payment methods (or collecting new card details from every customer), rewriting API integrations, reconfiguring reconciliation workflows, and testing the new settlement process. For a mid-market company with 500 active accounts and a custom integration, the migration project typically costs $30,000 to $80,000 in development time and takes 2 to 4 months. Companies rationally conclude that staying with a suboptimal processor is cheaper than migrating — which is precisely the lock-in dynamic the processor relies on.
A gateway-agnostic payment architecture eliminates lock-in by abstracting the gateway layer. Payment tokens are managed at the platform level, not the gateway level. API integrations connect to a unified payment orchestration layer, not directly to a specific processor. Reconciliation consumes a normalized data format regardless of which gateway processed the transaction. This means adding a new gateway takes days instead of months, switching processors requires no customer-facing changes, and your negotiating position with every processor improves because migration is no longer a prohibitive event.