Skip to main content

Get Started with the BIN Lookup Service

Before You Begin

Before you begin using the BIN Lookup Service:

Request the BIN Lookup Service

recommends that you send the full payment card number (PAN), a TMS token, or a network token when you request the BIN Lookup Service. This ensures that the service identifies a single BIN record during the request. Even though the service supports sending the six-digit or eight-digit card prefix in the request, this option can result in a MULTIPLE record match error if a single BIN record cannot be identified.

Send one of these payment credentials to the BIN Lookup Service to get the payment card account information.

  • Full payment card number (recommended best practice)
  • Eight-digit card prefix (not recommended because it might result in a MULTIPLE status record match error)
  • Six-digit card prefix (not recommended because this option can result in a MULTIPLE status record match error)
  • TMS customer ID token
  • TMS payment instrument token
  • TMS instrument identifier token
  • TMS jti transient token
  • Flex API JWT transient token
  • Network tokens (Visa VTS, MDES, and Discover)

Send the request to the BIN Lookup Service endpoint

POST /bin/v1/binlookup

POST /bin/v1/binlookup

POST /bin/v1/binlookup

For the full list of URL prefixes by environment and brand, see Endpoints.

Include one of the payment credential fields in the request

Include one of these fields:

  • paymentInformation.card.number (full payment card number is recommended)
  • paymentInformation.customer.id
  • paymentInformation.instrumentIdentifier.id
  • paymentInformation.paymentInstrument.id
  • tokenInformation.jti
  • tokenInformation.transientTokenJwt

For field descriptions and requirements, see BIN Lookup.

This example sends the full payment card number and receives a successful response:

{  "paymentInformation": {    "card": {      "number": "4XXXXXXXXXXXXXXX"    }  }}
{  "id": "7187318127246929204951",  "submitTimeUtc": "2024-06-18T05:30:12Z",  "status": "COMPLETED",  "paymentAccountInformation": {    "card": {      "type": "001",      "brandName": "VISA",      "maxLength": "16",      "credentialType": "PAN"    },    "features": {      "accountFundingSource": "DEBIT",      "cardPlatform": "CONSUMER",      "cardProduct": "Visa Classic"    }  },  "issuerInformation": {    "name": "CONOTOXIA SP. Z O.O",    "country": "PL",    "binLength": "6",    "accountPrefix": "41111111"  }}

Include optional fields as needed

Include these optional fields in the request as needed:

  • paymentAccountInformation.network.id
  • processingInformation.binSource

For field descriptions and requirements, see BIN Lookup.

Check the response

Verify that the response message confirms a successful request. A 200-level HTTP response code indicates success. For information about response codes, see Response Codes.

Last published: September 29, 2026