Enfuce FAQs: pricing, onboarding, security and integrations.

Yes. A bank keeps its own ledger and uses Enfuce for the processing layer underneath — authorisations, clearing, spend controls and transaction data, while the balances stay in its core. Enfuce runs issuer processing, processing on the bank's own licence, or authorisation only on top of the bank's ledger.

A modular ledger means one infrastructure carrying structures that usually need separate systems, Multi-PAN, multi-application and multi-wallet cards across prepaid, charge and revolving credit, with separate balances per account. Interest, fees, billing and repayment logic, including instalments and BNPL, are configured per programme type rather than one fixed model.

Modular spend controls apply rules at authorisation, set by merchant, category, vehicle, driver or budget and mapped to commercial, fleet or employee-benefit programmes, adjusting in real time without reissuing. Because ledger and controls sit on one base, a fleet ledger, credit card and multi-benefit card all run from one platform.

Enfuce holds the regulated foundation, so a card programme launches on compliance already in place. As a dual-regulated EMI authorised by the UK FCA and Finnish FSA, principal member of Visa and Mastercard, and PCI DSS Level 1 certified, Enfuce carries the licensing, scheme membership and security otherwise built in-house.

Compliance sits in the core, built in by design rather than layered on top. Onboarding, KYC and KYB, transaction monitoring, audit trails and fraud intelligence come embedded, covering PSD2, AML, GDPR and DORA. Scheme reporting, settlement, prefunding, safeguarding and dispute handling are managed at Enfuce's level as the regulated counterparty.

The foundation scales as the programme grows. Scheme updates, audit requirements and regulatory change are tracked and communicated, so a fintech or corporate stays aligned across markets and volumes, with capital and team focus freed for the product itself.

Enfuce aligns its go-to-market, product and delivery teams by vertical, Banking & Financial Services, Fleet Fuel & Mobility, Employee Benefits and Expense Management, each with infrastructure pre-configured for the programmes it runs, from fleet payments to employee benefits to corporate spend.

Fleet and mobility programmes run on line-item transaction data, vehicle and driver ID, category-level tagging and controls applied at authorisation, arriving in real time in a consistent structure ready to act on. 

Employee-benefit programmes run on Multi-PAN, separating each benefit type into its own balance and ledger under one card. The controls and data are built for those use cases rather than added as a generic layer.

The proof sits across the verticals, Avida in banking, Octopus Electroverse in fleet and mobility, Swile in employee benefits, Pleo in expense management, each a programme built on the infrastructure aligned to it.

Enfuce prices each programme from three consistent fees, a one-time implementation fee to set it up, a fixed monthly service fee for the core services that keep it running, and a volume-based fee that follows active cards and usage. 

Add-ons like BIN sponsorship, digital wallets, advanced spend controls or physical cards are priced only where they apply. Each programme is scoped to its own structure, scale and needs before you sign. 

Enfuce is a principal member of both Visa and Mastercard, and has been since 2017. That scheme-agnostic position lets a programme structure across either network or both, with Enfuce managing scheme membership, certification, reporting and settlement as the regulated counterparty.

For customers, one scheme relationship covers both networks, programmes issue Visa or Mastercard cards, migrate between schemes, and expand across the UK and EEA on the same footing. Enfuce has run scheme-to-scheme migrations at scale, including Pixpay's move from Mastercard to Visa across France, Spain, Italy and Germany.

A card-issuing API connects your product directly to regulated payment infrastructure, so card issuance, controls and lifecycle management sit inside your own systems and workflows. Through API requests you create customers, accounts and cards, apply authorisation rules, configure spend controls, enable digital wallets, and receive transaction data and notifications in real time.

With Enfuce's API, you issue physical, virtual and tokenised cards, single- or multi-use, across prepaid, debit and credit, as Visa or Mastercard cards. Each card can carry real-time spend controls, support multiple currencies, and work online, in-store or through digital wallets like Apple Pay and Google Pay.

A card-issuing API covers the issuance step. Enfuce's issuer processor API goes further, running the full card lifecycle, authorisation, clearing, settlement and lifecycle events, through the same integration, so a programme scales on one system.

Both terms describe the same underlying design: infrastructure built to scale in the public cloud and to change without re-platforming. In practice that means real-time processing rather than overnight batches, an event-driven ledger, and a modular stack where components can be added or swapped over time. 

Developer tooling comes as standard documented APIs, webhooks, versioning and a sandbox to build against before going live.

The practical test is behaviour, not labels. A buyer can check whether spend controls and rules update instantly or wait on a release cycle, whether transactions are processed and streamed in real time, and how the system holds up during a partial outage. 

Stand-in processing and tenant isolation are two signals worth asking about, one keeps authorisations running if part of the system is unavailable, the other keeps one customer's traffic or incident from affecting another.

Enfuce runs on this design – an API-first platform on AWS with 99.999% uptime, real-time processing, and modular architecture where services evolve independently, so a programme adds products, markets and regulatory updates without major system overhauls.

Launch timelines depend on the programme, the use case, the number of markets, the card products and integrations involved, and whether it's a new build or a migration from an existing provider. A clear view of those upfront is what sets the pace.

Working with a BIN sponsor removes the single biggest time sink. Obtaining your own EMI licence and scheme membership can take months, sometimes close to a year, of approvals and certifications. 

With Enfuce holding the licence, principal scheme membership and processing infrastructure, that stage is already in place, so the work is scoping, configuring and integrating your programme. A structured onboarding framework, full API specs and a sandbox environment let developers build and test against the platform before go-live.

For migrations, a phased approach keeps the timeline predictable and the programme running throughout. New infrastructure runs alongside legacy systems during transition, and the track record is there, Enfuce and Avida migrated 500,000+ card customers from Santander in under seven months, with no service interruption.

CaaS lets a business issue branded payment cards by integrating with an issuing and processing platform via APIs. The provider supplies the regulatory foundation, a licence to safeguard and transfer cardholder funds, and scheme membership with networks like Visa and Mastercard, plus the technical infrastructure to bring cards to market.

The business designs and configures the programme to its specifications. The provider handles compliance, card issuance, and the authorisation, clearing, settlement and processing behind each transaction. 

Cards can be virtual, physical or in a digital wallet, across prepaid, debit, credit and specialised types, configured with the spend controls and data the programme needs.

The model fits different starting points. A non-financial company issues cards compliantly under the provider's licence and scheme membership, with no need to become a regulated issuer itself. A licensed institution launches a new product or enters a new market on the platform while its existing infrastructure runs as-is, and can consolidate more of its portfolio onto one system over time.

An issuer processor runs the technical infrastructure behind a card programme, card issuance, authorisation decisioning, clearing, settlement, transaction processing and lifecycle events, along with the spend controls and data that sit on top. It's the layer that makes each transaction run.

A programme manager runs the card product as a commercial proposition, designing the programme, onboarding and serving cardholders, and coordinating the partners behind it, including the issuer processor and BIN sponsor. It's the layer between the end customer and the infrastructure.

The two roles can sit with one provider or split across several. A business can act as its own programme manager and buy processing alone, or take both from the same partner. Consolidating them reduces the number of vendors to coordinate and keeps ownership clear. 

With Enfuce, issuer processing, programme management and BIN sponsorship can run under one roof rather than being stitched together across providers.

BIN sponsorship covers everything a card programme needs to operate compliantly without the partner holding its own licence or scheme membership. At its core that's two things: the regulatory licence to hold and move cardholder funds, and principal scheme membership to issue Visa or Mastercard cards on the networks' rails.

Around that sit the operational services the sponsor runs on the programme's behalf:

• Scheme reporting and settlement – all reporting obligations to the schemes, and settlement of transactions.
• Prefunding and safeguarding – cardholder funds held in segregated accounts under the EMI licence, with prefunding to cover scheme fees and settlement exposure.
• Regulatory and compliance oversight – the sponsor holds the licence and scheme membership, so it's accountable for compliance on both fronts.
• Operational support – fraud monitoring, dispute management and chargeback handling, where the sponsor offers them.

Coverage varies by sponsor. Some provide licensing and scheme access only; others, Enfuce among them, combine that with processing, compliance oversight and operational services, so the regulated foundation and the platform run from one place.

Enfuce is a dual-regulated EMI, authorised by the UK Financial Conduct Authority (FCA) and the Finnish Financial Supervisory Authority (Finnish FSA). 

The Finnish licence is passportable across the EEA, and the UK licence covers the UK as a separate market, so one partnership covers card issuing across the UK and EEA on a single platform.

The two apply differently by design. Within the EEA, a licence issued in one member state passports to the others, so the Finnish licence covers the region. The UK sits outside the EEA and requires its own licence, which not every EEA-based provider holds. 

Holding both means a programme launches across the UK and EEA without running parallel regulatory setups in each market.

An EMI licence is a company's own authorisation to hold and move cardholder funds. With its own scheme membership, the company is the regulated issuer itself, full control over payments and customer funds, and full ownership of the obligations: compliance, capital reserves, scheme reporting and the collateral scheme members hold.

BIN sponsorship is access to someone else's. A licensed partner that already holds the EMI licence and scheme membership lets a company issue cards under its regulatory foundation. The partner carries the licence, the scheme accountability and the compliance layer, the company owns the brand, the product and the customer.

The choice is control versus speed and overhead. Holding your own licence gives maximum independence but takes months, sometimes close to a year, of approvals and certifications, plus the capital and in-house expertise to maintain it.

BIN sponsorship gets a programme to market faster and frees that capital for the product, within the sponsor's commercial and governance framework. Some companies start with sponsorship and move to their own licence as they scale, the two are stages on a path, not just alternatives.

It depends on four things: your growth stage, your appetite for regulatory ownership, how much direct control you need over payments, and how fast you want to launch.

An EMI licence suits companies that scale across multiple markets, need to hold customer funds directly, treat payments as a core revenue stream, and can absorb a 12–18 month approval timeline and ongoing capital reserves. In return: full control over product design, pricing and interchange economics, a stronger position as a financial services provider.

BIN sponsorship suits companies that want to launch fast, treat payments as enabling infrastructure than the differentiator. A licensed partner holds the licence, scheme membership and compliance layer, and runs the regulated operations. Your team stays focused on the product, the customer experience and growth. 

With a partner like Enfuce, that means BIN sponsorship, processing and compliance from one place across the UK and EEA, with the room to add products and markets as you grow.

A hybrid path starts on BIN sponsorship to launch and validate demand, then take on more ownership over time, up to a licence of your own, as scale, internal expertise and revenue opportunities justify it. Building on scalable infrastructure from the start avoids re-platforming later. 

The real question underneath is where you want your differentiation to live: in the payment rails themselves, or in the product built on top of them and a partner that carries the rails lets you put that focus on the product from day one.

Yes. Many companies begin with BIN sponsorship to validate the payment proposition and launch fast, then take on more ownership as they scale, build internal compliance expertise and identify stronger revenue opportunities, a phased path rather than an all-or-nothing decision.

What makes the move practical is starting on infrastructure built to scale. When the programme runs on the same modular platform throughout, taking on more of the regulated layer, up to your own EMI licence, is a change in ownership, not a rebuild. The card products, controls and data carry forward, so the shift happens without disrupting what's already live.