Financial features declaration completed for Google Play

Google Play requires every app targeting Android — including apps with zero financial features — to complete a Financial Features declaration in the Play Console before publication. Skipping this step blocks promotion to the production track entirely; it is not a soft warning. For apps with in-app purchases (React Native IAP, RevenueCat, Stripe), an incomplete declaration is treated as a policy violation under Google Play's Financial Services policy, which can result in app removal and developer account suspension. Developers who discover this requirement the night before a launch date lose 48–72 hours to Play Console processing time.

Complete the Google Play Financial Features declaration in Play Console under App content → Financial features before the first production submission. Document completion in the repository so future contributors don't repeat the work:

# Create a submission record to track compliance steps
touch SUBMISSION_NOTES.md

In SUBMISSION_NOTES.md, record: the declaration date, whether IAP was declared, and the Play Console account email used. If RevenueCat (react-native-purchases) or react-native-iap is present in package.json, select 'Yes, my app includes in-app purchases' and specify the purchase type. If no financial features exist, the 'No' declaration still requires completion — it takes under two minutes. Reference completed declarations in fastlane/metadata/android/ or src/store-metadata/compliance/.

• ID: app-store-metadata-listing.compliance-declarations.financial-declaration
• Severity: high
• What to look for: Google Play requires ALL apps — including those with no financial features — to complete a Financial Features declaration in the Play Console. From the codebase, check for signals that indicate whether financial features are present: (a) react-native-iap, expo-in-app-purchases, react-native-purchases (RevenueCat), or purchases-flutter in package.json/pubspec.yaml — indicates IAP, (b) Stripe, Braintree, or PayPal SDK dependencies — indicates payment processing, (c) react-native-plaid-link-sdk or similar — indicates financial data access, (d) bank account, credit card, cryptocurrency, or investment-related screen names or components. If no financial features are detected but the app targets Android, note that the declaration is still required (answered as "No financial features"). The declaration cannot be directly verified from the repository, but check for any SUBMISSION_NOTES.md or similar documentation noting it has been completed. Count all instances found and enumerate each.
• Pass criteria: Evidence in submission notes that the Google Play financial features declaration has been completed; or the project is iOS-only. At least 1 implementation must be confirmed.
• Fail criteria: Android app with financial features (detected IAP, payment, or banking libraries) with no documentation that the declaration has been addressed.
• Skip (N/A) when: iOS-only project (no Android target detected).
• Detail on fail: "react-native-purchases (RevenueCat) detected — Google Play requires the Financial Features declaration to be completed in Play Console for apps with in-app purchases".
• Remediation: The declaration is required for app publication on Google Play, regardless of whether financial features are present.
  1. In Google Play Console → App content → Financial features, complete the questionnaire
  2. If your app has in-app purchases: select "Yes, my app includes in-app purchases" and describe the purchase types
  3. If no financial features: select "No" for each category — the declaration is still required but quick to complete
  4. Add a note in REVIEW_NOTES.md or SUBMISSION_NOTES.md confirming this has been done so future submitters don't wonder Document financial feature declarations in src/store-metadata/compliance/ or update via Play Console. Keep a reference in app.json or package.json.