Skip to content
AppDues
Log in
Contact salesSign up

Google Play prepaid plans: a practical setup guide

Google Play prepaid plans give Android subscribers a way to buy access up front and extend it themselves, instead of being charged automatically at the end of each cycle. For apps serving markets where recurring billing is restricted, or users who prefer to control their spending, that model can widen who can pay. This guide explains how prepaid plans behave, when they are worth offering, and the steps to ship one with a billing integration.

What a prepaid plan actually does

A prepaid plan is a subscription model introduced with Google Play Billing Library 5. Nothing renews on its own: the subscriber's access simply ends at the close of the paid period unless they choose to buy more time. That choice is a top-up, and it is what keeps the entitlement alive.

A useful detail: the top-up does not have to match the original purchase duration. A user can pick any prepaid base plan that belongs to the same subscription, even one with a different length.

Prepaid plans always use the IMMEDIATE_AND_CHARGE_FULL_PRICE proration mode. In plain terms, the buyer is charged the full price of a billing period immediately, and access is extended by the duration of the top-up they bought. That makes the cost and the time gained easy to state up front.

After a top-up, several fields in the Purchase result object change: the order ID, purchase time, signature, purchase token, and acknowledgment status. Those updates are what let you and the user see an accurate, current picture of the subscription.

A worked example: a user buys a 30-day base plan on day 1. On day 25 they top up with a 7-day base plan from the same subscription. Under IMMEDIATE_AND_CHARGE_FULL_PRICE they are charged the full 7-day price at once, and access now runs to day 32 rather than day 30. The Purchase result reflects the new order ID, purchase time, signature, purchase token, and acknowledgment status.

When prepaid plans are the right fit

Prepaid plans are not a universal upgrade over auto-renewing subscriptions. They are a fit when at least one of these conditions is true:

  • Recurring billing is restricted. Some markets limit auto-renewing subscriptions, and prepaid plans let you keep serving those users within local rules.
  • Pay-as-you-go is the norm. In markets where prepaid mobile and voucher-based payment are familiar, a prepaid app subscription matches existing habits.
  • Payment infrastructure is uneven. Where digital banking access is limited, prepaid balances and vouchers can reach users who cannot easily use standard recurring payment methods.
  • Price sensitivity is high. Users who dislike open-ended recurring charges often accept a plan they consciously renew.
  • Subscription fatigue is a factor. A less binding option can bring in users who avoid signing up for another recurring charge.

A quick decision check before you build:

  1. Does a meaningful share of your audience sit in a market with recurring-billing limits?
  2. Can your paywall clearly show the price and the duration gained per top-up?
  3. Will you support more than one base-plan duration, so users can choose a shorter or longer extension?
  4. Do you have a way to remind users before access lapses, since nothing renews automatically?

If most answers are yes, prepaid plans are worth testing alongside your existing plans rather than replacing them outright.

Setting up a prepaid plan with a billing integration

Creating a prepaid plan in Google Play Console follows much the same path as creating an auto-renewing base plan. A billing integration then handles the billing side so you do not have to build the top-up and acknowledgment logic yourself. The sequence below is the practical order of work.

Step 1: Move to Google Play Billing Library 5

Prepaid plans depend on Billing Library 5, so the migration comes first. Google set transition deadlines: new apps were required to use Billing Library 5 from August 2023, and existing apps had until November 2023. Those dates are historical reference points from the original publication; confirm the current requirement in Google's own deprecation guidance before you plan a release.

Step 2: Update the billing SDK

A billing SDK that supports Google Play Billing Library 5 handles the migration work on that side. Bring your SDK to the latest version and follow the Android installation and migration documentation for your platform. There is no separate prepaid-specific SDK to add.

Step 3: Create the plan in Google Play Console

In the Play Console you define the plan's duration and price, decide whether customers may extend it, and mark it as prepaid rather than auto-renewing. The setup mirrors an auto-renewing base plan closely; the billing integration documentation walks through the console fields in detail.

Step 4: Connect products in the billing dashboard

Configure your products in the billing dashboard, or import them directly from Google. The integration acknowledges prepaid plans and their top-ups automatically, which is the behavior that keeps a subscriber's access continuous across renewals they initiate themselves. Treat that as a described product capability to verify against current documentation, not as a guarantee from this guide.

Step 5: Test the purchase and top-up paths

Test before release, and test both flows: the first purchase and the later top-up. Confirm that content unlocks after the initial purchase, that a top-up extends access by the expected duration, and that a plan left to expire actually loses access. Use the Play Store sandbox for test purchases.

A common confusion worth separating out: a plan that has simply run out is not the same as a failed acknowledgment. An expired plan should show as expired with no active entitlement; a failed acknowledgment is a processing problem on the purchase itself. Check the acknowledgment status in the Purchase result before assuming the user let their plan lapse.

Step 6: Watch performance in the dashboard

Once live, the billing dashboard tracks plan performance from first purchases through to expirations. Because prepaid plans do not renew on their own, expiration data is especially useful: it tells you how many users chose not to top up and when. Confirm the current dashboard metrics against the integration's own documentation before you rely on them for reporting.

Step 7: Adjust based on what you see

Use the dashboard data to decide what to change: pricing, the set of available durations, or targeted promotions. The integration supports pricing experiments, so you can compare variants rather than guessing; verify the current experiment capabilities in the integration's documentation before designing a test.

Where to start

Prepaid plans are most valuable where recurring billing is constrained or where users prefer to pay as they go. The work splits cleanly: Google Play Console defines the plan, and the billing integration handles acknowledgment and top-up tracking. Start with one base plan in a market where the model fits, test both the purchase and the top-up path, and let expiration data guide the next iteration.

Frequently asked questions

Can a top-up have a different duration from the original purchase?

Yes. A user can top up using any prepaid base plan in the same subscription, including one whose duration differs from their first purchase.

Which proration mode do prepaid plans use?

They always use IMMEDIATE_AND_CHARGE_FULL_PRICE: the user is charged the full price for a billing period immediately, and access is extended by the top-up's duration.

What changes in the Purchase result after a top-up?

The order ID, purchase time, signature, purchase token, and acknowledgment status are all updated.

Does the billing integration acknowledge prepaid top-ups automatically?

The integration acknowledges prepaid plans and their top-ups so subscribers keep uninterrupted access. Verify this against current documentation for your SDK version.

Why do prepaid plans matter in markets like India?

Some markets restrict auto-renewing subscriptions. Prepaid plans let developers serve those users while staying within local rules, and they match pay-as-you-go habits that are already common there.