Skip to main content
​
Change

​
Fee Configuration API | Binding Lists Removed

GET /v1/fee-configs returns configurations effective now, without program or card bindings. The apply_to response attribute, including its programs and cards lists, is removed.
Update integrations that read apply_to.programs or apply_to.cards. Use GET /v1/programs/{program_id}/fee-configs to retrieve the configuration bound directly to a program, or GET /v1/cards/{card_id}/fee-configs to retrieve the effective configuration for a card.
For more information, see the Get Fee Configurations Endpoint.
​
Addition

​
Fee Configuration API | Program and Card Configuration Retrieval

Two new endpoints retrieve fee configurations: GET /v1/programs/{program_id}/fee-configs returns the configuration bound directly to a program, and GET /v1/cards/{card_id}/fee-configs returns the effective configuration applied to a card. Both accept an optional at query parameter to resolve the configuration at a specified instant, defaulting to the current instant.Both responses include fee_config_id and fee_config attributes. The card response also includes a source attribute with the value card or program to identify the binding type. Both endpoints return 204 when no configuration applies at the requested instant or fee configuration is disabled.
​
Addition

​
Fee Configuration API | New API

The Fee Configuration API is now documented. Use GET /v1/fee-configs to retrieve your tenant’s fee configurations and the card programs and cards each configuration currently applies to.For more information, see the Get Fee Configurations Endpoint.
​
Addition

​
PIN API | Hosted-Page Method for Set PIN

Set PIN now supports a hosted-page method, using the same PIN Control Access Token model as View PIN. The cardholder’s device is redirected to an Enfuce-hosted page that handles PIN entry and encryption directly with Enfuce, so no PIN material passes through the issuer’s back-end.For more information, see the Set PIN Guide.
​
Addition

​
PIN API | Hosted-Page Method for Change PIN

Change PIN now supports the same hosted-page method as View PIN and Set PIN, requested via the CHANGE_PIN scope. As with those, no PIN material passes through the issuer’s back-end.For more information, see the Change PIN Guide.
​
Addition

​
Spend Controls API | New API

The Standard Spend Control API is now documented, with endpoints to retrieve rule sets and rules, bind rule sets to entities, and create, update, delete, and retrieve rule parameters for an entity.For more information, see the Spend Control API Endpoints.
​
Addition

​
Test API | Transaction Lifecycle Simulation

The Test API is now documented for the integration environment. You can use it to simulate payment card transaction messages, including authorisation requests, reversals, advices, adjustments, incremental authorisations, Stand-In Processing (STIP) authorisations, purge requests, clearing requests, and batch transactions.For more information, see the Test API Endpoints.
​
Addition

​
Data Files | New Guide

A new guide explains data files for card, cardholder, transaction, and token events, including file naming, schema scope, and SFTP delivery.For more information, see the Data Files Guide.
​
Addition

​
Issuer Fees | New Transaction Fee Attributes

Issuer transaction fee details are now available on transaction.issuerTransactionFees in the Authorisation Request API, the clearing file copy, and the Transaction Events webhook. Each fee includes type and amount attributes, with type values of CASH_FEE, ATM_FEE, and MARKUP_FEE.For more information, see the Issuer Fees Guide.
​
Addition

​
Transaction Events | New AFT Transaction Type

A new AFT 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.
​
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.
​
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.
​
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:
​
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 and the Transaction Event Webhook Endpoint.
​
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 and the Transaction Event Webhook Endpoint.
​
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.
​
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.
​
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.
If you match on these message categories in the authorisation request webhook, update your integration accordingly.
​
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.
If you use Enfuce as your BIN sponsor (under ELS or EUK licensing), birthCountry is required for regulatory reasons.
For more information, see the Create Cardholder Endpoint.
​
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.
​
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.
​
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.
​
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.
​
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.
​
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.
If your integration sends or reads name on the Cardholder API, update it to use the structured cardholder name parameters and attributes.
​
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.
​
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.
​
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.
​
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.
​
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.