ed_api | Stripe Developers | Page 1

wary carbonBOT Mar 19, 2025, 9:09 PM

#

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

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

ed_api, 18 hours ago, 27 messages

#

crimson cypress Mar 19, 2025, 9:12 PM

#

Hi there. Having a look now

opal hearth Mar 19, 2025, 9:15 PM

#

Thanks palamedes

#

Connected accounts are complaining that they have no clue who is paying them

#

in a very serious way 😨

crimson cypress Mar 19, 2025, 9:20 PM

#

Uh oh!

#

Just doing some quick testing to see if metadata is copied to the destination payment

opal hearth Mar 19, 2025, 9:21 PM

#

ok

crimson cypress Mar 19, 2025, 9:21 PM

#

Ah, but you're already using metadata

opal hearth Mar 19, 2025, 9:21 PM

#

yep

#

and AI is not telling me anything useful. I wish the code were opensource so I could trace it myself

crimson cypress Mar 19, 2025, 9:31 PM

#

Essentially, if you want for your connected accounts to have more detailed information at the Charge level about what the charge is for, where it came from, you should listen to the transfer.created event, which ties together the Charge (on your platform), the Balance Transaction, the Transfer, and the destination payment. You would then need to update the destination payment py_123 object on your connected account

#

https://docs.corp.stripe.com/api/events/types?lang=java#event_types-transfer.created
https://docs.corp.stripe.com/connect/authentication#stripe-account-header

opal hearth Mar 19, 2025, 9:32 PM

#

No you're kidding.

#

I have to manually track and do the matching on behalf of Stripe??

crimson cypress Mar 19, 2025, 9:33 PM

#

It isn't very intuitive that the destination payment doesn't inherit fields like description or metadata from the source transaction on your platform, but that is generally consistent with how transfer of information between related objects works on Stripe

opal hearth Mar 19, 2025, 9:39 PM

#

Why is that consistent? That seems like a meaningful api oversight?

crimson cypress Mar 19, 2025, 9:47 PM

#

Because generally in Stripe objects do not inherit data from related objects, and this is by design. An example of an exception would be that there is a one-time copy of the metadata, as well as some other fields, from PaymentIntent to Charge when a PaymentIntent is confirmed.

#ed_api