Customer portal links can now be returned in API

Customer portal – which is basically a Quiz with new blocks "Subscriptions list" and "Cancel subscription button"

Now, you can get the link to this portal from API /subscriptions and in webhook

To create customer portal

Copy "Manage subscriptions" Quiz from "Quizzes & Pages => New quiz from template" section
Edit it as you wish
In project settings, in Stripe/Paddle/PayPal tabs, add a link for Customer Portal in a format
[https://quiz.YOURDOMAIN.com/manage-link?user_id={user_id}

You need to pass user_id to the link, so the user will be authorized in their customer portal.

Next, you will receive individual link in API and webhooks and you can present this link to a user in your mobile app, in emails, or in your customer support, when a user wants to cancel their subscriptions

Subscription Cancellation with Downsell offer

Quick setup checklist

Copy downsell template

Use "Button Update Subscription" to offer downsell
Hardcode the offer – e.g. always use "50% OFF"
Define Downsell price ID for each Downsell price in Button settings
1. Main price ID 1 => Downsell Price ID 1
2. Main price ID 2 => Downsell Price ID 2
3. 37837 => 21988
4. 37823 => 21129
Use selected_subscription.price.id in the Conditions to modify target prices
Skip screen with "Button Update Subscription" for each Downsell price, so user will not be in constant loop

Detailed setup (step-by-step, as in the video)

Subscription cancellation flow with downsell offer

Use this flow to let users cancel subscriptions while offering a personalized downsell price before final cancellation.

1. Start from the downsell template

Create a new quiz from the Downsell template so you don’t have to build the flow from scratch.

The template already includes the key blocks and screens for subscription selection, confirmation, downsell, and cancellation. You will only adjust content, prices, and conditions to match your offers.

2. Show user subscriptions

Add the User Subscription List block to the first screen of your flow.

For the API/Deeplink: with user_id passed from a deep link or another source so the user is auto-authorized and sees their own subscriptions in the list.
Let the user select which subscription they want to cancel, and optionally show a “reason for cancellation” question and custom follow-up screens (for example, if they choose “Other,” show an extra text question screen).

3. Build confirmation screens before cancellation

Insert 1–2 “are you sure?” confirmation screens between subscription selection and actual cancellation to reduce accidental churn.

A typical pattern is:
- Screen 1: title, paragraph, and two buttons:
  - Keep plan → sends user to a “Great choice” / “Glad you decided to stay” screen (no cancellation happens).
  - Cancel plan → sends user to the next pre-cancellation screen.
- Screen 2: repeat confirmation (“Are you sure?”) with the same logic:
  - Yes, keep plan → “Great choice” screen.
  - Still cancel → sends user to the downsell offer screen.

4. Configure the downsell offer (Button Update Subscription)

On the downsell screen, use the Button Update Subscription block to switch the selected subscription to a lower-priced Stripe price instead of canceling.

In the Subscription_Id parameter set {subscription_id} placeholder that points to the subscription selected in User Subscription List, so the button updates the correct subscription for this user.
In the button settings, specifically the Price parameter downsell discounts cannot be calculated dynamically; instead, define a fixed discount (for example, 50% off) and create a separate mapping of “main price → downsell price.”

Example mapping table:

Main price A → Downsell price A
Main price B → Downsell price B
Main price C → Downsell price C

5. Set conditional overrides for each main price

In Button Update Subscription, leave the default price empty or set a neutral default.
Use the Price → Has Conditions to override the price based on the selected subscription’s price ID:
- Condition 1: if selected_subscription.price.id = MAIN_PRICE_1, set button price ID = DOWNSELL_PRICE_1.
- Condition 2: if selected_subscription.price.id = MAIN_PRICE_2, set button price ID = DOWNSELL_PRICE_2.
- Repeat for every main price you support.

In the Stripe create new downsell price and import it. In the Plans & Prices, import new prices and retrieve the downsell Price ID.

Conditional logic for the Price parameter to map base price with downsell price

This creates one rule per main price.

For On success of the downsell button, send the user to the “Great choice / Thanks for staying” screen so they clearly see that their plan has been updated instead of canceled.

6. Keep the standard cancellation path

Keep a User Subscription Cancel button in the flow for users who decline the downsell and still want to cancel.

This button should use the selected subscription and call the standard cancellation logic (for example, cancel at period end or immediately, depending on your configuration).

7. Handle users who already have a downsell or PayPal subscription

If a user accepted a downsell earlier and later returns to the Manage subscription flow, they will now see the subscription with the already discounted price.

For these cases, you should skip the downsell offer and send them directly to cancellation, because you don’t want to offer a second downsell on top of an existing one.

The same applies to subscriptions with PayPal payment system when subscription price updates are not supported via the downsell button.

On the pre-cancellation screen where you show the “Cancel plan” button that leads to the downsell offer:

Add conditions to Visibility → Has conditions parameter:
- selected_subscription.price.id is one of your downsell prices (user is already on a downsell), value hide
- selected_subscription.payment_system_label = PayPal (downsells not supported via this flow), value hide

Conditional logic for Visibility parameter to hide it from users that already purchased it or if you're using PayPal

For the User Subscription Cancel Button block that cancels the subscription immediately:

Hide this button by default (Visibility - hide).
Add inverse conditions to Visibility → Has Conditions it if:
- selected_subscription.payment_system_label = PayPal, value show
- selected_subscription.price.id equals any of your downsell prices, value show

Conditional logic to show the button if user already has purchased downsell or if PayPal is used

In this case, clicking the button sends the user directly through the cancellation (without going to the downsell screen).

8. Resulting behavior

With this setup:

First-time cancellation attempts on full-price Stripe plans will go through the pre-cancellation screens and receive a matching downsell offer based on the selected price ID.
Users on an existing downsell price, or those paying via PayPal, will skip the downsell screen and go directly to an immediate cancellation button.
You can extend the flow with additional questions, screens, or more complex conditions, but this structure covers the most common retention plus cancellation cases supported today.

Refunds and subscription cancellations right on the platform

Now you can refund users their payments and cancel their subscriptions right on the platform – no need to go to payment system and look for payment, everything from web2wave interface

It works for Stripe, Paddle, PayPal and Primer