Test keys and test data

A test key (sk_test_…) calls the same engines as production, so what you see while building is what you'll get. There are no fake fixed answers: send a real photo and you get a real result.

Trying an API without code#

The playground on verisec.dev runs any endpoint with sample images or your own, and shows the request and the answer. It's the quickest way to see what an endpoint returns before you write code. You need to be signed in.

Test cards#

These card numbers are safe to send to the card APIs. They pass the Luhn check and resolve to a real network and issuer, but they're public test numbers, never real cards.

NumberNetworkBehaviour
4242 4242 4242 4242VisaReads cleanly, Luhn valid
5555 5555 5555 4444MastercardReads cleanly, Luhn valid
3782 822463 10005American Express15-digit number
6011 1111 1111 1117DiscoverReads cleanly
4000 0056 0000 0008VisaUK issuer, debit
4111 1111 1111 1111VisaClassic Visa test BIN
Check a test card
curl -X POST https://verisec.dev/v2/cards/check \
  -H "Authorization: Bearer $VERISEC_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "number": "4242 4242 4242 4242",
    "expiry": "09/29"
  }'