Docs/APIs/Card Validator

Card Validator

Validate card numbers

OperationalCredits 1 per callp50 756msData ValidationStar

Overview

Card Validator works by validating the card number against the Luhn algorithm and the brand's prefix and length rules. It identifies the card scheme, extracts the BIN and last four digits, checks the number against a list of known published test cards, and returns a risk score summarizing how safe the number is to trust.

Endpoint

One host, one path per API. The block below shows this call in four languages; every one of them is the same HTTP request. Making requests covers the timeouts, retries and parameter rules that apply to all of them. The SDKs wrap the same call in a typed client.

GEThttps://api.apiverve.com/v1/cardvalidator
curl "https://api.apiverve.com/v1/cardvalidator?number=4900264223817524" \
  -H "x-api-key: your_api_key_here"
const res = await fetch('https://api.apiverve.com/v1/cardvalidator?number=4900264223817524', {
  headers: { 'x-api-key': 'your_api_key_here' },
});

if (!res.ok) throw new Error(`${res.status} ${await res.text()}`);

const { data } = await res.json();
console.log(data);
import requests

res = requests.get(
    "https://api.apiverve.com/v1/cardvalidator?number=4900264223817524",
    headers={"x-api-key": "your_api_key_here"},
    timeout=15,
)
res.raise_for_status()

print(res.json()["data"])
package main

import (
	"fmt"
	"io"
	"net/http"
)

func main() {
	req, _ := http.NewRequest("GET", "https://api.apiverve.com/v1/cardvalidator?number=4900264223817524", nil)
	req.Header.Set("x-api-key", "your_api_key_here")

	res, err := http.DefaultClient.Do(req)
	if err != nil {
		panic(err)
	}
	defer res.Body.Close()

	out, _ := io.ReadAll(res.Body)
	fmt.Println(string(out))
}

Replace your_api_key_here with the key from your dashboard. When the inputs arrive as a list rather than one at a time, batch requests run up to 200 of them through this same API in a single call.

Authentication

Send your key in the x-api-key header. That is the only auth step — there is no token exchange and no per-endpoint scope to configure. Authentication covers creating, rotating and revoking keys.

401 is the only auth verdict

A 401 means the key is missing, invalid or expired. A 403 means the key is valid but not permitted here — blocked by a key restriction or an IP allow-list. Running out of credits is a 429.

Parameters

Sent in the query string. Premium parameters are accepted on every plan but only take effect on plans that include them.

ParameterTypeDescription
numberRequiredstringThe card number to validate
length 13–19

Response

Every API returns the same three top-level keys, so one response handler covers your whole integration: status, error and data. Only data changes shape. Response format covers the envelope, the other output formats and how premium fields are withheld.

Sample response
{
  "status": "ok",
  "error": null,
  "data": {
    "card": {
      "niceType": "Visa",
      "type": "visa",
      "patterns": [
        4
      ],
      "gaps": [
        4,
        8,
        12
      ],
      "lengths": [
        16,
        18,
        19
      ],
      "code": {
        "name": "CVV",
        "size": 3
      },
      "matchStrength": 1
    },
    "brand": "Visa",
    "cardNumber": "4900264223817524",
    "bin": "490026",
    "last4": "7524",
    "isValid": true,
    "isPotentiallyValid": true,
    "isTestCard": false,
    "riskScore": 0,
    "riskLevel": "low"
  }
}

Response fields

Paths are relative to data. Premium fields are absent rather than zeroed on plans that do not include them, so check for presence instead of comparing to 0.

FieldTypeExampleDescription
cardobject{...}Card identification and validation details
niceTypestring"Visa"Human-readable card type name like Visa
typePremiumstring"visa"Machine-readable card type identifier
patternsPremiumarray[4]Starting digit patterns for card type
gapsPremiumarray[4, ...]Character positions for spacing formatting
lengthsPremiumarray[16, ...]Valid card length values in digits
codePremiumobject{...}Security code specifications for card
namePremiumstring"CVV"Name of security code like CVV
sizePremiumnumber3Number of digits in security code
matchStrengthPremiumnumber1Confidence level of card type match
brandstring"Visa"Human-readable card brand (e.g. Visa, Mastercard), or null if the scheme could not be identified
cardNumberstring"4900264223817524"The validated card number provided
binstring"490026"The card's BIN/IIN (first 6 digits), or null if fewer than 6 digits were supplied
last4string"7524"The last 4 digits of the card, or null if fewer than 4 digits were supplied
isValidbooleantrueWhether the card number is complete and passes the Luhn checksum
isPotentiallyValidbooleantrueWhether the number could still become valid (correct brand prefix but possibly incomplete) — useful while a user is still typing
isTestCardPremiumbooleanfalseWhether the number is a known published processor test card (Stripe, Adyen, etc.) rather than a live card
riskScorePremiumnumber0Composite 0-100 risk score combining Luhn validity, test-card and scheme-recognition signals (higher is riskier)
riskLevelPremiumstring"low"Risk band derived from the score: low, medium or high

Errors

Read the HTTP status first, then error for the specific reason. The body names the parameter that has to change. Error handling covers the full status list and which of them are worth retrying.

StatusMeaningWhat to do
400Input was rejectedRead error; it names the parameter.
401Key missing or invalidCheck the header name and the key value.
403Key valid, but not permittedA key restriction or IP allow-list; see key scoping.
429Rate limited, or out of creditsRead error to tell them apart; see rate limits.

Use cases

Payment Processing
Use the Card Validator API to validate card numbers for payment processing. Use the data to verify card information and prevent fraudulent transactions
E-commerce Platforms
Validate card numbers by using the Card Validator API for e-commerce platforms. Use the data to ensure secure transactions, protect customer data, and comply with regulations
Financial Services
Secure financial services by using the Card Validator API to validate card numbers. Use the data to verify cardholder information, prevent identity theft, and enhance data security
Fraud Detection
Detect fraud by using the Card Validator API to validate card numbers. Use the data to identify suspicious activities, block fraudulent accounts, and protect against scams

Other ways to use Card Validator

Set up Card Validator on APIVerve, or reach the same source a different way. Your APIVerve account and credits work on all of them — one key, one balance.

Give it to an AI agentConnect over MCP and your agent calls it as a native tool — Claude, Cursor, ChatGPT.VerveKitReference →
Use it in Google Sheets or ExcelA =VERVE() formula fills a column — no script, no export, recalculates in place.VerveSheetsReference →
Ground an agent on itA cited, machine-checkable fact your model can't produce on its own.VerveContextReference →

More in Data Validation:

Was this page helpful?