Getting a crypto wallet app through App Store and Google Play review: the rules and the common rejection reasons
What Apple's guideline 3.1.5 and Google Play's crypto policy ask of wallet and exchange apps: entity, licences per country, demo accounts and rejection fixes.
BitPolaris Engineering
Getting a crypto wallet app through App Store and Google Play review is decided mostly before a reviewer opens the app. Four things carry the result: the account that submits it, what the app does with customer funds, the countries it is offered in and the licence behind each, and whether the reviewer can sign in and test a money flow. Apple’s rules are in App Review Guideline 3.1.5. Google Play’s are in its Cryptocurrency Exchanges and Software Wallets policy and the Financial features declaration.
This article reads both rule sets as published on 21 November 2026 (Apple’s guidelines were last updated on 16 October 2026; Google’s country table carries an October 2026 change log). What we add from our own wallet and exchange submissions is marked as such: observations from a few apps, not rules and not a forecast of your review. It is a technical reading of the store policies, not legal advice; counsel should confirm which licences your service needs. The build side is in how to build a crypto wallet app.
How do Apple and Google classify a crypto app?
Neither store has one rule for “a crypto app”. Each rule attaches to a function, and one app can fall under several.
| What the app does | Apple App Review Guidelines | Google Play policy |
|---|---|---|
| Stores crypto (wallet) | 3.1.5(i): allowed when the developer is enrolled as an organisation; the text does not separate custodial from non-custodial | Declare “Cryptocurrency wallet”; in listed countries, the named licence or a confirmation that the wallet is non-custodial |
| Buys, sells, converts or transfers crypto | 3.1.5(iii): transactions or transmissions “on an approved exchange”, only where the app has the licensing and permissions to provide an exchange | Declare “Cryptocurrency exchange”; in listed countries, the named licence |
| Futures, token sales, “crypto-securities” | 3.1.5(iv): must come from established banks, securities firms, futures commission merchants or other approved financial institutions | Binary options are not allowed; other products follow local licensing |
| Mining | 3.1.5(ii): not on the device | Not on the device; remote management of mining is permitted |
| Rewards | 3.1.5(v): no currency for completing tasks | Apps that sell or let users earn tokenised digital assets declare it and may not promote potential earnings |
Apple does not separate custodial from non-custodial. 3.1.5(i) covers “virtual currency storage” and 3.1.5(iii) covers “transactions or transmissions of cryptocurrency”, so a wallet with a Buy or Convert button can be reviewed as an exchange, whatever the product is called. One developer of a non-custodial wallet whose buy button opened a third-party on-ramp reported on Apple’s forums in May 2023 a 3.1.5 rejection that asked for licences for “cryptocurrency exchange features” in all locations. That is a single report, not Apple policy, but it fits the wording of the rule.
Google Play does. A non-custodial wallet is still declared as a cryptocurrency wallet, but in listed countries the declaration has a box that confirms that status in place of the licence. Custodial vs non-custodial for a fintech covers the licensing side.
Both stores judge the binary, not the label. Apple’s 2.5.19 bars “hidden, dormant, or undocumented features”, and Google checks the Financial features declaration during app review. If Convert or Earn is not offered in a store build, remove it from that build; hiding the button is not enough.
Who has to submit the app?
The company that provides the service, from an organisation account.
- Apple. 3.1.5(i) requires wallets to come from “developers enrolled as an organization”. 5.1.1(ix) says apps in highly regulated fields, crypto exchanges among them, “should be submitted by a legal entity that provides the services, and not by an individual developer”; 3.2.1(viii) says the same of trading apps and the financial institution behind them. Apple’s App Review page lists “Submitted by incorrect entity” as a common issue and says partnership documentation can be attached in App Store Connect.
- Google Play. The Play Console Requirements policy says developers of financial products, with “cryptocurrency software wallets, and cryptocurrency exchanges” named, must register as an Organization.
- Enrolment. Apple asks an organisation for legal-entity status, a D-U-N-S Number, and a work email and public website on its own domain. Google asks for a D-U-N-S number and details that match the Dun & Bradstreet profile.
Apple shows the organisation’s name as the seller. The simplest file is one where the seller, the entity in the terms of service and the entity on the licence are the same company; if the licence sits with a group company or a partner, have the agreement ready to attach.
It is also why a software vendor should not publish your app from its own account: Apple’s 4.2.6 rejects apps built from a commercialised template “unless they are submitted directly by the provider of the app’s content”, and only the operator can answer the licence questions.
Which countries can you offer it in?
Only those where you can show a licence, a registration or a documented reason why none is needed.
Apple publishes no country list. You select storefronts in App Store Connect (175 countries and regions); 3.1.5(iii) limits exchange functions to places where the app “has appropriate licensing and permissions”, and section 5 requires compliance with the law wherever the app is available. In our submissions, Apple asked an exchange-type app for licence documentation for specific storefronts within a day of those countries being enabled, and approved the app after the storefronts were narrowed to the countries where the operator could show a licence. Developers report the same message on Apple’s forums: the selected storefronts “include locations where you or your third-party service provider(s) have not provided supporting evidence of permissions, registrations, and/or licenses” (thread from October 2024).
Google Play publishes what it expects. For each listed country the app is distributed in, Play Console serves a form:
| Country or region | What Google expects of the developer | Applies to |
|---|---|---|
| EU member states (27); Liechtenstein, Iceland and Norway from July 2026 | Authorisation as a crypto-asset service provider under MiCA | Exchanges and wallets |
| United Kingdom | Registration with the FCA | Exchanges and wallets |
| United States | FinCEN money services business registration and state money transmitter registration, or a federal or state bank charter | Exchanges and wallets |
| United Arab Emirates | A licence from the FSRA, VARA, the DFSA or the Capital Market Authority | Exchanges and wallets |
| Canada | FINTRAC registration as a money services business | Exchanges and wallets |
| Hong Kong | SFC type 1 and type 7 licences and/or a VATP licence | Exchanges; wallets “Not required” |
| Thailand | A digital asset business licence from the SEC of Thailand | Exchanges; wallets “Not required” |
The table also lists Bahrain, Indonesia, Israel, Japan, the Philippines, South Africa and South Korea. Without the listed licence, a developer removes the country or selects one of three declared alternatives: the app is a non-custodial wallet; the app does not offer purchase, holding or exchange there and is geo-restricted; or local law requires no licence or grants an exemption. The third needs supporting documents (a regulator’s letter or a local legal opinion), a disclosure in that country’s store listing of the entity providing the service and its regulatory status, and either a licence in another listed jurisdiction or a publicly traded entity behind the service. Google adds that none of this changes the app’s legal status in the country.
A country missing from the table is not a country without rules: Singapore and Switzerland were absent when we read it, and Google says developers are expected to hold whatever local law requires. For the evidence behind two of the listed authorisations, see our guides to the MiCA CASP application and the UAE VARA licence.
Three operating notes:
- Storefront is not location. Apple assigns a customer to a storefront by the country on their Apple Account; Google targets by where the Play account is registered, “not their physical location”. Availability controls who can download. Country checks at sign-up and KYC still belong on the server.
- Availability can change without a new binary. App Store Connect lets you edit it “at any time”, and existing users in a deselected country keep receiving updates. In our submissions the change itself was not reviewed; questions about the country list arrived with the next version.
- Explain the limits. Apple’s 3.2.2(v) calls “arbitrarily restricting who may use the app, such as by location” unacceptable, so say in the review notes that the country list follows the licence.
What goes in the review notes and the demo account?
The reviewer has to reach every money screen with the credentials you supply.
- Apple, 2.1(a): include demo account details and keep the back end switched on; a built-in demo mode replaces the account only with Apple’s prior approval. App Store Connect’s reference says the demo account “must not expire” and gives the Notes field up to 4,000 bytes. 2.3.1(a) wants new features described “with specificity” and says generic descriptions will be rejected.
- Google Play: sign-in details must be “accessible at all times, reusable, and valid regardless of user location”. Where the app normally asks for a two-step or one-time code, Google asks for “reusable login credentials that can bypass these requirements”.
In our submissions, an “Information Needed” message under guideline 2.1 asked for a working demo account, and an update to a custodial wallet app was approved after one such round, once the reviewer had an account they could sign in to. A second factor that depends on your phone or inbox stops the review; our wallet article describes how Google rejected a demo account with 2FA on as a “multi-factor authentication wall”.
What we put in the notes:
- What the app is. Custodial or non-custodial, the legal entity that operates it, who holds the keys, and who the counterparty is on a conversion or trade.
- Where it is and is not offered, with the licence, registration or exemption for each group of countries attached.
- What is not in this build: product features removed from the store version.
- How to test each money flow: the asset to deposit, how the test balance was funded, an address to send to, the limits.
- The demo account, how its second factor and PIN are handled, and where account deletion is.
Build the review account on the server, not as a special case in the app: a flagged account that skips the one-time code, holds a small balance, has low limits and is monitored. That is our recommendation, not a store rule.
How do the in-app purchase rules touch crypto?
Apple’s 3.1.1 requires in-app purchase for digital features and content sold in the app and names “cryptocurrencies and cryptocurrency wallets” among the mechanisms that may not replace it. A wallet cannot sell a premium tier, or lower fees, for a crypto payment. On NFTs, the same guideline lets apps sell services such as minting, listing and transferring through in-app purchase and show a user’s own NFTs, as long as owning one does not switch on features in the app.
Buying, selling, converting and sending crypto is the regulated service itself, which Apple addresses in 3.1.5(iii) with a licensing condition, not in the in-app purchase rules. That is our reading of the structure; the guidelines do not say it in one sentence, so state in the review notes what the user pays for and to whom.
Google’s Payments policy draws a similar line: Play’s billing system is for in-app features and digital content and “must not be used” for peer-to-peer payments. An app that sells or lets users earn tokenised digital assets declares it in the Financial features form.
Rewards need the same care. Apple’s 3.1.5(v) bars crypto apps from offering currency for tasks “such as downloading other apps, encouraging other users to download, posting to social networks”; a referral bonus paid in crypto for an invited download fits that wording.
Common rejection reasons and how each is fixed
We have met the first two rows ourselves. The others follow from the text of the rules.
| Reason | Rule | Fix |
|---|---|---|
| No licence evidence for a selected storefront | Apple 3.1.5(iii); Google country forms | Narrow availability to the licence footprint, or attach the licence, registration or exemption for each country |
| The reviewer cannot sign in or cannot pass the second factor | Apple 2.1(a); Google sign-in details | A reusable review account that does not expire; back end live and reachable from any country |
| Submitted from an individual account, or by a company that does not provide the service | Apple 3.1.5(i), 5.1.1(ix), 4.2.6; Play Console Requirements | Organisation account of the operating entity; attach partner or group documentation |
| The binary contains features the notes or the declaration do not mention | Apple 2.5.19, 2.3.1(a); Google Financial features declaration | Remove disabled features from store builds; describe every new feature; keep the declaration current |
| Futures, token sales or binary options | Apple 3.1.5(iv), 3.2.2(viii); Google Financial Services policy | Remove from the app, or submit as an approved financial institution with the licence for each country; binary options are barred on both stores |
| Crypto rewards for tasks, or mining on the device | Apple 3.1.5(v), 3.1.5(ii), 2.4.2; Google cryptomining rule | Remove the feature from store builds |
| App features sold for crypto, or NFT ownership switching features on | Apple 3.1.1 | Use in-app purchase or drop the feature |
| No account deletion inside the app | Apple 5.1.1(v); Google account deletion requirement | An in-app path to start deletion; Play also needs a web link |
| Crashes, placeholder text, broken links | Apple 2.1 | Test the store build against the production back end before you submit |
Apple says that, on average, over 40% of unresolved review issues relate to guideline 2.1, so the last row is not a formality. On account deletion, Apple’s guidance lets apps in highly regulated industries add a customer-service step to confirm the request.
If a rejection is wrong on the facts, reply in App Store Connect before you resubmit; Apple also offers an appeal to the App Review Board and a 30-minute appointment with App Review.
Pre-submission checklist
| Item | Apple | Google Play |
|---|---|---|
| Organisation account in the operating entity’s name, D-U-N-S Number in place | Required for wallets (3.1.5(i)) | Required for wallets and exchanges |
| Licence, registration or exemption document for every country selected | Attachment and notes in App Review Information | Country forms in the Financial features declaration |
| Availability list equals the documented country list | Pricing and Availability | Production, Countries / regions |
| Declared features equal the features in the build | Review notes | Financial features declaration: wallet, exchange, tokenised assets |
| Review account: reusable, does not expire, no second factor the reviewer cannot complete, funded for one test send | Sign-in information and notes | Sign-in details under App content |
| Back end live and reachable from any country during review | 2.1(a) | “valid regardless of user location” |
| Privacy policy linked in the listing and inside the app | 5.1.1(i) | Privacy policy and Data safety form |
| Account deletion path | In the app | In the app and by web link |
| Notes state custody model, operating entity, counterparty and test steps | Notes, up to 4,000 bytes | “Any other instructions” field |
| A named contact who can answer the reviewer the same day | App Review contact | Account contact details |
How long does review take?
Neither store publishes a figure for crypto apps. Apple says App Review typically handles at least 50% of submissions in under 24 hours and 90% in under 48 hours, and that complex apps may need more scrutiny. Google says review for certain developer accounts may take up to seven days, or longer in exceptional cases.
Those figures describe a single pass. Each information request adds a round, and a licence question is answered only as fast as you can produce the documents. We have seen questions arrive within a day and an approval follow one round of answers, but that is two apps, not a statistic. Open the organisation accounts early, and do not tie a launch date to a review you do not control. Our launch timeline uses two weeks per storefront as a planning assumption.
What we do, and what stays with you
BitPolaris builds the Wallet and the exchange apps and publishes them under your Apple Developer and Google Play accounts, with your certificates. We prepare the builds, metadata, screenshots, the reviewer account and the review package (compliance notes, demo account, privacy labels). On the pricing page, the Wallet’s iOS app module is €65 a month on the cloud model or €1,250 one-time with a self-hosted or source-code licence, the Android module is €50 a month or €1,050, and the cloud setup fee includes store submission.
The licence, the country list and the answers to licence questions are yours. We are a software vendor, not a law firm, and no vendor can promise an approval: Apple and Google decide.
Crypto app store review FAQ
Does Apple allow crypto wallet apps on the App Store?
Yes. Guideline 3.1.5(i) allows apps that store virtual currency when the developer is enrolled as an organisation. If the wallet also buys, sells, converts or transfers crypto, 3.1.5(iii) limits those functions to countries where the app has the licensing and permissions to provide an exchange.
Do I need a license to publish a crypto wallet on Google Play?
In the listed countries, yes, unless one of Google’s declared alternatives applies. The policy names the authorisation it expects in 13 countries and regions and the EU, such as a MiCA CASP authorisation; Hong Kong and Thailand list none for wallets, and a non-custodial wallet confirms that status in place of a licence. Elsewhere, local law decides.
Why was my crypto app rejected under guideline 3.1.5?
The rule gives five grounds: a wallet from an account that is not an organisation, mining on the device, exchange functions in countries without licensing, futures or token-sale features from a developer that is not an approved financial institution, and currency offered for tasks. For exchange-type apps, missing licence evidence for selected storefronts is the one we have met.
Can the review account have two-factor authentication switched on?
Only if the reviewer can complete it without you. Google asks for reusable credentials that bypass two-step or one-time codes, and Apple requires a demo account that does not expire. We use a separate review account with a small balance.
Can a wallet app take crypto as payment for premium features?
Not on the App Store. Guideline 3.1.1 requires in-app purchase for features sold in the app and names cryptocurrencies and cryptocurrency wallets among the mechanisms that may not replace it. Exchanging and transferring crypto is addressed separately, in 3.1.5(iii).
Sources
All read on 21 November 2026.
- Apple, App Review Guidelines, last updated 16 October 2026: 2.1, 2.3.1, 2.4.2, 2.5.19, 3.1.1, 3.1.5, 3.2.1(viii), 3.2.2(v) and (viii), 4.2.6, 5, 5.1.1(i), (v) and (ix)
- Apple, App Review (review times, common issues, appeals, appointments)
- Apple, Apple Developer Program enrolment (organisation requirements)
- Apple, App Store Connect Help, Manage availability for your app on the App Store
- Apple, App Store Connect Help, Platform version information (App Review information: sign-in and notes)
- Apple, Offering account deletion in your app
- Google Play Console Help, Understanding Google Play’s Cryptocurrency Exchanges and Software Wallets Policy (country table, declaration options; change log October 2026)
- Google Play Developer Program Policy, Blockchain-based Content (exchanges and wallets, cryptomining, tokenised digital assets)
- Google Play Developer Program Policy, Financial Services and Play Console Help, Provide information for the Financial features declaration
- Google Play Developer Program Policy, Play Console Requirements (organisation accounts)
- Google Play Console Help, Requirements for providing sign in details for review and Prepare your app for review
- Google Play Developer Program Policy, Payments
- Google Play Console Help, Distribute app releases to specific countries and regions, Publish your app (review times) and Understanding Google Play’s app account deletion requirements
- Apple Developer Forums, developers’ reports of 3.1.5 rejections: Non-Custodial Cryptocurrency Wallet (May 2023) and thread 765347 (October 2024). Forum posts are individual reports, not Apple policy
Apple, App Store, Google and Google Play are trademarks of their owners; this article describes their published policies and implies no affiliation.
BitPolaris builds the custodial wallet and the exchange apps and publishes them under your developer accounts: builds, metadata, a reviewer account and review notes prepared by us, licence documents and country list supplied by you. Prices are public.