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

Add 24 hour notification to Stripe receipt custom message #10

Open
vanderaj opened this issue Jul 28, 2021 · 2 comments
Open

Add 24 hour notification to Stripe receipt custom message #10

vanderaj opened this issue Jul 28, 2021 · 2 comments

Comments

@vanderaj
Copy link

Please add that a custom message to the Stripe receipt, to let folks know that they should receive a follow up email with instructions on how to claim their owasp.org email. That way they know that it's not immediate and avoiding client contact tickets that are working sort of as intended.

Also, try to reduce this time. I think folks are looking for immediate access to this stuff. If there's a day delay, please find out why.

@hblankenship
Copy link
Contributor

First, a primer on what is happening:
A person signs up
A person is added to mailchimp if they do not exist
When mailchimp membership email notifications run (once a day), they receive an email. <-- This is why it can take up to 24 hours

Now, regarding the receipt, that is a stopper because we are using Stripe automatic receipts and they are not customizable.

There are two solutions:
1.) start using customized receipts (we create the receipt when the membership gets created in the back-end)
or
2.) we automatically send a 'welcome' email to the member when membership gets created.

In the first instance, I think we should not do it - it is re-inventing the wheel and there are legal issues to address (making sure we get all required data for receipts).

In BOTH instances, it requires that we use SendGrid to send the email and we are using a rate limited account here; the fewer SendGrid emails we send the better.
I clearly do not favor choice 1 so, addressing choice 2:
We will need to create a template in SendGrid that basically duplicates information from Mailchimp's template
We will need to implement code in the back-end to send said mail.
We will need to turn off or modify the 0-day email from mailchimp so that it doesn't duplicate what we've sent already or seem spammy.
We MAY need to pay for SendGrid if our limits are exceeded.

You are good with moving forward with choice 2? Time/effort versus responding to tickets in JIRA seems reasonable?

@hblankenship
Copy link
Contributor

Per Andrew, update membership-success.md :
https://github.com/OWASP/owasp.github.io/blob/main/pages/membership-success.md

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

No branches or pull requests

2 participants