> ## Documentation Index > Fetch the complete documentation index at: https://docs.greip.io/llms.txt > Use this file to discover all available pages before exploring further. # 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. export const MCPCallout = () => { return
Want to skip the docs? Use the{" "} MCP Server
; }; export const Availability = ({plan, color}) => { const colorMap = { green: "text-green-700 dark:text-green-400", blue: "text-blue-700 dark:text-blue-400", purple: "text-purple-700 dark:text-purple-400" }; return
Endpoint availability:{" "} {plan} Learn more
; }; ### 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](/options/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](/options/development-environment). The userID command can be used to identify requests sent by specific users to monitor in the [Events Page](/dashboard-guides/monitoring-capabilities/real-time-threat-monitoring). Expected values: email address, phone number, user id, name, etc. For more information please refer to [User Identifier](/options/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](/options/jsonp-callback). ```json Success theme={null} { "data": { "reason": "", "isValid": true, "blacklisted": false, "bin": "456789", "info": { "scheme": { "name": "Visa", "coName": "Mada", "isLuha": true, "isPrepaid": false, "isCommercial": false, "type": "debit", "brand": "Traditional", "currency": "SAR" }, "detected_digits": "4", "syntax": { "gaps": [4, 8, 12], "lengths": [16, 18, 19], "code": { "name": "CVV", "size": 3 } }, "bank": { "id": "588847", "identifier": "80", "name": "AL RAJHI BANKING AND INVESTMENT CORP.", "city": "Riyadh", "url": "https://www.alrajhibank.com.sa", "phone": "+96611211600", "logo": "https://greip.io/img/banks/al-rajhi.jpg", "latitude": "25", "longitude": "45" }, "country": { "alpha2": "SA", "name": "Saudi Arabia", "code": "966", "numeric": "682", "emoji": "🇸🇦", "continent": "Asia", "languageCode": "ar", "languageNative": "العربية" } }, "custom_rules_applied": { "total": 0, "rules": [] } }, "status": "success", "executionTime": 2 } ``` ```json Error theme={null} { "status": "error", "code": 101, "type": "invalid_key", "description": "The API Key is missing or invalid." } ``` ### Response properties Reason for the validation result. Validation result (`true` or `false`). Indicates if the BIN is blacklisted due to applying [custom rules](/knowledge-base/custom-rules/overview) or were found in one of your blacklists. The BIN/IIN of the card you passed in the request. Card scheme name. Card company name. Is the card issued by Luha? Is the card prepaid? Is the card commercial? Card type (`debit`, or `credit`). Card brand (`Traditional`, `Gold`, `Platinum`, etc.). Card currency. The digits used to detect the scheme details. The gaps variations of the card number. The possible lengths of the card number. The name of the code (e.g: CVV). The number of digits in the code. Bank ID. Bank identifier. The official bank name. The city where the bank's headquarters are located. Bank URL of the official website. Bank phone number for contact. Bank logo URL (image). Bank latitude coordinates of the country where the bank is located. Bank longitude coordinates of the country where the bank is located. Country code (in ISO 3166-1 alpha-2 format). The Country name. Country dialing code. Country numeric code. Country flag emoji. Continent where the country is located. Country language code (in ISO 639-1 format). Country native language name. The custom rules applied to this request, [learn more](/knowledge-base/custom-rules/overview). The total number of custom rules applied to this request. The custom rules applied to this request, [learn more](/knowledge-base/custom-rules/overview). The rule ID as shown in the dashboard (e.g: `CR104`). The rule title you set when creating the rule. Response status (`success`, or `error`). Time taken to process the data (in milliseconds).