jrfr23 | Stripe Developers | Page 1

solemn prawnBOT Aug 1, 2023, 5:07 AM

#

copper citrus Aug 1, 2023, 5:10 AM

#

Hi there, what do you mean by unrelated transfer?

hallow cairn Aug 1, 2023, 5:10 AM

#

hi there apologies trying to think of the best way to explain

#

so when dispute.created is fired if i create a transfer my understanding is nothing about that transaction will be tied to the transaction being disputed

#

so in the event that the dispute is "won" and i get the corresponding "charge.dispute.closed" event for transaction A wondering if theres something I could use to have it contain the ID of the manual transfer (lets call it transaction B)

#

basically in the processing of transaction A I'm being advised to create a secondary transaction B and then when transaction A triggers certain events to take action on transaction B

#

it just so happens the workflow this pertains to is when trasnaction A is disputed

copper citrus Aug 1, 2023, 5:17 AM

#

OK, so the manual transfer that you created to cover the chargeback is unlinked to the Dispute object. So you can consider using metadata (https://stripe.com/docs/api/issuing/disputes/update#update_issuing_dispute-metadata) to associate the transfer to the dispute.

Stripe API reference – Update a dispute – curl

Complete reference documentation for the Stripe API. Includes code snippets and examples for our Python, Java, PHP, Node.js, Go, Ruby, and .NET libraries.

hallow cairn Aug 1, 2023, 5:19 AM

#

ah I see perform the unrelated api calls and attach the id's of the resources those calls create to the dispute meta data which will then be available when the subsequent future dispute events are fired?

copper citrus Aug 1, 2023, 5:24 AM

#

Yes you are right.

hallow cairn Aug 1, 2023, 5:25 AM

#

that makes sense, thanks for the help

#jrfr23