BIN/IIN Lookup
Utilize this module to effortlessly retrieve comprehensive information associated with a debit or credit card.
The API provides details such as card type (debit or credit), scheme (Visa, Mastercard, etc.), brand (gold, platinum, etc.), and bank information.
This data is invaluable for various applications, including verifying customer payment details, detecting fraudulent transactions, and delivering personalized services to enhance user experiences.
Overview
The IIN (Issuer Identification Number), also known as the BIN (Bank Identification Number), is the first 6 digits of a debit or credit card number. These unique numbers are used to identify the issuing entity, such as the bank or financial institution that issued the card.
One of the most common and critical use cases of this method is to detect and prevent fraud payments in your app or website. This is an essential task for any business that accepts online payments, as fraud can lead to significant financial losses and reputational damage.
For example, based on of our case studies, if you notice a user from the UK purchasing large amounts of your product, and the card used for payment is issued by a bank located in the US, this could be a red flag. This may indicate that the user is using a stolen or fraudulent card to complete the checkout process. By flagging such transactions for review or rejection, you can prevent fraud and protect your business from financial loss.
Query Parameters
The BIN/IIN of the card (min: 6 digits).
Sample value: 456789, 456789XXXXXX1234, or 4567891234567890.
The format command is used to get a response in a specific format.
Expected values: JSON, XML, CSV, or Newline
For more information please refer to Response Format.
The mode command is used to in the development stage to simulate the integration process before releasing it to the production environment.
Expected values: live, or test.
For more information please refer to Development Environment.
The userID command can be used to identify requests sent by specific users to monitor in the Events Page.
Expected values: email address, phone number, user id, name, etc.
For more information please refer to User Identifier.
The callback command can help you make the response as a JSONP format.
Expected values: any name that can be used as a function name in Javascript, e.g: myFunctionName.
For more information please refer to JSONP Callback.
Response properties
Response status (success, or error).
Time taken to process the data (in milliseconds).
Was this page helpful?