#Lorey-returnurl
1 messages · Page 1 of 1 (latest)
hi! we don't. really document that unfortunately
I would just test it in test mode, the parameters you see can be relied on, as far as I know we do add &payment_intent=pi_xxx so you can reconcile with that.
Hi @misty quarry thanks for responding so quickly!
Is this something you plan on adding?
It feels like relying on parameters that aren't really supported
Would it be better if we were to add the payment_intent_id ourselves? To avoid regression in the future?
no direct plans, I agree with you
well really the safest solution is webhooks. Ultimately we won't change this since even if we don't document it explicitly anywhere, we completely know people use those params and reply on them so we are unlikely to change them
We are using webhooks! 🙂
We just need a reference to the original payment intent once the user lands on the return_url page
So we can verify the payment_intent's status and redirect the user to the correct page
yep makes sense
Alright, well thank you for your answer!