#alex-xentral_api
visual trenchBOT
👋 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/1229795044773335104
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
clever zephyrBOT
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.
- alex-xentral_api, 4 hours ago, 7 messages
wheat kernel
Hi there 👋 you mentioned a concern with the information on a Payout object, but the provided ID appears to be for a Charge object. Can you help me better understand how the two are related?
prisma otter
ah sorry, probably didn't convey everything correctly. I am the PM for Xentral Finance and this info came from our devs. To give you some context, we are integrating with Stripe in order to import payments to our ERP system and match them with the respective orders. So I guess the issue is in the Charges and not the Payouts.
wheat kernel
Hm, I just double checked our object structure and don't see source as a field Charge objects.
I see the source field on the Payment Intent related to that Charge is null, because it used a Payment Method instead of a source so the payment_method field is populated.
wheat kernel
It may
Yeah, they're using Payment Methods instead of sources, so you will likely want to start looking at both fields.
What's the concern regarding the metadata, where are you providing that?
prisma otter
so apparently we used to take the original order id from the metadata field, but now it's NULL...
sorry, order number, not id
wheat kernel
Where are you providing that metadata? Metadata is something that is provided by your integration and stored on Stripe objects. Do you have an example of one where you had that data before that I can use as a comparison?
prisma otter
I don't have an old JSON but I do have an id for which we had all that filled in. one sec.
ch_3O7aXyB3j83p8hea0NgG5LgT
so you mean that another part of Xentral is sending this data and storing it on a Stripe object and then we import it again when the payment is made?
wheat kernel
That Charge was created from a Payment Intent where metadata had been provided. This is the request for that
https://dashboard.stripe.com/logs/req_nfF7hbpIrAc8Zb
metadata is copied from a Payment Intent to a Charge object (one of the few scenarios where we automatically copy metadata to another object)
Pulling one of the new charges, it came from a Checkout Session which was created without any metadata:
https://dashboard.stripe.com/logs/req_5tgT1N02J8VThs
It also looks like that request may have been made by a Platform for your account. I'm not exactly sure which accounts are yours in this flow.