Android Play Store Review Guidelines for IAP

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

Google Play Billing Requirements

Mandatory Billing System

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

Digital Goods (Must Use Play Billing):

• Subscriptions to premium features
• In-app currency or credits
• Digital content (ebooks, music, videos)
• Game upgrades and power-ups
• App unlocks and premium tiers

Physical Goods (Cannot Use Play Billing):

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

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

Implementation with Native Purchases

import { NativePurchases } from '@capgo/native-purchases';

// Configure with Google Play billing
await NativePurchases.configure({
  apiKey: 'your_api_key_here'
  // Google Play billing is automatically used on Android
});

// Fetch subscription products
const { products } = await NativePurchases.getProducts({
  productIdentifiers: [
    'premium_monthly',
    'premium_yearly'
  ]
});

// Purchase flows through Google Play
const { customerInfo } = await NativePurchases.purchaseProduct({
  productIdentifier: 'premium_monthly'
});

Transparency and Disclosure Requirements

Upfront Pricing Disclosure

Google Play mandates clear disclosure of all costs before purchase:

Required Elements:

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

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>
  );
}

Auto-Renewal Disclosure

Before a subscription auto-renews, Google requires:

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

Tip

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

Price Consistency Across Platforms

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.

Privacy Policy Requirements

Mandatory Privacy Policy

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

1. Link in Play Store Listing

   • Add privacy policy URL in Play Console
   • Must be publicly accessible
   • Must be in the same language as your app

2. Link Within App

   • Display privacy policy in app settings
   • Show before collecting any user 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>
  );
}

Data Safety Section

Google Play requires detailed disclosure in the Data Safety section:

For IAP Apps, Declare:

• Purchase history collection
• Email addresses (for receipts)
• Device IDs (for fraud prevention)
• Payment information handling
• Analytics data collection

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

Common Rejection Reasons

1. Missing or Incorrect Billing Implementation

Why It Fails:

• Not using Google Play Billing for digital goods
• Using deprecated 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);

2. Unclear Pricing or Hidden Costs

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>
  );
}

3. Deceptive Subscription Patterns

Why It Fails:

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

Prevention:

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

4. Incomplete Testing

Why It Fails:

• App crashes when purchasing
• Products don’t load
• Purchase confirmation doesn’t show
• Premium features don’t unlock after purchase

Prevention:

// Comprehensive testing before submission
async function testPurchaseFlow() {
  try {
    // 1. Test product loading
    const { products } = await NativePurchases.getProducts({
      productIdentifiers: ['premium_monthly', 'premium_yearly']
    });
    console.log('✓ Products loaded:', products.length);

    // 2. Test purchase flow
    const { customerInfo } = await NativePurchases.purchaseProduct({
      productIdentifier: 'premium_monthly'
    });
    console.log('✓ Purchase completed');

    // 3. Verify entitlements
    if (customerInfo.entitlements.active['premium']) {
      console.log('✓ Premium features unlocked');
    }

    // 4. Test restore
    const restored = await NativePurchases.restorePurchases();
    console.log('✓ Restore works');

  } catch (error) {
    console.error('✗ Test failed:', error);
  }
}

5. Privacy Policy Violations

Why It Fails:

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

Prevention:

• Add privacy policy to Play Store listing
• Include link in app settings
• Accurately fill out Data Safety section
• Update policy when adding new data collection

Alternative Billing Systems (2025 Update)

Regional Compliance

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 users about choice
• Comply with local regulations
• Service fee still applies (reduced)

Note

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

Subscription Management

Easy Cancellation

Users must be able to:

• View active subscriptions easily
• Cancel 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>
  );
}

Cancellation Grace Period

Required Disclosure:

• When does cancellation take effect?
• Do users keep access until period ends?
• Are partial refunds available?

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 native-purchases)
   • All subscription products created in Play Console
   • Products are activated and published
   • Pricing set for all target countries

2. Test Purchase Flows

   • Create license test account
   • Test each subscription tier
   • Verify products load correctly
   • Test purchase completion
   • Verify premium features unlock
   • Test subscription restoration
   • Test on multiple devices

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 app
   • Data Safety section completed accurately
   • Permissions justified and documented

5. Content Rating

   • Complete content rating questionnaire
   • Ensure rating matches actual content
   • Declare in-app purchases in questionnaire

6. Prepare Store Listing

   • App description accurate
   • Screenshots show current version
   • Feature graphic meets requirements
   • All required assets uploaded

Review Timeline

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

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

Testing Before Submission

License Testing

1. Add Test Account:

   • Go to Play Console
   • Setup > License Testing
   • Add Gmail account for testing

2. Test in Sandbox:

// Test purchases with license test account
async function testInSandbox() {
  // Configure SDK (same as production)
  await NativePurchases.configure({
    apiKey: 'your_api_key'
  });

  // Fetch products (will be in test mode)
  const { products } = await NativePurchases.getProducts({
    productIdentifiers: ['premium_monthly']
  });

  console.log('Test products:', products);

  // Make test purchase (no charge)
  const { customerInfo } = await NativePurchases.purchaseProduct({
    productIdentifier: 'premium_monthly'
  });

  console.log('Test purchase complete:', customerInfo);
}

3. Verify Test Banner:
   • When purchasing with test account
   • Should see “Test purchase” notification
   • No real charges occur

Internal Testing Track

Before production release:

1. Create Internal Testing track in Play Console
2. Upload APK/AAB
3. Add tester email addresses
4. Testers download from Play Store (testing track)
5. Verify purchase flows work end-to-end

Best Practices for Native Purchases

Handle All Purchase States

import { NativePurchases } from '@capgo/native-purchases';

async function handlePurchase(productId: string) {
  try {
    setLoading(true);

    const { customerInfo } = await NativePurchases.purchaseProduct({
      productIdentifier: productId
    });

    // Success - check entitlements
    if (customerInfo.entitlements.active['premium']) {
      showSuccess('Premium activated!');
      unlockPremiumFeatures();
    }

  } 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);
  }
}

Implement Restore Purchases

function RestorePurchasesButton() {
  const [loading, setLoading] = useState(false);

  const handleRestore = async () => {
    setLoading(true);

    try {
      const { customerInfo } = await NativePurchases.restorePurchases();

      if (customerInfo.activeSubscriptions.length > 0) {
        showSuccess('Subscriptions restored!');
        unlockPremiumFeatures();
      } else {
        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>
  );
}

Check Subscription Status

async function checkSubscriptionStatus() {
  try {
    const { customerInfo } = await NativePurchases.getCustomerInfo();

    // Check if user has active premium subscription
    const hasPremium = customerInfo.entitlements.active['premium'] !== undefined;

    if (hasPremium) {
      const premiumInfo = customerInfo.entitlements.active['premium'];

      console.log('Subscription active:', {
        productId: premiumInfo.productIdentifier,
        expiresAt: premiumInfo.expirationDate,
        willRenew: premiumInfo.willRenew,
        periodType: premiumInfo.periodType
      });

      unlockPremiumFeatures();
    } else {
      showPaywall();
    }
  } catch (error) {
    console.error('Failed to check subscription:', error);
  }
}

If Your App Gets Rejected

Common Policy Violations

Payments Policy:

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

User Data Policy:

• Missing privacy policy
• Inaccurate Data Safety declarations
• Excessive permissions

Resolution Steps

1. Review the Violation Notice

   • Read the specific policy cited
   • Understand what Google flagged
   • Check examples they provided

2. Fix the Issue

   • Address root cause, not just symptoms
   • Test thoroughly after fix
   • Document all changes made

3. Submit Appeal (if applicable)

   

   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.

   

4. Resubmit or Update

   • Upload fixed version
   • Resubmit for review
   • Monitor status in Play Console

Additional Resources

• Google Play Developer Policy Center
• Google Play Billing Documentation
• Subscriptions Best Practices
• Play Console Help

Need Expert Help?

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

Book a consultation call with our team for help with:

• Complete Play Store review preparation
• Testing track setup and tester recruitment
• IAP implementation review
• Data Safety and privacy compliance
• Rejection troubleshooting and appeals
• Complete app submission process

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

Support

Need help with implementation?

• Review the Native Purchases documentation
• Check Android sandbox testing guide
• Visit Google Play Developer Support