Home / Issuing / Issue Cards
Payment Card Revisions
When a payment card is issued or updated, the action is recorded in Highnote as a revision. A revision record captures the snapshot of the PaymentCard object before the changes to it were applied. The following types of payment card actions result in a revision:
- Issue
- Reissue
- Activate/deactivate
- Suspend
- Terminate
- Update other attributes: currently, only card form factor and card usage
You can use the Highnote API to view the revision on a payment card. The following revision data types are supported:
| Revision type | Description |
|---|---|
| Card status | Available enums: ACTIVATION_REQUIRED, ACTIVE, SUSPENDED, CLOSED. See PaymentCardStatus |
| Card form factor | Available enums: PHYSICAL, VIRTUAL. See CardFormFactor |
| Expiration date | ISO 8601 UTC timestamp of payment card expiry date |
| Card usage | Available enums: MULTI_USE, SINGLE_USE. See CardUsage |
| Updated timestamp | ISO 8601 UTC timestamp when the revision took place |
| Status change reason | Available enums: CREATED, EXPIRED, LOST, STOLEN, OTHER. See PaymentCardStatusChangeReason |
-
Traceability and Troubleshooting: By tracking when these changes were made (with the
updatedAttimestamp), organizations can quickly trace the origins of issues or unauthorized modifications. -
Compliance and Auditing: Maintaining a thorough record of all updates assists in compliance with financial regulations, providing auditors with a transparent view of the card's history.
-
Security and Fraud Prevention: Historical logs of status changes are invaluable for detecting patterns that may indicate fraudulent activity.
-
Operational Insights: Analysis of updates over time can reveal trends in card usage and lifecycle management, informing strategic decisions.
You can use the following FindPaymentCardRevisionSnapshot query to find revisions associated with a payment card. Additionally, the revisions attribute can be included on queries that support the PaymentCard object.