Skip to main content


         This documentation site is for previous versions. Visit our new documentation site for current releases.      
 

Impact on migrating to 8-Digit BIN

Updated on March 9, 2022

The Issuers that use Smart Dispute BIN data transform rules to populate the Issuer Details page can plan whether to move to 8-digit BIN or use 6-digit BIN or a combination of both. However, the Issuers need to make necessary configurations based on the plan.

Pega Smart Dispute for Issuers

The following factors affect migrating to an 8-digit BIN:

  1. If you are an issuer that does not use Smart Dispute BIN data transform rules to populate the Issuer Details page and that has a custom configuration to populate the Issuer Details page from the system of records, this fix from Smart Dispute will not affect your system. Ensure the ‘8DIGITBIN’ DSS is always set to false in your system.
  2. If you are an issuer that uses the Smart Dispute BIN data transform rules to populate the Issuer Details page and plans to use only 6-digit BINs but do not plan to move to 8-digit BINs, this fix from Smart Dispute will not affect your system. Ensure the 8DIGITBIN DSS is always set to false in your system.
  3. If you are an issuer that uses Smart Dispute BIN data transform rules to populate the Issuer Details page and plan to use 8-digit BINs now or in the future, this fix affects your system. Based on your plan to use only 8-digit BINs or a combination of 6-digit and 8-digit BINs, make the necessary configurations.

Note: For a custom configuration, individual issuers must assess the impact on their custom code due to 8-digit BIN changes in the scheme.

  • Previous topic Implementation of 8-digit BIN in Pega Smart Dispute
  • Next topic Current implementation in Pega Smart Dispute

Have a question? Get answers now.

Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us