#bachir-connected account capabilities

1 messages ยท Page 1 of 1 (latest)

west vault
#

๐Ÿ‘‹ happy to help

#

could you please share some examples (account ids)?

pine arch
#

Sure acct_1LDCjHQnb53ckbMR
You can see that the capability transfer was activated on the 6/24 during their onboarding even though they failed their document verification with verification_failed_keyed_identity error only because the current_deadline is set to the 7/1. On the 7/1, the capabilities are disabled due to the document verification being past_due.

west vault
#

I'll take a look

pine arch
#

Thanks

west vault
#

I'm having trouble with my connection, one of my colleagues will take over shortly

modern halo
#

Hello ๐Ÿ‘‹
Catching up here, give me a moment and I'll respond as soon as I can ๐Ÿ™‚ Thanks

pine arch
#

no worries, thanks

deep quiver
#

Hey, just pinging again that we are still looking in to this. So is your end goal here to make sure that the account is disabled immediately if that verification fails? Or are you more looking for an explanation on why?

pine arch
#

So is your end goal here to make sure that the account is disabled immediately
Yes - If this means that both capabilities card_payments and transfer are only activated when the ID document verification is also successful

deep quiver
#

Now that I look at that account again, I actually don't see the additional_verifications properties being passed when it was created. Did you add them with a later update? I am trying to find that in our logs but currently not seeing it

pine arch
#

From what I gathered, it's the pending_verification field that contains the documentation verification (see capability.updated event) https://dashboard.stripe.com/acct_1LDCjHQnb53ckbMR/events/evt_1LE5deQnb53ckbMRW4lu3FaB (you can see the current_deadline being set)

then here https://dashboard.stripe.com/acct_1LDCjHQnb53ckbMR/events/evt_1LE5e3Qnb53ckbMR3kupikzt you can see that they failed to verify, but the status of the capability is still active.

I might have been unclear, but we do not have any API integration for the ID document check, we did everything through the Connect > Settings section (see screenshot for the config)

deep quiver
#

Ah I see thank you. I was unfamiliar with the Additional Verifications functionality. I've reached out to my colleagues for help on this. Huge apologies on my delay here

deep quiver
#

We are still not seeing additional verifications set up on that account. For this it would probably be best to reach out to our support team for guidance on how to utilize the additional verifications tat you set up in the dashboard. It looks like they were not applied to that account and unfortunately I am not finding much on whether it should for accounts that you create through the API. https://support.stripe.com/?contact=true