{"digits_count":16,"brand":"visa","luhn_valid":true,"length_valid_for_brand":true,"valid":true,"masked":"411111******1111","note":"Validacao por algoritmo de Luhn e bandeira pelo prefixo. Nao consulta banco emissor. Nada e armazenado."}
curl --location --request GET 'https://zylalabs.com/api/13157/credit+card+number+validator+api/26703/validate+card+number' --header 'Authorization: Bearer YOUR_API_KEY'
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 Credit Card Number Validator API simply include your bearer token in the Authorization header.
| 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.
(Save 2 months with annual billing 🎉)
Catch invalid card numbers at the form, before a costly gateway round trip. One call verifies the checksum, detects the brand by prefix and checks the number length for that brand.
Useful for checkout form validation in online stores and subscription billing, pre-validation before tokenization, cleaning card data in customer systems, and showing the right brand logo at checkout. The verdict means the number is well formed; it does not query the issuing bank.
The Validate Card Number endpoint returns data including the validity of the card number, detected brand, digit count, length validity for the brand, and a masked version of the card number.
Key fields in the response include "valid" (indicating overall validity), "brand" (the detected card brand), "digits_count" (total digits), "length_valid_for_brand" (length check result), "luhn_valid" (checksum validation), and "masked" (masked card number).
The response data is structured in JSON format, with key-value pairs for each field. For example, a typical response might look like: {"valid": true, "brand": "visa", "masked": "411111******1111"}.
The endpoint provides information on card validity, brand detection, checksum verification, and length validation specific to the card brand, ensuring comprehensive pre-validation before processing.
Users can customize their requests by providing different card numbers to the Validate Card Number endpoint. Each request will return validation results specific to the submitted card number.
Typical use cases include validating card numbers during online checkouts, pre-validating cards before tokenization, cleaning card data in customer systems, and displaying the correct brand logo at checkout.
Data accuracy is maintained through the use of the Luhn algorithm for checksum verification and brand detection based on established prefix rules, ensuring reliable validation without querying issuing banks.
Standard data patterns include a boolean "valid" field indicating overall validity, a "brand" field with recognized card brands, and a "masked" field showing the card number with sensitive digits obscured.
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