Google Play Financial services rejection: loans, crypto and trading apps

Play treats money apps as a special category: if your app lends, invests, trades, exchanges or holds value on someone's behalf, you have to declare it, and in many countries you have to prove you are licensed to do it. A Financial services rejection almost always means one of three things, a declaration you did not complete, a disclosure missing from the app or listing, or a market where you are not permitted to operate at all.

How the rejection is worded

Financial services enforcement usually arrives as a policy email, and it is often more specific than other Play emails because the requirement is concrete. Expect something in the shape of:

"Your app provides personal loan services but does not include the required disclosures in the app's store listing."

"Your app offers financial services in a country where it is not licensed to operate, or you have not provided evidence of the required licence."

"We found that your app has not completed the required Financial features declaration in Play Console."

The in-console copy of the issue lives under App content → Financial features, and on the app's Policy status page.

What it means

Play's Financial services policy sits on top of everything else. It asks you to say what kind of financial product your app touches, then applies rules per product and per country. The three areas that generate most rejections:

Personal loans. If your app offers, arranges or brokers personal loans, Play requires specific disclosures, minimum and maximum repayment period, the maximum APR, and a representative example showing the total cost of a loan. Play also prohibits short-term personal loan apps where full repayment is required within 60 days.

Several countries add a licensing layer: you declare the licence, name the regulated lender you partner with, and upload documentation. India, Indonesia, Kenya, Nigeria, the Philippines and Thailand have all had country-specific requirements at various points.

Personal loan apps also face a permissions restriction: access to contacts, photos, media and precise location is not permitted for these apps, because those permissions have been used for debt-collection harassment.

Cryptocurrency. Exchanges and software wallets are permitted but regulated: you declare the activity, and in some markets you must show registration with the relevant financial authority. On-device mining is not allowed; apps that manage mining performed elsewhere are. Anything that combines crypto with chance-based rewards can fall under the separate real-money gambling policy instead.

Trading and investment. Binary options apps are prohibited outright. Apps offering CFDs, forex or other complex instruments generally require licensing evidence for each country you distribute in.

Why it happens

• The declaration was never completed, usually because the developer did not think of the app as a financial product. Budgeting apps that added a lending referral, or a wallet that added a swap, are common cases.
• Disclosures live in the app but not the listing: or the other way round. Loan terms have to be findable before a user installs and commits.
• The APR example is missing or unrepresentative. A range with no worked example does not satisfy the requirement.
• You distribute everywhere by default. Play publishes to all countries unless you restrict it, so an app licensed in one market gets assessed against the rules of markets it never intended to enter.
• Permissions in the manifest that a loan app may not hold, often dragged in by an SDK rather than requested by your code.
• A partner's licence is claimed but not evidenced. Naming a regulated lender is not the same as uploading proof.
• Marketing language makes it a financial product. "Guaranteed returns", "instant credit", "get approved in minutes" moves an app into this policy even if the app itself only collects an email address.

How to fix it

1. Work out precisely which sub-policy applies. Loans, crypto, trading and payments each have different requirements, and answering for the wrong one is a wasted cycle. The email normally names it; if it does not, the Financial features form's categories will tell you.
2. Complete the declaration in Play Console under App content → Financial features, honestly and in full. If you partner with a licensed institution, name it and upload the documentation rather than describing it.
3. Put the required disclosures where a user sees them before committing. For loans that means the full description as well as the in-app flow: repayment period range, maximum APR, and a worked example, principal, term, fees, total repayable.
4. Restrict distribution to the countries you are actually licensed for. In Play Console this is a per-country setting on the release; use it rather than hoping regional rules will not be applied.
5. Strip the prohibited permissions. Check the merged manifest, not your source, contacts and location permissions frequently arrive from analytics or attribution SDKs.
6. Remove outcome claims from the listing. No guaranteed returns, no promised approval, no implied endorsement by a regulator.
7. Re-read your own onboarding as a first-time user in the strictest market you ship to. If the terms are three taps behind a "Get started" button, move them.

Appeal, or fix and resubmit?

Know which enforcement you are dealing with, because the answer differs:

• Rejected: the release was not published. Fix the declaration or the disclosures and upload a new release. No appeal needed, and appealing instead of fixing loses time.
• Removed: the app is off Play; existing installs keep running. Correct it and submit an update.
• Suspended: the app is off Play and the enforcement is recorded against your developer account.

Appeals are submitted through the form linked in the policy email or from the app's Policy status page in Play Console.

Appeal when you hold documentation the reviewer did not see. This is the one policy area where appeals genuinely work, because licensing questions are factual. If you are registered with the relevant authority, or you operate through a licensed partner, attach the evidence, registration number, licence document, the partner agreement, and state the countries it covers.

Do not appeal a structural finding. If your product requires repayment inside 60 days, or your app mines crypto on the device, no amount of explanation will clear it. Change the product or withdraw from the market.

Financial services is also the area where repeat violations escalate fastest. Google is dealing with a category that attracts genuine predatory behaviour, and enforcement is correspondingly unsentimental: a second or third finding puts the developer account at risk, not just this app. Fix it properly the first time, and never open a second developer account to get around an enforcement, related accounts get terminated together.

What to send

This app arranges personal loans exclusively through [licensed institution], licence number [X], issued by [regulator]. The licence document is attached. Distribution is now restricted to [countries]. The store listing and the in-app flow both disclose the repayment period range, the maximum APR and a representative example of the total cost of a loan before any application begins. The contacts and location permissions have been removed from the manifest.

If it helps to have the email decoded before you start, AppSubmit's rejection explainer will name the specific sub-policy cited and rank the fixes by effort, though the declaration itself can only ever be completed by you, in Play Console.