#darius-events
1 messages · Page 1 of 1 (latest)
Hey! That's quite a range of failures to cover, are you seeing any specific issues in your integration?
Specifically regarding Connect onboarding: https://stripe.com/docs/connect/identity-verification-api
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?
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.
So the majority of your payments are on-session?
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?
It'll be the account.updated event
Continue watching for account.updated event notifications to see if the requirements hash changes, and reaching out to your user for additional information as needed.
https://stripe.com/docs/connect/identity-verification-api#verification-process
Yes, most payments are on-session.
We also charge our connected acounts in certain cases. For this, we're using those debit charges I think they are called:
https://stripe.com/docs/connect/account-debits
Yeah, that's different to payments (those are transfers and aren't subject to same regulations like SCA, etc)
If your payments are on-session then the majority of payment failures should be handled by your integration