Fintech MVP Rules in the UK, US and UAE: Scope and Timeline

Start with one question: who holds the money?

Write the answer down before you ask anyone for a quote. Does user money ever sit in an account your company controls? The rest of this article covers how that answer plays out in each market.

• No, a payment provider or licensed partner holds it. You build the app, the onboarding flow and the integration with the partner. The partner runs the regulated activity under its own authorisation, within the limits of its permissions.
• Yes, your company holds it. You need your own authorisation in each market. On top of the app, you build and run a ledger, monitoring, reporting and the controls your regulator expects.

United Kingdom: FCA authorisation or a partner

In the UK, payment services fall under the Payment Services Regulations 2017, and e-money falls under the Electronic Money Regulations 2011. The FCA says a firm that provides payment services as a regular business in the UK must apply to become an authorised payment institution, a small payment institution or a registered account information service provider, unless it is exempt or already holds permissions. What this changes for your MVP:

• On a partner route, the scope is the app, the partner's onboarding and verification flow, and webhooks for payment and account status. Your timeline also depends on the partner approving your use case, so start that conversation before the build.
• On your own authorisation, the app waits for the authorisation. You can still build and test a demo for investors, but you can't go live with real money flows until you are authorised.
• Read only features, like showing bank data and insights, sit in a different category from moving money. Ask your lawyer which category your first feature falls into. It can change the route completely.

United States: federal registration and state licenses

The US has two layers. At federal level, FinCEN says money services businesses must register with the Treasury, with limited exceptions. The first registration is due within 180 days of setting up the business, and it must be renewed every two years. At state level, state regulators license and supervise money transmitters, and many of them do it through the NMLS system, according to CSBS. What this changes for your MVP:

• State by state licensing is why many US founders launch on a partner that already holds the licenses. Your build then covers the integration, not the licensing.
• Launch geography is a scope decision. If you or your partner can only serve some states, the app needs to check where users live at sign up and block the rest. Plan that screen from day one.

UAE: three regulators depending on where you set up

In the UAE, the regulator depends on your activity and on where your company is licensed.

• Onshore payments. The Central Bank of the UAE runs a licensing regime for retail payment services and card schemes under its Retail Payment Services and Card Schemes Regulation.
• DIFC. The DFSA regulates financial services carried out in or from the DIFC. It has also run an Innovation Testing Licence. This restricted license lets fintech firms test a product for a limited period without meeting every requirement that normally applies.
• Virtual assets in Dubai. VARA regulates virtual assets across Dubai's mainland and free zones, except inside the DIFC.

What the UAE setup changes for your MVP

Your company setup comes before your feature list.

• Decide where to set up your company before the build. That decides which regulator applies, and so which features you can ship.
• A sandbox or testing license can let you go live with real users, within limits. Your app then needs those limits built in, like user caps or transaction caps, so the product can't go past them.
• Crypto features fall under a separate regulator. Keep them out of the first version unless they are the product.

The three markets side by side

Use this as a starting point for the conversation with your lawyer.

• Main regulator for payments. UK: FCA. US: FinCEN plus state regulators. UAE: CBUAE onshore, DFSA in DIFC, VARA for virtual assets in Dubai.
• Main source. UK: PSRs 2017, EMRs 2011. US: MSB registration, state money transmitter licenses. UAE: Retail Payment Services and Card Schemes Regulation, DFSA rules, VARA rules.
• Extra scope on a partner route. UK: partner onboarding, status webhooks. US: partner onboarding, state checks at sign up. UAE: partner onboarding, limits set by your license or sandbox.
• What sets the go live date. UK: partner approval or FCA authorisation. US: partner approval or federal and state licensing. UAE: company setup, then partner or regulator approval.

App store rules apply in every market

Two store rules can delay a fintech launch whichever market you pick. Account verification can delay your launch, so open your company developer accounts in the first week.

• Apple. Guideline 5.1.1(ix) of the App Review Guidelines says apps in highly regulated fields, including banking, financial services and crypto exchanges, should be submitted by the legal entity that provides the service, not by an individual developer. Under guideline 3.1.5, crypto wallets must be offered by developers enrolled as an organization.
• Google Play. Any app with financial features must fill in the Financial features declaration in Play Console. Personal loan apps also have disclosure rules. In some countries they also need licensing documents that Google must be able to link to your developer account.

What your quote should say about your route

A fintech quote that doesn't name the regulatory route can't really be fixed. Before you sign, get these three points in writing. Security is a separate topic, and every money app needs it. Our AI prototype to production guides cover what to check, especially if you built your first version with an AI app builder.

• The route the build assumes. Partner, sandbox or your own license. The scope, the screens and the go live date all follow from it.
• On a partner route, which partner the build is tested against. The quote should name the partner's sandbox environment and say who pays the partner and verification fees.
• On a sandbox or your own license, which limits are built into the app. User caps, transaction caps and blocked regions should be listed. The quote should also say which features wait for authorisation.

How to keep the first version small

The fastest fintech MVPs test one money flow, not five. A budgeting app can start with read only bank data. A B2B tool can start with invoices and payment links. A user to user payments app can start on a partner that handles payouts. Each cut means less regulated scope. Our MVP development package is a fixed price from $3,460 and ships in about 20 days. You own 100% of the code, and you get two weeks of fixes after launch. To see what individual features add, read our feature cost guides. To see how AI changes build cost overall, read MVP Development Cost in 2026. Want to know which route your idea needs before you spend money on a build? Book a call and leave with a clear first version scoped around your route.

Do I need a license to launch a fintech MVP?

Not always. If a licensed partner holds the funds and runs the regulated activity, you may be able to operate under its setup. That depends on your market, your product and the partner's permissions. A lawyer in your market should confirm it.

Which market is fastest for a fintech MVP?

The route matters more than the country. In all three markets, the partner route avoids waiting for your own license, but depends on the partner's approval. Your go live date then depends on the partner's approval and your store accounts, not just on the build.

Can I build the app while the license is pending?

Yes. You can build and test with test data, and show a working demo to investors. Real money flows have to wait until you or your partner are allowed to run them.

Does Apple accept fintech apps from individual developers?

For banking and financial services, Apple's guideline 5.1.1(ix) says the app should be submitted by the legal entity that provides the service. Set up an organization account early.