#Jordy

1 messages · Page 1 of 1 (latest)

rugged yokeBOT
spice orchid
#

Hi 👋 not sure I understand. That is an error being returned to a request, you can catch that in your code that makes the request without using a webhook.

thick finch
#

Ok, that makes sense. I'm using a no-code, bubble.io to send these payment requests but I'm having trouble figuring out a way for the user to know there's an issue and I thought a webhook would tell me

#

acct_1MvhThPHji0EFnx2 for this account, we used accurate data but it still won't verify it. Is it because there's another account in the connect tab with this info?

#

and if so, how do I delete them because stripe says it will only verify once

spice orchid
#

It looks like that account is missing an External Account, and that the ID is coming back as not verified.

thick finch
#

Does that mean I didn't send stripe the correct information then?

spice orchid
thick finch
#

Thank you for this. We were using actual data instead of test id numbers

spice orchid
#

Gotcha, that is expected to fail in that case.

rugged yokeBOT
thick finch
#

Interesting

#

Back to the original message, what is the best way for me to know there's an error with our request?

#

Is there a stripe.js message that would send? That's what I used to build this integration?

#

The bad news (for me) is I am taking over for another developer so I'm trying to figure it out afterwards why certain decisions were made

spice orchid
#

To know if there was an error with a request, you should wrap it in a try/catch block.

Webhook events are for being notified about things that are happening outside of requests you're making. What is it that you want to be notified about?

thick finch
#

That the user's status is restricted and for what reason so that they can resubmit and have it, eventually, be verified

spice orchid
#

You'll want a Connect webhook endpoint, likely listening for account.updated events at least, capability.updated may also be useful.

account.updated events will be triggered whenever a Connected Account is updated. You can then check the fields on the account to understand its state.

payouts_enabled, charges_enabled, and the capabilities hash are places to look to determine what the account is allowed to do.

requirements and future_requirements are where you look to see what information is required, when, and see if there were errors processing the previously provided information.