#sirbuland-atlas_code

1 messages · Page 1 of 1 (latest)

willow marlinBOT
#

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

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

ocean shuttle
#

Hi, what you see is expected. It is definitely possible to do but is going to require some custom development. The idea here would be to update the charge on the connected account to set the wanted description

First off, to get the corresponding payment id you’d need to do two steps. The first step is to get the id of the transfer associated with the charge which is in the transfer property on the charge object. Then, you would retrieve that transfer and you’d see the destination_payment property corresponding to the payment on the connected account (py_XXX).

You can get all of this in one API call by using the expand feature and passing transfer to get the transfer property expanded in the response. This gives you access to the payment id (py_XXX) directly in that API call.

Then, once you get this, you’d call the Update Charge API using the Stripe-Account header, https://docs.stripe.com/connect/authentication so that you can set the description you want on that payment.

sinful shadow
#

The issue is
after charging a customer using a PaymentIntent, our system attempted to immediately retrieve the associated Charge object via Stripe::Charge.retrieve(charge_id). In rare cases, particularly under high load, Stripe may take a moment before that Charge object becomes fully accessible through the API. As a result, even though the payment was completed and visible in the Stripe Dashboard, the system could not retrieve the charge at that exact moment