prohibited
, to the riskScore
field in the Customer API.The riskScore
field now supports the following values:prohibited
value can be used to indicate customers who are restricted from using services due to sanctions or internal risk appetite. The API documentation have been updated accordingly.additionalValues
, to allow storing customer-level metadata as key-value pairs.These fields can be used to store additional data as needed. Enfuce does not apply any logic or validation to the values, so it is up to each customer to decide what to include in the key-value pairs.The new field is available in the following endpoints:locale
field in our Customer API:responseDescription
to the Notification API to provide more detailed context on declined transactions. When a payment is declined, the response description—if available—includes a return code and a brief explanation of the failure reason.This enables customers to send instant, informative notifications to cardholders via their app, improving transparency beyond the standard response codes. Only the most relevant reason is returned when multiple issues are present.Example:
“061 - Usage Limit 24H_RETAIL Amount Exceeded”This field was previously introduced in the Transaction API and is now also available in the Notification API. Refer to our service description for a list of response descriptions and usage details.57
to 58
78
to 5C
78
to 93
78
to 62
dueDate
field has been added to the Update Invoice API and GET Invoice API.
With this new field, charge card customers can shift the due date as long as the following requirements are met:IMMEDIATE_ACCOUNT_CLOSE
, has been added under the propertyToUpdate field. This action immediately closes the account.
For the change to take effect:regNumber
has been added to credit statement files. The field is optional and not applicable to all customers. If you wish to apply it to your statement files, please contact Enfuce.AdditionalValues
has been added to the Create Credit Account API, Update Credit Account API, and Get Account API. The additionalValues array is used to store information in the form of key-value pairs. These values are then populated in the statement files under ADD_INFO.accountCardBlocks
, has been added to the Account API for both updating a fleet account and updating a credit account, as well as in the GET Account information API. This field indicates which blocks are set for the account cards. The current values are SoftBlock and HardBlock, which can be true or false. If either SoftBlock or HardBlock is set to true, the account card usage is blocked. To enable card usage, both blocks must be set to false. To block account card usage, setting either value (SoftBlock or HardBlock) to true is sufficient.invoiceNumber
, has been added to the Invoice API for both updating and retrieving invoices. This field indicates the invoice number.homePhoneNumber
, mobilePhoneNumber
, and email
. These fields take the data from the customer linked to a card and can support use cases like courier deliveries, where contact information is needed.Details: If you need these fields in your embossing files, please contact Enfuce to ensure that the latest version has been enabled for you and aligned with the card personalisation bureau.