#darius-events

1 messages · Page 1 of 1 (latest)

thorny plaza
#

Hey! That's quite a range of failures to cover, are you seeing any specific issues in your integration?

#

Requirements will likely be updated throughout verification, and you might need to bring your users back on-session to provide additional requirements

#

The payments question generally depends on what kind of payments you're processing?

old parcel
#

For Payments, we are using the transfer capability. And using the Destination charges type.
When the Buyer first sends a buy request, we create a setupIntent (usage on-session) just to save the cards details, we use that card for the future on session payments.

thorny plaza
#

So the majority of your payments are on-session?

old parcel
#

Requirements will likely be updated throughout verification, and you might need to bring your users back on-session to provide additional requirements

About this, I was always wondering. How can we detect when Stripe changes the requirements? Is it the capability.updated event on the webhook?

thorny plaza
#

It'll be the account.updated event

old parcel
thorny plaza
#

If your payments are on-session then the majority of payment failures should be handled by your integration

old parcel
#

It's working fine from my test. But we're just in the test mode and this is the first time I'm integrating Stripe.
So it's mostly prevention work for now.

#

Alright, good to know that! Thanks 🙂

thorny plaza
#

i.e. if 3DS is requested, Stripe.js will handle that (which is payment_intent.requires_action)

#

Let me know if you have any specific concerns!