Card Entity Enhancements & Validation

This changelog documents card-related API improvements including new properties, callback triggers, and validation enhancements.

Card Activation Method Property

A new activationMethod property has been added to the card entity based on the card manufacturer.

Response Changes:

The card entity now includes:

{
  "status": "PENDING_ACTIVATION",
  "activationMethod": "refNum" | "activationCode" | null,
  ...
}

Affected Endpoints:

• GET /cards/{id}
• GET /cards
• Card-related callbacks

For virtual cards, or cards where activation does not apply, this value is set to null. For more information, please check: https://partner.getpliant.com/reference/activate-physical-card

Small Improvements / Bugfixes

• The CARD_DETAILS_CHANGED callback is now triggered when a card's cardholder is changed via POST /cards/platform-fee/{id}/reassign
• Enhanced validation to prevent benefit card issuance or requests with invalid configuration properties like e.g. limit or limitFrequency != TOTAL.