#milan_api
1 messages ¡ Page 1 of 1 (latest)
đ 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/1413268275235782818
đ Have more to share? Add more details, code, screenshots, videos, etc. below.
Looking up the Payment Intent. Do you have any example of the code you are using to retrieve the Payment Intent with the ID or what code is outputting the error you shared in quotes?
var stripeClient = new StripeClient(platformCredential.SecretKey);
var paymentIntentService = new PaymentIntentService(stripeClient);
var paymentIntent = await paymentIntentService.GetAsync(paymentIntentId);
The error I pasted is the exact error that we received.
And when I look in the Stripe dashboard, the payment intent looks valid.
Do you have a request ID I can look out for that get request?
I'm trying to pick through the logs to find it but I can't
This happened at 3:51 pm CST today
Is there an easy way to find the list of requests that were to payment_intents/acct_1Lnnca2axWWrzryW?
Filters wont' show get requests by default you'll filter your requests in the dashboard to include get requests
I'm looking on my end.
And I realized I mistyped that URL above. That example should have had the PI and not the account Id. Just a typo but we use the PI in the actual request.
I'm not seeing any get requests for that PI.
While our back end logs wouldn't save the reponse itself. We shoudl be able to see the request being made.
That's strange. You don't see any requests at all even those that returned an error?
And to reconfirm, we just need to pass in the platform's secret key and not the connect account Id to look up a PI information, correct?
It's odd this is working sometimes and not others.
Oh. actually, I read the error in our logs wrong. Give me one second...
Also the response we send would usually be in the form No such payment_intent: 'pi_xyz123'
I don't see an error code shaped like what you provided that would come from us. Is there a larger coded snippet you could share. Maybe the answer lies within.
My mistake. I read the error from our logs as if we didn't get the PI details from your API. Apparently, this error is because we couldn't find the PI Id on the query string. This is on our side. Sorry for the trouble here.