Skip to main content
The Pagos BIN Database is a powerful tool that provides detailed bank and market data for the payment cards your customers transact with. To augment your payments optimization strategy, we recommend pairing the information available through our BIN Database with other card network services like the Account Updater API and Network Tokenization API.

​
Creating Rules around Tokenization and Account Updates

The Pagos Network Tokenization API offers quick and easy access to global network tokens from all four major card brands with a single integration, while our Account Updater tools are account lifecycle management services for keeping card-on-file account information up-to-date for all major card brands. The Pagos BIN Database provides BIN attributes to help you better understand your customers’ PANs; with this information, you can make better decisions around how to process and store those cards. If you’re using Network Tokenization or Account Updater, you can also use that data to create and manage rules around how, when, or if certain PANs should be sent for tokenization or account updates. Here are just a few examples of the BIN data attributes you can integrate into your network tokenization and account updater strategies to make them more efficient or optimize for cost savings:
  • Card Type – When you know the type of cards your customers transact with, you can build rules around which cards you tokenize or update. If your historical processing data shows that non-reloadable prepaid cards have low approval rates or aren’t typically used for repeat purchases, you could sort out this card type from the PANs you send for tokenization. Similarly, non-reloadable prepaid cards aren’t eligible for updates through Pagos Account Updater; when you know which cards aren’t eligible for account updater, you can avoid even attempting such updates and the costs associated with the attempt.
  • Issuing Country – Certain regions have a higher issuer adoption rate for network tokenization and account updater than others. When you know what country a card is issued in, you can make decisions on a card-by-card basis as to which ones you want to tokenize or request updates on. Doing so ensures you only tokenize those cards for which you have the highest likelihood of success.
  • Token Ranges – Some card brands identify a BIN range as being a token range instead of a PAN range with a pan_or_token identifier. With this information, you can proactively exclude token ranges from those sent off for tokenization, since there’s no reason to tokenize a payment method that’s already a token.
  • BIN Ranges – Card brands identify the BIN ranges that aren’t eligible for account updater. You can then exclude any cards in these minimum/maximum ranges from your update requests.

​
Collecting Better Data

As mentioned in the section above, BIN Data’s main value-add is in helping you get to know your customer base better. When you can assign data attributes to individual BINs, you can then use those attributes to sort, analyze, and spot trends in your customer and transaction data. The same is true of your network token and account updater data! With the Pagos BIN Database, you can use eight+ digit BINs to start identifying the attributes of different BIN ranges associated with successful network tokenization or account update attempts, and adapt your processes accordingly. This analytic capability is especially important in the long run, as issuer adoption of network tokenization and account updater evolves. When you know what issuing banks or issuing countries have changed their stance on these services, for example, you can immediately adapt your network tokenization and account updater strategies to leverage the right service at the right time to optimize payment performance.