A customer requests that a BIN in TEST environment be moved into PRODUCTION environment This procedure explains and provides steps to do so.
Originally Published: 2012-06-29
Article Number
Applies To
The FI_BIN load validation allows for the existence of 2 BINS with same numbers in both TEST and PROD environments simultaneously.
Yet there is an over-ride giving precedence to the TEST environment.
The reason is that sometimes customer will want to do a short term test of cards in a particular BIN range so Operations will add the BIN into TEST, leaving the BIN in PROD.
There are two separate Database tables that can contain the same BIN number. So, to move a BIN from Test into Production requires an FI_BIN Loadsheet
1) FI_BIN to Delete the Test BIN entry
2) FI_Bin to add NEW the Production BIN entry
Issue
A customer requests that a BIN in TEST environment be moved into PRODUCTION environment
This procedure explains and provides steps to do so.
Notes
Note Warning if only step 2 is performed, there are now entries in both Tables for These BIN numbers and there could be errors when attempts are made to register cards in these BINS since when this condition exists, Test BIN will take the precedence.
Related Articles
Change hostnames on a deployed production environment in RSA Web Threat Detection Number of Views Setting up on-the-fly SOAP logs in production Number of Views Overview of steps to move Authentication Manager 8.1 production data to VMware ESX 6.0 Number of Views Use Quick Search to View the User Dashboard for a User Number of Views Can't edit workflows on production without using AveksaAdmin Number of Views
Trending Articles
Passwordless Authentication in Windows MFA Agent for Active Directory – Quick Setup Guide RSA Authentication Manager 8.9 Release Notes (January 2026) RSA Authentication Manager Upgrade Process RSA Authentication Manager 8.7 SP2 Setup and Configuration Guide An example of SSO using SAML and ADFS with RSA Identity Management and Governance 6.9.x
Don't see what you're looking for?
