Skip to content

feat(payments-next): Add Churn Intervention feature flag#19905

Merged
elizabeth-ilina merged 1 commit intomainfrom
PAY-3469-add-churn-feature-flag
Jan 22, 2026
Merged

feat(payments-next): Add Churn Intervention feature flag#19905
elizabeth-ilina merged 1 commit intomainfrom
PAY-3469-add-churn-feature-flag

Conversation

@elizabeth-ilina
Copy link
Copy Markdown
Contributor

@elizabeth-ilina elizabeth-ilina commented Jan 19, 2026

Because

  • We want to be able to enable/disable the churn intervention features using a flag.

This pull request

  • Adds a churn intervention feature flag.

Issue that this pull request solves

Closes: (issue number) #PAY-3469

Checklist

Put an x in the boxes that apply

  • My commit is GPG signed.
  • If applicable, I have modified or added tests which pass locally.
  • I have added necessary documentation (if appropriate).
  • I have verified that my changes render correctly in RTL (if appropriate).

Screenshots (Optional)

Please attach the screenshots of the changes made in case of change in user interface.

churn-intervention-flag.mov

Other information (Optional)

Any other information that is important to this pull request.

@elizabeth-ilina elizabeth-ilina force-pushed the PAY-3469-add-churn-feature-flag branch 2 times, most recently from e14c2cc to 9cfa36c Compare January 19, 2026 21:06
@elizabeth-ilina elizabeth-ilina marked this pull request as ready for review January 19, 2026 21:31
@elizabeth-ilina elizabeth-ilina requested a review from a team as a code owner January 19, 2026 21:31
@elizabeth-ilina elizabeth-ilina force-pushed the PAY-3469-add-churn-feature-flag branch from 9cfa36c to 96dbad4 Compare January 20, 2026 15:49
Copy link
Copy Markdown
Contributor

@StaberindeZA StaberindeZA left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

r+wc

Just a few questions and a nitpick, but looks good otherwise.

Just a note, this will also require an update to the env vars in webservice-infra before this change lands in Stage and ultimately Prod

public readonly collectionName!: string;

@IsBoolean()
public readonly enabled: boolean = true;
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nitpick: Even though the default is already set here, could it also please be added to apps/payments/next/.env?

Currently that file serves as an easy single source to see what the default values are for the service.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

question: should this rather be disabled by default?

Comment on lines +29 to +31
if (!config.churnInterventionConfig.enabled) {
redirect(`/${locale}/subscriptions/${subscriptionId}/stay-subscribed`);
}
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

question: should logic like this be added to other churn related pages?

For example, I see that .../loyalty-discount/stay-subscribed/error/page.tsx also makes a call to action determineStaySubscribedEligibilityAction

Because:

* We want to be able to enable/disable the churn intervention features using a flag.

This commit:

* Adds a churn intervention flag.

Closes #PAY-3469
@elizabeth-ilina elizabeth-ilina force-pushed the PAY-3469-add-churn-feature-flag branch from 96dbad4 to e62ac23 Compare January 22, 2026 15:17
@elizabeth-ilina
Copy link
Copy Markdown
Contributor Author

elizabeth-ilina commented Jan 22, 2026

Webservices-infra change: https://github.com/mozilla/webservices-infra/pull/9229
(older, not correct format change: https://github.com/mozilla/webservices-infra/pull/9222)

@elizabeth-ilina elizabeth-ilina merged commit 607202e into main Jan 22, 2026
20 checks passed
@elizabeth-ilina elizabeth-ilina deleted the PAY-3469-add-churn-feature-flag branch January 22, 2026 15:46
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants