continuity object and the last known card attributes in the nested card object.
The
card object contains the same fields as the BIN Data API enhanced response. This represents the current state of an active BIN, or the last known state of a BIN before it was deleted from the Pagos BIN Database.Continuity Object Fields
| Field | Type | Required | Description | Example |
|---|---|---|---|---|
bin | string | Yes | The queried BIN value (6-10 digits) | "41234567" |
bin_min | string | Yes | Minimum PAN value for the BIN range | "4123456700000000" |
bin_max | string | Yes | Maximum PAN value for the BIN range | "4123456799999999" |
status | string | Yes | Current lifecycle status of the BIN; see Status Values | "active" |
first_seen_at | string (ISO 8601) | Yes | Timestamp of the first BIN file in which this BIN range appeared | "2019-03-15T00:00:00Z" |
last_seen_at | string (ISO 8601) | Yes | Timestamp of the most recent BIN file in which this BIN range was present | "2024-11-01T00:00:00Z" |
flagged_for_delete_at | string (ISO 8601) | No | Timestamp when the BIN was marked for deletion; null if never flagged | "2024-10-15T00:00:00Z" |
deleted_at | string (ISO 8601) | No | Timestamp when the BIN was removed from the BIN file; null if still active | "2024-11-01T00:00:00Z" |
days_active | integer | Yes | Total number of days the BIN range was/has been present in BIN files | 2058 |
file_appearances | integer | Yes | Count of BIN file versions containing this BIN range | 68 |
card | object | Yes | Last known card attributes for this BIN range; see Card Object | see below |
Card Object
Thecard object contains the last known attributes for the BIN range. This is the same structure as the BIN Data API enhanced response.
For deleted BINs, this represents the state of the BIN at the time it was last present in a network source file.