Skip to main content
Ensure your integration with the BIN Benchmark API works correctly by making calls to our simulator in Test Mode.

Step 1: Create a Pagos Account or Sign In

If you’re interested in the BIN Benchmark API, you can try it out in Test Mode. Sign up for a Pagos account or log into your existing account, then click the environment toggle in the top-right corner; a yellow bar will appear across the top of the Pagos Service Panel to confirm you’re in Test Mode.

Step 2: Generate Your Test Mode API Keys

In Test Mode, generate an API Key for the BIN Benchmark API.
These API Keys are universal across Test Mode and will be used for testing all Pagos API products. If you’ve already created an API key in Test Mode, you don’t need to create a new one.
To generate your API key:
1
Click your settings icon in the top-right corner of your Pagos Service Panel.
2
Under Developers, click API Keys.
3
In the API Keys tab, click Create API Key to add a new key to your account.
API keys generated in any other tab under DevelopersBIN Data API, Action API, and Data Ingestion & Observability API—are legacy keys that will stop working on September 1, 2026.
4
In the side panel that opens, set your Key Name, then click Create API Key.
5
Copy your new API Key and store it somewhere secure.
This is the only time you can view this key!
6
Click I’ve Copied My Keys to confirm and exit the side panel.

Step 3: Test Looking up BIN Benchmark Data

Use our test BINs to test looking up BIN benchmark data in Test Mode. Note the endpoint for Test Mode points to sandbox, and—unlike other BIN Data API sandboxes—the BIN Benchmark API simulator only supports the exact BIN values listed below rather than entire BIN ranges.

BIN-6 to BIN-6 Match

Querying a 6-digit BIN returns benchmark data matched at the same length:
This will return the mock benchmark details, with bin_matched equal to the 6-digit BIN you queried:

BIN-8 to BIN-6 Match (Partial Match)

Querying an 8-digit BIN doesn’t guarantee a match at that same length. In this example, Pagos doesn’t have enough transaction volume at the full 8-digit length, so the response falls back to the closest 6-digit prefix with sufficient data; learn more about partial matches.
This will return the mock benchmark details, with bin_matched truncated to the 6-digit prefix 423808:

BIN-8 to BIN-8 Match

Some 8-digit BINs do have enough transaction volume for Pagos to calculate a reliable benchmark at the full length. In this example, the response matches at the same 8 digits queried:
This will return the mock benchmark details, with bin_matched equal to the 8-digit BIN you queried:

No Match or Insufficient Data

If the queried BIN doesn’t exist in the Pagos BIN Database, or Pagos doesn’t have enough transaction volume for it, bin_benchmark is returned as null; learn more about missing or insufficient network BIN data.
This will return a null benchmark:

Test BINs

Unlike the other BIN Data API sandboxes, the BIN Benchmark API simulator matches against the exact BIN values below rather than entire BIN ranges. Use these BIN values, as-is, for testing.