- Why stored value changes the discussion
- The wallet features that usually need closer review
- SVF is a heavier route because customer float becomes central
- Float management is a real operating obligation
- Redemption changes the product design
- Float cannot become the main income engine
- Partner first may be better for early wallet validation
- When direct SVF planning becomes necessary
- Overseas and UK fintechs need to be careful
- Common founder mistakes
- Practical conclusion
A wallet can look simple from the product side. A user tops up, sees a balance, spends later, transfers value, receives rewards, or keeps money inside an app for a specific use case. For a founder, this may feel like a normal fintech feature. In the UAE, that design choice can change the regulatory map completely.
The key question is whether the product only helps money move, or whether it stores value for later use. If value is stored, the product may move into the Central Bank of the UAE’s Stored Value Facilities framework. That can bring a heavier capital, float management, governance, and operational burden than a narrower retail payment services model.
At Finamp, we treat stored value as one of the most important early discovery points for UAE market entry. It affects the route a fintech chooses, the type of partner it needs, the capital model behind the product, and the long-term decision between partner-led launch and direct licensing. A wallet is rarely just a front-end feature. In the UAE, it may become the centre of the regulatory analysis.
Why stored value changes the discussion
The UAE payment framework is product-based. A fintech first needs to understand what the product actually does: does it issue a payment account, issue a payment instrument, aggregate payments, acquire merchants, transfer funds, initiate payments, access account information, use payment tokens, or store value for future use?
This distinction matters because the UAE’s Retail Payment Services and Card Schemes Regulation, or RPSCS Regulation, covers digital retail payment services such as payment account issuance, payment instrument issuance, merchant acquiring, payment aggregation, domestic and cross-border fund transfer, payment token services, payment initiation, and payment account information services. However, the same regulation expressly excludes payment transactions involving Stored Value Facilities from its scope. That is why a wallet product cannot be assessed only as a normal payment services product if customer value is being stored. (Retail Payment Services and Card Schemes Regulation)
The Stored Value Facilities Regulation defines a Stored Value Facility as a non-cash facility where a customer, or another person on the customer’s behalf, pays money or money’s worth to the issuer in exchange for storage of that value and a relevant undertaking. The definition expressly refers to money’s worth such as values, reward points, crypto-assets, or virtual assets, and includes both device-based and non-device-based stored value facilities.(SVF Regulation)
For founders, this creates a practical rule of thumb: if the product lets users hold value inside the product and use it later, stored value analysis should happen early. The label used in the product interface does not decide the issue. “Wallet”, “balance”, “credits”, “points”, “voucher”, “prepaid account”, or “stored funds” may all require closer review if they perform the function of stored value.
The wallet features that usually need closer review
A wallet product becomes more sensitive when it allows users to top up a balance and spend later. The same applies where users receive value from another user, business, merchant, employer, platform, or rewards programme and can later use that value for payments. Stored value can also appear in products that do not initially look like financial accounts, especially where rewards, points, vouchers, digital stamps, or loyalty balances can be used as money’s worth.
This is why product language can be misleading. A founder may describe the feature as a simple customer balance, but the regulatory question is what that balance represents and how it can be used. If the user has a claim to stored value and can use that value later to make payments, the product may move closer to SVF analysis. If the product only supports technical processing and never holds or controls money, the analysis may be different. The Retail Payment Services and Card Schemes Regulation excludes certain technical service providers that support payment services but do not at any time enter into possession of money under that payment service. (Retail Payment Services and Card Schemes Regulation)
The difference matters for UAE market entry. A UK fintech founder may be used to thinking in terms of EMI, SEMI, or AEMI. In the UAE, the more useful first question is whether the product is a payment service, a stored value product, or a combination that requires a wider regulatory map.
SVF is a heavier route because customer float becomes central
Stored value regulation is heavier because customer float becomes part of the business model. The company is not only enabling a payment action. It is responsible for a structure where customer value is received, recorded, safeguarded, reconciled, made available for use, and redeemed when required.
The UAE SVF framework reflects this. Under the Stored Value Facilities Regulation, a licensee must maintain paid-up capital of at least AED 15 million or an equivalent amount approved by the Central Bank. It must also maintain aggregate capital funds of at least 5% of the total float received from customers. The regulation also states that the Central Bank may impose higher financial resources requirements after considering the scale and complexity of the licensee’s business, and it requires an unconditional irrevocable bank guarantee for the full paid-up capital amount in favour of the Central Bank.(SVF Regulation)
This is a major business-model point. A wallet with stored value can be much more expensive to operate than a narrow payment services product. The burden is not limited to the application process. It affects capital planning, balance sheet design, treasury operations, float protection, reconciliation, user account records, partner agreements, and the operational team needed to run the product safely.
Float management is a real operating obligation
A stored value product must be designed around accurate float management. The Stored Value Facilities Regulation requires timely and accurate records of funds paid into and out of the float, with regular reconciliation between system records and the actual float. The regulation says this reconciliation should be performed at least daily. It also requires the licensee to ensure that customer ledger balances accurately reflect the total float at all times.(SVF Regulation)
The same section requires the assets in which the float is held, including cash and bank deposits, to be segregated from the licensee’s own funds and from funds received for other business activities. It also requires internal controls to protect the float from operational risks, including theft, fraud, and misappropriation.
This means a founder cannot treat the wallet balance as a product database field alone. The product interface, ledger, bank account structure, reconciliation process, customer terms, redemption flow, and operational controls need to work together. If the business cannot explain how customer value moves through the system and how the float is protected, the wallet concept is not mature enough for direct stored value operation.
Redemption changes the product design
A stored value product also needs a credible redemption model. The Stored Value Facilities Regulation expects proper legal positions, authorisations, and detailed procedures to support smooth and efficient redemption where circumstances trigger redemption of the float to customers. (SVF Regulation)
This affects product design more than founders sometimes expect. A wallet is not only about top-up and spend. It also needs rules for refunding, closing accounts, unused balances, merchant failures, expired value, customer disputes, suspicious activity, operational incidents, and the possibility that value must be returned to customers in a controlled way.
That is why stored value should be discussed before the first build, not after the product is already live. The redemption logic can affect database structure, customer terms, support processes, compliance operations, accounting, liquidity planning, and partner contracts. If those elements are added late, the company may have to rebuild core parts of the wallet infrastructure.
Float cannot become the main income engine
Some founders see stored customer balances and immediately think about yield. In the UAE SVF framework, that thinking needs care. The Stored Value Facilities Regulation states that the float must be managed mainly for liquidity management so that sufficient funds are always available for redemption. It also says a licensee must not adopt a business model that treats investment returns from float management as a significant source of income. If the licensee wants to hold part of the float in low-risk financial assets other than cash or bank deposits, it must obtain prior written consent from the Central Bank and demonstrate that the float will be adequately protected from relevant risks. (SVF Regulation)
This point has direct commercial impact. A wallet business should not be modelled primarily around earning returns on customer float. The more reliable economics usually need to come from transaction fees, platform fees, merchant services, embedded workflows, card or payment instrument economics, premium features, or other value-added services that do not depend on treating the float as a yield engine.
For founders comparing the UAE with the UK or EU, this matters. Stored value regulation is designed around customer protection and liquidity, not around giving startups a low-cost funding base. A wallet model that only works if float income becomes material needs to be reviewed carefully before it becomes a business plan.
Partner first may be better for early wallet validation
Because SVF licensing is heavier, a partner-first route can be attractive for early UAE market entry. A fintech may work with a licensed SVF provider, bank, PSP, or other regulated partner if the product can fit within the partner’s permissions and operating model. This can help the founder test the UAE market before carrying the full regulatory and capital burden directly.
The benefit is speed and controlled learning. The company can test user demand, onboarding, top-up behaviour, spend patterns, support load, fraud pressure, merchant acceptance, and local product fit. The cost is dependency. The partner’s permissions, risk appetite, customer due diligence standards, product approvals, settlement model, operational process, and commercial terms will shape the product.
This route is often sensible where the wallet is still narrow, the company is testing one use case, and the main priority is market discovery. It becomes more restrictive when the wallet is the core business model and the company needs direct control over float, ledger logic, customer balances, redemption rules, pricing, partner integrations, and roadmap expansion.
When direct SVF planning becomes necessary
Direct SVF planning becomes more important when stored value is not an accessory, but the product’s core. A fintech building a wallet around customer balances, spending accounts, merchant ecosystems, loyalty value, vouchers, prepaid functionality, or platform-based stored funds may eventually need direct control over the regulated layer.
That shift is a business decision. The company is no longer only testing whether users want the product. It is deciding to operate the infrastructure that holds value, protects customers, manages liquidity, controls reconciliation, and supports redemption. Direct licensing may be slower and more expensive, but it can give the business more control over product architecture, economics, governance, and long-term scale.
A useful test is to ask whether the company can still deliver its roadmap if the stored value layer remains controlled by a partner. If the answer is yes, partner-led launch may remain efficient. If the answer is no, direct SVF planning should start earlier, even if the company still uses a partner during the first phase.
Overseas and UK fintechs need to be careful
A UK fintech should also be careful when offering a wallet into the UAE from outside the country. The Stored Value Facilities Regulation states that it applies to companies providing SVF in the UAE, excluding financial free zones, and that financial institutions regulated by financial free zone authorities may conduct SVF business in the UAE only after obtaining a Central Bank licence.(SVF Regulation)
The regulation also explains that the Central Bank can consider whether an overseas SVF appears to be issued in the UAE or promoted to the UAE public. Factors may include Arabic-language website content, a UAE-related domain name, AED as an accepted currency, contact details in the UAE, promotional activity available to persons in the UAE, and whether the issuer has systems to avoid providing services to UAE residents. The Central Bank uses a holistic approach and considers the particular circumstances of each case.
This is important for market-entry strategy. A UK fintech should not assume that it can test a UAE-facing wallet simply because the entity is incorporated or licensed elsewhere. If the product is presented to UAE users, uses AED, supports local contact points, or is promoted as UAE-relevant, the local perimeter needs to be assessed before launch.
Common founder mistakes
The most common mistake is treating a wallet as a user experience feature rather than a regulated value structure. The interface may be simple, but the regulatory analysis follows the money and the stored claim behind the interface.
The second mistake is assuming that all payment products sit under the same UAE route. The Retail Payment Services and Card Schemes Regulation covers many retail payment services, but payment transactions involving Stored Value Facilities are excluded from that regulation’s scope. A wallet that stores value may therefore need separate SVF analysis rather than only a payment services category review. (Retail Payment Services and Card Schemes Regulation)
The third mistake is underestimating float operations. A founder may budget for licensing and legal support but forget the daily reality of reconciliation, ledger integrity, segregation, redemption, controls, customer support, incident handling, and partner management. These are not secondary details. In a stored value product, they are the operating core.
The fourth mistake is choosing partner-first without migration planning. A partner-led route can be smart, but if the company expects to own the stored value layer later, it should design the first phase with data portability, ledger clarity, customer terms, operational continuity, and future licensing in mind.
Practical conclusion
Stored value is one of the main points where UAE fintech discovery becomes more demanding. A wallet product may trigger heavier regulation because it introduces customer float, stored balances, redemption obligations, capital requirements, segregation, reconciliation, and liquidity controls. These obligations can change the economics and operating model of the business.
For early validation, a licensed partner may be the right route if the use case is narrow and the company still needs local learning. For a long-term wallet business, direct SVF planning may become necessary because the stored value layer is too important to remain outside the company’s control.
The best starting point is simple: define whether the product only moves money or stores value for later use. Once that distinction is clear, the UAE route becomes easier to assess. If the product stores value, the founder should treat the wallet as regulated infrastructure from the beginning, not as a late-stage compliance detail.