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.
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":"444444","card_brand":"VISA","card_type":"CREDIT","card_level":"GOLD","issuer_name_bank":"CREDIT AGRICOLE BANK POLSKA, S.A.","issuer_bank_website":"------","issuer_bank_phone":"022-2133067","iso_country_name":"POLAND","iso_country_code":"PL"}}
curl --location --request GET 'https://zylalabs.com/api/40/credit+card+validator+-+bin+checker+api/1885/bin+checker?bin=444444' --header 'Authorization: Bearer YOUR_API_KEY'
After signing up, every developer is assigned a personal API access key, a unique combination of letters and digits provided to access to our API endpoint. To authenticate with the Credit Card Validator - BIN Checker API REST API, simply include your bearer token in the Authorization header.
Header | Description |
---|---|
Authorization
|
[Required] Should be Bearer access_key . See "Your API Access Key" above when you are subscribed. |
No long term commitments. One click upgrade/downgrade or cancellation. No questions asked.
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.
Zyla API Hub is, in other words, an API MarketPlace. An all-in-one solution for your developing needs. You will be accessing our extended list of APIs with only your user. Also, you won't need to worry about storing API keys, only one API key for all our products is needed.
Prices are listed in USD. We accept all major debit and credit cards. Our payment system uses the latest security technology and is powered by Stripe, one of the world’s most reliable payment companies. If you have any trouble with paying by card, just contact us at [email protected]
Sometimes depending on the bank's fraud protection settings, a bank will decline the validation charge we make when we attempt to be sure a card is valid. We recommend first contacting your bank to see if they are blocking our charges. If more help is needed, please contact [email protected] and our team will investigate further
Prices are based on a recurring monthly subscription depending on the plan selected — plus overage fees applied when a developer exceeds a plan’s quota limits. In this example, you'll see the base plan amount as well as a quota limit of API requests. Be sure to notice the overage fee because you will be charged for each additional request.
Zyla API Hub works on a recurring monthly subscription system. Your billing cycle will start the day you purchase one of the paid plans, and it will renew the same day of the next month. So be aware to cancel your subscription beforehand if you want to avoid future charges.
Just go to the pricing page of that API and select the plan that you want to upgrade to. You will only be charged the full amount of that plan, but you will be enjoying the features that the plan offers right away.
Yes, absolutely. If you want to cancel your plan, simply go to your account and cancel on the Billing page. Upgrades, downgrades, and cancellations are immediate.
You can contact us through our chat channel to receive immediate assistance. We are always online from 9 am to 6 pm (GMT+1). If you reach us after that time, we will be in contact when we are back. Also you can contact us via email to [email protected]
Service Level:
100%
Response Time:
2,086ms
Service Level:
100%
Response Time:
472ms
Service Level:
100%
Response Time:
411ms
Service Level:
100%
Response Time:
816ms
Service Level:
100%
Response Time:
185ms
Service Level:
100%
Response Time:
2,401ms