Skip to main content
The BIN Continuity API is coming soon.
If the BIN Continuity API fails, you’ll receive an error response with an appropriate HTTP status code.

Error Responses

Error Response Format

Error responses are returned in the following JSON format:

Common Error Scenarios

BIN Not Found (404)

Unlike the standard /bins endpoint which returns 404 for BINs not in the current file, the /bins/continuity endpoint only returns 404 if the BIN has never existed in any Pagos BIN file. If a BIN was previously active but has since been deleted, the continuity endpoint will return the historical data with the status "deleted".

Invalid BIN Format (400)

Ensure your BIN value:
  • Contains only numeric digits
  • Is between 6 and 10 characters in length
  • Does not include spaces or special characters

Rate Limit Exceeded (429)

If you exceed the rate limit of 100 calls every 10 seconds, wait briefly before retrying. Consider implementing exponential backoff in your integration.