Why BINs matter
Every card transaction begins with the network looking up the BIN to determine where to route the authorization. The BIN identifies the issuing bank, the card product (debit, credit, prepaid, commercial), and a host of attributes that drive interchange, fraud screening, and rail selection. Without a BIN, your card is plastic.
For a fintech, the BIN range your cards sit on is one of the most consequential portability questions in the program. A BIN owned by your sponsor bank can move with you if the bank moves; a BIN owned by your BaaS platform usually cannot.
When BIN ownership matters
It matters most at three moments: (a) at program launch, when the BIN range is assigned and the network records the issuer; (b) when scaling, because a fintech outgrows a small shared BIN range and needs its own; and (c) at exit, when the question of whether the BIN ports to a new sponsor bank determines whether you can keep your existing cards live during migration.
Common pitfalls
- 8-digit migration. Card networks have shifted from 6-digit to 8-digit BINs to expand capacity. Some legacy systems still hash on the first 6, which creates collision risk in modern programs.
- Shared BINs. Operating on a BaaS platform's shared BIN range means your cards look like every other fintech's cards to the networks \u2014 and your portability depends on the platform's cooperation.
- BIN routing tables. Merchants and acquirers maintain their own BIN routing tables; new BIN ranges sometimes get mis-categorized at the merchant level and cause unexpected declines.
The BIN looks like metadata. It is actually a portability decision.