#Tomac-stripe-js-confirm

1 messages · Page 1 of 1 (latest)

untold sleet
#

Hi 👋 I'm not entirely certain off the top of my head, but could you provide an example of each type of behavior that I could take a closer look at? The IDs of the related Payment Intents would help me find that.

severe scaffold
#

I usually create a POST request in the callback to redirect the user to a page to indicate the payment went through. But on my apache log, I don't see this POST request for some payment

#

for instance this payment is problematic on my side: pi_3LSnc5JCVzpqzxax1mVgP7n0 for Stripe side everything is normal

#

but pi_3LSkngJCVzpqzxax0JOL6CYU is working fine (same stripe account, same date than the previous one)

#

I did not find a common pattern for all of the payment which seems to miss the redirect (4% of all processed payments on the account)

#

so my guess is that after the payer finish the 3D secure authent he just closes the browser but it seems a weird behavior

untold sleet
#

That aligns with what I'm thinking may be happening. I looked at the first payment that you referenced, and as far as I can tell it all worked as expected. This is leading me to suspect that your customers may be completing the authentication, and then immediately closing their browser (or possibly losing network connection) before the redirect back to your success url can occur.

severe scaffold
#

yes, just wanted to ask if you were aware of similar problem is the past, because I am sure I would not be alone to rely on this callback to complete my payment workflow

untold sleet
#

Yeah, we don't see it happen too often, but we always warn about it being a possibility and it's why we recommend using webhooks for handling downstream processes rather than relying on processing triggered from your success url.
https://stripe.com/docs/webhooks

Use incoming webhooks to get real-time updates

Listen for events on your Stripe account so your integration can automatically trigger reactions.