What can platforms listen for to track payments that become disputes?

• A. transaction.dispute.created
• B. payment.error.occured
• C. charge.dispute.created
• D. account.dispute.success

Answer: (C)

The correct choice is to listen for "charge.dispute.created" to track payments that become disputes. This event is specifically designed to notify the platform when a dispute associated with a charge has been initiated. By listening for this event, the platform can take appropriate actions, such as notifying the user, adjusting their records, or responding to the dispute if needed.

The other choices do not accurately reflect the event related to payment disputes. For instance, "transaction.dispute.created" is not an actual event name in the Stripe API, and "payment.error.occured" relates to errors occurring in processing payments rather than disputes specifically. "Account.dispute.success" implies a success state in a dispute process, which does not help platforms monitor the initiation of disputes stemming from charges. Hence, focusing on the correct event name allows developers to effectively manage and respond to disputes in their payment systems.