Why eWallets Keep Reappearing on UK Fintech Roadmaps
A wallet changes the funds flow as well as the customer experience. Establish who issues or holds value, the providers involved and the applicable permissions. Remitz supplies wallet software, not e-money issuance or customer-funds custody.
The logic is also a trap for unprepared operators. An eWallet is not a bigger money transfer product; it is a different regulatory animal with its own capital requirements, safeguarding obligations, accounting treatment, and technology complexity. Buying white-label software is one part of the stack; understanding what you are building is the other.
This guide covers both — the feature requirements for eWallet software, and the regulatory and commercial context every UK buyer needs to understand before signing a contract.
What an eWallet Actually Is
The label “eWallet” does not determine the legal product. Have qualified advisers assess issuance, acceptance, redemption and funds flows before choosing software.
- Customers load funds and hold a balance
- That balance can be used for payments, transfers, or reconversion to cash
- The issuer is regulated as an Electronic Money Institution (EMI) — either fully authorised or small-EMI registered
- Customer funds must be safeguarded separately from the issuer's corporate funds
Remittance and e-money products can have different obligations. Neither an account label nor how long funds remain in a system determines the legal treatment.
Common UK eWallet Use Cases in 2026
Remittance-Adjacent Wallets
A send-and-receive wallet tied to a remittance product. Senders fund the wallet once, then make multiple transfers without re-funding each time. Receivers abroad can also receive into a wallet if the platform supports it. This is the most common entry-point for UK MTOs adding wallet capability.
Diaspora-Community Wallets
Wallets targeting specific immigrant communities in the UK, often paired with services the community uses — money transfer home, airtime top-up, bill payment, international calling credit. The wallet becomes the central financial-service interface.
Employer-Payroll Wallets
Employers paying migrant or gig workers into wallets that customers can then spend, send home, or withdraw. Growing use case as gig platforms scale internationally.
Merchant-Ecosystem Wallets
Wallets paired with a merchant-acceptance network — customers load, pay merchants from the wallet. Common in Southeast Asia and Africa; less common in UK outbound remittance unless paired with specific community networks.
Regulatory Perimeter: The Decision That Shapes Everything
The single most important early decision: which regulatory perimeter covers your wallet?
Option A: Payment Institution (SPI/API) Perimeter
A payment-institution arrangement needs to be assessed against the proposed service. A short holding period does not establish that it covers the product.
This is simpler, cheaper, and faster to authorise, but commercially restricted — your customers cannot genuinely "store" funds for future use.
Option B: Electronic Money Institution (Small EMI)
Small EMI eligibility involves average outstanding e-money, not a €5 million monthly payment-volume allowance. Other conditions apply. Check the FCA’s current applicant guidance with your advisers.
Option C: Electronic Money Institution (Authorised)
Authorised EMI capital and ongoing own-funds requirements require a service-specific assessment. Do not substitute a single percentage of wallet balances for the applicable rules.
Choosing Between Them
The choice comes down to product design:
- Document how value is issued, accepted, redeemed and held
- Identify the entity performing each regulated service
- Assess customer-to-customer transfers against the actual funds flow
- Assess card-issuing partners and responsibilities separately
Choose permissions through a documented product assessment. Remitz supplies technology, not regulatory authorisation or legal advice.
Core Feature Requirements for White-Label eWallet Software
Multi-Currency Wallet Balances
Customers should be able to hold balances in multiple currencies — typically GBP plus one or two currencies relevant to their remittance corridors. Internal FX conversions happen at the platform's mid-market rate plus your configured margin.
Fund Loading
- Debit card (3DS 2.x, with SCA)
- Credit card (where supported by acquirer and agreed with compliance on AML risk)
- Bank transfer (Faster Payments, SEPA, SWIFT)
- Open Banking (account-to-account, typically lowest-cost)
- Cash at partner agents (for agent-network MTOs)
- Wallet-to-wallet (for platforms supporting P2P)
Outbound Transactions
- International remittance (the classic use case)
- Peer-to-peer transfer (within the platform)
- Bill payment (where partner integrations exist)
- Withdrawal to bank account
- Airtime top-up
Compliance Workflows
- KYC and EDD for wallet onboarding — deeper than a one-off remittance because the customer holds funds with you
- Sanctions and PEP screening on every outbound transaction
- AML transaction monitoring with wallet-specific typologies (structuring, layering, rapid in-and-out patterns)
- Customer-fund safeguarding — segregated accounts, daily reconciliation
- SAR filing workflow with MLRO dashboard
Customer Experience
- Branded mobile app (iOS + Android) under your App Store and Google Play accounts
- Web portal as a fallback / complement
- Transactional email and SMS with full white-labelling
- Push notifications
- In-app customer support
Back Office
- Transaction reconciliation across wallet balances, safeguarded accounts, and payment rails
- Regulatory reporting (FCA annual return, HMRC SAR volumes)
- BI dashboards (active customer count, AUM, transaction frequency, revenue per customer)
- Customer support tools (ability to view account, transaction history, freeze, reverse)
- Audit trail across every compliance decision and transaction
What to Look for in a White-Label eWallet Vendor
Regulatory Alignment
Does the platform explicitly support both SPI/API and EMI regulatory models? Some vendors only support payment-institution flows and expect you to bolt safeguarding on externally. Others are EMI-native and more expensive than an MTO needs.
Customer-Fund Safeguarding
Safeguarding duties depend on the institution and activity. Additional FCA rules took effect on 7 May 2026; SPIs may opt in. Review current requirements with your advisers. Remitz does not supply safeguarding accounts or a safeguarding reconciliation service.
Wallet-Specific Compliance
AML monitoring rules designed for stored-value patterns — not just single-transaction remittance patterns. Wallet-specific typologies include rapid load-and-send patterns, structured loads below KYC thresholds, and peer-to-peer networks used for value transfer.
Multi-Currency Without Surprises
Real multi-currency support means the platform can hold, convert, display, and reconcile balances across currencies without performance issues. Test this explicitly — some platforms support "multi-currency" at the UI layer but settle in a single base currency behind the scenes, creating FX friction.
Open Banking and Funding Flexibility
Compare actual fees, customer coverage, confirmation times, refunds and fraud exposure. No funding method is always cheapest.
White-Label Depth
Same questions as any white-label software decision — custom domain, app-store accounts, email templates, receipts, back-office branding. For wallets the customer relationship is deeper (they trust you with stored funds) so white-label depth matters more.
Pricing Models for White-Label eWallet Software
Common pricing structures in the 2026 market:
- Flat subscription — monthly fee covers the platform. Revenue-side economics sit entirely with the operator. Remitz's eWallet module sits inside the Growth plan (£799/month) on this model.
- Per-active-user — priced per monthly active wallet. Lower upfront but scales with your success, which can be good or bad depending on unit economics.
- Per-transaction — priced per wallet transaction. Tends to be expensive at scale.
- Revenue share — vendor takes a cut of your FX, payment, or service revenue. Common with higher-end EMI-grade vendors, aligning their incentive with yours but reducing your margin.
Evaluate total cost at your expected 3-year scale — not at today's activity level.
Integration Considerations
Safeguarded Bank Account
You need a UK bank willing to hold safeguarded customer funds. Not every UK bank offers this — some only serve established EMIs. Lining up a safeguarding bank is often the first gate in a realistic wallet launch.
Fund-Loading Integrations
Card acquirer (for card loads), Open Banking provider, bank-transfer rails, and possibly a cash-in partner for agent-network operators.
KYC Provider
Define customer due-diligence requirements with your compliance team and verification provider, based on the product and risk assessment.
Outbound Payout Network
Same payout partners as a remittance product, but the wallet needs to support multiple outbound methods from the same customer account.
Compliance Tooling
Confirm the monitoring rules, screening services, review queues and audit outputs for your implementation. Checks use your provider relationships; regulatory decisions remain yours.
Card Issuance (if relevant)
If your wallet issues cards, you need a card-issuing partner (BIN sponsor) and scheme membership. Meaningful additional complexity; not worth adding to a first launch unless core to the proposition.
Common Pitfalls in eWallet Launches
- Misaligned regulatory perimeter — operating a stored-value wallet under a PI licence that does not cover it
- Weak safeguarding discipline — daily reconciliation drift on safeguarded accounts, which the FCA takes very seriously
- Under-scoped AML rules — wallet-specific typologies missed because rules were ported from a remittance product
- Inadequate customer support — wallet customers expect faster responses than remittance customers because they trust you with their money balance
- Multi-currency illusion — UI appears multi-currency but settlement is single-currency, creating FX friction at reconciliation
- Unfunded marketing — wallets need customer acquisition to reach break-even; a small user base on a high-fixed-cost platform is a slow bleed
Remitz's White-Label eWallet Module
Growth includes the eWallet module at £799/month plus £2,000 setup. It is software, not an e-money licence, account or safeguarding service. Validate the following requirements against your agreed scope:
- Multi-currency wallet balances
- Fund loading via card, bank transfer, Open Banking
- Peer-to-peer transfers within the platform
- Outbound remittance integrated with the corridor payout network
- Compliance workflows and third-party checks to validate
- Available ledger records and exports for your own reconciliation process
- White-label branding across portal, mobile app, emails, receipts
- Back-office reconciliation and reporting
See the eWallet module page for feature-level detail, or explore the full platform features.
Deciding Next Steps
If you are considering an eWallet launch in 2026:
- Obtain advice on the regulatory perimeter before committing to the wallet design
- Identify your safeguarding bank partner early
- Evaluate vendors using a feature-and-compliance matrix (not just pricing)
- Model 3-year unit economics including safeguarding costs, permitted revenue sources and user acquisition
- Start with a narrow customer segment and expand, rather than launching broad
Explore the sandbox or book a 15-minute demo to see the Remitz eWallet module live, or read the vendor comparison framework for a broader evaluation methodology.
