#topbar-cta-button span {
  background-color: #ffdc10;
  color: #121132;
}

#content-area p > a,
#content-area li > a {
  color: #8937ef;
  font-weight: 400;
  border-bottom: 1px solid #8937ef;
}

#content-area a:has(.icon) {
  border-bottom: none;
  color: #121132;
}

th.top {
  vertical-align: top;
}

/*
Needs more effort to work properly.
Does not work nicely with changing theme via button.

#navbar a:nth-of-type(1) {
    color: #121132;

@media (prefers-color-scheme: dark) {
    #navbar a:nth-of-type(1) {
        color: #FFFFFF;
    }
}
*/


Close an existing instalment plan

basicAuth

Enfuce

Get to know Enfuce's award-winning payments solution by catching up on all our documentation and guides. Welcome to the land of absolute transparency.

Enfuce Documentation

First of all, nice to meet you! Here’s a short introduction to get to know us better

Quick guide to Enfuce

Congratulations on taking the first step to building flexible, modern payment cards! You are probably eager to get going and start creating your card product.

Start developing with Enfuce

Enfuce License Services (ELS) is the licensed Enfuce group entity offering BIN sponsorship and card issuance in the EEA area under our EMI authorisation from the FIN-FSA, passported to the EEA.

BIN sponsorship

3-D Secure is designed to increase consumer confidence in online payments by providing additional authentication of the customer during the purchase process.

3DS – authentication of online payments

We value collaboration with several trusted partners from both commercial and product perspectives.

Partnerships

Enfuce offers comprehensive support throughout your lifecycle as a customer.

Customer success

Enfuce’s MyApp is a ready-to-launch mobile application (app) that lets you launch your card products with a branded card management app without binding internal development resources.

MyApp – Cardholder app

If you wish to issue physical cards with your own design, it usually takes months with time-consuming steps like:"

MyCard – Embedded card bureau

Here you'll find documentation about Payment API.

Overview

Endpoint for doing various actions connected to a account

Account Details

Authorisation control gives the issuer the flexibility to create sophisticated rules for approving and declining transactions in real time.

Authorisation Control

Authorisation Forwarding

Card API have different endpoints for creating, editing and updating a card via different methods.

Card details

Endpoint for doing various actions connected to the customer domain

Customer details API

Endpoint for querying FX rates of payment scheme (including benchmark to ECB FX rates). API enables the issuer to comply with regulation (EU) 2019/518) and provide the cardholder with a better user experience by providing real-time visibility to scheme FX rates that are used for card transactions.

Exchange Rates API

Endpoint for handling 3rd party authentication

Enfuce ID

Instalment API

Endpoint for doing doing operations on a invoice

Invoice API

Endpoint for retrieving notifications for various entities from Enfuce system

Enfuce API - Notification

Card PIN API

Endpoint for managing an access token used to view or set PIN. This is a PCI DSS Category 2 service.

Card PIN Control API

Purchase Details API

RBA Forwarding V1

Repricing API

Transaction details API

Batch payment

Transfer API

Wallet API enables getting needed data for tokenization and enablement in programs like Apple Pay and Google Pay.

Wallet operations

This API is only available in DEMO environment and intended solely for testing purposes.

Test API

Card hierarchy defines a tree-structure that separates card space in non-intersecting groups. Such groups can be further used for ruleset attachments via Spend Control API.

Hierarchy API

Spend Control API

Release Notes

Platform

Payment API

Contact

Sign in

Enfuce offers several options for the interest calculation.

Revolving credit product – Interest accrual

Enfuce credit product has also an instalment feature, which can be separately configured.

Revolving credit product – Instalments

The Enfuce credit account product has several technical accounts that enable the segregation of balances. This, in turn, allows you to keep track of the age of overdue amounts and a variety of interest calculation models.

Revolving credit product – Segregation of balances

Enfuce provides the issuer invoice data (“statement”) on account level once per month. You can use the provided data for creating and sending invoices to your customers.

Revolving credit product – Invoicing process

Revolving credit product – Customer Payments

Revolving credit product – Reminder and collection process

Our customer portal, known also as MyEnfuce, gives you access to your cardholder information.

MyEnfuce customer portal – your access to cardholder data

Registration and login

All transactions have one common characteristic. They are designed to either increase or decrease the account balance. The term ‘transaction’ includes all transaction-related communication between the merchant, an issuing processor and the issuer.

Introduction to transactions

Transaction conditions describe the particular conditions in which a card transaction was made, for example, was the chip read or was it contactless, how was the cardholder authenticated and was it e-commerce or a card present transaction.

Transaction conditions

An authorisation refers to the merchant obtaining approval or denial of a card transaction from the issuer. The authorisation process starts when a customer makes a purchase.

Authorisation and authentication of payments

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

Discounts

A financial transaction is defined as a transaction that either increases or decreases the account balance. This section will describe both card scheme transactions that are posted when cards are used at merchants and API triggered transactions that can be posted via Enfuce APIs.

Financial transaction

There may be situations when you need to be able to link authorisations or notifications of authorisations with financial transactions. For example, some issuers send a notification to their customer after an authorisation, requesting the customer to take an action based on it (like take a picture of the receipt or assign it to a cost category).

Linking authorisation with transaction

This API allows you to do peer-to-peer transfers between accounts and cards residing in Enfuce.

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, it lacks detailed data about what was bought.

Purchase details

A card serves as the actual payment instrument. Cards can take many forms: They can be plastic, virtual or tokenised elements that work though a variety of devices, like smart watches, mobile phones and rings. 

Card

Disposable cards can have many use cases for private and corporate customers.

Disposable card – time-based closing

A card as a payment instrument can take many forms nowadays, virtual, tokenised, and physical one. A modern issuer needs to be able to support these multiple representations of cards, as well as manage the varying preferences of their end users.

Digital card – creating the omnichannel payment card experience

A customer is the entity to which a card and/or an account is issued to. A customer can be a private person, a corporate customer, or even an item, like a vehicle.

Customer

The All-in-One card combines multiple card applications (PANs) into one physical card.

All-in-One card

The account entity’s main functionality is to hold the balance. It also functions as the link in case several cards share the same balance. For credit products, the account also represents the invoice level from which invoices are generated.

Account

Depending on your needs and the agreed setup between Enfuce and yourself, there are different types of account products.

Account product types

Account hierarchies allow you to create a hierarchical structure of your corporate customer accounts.

Account hierarchy

Balance types are used to improve the financial information that is provided in the data export files.

Balance types

A great cardholder experience is at the centre of what Enfuce does. This includes giving cardholders the ability to manage their cards themselves.

Introduction to our APIs

The Enfuce data approach is based on a generic solution that is designed to fit different types of payment products (credit, debit, consumer, corporate, fleet cards, etc.).

Enfuce interfaces and data sharing

Visa Click to Pay

‘View card data’ allows the cardholder to safely and conveniently access the data required for making an e-commerce purchase, without having access to a digital wallet or a physical card.

View card data

The ‘view PIN’ functionality allows your customer to safely and conveniently access their card’s PIN via a mobile or web app when needed.

View PIN

Set PIN allows the customer to choose the PIN (Personal Identification Number) of the card. This can be done safely and conveniently through mobile or web app.

Allowing the cardholder to choose a PIN of their choice improves the end-user experience as it reduces the burden of remembering multiple PINs and decreases the amount of failed transactions as well as requests for resetting the PIN attempts.

Change PIN

Authorisation control gives you the flexibility to create sophisticated rules for approving and declining transactions in real time.

Authorisation control

Have full control over where your cards can be used, in what way, how much, and when.

Advanced spend controls

Enfuce supports a range of spend controls that are used to provide the customer with the possibility to control the use of the card and improve trust and a sense of safety.

Spend controls

Data export files are a set of files which are exported from the Enfuce data warehouse for the issuer.

Enfuce data export files

Token file description

Account file description

Customer file descriptions

Card file description

Transaction file description

Lead the charge towards a sustainable future. Transform your digital banking services with cutting-edge carbon data and engaging experiences with Deedster.

Carbon footprint tracking: Enfuce x Deedster

To comply with EU Cross Border Payment regulation (EU 2021/1230) and to enable improved end user experience, Enfuce provides a solution to disclose to the end user the exchange rates used for card payments.

Cross-border payment regulation (CBPR)

The EU Payment Service Directive includes multiple requirements that have to be considered by payment issuers.

Payment Service Directive (PSD)

We develop and maintain all our services keeping in mind best practices for security and data protection.

The European Union’s General Data Protection Regulation (Regulation (EU) 2016/679) regulates the processing of personal data, which applies to financial data processed by Issuers of payment instruments.

Privacy and data protection

Transaction-specific strong customer authentication (SCA) data

The card schemes’ address verification service allows card-not-present merchants to check the cardholder’s billing address with the card issuer to increase security and protect against fraud.

Address verification service

Dispute management includes the initiation and management of your customers’ payment disputes.

Dispute management

Managing fraud is essential in ensuring continuous customer trust in any payment solution.

Fraud prevention

Create an account

This operation will create a credit account

Create credit account

This operation will create a debit account

Create debit account

This operation will create a prepaid account

Create prepaid account

This operation will create a fleet account

Create fleet account

This operation will create a multicurrency account

Create a multi-currency account

Create account (Deprecated)

Create account

This operation will update given fields given an account id

Update a credit account

This operation will update given reminder data fields given an account id

Update a credit account reminder data

Update a debit account

Update a prepaid account

Update a fleet account

Update a multicurrency account

Update an account (Deprecated)

Update an account

Basic operation for updating an account. Check parameter updateProperty for possible parameters to update

Update account

Get account information

This operation will respond with an account given account id

Get account

This operation will respond with an account given account number

Get account by accountNumber

This operation will respond with a list of accounts given the customer id

Get accounts given customerId

This operation will respond with a list of accounts given the account id

Get accounts lower in the hierarchy

Get account (Deprecated)

Get accounts given customerId (Deprecated)

Authorisation Control Webhook

This is not an endpoint. This is the description of a request that is sent to issuers' decision-making systems

Outgoing authorisation control webhook endpoint

Forward authorisation webhook

This is not an endpoint. This is the description of request the which is being sent to customers decision making system if provided

Request which is being send to customers decision making systems

Create card

This operation will create a credit or prepaid card media connected to given customer. An account id needs to be provided as well so we know to which account the card should be connected to.

Create a Multi-application card

Create a MasterCard branded card

Create a virtual Mastercard branded card

This operation will create an debit card media connected to given customer. An account id needs to be provided as well so we know to which account the card should be connected to.

Create a debit Mastercard branded card

This operation will create a debit card media connected to given customer. An account id needs to be provided as well so we know to which account the card should be connected to.

Payment API

Account Details

Authorisation Control

Authorisation Forwarding

Card details

Customer

Exchange Rates API

ID

Instalment

Invoice

Notification

PIN

PIN Control

Purchase Details

RBA Forwarding

Repricing

Transaction

Transfer API

Wallet

Test API

Hierarchy API

Spend Control API

Close an existing instalment plan

Authorizations

Query Parameters

Body