#.abishek

1 messages ยท Page 1 of 1 (latest)

fair iglooBOT
proven garnet
#

๐Ÿ‘‹ happy to help

proven stag
#

ch_3Nx7ZZ25zCqxTDIn1udniSrl

#

cs_test_a1tNiN49OnHHeqexmGICHuclLOuD4HOTqqRj3P0OvIJ4u5rycC0kJ3Lgjo

proven garnet
#

still checking

#

would you mind creating a new test checkout session and share the ID?

swift rapids
#

Hi there ๐Ÿ‘‹ jumping in as my teammate needs to step away soon.

#

That is expected behavior, the success URL will not have payment information appended to it. You can configure it so that the Checkout Session's ID is appended to that URL, so that you can look up details of the session afterward. You success URL is currently not set up that way. Instructions for setting that up can be found here, but let me know if that doesn't allow you to do what you're hoping.
https://stripe.com/docs/payments/checkout/custom-success-page#modify-success-url

proven stag
#

Thank you @swift rapids @proven garnet

swift rapids
#

Any time!

proven stag
#

can the checkout session tell me if the payment was captured succesfully?

#

ah, the payment_status should tell me

swift rapids
#

Yup, that should do it

proven stag
#

therea are no other edge cases right? the success url is always reached after all 3DS redirects and payment completions. correct? and if the customer cancels the transactions at the 3DS bank page, it will redirect back to the cancel_url correct?

swift rapids
#

We will always redirect there, but we can't guarantee the customer will actually make it to the page. They could unexpectedly lose network access, or they could close their browser window/tab before the redirect completes. Are you planning to use this for triggering post-payment processes?