Multiple Card Limits & Callback Improvements

New Feature: Multiple Card Limits

You can now create cards with multiple concurrent spend limits in a single request. Each additional limit has its own monetary cap, renewal frequency, and optional scope targeting a subset of transactions by merchant category, acceptance method, or ATM.

The additionalLimits array is optional. Existing integrations without it are unaffected.

Updated Endpoint: POST /api/cards (v2.1.0)

{
  "additionalLimits": [
    {
      "limitRenewFrequency": "MONTHLY",
      "limit": { "value": 20000, "currency": "EUR" },
      "scope": { "atmWithdrawal": true }
    },
    {
      "limitRenewFrequency": "MONTHLY",
      "limit": { "value": 150000, "currency": "EUR" },
      "scope": { "categories": ["TRAVEL_AND_ACCOMMODATION"] }
    }
  ]
}

Affected Endpoints:

• POST /api/cards - Create card with additional limits
• POST /api/cards/requests - Create a card request with additional limits
• POST /api/cards/limits/requests - Create a limit change request including additional limits
• PUT /api/cards/limits/{cardId} - Add, update, or remove additional limits on an existing card
• GET /api/cards/{cardId} - Returns additionalLimits with current balance info
• POST /api/cards/details (batch) - Returns additionalLimits per card
• GET /api/cards/requests/{cardRequestId} - Returns additionalLimits for card requests

Note: Requires the ADVANCED_CARD_LIMITS feature module to be enabled.

More information can be found here: https://customer-api.getpliant.com/docs/advanced-limits

New Feature: Callback Management Endpoints

You can now search, inspect, and resend callbacks directly via the API. The old /callback-log endpoint is deprecated.

New Endpoints:

• GET /api/callbacks - Search and filter callbacks with pagination
• GET /api/callbacks/{callbackId} - Fetch details and payload for a single callback
• POST /api/callbacks/{callbackId}/resend - Resend a previously delivered callback

Deprecated: GET /api/callback-log - Replaced by the endpoints above.

Improvement: cardAccountId in Callback Payloads

The cardAccountId field is now included in the following callback payloads:

• Copilot callbacks
• Card controls callbacks
• Card tokenization status change callbacks
• Card tokenization OTP callbacks

Improvement: HEALTHCARE Accounting Category

HEALTHCARE has been added as a valid value for the category field on transactions and accounting categories.

Affected: GET /api/transactions, GET /api/accounting-categories, and related transaction callbacks.

Improvement: CASH_WITHDRAWAL in Test Transactions

The CASH_WITHDRAWAL transaction type is now available when generating test transactions in sandbox environments.

Affected Endpoint: POST /api/test/generate-transactions

Change: Default maxTransactionCount for Travel Cards Lowered

The default value of maxTransactionCount for travel cards has been lowered from 5 to 3. This only affects newly created travel cards where maxTransactionCount is not explicitly set.

No breaking changes in this release. All changes are backward compatible.