-
Notifications
You must be signed in to change notification settings - Fork 19
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
Success URL Redirect Not Working SCA? #292
Comments
Also just hit this issue... Forms doesn't seem to be respecting checkout Success URL set in admin or set in code via:
However success url in Stripe we're seeing is:
Craft version: 3.7.37 |
Could you please confirm if the order was created under Stripe Payments -> Orders? |
I can confirm that for mine it was.
… On 9 Jun 2022, at 16:32, Andre Lopez ***@***.***> wrote:
Could you please confirm if the order was created under Stripe Payments -> Orders?
—
Reply to this email directly, view it on GitHub <#292 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AQ35SD5I5L7WMUFHKCHQ4K3VOIE7DANCNFSM5YALO6WA>.
You are receiving this because you commented.
|
Mine was not under “Orders”.
From: gazlawn22 ***@***.***>
Sent: Thursday, June 9, 2022 11:36 AM
To: enupal/stripe ***@***.***>
Cc: beckbailey ***@***.***>; Author ***@***.***>
Subject: Re: [enupal/stripe] Success URL Redirect Not Working SCA? (Issue #292)
I can confirm that for mine it was.
On 9 Jun 2022, at 16:32, Andre Lopez ***@***.*** <mailto:***@***.***> > wrote:
Could you please confirm if the order was created under Stripe Payments -> Orders?
—
Reply to this email directly, view it on GitHub <#292 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AQ35SD5I5L7WMUFHKCHQ4K3VOIE7DANCNFSM5YALO6WA>.
You are receiving this because you commented.
—
Reply to this email directly, view it on GitHub <#292 (comment)> , or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAN5MH7TSBVR3NPUQVFLTT3VOIFO5ANCNFSM5YALO6WA> .
You are receiving this because you authored the thread. <https://github.com/notifications/beacon/AAN5MHZLFRH4XVZL7XRZZ7TVOIFO5A5CNFSM5YALO6WKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOISPUOSI.gif> Message ID: ***@***.*** ***@***.***> >
|
The @beckbailey Your issue sounds like a wrong webhook URL setup on Stripe. If you're working locally, are you using the Stripe CLI? @gazlawn22 After the order is finished, does the user is redirected to the 'checkoutSuccessUrl` ? |
@andrelopez - No I'm not using the Stripe CLI. This is happening in my local and production environments. |
Our client has reported a very similar issue. Intermittently, users are redirected to the Cancel URL not the Success URL, which is a problem in this case as they can not complete the form they are paying access to. This doesn’t happen for every order and we noticed an anomaly with the most recent record our client informed us about in that the user was recorded as Guest. This is weird as login is required before the user can gain access to this section. All other orders has a correctly assigned user. SCA is enabled for this website. We are running Stripe Payments 3.4.2. Craft Pro 3.7.37. We are about to deploy an update to Stripe Payments 4.0.6 as part of wider system updates, but this has not be actioned as yet. We will also be bumping Craft to 3.7.48. Just mentioning this in case it is session related. Anyway, I thought I would share this information in case it helps uncover what may be causing this issue. We are still actively monitoring the website, so if we have another reoccurrence or uncover anything we will share it here. |
Description
My success URL redirect is not working. In the Stripe log, the success_url looks like this:
https://mydomain.com/enupal/stripe-payments/finish-order?session_id=cs_test_a10l2JKNKRFdFQfqnoC2u2XE2BogBBOqIvNAQvPa3gYuMfHVuVw1XYLaMg
However in the Craft admin, my checkout success url looks like this /thank-you?number={number}
I should state the cancel URL works fine and matches in the Stripe log and Craft Admin payment form setting field.
Steps to reproduce
Additional info
The text was updated successfully, but these errors were encountered: