#tobe_webhooks-connect
stray sonnetBOT
đ 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/1488987991228682280
đ 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.
- tobewisebeforeiamold_code, 1 hour ago, 20 messages
- tobewisebeforeiamold_code, 23 hours ago, 17 messages
- tobewisebeforeiamold_code, 5 days ago, 37 messages
nimble field
Here's the events I have asked Stripe to listen for on my connect webhook
And here you can see the events for the other non-connect webhook come in
I just can't seem to see any webhook event for when py_1THU9aD6h2U84xyAZdRScoKf is made to the connect account, so I can listen for that to add a customer to that charge
fathom storm
Hello, there isn't a way to assiosciate the charge on the connected account with a Customer object on the connect account. You can make a connection within your system and display that in any UI you own, but the Stripe objects don't have a way of linking here.
From my test just now it looks like a payment.created event is created on the connected account when the transfer/charge are created and it does contain the Charge object that is created on the connected accounts
nimble field
Hm, in another thread one of the Stripe developers suggested I can add a customer to that charge via a webhook for the connect account, and they also mentioned payment.created, but I don't see that as an option in the Dashboard "edit destination" UI. Is there some other place that I'd configure that?
fathom storm
Interesting, looking back at that thread.
In that screenshot are you viewing the dashboard as your connected account?
stray sonnetBOT
surreal tapir
tobe_webhooks-connect
payment.created is a weird historical name that is something I recommend just ignoring
nimble field
In that screenshot are you viewing the dashboard as your connected account?
No, not as the connect account, as the platform. But it seems like it wouldn't scale well if we had to add seperate webhooks for every connect account on the platform...but is that what I'd need to do?
We seem to get events for connect account in the platform webhook currently...
surreal tapir
As a Connect platform, you create a Connect WebhookEndpoint on your own account and that automatically gets Events for all your connected accounts
Just payment.created is a weird/bad old Event you never need to listen to
nimble field
OK, that makes sense. So then what event should I listen for to see that py_1THU9aD6h2U84xyAZdRScoKf destination_payment happen, so I can updated it to add a customer?
I have charge.succeeded turned on there and I see the non-connect webhook get the transfer.created, but I don't see the connect webhook get a charge.succeeded for the charge initiated by that transfer. I feel like maybe the destination_payment charge comes into the connect account maybe with a different event type?
surreal tapir
There's no Event for it really
I would listen to transfer.created on your platform and that has the destination_payment: 'py_12345'
IMO it's quite weird to try and attach a Customer to a connected account's Charge that is the result of a Transfer. It's possible to be clear but is more than uncommon and doesn't really make sense to me
nimble field
We're trying to use <ConnectAppViewport app='com.example.acodeistripeapp' /> and Acodei tells me that in order to get the name of the payer to show up in quickbooks they need the charge that the connect account can see to have a customer on it. But I cannot seem to make that happen.
I tried attaching a customer to it from the platform charge.succeeded event, but I tried to just use the platform customer, and now realize that the connect account has it's own customers. So I guess I'll try that next.
I also hoped that adding on_behalf_of to the payment intent would get Stripe to do the customer upsert on the connect account for me, to no avail.
Am I correct in my understanding that you'd suggest using the platform transfer.created event, and not the connect account webhook, to try and add a customer to the charge it makes, but of course do that upsert on the connect account customers myself so that the customer I add can show up in the connect account?
surreal tapir
What type of connected accounts are you using here?
Looks like you use Custom accounts. I don't really understand how the data on the connected account could get into Quickbooks, can you explain this to me?
nimble field
What type of connected accounts are you using here?
I'm not 100%, but one of them isacct_1REE7KD6h2U84xyA
Looks like you use Custom accounts
That sounds right
I don't really understand how the data on the connected account could get into Quickbooks, can you explain this to me?
Acodei tells me that they listen to charge.created and charge.updated events on the connect account, and use that data to create entries in a Quickbooks account associated with that connect account. And they get the data they need from those events.
https://docs.stripe.com/stripe-apps/embedded-apps
If I can use the platform transfer.created event to update the destination_payment charge with a customer I create/update on the connect account, then I think that'll do the trick. If you think I should try that next?
surreal tapir
Yeah I don't really understand how Acodei would get those Events, unless you proxy those to them. You might have to chat to the support team about this.
But ultimately, I don't think putting a Customer on the connected account makes sense for Custom accounts honestly. They should pull the information from your platform account instead
nimble field
That would certainly make me happier. I've already burned a ton of hours trying to get their integration to work for our data...
I suspect that when the vendors go their their embedded onboarding maybe they inject their webhooks into the connect account webhooks?
Se la vie - I'll give that transfer.created platform webhook a go next. Thank you!