Forex trading app store approval: Apple and Google Play rules for

Can a forex trading app be approved on the App Store and Google Play?

Yes, and many broker apps are live in both stores, but the stores treat trading apps as regulated financial products rather than ordinary software. The questions reviewers ask are not about code quality. They are about identity: is the company that submitted this app the company that offers the trading service, and is that company allowed to offer it in the countries where the app will be available?

That is why the first decisions are commercial and legal rather than technical. Which entity holds your licence or permissions? Which countries will you make the app available in? Is your developer account in that entity’s name? Get those three right and the rest of this guide is paperwork. Get them wrong and no amount of polish will help.

Everything below is based on Apple’s and Google’s published policy pages, checked on 12 October 2026. The stores change their wording from time to time, so read the current version before you submit. This is practical guidance, not legal advice.

Which Apple App Store guidelines apply to trading apps?

Guideline 3.2.1(viii) is the central one. It sits in a list of business models Apple accepts with conditions, and it is short enough to quote in full.

Read it closely and it contains two separate tests. The first is about the submitter: the app “should be submitted by the financial institution performing such services”. The second is about permission: the institution “must have necessary licensing and permissions in the locations where you make them available”. Making an app available in a country where you have no permission to offer trading is a reason for rejection even if your licence elsewhere is perfectly valid.

Why are white label trading apps rejected under guideline 4.2.6?

Because Apple does not want app factories submitting near-identical apps for many clients. Guideline 4.2.6 says: “Apps created from a commercialized template or app generation service will be rejected unless they are submitted directly by the provider of the app’s content.” It adds that “these services should not submit apps on behalf of their clients”.

For a broker, the provider of the content is the broker. So the app must be submitted from the broker’s own Apple developer account, not from the technology provider’s account. This is the single most common reason a white label trading app is turned down, and it is entirely avoidable. It is also why we describe our apps as publishable under your own developer accounts: that is the only arrangement that fits both 3.2.1(viii) and 4.2.6.

Apple’s 4.2 guideline also expects an app to be more than a wrapped website. A real trading app with native charts, order tickets and account screens meets that easily. A thin wrapper around your client portal is more likely to be questioned.

What does Google Play require for forex and CFD trading apps?

A financial features declaration in Play Console, and evidence that links your developer account to your licence. Google’s Financial Services policy states that “any app that contains any financial features must complete the Financial features declaration form within Play Console”. It also says Google “must be able to establish a connection between your developer account and any provided licenses or documentation”.

In practice this means the company name on the Play developer account should match the licensed entity, or you should be able to show clearly how the two are connected, for example through group structure documents. Google also requires apps to comply with the regulations of every region or country they target, and some countries have their own extra documentation requirements set out on the same policy page.

One product type is ruled out completely. The policy says: “We do not allow apps that provide users with the ability to trade binary options.” If your offering includes anything that could be read as binary options, take it out of the app before submission.

Which developer accounts do I need for a trading app?

An Apple Developer Program membership and a Google Play developer account, both opened in the name of your company. Apple’s enrolment page is specific about organisations: your organisation “must be a legal entity so that it can enter into contracts with Apple”, and Apple does not accept “DBAs, fictitious businesses, trade names, or branches”. The legal entity name appears as the seller on the App Store.

Google requires a D-U-N-S number for organisation accounts and states that a company developer account cannot be created without one; only organisations unable to obtain a number are offered an alternative route. Google also applies extra testing rules to new personal accounts: those created after 13 November 2023 must run a closed test with at least 12 testers opted in for at least 14 days before publishing. A company account is the right choice for a broker in any case, and it avoids that step.

Both memberships are paid directly to Apple and Google by the account holder, which is another reason the accounts must be yours. The store fees are a small part of an app project. The larger items are the build itself, the back end that connects the app to your MT5 server, store preparation, and the updates every new iOS and Android release forces on you. When you compare app quotes, check whether each one includes store submission support, how many update releases a year are covered, and who pays if a rejection means rework. If you would like current figures for an FXUP app on your own accounts, message us on WhatsApp and we will send them for your setup.

What do App Store and Google Play reviewers ask brokers for?

Mostly proof that the company behind the app is who it says it is and is allowed to do what the app does. The requests we see most often are these.

• Licence evidence. A copy of the licence or authorisation, the regulator’s public register entry, and a clear link between that entity and the developer account.
• Company accounts. Developer accounts in the name of the licensed entity, not an individual, a marketing agency or the technology provider.
• A working demo login. Apple’s guideline 2.1 asks for demo account details whenever an app includes a login, and for the back-end service to be running during review. A demo account on your MT5 demo server is ideal.
• Matching details. The same company name, address and website across the licence, the developer account, the store listing and the privacy policy.
• Country availability. An explanation of why the app is available in each country, or a narrower list of countries.
• Account deletion. If clients can create an account inside the app, a way to delete it in the app, as guideline 5.1.1(v) requires.

Which documents should I prepare before submission?

Prepare everything before the first build is uploaded. Reviewers respond to what they are given; a submission that answers the obvious questions in advance tends to move faster.

1. Corporate documentsCertificate of incorporation and any group structure chart that links the licensed entity to the developer account holder.
2. Licence or permissionThe licence document and a link to the regulator’s public register entry, in the same entity name.
3. Website and policiesA live website on your domain with a privacy policy, terms and contact details matching the company documents.
4. Review notesA short explanation of what the app does, which entity offers the service, and in which countries.
5. Demo accessA demo login with funds and open positions, so reviewers can see trading screens without registering.
6. Store assetsApp name, icon, screenshots, description and the privacy details each store asks for.

How do I publish a forex trading app on the App Store and Google Play?

In a fixed order, with the slow steps first. The accounts and the D-U-N-S number take the longest and do not depend on the app, so start them the week you decide to build.

1. Open company developer accountsApple Developer Program and Google Play Console, both as organisations, with D-U-N-S numbers.
2. Give your provider accessInvite your technology provider with the roles needed to upload builds, without transferring ownership.
3. Build and test internallySigned builds go to TestFlight and a Play testing track; your team tests every trading flow on demo.
4. Complete store declarationsPrivacy details on both stores and the financial features declaration on Google Play.
5. Submit with review notesInclude the demo login, the licence evidence and the list of countries.
6. Answer questions quicklyReply to reviewer messages from the account owner’s side, with documents, the same day if you can.

How long does trading app review take?

For Apple, usually a day or two once everything is in order. Apple says App Review is “typically reviewing at least 50% of submissions in less than 24 hours and 90% in less than 48 hours”, and warns that “if your submission is incomplete, review times may be delayed or your submission may not pass”. Apple also offers expedited review for critical bug fixes and event-related releases.

Google does not commit to a fixed review time, and first submissions from new accounts or in sensitive categories such as financial services can take longer. Plan for at least a week of buffer between submission and any public launch date, and do not announce a date to clients until both apps are approved. The time that hurts is rarely the review itself; it is the back-and-forth when documents are missing.

What are the most common reasons trading apps are rejected?

Nearly all of them come back to the same few causes, and none of them is technical.

How does approval differ by brokerage setup?

The stores do not care which MT5 arrangement you use; they care which entity offers the service. That plays out differently depending on your setup. A broker with its own licence on its own server has the simplest case. A broker on an MT5 grey label or white label is still the one offering the service to clients, so the app should be submitted by the broker’s licensed entity, not by the platform provider. An introducing broker that does not hold its own licence will usually struggle to publish its own trading app; sending clients to the partner broker’s app, or moving to its own licensed structure first, is the realistic route.

If you are still deciding on structure, our guides to forex licence jurisdictions and starting a forex brokerage explain the options. The licence question is worth settling before you commission an app, not after.

What happens after the trading app is approved?

Each update goes through review again, usually faster, and the same rules keep applying. If you add countries, check that your permissions cover them before you widen availability. If you change the legal entity, the developer account and documents need to move with it, which is far easier to plan than to fix after a rejection.

Keep ownership of the accounts and the Android signing key with your company. If you ever change technology provider, the listing, reviews and client installs stay with you. Ask any provider to confirm this in writing.

How does FXUP handle store submission for broker apps?

Our mobile trading app is publishable on the App Store and Google Play under your own developer accounts. We prepare signed builds, screenshots, store texts, privacy details and review notes with a demo login on your MT5 demo server, and we help you assemble the licence evidence. The submission comes from your accounts. Approval is decided by Apple and Google, so we cannot promise the outcome, but we can make sure the submission answers the questions reviewers ask.

FXUP is an independent technology provider and is not affiliated with MetaQuotes, Apple or Google. You can try the app now at mobile.fxup.net. If you already have a rejection message, send it to us on WhatsApp and we will tell you what we think the reviewer needs.

Questions buyers ask

Not covered here? Ask us on WhatsApp, message @FXUPCK on Telegram or write to [email protected].