Disputes on payments

What's new

Payments returned by get_payments now carry an optional disputes array, listing the chargebacks raised against each payment, newest first. It is null when the payment was never disputed.

Impact

You no longer need a separate get_disputes call to see whether a payment was charged back. Each nested dispute has the same fields as a get_disputes item, except payment_id, order_id, user_id, and player_id, which the payment already carries:

• id, status, reason, reason_category, and description
• amount in minor units of currency, and amount_decimal in major units
• amount_usd and amount_eur, booked in minor units (cents) as of when the dispute was recorded
• created_at and updated_at, in Unix seconds
• fees, the processor-reported or estimated dispute fees

Changes

Resource	Change
get_payments	Added optional disputes array of PaymentDisputeRead objects to each payment in the 200 response
Components	Added the PaymentDisputeRead schema

Upgrade

• No changes are required.
• If you call get_disputes only to match disputes to payments, you can read disputes from get_payments instead.

Need help?
Contact our integration team at [email protected]