Before you buy
Whether you can publish this app at all — the organisation account requirement, the licence tests each store applies, and the four questions to answer before you spend anything.
This page exists to talk some readers out of a purchase. A mobile crypto app is not a theme: both stores apply eligibility tests to the developer, before anyone looks at the build, and no amount of configuration passes them on your behalf.
Answer four questions first.
1. Are you a company?
Apple 3.1.5(i): apps that "facilitate virtual currency storage" may do so "provided they are offered by developers enrolled as an organization". This app holds customer balances, so it is one of those.
An Apple Developer Program organisation enrolment requires a legal entity and a D-U-N-S number for that entity. Google Play requires a verified organisation account for financial-services apps, with matching business documentation.
If you are an individual — a sole trader with no registered entity — you cannot publish this app. Not on either store. That is not a limitation of the package and there is no workaround inside it. Buy it for the source, or to run your platform on the web, but do not buy it expecting to publish.
2. Are you licensed where you intend to publish?
Apple 3.1.5(iii): an app may facilitate cryptocurrency transactions "only in countries or regions where the app has appropriate licensing and permissions to provide a cryptocurrency exchange". You choose your storefronts, and each one you choose is a claim.
Google Play has enforced its crypto exchange and wallet policy since 29 October 2025. It names the countries where a licence or registration is required and where Play will ask you for it before your app stays up. As of writing that list covers, among others:
| Country / region | What is asked for |
|---|---|
| United States | FinCEN registration as a Money Services Business, plus a money transmitter licence in each state you serve |
| European Union | MiCA authorisation as a Crypto-Asset Service Provider |
| United Kingdom | FCA registration under the Money Laundering Regulations |
| Bahrain, Hong Kong, Israel, Japan, Philippines, Singapore, South Africa, South Korea, Thailand, United Arab Emirates, Canada, Indonesia | A named national licence or registration in each |
Read that as a shape, not as legal advice, and check the current list against Play's own policy page before you target a country. Both stores treat publishing into a market you are not licensed in as a policy violation rather than a paperwork error.
3. Are you an approved financial institution?
Two modules ask a harder question than the one above, and it is easy to miss because a country licence does not answer it.
Apple 3.1.5(iv): apps facilitating Initial Coin Offerings, "cryptocurrency futures trading, and other crypto-securities or quasi-securities trading must come from established banks, securities firms, futures commission merchants ('FCM'), or other approved financial institutions and must comply with all applicable law."
That is a test of who you are, not of where you are licensed. If your entity is not one of those, expect futures and token offerings to be rejected in the app however complete your licence attestations are. The rest of the app is unaffected — turn those two modules off for mobile and publish the rest.
4. Do you have your own everything?
You will need, in your own name and not ours:
- Apple Developer Program organisation enrolment, and a Google Play developer account with verified organisation details.
- A published privacy policy URL and an account-deletion URL. Both stores require them, and both must describe your service.
- Your own RPC endpoints and market-data keys. Vendor keys are shared quota; using them in a published app is also Apple 5.2.2 territory.
- Your own app name, icon, colours and store listing copy. This is not cosmetic advice — see Differentiation.
What we will never do
We do not submit apps. Not for you, not for a reseller, not as a favour. Apple 4.2.6 governs apps built from a commercialised template and the submission has to come from the operator's own account; a vendor submitting on a client's behalf is the arrangement the rule is written against, and 4.3(b) allows Apple to remove apps that are already live. Google Play's Misrepresentation policy propagates enforcement across accounts it considers linked, which is how one submission made from the wrong account can cost several operators theirs.
If someone offers to publish this app for you under their account, that is the arrangement both stores are looking for.