Passer au contenu

Android Play Store Review Guidelines for IAP

Getting your Android Application approved on Google Play requires compliance with Google’s policies, especially for apps with in-Application purchases and subscriptions. This Guide covers everything you need to pass review successfully.

For digital goods and services, you must use Google Play’s billing system:

Digital Goods (Must Use Play Billing):

  • Subscriptions to premium Fonctionnalités
  • In-Application currency or credits
  • Digital content (ebooks, music, videos)
  • Game upgrades and power-ups
  • Application unlocks and premium tiers

Physical Goods (Cannot Use Play Billing):

  • Physical merchandise
  • Real-world services
  • One-time donations to nonprofits

:::Attention 2025 Requirement New apps must use the monetization.subscriptions APIs for handling subscription catalogs. Legacy billing APIs are deprecated. :::

import { NativePurchases, PURCHASE_TYPE } from '@capgo/native-purchases';
// Ensure billing is available on the device
const { isBillingSupported } = await NativePurchases.isBillingSupported();
if (!isBillingSupported) throw new Error('Google Play Billing not available');
// Fetch subscription products (Store data is required—never hardcode pricing)
const { products } = await NativePurchases.getProducts({
productIdentifiers: ['premium_monthly', 'premium_yearly'],
productType: PURCHASE_TYPE.SUBS,
});
// Plan identifiers are the Base Plan IDs you create in Google Play Console
const transaction = await NativePurchases.purchaseProduct({
productIdentifier: 'premium_monthly',
planIdentifier: 'monthly-plan', // REQUIRED on Android, ignored on iOS
productType: PURCHASE_TYPE.SUBS,
});
console.log('Purchase token for server validation:', transaction.purchaseToken);

Google Play mandates clear disclosure of all costs before purchase:

Required Elements:

  • Exact price in Utilisateur’s local currency
  • Billing frequency (monthly, yearly, etc.)
  • What’s included in the subscription
  • Total cost for introductory offers
  • When charges will occur

UI Design Bonnes pratiques

Example of Compliant UI:

function SubscriptionCard({ product }) {
return (
<div className="subscription-card">
<h3>{product.title}</h3>
{/* Show intro offer if available */}
{product.introductoryPrice && (
<div className="intro-offer">
<p className="intro-price">{product.introductoryPriceString}</p>
<p className="intro-period">
for {product.introductoryPricePeriod}
</p>
</div>
)}
{/* Regular price */}
<div className="regular-price">
<p className="price">{product.priceString}</p>
<p className="period">per {product.subscriptionPeriod}</p>
</div>
{/* Clear description */}
<p>{product.description}</p>
{/* Renewal terms */}
<p className="terms">
Renews automatically. Cancel anytime in Google Play.
</p>
<button onClick={() => handlePurchase(product)}>
Subscribe Now
</button>
</div>
);
}

Before a subscription auto-renews, Google requires:

  • Clear notification that renewal will occur
  • Reminder of the price
  • Easy access to cancellation

The Natif-purchases plugin works with Google Play to handle auto-renewal notifications automatically. Ensure your subscription products are properly configured in Google Play Console.

Critical Rule: Prices must be consistent across all platforms where your app is available.

Example Violation:

  • iOS: $9.99/month
  • Android: $7.99/month
  • Web: $11.99/month

Why It Matters: Users can screenshot price differences and report to Google, triggering policy violations.

If your Application includes in-Application purchases, you must:

  1. Link in Play Store Listing

    • Ajouter privacy policy URL in Play Console
    • Must be publicly accessible
    • Must be in the same language as your Application
  2. Link Within Application

    • Display privacy policy in Application Paramètres
    • Show before collecting any Utilisateur data
    • Make easily discoverable

Example Implementation:

function SettingsScreen() {
const openPrivacyPolicy = () => {
window.open('https://yourapp.com/privacy', '_blank');
};
const openTerms = () => {
window.open('https://yourapp.com/terms', '_blank');
};
return (
<div>
<h2>Settings</h2>
<button onClick={openPrivacyPolicy}>
Privacy Policy
</button>
<button onClick={openTerms}>
Terms of Service
</button>
<button onClick={() => NativePurchases.showManageSubscriptions()}>
Manage Subscriptions
</button>
</div>
);
}

Google Play requires detailed disclosure in the Data Safety section:

For IAP Apps, Declare:

  • Purchase history collection
  • Email addresses (for receipts)
  • Appareil IDs (for fraud prevention)
  • Payment Information handling
  • Analyse data collection

The Data Safety section is legally binding. Inaccurate declarations can result in Application removal.

1. Missing or Incorrect Billing Implementation

Section titled “1. Missing or Incorrect Billing Implementation”

Why It Fails:

  • Not using Google Play Billing for digital goods
  • Using Obsolète billing APIs
  • Implementing custom payment Solutions for subscriptions

Prevention:

// ✅ Correct: Use native-purchases (uses Google Play Billing)
await NativePurchases.purchaseProduct({
productIdentifier: 'premium_monthly'
});
// ❌ Wrong: Custom payment processor for subscriptions
// await CustomPayment.charge(user, 9.99);

Why It Fails:

  • Price only shown after clicking purchase
  • Additional fees not disclosed upfront
  • Vague subscription terms

Prevention:

function PurchaseScreen({ product }) {
return (
<div>
{/* Show ALL costs upfront */}
<h2>Premium Subscription</h2>
<div className="pricing">
<p className="price">{product.priceString}/month</p>
<p className="taxes">Taxes may apply based on location</p>
</div>
<div className="features">
<h3>Includes:</h3>
<ul>
<li>Ad-free experience</li>
<li>Unlimited cloud storage</li>
<li>Priority support</li>
</ul>
</div>
<div className="terms">
<p>
Subscription renews automatically unless cancelled at least
24 hours before the end of the current period.
</p>
<p>
Manage or cancel in Google Play Subscriptions.
</p>
</div>
<button onClick={handlePurchase}>
Start Subscription
</button>
</div>
);
}

Why It Fails:

  • Pre-selecting premium Options
  • Hiding cheaper alternatives
  • Making cancellation difficult
  • Fake urgency (“Only 3 spots left!”)

Description Bonnes pratiques

Marketing Guidelines

Prevention:

  • Display all subscription tiers equally
  • Make cancellation clear and accessible
  • Avoid countdown timers or fake scarcity
  • Don’t use dark patterns to Pousser expensive Options

Why It Fails:

  • Application crashes when purchasing
  • Products don’t load
  • Purchase confirmation doesn’t show
  • Premium Fonctionnalités don’t unlock after purchase

Prevention:

import { NativePurchases, PURCHASE_TYPE } from '@capgo/native-purchases';
// Comprehensive testing before submission
async function testPurchaseFlow() {
try {
// 1. Test product loading
const { products } = await NativePurchases.getProducts({
productIdentifiers: ['premium_monthly', 'premium_yearly'],
productType: PURCHASE_TYPE.SUBS,
});
console.log('✓ Products loaded:', products.length);
// 2. Test purchase flow
const transaction = await NativePurchases.purchaseProduct({
productIdentifier: 'premium_monthly',
planIdentifier: 'monthly-plan',
productType: PURCHASE_TYPE.SUBS,
});
console.log('✓ Purchase completed', transaction.transactionId);
// 3. Verify entitlements
const { purchases } = await NativePurchases.getPurchases({
productType: PURCHASE_TYPE.SUBS,
});
if (
purchases.some(
(purchase) =>
purchase.productIdentifier === 'premium_monthly' &&
['PURCHASED', '1'].includes(purchase.purchaseState ?? '') &&
purchase.isAcknowledged,
)
) {
console.log('✓ Premium features unlocked');
}
// 4. Test restore
await NativePurchases.restorePurchases();
console.log('✓ Restore works');
} catch (error) {
console.error('✗ Test failed:', error);
}
}

Why It Fails:

  • No privacy policy link in Application
  • Privacy policy not accessible
  • Data collection not disclosed
  • Data Safety section inaccurate

Prevention:

  • Ajouter privacy policy to Play Store listing
  • Include link in Application Paramètres
  • Accurately fill out Data Safety section
  • Mise à jour policy when adding Nouveau data collection

Alternative Billing Systems (2025 Mise à jour)

Section titled “Alternative Billing Systems (2025 Mise à jour)”

Google now allows alternative billing systems in certain regions:

Eligible Regions:

  • European Economic Area (EEA)
  • South Korea
  • India (coming soon)

Requirements if Using Alternative Billing:

  • Must still offer Google Play Billing as Option
  • Clear communication to Utilisateurs À propos choice
  • Comply with local regulations
  • Service fee still applies (reduced)

For most developers, sticking with Google Play Billing only is simpler. The Natif-purchases plugin handles this automatically.

Utilisateurs must be able to:

  • View Actif subscriptions easily
  • Annuler without contacting Support
  • Understand when cancellation takes effect

Implementation:

import { NativePurchases } from '@capgo/native-purchases';
function ManageSubscriptionButton() {
const openManagement = async () => {
try {
// Opens Google Play subscription management
await NativePurchases.showManageSubscriptions();
} catch (error) {
// Fallback to direct URL
const playStoreUrl = 'https://play.google.com/store/account/subscriptions';
window.open(playStoreUrl, '_blank');
}
};
return (
<button onClick={openManagement}>
Manage Subscription in Google Play
</button>
);
}

Required Disclosure:

  • When does cancellation take effect?
  • Do Utilisateurs keep access until period ends?
  • Are partial refunds Disponible?
function CancellationInfo() {
return (
<div className="cancellation-info">
<h3>Cancellation Policy</h3>
<ul>
<li>Cancel anytime in Google Play</li>
<li>Access continues until end of billing period</li>
<li>No refunds for partial periods</li>
<li>Resubscribe anytime to regain access</li>
</ul>
<button onClick={() => NativePurchases.showManageSubscriptions()}>
Manage in Google Play
</button>
</div>
);
}

Pre-Submission Checklist

  1. Verify Billing Implementation

    • Using Google Play Billing (via Natif-purchases)
    • All subscription products created in Play Console
    • Products are activated and published
    • Pricing set for all target countries
  2. Test Purchase Flows

    • Créer Licence Test Compte
    • Test each subscription tier
    • Verify products load correctly
    • Test purchase completion
    • Verify premium Fonctionnalités unlock
    • Test subscription restoration
    • Test on multiple Appareils
  3. Review All Copy

    • Pricing displayed clearly before purchase
    • All fees disclosed upfront
    • Subscription terms are clear
    • Cancellation process explained
    • No misleading claims
  4. Privacy Compliance

    • Privacy policy linked in Play Console
    • Privacy policy accessible in Application
    • Data Safety section completed accurately
    • Permissions justified and documented
  5. Content Rating

    • Terminé content rating questionnaire
    • Ensure rating matches actual content
    • Declare in-Application purchases in questionnaire
  6. Prepare Store Listing

    • Application description accurate
    • Screenshots show current Version
    • Fonctionnalité graphic meets requirements
    • All required assets uploaded

Initial Review: 7 days on average (can be faster) Updates: Typically faster than initial submission Policy Violations: Immediate suspension possible Appeals: 7-14 days for review

:::Conseil Rolling Reviews Unlike Apple, Google reviews apps continuously. Your Application may go live at any time during the review period, not at a fixed time. :::

  1. Ajouter Test Compte:

    • Go to Play Console
    • Configuration > Licence Test
    • Ajouter Gmail Compte for Test
  2. Test in Sandbox:

import { NativePurchases, PURCHASE_TYPE } from '@capgo/native-purchases';
// Test purchases with license test account
async function testInSandbox() {
const { isBillingSupported } = await NativePurchases.isBillingSupported();
if (!isBillingSupported) {
console.error('Billing not supported in this environment');
return;
}
// Fetch products (returns test pricing when using a license tester)
const { products } = await NativePurchases.getProducts({
productIdentifiers: ['premium_monthly'],
productType: PURCHASE_TYPE.SUBS,
});
console.log('Test products:', products);
// Make test purchase (no charge)
const transaction = await NativePurchases.purchaseProduct({
productIdentifier: 'premium_monthly',
planIdentifier: 'monthly-plan',
productType: PURCHASE_TYPE.SUBS,
});
console.log('Test purchase complete:', transaction.transactionId);
}
  1. Verify Test Banner:
    • When purchasing with Test Compte
    • Should see “Test purchase” notification
    • No real charges occur

Before Production Libération:

  1. Créer Internal Test track in Play Console
  2. Télécharger APK/AAB
  3. Ajouter tester email addresses
  4. Testers Télécharger from Play Store (Test track)
  5. Verify purchase flows work end-to-end
import { NativePurchases, PURCHASE_TYPE } from '@capgo/native-purchases';
async function handlePurchase(productId: string, planIdentifier?: string) {
try {
setLoading(true);
const transaction = await NativePurchases.purchaseProduct({
productIdentifier: productId,
planIdentifier,
productType: planIdentifier ? PURCHASE_TYPE.SUBS : PURCHASE_TYPE.INAPP,
});
console.log('Purchase token:', transaction.purchaseToken ?? transaction.receipt);
// Success - check entitlements from the store
const { purchases } = await NativePurchases.getPurchases({
productType: planIdentifier ? PURCHASE_TYPE.SUBS : PURCHASE_TYPE.INAPP,
});
const isOwned = purchases.some(
(purchase) =>
purchase.productIdentifier === productId &&
(purchase.purchaseState === 'PURCHASED' || purchase.purchaseState === '1') &&
purchase.isAcknowledged,
);
if (isOwned) {
unlockPremiumFeatures();
showSuccess('Premium activated!');
}
} catch (error: any) {
// Handle specific error cases
switch (error.code) {
case 'USER_CANCELLED':
// User backed out - no error needed
console.log('Purchase cancelled');
break;
case 'ITEM_ALREADY_OWNED':
// They already own it - restore instead
showInfo('You already own this! Restoring...');
await NativePurchases.restorePurchases();
break;
case 'ITEM_UNAVAILABLE':
showError('This subscription is currently unavailable. Please try again later.');
break;
case 'NETWORK_ERROR':
showError('Network error. Please check your connection and try again.');
break;
default:
showError('Purchase failed. Please try again.');
console.error('Purchase error:', error);
}
} finally {
setLoading(false);
}
}
import { NativePurchases, PURCHASE_TYPE } from '@capgo/native-purchases';
function RestorePurchasesButton() {
const [loading, setLoading] = useState(false);
const handleRestore = async () => {
setLoading(true);
try {
await NativePurchases.restorePurchases();
const { purchases } = await NativePurchases.getPurchases({
productType: PURCHASE_TYPE.SUBS,
});
const hasSubscription = purchases.some(
(purchase) => purchase.productType === 'subs' && purchase.isAcknowledged,
);
if (hasSubscription) {
unlockPremiumFeatures();
showSuccess('Subscriptions restored!');
return;
}
// Check one-time unlocks if needed
const { purchases: iaps } = await NativePurchases.getPurchases({
productType: PURCHASE_TYPE.INAPP,
});
const hasInApp = iaps.some((purchase) => purchase.productIdentifier === 'premium_unlock');
if (hasInApp) {
unlockPremiumFeatures();
showSuccess('Previous purchases restored!');
return;
}
showInfo('No previous purchases found.');
} catch (error) {
showError('Failed to restore purchases. Please try again.');
} finally {
setLoading(false);
}
};
return (
<button onClick={handleRestore} disabled={loading}>
{loading ? 'Restoring...' : 'Restore Purchases'}
</button>
);
}
import { NativePurchases, PURCHASE_TYPE } from '@capgo/native-purchases';
async function checkSubscriptionStatus() {
try {
const { purchases } = await NativePurchases.getPurchases({
productType: PURCHASE_TYPE.SUBS,
});
const subscription = purchases.find(
(purchase) =>
purchase.productIdentifier === 'premium_monthly' &&
(purchase.purchaseState === 'PURCHASED' || purchase.purchaseState === '1') &&
purchase.isAcknowledged,
);
if (!subscription) {
showPaywall();
return;
}
console.log('Subscription active:', {
productId: subscription.productIdentifier,
expiresAt: subscription.expirationDate,
willRenew: subscription.willCancel === false,
purchaseToken: subscription.purchaseToken,
});
unlockPremiumFeatures();
} catch (error) {
console.error('Failed to check subscription:', error);
}
}

Payments Policy:

  • Not using Google Play Billing
  • Misleading subscription terms
  • Hidden costs

User Data Policy:

  • Missing privacy policy
  • Inaccurate Data Safety declarations
  • Excessive permissions
  1. Review the Violation Notice

    • Read the specific policy cited
    • Understand what Google flagged
    • Vérifier Exemples they provided
  2. Fix the Problème

    • Address root cause, not just symptoms
    • Test thoroughly after fix
    • Document all changes made
  3. Soumettre Appeal (if applicable)

    Clarification and Appeal Process

    Subject: Policy Violation Appeal - [App Name]
    Dear Google Play Review Team,
    I have received notification that my app violates [Policy X.Y].
    I have made the following changes to comply:
    1. [Specific change made]
    2. [Specific change made]
    3. [Specific change made]
    The updated version [version number] addresses all concerns raised.
    Test account for verification:
    Email: test@example.com
    Password: TestPass123
    Thank you for your consideration.

    Request Documentation Exemple

  4. Resubmit or Mise à jour

    • Télécharger fixed Version
    • Resubmit for review
    • Monitor status in Play Console

Navigating Play Store review can be complex, especially with the Nouveau 2025 Test requirements. If you need personalized assistance:

Book a consultation call with our team for help with:

  • Terminé Play Store review preparation
  • Test track Configuration and tester recruitment
  • IAP implementation review
  • Data Safety and privacy compliance
  • Rejection Dépannage and appeals
  • Terminé Application submission process

Our experts have guided hundreds of apps through successful Play Store submissions and can Aide you navigate the 2025 requirements.

Need Aide with implementation?