The BIN IP API offers a comprehensive solution for validating and analyzing credit cards and IP addresses in real time. It allows users to verify the authenticity of a BIN (Bank Identification Number) and obtain detailed information about the card issuer, including the bank name, card type, level, brand, whether it is commercial or prepaid, and the associated currency. In addition, the API provides complete data on the issuer's country, such as name, flag, numerical code, capital, currency, currency symbol, region, subregion, ISO codes, and official language.
On the other hand, the API performs a comprehensive analysis of the IP address, indicating its validity, version (IPv4 or IPv6), country, region, city, geographic coordinates, zip code, time zone, and current time. It also detects whether the IP is a proxy, providing details such as proxy type, ISP, ASN, domain, last seen, provider, and possible security risks. The match between the BIN location and the IP is automatically verified, ensuring that transactions are geographically consistent and helping to reduce fraud.
With fast, structured responses in JSON format, the API provides reliable access to detailed information, helping users efficiently integrate card validation and IP verification into their systems, ensuring security and accuracy in every transaction.
Verifies BINs and IP addresses, displaying geographic matches, card type and brand, issuing bank, city, country, ISP, and time zone.
BIN IP - Endpoint Features
| Object | Description |
|---|---|
bin |
[Required] Enter a BIN |
ip |
[Required] Enter an IP Address |
{"matched":true,"matchedResult":"BIN and IP address country is matched","bin_info":{"scheme":"mastercard","type":"debit","brand":"MASTERCARD","bank":{"name":"HUNTINGTON NATIONAL BANK"},"country":{"alpha2":"US","name":"United States"}},"ip_info":{"ip":"198.153.14.23","country":"US","city":"Saint Paul","continent":"NA","latitude":44.9354,"longitude":-93.1694,"zip":"55105","isp":"HealthPartners","proxy":false,"isHosting":false,"timeZone":"America/Chicago"}}
curl --location --request GET 'https://zylalabs.com/api/9979/bin+ip+api/18961/bin+ip?bin=517546&ip=198.153.14.23' --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 GET BIN IP endpoint returns detailed information about a BIN (Bank Identification Number) and an IP address. This includes card issuer details (bank name, card type, brand), geographic data (country, city, coordinates), and IP specifics (ISP, proxy status, time zone).
Key fields in the response include "bank_name," "card_type," "country," "city," "isp," "proxy_type," "latitude," "longitude," and "time_zone." These fields provide essential information for validating transactions and assessing geographic consistency.
The response data is structured in JSON format, organized into distinct sections for BIN and IP information. Each section contains relevant fields, making it easy to parse and utilize the data programmatically.
The endpoint provides information on BIN validity, card issuer details, geographic location of the IP, ISP information, proxy detection, and time zone data. This comprehensive data aids in fraud prevention and transaction validation.
The endpoint accepts parameters such as "bin" for the Bank Identification Number and "ip" for the IP address. Users can customize requests by providing valid BINs and IPs to retrieve specific data.
Data accuracy is maintained through regular updates from reliable sources, including financial institutions and IP registries. Quality checks are implemented to ensure the information is current and reliable for users.
Typical use cases include fraud detection, transaction validation, geographic analysis for compliance, and enhancing user experience by tailoring services based on location and card type.
Users can leverage the returned data to verify transactions, assess risk based on geographic consistency, and enhance security measures by identifying potential proxies or fraudulent activities.
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.
Please have a look at our Refund Policy: https://zylalabs.com/terms#refund
Service Level:
100%
Response Time:
1,044ms
Service Level:
100%
Response Time:
520ms
Service Level:
100%
Response Time:
772ms
Service Level:
100%
Response Time:
728ms
Service Level:
100%
Response Time:
403ms
Service Level:
100%
Response Time:
1,197ms
Service Level:
100%
Response Time:
1,958ms
Service Level:
100%
Response Time:
417ms
Service Level:
100%
Response Time:
47ms
Service Level:
100%
Response Time:
311ms
Service Level:
89%
Response Time:
0ms
Service Level:
100%
Response Time:
289ms
Service Level:
100%
Response Time:
663ms
Service Level:
100%
Response Time:
1,104ms
Service Level:
100%
Response Time:
123ms
Service Level:
100%
Response Time:
502ms
Service Level:
100%
Response Time:
105ms
Service Level:
100%
Response Time:
413ms
Service Level:
100%
Response Time:
0ms
Service Level:
100%
Response Time:
1,337ms