Who Enfuce is
Enfuce is a cloud-native issuer processor founded in 2016 and headquartered in Helsinki, with hubs in London and Mariehamn. It designs, launches and runs card programmes for its clients, under an e-money licence from the Finnish FIN-FSA passported across the EEA, with its UK business authorised separately by the FCA.
It is a principal member of Visa and Mastercard, so it can be your BIN sponsor as well as your processor, for debit, credit and prepaid cards that are virtual, tokenised or physical. It is privately held, backed by Vitruvian Partners, Maki.vc, Tencent and Visa, and it is one of the issuer processors our card issuing module connects to.
What it does in your platform
Card issuing
Issues your cards under its own licence and network membership, in the EEA and the UK, and sends each authorisation to the module through Authorisation Control, so the answer comes from your ledger, the customer's limits and your fraud rules. Disputes go to Enfuce, which runs the chargeback with Visa or Mastercard.
How the connection works
The card issuing module manages cards through Enfuce's API, answers its Authorisation Control requests and receives its notifications, all from your platform.
A card is issued
When a customer passes KYC, the module creates the card on Enfuce, virtual and ready for wallets at once, with the physical card to follow.
Into the wallet
From your app, the customer adds the card to Apple Pay or Google Pay through Enfuce's push provisioning API.
Enfuce asks the module
When the customer pays, Enfuce sends the authorisation to the module and expects an answer within one second of sending it.
The module decides
It checks the ledger, the limits and your rules, and answers with an approval or a decline code.
If the module is unreachable
Enfuce approves on its own checks, or declines when a critical check could not run, so a payment never waits on an outage.
Notifications follow
Transaction and card events arrive as notifications, and the module posts each one to the ledger.
Next to other processors
Enfuce is one of several issuer processors in the card issuing module. The card screens, the controls and the ledger belong to the module, so they work the same on Enfuce as on Marqeta, Thredd or Paymentology.
Because Enfuce can be sponsor and processor at once in Europe, you deal with one company for both. If you move the programme later, it is a migration you plan with Enfuce and the network; your apps stay the same, and past transactions stay in your ledger.
When Enfuce fits best
A strong fit when
- Your cards are for customers in the EEA or the UK.
- You want BIN sponsorship and processing from one licensed company.
- You want spend controls by merchant category, merchant country and amount, with high-risk categories blocked by default.
Also worth a look
- A processor that works with your own BIN sponsor, if you already have one.
- A processor you already have a contract with: it becomes a connector too.
How we get you live
The contract
We help you get your Enfuce contract in place, with Enfuce as both BIN sponsor and processor for your programme.
The card programme
We set up the programme with you: card types and designs, spend controls, 3-D Secure, wallets and how Authorisation Control answers.
The keys
API credentials and the credentials of the notification endpoint go into your platform's secrets and nowhere else.
A full test run
The whole flow runs in Enfuce's demo environment, whose test API simulates authorisations from the card schemes, before your first real card.
