Credit card number validation API

One GET, one JSON body, no registry fee and no rate limit: a payment card primary account number (PAN) (worldwide) verified against its own check digits - the Luhn checksum plus issuer BIN ranges.

Request

curl -H "Authorization: Bearer $API_KEY" \
  "https://autorev.rohnelt.dev/v1/identity/validate?type=card&value=4111 1111 1111 1111"

Response

{
  "type": "card",
  "valid": true,
  "formatted": "4111 1111 1111 1111",
  "details": { ... }
}

valid is a boolean you can branch on at the form boundary; formatted is the canonical rendering to store, so your database stops holding six spellings of the same number.

Try the response without a key

Result appears here.

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.