You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This ticket covers e-mails specific to Subscription Management.
–
Invoice emails currently have a strings like "Charged to Visa" and "card ending XXXX". This is the same information shown under "Billing Information" on the Subscription Management page. We should make sure the PayPal billing information is displayed instead for PayPal customers.
Per Barry:
There are 3 different types of e-mails right now that include the payment information if it’s there (it’d look for the last4 property on the Customer object), so we’ll have to update those ones to check if it’s Stripe or PayPal… Similar to FXA-2801 logic.
First invoice e-mail
Subsequent invoice e-mails
If they cancel and then resubscribe e-mail
Mini-spike:
These e-mails are driven by Stripe webhook events. Since we're manually invoicing with Stripe, we need to make sure whenever we update the invoice, we get the right webhook events. If we mark an invoice as paid, do we get the event that would trigger the payment succeeded e-mail? If not, we need to figure that out.
[~bchen@mozilla.com]: Does SubPlat own these emails? If so, how do we change them? If not, who do we need to contact?
This ticket covers e-mails specific to Subscription Management.
–
Invoice emails currently have a strings like "Charged to Visa" and "card ending XXXX". This is the same information shown under "Billing Information" on the Subscription Management page. We should make sure the PayPal billing information is displayed instead for PayPal customers.
Per Barry:
last4
property on the Customer object), so we’ll have to update those ones to check if it’s Stripe or PayPal… Similar to FXA-2801 logic.[~bchen@mozilla.com]: Does SubPlat own these emails? If so, how do we change them? If not, who do we need to contact?
┆Issue is synchronized with this Jira Task
┆Issue Number: FXA-2898
The text was updated successfully, but these errors were encountered: