BIN Lookup API

About the BIN Lookup API

Send the first six to eight digits of a card as the bin parameter. The API resolves the BIN against payment card records and returns the card network, card type, issuing bank name and issuing country, plus the number rules for that scheme: valid card lengths, whether the Luhn check applies, and the security code name and size. Paid plans add the card category, the issuer phone and website where the bank has published them, ISO alpha-2, alpha-3 and numeric country codes, the country currency and flag, and coordinates.

What people use it for

Checkout Brand Detection

Display the matching Visa or Mastercard logo automatically when customers type the first six digits into your checkout form.

Debit vs Credit Routing

Apply different fees, limits or review rules to debit and credit cards before you run the authorization.

Debit Fee Optimization

Route transactions through lower-cost debit payment rails whenever the lookup confirms an incoming debit card.

Billing Country Mismatch

Flag suspicious orders for manual review if the card issuing country does not match the customer billing address.

Ways to call it

One endpoint, many ways in — REST with JSON, XML, YAML and CSV, plus GraphQL and an MCP interface for AI agents.

JSON

Default REST response

XML

Markup format

YAML

Human-readable

CSV

Tabular export

Beta

GraphQL

Query language

New

MCP

For AI agents

How it compares

Side by side with the tools people weigh BIN Lookup against — what each one is better at, in plain terms.

Request parameters — GET /v1/binlookup

Sent in the query string. Premium parameters are accepted on every plan but only take effect on plans that include them. Anything not listed here is dropped rather than passed through.

Required

Optional

1
2

curl "https://api.apiverve.com/v1/binlookup?bin=448590&ip=81.2.69.142" \
  -H "x-api-key: YOUR_API_KEY"

Authentication

Send your key in the x-api-key header. That is the only auth step — no token exchange, and no per-endpoint scope to configure.

Response — GET /v1/binlookup

Every APIVerve endpoint returns the same three top-level keys, so one response handler covers your whole integration: status, error and data. Only data changes shape.

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46

{
  "status": "ok",
  "error": null,
  "data": {
    "bin": "448590",
    "brand": "VISA",
    "type": "CREDIT",
    "category": "PURCHASING",
    "country": "UNITED STATES",
    "issuer": {
      "name": "JPMORGAN CHASE BANK N.A. - COMMERCIAL",
      "country": "UNITED STATES",
      "phone": null,
      "website": null
    },
    "location": {
      "latitude": "37.0902",
      "longitude": "-95.7129",
      "alpha2": "US",
      "alpha3": "USA",
      "numeric": "840",
      "currency": "USD",
      "currencies": [
        "USD"
      ],
      "flag": "🇺🇸",
      "isEU": false,
      "isEEA": false,
      "isSEPA": false
    },
    "number": {
      "scheme": "visa",
      "lengths": [
        16,
        18,
        19
      ],
      "luhn": true,
      "code": {
        "name": "CVV",
        "size": 3
      }
    },
    "customerIp": null
  }
}

Response fields

Paths are relative to data. Premium fields are absent rather than zeroed on plans that do not include them, so check for presence instead of comparing to 0.

Response headers

Every response carries your balance, so your own code always knows where it stands without polling anything. All four are exposed to browsers through CORS.

Errors

Read the HTTP status first, then error for the specific reason. The body names the parameter that has to change.

What a call costs — 10 credits per call

Credits are shared across every APIVerve API — one balance, one key, one bill. Failed requests never count against it, so a rejected input costs nothing.

Calls are what the credits buy at this API's rate — spend them here, on any of the other APIs, or across both. Nothing is reserved per endpoint.

Zero-code embed — one snippet, no backend

Drop an interactive BIN Lookup form onto any page. The widget calls the API for you, so no key ever appears in your markup and there is nothing to deploy.

Changelog — BIN Lookup API

Every change to this endpoint, newest first. Breaking changes ship as a new version and the previous one keeps serving — response fields are added, never removed or retyped in place, so an integration written against v1 keeps working.

Currently v1