#vizio_webhooks

1 messages · Page 1 of 1 (latest)

viscid mossBOT
#

👋 Welcome to your new thread!

⏲️ We'll be here soon! Typically we respond in a few minutes, but sometimes we might take a bit longer if the server is busy or if you have a particularly tricky question.

⏱️ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can always start a new thread if you have another question.

🔗 This thread will always be available, even after it's closed. You can find it again using Discord's search, or you can save this link: https://discord.com/channels/841573134531821608/1317090965554597908

📝 Have more to share? Add more details, code, screenshots, videos, etc. below.

Below are links to other discussions we've had with you in the past week in case you want to review that information. If your question is related to one of these previous discussions, please provide a comprehensive summary of the current state and what you need help with now. We help many users simultaneously, so a summary allows us to resolve your issue as soon as possible.

grim trout
#

Yesterday we received this webhook event https://dashboard.stripe.com/workbench/events/evt_1QVGdxDD3nZJlvMpeoIuWYyd and you can see that
"id": "pm_1QVGduDD3nZJlvMp7zLCcpIQ"
"fingerprint": "lcw0Es0Wup0jirtO"
"created": 1734026262

we also logs the events on our side and for that specific event id I have different data
id: "pm_1QVGduDD3nZJlvMp7zLCcpIQ"
fingerprint: "v5gdHZanzX9BCjAd"
created: 1734026262

naive kestrel
#

👋 happy to help

#

that's expected

#

the fingerprint is specific to each account

#

so the fingerprint you see on the platform is different from the one you see on the connected account

grim trout
#

ok so this is the same stuff I was told yesterday

naive kestrel
#

so what's the question then?

grim trout
#

just wanting to understand why this happens

#

it was not happening in the past we always had the data matching and our logic relies on that data matching

naive kestrel
#

this has always been the case

#

did you change the way you listen to events?

#

did you use to create webhook events on each connect account?

grim trout
#

could it be because we have webhooks set up on both accounts?

#

I think we did not before the 3rd of Dec

naive kestrel
#

if you're a platform

#

you shouldn't create webhook endpoints on the connected accounts

viscid mossBOT
grim trout
#

we have these two accounts
acct_1Gin94DD3nZJlvMp
acct_1DW87gDRH1nN3Sur

could you tell me which one is the platform and which one is the connected account?

granite jacinth
#

the first is the connected account of the second(the platform)

grim trout
granite jacinth
#

that event is something changing on the connected account(a PaymentMethod getting attached to a Customer); as you have a Connect endpoint set up(https://docs.stripe.com/connect/webhooks#connect-webhooks) , events that happen on the connected account get sent to your URL. The JSON sent in that webhook request to your server will be rendered for your platform, which in this case will mean the fingerprint you see is one that is consistent across the platform and its connected account; and is different from the fingerprint that the account itself would see if it listened to that event on its own endpoint or if it retrieved the PaymentMethod object from the API using its own API key.

grim trout
#

ok and because we have webhooks set up for all events on both platform and connected account, do both of them trigger so we received two webhook calls?

granite jacinth
#

well in that specific event it was only sent to your platform's endpoint, it wasn't sent to any endpoint on the connected account. But yes, if you had a direct endpoint created on the connected account that listens to this event type, it would be sent there as well and the JSON would be rendered for the connected account's version of things.

grim trout
#

platform webhook

image.png
#

connected account

image.png
#

they are both listening to all events

granite jacinth
#

no, the connected account one is listening to events on its own connected accounts(the connected account can be, and is, a platform of its own), it's not listening to events on its own account(a non-Connect endpoint).

grim trout
#

🤯

granite jacinth
#

you do have a direct endpoint on the connected account that listens to all events, but that one is disabled

grim trout
#

which one

image.png
#

the last one?

granite jacinth
#

yes(that's why it says "your account")

grim trout
#

so is the accounts setup like so:

platform account acct_1DW87gDRH1nN3Sur
connected acc 1
connected acc 2
connected acc 3
connected acc 4 acct_1Gin94DD3nZJlvMp
connected acc 4-1
connected acc 4-2

granite jacinth
#

yes

grim trout
#

and this setup does not let us treat acct_1DW87gDRH1nN3Sur and acct_1Gin94DD3nZJlvMp as completely separate accounts.
Becuase for "connected acc 4 acct_1Gin94DD3nZJlvMp" we still want to get its own connected accounts events (4-1 and 4-2) but if we set it up to be "Your account" we only receive it's own direct events no events from its children.
correct?

granite jacinth
#

you can have any combination of

  • connect endpoint on acct_1DW87gDRH1nN3Sur . That receives events about things that happen directly on accounts 1/2/3/4
  • direct endpoint on acct_1Gin94DD3nZJlvMp. That (also) receives events about things that happen directly on account 4
  • connect endpoint on acct_1Gin94DD3nZJlvMp . That receives events about things that happen directly on accounts 4-1/4-2

you can't have an endpoint on acct_1DW87gDRH1nN3Sur that recieves anything on 4-1/4-2 (that's 'grandparent Connect access' and generally is not possible)

#

I know it's a bit complicated; in most Connect setups the platform and the connected account are not controlled by the same owner/technical integration and they operate much more independntly than in your setup(though your setup is also common too for merchants with regional/international branches, etc)

grim trout
#

"you can't have an endpoint on acct_1DW87gDRH1nN3Sur that recieves anything on 4-1/4-2 (that's 'grandparent Connect access' and generally is not possible)"
but this seems to be the case?

granite jacinth
#

why do you say that?

grim trout
#

because we are getting webhooks call on the platform account when something has happened on the connected accounts of connected acc 4 ?

granite jacinth
#

are you? do you have an example of that?

grim trout
#

ok that is the thing, I'm maybe confusing things

granite jacinth
#

if we're still talking about evt_1QVGdxDD3nZJlvMpeoIuWYyd, that is nothing to do with accounts 4-1/4-2 ( the connected accounts of your connected account acct_1Gin94DD3nZJlvMp); it's about a PaymentMethod being attached to a Customer object that exists on acct_1Gin94DD3nZJlvMp , so it's just one level of Connect and is normal.

grim trout
#

ok thanks

#

so I guess that at the moment with our current setup we have

platform account acct_1DW87gDRH1nN3Sur triggering events for acc 1/2/3/4
connected acc 4 acct_1Gin94DD3nZJlvMp triggering events for 4-1/4-2 but not itself

granite jacinth
#

seems that way to me yes

grim trout
#

can you disconnect accounts?

granite jacinth
grim trout
#

ok

#

not yet sure how we are going to fix our issue but at least I have a better understanding of the accounts structure

granite jacinth
#

what is the issue exactly?
I'd say overall if you're going to store something in a database, you'd store the platform's version of the fingerprint since generally it's the platform that is running the integration and calling the API on behalf of the other connected accounts.
I also have to point out that fingerprint on a card can change over time, because sometimes the saved card on Stripe can change https://docs.stripe.com/saving-cards#automatic-card-updates , so it can't be relied on as a 100% reliable identifier of a specific real card.

grim trout
#

the issue is that before the 3rd of December we only had one webhook on connected acc 4 and all our finger prints in our DB where from the viewpoint of that account. Now that we have added this new webhook, all the events are passing finger prints that we do not know about as they are from the platform perspective

#

at least, after all the discussions, I think that is what the problem is

granite jacinth
#

that would make sense!

grim trout
#

thank you for you help and patience 🙂

naive kestrel
#

👋 taking over for my colleague. Let me know if there's any follow-up Qs I can answer!