Docschargebeedocs

HomeBillingPaymentsRevRecGrowthReveal
Support

Product Updates


  • Release Notes

Getting Started


  • Overview
  • Chargebee Billing Data Centers
  • Object Relationship Model
  • Understanding Sites
  • Developer Resources
  • Chargebee Tech Glossary
  • Articles and FAQ

Implementing Chargebee


  • Implementation Guide
  • Go-live Checklist
  • Articles and FAQ

AI in Chargebee


  • Chargebee Agents
  • Chargebee Copilot
  • Chargebee MCP Server (Model context protocol)

Product Catalog


  • Product Catalog Overview
  • Coupons
  • Articles and FAQ

Subscriptions


  • Working with Subscriptions
  • Billing
  • Orders
  • Articles and FAQ

Customers


  • Managing Customers
  • Account Hierarchy
  • Email Notifications
  • Branding
  • Configure Multiple Languages
  • Articles and FAQ

Invoices, Credit Notes and Quotes


  • Invoices
  • Credit Notes
  • Quotes [Legacy]
  • Transactions
  • Articles and FAQ

Taxes


  • Overview
  • Configuring Taxes
  • Country-specific Taxes
  • Articles and FAQ

Hosted Capabilities


  • Overview
  • Hosted Checkout
  • Hosted Self-Serve Portal
  • Hosted Pages Features
  • Additional Hosted Pages
  • Payment Components
  • Managing payments with ChargebeeJS
  • Mobile-Optimized Hosted Pages
  • Articles and FAQ

Site Configuration


  • Users & Roles
  • Custom Fields & Metadata
  • Mandatory Fields
  • File Attachments & Comments
  • Advanced Filter Options
  • Multicurrency Pricing
  • Multi-decimal Support
  • Configuring Reason Codes
  • Events and Webhooks
  • API Keys
  • Time Zone
  • Time Machine
  • Transfer Configurations
  • Articles and FAQ

Reports and Analytics


  • RevenueStory
  • Home Dashboard
  • Frequently Asked Questions
  • FAQs for Classic Reports Sunset
  • Articles and FAQ

Integrations


  • Sales
  • Customer Support and Success
  • Finance
  • Tax
  • Marketing
  • Stitch
  • Collaboration
  • Contract Management
  • Order Management
  • Mobile Subscriptions (Legacy)
    • Legacy Vs New Solution
    • What do you need to know
    • What are the Limitations
    • Apple App Store
    • Google Play Store
      • Connect Play Store with Chargebee
      • Google Play Store Notifications
      • Google Play Store Product Import
      • One Time Purchase
      • Unlink Play Store Integration
      • Google Play Store Sandbox Configuration
      • Chargebee’s Solution for Implementing Billing Library 5.0
    • Multiple Apps Connection
    • Frequently Asked Questions
  • Other Integrations
  • Articles and FAQ

Data Privacy & Security


  • Two Factor Authentication
  • SAML Single Sign-On
  • System for Cross-Domain Identity Management (SCIM)
  • EU-GDPR
  • Consent Management
  • Personal Data Management
  • Compliance Certificates
  • HIPAA Guidelines
  • PCI Recommendations and Integration Types
  • Articles and FAQ

Data Operations


  • Bulk Operations
  • Migration
  • Articles and FAQ
  1. Billing
  2. Integrations
  3. Mobile Subscriptions (Legacy)
  4. Google Play Store
  5. Google Play Store Product Import
  1. Billing
  2. Integrations
  3. Mobile Subscriptions (Legacy)
  4. Google Play Store
  5. Google Play Store Product Import

Google Play Store Product Import

After successfully integrating your Google Play Store account with Chargebee, you can import subscription products configured in Google Play Console as equivalent plans within Chargebee.

  • If you have not imported Google Play Store plans in the test Chargebee site, then all the plans will be created in Chargebee test site with a daily frequency. This is because in the sandbox environment, renewals occur in durations of minutes (e.g. 5 minutes = 1 month), and in Chargebee, the minimum renewal duration is one day.
  • If the plans with daily frequency are migrated from test Chargebee site to live Chargebee site then same daily plans will be created in live Chargebee site. So in order to correct the plan frequencies, it is suggested to re-import the plans in live Chargebee site.
  • The purchase token is valid from subscription signup up to 60 days of token expiry. Therefore, subscriptions that expired more than 60 days ago cannot be imported to Chargebee. Attempting to call Import Receipt API with such an expired subscription token will return an error. Learn more.

Follow the steps below to import products to Chargebee:

  1. Access your Google Play Store integration from the App menu.

  2. Click Import in-app products into Chargebee.

    image
  3. Click Import to initiate product list import from Google Play Store.

    image
  4. The products fetched from your Google Play Store account appears on the import screen.

    image
  5. Click Done to complete the import process.

Import Errors

You may encounter certain errors while importing your products to Chargebee and these errors will restrict the product import to Chargebee. However, you can choose to either skip the product with errors or rectify them and try again.

Skip import with errors

Once the products are processed, you can review the status of the import action and determine which of the products are not imported due to errors. However, if you choose to skip the products with errors the subscription data associated with these products will not be available in Chargebee.

Follow the steps below to complete this:

  1. Click Ignore Errors if you wish to skip importing the products with errors.

    image
  2. Review the advisory message and click Yes, Proceed.

    image
  3. Click Done to complete the import process.

Resolve import errors

Follow the steps below to resolve the errors and reimport the products:

  1. Click Show errors to review the errors which are included within the notes.

    image
  2. The following errors are the most common while importing plans to Chargebee.

- Provide [Pub/Sub access](/billing/1.0/integrations/mobile-playstore-connect#generate-service-account-credentials-json-file) to the role in the Project and generate new [JSON credentials](/billing/1.0/integrations/mobile-playstore-connect#generate-service-account-credentials-json-file). 
- Provide [Financial access](/billing/1.0/integrations/mobile-playstore-connect#generate-service-account-credentials-json-file) and generate new [JSON credentials](/billing/1.0/integrations/mobile-playstore-connect#generate-service-account-credentials-json-file).
  1. After rectifying the errors specified, repeat the import process. Note: If you continue to receive the error displayed below, please reach out to support for further assistance.
image

API References

  • In app subscriptions
  • Non subscriptions
  • Processing Webhooks

Was this article helpful?