zuohao | Stripe Developers | Page 1

gaunt pastureBOT Jun 8, 2023, 3:48 AM

#

dark crown Jun 8, 2023, 3:49 AM

#

You can see your request log at https://dashboard.stripe.com/test/logs. Generally py_xxx is a Charge object, and pyr_xxx is a Refund object

Stripe Login | Sign in to the Stripe Dashboard

Sign in to the Stripe Dashboard to manage business payments and operations in your account. Manage payments and refunds, respond to disputes and more.

#

(notice it has r)

#

the py_xxx is a part of your original pi_xxx PaymentIntent

#

which mean you refund multiple times to the same source transaciton

whole pulsar Jun 8, 2023, 3:55 AM

#

However, I need to handle each refund object differently. The "charge.refunded" event only informs me that the refund was successful, but it doesn't indicate which refund object was successful.

#

Are there any other events that can indicate which refund object was successful?

dark crown Jun 8, 2023, 4:01 AM

#

Hmm could you provide example event id? evt_xxx

whole pulsar Jun 8, 2023, 5:17 AM

#

evt_3NGZs72eZvKYlo2C0EZmdn2S

crystal berry Jun 8, 2023, 5:25 AM

#

it's pretty unfortunate, but from v2022-11-15 (https://stripe.com/docs/upgrades#2022-11-15), the Charge object no longer auto expands the refunds, so you would probably have to list all refunds for a particular charge (https://stripe.com/docs/api/refunds/list#list_refunds-charge) to view the status of the relevant refund

whole pulsar Jun 8, 2023, 5:42 AM

#

I am using a test key, but I am receiving events that do not belong to me. Is this normal? For example, event ID: evt_1NGZFP2eZvKYlo2CXBiaRJyk.

#zuohao