#pagaok-webhook
jovial torrent
Hi, here you are: evt_3LUZIEAti7rRHD030huOa741
manic lark
Thank you, pulling that up and taking a look.
The webhook endpoints that you created are listening for events from your Connected Accounts rather than events from your account.
To listen to events from your account, you will need to create a new webhook endpoint. Webhook endpoints can either listen to events from your account or from your connected accounts but not both simultaneously.
jovial torrent
and is normal to read, webhook attempts to your account: zero and webhook attempts to platform connected: zero (is that connected account)
second point in my integration I'm using connected accounts,
payment was directed to connected account id: acct_1L58tQPEXCgis1uG
am I interpreting things in the wrong way ??
manic lark
Looking at that Payment Intent, it was created using our Destination charge approach. This means that the Payment Intent resides on the Platform account, and funds from that payment are transferred to your Connected Account (the destination account) as part of that process. Since the Payment Intent resides on the Platform account, the events related to it will also occur on the Platform account.
jovial torrent
can you point me to the resource where the payment intent creation to connected account is explained instead, probably I'm a bit confused in my integration ....
thanks in advance
manic lark
Sure, this section references the three models that we have; Direct charges, Destination charges, and "Separate charges and transfers":
https://stripe.com/docs/connect/charges#types
It talks about what scenarios fit which models well, and provides links to documentation for each charge model which discusses how to implement them.
jovial torrent
I will dig into , thanks again
manic lark
Happy to help! Let us know if that documentation doesn't clear up the questions you're facing.