> ## Documentation Index
> Fetch the complete documentation index at: https://nextgen-docs.enfuce.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Release Notes

<Update label="11 June 2026" description="Addition">
  ### Cardholder API | Address Returned in Responses and Events

  The address response now returns the full address: `address1`, `address2`, `address3`, `address4`, `city`, `region`, `zipCode`, and `country`. The same attributes are included in the corresponding cardholder webhook.

  For more information, see the [Get Cardholder Endpoint](/api/cardholders/get-cardholders/get-cardholder).
</Update>

<Update label="11 June 2026" description="Addition">
  ### Transaction Events | New `ORIGINAL_CREDIT` Transaction Type

  A new `ORIGINAL_CREDIT` value has been added to the transaction type enum, available across the Authorisation Request API, the clearing file copy, and the Transaction Events webhook.

  For more information, see the [Transaction Event Webhook Endpoint](/api/transaction-lifecycle/transaction-event/transaction-event-webhook-endpoint).
</Update>

<Update label="3 June 2026" description="Addition">
  ### New API | 3DS Out-of-Band Authentication

  Two new APIs support the Out-of-Band (OOB) 3-D Secure (3DS) authentication flow, where Enfuce sends an authentication challenge to the issuer's registered endpoint for the cardholder to approve:

  * The **3DS OOB Outgoing Webhook API** delivers the challenge — see the [OOB Authentication Challenge Webhook Notification](/api/transaction-lifecycle/3DS/OOB-authentication-challenge-webhook-notification).
  * The **3DS API** receives the cardholder's decision — see the [Submit Authentication Challenge Result Endpoint](/api/transaction-lifecycle/3DS/submit-authentication-challenge-result).
</Update>

<Update label="1 June 2026" description="Addition">
  ### Clearing File Copy and Transaction Events | Interchange Fee Breakdown

  A new `interchangeFee` object reports the interchange calculated by the scheme for the transaction, with `amount`, `currency`, and `direction`. The clearing file copy also adds `authorizationProcessedDateTime`, the time of the authorisation request. Both are available in the clearing file copy and the Transaction Events webhook.

  For more information, see the [Clearing File Copy Schema](/api/transaction-lifecycle/clearing-file-copy/clearing-file-copy-schema-contents) and the [Transaction Event Webhook Endpoint](/api/transaction-lifecycle/transaction-event/transaction-event-webhook-endpoint).
</Update>

***

<Update label="25 May 2026" description="Addition">
  ### Clearing File Copy and Transaction Events | Transaction Fee Attributes

  New attributes provide more detail on transaction fees:

  * `acquirerTransactionFeeAmount` — the fee charged (for example, by the acquirer) for transaction activity.
  * `issuerTransactionFees` — the issuer transaction fees applied to the transaction.

  The clearing file copy message category also gains `CHARGEBACK_REVERSAL`, `REPRESENTMENT`, and `REPRESENTMENT_REVERSAL`, and the Transaction Events message category gains `DOCUMENT_REQUEST`.

  For more information, see the [Clearing File Copy Schema](/api/transaction-lifecycle/clearing-file-copy/clearing-file-copy-schema-contents) and the [Transaction Event Webhook Endpoint](/api/transaction-lifecycle/transaction-event/transaction-event-webhook-endpoint).
</Update>

<Update label="18 May 2026" description="Addition">
  ### Cardholder API | Identification Number

  A new `identificationNumber` parameter is now available on the cardholder create and update requests, and is returned as an attribute on the cardholder response and the corresponding cardholder webhook.

  For more information, see the [Create Cardholder Endpoint](/api/cardholders/create-cardholder).
</Update>

<Update label="18 May 2026" description="Addition">
  ### Clearing File Copy and Transaction Events | Clearing Status

  The clearing file copy and the Transaction Events webhook now report `clearingStatus` and `partialClearingApplied`, which indicates whether the transaction was cleared in a single operation. The Transaction Events message category also gains `CHARGEBACK`.

  For more information, see the [Clearing File Copy Schema](/api/transaction-lifecycle/clearing-file-copy/clearing-file-copy-schema-contents).
</Update>

<Update label="18 May 2026" description="Change">
  ### Authorisation Request API | Message Categories Removed

  The following values have been removed from the authorisation request message category: `DECLINED_AUTHORIZATION`, `ADJUSTMENT`, `REVERSAL`, and `PIN_MANAGEMENT_REVERSAL`.

  <Warning>If you match on these message categories in the authorisation request webhook, update your integration accordingly.</Warning>
</Update>

<Update label="11 May 2026" description="Addition">
  ### Cardholder API | New Cardholder Parameters

  The cardholder create and update requests now support the `dateOfBirth`, `nationality`, `birthCountry`, and `riskScore` parameters, which are also returned as attributes on the cardholder response and the corresponding cardholder webhook.

  <Note>If you use Enfuce as your BIN sponsor (under ELS or EUK licensing), `birthCountry` is required for regulatory reasons.</Note>

  For more information, see the [Create Cardholder Endpoint](/api/cardholders/create-cardholder).
</Update>

<Update label="11 May 2026" description="Addition">
  ### Card API | Custom Card Delivery Types

  The card delivery type now supports five custom values — `CUSTOM_1` to `CUSTOM_5` — alongside the existing `MAIL` and `COURIER` options, for delivery arrangements agreed with Enfuce.

  For more information, see the [Create Card Endpoint](/api/cards/post-card/create-card).
</Update>

<Update label="4 May 2026" description="Addition">
  ### Cardholder API | Expanded Locale Support

  The cardholder `locale` parameter now accepts the full set of supported locales (around 140 values, such as `en-GB`, `fr-FR`, and `sv-FI`). The same enumeration applies to the corresponding cardholder webhook.

  For more information, see the [Create Cardholder Endpoint](/api/cardholders/create-cardholder).
</Update>

***

<Update label="27 April 2026" description="Addition">
  ### Clearing File Copy | Visa Message and Message Categories

  The clearing file copy now includes `records.visaMessage`, the raw Visa message, and adds the `DOCUMENT_REQUEST` and `CHARGEBACK` message categories and a `METADATA` posting status.

  For more information, see the [Clearing File Copy Schema](/api/transaction-lifecycle/clearing-file-copy/clearing-file-copy-schema-contents).
</Update>

<Update label="20 April 2026" description="Addition">
  ### Wallet API | Token Device Information

  Token responses and the token webhook now include device information: `deviceName` (the user-defined device name from the wallet or operating system), `deviceType` (for example `PHONE`, `WATCH`, `TABLET`, or `WEARABLE`), and `operatingSystem` (for example `IOS`, `ANDROID`, or `WATCHOS`).

  The Transaction Events message function also gains `ACCOUNT_STATUS_INQUIRY`.
</Update>

<Update label="13 April 2026" description="Addition">
  ### Transaction Events | New `REVERSAL` Transaction Type

  A new `REVERSAL` value has been added to the transaction type enum, available across the Authorisation Request API, the clearing file copy, and the Transaction Events webhook.
</Update>

<Update label="13 April 2026" description="Change">
  ### Cardholder API | `name` Removed

  The `name` parameter has been removed from the cardholder create and update requests, and the `name` attribute from the cardholder response.

  <Warning>If your integration sends or reads `name` on the Cardholder API, update it to use the structured cardholder name parameters and attributes.</Warning>
</Update>

***

<Update label="9 March 2026" description="Addition">
  ### New | Clearing File Copy

  The clearing file copy schema is now published, documenting the contents of the Enfuce clearing file copy.

  For more information, see the [Clearing File Copy Schema](/api/transaction-lifecycle/clearing-file-copy/clearing-file-copy-schema-contents).
</Update>

<Update label="2 March 2026" description="Addition">
  ### Authorisation Request API and Transaction Events | Processing Timestamp

  A new `processedDateTime` attribute — the time when the transaction was processed by Enfuce — is now returned on approved transactions in the Authorisation Request API and the Transaction Events webhook.

  For more information, see the [Transaction Event Webhook Endpoint](/api/transaction-lifecycle/transaction-event/transaction-event-webhook-endpoint).
</Update>

***

<Update label="16 February 2026" description="Addition">
  ### Transaction Events | New Transaction Types

  Two new values, `CONVENIENCE_CHECK` and `BALANCE_TRANSFER`, have been added to the transaction type enum, available in the Authorisation Request API and the Transaction Events webhook.
</Update>

***

<Update label="15 December 2025" description="Addition">
  ### Wallet API | Activate Token Endpoint

  A new endpoint activates a token by its card scheme's unique reference.

  For more information, see the [Activate Token Endpoint](/api/wallet/token/activate-token-by-token-id).
</Update>

<Update label="8 December 2025" description="Announcement">
  ### Initial Release | Enfuce Platform APIs

  The Enfuce platform documentation and APIs are now available, covering the full card lifecycle:

  * **Card API** — create, retrieve, update, replace, reissue, and activate cards, and manage card data and PIN control.
  * **Cardholder API** — create, retrieve, and update cardholders and list their cards.
  * **PIN API** — set, change, and retrieve the encrypted PIN.
  * **Wallet API** — push provisioning for Apple Pay, Google Pay, and Samsung Pay, and token lifecycle management.
  * **Authorisation Request API** — the outgoing authorisation control webhook for real-time authorisation decisions.
  * **Transaction Events API** — the transaction event webhook.
  * **Event webhooks** — outgoing card, cardholder, and token event webhooks.

  For more information, see the [API Introduction](/api/introduction).
</Update>