#primalfreeze_webhooks

1 messages ¡ Page 1 of 1 (latest)

scenic sundialBOT
#

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

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

azure ferry
#

evt_1QyNFdIezA7yLdDGQxqe5LO2 is not found in our system, and likely it's out of the retention policy. Could you share an event that was sent in the past 14 days?

odd root
#

No, I don't have any

#

I don't think the event itself is relevant, it's more of a conceptual thing

azure ferry
#

If the event is for an object that is created on the connected account, account field will be present to indicate the connected account that the event belongs to: https://docs.stripe.com/api/events/object#event_object-account

If the event is for an object that is created on the platform, it's expected that the connected account information will not be present

#

Without knowing which event that is and how the object in the event is created, I couldn't investigate why account isn't present

odd root
#

" object that is created on the platform" what do you mean by this?

#

The event Type will be a 'checkout.session.completed', and should only be provided by connected accounts (not expecting to see any for my account as it were)

azure ferry
#

For example, if you use Separate Charges and Transfers in your Connect integration, the Checkout Session will be created on your platform. Any Checkout Session or Payment Intent related events will be created on your platform, in which account parameter will not be present

Learn about separate charges and transfers, a Connect charge type where you create a charge for a connected account on the platform and then transfer funds to the connected account as a separate transaction.

#

Could you share an example Checkout Session ID (cs_123), so that I can check how your integration works?

odd root
#

No, we don't have any actually completing yet. Here is a payment link that was created earlier today though plink_1T4rjsA2c6uLmBgv6YF1MuPL

#

So my system will create those payment links, and then once they're paid, we want to know about it and update back to the source system.

#

I've found another payload from an event some time ago and I can see an account id in it

azure ferry
#

plink_1T4rjsA2c6uLmBgv6YF1MuPL is created for Direct Charges which the payment will be made on the connected account. If a payment is completed on this Payment Link, its checkout.session.* and payment_intent.* events should include account field for the Webhook endpoint on the platform.

I don't see any checkout.session.completed event on this connected account acct_1QSB80A2c6uLmBgv for similar Payment Link integration since 2025-08-11, so I can't verify your statement that account is absent. We will need a recent event ID to investigate why account is missing if the payment is indeed using Direct Charges flow.

Learn about direct charges, a Connect charge type where you create a charge for a connected account on the connected account and can transfer funds to the platform.

odd root
#

I wasn't reporting a failure, I was asking HOW to identify the account, and you've answered that. One of the samples I had from over a year ago happened to not be for the connected account, but my own, and that's the one I looked at.

#

I found another event from the same time that WAS from the Connected account and it does indeed have the account field.

azure ferry
#

Sounds good and thanks for clarifying! Feel free to let us know if you have any further questions about the Stripe integration

odd root
#

No problems, thanks for the assistance