---
agentTools:
  projectIndex: https://partner.getpliant.com/llms.txt
---

# Currency Card Controls, VOP, Beneficiary & Callback Updates

<br />

## What's New

### New Feature: Currency Card Controls

Partners can now restrict or allow card transactions by currency. Currency controls work alongside the existing country controls.

**Updated Endpoint:** `PUT /api/cards/{cardId}/card-controls`

Add a `currencies` object to the request body:

```json
{
  "currencies": {
    "restriction": "ALLOWED | BLOCKED",
    "values": ["EUR", "USD", "GBP"]
  }
}
```

The `currencies` field is also returned in `GET /api/cards/{cardId}/card-controls` responses.

**New Endpoint:** `GET /api/cards/card-controls/supported-currencies`

Returns the list of currencies supported for card controls.

***

### New Feature: Verification of Payee (VOP)

Partners can now verify that an account holder name matches a given IBAN before initiating a transfer.

**New Endpoint:** `POST /api/beneficiaries/{beneficiaryId}/payment-details/{paymentDetailId}/verify`

**Response:**

```json
{
  "matchLevel": "MATCH | CLOSE_MATCH | NO_MATCH | UNAVAILABLE"
}
```

<Callout icon="❗️" theme="error">
  VOP requests are subject to a configurable daily rate limit per partner. Requests exceeding the quota will receive a rate limit error response.
</Callout>

***

### New Field: `accountHolderName` in Beneficiary Payment Details

The `accountHolderName` field is now returned in beneficiary payment detail responses.

**Affected Endpoint:** `GET /api/beneficiaries/{beneficiaryId}/payment-details`

**New field in response:**

```json
{
  "accountDetail": {
    "accountHolderName": "Acme GmbH"
  }
}
```

***

### Improvement: `comment` Field on Card Limit Requests

The `comment` field is now included in card limit change request detail responses. Partners can retrieve the reason provided when a limit change was requested.

**Affected Endpoint:** `GET /api/cards/limits/requests/{limitChangeRequestId}`

**New field:** `comment` (String, nullable)

***

### Improvement: `taxIdentificationNumber` Now Optional in Onboarding

The `taxIdentificationNumber` field in `taxResidences` is no longer mandatory for UBOs and Authorized Signatories. Partners may omit it if not available.

**Affected resource:** Onboarding submission `taxResidences[].taxIdentificationNumber`

***

### New Callbacks: Card Benefit Load and Unload Events

Partners can now subscribe to notifications when benefit funds are loaded or unloaded from a card.

**New event types:**

* `CARD_BENEFIT_LOADED` -- fired when benefit funds are loaded to a card
* `CARD_BENEFIT_UNLOADED` -- fired when benefit funds are removed from a card

**Payload fields:** `organizationId`, `cardId`, `cardAccountId`, `loadAmount` / `unloadAmount`

Subscribe via the existing `CardSubscriptionRequest` with the new event types.

***

### New Callback: Cardholder Identity Verification Status Changed

Partners can now subscribe to notifications when a cardholder's identity verification status changes.

**New event type:** `CARDHOLDER_LEGITIMATION_STATUS_CHANGED`

**Payload fields:** `organizationId`, `cardholderId`, previous status, new status, verification timestamps

Subscribe via the existing `CardholderSubscriptionRequest`.

<br />