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.
Retunrs the information about the card issuer by it's first 6 digits.
Bin card information - Endpoint Features
Object | Description |
---|---|
bin |
[Required] |
{"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.
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.
Prices are listed in USD (United States Dollar), EUR (Euro), CAD (Canadian Dollar), AUD (Australian Dollar), and GBP (British Pound). 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 paying by card, just contact us at [email protected]
Additionally, if you already have an active subscription in any of these currencies (USD, EUR, CAD, AUD, GBP), that currency will remain for subsequent subscriptions. You can change the currency at any time as long as you don't have any active subscriptions.
The local currency shown on the pricing page is based on the country of your IP address and is provided for reference only. The actual prices are in USD (United States Dollar). When you make a payment, the charge will appear on your card statement in USD, even if you see the equivalent amount in your local currency on our website. This means you cannot pay directly with your local currency.
Occasionally, a bank may decline the charge due to its fraud protection settings. We suggest reaching out to your bank initially to check if they are blocking our charges. Also, you can access the Billing Portal and change the card associated to make the payment. If these does not work and you need further assistance, please contact our team at [email protected]
Prices are determined by a recurring monthly or yearly subscription, depending on the chosen plan.
API calls are deducted from your plan based on successful requests. Each plan comes with a specific number of calls that you can make per month. Only successful calls, indicated by a Status 200 response, will be counted against your total. This ensures that failed or incomplete requests do not impact your monthly quota.
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.
To upgrade your current subscription plan, simply go to the pricing page of the API and select the plan you want to upgrade to. The upgrade will be instant, allowing you to immediately enjoy the features of the new plan. Please note that any remaining calls from your previous plan will not be carried over to the new plan, so be aware of this when upgrading. You will be charged the full amount of the new plan.
To check how many API calls you have left for the current month, refer to the 'X-Zyla-API-Calls-Monthly-Remaining' field in the response header. For example, if your plan allows 1,000 requests per month and you've used 100, this field in the response header will indicate 900 remaining calls.
To see the maximum number of API requests your plan allows, check the 'X-Zyla-RateLimit-Limit' response header. For instance, if your plan includes 1,000 requests per month, this header will display 1,000.
The 'X-Zyla-RateLimit-Reset' header shows the number of seconds until your rate limit resets. This tells you when your request count will start fresh. For example, if it displays 3,600, it means 3,600 seconds are left until the limit resets.
Yes, you can cancel your plan anytime by going to your account and selecting the cancellation option on the Billing page. Please note that upgrades, downgrades, and cancellations take effect immediately. Additionally, upon cancellation, you will no longer have access to the service, even if you have remaining calls left in your quota.
You can contact us through our chat channel to receive immediate assistance. We are always online from 8 am to 5 pm (EST). If you reach us after that time, we will get back to you as soon as possible. Additionally, you can contact us via email at [email protected]
To give you the opportunity to experience our APIs without any commitment, we offer a 7-day free trial that allows you to make up to 50 API calls at no cost. This trial can be used only once, so we recommend applying it to the API that interests you the most. While most of our APIs offer a free trial, some may not. The trial concludes after 7 days or once you've made 50 requests, whichever occurs first. If you reach the 50 request limit during the trial, you will need to "Start Your Paid Plan" to continue making requests. You can find the "Start Your Paid Plan" button in your profile under Subscription -> Choose the API you are subscribed to -> Pricing tab. Alternatively, if you don't cancel your subscription before the 7th day, your free trial will end, and your plan will automatically be billed, granting you access to all the API calls specified in your plan. Please keep this in mind to avoid unwanted charges.
After 7 days, you will be charged the full amount for the plan you were subscribed to during the trial. Therefore, it's important to cancel before the trial period ends. Refund requests for forgetting to cancel on time are not accepted.
When you subscribe to an API free trial, you can make up to 50 API calls. If you wish to make additional API calls beyond this limit, the API will prompt you to perform an "Start Your Paid Plan." You can find the "Start Your Paid Plan" button in your profile under Subscription -> Choose the API you are subscribed to -> Pricing tab.
Payout Orders are processed between the 20th and the 30th of each month. If you submit your request before the 20th, your payment will be processed within this timeframe.
Service Level:
100%
Response Time:
91ms
Service Level:
100%
Response Time:
183ms
Service Level:
100%
Response Time:
240ms
Service Level:
100%
Response Time:
154ms
Service Level:
100%
Response Time:
124ms
Service Level:
100%
Response Time:
123ms
Service Level:
100%
Response Time:
57ms
Service Level:
100%
Response Time:
218ms
Service Level:
100%
Response Time:
1,583ms
Service Level:
100%
Response Time:
165ms
Service Level:
100%
Response Time:
2,277ms
Service Level:
100%
Response Time:
2,277ms
Service Level:
100%
Response Time:
2,277ms
Service Level:
100%
Response Time:
2,277ms
Service Level:
100%
Response Time:
2,292ms
Service Level:
100%
Response Time:
0ms
Service Level:
100%
Response Time:
1,930ms
Service Level:
100%
Response Time:
5,027ms
Service Level:
100%
Response Time:
5,027ms
Service Level:
100%
Response Time:
5,027ms