Why network routing matters
Every US debit card transaction has at least two networks it could route across \u2014 Reg II's dual-network requirement is mandatory \u2014 and each network produces different interchange, scheme fees, and risk-management profiles. For an issuer, the routing configuration shapes interchange revenue; for an acquirer, the routing choice shapes the merchant's discount rate. For both, the network rules differ in subtle ways.
In credit-card and prepaid worlds, the routing question is simpler (one network typically owns the BIN range), but in US debit it is a meaningful economic lever.
When routing matters
It matters when: (a) negotiating BIN sponsorship, where the issuer's routing configuration shapes program economics; (b) evaluating merchant-side fees, where the acquirer's routing strategy can move basis points; (c) modeling Reg II reform, where proposed rule changes could alter the routing balance; and (d) tracking fraud and chargeback patterns, since each network has its own dispute apparatus.
Common pitfalls
- Network routing tables are not static. Updates happen frequently; programs that don't audit periodically miss revenue or pay too much.
- Reg II compliance. Issuers must enable at least two unaffiliated networks; programs that ship a single-network configuration have a regulatory gap.
- Reciprocity rules. Some network arrangements include reciprocity terms that affect economics in non-obvious ways.
Network routing looks like plumbing; it is actually one of the more meaningful economic levers in a card program.