Google Play Crypto Exchange Compliance Requirements
A practical framework for cryptocurrency exchanges publishing on Google Play, covering organization-account identity, Financial Features Declaration, country targeting, licensing evidence and jurisdiction-specific compliance.
Direct answer
Google Play permits cryptocurrency exchange apps, but distribution must align with its financial-services rules, the Financial Features Declaration, developer identity requirements and applicable local law. For countries in Google Play's dedicated cryptocurrency policy table, the developer must satisfy the listed registration or licensing conditions before targeting that market. If the required authorization cannot be demonstrated, Google instructs developers to remove that location from targeting.
Map product functionality to Google Play declarations, determine whether the wallet is in scope of the exchange/software-wallet policy, document U.S. regulatory status, and separate platform compliance from underlying legal compliance.
Technology law research should connect legal rules to the actual product and business model.
This shared featured video and research layer are part of the sitewide authority architecture. The page-specific analysis below uses primary sources, passage-first explanations and practical decision frameworks.
About Dr. Rahul Dev and the research approach
How to patent fintech inventions
Gen AI Innovations
What is Extended Reality
How to patent artificial intelligence based innovations
Patent claim drafting
How to patent fintech inventions
Gen AI Innovations
What is Extended Reality
How to patent artificial intelligence based innovations
Patent claim drafting
App-store compliance for crypto and financial trading products
Watch this additional briefing alongside the page-specific legal and platform analysis below.
Determine whether the app is a cryptocurrency exchange under Google Play policy
Google Play maintains a dedicated policy for cryptocurrency exchanges and software wallets. The first submission question is functional: does the app enable users to buy, sell, exchange or otherwise transact in crypto-assets through an exchange service? A product should not be classified only by marketing labels. The declaration, store listing, terms, regulated entity and actual transaction flow should describe the same service.
Google expressly states that non-custodial wallets are outside the scope of its dedicated Cryptocurrency Exchanges and Software Wallets policy. That does not remove other Google Play rules or local-law obligations, but it makes exchange functionality a distinct compliance branch from a purely non-custodial wallet.
Build Google Play compliance across identity, declaration, distribution and authorization
1. Developer identity
Financial-service providers, including cryptocurrency exchanges, should use a Google Play Organization developer account. Google requires a D-U-N-S number for organization accounts.
2. Product declaration
All published apps must complete the Financial Features Declaration. Exchange apps should declare the cryptocurrency exchange feature accurately.
3. Country targeting
Selecting a country or region in Play Console is an affirmative distribution choice. The targeted markets should match the business's actual legal and operational footprint.
4. Regulatory authorization
For listed jurisdictions, the exchange must meet Google's specified local authorization route and any additional applicable local requirements.
Planning a Google Play launch or responding to a compliance inquiry?
Map your developer entity, exchange functionality, target countries and regulatory evidence before submission.
Send Your Query NowComplete the Financial Features Declaration accurately
Google requires all developers with an app published on Google Play to complete the Financial Features Declaration, including apps in closed testing, open testing or production. Apps with financial functionality must identify the relevant feature categories. Google's form expressly includes Cryptocurrency exchange as a declaration category.
The declaration should be treated as a regulatory-routing record, not a checkbox exercise. If the app also includes a wallet, stock trading, tokenized digital assets, financial advice or another financial feature, those functions should be assessed independently and declared where applicable. Material inconsistency between the declaration and the app's actual functionality can create avoidable review risk.
| Record | What should be consistent |
|---|---|
| Financial Features Declaration | Actual financial functions offered to users |
| Store listing | Accurate description of exchange and wallet features |
| Terms/customer agreement | Correct operating and contracting entity |
| Licences/registrations | Entity, activity and geography supporting the claimed service |
| Play Console targeting | Markets where the exchange is legally and operationally offered |
For U.S. targeting, Google Play specifies FinCEN and state-level authorization
Google's current country-specific cryptocurrency policy states that a cryptocurrency exchange targeting the United States must either be registered with FinCEN as a Money Services Business and with a state as a money transmitter, or operate through a qualifying federal or state chartered bank entity. Google also makes clear that developers remain responsible for all other applicable local legal requirements.
This should not be reduced to a single registration-number check. The submission record should identify the exact legal entity holding the relevant registrations, the states actually served, any states excluded from service, and whether the app's Play Store availability matches those operating restrictions.
Match each targeted Play Store market to the authorization Google identifies
Google Play's dedicated policy lists selected jurisdictions and the regulator or authorization route expected for cryptocurrency exchanges. The list changes as regulatory frameworks evolve, so developers should verify the current Google policy and the relevant regulator immediately before submission or expansion.
| Target market | Google Play policy reference | Submission implication |
|---|---|---|
| United States | FinCEN MSB plus state money-transmitter registration, or qualifying bank entity | Map federal and state coverage to actual target geography |
| United Kingdom | FCA registration | Verify the registered entity and permitted crypto activities |
| European Union | MiCA Crypto-Asset Service Provider authorization by a relevant competent authority | Map authorization and any national requirements to EU distribution |
| Japan | Japan FSA crypto-asset exchange registration | Ensure the Play developer and service entity relationship is clear |
| South Korea | KoFIU VASP-related filing/authorization route identified by Google | Check local operational and reporting prerequisites |
| United Arab Emirates | Authorization through an applicable UAE regulator identified by Google, such as VARA, ADGM/FSRA or DIFC/DFSA depending on the model | Do not treat a UAE corporate registration as equivalent to virtual-asset authorization |
| Canada | FINTRAC MSB registration referenced by Google | Confirm any additional securities or provincial obligations separately |
This table is a planning aid, not a substitute for Google's live policy or local legal advice. The applicable authorization depends on the product, legal entity and market.
Remove unsupported countries rather than overstate the exchange's permissions
Google Play directly links country targeting to authorization. If a developer targets a listed country but cannot provide the required registration or licensing information, Google's published process instructs the developer to remove that location from targeting.
This makes geographic configuration a legal-control issue. The team should compare Play Console availability against onboarding eligibility, geofencing, customer terms and licence coverage. A user should not be able to infer that the exchange is available in a jurisdiction merely because the app can be downloaded there when the underlying service is not authorized or intentionally offered there.
Countries not listed by Google still require local-law analysis
Google states that developers may continue to publish cryptocurrency exchanges and software wallets in countries not included in its dedicated country-specific table, but developers remain responsible for obtaining any licence required under local law. Google may also request additional information about compliance in a jurisdiction that is not listed.
Accordingly, an unlisted country is not a "no licence required" category. It means Google's policy page does not prescribe a specific Play-level authorization path for that market. The developer still needs a defensible local-law position and should be prepared to explain the regulated activity, operating entity and geographic restrictions if Google asks.
Prepare a country-by-country evidence pack before review
A practical Google Play evidence pack should be organized so that a reviewer can trace the app from developer identity to the regulated service and then to each target market. Depending on the jurisdiction and Google's request, useful materials may include the operating entity name, Organization developer-account details, D-U-N-S verification, registration or licence number, regulator name, official public-registry link, activity covered, territorial scope, customer agreement, product-flow diagram, wallet/custody relationships and screenshots of geographic controls.
This is a response architecture rather than a claim that Google universally requires every item for every exchange. The governing question is whether the submitted evidence supports the actual service and the locations selected in Play Console.
| Evidence question | Reviewer-ready answer |
|---|---|
| Who publishes the app? | Verified Organization developer entity |
| Who provides the exchange service? | Named operating/regulated entity |
| What does the app do? | Declared exchange and related financial functions |
| Where is it distributed? | Current Play Console country list |
| What supports each country? | Licence/registration or documented legal basis |
| How are unsupported markets handled? | Targeting removal, onboarding restrictions and/or feature geofencing |
Keep Google Play policy separate from the underlying legal analysis
Google Play policy and financial regulation overlap but are not identical. A regulator may permit an activity subject to particular conditions, while Google may impose its own distribution or verification requirements. Conversely, satisfying a Google Play form does not establish compliance with federal, state or foreign financial law.
For U.S. regulatory analysis, see Crypto Exchange Legal Compliance. For wallet functionality, compare Google Play Crypto Wallet Compliance. For Apple distribution of exchange functionality, see Apple App Store Crypto Exchange Approval Requirements. If Apple has already rejected a crypto app, the separate Apple crypto-app rejection response framework addresses remediation and reviewer evidence.
Google Play crypto exchange pre-submission checklist
- Confirm that exchange functionality is classified correctly.
- Use an Organization developer account and verify organizational identity.
- Complete the Financial Features Declaration accurately.
- Export the exact list of targeted countries/regions from Play Console.
- Map each listed jurisdiction to the authorization Google identifies.
- Perform local-law review for targeted countries not in Google's table.
- Verify public regulator records and entity names.
- Reconcile the store listing, terms, app functionality and regulatory entity.
- Remove unsupported markets or implement defensible geographic controls.
- Prepare reviewer-readable evidence before submission or material feature expansion.
Official Google Play verification starting points
- Google Play: Understanding the Cryptocurrency Exchanges and Software Wallets Policy
- Google Play: Financial Features Declaration
- Google Play: Choose a Developer Account Type
- Google Play: Financial Services Policy
Google Play policies and financial regulations change. Verify the current policy text, regulator records and local-law requirements immediately before submission or expansion.
Crypto app-store approval and compliance guides
Use these related guides to move between Apple App Store, Google Play, U.S. licensing, rejection remediation and cross-platform approval questions.
Need a Google Play exchange compliance map for your target markets?
Align the app's functionality, developer entity, financial declaration, jurisdiction targeting and regulatory evidence before review.