Payment details
Show details of a given payment and allow users to manage disputes and perform refunds.
This component is a subset of payments
, which provides the detail overlay of a given payment. The UI rendered by the payment details component is equivalent to the overlay that the payments
component renders when the user clicks on a payment row.
Use the payment-details
component to invoke the payment details overlay without the need to inline the entirety of the payments
list in your website. This allows you to invoke the payment detail overlay from your existing UI (for example, your payments list) and integrate with our detail view to enable your customers to view payment details, issue refunds, and manage disputed payments.
By default, the embedded components offer limited information for destination charges and separate charges and transfers. They don’t provide access to customer information, payment methods, and some charge amount details. The destination_on_behalf_of_charge_management feature allows a connected account to see additional information with destination charges, as well as perform refunds and manage disputes.
When creating an Account Session, enable payment details 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 payment details component in the frontend:
Note
For destination charges and separate charges and transfers, the connected accounts don’t own the payment intent objects associated with the charges. Pass in the ID of the payment object that belongs to the connected account for these charges.
The payment details component shows different information and supports different features for different charge types:
- For direct charges, your connected accounts can view the complete set of information. They can also manage refunds, manage disputes, and capture payments if you enable the corresponding features when creating an account session.
- For destination charges and separate charges and transfers, your connected accounts can only see the transfer object associated with the selected charge, which contains limited information.
- For destination charges with the on_behalf_of attribute, your connected accounts can view the complete set of information when the
destination_
feature is enabled. When this feature is turned on, you can also enable refund and disputes management by enabling the corresponding features.on_ behalf_ of_ charge_ management
Allow your connected accounts to manage destination charges
When you set the destination_
feature to true
, your connected accounts can use the payments component to view and manage destination charges that have the on_behalf_of attribute. If you also turn on the dispute_
feature, your connected accounts can participate directly in handling their disputes.
Enabling the destination_
feature has the following limitations:
- You can’t filter by charge status or payment methods.
- You can’t export certain data columns.
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.
Supported parameters
This embedded component supports the following parameters: