Disputes for a paymentPrivate preview
Enable a connected account to view and manage disputes for a payment.
Render a UI component for connected accounts to view disputes applicable to a specific payment. Connected accounts can see details for each dispute, such as the dispute reason, status, amount, and created date. If you enable the dispute_
feature for the account session, the connected account can perform actions like submitting evidence and accepting disputes. This functionality is also available in the Payment details component.
This inline component can be integrated on the same page as your other payments UI. It’s suitable for use in full screen, overlay, drawer, or any other layout with adaptable widths. If there aren’t any disputes associated with the payment, the component renders nothing. You can also configure custom behavior, such as different margins, for when there are no disputes. To do so, set a custom callback function using onDisputesLoaded
.
In rare cases, a connected account can receive multiple disputes for the same payment created by a customer. Your connected account must review and handle each dispute for the same payment separately. We recommend you inform your connected accounts about this best practice to help improve their payment success rate.
By default, embedded components are most compatible with Connect integrations that accept direct charges. Embedded components display less information for destination charges and separate charges and transfers, and this UI component renders nothing for these charge types. To enable users to see disputes associated with destination charges with the on_behalf_of attribute, enable the destination_
feature.
When creating an Account Session, enable this component by specifying payment_
in the components
parameter. You can turn on or off an individual feature of the payment details component by specifying the features
parameter under payment_
:
After creating the account session and initializing ConnectJS, you can render the Disputes for a payment component in the frontend:
Note
For destination charges and separate charges and transfers, the PaymentIntent doesn’t exist on the connected account. Instead, pass the associated charge ID that belongs to the connected account.
Supported parameters
This embedded component supports the following parameters:
Dispute management for destination charges 
For destination charges, with or without on_
, Stripe debits dispute amounts and fees from your platform account.
We recommend setting up a webhook to listen to dispute created events. When that happens, you can attempt to recover funds from the connected account by reversing the transfer through the Dashboard or by creating a transfer reversal.
If the connected account has a negative balance, Stripe attempts to debit its external account if debit_
is set to true
.
If you challenge the dispute and win, you can transfer the funds that you previously reversed back to the connected account. If your platform has an insufficient balance, the transfer fails. Prevent insufficient balance errors by adding funds to your Stripe balance.
Common mistake
Retransferring a previous reversal is subject to cross-border transfer restrictions, meaning you might have no means to repay your connected account. Instead, wait to recover disputed cross-border payment transfers for destination charges with on_
until after a dispute is lost.
When both dispute_
and destination_
are enabled, the connected accounts can update and modify dispute evidence, counter disputes, and accept disputes for destination charges with the on_
attribute set to the connected account.
Request early access Private preview
Sign in to request access to this Connect embedded component in preview.
If you don’t have a Stripe account, you can register now.