BIN Lookup - Card BIN/IIN Checker

BIN Lookup

BIN Lookup is a bulk BIN checker: look up 6-8 digit card BINs (IINs) offline and get the card scheme, debit or credit type, category, issuer and country. Full card numbers are rejected, never processed or stored.

Best for: Payments analysts, fraud and chargeback teams, checkout and routing logic, and reconciliation work that needs card-type data.

How to look up card BINs in bulk

1. Add 6-8 digit BINs to BINs (bins). Never paste full card numbers.
2. Click Start.
3. Download scheme, type, issuer and country for every BIN.

How it works

Uses a bundled copy of the open binlist-data dataset (about 343k BINs, CC BY 4.0, by Ian Nuttall), so lookups run offline with no third-party calls. Scheme detection comes from public IIN ranges (Visa, Mastercard incl. 2-series, Amex, Discover, JCB, UnionPay, Diners, Maestro). The dataset is community-compiled and no longer maintained, so issuer data may be out of date.

Output

input, schemeDetected, found, brand, type, category, issuer, country, countryName

Pricing (pay-per-event)

• bin-looked-up: $0.001 per result ($1 / 1,000). Platform usage is included; you pay only for results.
• Example: 10,000 BINs cost $10.00.

Example input

{
  "bins": [
    "424242",
    "535522",
    "37828224"
  ]
}

Example output

Values below are illustrative.

{
  "input": "424242",
  "schemeDetected": "VISA",
  "found": true,
  "brand": "VISA",
  "type": "credit",
  "category": "CLASSIC",
  "issuer": "EXAMPLE BANK",
  "country": "GB",
  "countryName": "United Kingdom"
}

Use it via API, schedules and integrations

Run it in Apify Console, or call it from your own code with the Apify API or the Python and JavaScript clients. Save an input as a task and add a schedule to run it regularly, and send results to Slack, email, webhooks, Zapier, Make or n8n with Apify integrations. AI agents can find and run it through the Apify MCP server.

from apify_client import ApifyClient

client = ApifyClient("YOUR_APIFY_TOKEN")
run = client.actor("sterlingverify/bin-lookup").call(run_input={"bins": ["424242", "535522"]})
for item in client.dataset(run["defaultDatasetId"]).iterate_items():
    print(item)

Use in Clay, Zapier, Make, n8n, Pipedream, Power Automate or Activepieces

All of them connect to Apify through their official Apify integrations, using your own Apify account: an API token from Apify Console > Settings > API & Integrations, or Apify sign-in for Power Automate. Runs bill to your Apify account at this Actor's pay-per-event price.

• Clay: save this Actor's input as an Apify task and copy it as JSON. In your Clay table, add the Run Apify Actor enrichment, choose it and paste the JSON into Input Data, mapping Clay columns into the fields. To pull a finished run into a new table, use the Import data from Apify Actor source.
• Zapier: use the Apify Run Actor action, or the Finished Actor run trigger followed by Fetch dataset items. Synchronous runs in Zapier stop after 30 seconds, so use the trigger for big batches.
• Make: add the Apify Run an Actor module with Run synchronously set to Yes, then Get Dataset Items with the run's dataset ID. For longer runs, use the Watch Actor Runs trigger.
• n8n: install the Apify node (@apify/n8n-nodes-apify, or search "Apify" on n8n Cloud) and use Run an Actor and get dataset.
• Pipedream: add the Apify app's Run Actor action, or Run Task Synchronously on one of this Actor's public example tasks (or your own saved task) to get the dataset items back in one step. For big batches, start from the New Finished Actor Run or New Finished Task Run trigger, then Get Dataset Items.
• Power Automate: add the Apify connector (a premium connector, currently in preview) and sign in with your Apify account. Use Run Actor with Enter custom value set to sterlingverify/bin-lookup and paste the input as JSON, then Get dataset items with the run's default dataset ID. For big batches, start the flow from the Actor run finished trigger instead.
• Activepieces: add the Apify piece and use Run Actor, or Run Task on one of this Actor's public example tasks (or your own saved task), then Get Dataset Items. For scheduled or big batches, use the Watch Actor Runs or Watch Task Runs trigger.
• Google Drive / Sheets: add Apify's Upload results to GDrive integration to a scheduled task to drop each run's CSV or XLSX into your team's Drive, or chain the Google Sheets Import & Export actor to append rows to a sheet.
• Slack alerts: add Apify's Slack integration to a scheduled task to post each run's results to your team channel, or start a check from Slack with /apify call and your task ID.
• Any HTTP tool or script: send one request and get the results back as JSON. Runs must finish within 5 minutes.

curl -X POST "https://api.apify.com/v2/acts/sterlingverify~bin-lookup/run-sync-get-dataset-items" \
  -H "Authorization: Bearer YOUR_APIFY_TOKEN" \
  -H "Content-Type: application/json" \
  -d @input.json

FAQ

Where does the BIN data come from?

A bundled copy of the open binlist-data dataset (about 343k BINs, CC BY 4.0, by Ian Nuttall). It is community-compiled and no longer maintained, so issuer data may be out of date.

Can I send full card numbers?

No. Anything over 8 digits is rejected and not processed.

Disclaimer

BIN data: binlist-data (github.com/iannuttall/binlist-data), © Ian Nuttall, licensed CC BY 4.0. Not an official IIN register, so accuracy is not guaranteed. Not affiliated with any card scheme. Submit BINs only (first 6-8 digits); anything over 8 digits is rejected and not processed.

Related sterlingVerify tools

Part of the sterlingVerify UK payments, KYB and data toolkit on Apify Store:

• Payments Region Checker: EEA, SEPA, SCA and interchange classification by country or BIN
• IBAN Validator: offline bulk IBAN validation and parsing
• UK Bank Account Validator: UK sort code and account number modulus check
• MCC Checker: check a merchant's MCC against its website or description