rocky-Dispute

[glass tusk]

Hi there, you can attach some custom data in the dispute's metadata https://stripe.com/docs/api/issuing/disputes/update?lang=node#update_issuing_dispute-metadata

[cyan marsh]

I set ClientReferenceId when create a session, but I can't find that when receive dispute event, only "payment_intent". Is there any way to transparent transmission of (session -> dispute)?

[glass tusk]

You can set a metadata to the checkout session's paymentIntent object (https://stripe.com/docs/api/checkout/sessions/create?lang=node#create_checkout_session-payment_intent_data-metadata) so that you can retrieve it later from the Dispute's payment_intent object

[cyan marsh]

Is have way to set it directly to Dispute?I have multiple keys , so I must obtain metadata before retrieve payment_intent

[keen moth]

you can call https://stripe.com/docs/api/disputes/update#update_dispute-metadata , not sure if that's what you mean.

if you mean, can the Dispute object which is automatically created when a payment is disputed, automatically include/inherit metadata from that payment, then no, it doesn't.

but as you mention, the Dispute is linked to a PaymentIntent and you likely have metadata or other context about that PaymentIntent.
client_reference_id isn't really recommended anymore and is very specific to just Checkout and doesn't interact with anything else like payments or disputes