Skip to content

How REM Payments changes a plan's price without breaking a single subscription

Gateways will not let you edit a plan's price. REM Payments keeps every price as a version, pins each subscription to the one it bought, and moves customers only when and how you choose - with the gateway doing the moving.

RREM Team3 min read

Raising a price sounds like editing one number. For a subscription business it is one of the riskiest things you can do: a customer who bought at ₹999 a month and is suddenly charged ₹1,299 without warning is a refund request, a chargeback, or a lost customer. And the payment gateways make it harder still, because none of them lets you edit the price of a plan. In Razorpay, Stripe and PayPal, a new price is a new plan.

This is how REM Payments handles it.

Every price is a version

A plan's price, currency, billing period, setup fee and feature values live in a price version. A checkout records which version it sold, the subscription is pinned to it, and every renewal charges that version's amount. The plan's own fields only show what new buyers get today.

A version nobody has bought can be corrected in place; there is no new version for a typo. A version someone bought is never edited again. Its invoices, payments and gateway plan point at it, and it can never be deleted.

You choose who moves, and when

Changing a price opens one dialog with three choices:

  • New purchases only. Everyone already subscribed keeps today's price. This is grandfathering, and it is the default worth considering first.

  • At their next renewal. Each customer moves at their first renewal after a notice period (30 days by default). Everyone affected is told right away by e-mail, and your systems get a signed plan.price_scheduled event with the old and new amounts and the date.

  • Immediately. Meant for price cuts. A rise needs an explicit confirmation, and even then nothing is charged for the period already running: the new amount starts at the next renewal.

Before you save, the dialog shows the impact: how many customers are on the plan, how many move and how many keep their price, monthly recurring revenue now and after, the date it takes effect, which features are added or reduced, and what each gateway will be asked to do.

A plain edit of the price is refused while customers are on the plan. The dialog is the only way.

The gateways do the moving

When a subscription is billed by a gateway, our record is not the source of truth for what the card is charged. So for each version REM Payments creates that version's own plan at the gateway, the first time someone buys it in that currency. When a new version is made, the old gateway plan is marked superseded. Where the gateway has an API for it, the old plan is also deactivated (PayPal) or archived (Stripe). Razorpay has no such API, so there the change is recorded on our side only.

At each subscription's switch date, the worker asks the gateway to move it:

  • Razorpay: update the subscription's plan with the change scheduled for the cycle end (card subscriptions only).

  • PayPal: revise the subscription to the new plan. If PayPal wants the buyer to approve, we e-mail them the approval link.

  • Stripe: swap the subscription item's price with proration turned off, so the running period is not charged again.

Our record moves only when the gateway confirms, by webhook or in its API answer. If the gateway refuses, nothing is forced. The subscription is set to end at the cycle end, and the customer gets an e-mail with a link to subscribe again at the new price.

The books always add up

Every payment and every invoice records the price version it was for. Each subscription keeps a history of which version it was on, from when to when, and what moved it. That history is on the subscription page and in the CSV exports, next to the gateway plan id. An accountant can answer "what did this customer pay, and why" without asking an engineer.

Nothing that was used can be deleted: not a version, not a plan, not an app. Instead you retire a plan, which stops new sales at once while existing customers carry on until they cancel or their term ends.

Read more

REM Payments is at rempayments.com. Questions: support@remplatforms.com.

AIProduct

REM Credits: one ledger for every REM app

AI actions in REM apps are paid for in REM Credits. All of them are kept in one ledger, in REM Payments, with every movement and its reason. Here is how credits are granted, spent and taken back.

RREM Team18 Nov 2026 · 3 min read
Product

One sign-in for every REM app

Every REM app now signs people in through REM Auth. One account, one password, one set of second factors - and apps that never see your password. Here is how it works and why we built it this way.

RREM Team18 Nov 2026 · 3 min read
How REM Payments changes a plan's price without breaking a single subscription · REM Platforms Blog