BIN Data API Overview
The Pagos BIN Data API is a very simple REST API that expects to receive—as input—a 6-10 digit BIN/IIN, and returns a simple JSON object back containing known details for the BIN.
If you prefer to query BIN data through your AI tools, check out our guide on the Pagos MCP Server
Testing
The Pagos BIN Data API doesn’t have a separate testing environment, but we do provide the ability to test a request and response by submitting a request with a valid API key; to do so, use the BIN: 999999.
For example:
Requests for information on this BIN (999999) won’t count towards your quota or be billed.
Enhanced Data
With the BIN Data API, you can request enhanced data by including the query paramater enhanced=true on you request. This provides you with up to 35 additional fields beyond the standard data fields. It includes additional card brand information, estimated interchange costs, SCA regulation requirements, and more. See the BIN Data API Dictionary for a detailed list of the enhanced data fields available and an example of how BIN data appears in a query response.
For example:
Error Handling
Any Pagos service errors will be presented in the following way:
Here are the possible values of the ERROR MESSAGE text:
| Message | Description |
|---|---|
| Too many requests. Please try again later. | The number of API calls has exceeded our default limits. |
| Trial for this account has ended. Please contact support@pagos.ai. | Your trial period has expired. Contact our Support team for continued access. |
| BIN Data Batch API access is not allowed. Please contact support@pagos.ai | Your account has not been enabled for the BIN Data Batch product. Contact our Support team for access. |
| This account is suspended. Please contact support@pagos.ai | Your account is suspended. Contact our Support team for more details. |
| This API key is invalid. | Our system can’t validate the provided API key. |
| API requires an API key in ‘x-api-key’ header. | You must pass your API key in the x-api-key header. See Getting Started with Pagos BIN Data for more details. |
| Card BIN/IIN not found. Please contact support@pagos.ai | We can’t find the requested BIN/IIN. This is an indicator that the BIN isn’t in our most recent BIN data and is likely no longer in use. Pagos BIN Data is updated weekly. |
BIN Data API Limits
The following are the API limits for BIN Data API calls:
| BIN Data API | API Endpoint | API Limit |
|---|---|---|
| Single BIN Lookup | /bins | 100 calls every 10 seconds |
| Multiple BIN Lookup (50 BINs per API call) | /bins/multiple | 6 calls every 10 seconds |
BIN Data API IP Addresses
The following static IP addresses can be used to allowlist API traffic to the Pagos BIN Data API:
99.83.189.21375.2.25.63
BIN Data API Overview
The Pagos BIN Data API is a very simple REST API that expects to receive—as input—a 6-10 digit BIN/IIN, and returns a simple JSON object back containing known details for the BIN.
If you prefer to query BIN data through your AI tools, check out our guide on the Pagos MCP Server
Testing
The Pagos BIN Data API doesn’t have a separate testing environment, but we do provide the ability to test a request and response by submitting a request with a valid API key; to do so, use the BIN: 999999.
For example:
Requests for information on this BIN (999999) won’t count towards your quota or be billed.
Enhanced Data
With the BIN Data API, you can request enhanced data by including the query paramater enhanced=true on you request. This provides you with up to 35 additional fields beyond the standard data fields. It includes additional card brand information, estimated interchange costs, SCA regulation requirements, and more. See the BIN Data API Dictionary for a detailed list of the enhanced data fields available and an example of how BIN data appears in a query response.
For example:
Error Handling
Any Pagos service errors will be presented in the following way:
Here are the possible values of the ERROR MESSAGE text:
| Message | Description |
|---|---|
| Too many requests. Please try again later. | The number of API calls has exceeded our default limits. |
| Trial for this account has ended. Please contact support@pagos.ai. | Your trial period has expired. Contact our Support team for continued access. |
| BIN Data Batch API access is not allowed. Please contact support@pagos.ai | Your account has not been enabled for the BIN Data Batch product. Contact our Support team for access. |
| This account is suspended. Please contact support@pagos.ai | Your account is suspended. Contact our Support team for more details. |
| This API key is invalid. | Our system can’t validate the provided API key. |
| API requires an API key in ‘x-api-key’ header. | You must pass your API key in the x-api-key header. See Getting Started with Pagos BIN Data for more details. |
| Card BIN/IIN not found. Please contact support@pagos.ai | We can’t find the requested BIN/IIN. This is an indicator that the BIN isn’t in our most recent BIN data and is likely no longer in use. Pagos BIN Data is updated weekly. |
BIN Data API Limits
The following are the API limits for BIN Data API calls:
| BIN Data API | API Endpoint | API Limit |
|---|---|---|
| Single BIN Lookup | /bins | 100 calls every 10 seconds |
| Multiple BIN Lookup (50 BINs per API call) | /bins/multiple | 6 calls every 10 seconds |
BIN Data API IP Addresses
The following static IP addresses can be used to allowlist API traffic to the Pagos BIN Data API:
99.83.189.21375.2.25.63