Data sources and credits

The datasets and documents behind the BIN checker, IBAN tools and gateway test card pages — with licenses and links.

Everything on Fakecreditcard that is not calculated from a formula comes from a published source. This page lists them, with their licenses and what we changed.

BIN data

The BIN checker and the BIN list use 374,788 BIN records from 225 countries.

BIN data: bin-list-data by Venelin Kochev (a lite version of binlookup.io), licensed under CC BY 4.0. Changes made by Fakecreditcard: issuer, brand and country names re-cased and standardized, spelling variants of the same issuer merged, malformed phone numbers and web addresses removed.

A BIN describes the card range, not a card or a person. If an entry is wrong, send us a correction.

Payment gateway test cards

The test numbers on the test card pages are copied from each provider’s official documentation, checked October 2026. Every number passes the Luhn check; numbers that fail it are left out.

GatewayOfficial documentation
StripeStripe docs – Testing
PayPalPayPal Developer – Card testing
PayPal Developer – 3D Secure test scenarios
BraintreeBraintree docs – Testing (General reference)
Braintree docs – 3D Secure Testing
Braintree docs – Processor Authorization Responses
AdyenAdyen docs – Test card numbers
Adyen docs – Testing 3D Secure 2 authentication
Adyen docs – Testing result codes and refusal reasons
Adyen docs – Testing card CVC/CVV/CID result codes
Adyen docs – Testing risk features (AVS)
SquareSquare Developer docs – Sandbox Payments
Authorize.netAuthorize.net Developer Center – Testing guide
Authorize.net Developer Center – Sandbox account
RazorpayRazorpay docs – Test Cards Details to Test Payments and Subscriptions
Razorpay docs – Test UPI ID Details
Checkout.comCheckout.com docs – Test cards
Checkout.com docs – Simulate card verification outcomes
Checkout.com docs – AVS check testing
Checkout.com docs – Payments testing
Checkout.com docs – API response codes
ShopifyShopify Help Center – Shopify Payments test mode and Test payment gateway
Shopify Help Center – Placing a test order
WorldpayWorldpay Developer – Card payment testing (Access Worldpay)
CybersourceCybersource Developer Center – Testing guide
MollieMollie API docs – Testing
Mercado PagoMercado Pago Developers (Brazil) – Test cards
Mercado Pago Developers (Mexico) – Test cards
Mercado Pago Developers (Argentina) – Test cards
FlutterwaveFlutterwave developer docs – Testing helpers
2Checkout2Checkout (Verifone) docs – Card test orders
2Checkout (Verifone) docs – Place test orders from the Merchant Control Panel
KlarnaKlarna Docs – Sample payment data
Klarna Docs – Sample customer data
Apple PayApple Developer – Apple Pay Sandbox Testing
Google PayGoogle Pay API for Web – Test card suite
Google Pay API for Android – Test card suite

IBAN formats

Lengths and BBAN structures for the 90 countries in the IBAN generator and IBAN checker follow the SWIFT IBAN registry (ISO 13616). Morocco’s national 28-character format is included and marked as not part of the registry. The IBAN check digits use the ISO 7064 mod-97 method.

Card number formats

Issuer prefixes (IIN ranges), lengths and security-code lengths for each brand follow the card networks’ published rules and the ISO/IEC 7812 numbering standard. The check digit is calculated with the Luhn algorithm (ISO/IEC 7812-1). Sandbox test numbers that payment providers document are listed separately on the gateway pages.

Fonts and icons

Text is set in Plus Jakarta Sans by Tokotype and card numbers in a digits-only subset of JetBrains Mono by JetBrains, both licensed under the SIL Open Font License 1.1 and served from this site. Icons and the card illustration are drawn in code for this site.

Related pages