This API is intended to help you spot fraudulent credit card transactions. Start verifying, validating, and checking all information on credit/debit cards just using BIN numbers.
The user will send the credit/debit card (Bank Identification Number) or IIN (Issuer Identification Number) to get the full details.
You have to provide a BIN (Bank Identification Number) - the first 6 digits of a credit/debit card, to receive the full details of this BIN/IIN in JSON format.
You will receive the card's validity, if it's VISA or MASTERCARD, what is the issuing bank, and the card's issuing location.
This API is ideal for those who are wanting to implement a payments gateway on their pages. This API will help those purposes because it will recognize if the card is invalid.
This is also helpful to recognize the issuing bank or entity. So if you have special offers with a specific bank you will be able to authorize the transaction or not.
Besides API call limitations per month:
Be able to validate any credit card based on its BIN number (first 6 digits).
Receive data from the Credit Card, CC Issuer, Card Type, Card Level, Card Brand, Issuer Country, and more.
BIN Checker - Endpoint Features
| Object | Description |
|---|---|
bin |
[Required] First 6 digits of the CC. |
{"status":200,"success":true,"isValid":true,"message":"The BIN number is valid.","data":{"bin_iin":"536817","card_brand":"MASTERCARD","card_type":"CREDIT","card_level":"PLATINUM","issuer_name_bank":"COMENITY CAPITAL BANK","issuer_bank_website":"------","issuer_bank_phone":"43218-2273","iso_country_name":"UNITED STATES","iso_country_code":"US"}}
curl --location --request GET 'https://zylalabs.com/api/7278/accurate+bin+number+analysis+api/11550/bin+checker?bin=444444' --header 'Authorization: Bearer YOUR_API_KEY'
| Header | Description |
|---|---|
Authorization
|
[Required] Should be Bearer access_key. See "Your API Access Key" above when you are subscribed. |
No long-term commitment. Upgrade, downgrade, or cancel anytime. Free Trial includes up to 50 requests.
The API allows developers to validate and verify credit card information using the Bank Identification Number (BIN). By providing the first six digits of a credit card, the API can detect the issuing bank, issuing entity (e.g., VISA, Mastercard), the card's location, and whether it is a valid credit card or not.
The API follows a secure approach by only requiring the Bank Identification Number (BIN), which consists of the first six digits of a credit card. This approach avoids the need to transmit or store sensitive credit card details.
The API response includes comprehensive details about the credit card. This includes information such as the card's validity (whether it is valid or not), the issuing bank's name, the card brand (e.g., VISA), the card type (e.g., credit), the card level (e.g., purchasing with fleet), the currency associated with the card, and the country of issuance. Additionally, the response provides contact information for the issuer, including their name, website, and phone number.
To access the API, you need to make an HTTP POST request to the API endpoint, providing the first six digits of the credit card (BIN) as a parameter. The API will then respond with a JSON object containing the requested information about the credit card, including its validity, issuing bank details, and location information. You can integrate this API into your application or system to leverage its functionality and enhance your credit card processing capabilities.
The POST Check by BIN and GET BIN Checker endpoints return detailed information about a credit card based on its BIN. This includes the card's validity, issuing bank, card brand (e.g., VISA, Mastercard), card type (e.g., credit, debit), and issuing country, among other details.
Key fields in the response include "valid" (indicating card validity), "issuer" (the issuing bank), "card-brand" (e.g., MASTERCARD), "card-type" (e.g., DEBIT), and "iso_country_name" (country of issuance). These fields help identify the card's legitimacy and details.
The response data is structured in JSON format, with a top-level status and success indicator, followed by a "data" object containing specific details about the card. This organization allows for easy parsing and integration into applications.
Both endpoints provide information such as card validity, issuing bank details, card type, card level, card brand, and the country of issuance. This data helps in assessing transaction risk and eligibility for promotions.
The data is sourced from financial institutions and card networks, ensuring a comprehensive and reliable database for BIN information. Regular updates and partnerships with banks help maintain data accuracy.
Users can customize requests by providing different BIN numbers to retrieve specific card details. Each request will return information relevant to the provided BIN, allowing for tailored validation checks.
Typical use cases include validating credit card transactions during online payments, identifying issuing banks for promotional offers, and preventing fraudulent transactions by checking card legitimacy.
Users can utilize the returned data to make informed decisions on transaction approvals, tailor marketing strategies based on issuing banks, and enhance security measures by identifying potentially fraudulent cards.
Please have a look at our Refund Policy: https://zylalabs.com/terms#refund
To obtain your API key, you first need to sign in to your account and subscribe to the API you want to use. Once subscribed, go to your Profile, open the Subscription section, and select the specific API. Your API key will be available there and can be used to authenticate your requests.
You can’t switch APIs during the free trial. If you subscribe to a different API, your trial will end and the new subscription will start as a paid plan.
If you don’t cancel before the 7th day, your free trial will end automatically and your subscription will switch to a paid plan under the same plan you originally subscribed to, meaning you will be charged and gain access to the API calls included in that plan.
The free trial ends when you reach 50 API requests or after 7 days, whichever comes first.
No, the free trial is available only once, so we recommend using it on the API that interests you the most. Most of our APIs offer a free trial, but some may not include this option.
Yes, we offer a 7-day free trial that allows you to make up to 50 API calls at no cost, so you can test our APIs without any commitment.
Zyla API Hub is like a big store for APIs, where you can find thousands of them all in one place. We also offer dedicated support and real-time monitoring of all APIs. Once you sign up, you can pick and choose which APIs you want to use. Just remember, each API needs its own subscription. But if you subscribe to multiple ones, you'll use the same key for all of them, making things easier for you.
Service Level:
100%
Response Time:
281ms
Service Level:
100%
Response Time:
69ms
Service Level:
100%
Response Time:
74ms
Service Level:
100%
Response Time:
728ms
Service Level:
100%
Response Time:
897ms
Service Level:
100%
Response Time:
1,232ms
Service Level:
100%
Response Time:
47ms
Service Level:
100%
Response Time:
839ms
Service Level:
100%
Response Time:
51ms
Service Level:
100%
Response Time:
403ms