Credit card number validator
A payment card primary account number (pan) (worldwide). Validation runs entirely on the check-digit algorithm: the Luhn checksum plus issuer BIN ranges. No external registry is queried, so there is no rate limit and no per-lookup fee.
Result appears here.
What the API returns
GET /v1/identity/validate?type=card&value=4111 1111 1111 1111
{
"type": "card",
"valid": true,
"formatted": "4111 1111 1111 1111",
"details": { ... }
}
Important limitation, stated plainly
A checksum proves the number is well-formed. It does not prove the number was ever issued, nor that it belongs to the person presenting it. Any vendor claiming otherwise from a checksum alone is overselling. Use this to reject the ~90% of bad input that is simply mistyped, then use an official registry for the rest.
Verify at scale, not one at a time
The same checks over a REST API: 250 calls per period free, no credit card, no sales call.