junnan-liu_webhooks

[red lake]

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

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

[mild pebble]

hmmmm, i'm not entirely sure if a trace_id is actually generated in test mode

do you have a connected account where you created a payout?

[slim coral]

Yes we have. like acct_1PlNmCPEMwSpNoOp

maybe this one has more data acct_1POxMDPLDRKLjDso

[mild pebble]

okay, sorry, I have no idea off the top of my head if the payout trace id is going to be available in test mode. My gut feel is that it may not be available in test mode because we don't actually send the payout to our banking partner and so there's no trace id to actually retrieve. If you want to confirm, I'll recommend reaching out to Stripe Support https://support.stripe.com/contact who can verify this for you

[slim coral]

Thanks. Because we want to consumer the trace_id , do you know any other ways to test/verify logics? If we can only do this in production, is it supposed to always have a payout.updated event with trace_id value after a payout.paid event?

[mild pebble]

you can probably see how it works in production, then mock it in test. https://docs.stripe.com/payouts/trace-id#api - it mentions that there's a couple of different scenarios for the trace id that you'll want to take into account