#dino_pephanis - webhook inconsistencies

1 messages · Page 1 of 1 (latest)

gilded umbra
#

Hello, what inconsistencies are you seeing?

summer hill
#

if you look at test account acct_1Lcq5g2UbDFqJf5w

#

onboarding is complete and the account is active.

#

however evt_1Lcqk92UbDFqJf5wRLzDDXZ2

#

there are alot of currently_due items

#

some which have been supplied. like "tos_acceptance.date", "tos_acceptance.ip"

#

The final request was req_GijcZQnty0blI7

#

where I pass some of the information missing.

gilded umbra
#

Thanks for the details. Checking in to what happened there

#

Also apologies for the delay

summer hill
#

Hello

gilded umbra
#

How was that TOS acceptance initially supplied, was that in another API call to update the account there?

summer hill
#

The request I sent is the final request in our boarding process. User checks all details & confirms tos as well as all directors, executives & owners provided

gilded umbra
#

Ah gotcha, that request came an hour after the event though it should have created another event here. Did you not get an event or get an event that still didn't have the tos related things set?

summer hill
#

the request was at 31/08/2022, 15:10:13
the event was at 31/08/2022, 15:13:47

#

there as was also and event at 31/08/2022, 15:10:17 not sure how long webhooks take

#

evt_1LcrcS2UbDFqJf5wZzavTQgU

gilded umbra
#

From what I see evt_1Lcqk92UbDFqJf5wRLzDDXZ2 was sent at 14:13:09

#

It does look like evt_1LcrcS2UbDFqJf5wZzavTQgU was the response to that call that updated tos_acceptance and that event does have the values that you provided

summer hill
#

OK when I setup a webhook for accounts should I listen to: Events on your account or Events on Connected accounts

gilded umbra
#

For this it would be events on connected accounts. That is how your platform would see this account.updated event

summer hill
#

Ok this that's what I did

#

evt_1Lcqk92UbDFqJf5wRLzDDXZ2 was the last event I could view in the developers section of the dashboard

#

I had to log into the connected account to view event evt_1LcrcS2UbDFqJf5wZzavTQgU

gilded umbra
#

As in you can currently see up to evt_1Lcqk92UbDFqJf5wRLzDDXZ2 in your platform's dashboard? I did not realize that the platform could see connect events like that in the dashboard

summer hill
#

Yeah. Developers > Webhooks click on Endpoint URL

#

You get a list of events

gilded umbra
#

Gotcha. So is that clarification on the endpoint type helpful for what to do next? Or do you still need help here?

summer hill
#

are you able to view

#

event evt_1LcrcS2UbDFqJf5wZzavTQgU

#

is line 165 "tos_acceptance": {

slim yoke
#

👋 stepping in here as Pompey needs to step away

summer hill
#

OK

slim yoke
#

Catching up

summer hill
#

no porblem

slim yoke
#

So you are seeing unexpected data in the account.updated hook?

summer hill
#

trying to understand why - I boarded a connect account

#

acct_1Lcq5g2UbDFqJf5w

#

in my dashboard it is complete with no missing data

#

and is enabled

#

event evt_1LcrcS2UbDFqJf5wZzavTQgU

#

which i believe was the webhook call

slim yoke
#

Yep that all looks good

#

I don't see anything in requirements for that event

summer hill
#

i see

 "requirements": {
      "current_deadline": 1663158742,
      "currently_due": [
        "company.directors_provided",
        "company.executives_provided",
        "company.ownership_declaration.date",
        "company.ownership_declaration.ip",
        "directors.dob.day",
        "directors.dob.month",
        "directors.dob.year",
        "directors.email",
        "directors.first_name",
        "directors.last_name",
        "directors.relationship.title",
        "executives.address.city",
        "executives.address.line1",
        "executives.address.postal_code",
        "executives.dob.day",
        "executives.dob.month",
        "executives.dob.year",
        "executives.email",
        "executives.first_name",
        "executives.last_name",
        "tos_acceptance.date",
        "tos_acceptance.ip"
      ],
#

line 186

#

line 105:

#
"requirements": {
      "alternatives": [
      ],
      "current_deadline": null,
      "currently_due": [
      ],
      "disabled_reason": null,
      "errors": [
      ],
      "eventually_due": [
      ],
      "past_due": [
      ],
      "pending_verification": [
      ]
slim yoke
#

Line 186 is previous_attributes

#

That is what was true of the account before

summer hill
#

OK

#

thanks

#

that's what threw me

slim yoke
#

np!

summer hill
#

for KYC, how long does it take for an account to be verified

slim yoke
#

Depends

#

It is pretty quick

#

But it is async

#

So can't really give a firm time

summer hill
#

once it has been verified will it fire and account updated event

slim yoke
#

Yep

#

Any time anything changes on the account an account.updated will fire

summer hill
#

OK that's what I want to use it for, once the account confirmed and all persons verified to email the that their account is active

slim yoke
#

Yep that's exactly what you should be doing

summer hill
#

excellent thanks for youe help

#

enjoy the rest of your day