How to update Stripe checkout redirect URLs when changes aren't taking effect after an hour? Answered

Post author
Shadi null

How long does it usually take for plan redirect logic changes to take effect? 😮
I changed where users are supposed to be redirected after buying a specific plan (on signup) but it still seems to be sending them to the old location (/welcome) instead of an onboarding form.
It's been roughly an hour now and it is still linking to the old redirect after stripe checkout

Comments

8 comments

  • Comment author
    Tyler Bell

    It should be instant.
    Did you make the update on the plan itself?

    Or did you update the default redirect?

    0
  • Comment author
    Shadi null

    Yea, I updated the plan itself and then deleted the default redirect as I assumed it might conflict

    0
  • Comment author
    Tyler Bell

    Ah do you happen to have a redirect set on your signup form?

    That would override redirects set in the dashboard.

    0
  • Comment author
    Shadi null

    The purchase transpires after signup so I dont think that is the cause in this instance. The plan is formatted as an addon, so users are already signed in when they are redirect to stripe for checkout.

    The only redirect referencing the /welcome page is the free plan, whereas the annual membership plan they would be upgrading to should redirect to /profile-setup with an onboarding form

    0
  • Comment author
    Tyler Bell

    Got it. Thanks makes sense.
    Feel free to send me you appId and I can take a closer look.

    0
  • Comment author
    Shadi null

    I appreciate it!

    One more question Tyler Bell
    I noticed that memberstack custom attributes have some issues on pages like 404 pages. For example my login function is done via just giving a button a data-ms-modal="login" attribute, however on pages like error 404 those attributes don't work (in this instance when logged out on the 404 page the login button vanishes).

    I also noticed this applies when you're logged on and have a navbar with Memberstack attributes (like ms-code-field-link=profile-link")

    Attributes such as data-ms-content="members" work on the 404 page, so it seems to be limited to only a select few

    0
  • Comment author
    Duncan from Memberstack

    Idk if this was sorted - but wanted to throw this out there. Usually when this happens it’s an issue with plan priority. https://docs.memberstack.com/hc/en-us/articles/11819235317147

    0
  • Comment author
    Shadi null

    I appreciate the help!
    It’s sorted now :)
    It was exactly as you said

    0

Please sign in to leave a comment.