#beemster_pi-redirect
rapid craterBOT
👋 Welcome to your new thread!
⏲️ We'll be here soon! Typically we respond in a few minutes, but sometimes we might take a bit longer if the server is busy or if you have a particularly tricky question.
⏱️ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can always start a new thread if you have another question.
🔗 This thread will always be available, even after it's closed. You can find it again using Discord's search, or you can save this link: https://discord.com/channels/841573134531821608/1401938760689778698
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
mild notch
Hi there 👋 I'm spinning up a test integration to double check what we send within that.
My understanding is that payment_intent and payment_intent_client_secret are the values that we'd append to the return_url you provide:
https://docs.stripe.com/payments/accept-a-payment?platform=web&ui=elements#web-submit-payment
Can you clarify what other query params you're seeing appended there?
scenic portal
We always see a redirect_status appended. Up until recently it always had the value succeeded. But now we also see the value pending, which makes us wonder how to handle it.
rapid craterBOT
scenic portal
And example we saw: /fr-ch/payments/components/verify_payment/stripe?payment_intent=[...]&payment_intent_client_secret=[...]&redirect_status=pending&sale_token=[...]
The sale_token is ours, the others (payment_intent, payment_intent_client_secret, and redirect_status) are appended by Stripe.
rapid craterBOT
rough forge
beemster_pi-redirect