#axel_api
undone flameBOT
👋 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/1242130366584721508
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
reef marten
Hello
You would retrieve that Charge on the Connected Account and updates its metadata.
tribal falcon
So the metadata on the connected account payment is in fact the metadata on the charge?
anyway to instruct Stripe to automatically set the charges metadata to match its payment intents?
I guess it's possible in a custom payment flow, but we use Checkouts
reef marten
A Payment (py_xxxx object) is actually just a Charge object (https://docs.stripe.com/api/charges/object)
No it isn't possible in any flow to have this set automatically
I can submit feedback about that
But right now you have to manually set the metadata on the objects that are created from a Destination Charge or a Transfer
(If you want to copy that metadata over)
tribal falcon
A Payment (`py_xxxx` object) is actually just a Charge object (https://docs.stri...
OK thanks. does that mean a py_x and and ch_x records are the same thing?