API Overview
Our API, designed primarily for online merchants, provides comprehensive insights into credit and debit card transactions, empowering businesses to assess transaction risks with confidence. Its versatility, however, extends beyond merchants, making it useful for anyone who needs to analyze transaction data across various platforms, all within the limits of their chosen plan.
How it Works
Users submit the Bank Identification Number (BIN) or Issuer Identification Number (IIN) associated with a credit or debit card to access detailed transaction data. By also including the IP address, the API can cross-reference BIN data with IP information, delivering a risk score that helps evaluate the security of each transaction. This feature is particularly beneficial for online merchants, enabling them to make informed decisions and reduce fraud risk.
Getting Started
Submitting just the BIN number returns extensive details about the BIN. Adding the client’s IP address to the request provides additional insights, including IP details and a risk score, which further enhances the assessment of each transaction.
{"bin":"543465","brand":"MASTERCARD","type":"DEBIT","category":"ENHANCED","issuer":"FIFTH THIRD BANK","issuer_phone":"+18666715353","issuer_url":"https:\/\/www.53.com","iso2":"US","iso3":"USA","country":"UNITED STATES"}
curl --location --request GET 'https://zylalabs.com/api/10105/bin+card+api/19299/bin+card+information?bin=543465' --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 Bin Card API returns detailed information about a card issuer based on the first six digits (BIN) of a credit or debit card. This includes the card brand, type, category, issuer name, issuer phone number, issuer URL, and country information.
Key fields in the response include "bin" (the BIN number), "brand" (card brand), "type" (card type), "category" (category of the card), "issuer" (issuer name), "issuer_phone" (contact number), "issuer_url" (website), and "country" (country of the issuer).
The response data is structured in JSON format, with key-value pairs representing various attributes of the card issuer. For example, a typical response might look like: {"bin":"543465","brand":"MASTERCARD","issuer":"FIFTH THIRD BANK",...}.
The API provides information such as the card brand, type, issuer details, and geographical data. It also offers a risk score when an IP address is included, enhancing transaction security assessments.
The primary parameter accepted by the API is the BIN number (first six digits of the card). Optionally, users can include an IP address to receive additional insights and a risk score related to the transaction.
Data accuracy is maintained through regular updates from reliable financial institutions and card networks. The API employs quality checks to ensure that the information provided is current and reliable.
Typical use cases include fraud detection for online transactions, risk assessment for merchants, and data analysis for financial institutions. It helps businesses make informed decisions based on card issuer information.
Users can leverage the returned data to assess transaction risks, verify card issuer details, and enhance security measures. For example, knowing the issuer can help identify potential fraud patterns based on geographic or issuer-specific trends.
To obtain your API key, first sign in to your account and navigate to the API you want to use. From the API's Pricing section, choose a plan and complete the subscription process. Once subscribed, return to the API page and you will see your API Access Key displayed at the top of the documentation page. You can use this key 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.
The free trial lasts for 7 days and allows you to make up to 50 API requests.
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. If the API offers a free trial, you will see a "Free 7-Day Trial" option in its Pricing section. The trial lasts for 7 days and allows up to 50 API requests, enabling you to evaluate the API before subscribing to a paid plan.
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.
You can monitor your API usage through the response headers included with every request:
x-zyla-api-calls-monthly-used: Shows the total number of API requests you have used during the current billing period.
x-zyla-api-calls-monthly-remaining: Shows the number of API requests you have remaining for the current billing period.
Yes, you can cancel your subscription at any time. Simply go to the Pricing section of the API you're subscribed to and click the "Unsubscribe" button.
Please note that upgrades, downgrades, and cancellations take effect immediately. Once your subscription is canceled, access to the service will end immediately, regardless of any remaining API calls in your quota.
Please have a look at our Refund Policy: https://zylalabs.com/terms#refund
Service Level:
100%
Response Time:
2,652ms
Service Level:
100%
Response Time:
787ms
Service Level:
100%
Response Time:
517ms
Service Level:
100%
Response Time:
105ms
Service Level:
100%
Response Time:
109ms
Service Level:
100%
Response Time:
75ms
Service Level:
100%
Response Time:
887ms
Service Level:
100%
Response Time:
460ms
Service Level:
100%
Response Time:
285ms
Service Level:
100%
Response Time:
419ms
Service Level:
100%
Response Time:
282ms
Service Level:
100%
Response Time:
354ms
Service Level:
100%
Response Time:
241ms
Service Level:
100%
Response Time:
227ms
Service Level:
100%
Response Time:
30ms
Service Level:
100%
Response Time:
13ms
Service Level:
100%
Response Time:
412ms
Service Level:
100%
Response Time:
485ms
Service Level:
100%
Response Time:
929ms
Service Level:
100%
Response Time:
840ms