#Rider-3DS

1 messages · Page 1 of 1 (latest)

scenic sonnet
#

Hi there, yep this is definitely a possibility and why we recommend to use webhooks for fulfillment.

oak kindle
#

All my logic should be in the webhooks page, and the confirm page should juste be a façade ?

scenic sonnet
#

No, you should have a webhook set up to ensure that all orders are fulfilled.

#

So you can handle most via your confirm page if you want (or you can just use it as a UI for the customer) but then you double check with your webhook so you don't miss any customers that dropped off.

oak kindle
#

Okay I will work on that. Thanks

#

And what I have to do with people who never confirm the 3DS ?

scenic sonnet
#

Nothing as then the payment won't be completed

oak kindle
#

A cronjob to disable order after 5min is OK ?

#

Yes but my order still in pending pp

scenic sonnet
#

You would handle it the same as any other order that has been started but not completed

#

So yes... something that discards that order

oak kindle
#

This is a reservation website so I need to free the booking

scenic sonnet
#

Gotcha

oak kindle
#

if payment not complete

scenic sonnet
#

Then yeah, you would want to determine a reasonable time frame

#

And you likely want to cancel the PaymentIntent at that point as well if 3DS was started

#

So that it can't be completed later after your "timeout" period.

oak kindle
#

OK I got it 🙂

#

Thanks a lot

scenic sonnet
#

Sure!

oak kindle
#

Do I need a little timer on my confirmation page to be sure the webhooks got fired ?

#

Maybe 2s ?

scenic sonnet
#

No webhooks are based on actions with Stripe

#

So they will fire based on the customer action and your API requests

#

Oh wait

#

Maybe I am misunderstanding you

#

You are talking about for displaying your success page?

oak kindle
#

Yes

#

Because if my confirm page check the PaymentIntents juste before the webhook got fired, the confirmation page will think the transaction failed

scenic sonnet
#

The typical way to do this is to handle everything from your confirm page so that you can show details to the customer instantly. However you also have a webhook set up to catch any disconnects — so when your webhook is hit you first check if the data has already been ingested, if so you skip doing anything with your webhook, if not then you ingest via your webhook.

oak kindle
#

Oh crap I was coding the opposite.... 😦

scenic sonnet
#

Well it is up to you

#

If you are okay with the delay for your success page

#

Then yeah just show a spinner for a few seconds and wait on the webhook

#

But webhooks are not synchronous and can take a few seconds to fire.

#

So there may be a bit of a delay.

oak kindle
#

Okay thanks for this precious informations 🙂