pepski-paymentintent | Stripe Developers | Page 1

iron stratus Aug 24, 2022, 9:18 AM

#

what's the ID of the PaymentIntent pi_xxx so I can have a look?

lavish talon Aug 24, 2022, 9:20 AM

#

pi_3LZeyhCZ1pXYosAt0YfPXzxO
ch_3LZeyhCZ1pXYosAt0Qocbetq

iron stratus Aug 24, 2022, 9:23 AM

#

well that one was impacted by one of the outages we had on Monday (https://twitter.com/stripestatus/status/1561803008261758976?cxt=HHwWgIChyfXj0awrAAAA) so the payment didn't actually process or succeed.

Stripe Status (@stripestatus)

From 18:00–19:33 UTC, we saw elevated error rates and response times with the API. This is now resolved.

lavish talon Aug 24, 2022, 9:24 AM

#

och okay, thanks

#

and why is it included in Payout?

#

po_1La8bK2SUhYWUUS1vLpxhqEM

iron stratus Aug 24, 2022, 9:34 AM

#

what specifically happened here is the API request failed (https://dashboard.stripe.com/logs/req_pufUAMH69R4HAn) but it looks like the charge went through. We automatically cancelled it and refunded the customer though [0]. So you probably will see some downstream objects like the charge in the payout since one was created.
[0] - https://stripe.com/docs/error-low-level#server-errors For example, if creating a charge returns a 500 error but we detect that the information has gone out a payment network, we’ll try to roll it forward. If not, we’ll try to roll it back. If this doesn’t resolve the issue, you may still see requests with a 500 error that produce user-visible side effects.

#pepski-paymentintent