# Google Subscription Model v2 - Current RevenueCat Support

🚧

New Subscription Features - Google I/O 2022

Due to the [recent announcements from Google](🔗), RevenueCat is not yet compatible with all functionality for subscriptions in the Play Console. At this time, please refrain from adding multiple base plans per subscription, adding multiple offers per base plan, or setting up prepaid base plans. The instructions on this page reflect these restrictions.

RevenueCat is actively working on supporting Google’s new features. Read more in the [RevenueCat Community](🔗).

For now, if you need multiple durations for a subscription, please create a new subscription and base plan for each. Your single base plan and (optional) associated offer should each be marked with a "Backwards Compatible" badge. If you don't see one, click the overflow menu and select "Use for deprecated billing methods".

See below for an example of a fully backwards compatible subscription in the dashboard.



## Existing customers

For customers with products set up in both the Play Console and RevenueCat before May 11th, 2022, these products will continue to work as expected -- Google updated existing subscription products to the new format with backwards compatibility.

Here's a breakdown of what you can expect in the new Google Play console:

• Your original Google subscriptions' product IDs are the same in this new subscription model.

• Google created a base plan with an auto-generated ID for each original subscription, with the duration of the subscription from your original setup. This is the base plan that will be purchased via RevenueCat. RevenueCat doesn't need these base plan IDs yet.

• If you had a free trial and/or introductory price on the original subscription, a single offer was auto-generated by Google and attached to the new base plan. If you had both, you'll see them represented as pricing phases in that single offer.

These auto-generated base plans and offers should be marked with a "Backwards Compatible" badge in the console. They will all continue to work as expected without any changes on your or RevenueCat's side.

## Making Subscriptions Editable, InAppProduct API

**RevenueCat does not use the InAppProduct API for subscriptions.** You are safe to make subscriptions editable, **unless** you are manually using this API outside of RevenueCat.

This is related to this notice:

If you are relying solely on RevenueCat for your subscriptions, you can safely select "Make editable".

Additionally, note that there are no changes to one-time products (i.e. any products configured under the "In-app products" section of the Play Console).

# The Google Play Console

To set up products for Android devices, start by logging into the Google Play Console. Google Play Console is Google's central hub for managing app releases, testing, in-app purchases, and more.

This guide assumes basic knowledge of Google Play Console, as well as having an app set up and ready for adding in-app purchases. For more information, visit [Google's documentation and guides for Google Play Console](🔗).

# Create an In-App Product or Subscription

📘



You'll need to have an APK uploaded before you can create in-app products. Check out our guide on [sandbox testing on Android](🔗) for details on how to upload an APK and roll out a release on a closed test track.

To create an in-app product or subscription, go to Google Play Console's 'All Applications' page and select your app from the list.

In the sidebar, select the **Products** dropdown. Depending on your in-app product type, you will either choose **In-app products** or **Subscriptions**.

After clicking Create, provide a couple pieces of metadata to Google:

## Tips for creating robust product IDs

After you use a Product ID for one product in Google Play Console, **it can’t be used again across any of your apps, even if the product is deleted**. It helps to be a little organized here from the beginning - we recommend using a consistent naming scheme across all of your product identifiers such as:

**`<app>_<price>_<duration>_<intro duration><intro price>`**

• **app:** Some prefix that will be unique to your app, since the same product Id cannot but used in any future apps you create.

• **price:** The price you plan to charge for the product in your default currency.

• **duration:** The duration of the associated base plan's billing period.

• **intro duration:** The duration of the introductory period, if any.

• **intro price:** The price of the introductory period in your default currency, if any.

For example, using this format the identifier for a product that has a yearly subscription with a one week trial for $39.99 USD would be:

**`rc_3999_1y_1w0`**

## Create a base plan

Next, you'll need to add a base plan. Base plans define a billing period, price, and renewal type for purchasing your subscription. Click "Add base plan" and fill out the associated fields. Make sure to set a price, and click "Activate".

Once complete, return to the subscription screen and ensure that the base plan has a Backwards Compatible badge. If you don't see one, click the overflow menu on the base plan and select "Use for deprecated billing methods".

**Keep in mind that the "Prepaid" renewal type is not yet supported by RevenueCat, and only one base plan per subscription will work with RevenueCat at this time.**

## (Optional) Create an offer

If you wish to create a promotion for your base plan, you can do so from the subscription page by clicking "Add offer".

You can then select a product ID, eligibility, and offer phases. As with your base plans, ensure that the offer has a Backwards Compatible badge upon returning to the subscription screen. If you don't see one, click the overflow menu on the base plan and select "Use for deprecated billing methods".

At this point, only one offer at a time can be backwards compatible at once, and additional offers will not work with RevenueCat.

# Integrate with RevenueCat

If you're ready to integrate your new Google Play in-app product with RevenueCat, continue our [product setup guide ](🔗).