Google Play installment subscriptions lock the buyer in but not your revenue, here's what a refund or missed payment costs you

Sell a 12-month plan on Google Play as an installments base plan and the buyer agrees to pay every month for a year. That commitment binds the buyer. It doesn't bind the money to you. Google pays you as each monthly payment lands, nobody pursues a buyer who stops paying, and a refund or chargeback can end the plan with most of the year still unpaid. Google Play installment subscriptions are a good conversion tool in the four countries that have them. They're a weak revenue guarantee. Here's how the commitment actually behaves when a buyer cancels, misses a payment, gets a refund, or disputes a charge, and what each outcome costs you.

How Google Play installment subscriptions work

An installments base plan is a subscription the buyer pays for in fixed monthly amounts over a commitment period you choose. In Play Console you set the monthly price and a commitment of 3 to 24 months, and the purchase screen shows the buyer the total. Every payment is monthly. Neither you nor the buyer can change the frequency or timing.

The feature is limited to buyers in Brazil, France, Italy and Spain, and Google tells developers to check Play Console for the latest availability. Showing the full commitment detail in your paywall, such as the number of committed payments, needs Play Billing Library 7 or later, where it arrives in the installmentDetails field.

What happens when the commitment ends

You pick one of two renewal types. With auto-renews monthly, the plan becomes an ordinary monthly subscription after the first commitment, with no further lock-in. With auto-renews for the duration, the buyer signs up for another full commitment period of the same length. Free trials don't count toward the initial commitment. Introductory pricing phases do.

The commitment is firm for the buyer, not for your revenue

Google describes the commitment as firm for cancellations and price changes. That's the part that sounds like guaranteed income. Read the rest of the documentation and three facts pull the other way.

• You aren't paid upfront. Google's documentation says payouts happen as buyers make their monthly payments, and developers are not paid when the buyer signs up.
• Missed payments are nobody's job to collect. If a buyer fails to pay, neither Google nor the developer attempts to collect the missed or outstanding payments, apart from Google's normal retries during grace period and account hold.
• Google won't make you whole. Its documentation states plainly that Google isn't responsible to the developer for any remaining unpaid installment payments.

Google's consumer-facing Payment Plan Terms tell the buyer they can't cancel the remaining installments and remain liable for outstanding amounts. That's the buyer's contract with Google. On your side of the ledger, an unpaid installment is simply revenue that never arrives.

What each exit does to an installment plan

There are four ways an installment subscription ends early or changes course. Each one leaves a different amount of money on the table.

The buyer cancels

A buyer who cancels mid-commitment doesn't get out of the remaining payments. Google sends a SUBSCRIPTION_CANCELLATION_SCHEDULED notification as soon as they cancel, while payments remain. The Google Play Developer API keeps the subscription in SUBSCRIPTION_STATE_ACTIVE and adds an empty pendingCancellation object to installmentDetails. At the end of the commitment you get SUBSCRIPTION_CANCELED, followed by SUBSCRIPTION_EXPIRED, unless the buyer restores the plan first. Keep the entitlement on until then. The buyer is still paying.

You stop the payments yourself

Sometimes you want a buyer out early, for a billing complaint or a product you're retiring. The purchases.subscriptionsv2.cancel method takes a cancellationType. USER_REQUESTED_STOP_RENEWALS behaves like a buyer's own cancellation, so the commitment still runs to the end. DEVELOPER_REQUESTED_STOP_PAYMENTS stops the next payment, the buyer doesn't have to finish the commitment, and the plan can't be restored. This is the quiet exit. It hands nothing back, it just stops the future charges.

The latest order gets refunded

Play Console's refund rules for subscriptions are blunt. Refund the most recent order and the order is refunded, the subscription is removed immediately, and future recurrences are canceled. Refund an older order and the subscription stays active. The revoke API behaves the same way. Its fullRefund option returns the full amount of the latest charge, and a SUBSCRIPTION_REVOKED notification tells you to cut access right away. On an installment plan, the latest charge is one monthly payment. So a refund-and-revoke hands back one month and cancels every payment still owed under the commitment.

The buyer stops paying

Google's documentation notes that payment declines and recoveries can happen on any individual installment. Grace period and account hold still apply, and Google retries during them. After that, the balance is written off, by nobody in particular. Google's Payment Plan Terms add one consequence for the buyer: someone suspended or canceled for missing an installment may lose the right to use a payment plan on Google Play again. You get nothing from that.

What a refund or chargeback costs on an installment plan

Here's where the mechanics turn into money. Take an example plan of €9.99 a month on a 12-month commitment. The buyer sees €119.88. Your ledger sees €9.99 a month, less Google's service fee, for as long as payments keep landing.

A refund forfeits the whole unpaid balance

Say you refund and revoke the most recent order in month four. You hand back one €9.99 payment. You also cancel the eight payments not yet made, €79.92 of the commitment that will now never arrive. Refunding an older order instead keeps the plan alive, which is why the order you pick matters more on an installment plan than on a monthly one. If what you actually want is to stop billing without returning money, DEVELOPER_REQUESTED_STOP_PAYMENTS does that without the refund.

Chargebacks now land on you, one installment at a time

For Google Play orders placed after August 3, 2026, Google makes the developer responsible for chargebacks: the purchase price less Play's service fee, plus the bank's chargeback fee. Because an installment plan bills monthly, each monthly payment is its own charge a bank can dispute. A buyer who regrets the whole year can dispute several of them. The cost you carry per dispute is small. The fee stack isn't, and a lost dispute is bank-final. A chargeback also ends the subscription, since Google sends SUBSCRIPTION_REVOKED when a purchase is charged back.

The costs that don't stop with the payments

Every month of access you serve costs you something real: compute for the features the buyer uses, third-party API calls, storage, and support time. When a buyer cancels, that bill keeps running to the end of the commitment, but so do their payments. When a buyer stops paying, the bill can keep running through grace period and account hold while no money arrives. That gap is the one to watch.

How to protect installment revenue

Track the commitment, not just the subscription state

Store initialCommittedPaymentsCount and remainingCommittedPaymentsCount from the subscription resource on every notification. SUBSCRIPTION_STATE_ACTIVE tells you access is on. The remaining payment count tells you how much of the commitment is still real money and how much is only a promise.

Treat a pending cancellation as an early warning

A buyer with a pendingCancellation is still paying, but they've told you they want out. They're the buyers most likely to ask for a refund or dispute a later charge. Handle their support tickets fast and don't let a billing complaint turn into a chargeback.

Pick the exit before you pick the refund

When a buyer wants out, decide what you actually intend. Stopping future charges is DEVELOPER_REQUESTED_STOP_PAYMENTS. Returning money for one month and ending access is a refund and revoke of the latest order. Returning money for an older month while keeping the plan running is a refund of that older order. RefundHalt watches these notifications per plan, so a refund, a revocation or a disputed installment shows up next to the payments still owed, not as a loose event you piece together later.