Payment SDKs and Data Safety: Declaring Financial Info Correctly
Payment processing SDKs (card readers, wallet integrations, in-app billing add-ons beyond Google Play Billing) typically require a "Financial info" row in Data Safety — covering purchase history and, depending on the integration, payment method details.
The mistake: developers using Google Play Billing exclusively sometimes still add a financial info row unnecessarily, since Play Billing itself handles the transaction and doesn't require your app to declare it the same way a third-party processor would.
The fix
Fix: distinguish between "Google Play Billing only" and "custom payment SDK" — they have different Data Safety implications.
The same check runs automatically when you upload your bundle to the AAB analyzer — permissions, SDK fingerprints, and version info in one pass, free.
Keep going
Run this check on your own AAB
Free analysis, exports when you need them.