aj-nixzy_api

[brave halo]

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

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

[crystal imp]

Hello, do you have the stripe object ID of the payment, transfer or reverse transfer that you are working with? Or an API request (req_123) where you tried to do something with one of those objects?

Ah I see tr_3RZD8iH2wLHuCKJp0Lz39NmU from the gist

[storm hound]

Yeah, that'd be just one of them. On the response from the API I do see the metadata, but when our product team tries to see those fields in the dashboard they aren't seeing anything on the transfer

[crystal imp]

Ah, gotcha. So the API is seeing the metadata just fine, it is more about dashboard visibility?

[storm hound]

Kind of, It doesn't appear that the metadata is storing at all. The initial response from the api will acknowledge the metadata and show it on the object, but then if I try to retrieve the object (tr_3RZD8iH2wLHuCKJp0Lz39NmU for example) from the api there isn't metadata set. So it's not on the object in the API or the dashboard.

[crystal imp]

Ah gotcha, so what is happening here is that a transfer reversal is actually its own object. So for that transfer you created trr_1Ro0yCH2wLHuCKJpr8H8a10A (notice trr_ instead of tr_). The transfer reversal object is the object that has this metadata stored, and it isn't automatically copied to the transfer object unfortunately

Double checking, but I think the workaround here would be making a separate update call that sets this metadata on the transfer object if you want this to be visible in the dashboard.

[storm hound]

Ah gotcha that clears a lot of things up. We could definitely do that on our side

[crystal imp]

Yeah unfortunately as far as I can see there isn't a way to set transfer metadata while creating a reversal, and it looks like there just isn't a dashboard page for transfer reversals so there isn't a good way to see the metadata without setting this.

API-wise, the metadata should start appearing in the reversal object that appears in the transfer's reversals array. So if the dashboard wasn't a factor you might not need to do this, but I think the best workaround here will be to make another API call.https://docs.stripe.com/api/transfers/object#transfer_object-reversals-data-metadata