Card BIN Lookup API

This API allows you to verify the authenticity of credit cards in real time during transactions on your website.

The Card BIN Lookup API is a powerful solution designed to improve the security and reliability of online transactions by delivering accurate, real-time information about credit cards based on their Bank Identification Number (BIN). As a critical component in e-commerce and financial services, this API helps mitigate fraud risks and safeguard the integrity of digital transactions.

At its core, the Card BIN Lookup API uses the first six digits of a credit card—the BIN—to retrieve key details about the issuing institution. This includes information such as the bank name, country of origin, card type, and more. By accessing this data, businesses can make informed decisions about the validity of a transaction, strengthening defenses against potential fraud.

API Documentation

Endpoints


Be able to validate any credit card based on its BIN number (first 6 digits).

Receive data from the Credit Card, CC Issuer, Card Type, Card Level, Card Brand, Issuer Country, and more. 



                                                                            
GET https://zylalabs.com/api/6616/card+bin+lookup+api/9712/bin+checker
                                                                            
                                                                        

BIN Checker - Endpoint Features

Object Description
bin [Required]
Test Endpoint

API EXAMPLE RESPONSE

       
                                                                                                        
                                                                                                                                                                                                                            {"status":200,"success":true,"isValid":true,"message":"The BIN number is valid.","data":{"bin_iin":"373723","card_brand":"AMERICAN EXPRESS","card_type":"CREDIT","card_level":"OPTIMA","issuer_name_bank":"AMERICAN EXPRESS US CONSUMER","issuer_bank_website":"------","issuer_bank_phone":"------","iso_country_name":"UNITED STATES","iso_country_code":"US"}}
                                                                                                                                                                                                                    
                                                                                                    

BIN Checker - CODE SNIPPETS


curl --location --request GET 'https://zylalabs.com/api/6616/card+bin+lookup+api/9712/bin+checker?bin=373723' --header 'Authorization: Bearer YOUR_API_KEY' 


    

API Access Key & Authentication

After signing up, every developer is assigned a personal API access key, a unique combination of letters and digits provided to access to our API endpoint. To authenticate with the Card BIN Lookup API REST API, simply include your bearer token in the Authorization header.
Headers
Header Description
Authorization [Required] Should be Bearer access_key. See "Your API Access Key" above when you are subscribed.

Simple Transparent Pricing

No long-term commitment. Upgrade, downgrade, or cancel anytime. Free Trial includes up to 50 requests.

πŸš€ Enterprise

Starts at
$ 10,000/Year


  • Custom Volume
  • Custom Rate Limit
  • Specialized Customer Support
  • Real-Time API Monitoring

Customer favorite features

  • βœ”οΈŽ Only Pay for Successful Requests
  • βœ”οΈŽ Free 7-Day Trial
  • βœ”οΈŽ Multi-Language Support
  • βœ”οΈŽ One API Key, All APIs.
  • βœ”οΈŽ Intuitive Dashboard
  • βœ”οΈŽ Comprehensive Error Handling
  • βœ”οΈŽ Developer-Friendly Docs
  • βœ”οΈŽ Postman Integration
  • βœ”οΈŽ Secure HTTPS Connections
  • βœ”οΈŽ Reliable Uptime

Card BIN Lookup API FAQs

The API allows developers to validate and verify credit card information using the bank identification number (BIN). By providing the first six digits of a credit card, you can verify whether it is a valid credit card or not.

The API follows a secure approach by only requiring the Bank Identification Number (BIN), which consists of the first six digits of a credit card. This approach avoids the need to transmit or store sensitive credit card details.

The API response includes detailed information about the credit card. This includes information such as the validity of the card (whether it is valid or not), the level of the card (e.g., fleet purchase), the currency associated with the card, and the country of issuance.

To access the API, you need to make an HTTP POST request to the API endpoint, providing the first six digits of the credit card (BIN) as a parameter. The API will then respond with a JSON object containing the requested information about the credit card, including its validity, issuing bank details, and location information. You can integrate this API into your application or system to leverage its functionality and enhance your credit card processing capabilities.

The BIN Checker endpoint returns a JSON object containing details about the credit card associated with the provided BIN. This includes the card's validity, brand, type, level, issuing bank name, country of issuance, and contact information for the issuer.

Key fields in the response data include `isValid` (indicating card validity), `card_brand` (e.g., MASTERCARD), `card_type` (e.g., DEBIT), `issuer_name_bank`, `iso_country_name`, and `iso_country_code`. These fields provide essential information for transaction validation.

The response data is structured in a JSON format. It includes a `status` code, a `success` boolean, a `message`, and a `data` object containing detailed information about the credit card, making it easy to parse and utilize in applications.

The BIN Checker endpoint provides information such as the card's validity, brand, type, level, issuing bank details, and the country of issuance. This data helps in assessing the legitimacy of credit card transactions.

The primary parameter for the BIN Checker endpoint is the BIN itself, which consists of the first six digits of a credit card. Users must ensure that the BIN is numeric and valid to receive accurate results.

Data accuracy is maintained through the use of comprehensive and regularly updated databases that track BIN information. The API cross-references the provided BIN with these databases to ensure reliable results.

Typical use cases include fraud prevention during online transactions, validating credit cards in payment gateways, ensuring authenticity for subscription services, and securing e-commerce transactions by verifying card details at the point of purchase.

Users can utilize the returned data to make informed decisions about credit card transactions. For example, if `isValid` is false, they can flag the transaction for further review or decline it, enhancing security and reducing fraud risk.

General FAQs

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.


Related APIs