Google Play subscription proration: choosing a replacement mode
When a subscriber changes plans in the middle of a paid period, the replacement mode decides three things at once: when the new plan starts, when money is collected, and whether the billing date stays put. This guide explains the five Google Play modes with a single worked example, a decision checklist, and the implementation pitfalls that most often break plan changes.
What proration means in practice
Proration is the arithmetic Google Play applies when a plan change lands before the current period ends. Think of the unused remainder of the old plan as a balance: each mode either discards it, converts it into time, converts it into a price difference, or ignores it until expiry. The worked example used throughout is a subscriber on a $2 monthly tier who switches on April 15 to a $36 annual tier, halfway through the month, leaving about $1 of unused value.
The five modes, compared on one example
WITHOUT_PRORATION starts the new plan immediately but collects nothing until the old plan would have expired, so the unused remainder is effectively given away and the billing date resets to the old expiry date. WITH_TIME_PRORATION also starts immediately, but turns the unused remainder into extra days before the first charge, which pushes the billing date to a user-specific day. CHARGE_FULL_PRICE collects the full new price right away and adds the unused remainder as extra time at the end, so revenue arrives early but service is extended. CHARGE_PRORATED_PRICE keeps the billing date fixed and collects only the difference between the old remainder and the new plan's price for the same span, which requires the new plan to cost more per unit of time. DEFERRED changes nothing until expiry: the current plan runs to its end, then the new plan activates and is charged.
Decision checklist
Start with direction. For a downgrade, DEFERRED is the default because the subscriber keeps what they paid for and goodwill is preserved. For an upgrade, ask three questions in order: Is the new plan more expensive per unit of time? If yes, CHARGE_PRORATED_PRICE gives immediate, fair revenue with a stable billing date. If no, such as moving from monthly to a discounted annual option, CHARGE_PRORATED_PRICE is unavailable, so CHARGE_FULL_PRICE is the immediate-revenue alternative. If immediate revenue is not the priority and you want to honour the full unused value, WITH_TIME_PRORATION works, but expect scattered billing dates. Reserve WITHOUT_PRORATION for low-value plans where simplicity outweighs the forfeited remainder. Finally, check availability for the exact transition: not every mode is valid for every product change, so code should fall back gracefully, for example to WITHOUT_PRORATION, if the preferred mode is rejected.
The DEFERRED callback trap
DEFERRED has a subtle failure mode. Google Play returns a successful transaction immediately, but that transaction belongs to the old product; the new product's transaction arrives only when the old subscription expires. If callback context is stored under the new product ID, the success callback never fires and the app can look broken to the user. The fix is to associate the callback with the old product when the replacement mode is DEFERRED. The protected contract modules code0001 to code0006 and code0008 carry the exact mode definitions and this callback handling; refer to those module IDs for the authoritative code rather than retyping them here.
Pitfalls and revenue impact
Four pitfalls recur. First, WITH_TIME_PRORATION is rejected between options of the same product, so do not use it for monthly-to-annual switches within one product. Second, proration math runs server-side in Google's timezone, so client-side displays of the next charge or deferred activation date can drift if device timezone is assumed. Third, DEFERRED messaging must not promise immediate access; tell the user the date the new plan takes effect. Fourth, treat mode availability as per-transition: wrap the purchase so a rejected mode falls back to a simpler one instead of failing the sale. At scale these choices compound: in an illustrative scenario of 10,000 subscribers moving halfway through a $9.99 month to a $99.99 year, forfeiting the remainder costs roughly $50,000, while charging the prorated difference recovers about $41,600 immediately, and pushing first charges out by about 15 days per user complicates monthly revenue reporting.
Testing checklist
Use test tracks and cover: mid-cycle upgrades between tiers and between monthly and annual billing; downgrades, which may need different messaging under DEFERRED; first-day and last-day-of-period changes, where proration math is most fragile; and rapid successive plan changes, which can expose callback race conditions. For DEFERRED specifically, confirm the success callback fires despite the transaction carrying the old product ID, and confirm the new plan actually activates on the old plan's expiry date.
| Mode | New plan starts | Charge timing | Billing date | Best fit |
|---|---|---|---|---|
| WITHOUT_PRORATION | Immediately | At old expiry | Resets to old expiry | Simplicity for low-value plans |
| WITH_TIME_PRORATION | Immediately | After unused time is consumed | Moves to a user-specific day | Honouring unused value |
| CHARGE_FULL_PRICE | Immediately | Full price now | Extends by unused time | Immediate revenue |
| CHARGE_PRORATED_PRICE | Immediately | Price difference now | Unchanged | Fair upgrades with stable dates |
| DEFERRED | At old expiry | At old expiry | Unchanged | Downgrades and goodwill |
Illustrative comparison based on the captured April 15 example: $2 monthly tier switching to a $36 annual tier halfway through the cycle.
Frequently asked questions
What does Google Play subscription proration control?
Proration decides how Google Play handles the charge and billing date when a subscriber moves between plans partway through a paid period. The replacement mode you select determines whether the new plan starts now, whether a charge happens now, and whether the next billing date moves.
Which mode should I choose for an upgrade or a downgrade?
CHARGE_PRORATED_PRICE is often the balanced choice for an upgrade when the new plan costs more per unit of time: it charges only the difference for the remainder of the cycle and keeps the original billing date. DEFERRED is usually better for a downgrade because the person keeps the current plan until it ends.
Why can WITH_TIME_PRORATION fail?
WITH_TIME_PRORATION fails when switching between subscription options of the same product, such as a monthly and an annual option for the same base product. Use it only when moving between entirely different products, and choose another mode for same-product option changes.
What is the DEFERRED callback gotcha?
With DEFERRED, Google Play returns an immediate successful transaction for the old product, while the new product activates when the old subscription expires. Store the callback context under the old product ID; storing it under the new product ID can prevent the success callback from firing.
What should proration testing cover?
Test mid-cycle upgrades, downgrades, first-day and last-day changes, and several rapid plan changes. For DEFERRED, also verify the callback fires and the new plan activates on the expected expiry date.