The submission fails with a short message referring to a policy section on financial services. No named issue, no path to fix. The firm resubmits with a longer description, fails again, and eventually discovers the actual objection was about who the publisher account belongs to.
Mobile distribution is the part of a broker's stack most often planned last and most often lost first. It is worth understanding as a policy regime in its own right, distinct from financial regulation, because the two answer to different masters and the app store review does not care that your licence is genuine if the publisher record does not line up with it.
What the major stores generally require
Published policies for financial applications across the main mobile stores converge on a small set of themes. The publisher must be the licensed entity, or be publishing on behalf of one with documentary evidence of the relationship. Apps offering regulated financial services must be available only in countries where the provider holds the necessary authorisation. Required disclosures and risk warnings must be present in the app, not only on a website. Ownership and contact details must be verifiable, with a real business entity behind the developer account.
Two consequences follow that catch firms out. First, a personal or agency-held developer account for a licensed brokerage's app is a structural problem, not a paperwork one. Second, country availability has to be set deliberately. Publishing worldwide because it is the default setting puts the app in markets where the firm has no permission, and that is a policy breach the store can act on later even if the initial review passed.
The prop firm and in-app purchase question
Firms selling evaluations hit a second layer. Store policies distinguish digital content and services consumed inside the app, which usually must go through the store's own purchase system, from physical goods and certain regulated financial services purchased outside it. Where a paid evaluation sits in that distinction is not obvious, and it interacts with commission on the transaction and with how the product is described.
The honest position is that this needs a direct answer from the store's own policy team for your specific model, in writing, before you build the flow. Guessing produces an app that passes review, sells for months and then gets pulled after a policy clarification, with the payment flow needing a rebuild while clients are mid-evaluation. Prop firm regulation covers the wider legal picture around the model.
Store policies are published by the companies that operate them, change regularly, and are applied at their discretion. Nothing here describes any particular company's current decision on any firm. Read the current published policy and take your own legal advice.
Why removals happen after approval
Approval is a snapshot. Ongoing enforcement is driven by different signals: user complaints, refund and dispute rates, regulator warnings naming the firm or its brand, changed policy applied retroactively across a category, and reports from other users of the same brand name. A firm can pass review, run for a year and be removed on a Tuesday because a national regulator published a warning list entry that a reviewer found.
That is the same pattern seen with payment account closures. The counterparty is not obliged to keep you, the decision is made on category and signal rather than on individual merit, and the appeal path is thin. Treat it as an availability risk and plan capacity around it.
The routes firms use when a store is closed to them
A progressive web app is the main one. A properly built web platform installs to a phone home screen, works offline for the parts that can, and needs no store approval. It cannot do everything a native app does, and push notifications behave differently across platforms, but it keeps clients trading. Our own mobile approach starts from web-first for exactly this reason.
On Android, direct distribution of a signed application package from the firm's own website is technically available and is used in practice. It carries real consequences: users must permit installation from an unknown source, update delivery becomes your responsibility, and some corporate device policies block it outright. Say that plainly to clients rather than pretending the experience is identical.
On iOS there is no equivalent general route outside the store in most regions, which makes web the practical answer there. Any firm building a distribution plan should assume both stores can become unavailable and size the web experience so it is the primary product rather than the fallback. The client portal matters more in that scenario than the app does.
Getting a submission through the first time
Publish from a developer account owned by the licensed operating entity, with details matching the register. Restrict country availability to markets where you have permission, and be able to explain the list. Put the regulatory disclosure, the risk warning and the entity name inside the app where a reviewer will see it without hunting. Provide working test credentials with a funded demo account so the reviewer can reach the trading screens, because a reviewer who cannot get past login rejects on that alone. Describe the app for what it is rather than in marketing language, and keep any performance claim out of the listing entirely. Marketing restrictions on CFDs apply to store listings the same way they apply to a landing page.
"Every firm I have watched get removed treated the app as the product and the website as the brochure. The ones that survived it had built the web platform properly and only lost a channel."
— Alex Onta, Executive Director, SINGUARD
Key Takeaways
- Store policies for financial apps commonly require the publisher to be the licensed entity or to evidence publishing on its behalf.
- Country availability must be set to the markets where you hold permission, not left on the worldwide default.
- Approval is a snapshot: complaints, dispute rates, regulator warning lists and retroactive policy changes drive later removals.
- A web-first platform, with native apps beside it, is the only distribution route no external reviewer can withdraw.
Frequently Asked Questions
Do app stores require a financial licence to publish a trading app?
Published policies for financial applications generally require the publisher to be appropriately licensed or to evidence that it publishes on behalf of a licensed provider, and to limit availability to countries where that authorisation applies. Check the current policy text directly.
Can an approved trading app be removed later?
Yes. Enforcement continues after approval and responds to complaints, dispute rates, regulator warning list entries and policy changes applied across a category, so removal can follow a long period of normal operation.
Is distributing an Android package from our own website a workable alternative?
It is technically possible and used in practice, with real trade-offs: users must allow installation from an unknown source, updates become the firm's responsibility, and some managed devices block it. On iOS a web app is usually the practical route.
About the Author
Alex Onta is an Executive Director at SINGUARD. He built eTrader, the terminal, the mobile apps, eTrader Broker, Copytrading, Business and Community, along with the worldwide clustered-server infrastructure it all runs on, with his brother Roman Onta helping on the design, and he leads that division today. Together with Roman he builds the Prop Firm CRM, the Broker CRM, Scalegram and CopySignals, and the two of them carry worldwide compliance, payment processing and international business structuring side by side. He lives and works in Dubai for most of the year. Meet the executive duo leading Singuard's five divisions.