Move payments without rebuilding plan logic
Changing providers puts checkout, payment methods and renewal dates in motion. Keep your plans, versions, grants and usage in Entitler so customer IDs and entitlement checks stay the same throughout the migration.
Explore the example- Before the movePayments with your old providerHas access. Comes from SSO add-on.
- After the movePayments with your new providerHas access. Comes from SSO add-on.
Where your apps look for access
Keep customer entitlements independent of provider-specific billing data, so a payment migration does not require new access logic.
- Plans
- Add-ons
- Grants
- Subscriptions
- Renewal dates
- Listings
- Payments
- Refunds
- Invoices
Your apps keep the same customer IDs and entitlement checks throughout the payment move.
A payment migration with the same customer terms
Follow Alice’s Pro plan and SSO add-on while her software provider moves billing. The example shows the work your integration still needs to do when payments succeed or fail.
Step 1 of 4: Review Alice’s subscription
A payment migration must preserve Alice’s Pro plan, SSO add-on and next renewal. Inspect those records before setting up the replacement subscription.
ProductionLive- AI credits212 of 500 used this periodAccess source Pro, version 2
- Export to PDFYesAccess source Pro, version 2
- Priority supportYesAccess source Pro, version 2
- Single sign-onYesAccess source SSO add-on
- Support SLA24 hoursAccess source Pro, version 2
- Added SSO17 Sep 2026
- Subscribed to Pro, monthly7 Sep 2026
Alice holds Pro and the SSO add-on under cust_1001. Use her customer reference and renewal date to prepare the new billing subscription. Your team arranges payment methods and billing history separately.
Entitler’s role here, and your billing provider’s
Entitler manages the plan terms and customer entitlements, and charges plan changes to a connected Stripe account. Your billing provider handles the money; with a provider other than Stripe, your integration records the subscription changes.
Customer terms
- Stores your plan catalogue and each customer's subscriptions, grants of extra access and renewal dates
- Provides customer entitlement checks independently of your payment provider
- With a Stripe account connected, opens checkout, subscribes customers once Stripe takes the payment and charges plan changes to the price each listing names
- Records the source of every purchase, such as a Stripe account, the App Store or Google Play, and whether its money is real or test
- Applies renewals, scheduled plan changes, cancellations and grant expiry
- Uses your own customer IDs across providers
- Provides test environments, with test customers and a clock you can move forward, for migration testing
Payments and billing
- Processes payments, issues refunds and sends invoices
- Stores product and price definitions
- Holds payment methods and billing history; your team arranges their transfer during a migration
When the provider’s records break your rules
Your business rules live in Entitler. Stripe records any subscription it is given, and the App Store and Google Play will follow the same model. Entitler shows each customer’s subscriptions exactly as the provider has them, and raises an alert for each rule they break.
- 1
Your rules live in Entitler
In your catalogue, Docs is a product, and a customer holds one Docs plan at a time. Stripe has no record of that rule.
- 2
Stripe accepts a second subscription
A teammate creates another Docs subscription for Ana in the Stripe dashboard. Stripe bills it and reports it to Entitler.
- 3
Ana’s page shows both, as Stripe has them
Entitler lists both subscriptions under Stripe on her page, unchanged, and raises an alert naming the rule they break.
- 4
You fix it in Stripe
Cancel the extra subscription in Stripe and refund it there if needed. Once Stripe reports one subscription again, Entitler resolves the alert.
ProductionLive- sub_1PqA4dLk2Xb8Active3 Oct 2026 to 3 Nov 2026Sells Docs Pro, Monthly, version 4price_1Pq0DocsProM × 1
- sub_1QxT7eMn9Rw3Active2 Oct 2026 to 2 Nov 2026Sells Docs Pro, Monthly, version 4price_1Pq0DocsProM × 1
More billing changes that leave access alone
Keep customer entitlements consistent as your billing setup changes.
Moving customers in waves
You need a staged migration rather than a single cutover. Point a Beta track at the new Stripe account first, with its own listings, so new purchases on Beta go there while All customers keeps the old account. Existing subscriptions keep billing where they started, and each customer's renewal date schedules their first charge with the new provider.
Paying through the App Store, Google Play and the web
Customers subscribe through different stores, but need consistent access across your apps. Record each customer's subscription in Entitler from any payment source, through the API or through a provider connection. Each purchase keeps its source, so support can see where it was bought.
More on answering access questionsA charge fails after the move
A customer’s first payment with the new provider does not go through. With Stripe connected, when Stripe stops billing a paid plan after failed payments, Entitler returns the customer to your default plan. With another provider, cancel now or at the end of the paid period yourself. Refunds stay with the provider.
New prices, same features
The move is a good time to change your prices. Create the new prices with your billing provider; Entitler never creates them. With Stripe connected, set each new price as a listing when you roll out the next release, or on the track’s page, where it takes effect at once. If features change too, release a new plan version and choose when customers receive it.
More on approving changes
Questions about changing provider
More solutions
Explore all solutions, organised by team, company size, industry and use case.
Try your plans in Entitler
Start with sample plans and customers. Then try a change you expect to make, such as a new tier, a usage allowance or an exception for an early customer. Request an invite to try it with your team.