• Why Pagos
  • Solutions
    Peacock
    Payments Data Visualization
    Canary Logo
    Payments Data Monitoring
    Toucan-Logo
    Network Tokenization Services
    Loon Logo
    Account Updater Services
    Parrot Logo

    BIN Data and Insights

    Peacock

    Payment Data Visualization

    Canary

    Payment Data Monitoring

    Toucan

    Network Tokenization Service

    Loon

    Account Updater Service

    Parrot

    BIN Data and Insights
  • Docs
  • Blog
  • About
  • Why Pagos
  • Solutions
    Peacock
    Payments Data Visualization
    Canary Logo
    Payments Data Monitoring
    Toucan-Logo
    Network Tokenization Services
    Loon Logo
    Account Updater Services
    Parrot Logo

    BIN Data and Insights

    Peacock

    Payment Data Visualization

    Canary

    Payment Data Monitoring

    Toucan

    Network Tokenization Service

    Loon

    Account Updater Service

    Parrot

    BIN Data and Insights
  • Docs
  • Blog
  • About
Login
Schedule a Demo
Event Detection: A Canary That Lives Beyond the Coal Mine
October 21, 2021
A Peacock User Guide: Getting the Most Out of the Data Visualization Interface
October 25, 2021
Published by Katie McCarthy on October 22, 2021
Categories
  • Parrot
Tags
  • BIN
  • parrot

Parrot Feature Release: Creating Uniformity and Simplicity in BIN Bank Names

You’ve already learned the importance of BIN list management and recent changes to BINs overall. We have also explored the types of BIN analysis that Parrot enables. BIN list management can be a complex topic, and that complexity goes beyond mere numbers. 

On November 1, Parrot by Pagos will be updated with the ability to address one of the barriers to simpler BIN analysis: inconsistent bank names. Banks tag their BINs with non-numerical names to list certain attributes more clearly in their database. For example, adding in regions, card type, or internal team ownership. However, this makes aggregating payment data across BINs of the same bank extremely cumbersome. In fact, we know many merchants that have to frequently reconcile bank names manually in order to conduct their standard BIN analysis.

Examples of Bank Names

Each bank can have many BINs, all with distinct names. Let’s take a look at an example.

BIN

Bank Name

400127

JPMORGAN CHASE BANK, N.A.

401135

JPMorgan Chase Bank N.A.

405607

JPMorgan Chase Bank N.A.  Commercial

405954

JPMorgan Chase Bank N.A.  Debit

410499

JPMorgan Chase Bank N.A.  Prepaid Debit

In the example above, you can see that the attributes listed in the bank names could be helpful identifiers for JP Morgan Chase. JP Morgan Chase likely uses tags like “Debit” or “Commercial” for BIN maintenance. You’ll also notice that some of the bank names are nearly identical, but just use different abbreviations or punctuation. This adds unnecessary challenge in conducting a simple, consistent BIN analysis. 

If you were to import a BIN table and not take time to conduct aggregation, you would have this BIN represented twice within your data. If you did not complete the time-consuming manual aggregation yourself, you would have inaccurate groupings of customer information.

Generating Uniformity in Bank Names

Now, Pagos can do the aggregation work for you in order to unify the BIN bank name taxonomy and display BIN data by bank. Our Clean Bank Name release is an automatic matching system that groups similar bank names together and labels them with a Pagos-created simple, consistent “Clean Bank Names”. Building on our example from above, the Pagos Clean Bank Name would look something like this:

BIN

Clean Bank Name

Bank Name

400127

JPMorgan Chase

JPMORGAN CHASE BANK, N.A.

401135

JPMorgan Chase

JPMorgan Chase Bank N.A.

405607

JPMorgan Chase

JPMorgan Chase Bank N.A.  Commercial

405954

JPMorgan Chase

JPMorgan Chase Bank N.A.  Debit

410499

JPMorgan Chase

JPMorgan Chase Bank N.A.  Prepaid Debit

This update reduces manual data cleansing time required from your payments or data science teams. Ultimately, it means that you can get to the real value of BIN analysis faster than ever before. Once you are able to meaningfully group the data of the same BINs from the same bank together, you are well on your way to analyzing the insights that up-to-date BINs afford: performance of card types, customer experience, decline analysis and more.

Coming Soon to a Parrot Near You

We can’t wait to continue improving the efficiency and accuracy of your payments data analysis! Stay tuned for the Parrot Clean Names release on November 1. If you don’t already use the Parrot BIN service, check out why Parrot is a better BIN service and sign up today.

Share
4
Katie McCarthy
Katie McCarthy
Group Product Leader

Related posts

February 17, 2023

Ready for Action: Direct-to-Network and Faster to Value


Read more
February 7, 2023

Two Isn’t Always Better Than One: Argentina’s New Tourist Exchange Rate


Read more
January 13, 2023

What is Enhanced BIN Data and Why Does It Matter?


Read more

Leave a Reply Cancel reply

You must be logged in to post a comment.

Company

  • Why Pagos
  • Developers
  • Careers
  • Blog
  • Contact Us
  • About
  • Why Pagos
  • Developers
  • Careers
  • Blog
  • Contact Us
  • About

Products

  • Peacock
  • Canary
  • Toucan
  • Parrot
  • Loon
  • Peacock
  • Canary
  • Toucan
  • Parrot
  • Loon

Stay In Touch

Linkedin Twitter
Terms of Service | Terms of Use | Data Policy | Privacy Policy
Copyright © Pagos Solutions, Inc. All Right Reserved.