The Retrieve BIN IP Details 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.
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/10000/retrieve+bin+ip+details+api/19001/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 the BIN and IP address, including card type, brand, issuing bank, geographic location (city, country), ISP details, and time zone. It also verifies the geographic match between the BIN and IP.
Key fields in the response include card type, brand, issuing bank name, country, city, ISP, geographic coordinates, time zone, and proxy details. Each field provides essential information for validating transactions and assessing risk.
The response data is structured in JSON format, organized into key-value pairs. Each section corresponds to specific data categories, such as BIN details and IP information, making it easy to parse and utilize in applications.
The endpoint provides information on BIN authenticity, card issuer details, IP address validity, geographic location, ISP information, and proxy detection. This comprehensive data aids in transaction validation and fraud prevention.
The GET BIN IP endpoint accepts parameters such as BIN number and IP address. Users can customize requests by providing specific BINs or IPs to retrieve targeted information relevant to their needs.
Data accuracy is maintained through regular updates from reliable sources, including financial institutions and IP registries. Quality checks are implemented to ensure the integrity and reliability of the information provided.
Typical use cases include fraud detection in e-commerce transactions, validating payment methods, enhancing user verification processes, and ensuring compliance with regional regulations by analyzing geographic data.
Users can leverage the returned data to assess transaction legitimacy, identify potential fraud risks, and enhance user experience by providing localized services based on geographic information from the API response.
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:
228ms
Service Level:
100%
Response Time:
213ms
Service Level:
100%
Response Time:
182ms
Service Level:
100%
Response Time:
39ms
Service Level:
100%
Response Time:
561ms
Service Level:
100%
Response Time:
75ms
Service Level:
100%
Response Time:
1,692ms
Service Level:
100%
Response Time:
1,971ms
Service Level:
100%
Response Time:
293ms
Service Level:
100%
Response Time:
2,084ms
Service Level:
100%
Response Time:
20,003ms
Service Level:
100%
Response Time:
20,003ms
Service Level:
100%
Response Time:
3,560ms
Service Level:
100%
Response Time:
20,002ms
Service Level:
100%
Response Time:
20,002ms
Service Level:
100%
Response Time:
121ms
Service Level:
100%
Response Time:
427ms
Service Level:
100%
Response Time:
132ms
Service Level:
100%
Response Time:
233ms
Service Level:
100%
Response Time:
195ms