#dan_webhooks

1 messages ¡ Page 1 of 1 (latest)

fervent sunBOT
#

👋 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/1318700342153707541

📝 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.

sharp tinsel
#

Hi there

scenic hawk
#

I'll add that I've triggered events by both actually testing transactions from my website and by using the Stripe CLI

sharp tinsel
#

The Checkout Session in that event was created using the CLI. It was not created within an account context.

#

Based on the logs in your account, I take it you used stripe trigger checkout.session.completed, is that right?

scenic hawk
#

That's right! there's a few chains of events there but neither triggered the webhook to send events to my backend unfortunately.

#

I'm probably making a noob mistake but can't figure out what I'm missing

sharp tinsel
#

Gotcha, okay

#

I see your test mode Connect webhook is listening for checkout.session.completed events but the only events that will be sent to this endpoint are events that occur on one of your connected accounts.

#

When you used stripe trigger checkout.session.completed, the Checkout Session was created on your platform account, not a connected account

#

In order to trigger events on one of your connected accounts, you'll need to adjust the command to stripe trigger checkout.session.completed --stripe-account acct_123abc

#

where acct_123abc is the account ID for an account connected to your platform

scenic hawk
#

Ah that makes sense! I'll try that.

  • can you check the following event too to make sure it's the same issue: evt_1QVG7sAw2dZTYBb9wc2u6Mg0
sharp tinsel
#

If you plan on using destination charges or separate charges and transfers, then it's correct to trigger the event on your platform account. In that case, you should create an account webhook that listens for this event type.

scenic hawk
#

Event evt_1QVG7sAw2dZTYBb9wc2u6Mg0 should be for a connected account I believe and it comes from end to end testing from my website

sharp tinsel
#

Okay, so the Session created here was still created on your platform but it used destination charges. This means that funds will be transferred to the connected account you specified but the Session "lives" on your platform account

#

This means that your connect webhook endpoint will not receive events related to this Session

scenic hawk
sharp tinsel
#

a little bit of both

scenic hawk
#

I guess I either switch the webhook to trigger on the parent account or I re-configure the charges to be on the connected accounts right?

sharp tinsel
#

If you intend to use direct charges, you would create the Session on the connected account by passing the stripe_account header when creating the Session, similar to this: https://docs.stripe.com/connect/authentication#stripe-account-header

If you create a Checkout Session in this way, the Session would "live" on your connected account so your connect webhook endpoint would receive the checkout.session.completed event when that Session is paid

sharp tinsel
#

There are some pretty nifty diagrams that show the different fund flows based on the charge type