This API is designed primarily for online store owners who want to perform a deep checking of their credit/debit card transactions, it gives a clear vision of how risky the transactions are. However, anyone can use this API on any platform as he wants and according to his plan limits How this API works? The user will send the credit/debit card (Bank Identification Number) or IIN (Issuer Identification Number) to get the full details as possible. Also, if the IP address is given with the request, it will return the IP address details and check the BIN information against the IP information and gives a risk score for the transaction. It’s beneficial for online merchants to help them take the best decision.
How to use this API? If the user sends the BIN number only, it will return the full details of the BIN. If the user sends the BIN and the IP address of his client, it will return the full details of the BIN and the details if the IP address as well with a risk score. Can I use it for free or test it? Different plans suit everyone, including a free program for small requests per day, but its rate is limited to prevent abuse of the service. Can I use it as “Pay per Request”? Sure, you can use it and pay only when you use it. The credit can’t be expired. How can I integrate it with my project? RapidAPI provides a wide range of integration methods for almost all programming languages. You can use these codes to integrate with your project as you need.
This API is designed primarily for online store owners who want to perform a deep checking of their credit/debit card transactions, it gives a clear vision of how risky the transactions are.
However, anyone can use this API on any platform as he wants and according to his plan limits
How this API works?
The user will send the credit/debit card (Bank Identification Number) or IIN (Issuer Identification Number) to get the full details as possible. Also, if the IP address is given with the request, it will return the IP address details and check the BIN information against the IP information, and gives a risk score for the transaction.
It’s beneficial for online merchants to help them take the best decision.
How to use this API?
If the user sends the BIN number only, it will return the full details of the BIN.
If the user sends the BIN and the IP address of his client, it will return the full details of the BIN and the details of the IP address as well with a risk score.
Can I use it for free or test it?
Different plans suit everyone, including a free trial for small requests, but its rate is limited to prevent abuse of the service.
The BIN Checker API is a powerful endpoint designed to validate and retrieve detailed information about Bank Identification Numbers (BINs), which are the first six digits of a payment card number. This API allows users to instantly determine essential details related to the issuer of the card, such as the bank name, card type (credit, debit, prepaid), card brand (Visa, MasterCard, etc.), and the issuing country. Potential use cases for the BIN Checker API include enhancing security measures during online transactions by verifying card authenticity, optimizing payment processing by categorizing card types for better user experience, and conducting fraud detection through identifying unusual patterns in transaction data.
BIN Checker API - Endpoint Features
| Object | Description |
|---|---|
bin |
[Required] BIN Number from 6 and up to 13 |
{"success":true,"code":200,"BIN":{"valid":true,"number":424242,"length":6,"scheme":"VISA","brand":"VISA","type":"CREDIT","level":"CLASSIC","is_commercial":"false","is_prepaid":"false","currency":"GBP","issuer":{"name":"STRIPE PAYMENTS UK, LTD.","website":"","phone":""},"country":{"name":"UNITED KINGDOM","native":"United Kingdom","flag":"🇬🇧","numeric":"826","capital":"London","currency":"GBP","currency_name":"British pound","currency_symbol":"£","region":"Europe","subregion":"Northern Europe","idd":"44","alpha2":"GB","alpha3":"GBR","language":"English","language_code":"EN"}}}
curl --location --request GET 'https://zylalabs.com/api/7932/bin+ip+insights+api/13075/bin+checker+api?bin=424242455555' --header 'Authorization: Bearer YOUR_API_KEY'
This API will check both the credit card BIN and the user request IP address. It will check the BIN details against the details if the IP and check if the country of the card BIN matches the country of the IP address. This is very helpful to avoid the fraudulent transactions before they even happen.
BIN IP Checker - Endpoint Features
| Object | Description |
|---|---|
bin |
[Required] BIN Number from 6 and up to 13 |
ip |
[Required] IP address details |
{"success":true,"code":200,"BIN":{"valid":true,"number":424242,"length":6,"scheme":"VISA","brand":"VISA","type":"CREDIT","level":"CLASSIC","is_commercial":"false","is_prepaid":"false","currency":"GBP","issuer":{"name":"STRIPE PAYMENTS UK, LTD.","website":"","phone":""},"country":{"name":"UNITED KINGDOM","native":"United Kingdom","flag":"🇬🇧","numeric":"826","capital":"London","currency":"GBP","currency_name":"British pound","currency_symbol":"£","region":"Europe","subregion":"Northern Europe","idd":"44","alpha2":"GB","alpha3":"GBR","language":"English","language_code":"EN"}},"IP":{"IP":"1.1.1.1","ip_version":4,"valid":true,"alpha2":"AU","flag":"🇦🇺","country":"Australia","region":"Queensland","city":"Brisbane","latitude":-27.46754,"longitude":153.02809,"zip_code":"4000","time_zone":"+10:00","current_time":"2026-03-30T23:53:05+10:00","is_proxy":false,"isp":"CloudFlare Inc","asn":"13335","IP_BIN_match":false,"IP_BIN_match_message":"The IP address country doesn't match the country of the BIN"}}
curl --location --request GET 'https://zylalabs.com/api/7932/bin+ip+insights+api/13076/bin+ip+checker?bin=4242424242&ip=1.1.1.1' --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.
If the user sends the BIN number only, it will return the full details of the BIN.
There are different plans suits everyone including a free plan for small amount of requests per day, but it’s rate is limit to prevent abuse of the service.
Zyla provides a wide range of integration methods for almost all programming languages. You can use these codes to integrate with your project as you need.
The GET BIN Checker API returns detailed information about the BIN, including validity, card type, issuer details, and country information. The GET BIN IP Checker combines this with IP address details, providing a risk score and checking if the BIN country matches the IP country.
Key fields include "valid" (indicating if the BIN is valid), "number" (the BIN number), "issuer" (issuer details), "country" (country information), and for the IP Checker, "IP" details and "IP_BIN_match" status.
The response is structured in JSON format, with a top-level "success" field, a "code" for status, and nested objects for "BIN" and "IP" (in the IP Checker), each containing relevant details.
The GET BIN Checker provides BIN validity, card type, issuer, and country details. The GET BIN IP Checker adds IP address validation, geographical data, and a risk assessment based on BIN and IP country matching.
The GET BIN Checker accepts a single parameter: the BIN number. The GET BIN IP Checker accepts both the BIN number and an IP address, allowing for comprehensive risk assessment.
Users can analyze the "valid" field to confirm BIN authenticity, use issuer details for customer support, and leverage the risk score from the IP Checker to make informed transaction decisions.
The data is sourced from financial institutions and payment networks, ensuring comprehensive coverage of BINs and IP address information, which is regularly updated for accuracy.
Typical use cases include fraud prevention for online transactions, verifying customer payment methods, and assessing transaction risk based on geographic consistency between BIN and IP address.
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:
681ms
Service Level:
100%
Response Time:
854ms
Service Level:
100%
Response Time:
1,044ms
Service Level:
100%
Response Time:
2,037ms
Service Level:
100%
Response Time:
520ms
Service Level:
100%
Response Time:
1,232ms
Service Level:
100%
Response Time:
1,197ms
Service Level:
100%
Response Time:
839ms
Service Level:
100%
Response Time:
1,840ms
Service Level:
100%
Response Time:
728ms
Service Level:
100%
Response Time:
1,696ms
Service Level:
100%
Response Time:
609ms
Service Level:
100%
Response Time:
202ms
Service Level:
100%
Response Time:
482ms
Service Level:
100%
Response Time:
257ms
Service Level:
100%
Response Time:
193ms
Service Level:
100%
Response Time:
1,291ms
Service Level:
100%
Response Time:
196ms
Service Level:
100%
Response Time:
315ms
Service Level:
100%
Response Time:
209ms