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

Incorrect stripe handoff #392

Closed
jamesgeddes opened this issue Oct 15, 2021 · 5 comments · Fixed by #616
Closed

Incorrect stripe handoff #392

jamesgeddes opened this issue Oct 15, 2021 · 5 comments · Fixed by #616
Assignees
Labels
blocker These are blocking further development. Most urgent and important. bug Something isn't working P1 Issues that are both high impact and urgent pre-go-live Required for MVP

Comments

@jamesgeddes
Copy link
Contributor

jamesgeddes commented Oct 15, 2021

When returning from stripe after the initial direct debit setup, the user is sent to

https://test.geek.zone/memberships/confirm/

This asks them to set up their direct debit which they have just done.

Users should be sent to a page that thanks them for setting up their direct debit and directs them to complete their member details.

The user should be considered a member from the moment they set up their direct debit. If the direct debit subsequentially fails, the member should be told to set up a new direct debit.

Impact

High

Urgency

Now

@jamesgeddes jamesgeddes added bug Something isn't working P1 Issues that are both high impact and urgent labels Oct 15, 2021
@SamWinterhalder
Copy link
Contributor

SamWinterhalder commented Oct 17, 2021

Just a little nudge in the right direction - I wasn't sure if it would work well enough (it appears not), but I essentially wrote to the database when the member has made payment and then in the redirect checked if this value in the database existed.

I think the most likely problem is that it does not write to the database, before the check is made in the redirect, it is just not quick enough. What made this hard for me was that there is no guaranteethat the payment will be made, it can take up to 72 hours for a payment to go through, and it could not be successful at any time up to that point.

web/memberships/views.py

Lines 230 to 233 in a00d665

@login_required()
def settings_view(request):
if not check_member_paying(request.user):
return HttpResponseRedirect(reverse("confirm"))

@blackbird7958 blackbird7958 self-assigned this Oct 17, 2021
@jamesgeddes
Copy link
Contributor Author

@SamWinterhalder thanks muchly, very helpful.

@blackbird7958 If we can tell the user a bit more info then this will be less confusing for them.

@jamesgeddes jamesgeddes added the blocker These are blocking further development. Most urgent and important. label Jan 29, 2022
@blackbird7958 blackbird7958 removed their assignment Feb 13, 2022
@jamesgeddes jamesgeddes added the pre-go-live Required for MVP label Feb 20, 2022
@crouchingtigerhiddenadam crouchingtigerhiddenadam removed their assignment Feb 26, 2022
@jamesgeddes
Copy link
Contributor Author

Just to confirm, we have decided that the user should be considered a member from the moment they set up their direct debit. If the direct debit subsequentially fails, the member should be told to set up a new direct debit.

@Freshrojek
Copy link
Contributor

Had a chat with @crouchingtigerhiddenadam earlier and we think we are gonna 🪓 the code mentioned above, because in tasks.py there's already a decent check for if a member doesn't have the right perms after a certain amount of time. So we think we are just going to edit that

@jamesgeddes jamesgeddes added P? Awaiting priority assignment and removed P? Awaiting priority assignment P1 Issues that are both high impact and urgent labels Apr 13, 2022
@geekzonebotold geekzonebotold added P1 Issues that are both high impact and urgent and removed P? Awaiting priority assignment labels Apr 24, 2022
@Freshrojek
Copy link
Contributor

Hey 👋🏼 @crouchingtigerhiddenadam how's this ticket going? Let me know if you need a hand or get bored of it or something lol

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
blocker These are blocking further development. Most urgent and important. bug Something isn't working P1 Issues that are both high impact and urgent pre-go-live Required for MVP
Projects
None yet
Development

Successfully merging a pull request may close this issue.

6 participants