Google Play Financial Features Declaration for Crypto Apps
A practical Play Console framework for classifying crypto and financial functionality, selecting the correct Financial Features Declaration categories, aligning developer identity and country targeting, and avoiding inconsistencies between declarations and the actual app.
Direct answer
All developers with an app published on Google Play must complete the Financial Features Declaration, including apps on closed testing, open testing and production tracks. A crypto app should declare the financial functions it actually provides, such as cryptocurrency exchange, cryptocurrency wallet, tokenized digital asset activity, stock trading or financial advice. The declaration should match the app, store listing, backend transaction flow, developer entity and jurisdictional compliance position.
Classify the app by function, select all applicable financial-feature categories, distinguish declaration from licensing, and reconcile Play Console records with the product, legal entity and targeted countries.
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.
Who must complete the Google Play Financial Features Declaration?
Google Play requires developers with an app published on Google Play to complete the Financial Features Declaration. The requirement applies to apps on closed testing, open testing and production tracks. A developer whose app does not provide financial functionality must still complete the declaration and state that no financial features are offered.
For crypto products, the first task is not to choose the category that sounds most convenient. It is to map the product's actual user-facing and backend functions. An app may combine exchange, wallet, NFT, portfolio, securities or advisory features, and the declaration should reflect that functional reality.
Map each crypto function to the relevant declaration category
Google's Financial Features Declaration includes categories that can directly apply to crypto and hybrid fintech products. These include cryptocurrency wallet, cryptocurrency exchange, tokenized digital asset activity, stock trading and portfolio management, financial advice, and other financial functionality. A multi-function app may require more than one category.
| App function | Declaration analysis | What to verify |
|---|---|---|
| Custodial crypto wallet | Cryptocurrency wallet | Who holds or controls customer crypto-assets and how the wallet is operated |
| Crypto trading or exchange | Cryptocurrency exchange | Whether users can buy, sell, convert or trade crypto-assets through the app |
| NFT sales, trading or rewards | Tokenized digital asset activity | Whether users can buy, sell, earn or transact in tokenized digital assets |
| Stock or securities trading | Stock trading and portfolio management | Whether the app facilitates securities transactions or portfolio activity |
| Investment recommendations | Financial advice | Whether the app provides individualized or compensated financial recommendations |
| Price tracking or educational content | Functional assessment required | Whether the app merely displays information or also enables financial transactions |
| Third-party trading API | Functional assessment required | Whether the app merely links out or actually facilitates instructions, orders or transactions |
The final two rows require product-specific analysis. They should not be treated as categorical Google determinations unless the live policy expressly addresses the exact functionality.
Make the declaration consistent with the app, store listing and backend transaction flow
A declaration can be technically completed yet still create review risk if it conflicts with the product presented elsewhere. Before submission, compare six layers of the product record and confirm that they tell the same story.
1. Play Console declaration
Every selected financial category should correspond to a real product function.
2. Store listing and screenshots
Marketing copy should not conceal or contradict regulated financial functionality.
3. In-app functionality
Review what users can actually do after registration, including gated or jurisdiction-limited features.
4. Backend/API transaction flow
Identify whether the app initiates, routes, settles or controls a financial transaction through another provider.
5. Developer-account entity
Confirm that the entity publishing the app is consistent with the provider structure and Google account requirements.
6. Country targeting and authorization
Verify that each targeted market is supported by the required legal and regulatory position.
Unsure how to classify a hybrid crypto or fintech app?
Map the product functions, provider entities, Play Console categories and target jurisdictions before submission.
Send Your Query NowDeclaration answers what the app does; licensing answers whether it may offer that activity
The Financial Features Declaration and regulatory authorization solve different problems. The declaration identifies the app's financial functionality for Google Play. Licensing and registration determine whether the relevant entity may lawfully provide that functionality in a particular jurisdiction.
Selecting Cryptocurrency exchange therefore does not establish that an exchange is authorized. It routes the product into Google's financial and crypto policy framework. For markets covered by Google's dedicated cryptocurrency exchange and software wallet policy, country targeting must then be reconciled with the authorization Google identifies and with applicable local law.
For the country-specific authorization layer, see Google Play Crypto Exchange Compliance Requirements.
Financial-service developers should align the declaration with the Organization developer account
Google states that developers providing financial products and services, including cryptocurrency exchanges and software wallets, should use an Organization developer account. Organization accounts require organization verification and a D-U-N-S number.
This creates another consistency check. If the Financial Features Declaration identifies regulated financial functionality, but the publishing account, store listing and customer-facing legal entity describe unrelated entities, the submission record can become difficult to verify. The legal review should identify the publisher, operating entity, regulated entity and third-party provider relationships before the declaration is finalized.
Hybrid apps should declare each financial function rather than force the product into one label
A modern fintech app can contain several distinct financial functions. A single product may allow a user to hold crypto, trade crypto-assets, view tokenized assets, buy securities and receive portfolio recommendations. Those functions should be analyzed separately because each may trigger a different declaration category and a different regulatory or Google Play policy path.
| Hybrid combination | Likely declaration work | Follow-on review |
|---|---|---|
| Wallet + exchange | Assess both wallet and cryptocurrency exchange categories | Crypto exchange/wallet country policy and authorization |
| Crypto + securities | Assess cryptocurrency exchange plus stock trading/portfolio categories | Crypto and securities provider/entity analysis |
| Crypto + investment recommendations | Assess crypto category plus financial advice | Advisory-function and disclosure analysis |
| NFT + crypto wallet | Assess tokenized digital asset plus wallet categories | Blockchain content, wallet and payments rules |
The goal is not to maximize the number of categories selected. It is to make the declaration faithfully represent the current product.
Do not confuse non-custodial-wallet treatment with the broader declaration obligation
Google states that non-custodial wallets are outside the scope of its dedicated Cryptocurrency Exchanges and Software Wallets policy. That policy boundary should not be converted into a blanket conclusion that a non-custodial wallet has no Financial Features Declaration obligation.
The safer analytical sequence is to determine what the app does, review the declaration categories, and then separately determine which dedicated crypto policy rules apply. A product can be outside one narrow policy while remaining subject to the broader Play Console declaration, financial-services rules, local law and other platform requirements.
For a deeper wallet-specific treatment, see Google Play Crypto Wallet Compliance.
Tokenized digital asset functionality can create a separate declaration branch
Google's blockchain-content policy requires apps that sell or enable users to earn tokenized digital assets to declare that functionality through the Financial Features Declaration. This makes NFT functionality more than a cosmetic product feature when it is integrated into an Android app.
A project should identify whether users can buy, sell, earn, transfer or otherwise interact with tokenized assets and whether those functions coexist with wallet, exchange or payment functionality. The declaration should then reflect the actual mix rather than relying on a single umbrella description such as "Web3 platform."
Apps with no financial functionality must still complete the declaration
An app does not escape the Financial Features Declaration simply because it has no financial functionality. Google's current instructions require developers to complete the declaration and state that the app does not offer financial features.
This matters for crypto-adjacent products such as education, news, analytics, market-data or developer tools. The product team should verify that the app truly remains informational. If users can initiate transactions, connect accounts, manage assets, receive personalized financial advice or access other financial services, the "no financial features" position should be reconsidered before submission.
Avoid declaration mistakes that create preventable review friction
- Using branding instead of functionality. Calling a product a "technology platform" does not answer what financial actions users can perform.
- Declaring only the principal feature. Hybrid apps may require multiple applicable categories.
- Treating declaration as licensing. A selected category does not prove legal authorization in a target market.
- Ignoring third-party APIs. Product flow matters even when a regulated partner performs execution or custody.
- Leaving the store listing inconsistent. Screenshots and marketing text should not contradict the declaration.
- Using the wrong developer-account type. Financial-service providers should review Google's Organization-account requirement.
- Assuming a non-custodial wallet is exempt from everything. Exclusion from the dedicated crypto-wallet policy is not a universal Play Console exemption.
- Failing to update the declaration after product changes. Material new financial functionality should trigger a fresh compliance review.
Google Play financial-features declaration checklist for crypto apps
- Inventory every financial and crypto function available in the current app build.
- Separate informational functions from transaction, custody, exchange and advisory functions.
- Map each function to Google's current Financial Features Declaration categories.
- Select every applicable category without adding functions the app does not provide.
- Confirm whether an Organization developer account is required and verified.
- Reconcile the declaration with the store listing, screenshots and terms.
- Map third-party execution, custody, wallet and API providers.
- Compare Play Console country targeting with licensing and operating restrictions.
- Review Google's dedicated crypto, financial-services and blockchain-content policies where applicable.
- Revisit the declaration whenever the product adds or removes a material financial function.
Official Google Play verification starting points
- Google Play: Financial Features Declaration
- Google Play: Cryptocurrency Exchanges and Software Wallets Policy
- Google Play: Choose a Developer Account Type
- Google Play: Blockchain-based Content Policy
- Google Play: Financial Services Policy
Google Play policies and Play Console forms can change. Verify the current declaration categories, developer-account requirements and crypto policy immediately before submission or a material product update.
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 to classify a crypto app before completing the Play Console declaration?
Align the app's actual functionality, developer entity, Financial Features Declaration, country targeting and regulatory position before submission.