Introduction


Bank Identification Number (BIN) is s set of numbers that identify among many other things the banking/final institution that issues the card. BINs can be found on various payment cards, including credit card, charge cards, and debit cards etc. The BIN helps merchants to evaluate and assess their payment card transactions.


Objectives


The objective is to demonstrate through screen representation the BIN Management process via the iVeri Administration Website. 

The content will cover the following objectives:

At an Acquirer level – Per Gateway or Across Acquirers if on Hosted:

Any BIN management updates made would apply across the merchant base:

  • How to create a new BIN 
  • How to amend an existing BIN

At a Merchant level:

Any BIN management updates made would apply to the specific merchant:

  • BIN management related to a merchant
  • A possible scenario when a BIN type and Description may be required to be amended for a merchant.

Target Audience:
This guide is intended for the support team tasked with generating new and modifying existing BINs upon request from Acquirers.

Pre-requisites:
Requesting a new BIN:

  • Select personnel are allowed to request and authorize the creation of a new BIN. For e.g. At Nedbank, Integrator Ops is allowed to request a creation of a new BIN.


Creating a new BIN


Below is a step-by-step illustration of how to create a new BIN. This request will come from authorized personnel ONLY at the Acquiring bank for the creation of a new BIN.


Navigation Path:

From the main menu select:
Systems > iVeriDB BIN > Local BIN

1. Select the ‘Create New’ tab to initiate the process of creating a new BIN.



The following General information’s tab will appear.

2. Here the user will complete the information relating to the BIN as received from the Acquirer.

BIN – BIN number will be provided by the Acquirer. This applies to the creation of a new BIN as well as amending the parameters of an existing BIN.
Card Number Length – We require confirmation from the Acquirer regarding the Card Number length. Specifically, we need confirmation of both the minimum (referencing the first tab) and the maximum (referencing the second tab) Card number lengths.


Card Association – Refers to the brand network that owns the card. While important for reporting and monitoring purposes, omitting this information will not affect the processing of a transaction.



Card Type – Card types and BIN (Bank Identification Number) provide essential information about the type of card being used. 
Card Types are essential to capture, considering the rules regarding transaction types will apply. For instance, a ‘Debit SMS’ card can do Sale but not Refunds.
While important for reporting and monitoring purposes, omitting this information will not affect the processing of a transaction.



Card issuer – Capture the Card issuer details from the dropdown. In certain instances, this will not be available as the Acquirer is not the actual issuer of the card.
The details of the card issuer may not affect the actual processing of a transaction. However, they play a crucial role in scenarios such as handling inquiries or determining appropriate fees for each transaction. 
For instance, knowing whether the card issuer is local or international helps merchants decide on the fees to charge.




Having the card issuer details can also assist in determining declined transactions from a specific BIN issued by a Bank.
Jurisdiction – This is very important to understand if the BIN being loaded is issued in South Africa or in a different country. The country would need to be stated from the drop down.
In certain instances, the jurisdiction may play an important role in routing a transaction for an Acquirer.
If the country is not available  from the drop down, we have
IsManagedBySystem – This would need to be ticked.
PinBehaviour – This setting typically remains on the default parameter, which is 'Derive'. 'Derive' utilizes the data based on the configuration set for the card. 
For example, it may prompt for a PIN or not prompt for a PIN, depending on the card's setup when used on a device.



If support receives a specific request to modify the PIN behavior from the default setting, they will make the necessary adjustments based on the available parameters in the dropdown menu:

Clicking ‘Ok’ to capture the information related to a BIN, please ensure that all the information has been captured correctly.


Amending / Updating an existing BIN


Now that we have a grasp of the process and the parameters required for a new BIN request, let's delve into the process of amending or updating an existing BIN.

Navigation Path:

From the main menu select:
Systems > iVeriDB BIN > Local BIN

1. Capture the BIN number in the search bar provider.  Run the search.



The information related to the BIN will populate.

2. To amend the BIN, select the ‘Edit’ tab.
 



3. The general information tab will populate with information relating to the BIN.

Since this is an existing BIN you are amending or updating, the BIN number cannot be edited, which is why it appears greyed out.

Update and amend the applicable parameters based on the requested amendments or updates.

The most common parameters that are requested to be amended are ‘Card Number Length’ and ‘Card Type’.



Note: It's crucial to remember that for requests concerning the 'Card Number Length', support must verify that both the minimum and maximum lengths have been provided by the requester.





BIN Management at a Merchant level


Merchant BIN management is crucial. The BIN configuration determines what actions a merchant is permitted or restricted to perform.  A Merchant may request certain restrictions within a BIN
The below scenario will demonstrate the importance of the BIN Management process that may be amended at a Merchant level:


Meet John. John is a merchant who has expanded his business over the past 5 years. He has international clients but has decided to shift his business focus from international to local, highlighting economic downturn and the fees attached to international cards as his main reasons. John no longer wishes to do business internationally. In line with his cost cutting initiatives, he has also decided that he will no longer accept credit cards.
John proceeds lodges a query with support to assist with issue via his Acquiring bank.


Support receives the request from the Acquiring Bank on behalf of the merchant. Based on the investigation done by support the Jurisdiction for this BIN is setup for International. We will now show the steps the Support team will take to amend this at a Merchant Level.

BIN Management – Update Jurisdiction

Navigation Path:

From the main menu select:
Applications > Update > BIN Management.

1. Capture the Merchant Profile ID and click ‘Search’.



2. Select the applicable ‘Live Application ID’.



The user will then be redirected to the BIN Management Parameters.
Here the user can update / amend the following information:

  • Jurisdiction
  • Card Association
  • Card Type 
  • Issuer


Please note the information populated here defaulted values.

3. Under the ‘Type’ parameter, navigate to Jurisdiction.



Here the user will view the defaulted Jurisdiction descriptions that are allowed for this merchant.

4. Untick the box for ‘International’ as illustrated.



Lastly, ‘Update parameters’ to ensure updates are saved.


BIN Management – Update Card Type


2. Select the applicable ‘Live Application ID’.



Please note the information populated here defaulted values.

3. Under the ‘Type’ parameter, scroll down to the ‘Card Type’ parameter.


Here the user will view the defaulted Card Types that are allowed for this merchant.

4. Locate the ‘Credit Card’ value and untick the box.


Lastly, ‘Update parameters’ to ensure updates are saved.