/
Public MintBIN service homepage and usage counter. Values refresh when this page is reloaded.
Card metadata service
MintBIN
is online.
Card metadata lookup through the MintBIN API, returning BIN, brand, card type, product level, issuer, country and last-four metadata.
Endpoints
Simple public endpoints for status and card-metadata requests.
/health
Lightweight service health endpoint for monitoring and availability checks.
/v1/bin
Validates the supplied card and expiry fields, applies per-IP rate limiting, then returns card metadata.
/v1/dataset
BIN dataset status: record count, source version, last update check and whether a newer release is available.
Request rules
MintBIN validates the request locally before querying its local BIN dataset.
Card number
Minimum 6 digits. A partial card number is accepted, but a complete card number is recommended for the most accurate metadata result.
Expiry month
Optional. If supplied, use 1–12 or the zero-padded form such as 06.
Expiry year
Optional. If supplied, use YY or YYYY format, such as 30 or 2030.
Rate limit
Each client IP may have at most 20 admitted requests in any rolling one-second window.
POST /v1/bin request headers
Use these headers when sending the JSON request body to MintBIN.
Content-Type: application/json
Required. MintBIN expects the POST /v1/bin request body to be JSON.
Accept: application/json
Recommended, not required. Explicitly tells the service that the client expects a JSON response.
Content-Type: application/json Accept: application/json
Example request
Send JSON to POST /v1/bin. Use HTTPS and do not place card data in a query string. Expiry fields may be omitted.
{
"number": "BIN_OR_FULL_CARD_NUMBER",
"expiry_month": "06",
"expiry_year": "2030"
}
Example response
The exact fields depend on the metadata returned for the supplied card.
{
"status": true,
"bin": "12345678",
"brand": "VISA",
"type": "CREDIT",
"level": "CLASSIC",
"bank": "EXAMPLE BANK",
"country": "EXAMPLE COUNTRY",
"country_code": "XX",
"flag": null,
"last4": "1234"
}
Request counter
The homepage counter records requests, from the time tracking is enabled, that pass local request validation
and enter the /v1/bin handler. Homepage visits, health checks,
malformed/invalid request bodies and requests rejected by the rate limiter
are not added. The counter is stored on disk and survives normal service restarts.