Card networks · SVG logos · BIN lookup

Card API

Show the card network.
Know the issuer when available.

Turn a processor-provided card prefix into a network name and logo for your payment UI. Add issuer and funding details to your dashboard with the same lookup.

Get startedExplore the API

Start free. Network and issuer lookups on every plan.

Try a card prefix

Try it

Example response/card/51
{
  "bin": "51",
  "brand": "mastercard",
  "brand_name": "Mastercard",
  "logo": "https://cdn.parseapi.com/card/mastercard.svg",
  ?deep=true
}

Use 2–11 prefix digits. Never send a full card number.

A prefix in. Card details out.

Start with the network.
Add detail when needed.

Get a network and logo by default. Add deep=true for issuer details. Explore the request and complete JSON for each case.

A network your interface can use.

Send a short prefix. Get the network key, display name and SVG logo.

Request

curl "https://api.parseapi.com/card/51" \
  -H "X-API-Key: YOUR_API_KEY"

Example response

JSON200 OK
{
  "bin": "51",
  "brand": "mastercard",
  "brand_name": "Mastercard",
  "logo": "https://cdn.parseapi.com/card/mastercard.svg"
}

Built for your interface

The name.
The logo.
Ready to show.

Give saved payment methods and transaction rows a recognizable network. Use the brand key in your code, the display name in your interface and the SVG at any size.

Use the network and logo
Example interface
  • Visa
  • Mastercard
  • American Express

BIN & IIN lookup

More context.
One lookup.

Add recorded issuer details to payment dashboards and reporting. Send at least six prefix digits and add deep=true.

The network and logo stay in the response. The matched prefix tells you which directory record supplied the detail.

Explore issuer details
Issuer
The recorded institution behind the matched prefix.
Country
The issuer’s recorded country code.
Funding type
Credit, debit or charge, when recorded.
Prepaid status
True or false when known. Null when unavailable.

Network & issuer coverage

Recognize the network.
Keep unknowns clear.

Network detection works independently of issuer coverage. Short prefixes can identify a network; more digits can resolve an ambiguous result.

Issuer coverage is partial and source ages vary. Unknown or ambiguous networks use a generic card logo.

Card networks

Recognize the networks below from a card prefix.

  • Visa
  • Mastercard
  • American Express
  • Diners Club
  • Troy
  • Discover
  • JCB
  • UnionPay
  • Maestro
  • Elo
  • Mir
  • Hiper
  • Hipercard
  • Naranja
  • Verve

Issuer details vary by prefix. Unknown fields stay null.

From the first request to your app

Your prefix.
Your stack.

Use the prefix your payment processor provides. Send it as a string to preserve leading zeros. One API key connects Card with the rest of ParseAPI.

Card API reference

HTTP, SDKs and MCP

Copy a request above or use an SDK in your application. Give your agent the same Card lookup through MCP.

Explore the response fields

Response fields

binstring
Supplied 2-11-digit card prefix with spaces and hyphens removed. Leading zeros are preserved
brandstring or null
Network key from reviewed prefix rules, or null when unknown or ambiguous
brand_namestring or null
Display name for brand, or null when brand is null

Deep fields

deep.prefixstring or null
Longest recorded prefix matching the start of bin, or null when unknown. May be shorter than the supplied input
deep.countrystring or null
Recorded card-issuer country as an ISO 3166-1 alpha-2 code, or null when unavailable
deep.issuerstring or null
Recorded issuer name, or null when unavailable
deep.typestring or null
Recorded card type, such as credit, debit, or charge, or null when unavailable or mixed
deep.prepaidboolean or null
true or false only when known. null means prepaid status is unavailable

Before you build.

How many digits should I send?

Send the processor-provided prefix you have, from 2 to 11 digits. Two digits identify some networks; others need more. An ambiguous prefix returns null until enough digits resolve it. Six or more digits enable issuer lookup. Never send a full card number.

What is a BIN or IIN?

A six- or eight-digit issuer identifier at the start of a card number. Shorter prefixes can identify a network. Some directory records use longer prefixes for additional detail.

What does Deep add?

Add deep=true for prefix, issuer, country, type and prepaid. deep.prefix is the longest recorded match and may be shorter than your input. The matched row keeps its null fields; missing values never inherit from a broader record. Deep is included on every plan.

Can I use the logo directly?

Yes. logo is a CDN SVG URL that scales to your layout. Set a width such as 40 pixels in your dashboard. Unknown or ambiguous brands, and brands without reviewed artwork, use a generic card logo.

How complete is coverage?

Network detection uses reviewed prefix rules. Issuer coverage is partial and source ages vary. Unknown or ambiguous brands return null with a generic logo; missing issuer facts stay null. A lookup does not confirm card validity, account activity or payment acceptance.

Will I need to change my code as issuer coverage grows?

No. Keep sending the same available prefix and add deep=true when you want issuer details. New records can improve those details without changing the response structure. Eleven digits is the current maximum, not a promise about every future data source.

What does a lookup cost?

One API request on every plan, including Free. Adding deep=true uses the same request, with no separate issuer lookup charge.

Card API pricing

Put card details in your app.

Network, logo and optional issuer details count as one API request on every plan. Your monthly allowance is shared across ParseAPI products.

Free

Start with a free API key.

Room to grow

Choose your capacity on Plans.

Get startedCompare plans