Batch CSV (Dashboard)

Upload a CSV of BINs in the dashboard and download the same file enriched with a full lookup for every row — scheme, funding, issuer, country, currency, and card flags. No code, no API key, no integration work.

This is the no-code counterpart to POST /v1/bins: same 2,000-row cap, same data, same quota accounting.

Availability

Batch CSV is included in the BLAPI-500KPM plan ($100/month). See Plans & Quotas for the full comparison.

Test-mode organisations always have access and receive mock data, so you can try the workflow before subscribing. Test mode has a 500-lookups/day limit, so a test file larger than 500 rows is rejected on quota.

Any member of the organisation can use the page — no specific role is required.

Running a Batch

1. Sign in to the dashboard and open Batch in the navigation.
2. Check the remaining daily quota shown on the page — the whole file must fit in it.
3. Choose your CSV file and press Process CSV.
4. The enriched file downloads automatically, named <your-file>-enriched.csv. A summary line reports how many rows were found, not found, and invalid, with a Download again button.

The result is held in the browser only — it is not stored on our servers, and leaving the page discards it.

Preparing Your File

Each value follows the same rules as the single-lookup endpoint: 6 to 11 digits, from 100000 to 99999999999. Leading zeroes are not significant — 0400062 is looked up as 400062, though the bin column echoes exactly what you submitted.

Do not upload full card numbers. Values longer than 11 characters are redacted before anything is written or logged — see Card Number Redaction.

Example Input

bin
400062
99999999
invalid
4242424242424242

Output Columns

The downloaded CSV always has these 15 columns, in this order:

bin,scheme,funding,brand,category,country_code,country_name,issuer_name,issuer_website,issuer_phone,currency,prepaid,commercial,longer_bin_available,error

Fields with no value in the dataset come back as empty cells.

Example Output

bin,scheme,funding,brand,category,country_code,country_name,issuer_name,issuer_website,issuer_phone,currency,prepaid,commercial,longer_bin_available,error
400062,visa,debit,VISA,SIGNATURE,AE,UNITED ARAB EMIRATES,EMIRATES NBD BANK (P.J.S.C.),http://www.emiratesnbd.com/en/,+971800456,AED,false,false,true,
99999999,,,,,,,,,,,,,,NOT_FOUND
invalid,,,,,,,,,,,,,,BAD_REQUEST
[REDACTED],,,,,,,,,,,,,,BAD_REQUEST

Row Errors

Rows are never dropped or reordered: the output has exactly one row per input row, in the order you submitted them. A row that could not be resolved carries an error code and leaves the remaining columns empty.

Card Number Redaction

A value longer than 11 characters could be a full card number. It is replaced with [REDACTED] in the bin column and marked BAD_REQUEST. The original value is never written to the output file or to your request log.

Quota Accounting

Every data row counts as one lookup against the daily quota — including rows that come back NOT_FOUND or BAD_REQUEST. A 2,000-row file uses 2,000 lookups.

Booking is all-or-nothing. If the file does not fit in the organisation’s remaining daily quota, nothing is charged, no request-log entry is created, and the page reports how many lookups the file needs against how many remain:

Daily quota exceeded: this file needs 2,000 lookups but only 340 remain today (limit 10,000).

Split the file and retry, or wait for the reset at midnight UTC. See Plans & Quotas for daily limits.

A successful run appears as a single entry in Usage, with the row count as its unit total.

Upload Errors

The whole file is rejected — and nothing is charged — when it fails validation:

Line numbers refer to physical lines in the uploaded file, so they match what your editor shows.

When to Use the API Instead

Both consume the same quota at the same rate, and both are on BLAPI-500KPM.

Next Steps

• Batch Lookups — the POST /v1/bins endpoint
• Plans & Quotas — daily limits and plan features
• API Reference — every response field explained