Release Notes

​

Enhanced Transparency on Payment Declines

We have added a new field, Response Description, to our Transaction API. If available, it provides additional context on why a transaction failed, including a return code and a brief explanation.

Examples include:

• 061 - Usage Limit “24H_RETAIL” Amount Exceeded
• 057 - Invalid Contract Status

If multiple issues cause the decline, only the most relevant response description is returned. For a list of common response descriptions, refer to our service description.

​

Updated Response Codes for Advanced Spend Control Declines

We have introduced more granular response codes for payments rejected due to Advanced Spend Control rules. Previously, these transactions were rejected with response code “05.”

The new, more specific response codes include:

• 03 BLOCKED_MERCHANT: Declined due to merchant restrictions.
• 57 (Mastercard) and 62 (Visa) BLOCKED_COUNTRIES: Declined due to country restrictions.
• 61 AMOUNT: Declined due to an amount limit set by spend control rules.

​

Chip Transaction Security Update

Effective April 28, 2025, all chip transactions without PIN verification will be declined unless an exemption has been granted.

​

SubmerchantID Parameter Added to TransactionAPI Endpoints and Data Exports

For improved merchant hierarchy support, the submerchantID parameter was added to all relevant TransactionAPI endpoints and included in all exported transaction files to enable downstream reconciliation and reporting.

​

Enhanced API Documentation on Usage Limiters

Enhanced the Usage Limiters section with real-world use cases and step-by-step examples demonstrating how to configure and apply usage limiters.

​

Enhanced Service Description on Response Codes and Declined Payments

• Updated the Response Codes & Declined Payments section in our Service Description to cover every response code.
• Added real-world example use cases demonstrating each response code.
• Included detailed information on decline‐reason prioritization to help interpret multiple failure scenarios.

​

New Transaction Types and Enhanced Traceability in Authorisation Control Webhook Payloads

Additional Transaction Types

We have added 4 new enums: CARDHOLDER_CREDIT, CASH_DISPENSE, CARDHOLDER_CREDIT_REVERSAL, CASH_DISPENSE_REVERSAL to the transactionData.transactionType field.

New Field for Enhanced Traceability

A new field, transactionData.schemeTransactionLinkId, has been added to the webhook payload. This scheme-specific field, provided by Visa and Mastercard, enables better traceability across multi-step transaction flows and assists in reconciliation and dispute resolution.

• Visa Field: transactionIdentifier (Field 62.2)
• Mastercard Field: transactionLinkId (Field DE105 subfield 001, only applicable if enabled by scheme until 17th October 2025, when becomes available for all)

For detailed information, please refer to our current API documentation.

With these changes, our Authorisation Forwarding Webhook became obsolate. Planning has begun to phase it out and migrate current users to Authorisation Control. Current users of Authorisation Forwarding will be contacted to plan migration.

​

Update to card closing logic

We have updated the logic governing card closures to ensure a consistent approach when accounts are closed. This change aligns with compliance requirements and ensures clear, predictable handling of accounts, cards, and tokens.

What has changed?

• When an account enters “Account To Close” status, linked cards are Blocked.
• When an account reaches “Auto-Closed” or “Account Closed” status, linked cards are now Closed, and any linked tokens (e.g., Apple Pay) are Deleted.

​

Enhancements to Statement, Invoice and Reminder exports

We have improved the billing document export process for invoices, statements, and reminders to enhance file handling, reconciliation, and data consistency.

What has changed?

• Increased file size limit – The maximum number of records per file increases from 99 to 50,000. File size will now depend on the number of transactions and cards linked to the account.
• New reconciliation file – Each export will include a reconciliation file to track processed and failed records.
• Streamlined XML formatting – Fields without values (null/undefined) will no longer appear as empty tags.
• Improved currency representation
  • Currency fields will now use Alpha codes (e.g., “EUR”, “SEK”).
  • CurrencyCode fields will use numeric values (e.g., “978”, “752”).

​

Introducing NPS surveys in MyEnfuce

We’re excited to launch Net Promoter Score (NPS) surveys for MyEnfuce! Since MyEnfuce plays a big role in our customers’ experience, it’s crucial for us to measure how well we’re contributing to that experience.

All users will receive a quick survey every 90 days. Your feedback is invaluable in helping us improve MyEnfuce and stay on the right track.

Thank you for helping us make MyEnfuce even better!

​

Updated Response Codes for Visa Transactions

Visa transaction response codes have been updated to improve clarity and align with industry standards.

• Card Closure: Response code updated from RC 14 (Invalid Card Number) to RC 46 (Contract Closed).
• Account Closures: Similar to card closures, account closure response code RC 14 (Invalid Card Number) is replaced with RC 46 (Contract Closed).
• Fraud-Related Card Closures: Transactions blocked due to fraud will now return RC 07 (Pick Up Card, Special Condition) instead of RC 04 (Pick Up Card).
• Account Blocks: Response code RC 57 (Transaction Not Permitted to Cardholder) is now replaced with RC 78 (Contract Blocked) for blocked accounts.

​

Authorization Control Webhook Update

The BALANCE_INQUIRY transaction type has been added to the transactionData.transactionType enum in the request payload. Additionally, a new optional field, availableBalance, is now included in the response to support ATM balance inquiries.

​

3DS Static Password Length Update

To enhance security and flexibility, the maximum length for 3DS static passwords has been increased from 6 to 16 characters, while the minimum remains 4 characters.

This update allows for stronger passwords, improving authentication security for online transactions.

​

New riskScore field added to Customer API

A new riskScore field has been introduced in the Customer API. This field represents a customer’s risk assessment score and supports predefined values: High, Med, Low, and Pep (Politically Exposed Person).

The field is included in customer creation and update processes, with the ability to modify it as needed. If not provided at creation, it defaults to null but cannot be reset to null once set.

For more details, refer to the API documentation: Create a Customer.

​

Notifications for NRC Advices, Adjustments & Reversals

Previously, notifications were only sent for positive response codes. Now, negative response code (NRC) transactions for Advices, Adjustments, and Reversals will also trigger notifications.

This ensures better visibility of all processed transactions. No action is required, but clients should expect more complete event coverage.

​

Default Value for “Interest Posting Enabled” in Account API

The Account API previously returned “interestPostingEnabled”: null, instead of the expected true by default. This caused MyEnfuce UI to display null also. The issue has been fixed to ensure the API returns true by default, aligning with documentation.

​

Enhanced Transaction Details in MyEnfuce

We’ve made key improvements to the transaction listing and details view in MyEnfuce, providing more clarity and reducing unnecessary support inquiries.

• Transaction Type Name in List View – The transaction type name is now displayed in the list view, making it easier to identify transactions, especially those posted via API (merchant: “API”).
• Transaction Type Name in Details – This information is also now available in the transaction details view, offering more context beyond just the transaction code.
• Response Description for Error Code ‘61’ – We’ve introduced a more detailed response description for transactions failing with error code ‘61’, with plans to expand this enhancement to other error codes soon.

These enhancements are also available via the Transaction API.

​

Real-Time Purchase Notifications with Merchant Details

Our Notification API now includes Merchant ID and Acquirer ID for every transaction, this enables our customers to include merchant details in real time purchase notifications.

​

Enhanced Authorization Handling for Partial Approvals and Advanced Spend Controls

The authorization system has been updated to process transactions based on merchant support for partial approvals and advanced spend control authorization limits. When the merchant supports partial approvals, if the authorization amount exceeds the allowed single-amount rule in advanced spend controls, the transaction will be partially approved up to the allowed rule amount.

​

”WARM UP” Message Format Update

“WARM UP” messages sent via our Outgoing authorisation control webhook endpoint and Forward authorisation webhook to customer endpoints are now in JSON format instead of plain strings. This update improves clarity, consistency, and compatibility across our API.

​

Chargeback Transactions Reintroduced in VISA Clearing File Copy

Retail Chargeback (Retail Cbk) and ATM Chargeback (ATM Cbk) transactions have been reintroduced into the VISA clearing file copy. These chargeback transactions were previously excluded as they do not impact cardholder balances. They are now included to ensure the clearing file copy accurately reflects VISA’s original clearing files.

​

Updated Response Code for Merchant MCC Blocks for Mastercard Transactions

The response code for Merchant MCC (Merchant Category Code) blocks has been updated from RC 57 (“Transaction Not Permitted”) to RC 03 (“Invalid Merchant”). Transactions declined due to MCC blocks will now return RC 03 (“Invalid Merchant”) instead of RC 57. This update aligns with Mastercard recommendations and improves clarity in decline messaging.

​

Updated Response Codes for Visa Transactions

Visa transaction response codes have been updated to improve clarity and align with industry standards.

• Merchant MCC Blocks: RC updated from 57 to 03 (Invalid Merchant).
• Geo Blocks: RC updated from 57 to 62 (Restricted Card).
• Usage Limits: RC updated from 61 to 65 (Exceeds Withdrawal Frequency Limit) for spend limits (Monthly, Weekly, 24H usage).
• Card Contract status (Card blocked): RC updated from 57 (Transaction Not Permitted to Cardholder) to RC 78 (Invalid Account).

​

Bug fix: Available balance was not shown for sub-accounts

The available balance for sub-accounts in the account hierarchy is now displayed in the Account_Balance_Type data warehouse file.

​

New field added to Update Invoice API and GET Invoice API

A new 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:

• The invoice needs to be open.
• The current due date has not been reached yet.
• The new due date is not in the past.
• The new due date is not earlier than the current due date.
• The new due date is set to a maximum of 365 days forward from the current due date.

Note: The new due date shifting calculation does not account for logical adjustments. For example, if the new due date falls on a Saturday, it will not automatically move to the next banking day.

​

New field added to Update Account (POST) API

A new action, IMMEDIATE_ACCOUNT_CLOSE, has been added under the propertyToUpdate field. This action immediately closes the account. For the change to take effect:

• The account to be closed must have a zero balance.
• The use of this feature must be agreed upon and enabled with Enfuce before it can be utilized.

​

New invoice DWH files for charge card customers

Enfuce offers charge card customers two data export files where customers can view invoice lifecycle events, such as invoice payments and invoice statuses. More information about these files and their contents can be found in the Enfuce data export file documentation: Invoice file description.

​

Weak PIN validation

To enhance security, we have implemented a weak PIN prevention feature. Enfuce will now reject PIN change requests to weak PINs and avoid generating new weak PINs, strengthening PIN protection for cardholders.

• Weak PIN List: Predictable and common patterns like ‘1234’, ‘0000’, and years from ‘1956’ to ‘2015’ are now restricted.
• New PIN Generation: All newly generated PINs will exclude weak patterns.
• No Impact on existing PINs: Current PINs remain unaffected; this feature applies to new PINs and changes only.

​

Enhanced Transaction Filtering in MyEnfuce

Introducing the “Show Authorizations” filter in the Transaction view! Quickly hide authorizations to focus solely on posted transactions, simplifying your data analysis.

​

Longer MyEnfuce Session Duration

We’ve extended the maximum session duration from 60 minutes to 8 hours, allowing you to work without frequent logouts. MyEnfuce remains fully PCI DSS compliant to ensure your data is secure.

​

Rounding issue with statement files

Credit statement files contained a rounding error in the FX markup fee for some transactions. This issue has now been corrected.

​

New optional client registration number field added to Statement XML and XSD

A new field called 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.

​

New API field in Account API

A new field called 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.

​

Reminder file bug fix

We found a bug in the reminder files where the number mapped in the invoice number field was incorrect and was taken from the invoice reference number. This has now been fixed so that the actual invoice number is mapped to the invoiceNumber field.

​

New field in Account API

A new field, 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.

​

New field in Invoice API

A new field, invoiceNumber, has been added to the Invoice API for both updating and retrieving invoices. This field indicates the invoice number.

​

New contact information fields added to embossing file

Three new fields have been added to the embossing file: 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.

​

Enfuce Tokenisation Notification Update

Enfuce has updated the notification messages for tokenisation events to enhance security and privacy for cardholders. These changes will become applicable in week 50. Below is a summary of the updates: Changes to tokenisation event notifications

• ACTIVATE event notification
  • Previous behavior: Enfuce sent a notification containing an SMS OTP message, which the cardholder used to complete the activation of a new token.
  • Update: The exposure of this OTP will now be restricted. Enfuce will no longer send this OTP message directly to customers.
  • Impact: Cardholders will continue to receive the SMS OTP, so no action is required by Enfuce customers.
• STATUS_CHANGE event notification
  • Update: No changes to this notification. It remains the primary notification for tracking tokenisation events.
• TOKENIZATION_REQUEST event notification
  • Previous behavior: This notification contained cardholder-sensitive information, such as device IP, for fraud monitoring purposes.
  • Update: To enhance security, this notification will now be restricted and only sent to customers who conduct external fraud monitoring.
  • Impact: Customers not conducting external fraud monitoring will no longer receive these TOKENIZATION_REQUEST notifications.

All updates will be in effect starting in week 50. For questions or assistance, please contact Enfuce support.

​

User Management available in MyEnfuce

The User Management feature allows you to manage users within your organisation by adding, removing, and updating user roles. If you are a customer of Enfuce, you must first ask Enfuce Business Services to assign the Tenant Admin role to one or more of your users. See MyEnfuce Help for further information.

​

Flexible card artwork and branding in digital wallets

This feature allows the issuer to personalise card artwork, update terms and conditions, and modify issuer contact information effortlessly. With support for multiple looks within the same BIN range, the issuer can cater to diverse customer preferences and strategic needs without setting up new products for every type of artwork.

Key benefits:

• Cost and time savings: No need to set up a new product for different artwork, saving both time and resources.

• Cater to customer preferences: Offer various card artworks in B2C and B2B sectors to meet different customer needs.

• Target strategic customers: Provide different artwork for strategic customers, partners, or segments (e.g., silver, platinum, gold).

• Increase brand recognition: Differentiate your brand with unique designs.

More information here.

​

Update to Test API DNS Name

Enfuce has made internal changes to expose all different endpoints under a single DNS name. This only impacts the use of our Test API, where the DNS name has now been updated. For those using the Test API, please see our API documentation for the updated DNS name to use.

​

New Informational Fields Added

New field minimumToPayBalance added in GET Account information API. This minimum to pay balance is the actual balance that the cardholder should pay after invoicing.

​

 Transaction API – enhancements to reversals 

RE (Refund Positive Balance) transactions can now be reversed with the Transaction API.

Also, transaction fee types: PI (Paper Invoice), REM1 (Reminder 1) and REM2 (Reminder 2) can now be reversed.

​

Fixing a typo in institution_id field in Enfuce Data Export Files (Week 39)

We’ve found a typo in the institution_id field within the Enfuce data export files, specifically in the “Token file.” The field is currently labeled as INSTITITION_ID (with an extra character). This will be corrected to INSTITUTION_ID on week 39, 25th of September 2024. Please ensure any systems or processes that use this field name are updated accordingly for that date.

​

Enfuce spend blocks enabled for virtual card endpoints

The Enfuce spend blocks for regional and e-commerce transactions have now been enabled for virtual card endpoints, which means that you can now limit virtual cards to desired regions and block e-com use of the virtual card. The relevant field name for this functionality is regionAndEcommBlocking.

​

New additionalvalues field added to Card API

We’ve implemented a new additional information field to our Card API. The additionalValues array has been implemented in the Card API to store key-value pairs. While Enfuce ensures these pairs meet character limit constraints, no further validation or processing is applied. These key-value pairs may also be included in the card personalisation files, depending on the version. If needed, please review the specific version details of your card personalisation files to confirm if these values are relevant for your implementation.

​

New informational fields added

These new informational fields have been added to the Customer API. The purpose of these fields is to add context to the customer accounts.

Private customer

Field Name: deceasedDate Description: The date when the customer has deceased, in ISO 8601 format (“YYYY-MM-DD”). This field is for informational purposes only and does not trigger any further actions or processes implemented by Enfuce.

Corporate customer

Field Name: bankruptcyDate Description: The date on which the company declared bankruptcy, in ISO 8601 format (“YYYY-MM-DD”). This field is for informational purposes only and does not trigger any further actions or processes implemented by Enfuce.

​

Creating digital cards

Now you can easily choose with just one click whether you want to create a physical, digital, or both card types when issuing a new card. Previously, a physical card was automatically created for the cardholder. Now, there is an option to choose if the physical card is needed and that decision can be changed at any time during the card lifecycle. This streamlined approach to card form management makes it easier for the issuer to manage different card types and reduce unnecessary physical cards. It also improves the end-user experience with the possibility to seamlessly use different card types.

Key benefits:

• Reduce the amount of unnecessary physical cards.

• Increased flexibility for the end user.

• Choose card types with just a click.

More information here.

​

Reminder and collection process 

This enhancement allows issuers to effortlessly remind customers of any overdue balances, thereby reducing credit risk. This new process streamlines the management of overdue balances, ensuring timely and effective customer reminders, and enhancing overall credit risk management.

Our comprehensive suite of reminder and collection events provides a variety of rule options, enabling issuers to customize a flow that best meets their specific needs and complies with regulatory standards across different markets.

Key features:

• Fully automated reminder and collection process.

• Customisable actions based on predefined rules set during the implementation project.

• Diverse rule options to tailor the process according to issuer requirements.

• Compliance with various regulatory standards across multiple markets.

More information here.

​

Disposable cards 

Enfuce’s new card type, a disposable card, is a virtual card, which will be disposed of after a certain pre-defined time. Disposable virtual cards are easy and instant to issue and live in the issuer’s app or in their digital wallet. Disposable cards are a cost-effective and efficient solution which adds security and convenience to issuers and cardholders.

Key benefits:

• Added security for issuers.

• Ability to assign cards for certain projects, for example, for a business trip.

• Reduce the number of expense claims paid with personal cards.

More information here.

​

New Transaction Types added in statement and invoice files 

As we have enabled reversing these fees, we’ve also added these transaction types “Refund positive balance (RE-R)”, “Paper invoice fee (PI-R)”, “Reminder 1 fees (REM1-R)”, “Reminder 2 fees (REM2-R)” added to Statement and Invoice exports.

​

Fleet Management – Invoice View in MyEnfuce 

This feature allows Fleet customers to manage and track all their invoices in one place. You can easily see invoice statuses, amounts, references, and important reminder dates. While the view is currently read-only, editing functionalities are under development. To access this, simply navigate to the Invoices tab on the Fleet account of your choice. This addition simplifies invoice management and helps customers stay on top of their billing processes.

​

Manage Suspended Payments in MyEnfuce

With the new Suspended Payments feature in MyEnfuce, you can now easily handle incoming payments where the reference number does not match any outstanding invoices. MyEnfuce users can go through a list of such payments and attempt to manually find matching accounts. If a matching account is found, the payment can be reserved and posted to the correct account. If no match is found, the payment can be reserved and returned to the customer. Note that this feature requires configuration by Enfuce. This update helps streamline the reconciliation process, reducing manual errors and ensuring payments are handled correctly.

​

Discounts

Issuers can now offer discounts for single transactions or linked line items. You can offer your customers a rewards program with transaction-specific cashbacks and discounts – making your payment product more attractive to a range of end users. You have full control over how much discount each customer gets and for which transactions.

The discounts are posted as refunding transactions that will benefit your customers immediately. This feature is available for both credit and prepaid products.

Key benefits:

• Create a rewards program that is highly attractive to end users and stays relevant in comparison to your competitors.

• Almost instant rewards to your customers – not only at the end of the month like comparable solutions.

• Control on card level which transactions are applicable for a discount.

• Control on card level how much the discount is and whether is it a fixed amount or a percentage.

• All discount rules are controllable through APIs, allowing for real-time creation, viewing and updates.

More information here.

​

Purchase details

This solution enables enriching transactional data with, for example, receipt line items, quantity of items or travel details. While normal card transactions have a lot of information, they lack detailed data about what was bought. Enfuce’s purchase details feature allows you to enhance each transaction with additional details and utilise these in user interfaces and the invoicing process.

Key benefits:

• Effortless way to capture purchase details related to transactions

• Enables adding purchase details to invoices, cardholder-facing interfaces and customer service interfaces

More information here.

​

One-time password authentication in 3DS

Enfuce has two authentication options for e-commerce purchases (3DS):

1. Authentication performed by the issuer

2. Authentication with a one-time password (NEW)

Enfuce offers SMS OTP (one-time password sent with SMS text) to authenticate 3DS online payments. This method authenticates the purchase by using a static password and One-Time password (OTP) sent to the customers’ mobile device.

The main benefit of choosing this method is that you don’t need to have an external authentication provider or implement anything additionally – we do it for you!

More information here.

​

 Instalments

The instalments feature allows the cardholder to pay for their purchases in instalments. In practice, they convert a portion of their account balance into instalments, which means that they can divide the balance into smaller equal payments over a certain period. This allows the cardholder to spend more and finance their bigger purchases.

Key benefits:

• More flexibility for the cardholder.

• The issuer can charge fees from the cardholder and create additional revenue streams.

More information here.

​

Balance write-offs  

Sometimes debt collection fails, and the issuer wants or needs to write off the debt either partially, or in full. The reasons for writing off debt range from customer bankruptcy or insolvency to fraud or even the death of the customer.

Writing off a card account debt happens through the Transaction API. The issuer will define the write-off amount (either full balance or partial balance) and they will have a full audit trail of the balance types that have been written off (principal, fees, interest). The information can be found in the Account Balance DWH files.

In case of a positive balance write-off, the write-off is done through a support ticket to Enfuce. Enfuce specialists will ensure that the write-off is done correctly.

Enfuce provides four different balance write-off transaction types (BWO1, BWO2, BWO3, BWO4), which the issuer can use to segregate the write-off reasons in their reporting. As the balances are written off, they are posted to specific Write-off GL accounts, which will allow the issuer to have the necessary data for bookkeeping. For regulatory reporting, more details can be added to the transaction’s text section, which will be then reflected in the DWH reports and can also be queried via transaction API. For example, in case only one transaction needs to be written off, the transaction ID can be inserted into the text section of the write-off.

More information here.

​

Institution id added in GL file naming 

To improve the differentiation of GL files, we have included the customer institution ID in the filename

​

Generate Account Statements in MyEnfuce

You can now generate PDF account statements directly from MyEnfuce for any account. This feature allows you to select a period of up to 3 months and include all transactions made during that time. These statements can be easily printed and used for bookkeeping or reporting purposes. To access this, simply navigate to the Actions menu on the account of your choice.

​

Generate Transaction Receipts in MyEnfuce

You can now generate and print PDF receipts for individual transactions directly in MyEnfuce. Each receipt allows you to add a custom description, which will be displayed on the receipt but not saved in the transaction details. This feature is perfect for customers who need proof or confirmation that a transaction has been processed. To access it, go to any posted transaction and find the option in the Actions menu.

​

Audit Logs in MyEnfuce

MyEnfuce now offers Audit Logs, providing a detailed chronological record of events and activities. Whether initiated through MyEnfuce or the Enfuce APIs, every action is captured with its associated requests and responses. This feature is available at the Customer, Card, Account, and Transactions level, accessible via the new “Audit” button. Audit Logs help customers maintain transparency and track every important event for compliance and internal reviews.

​

New Features

Write-offs enabled via API calls

It is common for issuers to write off a debt when debt collection fails. When a write-off is done and what rules it’s based on depends on issuer policy.

Card account debt write-offs can now be done through the Update Account API. This clears off all open balances from each technical balance account. The issuer will have a full audit trail of the balance types that have been written off (principal, fees, interest).

​

Improvements

Idempotency

Idempotency is an important feature of software systems such as card processing platforms. It ensures that executing a change or request multiple times has the same effect as executing it once. Idempotency makes it possible for a client to send multiple identical requests to an API without risking unwanted changes.

Idempotency ensures data consistency, avoids duplication of operations, and improves the fault tolerance of software systems. Overall, these updates further improve the reliability and resilience of Enfuce’s platform.

By default, HTTP methods such as GET and PUT are idempotent as the state on the server will be the same on a second attempt.

For HTTP methods POST and PATCH, we need to add features to ensure these methods also support idempotency. For example, two identical POST requests would create two different cards via the Enfuce API. The desired behaviour would be that only one card is created in such a scenario.

This is typically an issue when there is an issue on either the client or server side. It can also happen when there are network glitches and clients might not even receive a response back.

The solution is to make it possible to send a request a second time within a timeframe, without duplicating operations.

This feature applies to all POST and PATCH methods in our API:

• Create customer
• Update customer
• Create account
• Update account
• Create card
• Update card
• Update application
• Update plastic
• Create transactions
• Create fees

The API Documentation of this feature has been published in MyEnfuce’s Payment API documentation.

New Multi-country code classifier

We’ve added a new code to help identify country specific data to Enfuce’s Datawarehouse files. Card and Account Properties files will now include a MULTICOUNTRYCODE classifier to indicate which country specific data it is about. A description of this new field has been added to MyEnfuce Service Descriptions:

Account properties file

Card properties file

​

New Features

True instant issuing – Physical cards that can be used straight away

Instant issuing means that a payment card can be used instantly. This has always been the case with virtual cards, e.g., a virtual card can be enrolled to digital wallets and the credentials can be used for e-commerce purchases right away.

We’re now introducing an improvement that allows the same experience for issued physical cards as virtual cards which will enable the end users to enrol them to digital wallets and use them for ecommerce purchase instantly.

All-in-One card

The All-in-One card combines multiple PAN’s into one physical card, instead of having a separate card for each payment method. In practice, this product can combine things like lunch allowances, mobility cards and travel expense cards, making life easier for the cardholder since they will have just one card with one PIN code.

The issuer can set custom limits and controls to each of these card applications and make changes to them in real-time. They can also manage which card applications are enabled for the cardholder and add or remove them without having to issue a new physical card when changes are made.

Each card application is linked to its own account which holds the balance, so funds are always taken from the correct ledger.

Credit Ledger Improvements

As Enfuce expands to new markets, we’re enhancing our credit ledger functionalities to help customers build unique credit card products and achieve their business goals, as well as meet local regulatory requirements.

The second batch of improvements includes interest waiving capabilities as well as new minimum to pay calculation logic.

Interest-waiving after full payments

Enfuce has enabled an interest waiving option, if the cardholder pays the full invoiced amount. When full payment is received, revolving interest will not be posted to the account.

This can be also configured so that the system requires two full payments in a row, in order to prevent the interest posting. The feature enables the issuer to stay competitive in the market and encourages the cardholder to pay the full debt after each invoice and reduce the issuer’s credit risk.

New Minimum To Pay calculation logic available*

Enfuce credit ledger now supports two different minimum to pay calculation logics to meet different market requirements.

• Option 1 – the standard calculation logic option (EEA market):
  • % of the whole principal balance (containing interest and fees) + the amount of overdue balance
• Option 2 – the newly available calculation logic option (UK market):
  • Interest + fees + % of the principal balance + the amount of overdue balance

​

New Features

Account Hierarchy

Account hierarchies allow you to create a ranked structure for your corporate customers’ accounts, with a defined top account, unlimited sub-accounts, and associated Prepaid or Credit cards.

The hierarchy links the customer accounts for a, e.g., department, geographical area, or business area.

This feature allows you to set spend controls, credit limits, or, e.g, ATM withdrawal limits for the whole hierarchy at the top level, enabling customers to control spending, enforce budgets, and track balances effectively. The link between the accounts also allows you to block or close multiple cards at once when needed.

Read more about this new feature in the service descriptions.

Credit Ledger Improvements

As Enfuce expands to new markets, we’re enhancing our credit ledger functionalities to help customers build unique credit card products and achieve their business goals, as well as meet local regulatory requirements. The first batch of these improvements include different payment priorities and interest calculation logic options.

Payment priorities

When a credit account holder makes a payment, and it’s posted to Enfuce’s system, we have a logic for how that payment is allocated to different balance items such as overdue debt, invoiced debt, and current cycle debt. Further, it can be specified if, e.g., interest should be covered before fees. These priorities are usually set based on regulatory requirements.

Interest calculation improvements

There are multiple ways to calculate interest. We’ve added a few options to give customers more flexibility in defining their credit product:

Possibility to start accruing interest from transaction posting date Interest on interest, i.e. that interest balances also accrue interest.

Upcoming features

• Interest-waiving after full payments
• New Minimum To Pay calculation logic

Send files to multiple locations (SFTPs)

Enfuce sends data warehouse files daily. These files can be payment transaction data and other reports, statements, invoices, etc. Previously these files could only be sent to one location, but we have now implemented a solution to send files to multiple locations if necessary e.g., to our customer and a credit line partner.

Visa Address Verification Service (AVS)

Visa’s Address Verification Service allows card-not-present merchants to check cardholder’s billing address with the card issuer to increase security and protect against fraud. Enfuce offers this service to comply with mandatory card scheme rules in the UK.

An Address Verification request includes the billing address provided to the merchant by the cardholder (street address and/or zip or postal code). The request can be transmitted as part of an authorization request or an account verification. Enfuce checks the transmitted address information against the address information in our database and provides a result code to the merchant, indicating whether the address given by the cardholder is a match.

MyEnfuce search improvements

Previously, it was only possible to search with customerNumber, customerID, accountID and cardID in MyEnfuce. Now you can also search with and RegNumber (for example a SSN or business id), as well as free text to find entries by name.

The new free search has been made available as its own functionality, in addition to the previous filtered search. The new search functionality is now the landing page (default) of MyEnfuce customer portal, but the filtered search can still be accessed from the same page.

In addition to RegNumber, the following customer information can be searched with free text: First name, Middle name, Last name, Company name.

​

Fixed

Mac ID&V options

A risk assessment is done with every Apple Pay provisioning request. When necessary, the cardholder is presented with authentication (Identity and Verification, ID&V) options to verify their identity.

Apple has multiple methods available for Card Issuers to facilitate user ID&V. When doing the provisioning on a Mac computer, the only available ID&V was inbound Call centre. This has been fixed and multiple ID&V options can be presented.

Account API usage limiters

A bug in the Update Account API in regards to updating some of the account usage limiters has been fixed. Now all account usage limiters applicable for an institution are working as expected.

​

New Features

Authorisation Control feature for real time decision making

We’ve launched a new feature ‘Authorisation Control’ to support real time decision making at the moment of a payment authorisation request. With Authorisation Control, you can decline and approve transactions based on advanced rules and create cards with incredible details. See how this feature works.

Tokenisation of card to digital wallet messages available in Notification API

When a customer enrols a card to a digital wallet, the card’s information is tokenized by the card scheme for security reasons. We now have the capability to trigger a notification to the issuer to inform them that their customer has started enrolling their card to a digital wallet. The issuer can utilise these messages to get real-time information about digital wallet enrolments as well as proactively offer help to their customers if they see that enrolment has failed mid-process.

Enhancements in the embossing service to cater for laser printing

We now enable a wider variety of characters for cardholders’ names in physical cards. There are two ways to have a cardholder’s name on a physical payment card – embossed (i.e. stamped) and laser-printed. In addition to embossing, we’ve now adjusted our service to cater to laser printing, which offers more possibilities for printing characters on cards. For more information, contact Enfuce and your embossing house.

Usability improvements in the Developer Portal

The Developer Portal in MyEnfuce, where you can access our sandbox, API explorer and documentation, has received several upgrades. These include, but are not limited to, the possibility to navigate to the sandbox directly from the API explorer and the option to add more than one item in an array in our API explorer. You could use this to, for example, add multiple different usage limiters into one update call. If you’d like to see the improved portal, log in or create a free account here.

Better Customer Portal UI for MyEnfuce

MyEnfuce customer portal, which issuers can use to manage their cardholder data, has been refreshed with improved user interface that includes better navigation abilities.

MyEnfuce change log for keeping track of updates

MyEnfuce now features a change log that tracks all updates and improvements in the portal. The change log is updated monthly.

MyEnfuce Help for frequently asked questions

For all frequently asked questions, MyEnfuce has been updated with a Help section. Here you can find answers to all questions about Enfuce documentation, accessing the MyEnfuce portal and more.

New service documentations in MyEnfuce

MyEnfuce has been updated with new service descriptions. These include detailed descriptions for the Enfuce data export file, our revolving credit product, our sustainable physical card product MyCard, spend controls, authorisation control, Transfer API, MyApp and several compliance related service descriptions.

​

New Features

Full support for Visa* biometrics**

Enfuce has enabled support for processing transactions made with 2nd generation Visa biometric cards. Enfuce is now able to read and validate the biometric authentication in an authorisation message. Successful biometric authentication is considered comparable to PIN-entries, and transactions done with biometric authentication will be considered as strong as customer authenticated. This also means that biometric transactions will clear the PSD2 required calculator that keeps track of consecutive non-authenticated transactions.

* Visa is a registered trademark of Visa International Service Association

** Biometric card works through a sensor on the card that captures an image of the cardholder’s fingerprint, which is verified by a fingerprint record securely stored on the card chip. This is considered as a valid strong customer authentication method according to PSD2 regulation.

Transfer API

Enfuce now offers the Transfer API which supports peer-to-peer transfers between accounts and cards residing in Enfuce services. Now the issuer can offer convenient peer-to-peer payments between its customers without third parties or intermediaries. Transfer API supports both transfers between accounts as well as between cards. The transfer between accounts or cards is processed in real-time and the balance is also updated in real-time. The API also has a free text field that will allow messages or identifiers to be recorded for each transfer.

FX rate API v2 launch

Enfuce’s exchange rate API, developed to support issuers with the EU Cross border payment regulation, has been updated to meet the needs of issuers with varying mark-up rates. Additionally, we now have support also for Mastercard exchange rates. The new version of the API allows the issuer to set currency pairs of the exchange as well as define the applicable mark-up rate, allowing issuers that issue cards in multiple currencies and differing mark-up rates to use the same API endpoint for all customers.

MyApp (a white-label mobile app for card management) launch

Enfuce now offers a white-label app for Card-As-A-Service customers as a new value-added product. MyApp has all modern card management features as:

• Two-factor authentication
• Biometric or passcode authentication
• View PAN (Full Card Number) & View PIN
• Transaction history and detail
• Manage limits and region blocking on the card
• Temporary block and unblock the card
• Push notification per transaction
• Add to Apple Pay, Google Pay or Samsung Pay

Now Enfuce customers can launch their own branded mobile app on both iOS and Android platforms. Customers configure the features and design with the chosen branding style, then Enfuce supports the app publishing process together with a customer and makes sure the app stays compliant with all regulations.

​

Fixed

• Incorrect product code value appeared when listing cards for a given account.
• The Account API endpoint Get cards given accountId, incorrectly displayed the account product code in the “template” field when the expected value is the card product code.

​

New Features

Set PIN in Web view

The Set PIN functionality is improved and now requires less development work on the customer’s end. This is enabled by providing a ready-to-use WebView solution that takes care of all logic related to the PIN entry and transmission.

Layout enhancement to View Card Data

Enfuce has enabled the possibility to add customers’ own card design layout to View Card Data service. View card data enables users to view card data safely without access to digital wallets or their physical card.

Support for changes in the EU regulatory reporting

The European Central Bank payment statistics requirements have been revised. This means that annual reporting requirements are being expanded and that issuers need to report to their local regulators. Enfuce has reacted to these new requirements by ensuring the required information is in a downloadable format in the Enfuce Data export files. Enfuce has also implemented a new optional report that includes transaction level information about if strong customer authentication (SCA) has been done and if not, which PSD2 SCA exemption has been applied.

Helping customers move under their own BIN

Enfuce has enabled one of its BIN-sponsored Visa* customers to become a principal scheme member instead. Enfuce supports issuance, authorization processing (including 3DS-enrolment) and clearing of both BIN-sponsored cards and cards under a customer-owned BIN in parallel. This is done by segregating the relevant data flows and reporting functions between the BINs involved. Enfuce supports migrating to the new BIN by allowing cards of both BINs to coexist and by allowing balance transfers between those cards through Transaction API.

Multi-country improvements

Previously, expanding to a new country required setting up a new institution, which involved a lot of manual work and resources. Enfuce has re-designed the setup so that one institution can support products in multiple different countries/currencies while still enabling differentiation on country level. The implementation time and effort has been substantially reduced with the new approach. As a result of the new setup, Enfuce has helped its customers to expand to 8 new markets in the past 8 weeks.

SMS OTP for enrolling to Digital Wallets

Enfuce now supports the deliveries of one-time passwords (OTPs) through text messages to allow users to enroll for Digital Wallets such as Apple Pay or Google Pay. Enfuce has implemented the capabilities to support these flows end-to-end. This covers card scheme implementations as well as SMS gateways to deliver these codes to the users.

* Visa is a registered trademark of Visa International Service Association