Skip to content

Conversation

@xlisachan
Copy link
Contributor

@xlisachan xlisachan commented Jan 20, 2026

This pull request

  • Adds the following churn pages and en.ftl:
    • Error
  • Not Found
  • Cancel/component
  • Updates ChurnInterventionService
    • redeemCoupon to include churnType
    • determineCancelChurnContentEligibility to include additional reasons (subscription_not_active, already_canceling_at_period_end, adds cmsOfferingContent when needed
  • Updates SubscriptionManagementService to return subscription invoice information

Issue that this pull request solves

Closes: PAY-3434

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 verified that my changes render correctly in RTL (if appropriate).

Screenshots (Optional)

Reason: Eligible
Mobile
Screenshot 2026-01-20 at 6 10 14 PM

Tablet
Screenshot 2026-01-20 at 6 09 52 PM

Successfully redeemed
Mobile
Screenshot 2026-01-20 at 6 10 37 PM

Tablet
Screenshot 2026-01-20 at 6 10 50 PM

Reason: Already canceling
Mobile
Screenshot 2026-01-20 at 6 03 49 PM

Tablet
Screenshot 2026-01-20 at 6 04 03 PM

Reason: Discount already applied/Redemption limit exceeded
Mobile
Screenshot 2026-01-20 at 6 07 00 PM

Tablet
Screenshot 2026-01-20 at 6 06 49 PM

Reason: Subscription not active
Mobile
Screenshot 2026-01-20 at 6 01 51 PM

Tablet
Screenshot 2026-01-20 at 6 01 39 PM

Reason: No churn found
Mobile
Screenshot 2026-01-20 at 6 07 42 PM

Tablet
Screenshot 2026-01-20 at 6 07 55 PM

'churn-error-page-message-discount-already-applied',
{ productName },
`This discount was applied to a ${productName} subscription for your account. If you still need help, please contact our Support team.`
`This discount was applied to a ${productName} subscription for your account. If you still need help, contact our Support team.`
Copy link
Contributor Author

Choose a reason for hiding this comment

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

Updated as string in en.ftl is as follows:
churn-error-page-message-discount-already-applied = This discount was applied to a { $productName } subscription for your account. If you still need help, contact our Support team.

@xlisachan xlisachan marked this pull request as ready for review January 21, 2026 00:18
@xlisachan xlisachan requested review from a team as code owners January 21, 2026 00:18
Comment on lines 13 to 20
enum ChurnCancelErrorReason {
AlreadyCanceling = 'already_canceling_at_period_end',
SubscriptionNotActive = 'subscription_not_active',
SubscriptionStillActive = 'subscription_still_active',
OfferExpired = 'no_churn_intervention_found',
GeneralError = 'general_error',
RedemptionLimitExceeded = 'redemption_limit_exceeded',
}
Copy link
Member

Choose a reason for hiding this comment

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

It looks like this is never really used as an enum, just converted to an array of strings (and casted) below. I'd probably just switch this to an array of strings as const.

Comment on lines 308 to 311
return {
...result,
cancelContent,
};
Copy link
Member

Choose a reason for hiding this comment

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

[non-blocking] Imo we shouldn't combine return types like this. Instead return each separately.

return {
  cancelChurnContentEligibility,
  cancelFlowContent
}

This pull requests

Adds the following churn pages and en.ftl:
  Error
  Not Found
  Cancel/component
Updates ChurnInterventionService
  redeemCoupon to include churnType
  determineCancelChurnContentEligibility to include additional reasons (subscription_not_active, already_canceling_at_period_end, adds cmsOfferingContent when needed
Updates SubscriptionManagementService to return subscription invoice information

Closes PAY-3434
@xlisachan xlisachan force-pushed the PAY-3434 branch 3 times, most recently from 3802d41 to 0b10821 Compare January 23, 2026 17:50
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.

4 participants