Docschargebeedocs

HomeBillingPaymentsRevRecGrowthReveal
Support

Product Updates


  • Release Notes

Getting Started


  • Overview
  • Chargebee Billing Data Centers
  • Object Relationship Model
  • Understanding Sites
  • 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)

Developer Resources


  • Developer Resources Overview
  • Articles and FAQ

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

Entitlements


  • Entitlements Overview
  • Features Overview
  • Feature Management
  • Managing Product Entitlements
  • Subscription Entitlements
  • Customer Entitlements
  • Grandfathering Entitlements
  • Articles and FAQ

Usage Based Billing


  • Understanding Usages
  • Setting up Usage Based Billing
  • Metered Billing
  • Articles and FAQ

Chargebee CPQ


  • Chargebee CPQ
  • Chargebee CPQ for Salesforce
  • Chargebee CPQ for HubSpot

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
  • Pricing Table
  • Managing Payments with Chargebee.js
  • Mobile-Optimized Hosted Pages
  • Articles and FAQ

Site Configuration


  • Users & Roles
  • Custom Fields & Metadata
  • Approvals
  • 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

Multi Business Entity


  • Multi Business Entity Overview
  • Customer Transfer Overview
  • Articles and FAQ

Mobile Subscriptions


  • Overview
  • Omnichannel Subscriptions
  • Omnichannel One-Time Orders
  • Mobile Subscriptions (Legacy)

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
  • Ecommerce Management
  • 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

Google Play Store Sandbox Configuration

Introduction

It is essential that you configure your play store sandbox environment and add testers for accurate testing results as part of your efforts to test the functioning of your integration.

You can use this Sandbox to enable test purchases that can mimic real-world purchases. However, the following conditions apply:

  • There is no amount charged for the purchases made in the sandbox environment.
  • Upon purchase of a subscription, the billing period depends on the subscription period. Learn more about Google Play Billing Library Integration.
  • Google Play Billing Library Integration/Google Play's Billing System
  • Prepare and Roll out a Release

Prerequisites

Review the following prerequisites prior to sandbox configuration:

  • You must have a Google account to perform testing that is configured to Google Play Console.
  • You must use an android device or an emulator with Google Play services installed. Note: It is recommended that you use an Android device for testing and you are logged in to the Google Play Store.
  • The user account being used for testing must be the primary account on the Android device/emulator. A factory reset will allow you to add the testing email address as the primary account on your device. Note: You may lose any unsaved data associated with the previous primary account during the factory reset.
  • Ensure that a security pin is set up on the device or emulator. This will mitigate any errors associated with subscriptions and purchases.
  • Ensure with the mapping package name with app-id which is the same as the app in Google Play. The screenshot below is an example of an App ID:
    image

Adding License Testers

As part of this step, add the email address of the tester that is used as the primary account on the device/emulator. Follow the steps below to add a tester:

  1. Log into your Google Play Console

  2. Click Setup > License testing from the Setup left menu.

    image
  3. Type the email address of the tester in the Add license testers field and press Enter to add to the list.

    image
  4. Click Save Changes.

Create a Closed Track

The Closed Track provides the functionality to view the test results of your app to gather feedback prior to a complete open release. This allows you to gather targeted feedback and resolve any concerns. Follow the steps below to create a Closed Track test:

  1. Click All apps to view your apps.

    image
  2. Click applicable app from the list.

    image
  3. Click Closed testing from the Testing menu.

  4. Click Create track.

    image
  5. Enter the name of the closed track and click Create track.

    image

Add Testers to the Closed Track

After the creation of a closed track, you can now create a list of testers. Follow the steps below to create a list:

  1. Click the Testers tab.

    image
  2. Type contact details of the individual with whom feedback must be shared in the Feedback URL or email address field.

  3. Click Create email list to add the contacts of the testers.

    image
  4. Type the applicable name for the list in the List name field.

  5. Type the email address of the testers in the Add email addresses field. In this example, we added the email address of the primary tester added earlier. Note: Use a comma after each email address and press enter if you wish to add multiple testers.

  6. Review the Email addresses added list to ensure all your entries are included.

  7. Click Save Changes.

    image
  8. Click Create in the pop-up alert to confirm the creation of the email list.

    image
  9. Click Copy link and share the invite with the tester via email. This link must be accessed via the Android device being used for testing.

    image
  10. Click Save changes to ensure your updates are saved.

Assign Country or Region

If your app is new, you may need to make your app available to your country or region. Follow the steps below to do this:

  1. Click the Countries / regions tab.

  2. Click Add Countries / regions.

  3. Select applicable countries with the checkbox and click Add Countries/ regions.

  4. Click Add to confirm your selection.

    image

Create a Release

After you have created the email list of testers, you must upload theAndroid App Bundle to publish the signed APK to the closed track you just created. Access additional details about managing a release.

Once the pre-release (Closed Testing) is approved and available the testers can verify if the purchases and transactions reflect on Chargebee.

Guide for Testers

Assigned testers must follow the steps below to accept testing invites:

  1. Click Accept Invite to proceed with testing. Below is a sample of the invite.

    image
  2. Follow the steps to download the app to their device or emulator prior to testing.

    image
  3. Prior to making a purchase, the tester must ensure the release is approved and is available for selected testers.

    image

    Note: Within the Sandbox environment, subscription renewals happen at a faster rate. Learn more about subscription renewals here.

API References

  • In app subscriptions
  • Non subscriptions
  • Processing Webhooks

Was this article helpful?