What a BIN lookup returns

Call /api/bin?bin=411111 and get:

  • brand: Visa, Mastercard, Amex and so on
  • type: debit, credit or prepaid
  • issuer: the issuing bank
  • country and country_code: where the card was issued

On the Complete plan, /api/bin-logo also returns the issuing bank's logo, handy for showing the card's bank in your checkout or admin tools.

How teams use it

  • Country mismatch. A card from one country, used from an IP in another, shipping to a third, deserves a second look.
  • Prepaid cards. Prepaid and gift cards are a favourite for free-trial and promo abuse. Apply stricter rules to them without punishing everyone.
  • Issuer patterns. If fraud keeps tracing back to a few issuers, tighten screening for those alone.
  • Better checkout UX. Show the card brand and bank as the customer types.

More in what a card BIN tells you at checkout.

Pair it with the IP check

A BIN alone is a weak signal. Next to an IP verdict it gets much stronger: a prepaid card behind a VPN shipping to a freight forwarder is a very different risk from a local credit card on a home connection. The IP + BIN plan gives you both on one API key, so one checkout step can screen the connection and the card. See the VPN detection API.

Safe by design

Send only the first 6 to 8 digits. Fraudex trims anything longer to 8 digits before it is used or logged, so a full card number never touches our logs even if one is sent by mistake. A BIN identifies the card product, never the cardholder.

Questions

How many digits should I send?

6 to 8. Newer cards use 8-digit BINs; if an 8-digit prefix is not on record, Fraudex retries with the first 6 automatically.

How much does it cost?

BIN lookups are included in the IP + BIN plan ($70 for 30 days, unlimited, up to 300 requests a minute) and the Complete plan ($99, adds bank logos and 600 requests a minute). See pricing.

Can I try it first?

Yes: the free BIN checker gives you 3 lookups a day.