Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Don't send 'automatic payment' email for subscriptions with non-authenticated payment methods #508

Open
BethanOFN opened this issue Jun 4, 2024 · 0 comments

Comments

@BethanOFN
Copy link

What is the need/problem?

When an order cycle closes which has attached subscriptions, subscription customers are sent an order confirmation email and an 'automatic payment has been processed' email. For customers with a card on their subscription, this email alerts them that they've been charged automatically. For customers with a non-authenticated payment method (e.g. cash on collection/BACs) on their subscription, this email is confusing as they have not provided an automatic payment method. Customers are therefore getting confused, and producers want to be able to turn off this automatic email.
Screenshot 2024-06-04 at 15 10 48

What type of users does this affect (and how many, if known)?

Shoppers (who receive the email and are confused)
Hub Managers (who have to deal with confused customers)
Producers (who have to deal with confused customers)

Potential solutions that could solve the problem?

  • Amend the email logic such that the 'automatic payment has been processed' email is only sent to subscriptions with an authenticated payment method attached. Authenticated payment methods are those with:
    spree_payment_methods.type = Spree::Gateway::StripeSCA
  • Changing the email content in transifex was considered, however trying to rewrite it to suit both scenarios (you've been automatically charged/you've not been charged and may or may not need to pay) was too long and confusing

Additional context

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Candidates
Development

No branches or pull requests

1 participant