Payments
Show a list of payments with export, refund, and dispute capabilities.
Web
iOS
Android
React Native
Payments renders a transaction list for direct charges, destination charges, and separate charges and transfers on the connected account.
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 perform refunds, manage disputes, and see additional information for destination charges, including customer information, payment methods and fees.
Create an Account Session
When you create an Account Session, enable the payments embedded component by specifying payments in the components parameter. You can turn on or off an individual feature of the payments component by specifying the features parameter under payments:
Command Line
Select a language
cURL
Stripe CLI
Ruby
Python
PHP
Java
Node.js
Go
.NET
No results
The payments 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 _ on _ behalf _ of _ charge _ management feature is enabled. When this feature is turned on, you can also enable refund and disputes management by enabling the corresponding features.
Allow your connected accounts to manage destination charges
When you set the destination_on_behalf_of_charge_management 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_management feature, your connected accounts can participate directly in handling their disputes.
Enabling the destination_on_behalf_of_charge_management feature has the following limitations:
- You can’t filter by charge status or payment methods.
- You can’t export certain data columns.
Render the payments component
After you create the account session and initialise ConnectJS, you can render the payments component in the front end:
payments.js
Select a language
JavaScript
React
No results
// Include this element in your HTML
const payments = stripeConnectInstance.create('payments');
container.appendChild(payments);
// Optional: specify filters to apply on load
// payments.setDefaultFilters({
// amount: {greaterThan: 100},
// date: {before: new Date(2024, 0, 1)},
// status: ['partially_refunded', 'refund_pending', 'refunded'],
// paymentMethod: 'card',});
| Method | Type | Description | Default |
|---|---|---|---|
setDefaultFilters | PaymentsListDefaultFilters | On load, show the payments matching the filter criteria. See the possible PaymentsListDefaultFilters properties. | none |
Set default filters
Setting default filters for the payments list is optional. If set, it applies any valid filters and ignores invalid filters. If the destination_on_behalf_of_charge_management feature is enabled, then you can’t filter by status or payment method so it ignores these filters automatically.
You can specify any combination of payment filters of your choice using the PaymentsListDefaultFilters object.
The PaymentsListDefaultFilters object
To specify default filters, pass a PaymentsListDefaultFilters object into the setDefaultFilters setter. The object has the following properties, which are all optional:
| Name | Type | Description | Example value |
|---|---|---|---|
amount | {equals: number} | {greaterThan: number} | {lessThan: number} | {between: {lowerBound: number, upperBound: number}} | Filter by the payment amount (to the nearest hundredth). | {greaterThan: 100} |
date | {before: Date} | {after: Date} | {between: {start: Date; end: Date} | Provide Date objects to filter by date. It accepts any date format allowed by a JavaScript Date object. Only the year, month, and day are taken into consideration. | {before: new Date(2024, 0, 1)} |
status | Status[] | Provide one or more statuses. The valid status options are: 'blocked' | 'canceled' | 'disputed' | 'early_fraud_warning' | 'failed' | 'incomplete' | 'partially_refunded' | 'pending' | 'refund_pending' | 'refunded' | 'successful' | 'uncaptured' This filter is ignored if the destination_on_behalf_of_charge_management feature is enabled. | ['disputed', 'canceled'] |
paymentMethod | PaymentMethod | The full list of payment methods is available under the type enum for the PaymentMethod object. To see which payment methods are available to you, check your payment method settings. This filter is ignored if the destination_on_behalf_of_charge_management feature is enabled. | 'card' |
Dispute management for destination charges
When you enable both dispute_management and destination_on_behalf_of_charge_management, your connected accounts can update and modify dispute evidence, counter disputes, and accept disputes for destination charges with the on_behalf_of attribute set to the connected account.
For destination charges, with or without on_behalf_of, 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_negative_balances 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_behalf_of until after a dispute is lost.
Customise the description
If you’re using the destination_on_behalf_of_charge_management option, the payment information (including the description) shown for destination charges with the on_behalf_of attribute corresponds to the original created payment. To display a custom description within the payment detail view for destination charges and separate charges and transfers when this feature is off, follow these steps:
Destination charges
To update the description on a payment object that’s visible to your platform’s users, you need to use the Stripe API. This applies to all platforms that use destination charges.
- Find the existing transfer object you created for an account by finding the latest charge created on the PaymentIntent .
- Use the charge object to find the transfer object associated with the charge.
- Use the transfer object to find the destination_payment ID that exists on the transfer.
- Call the Update Charge API to update the description on the destination payment using the destination _ payment ID.
Note
The destination_payment object belongs to the connected account, so you’ll need to set the Stripe-Account header to the connected account’s ID to make this call.
Command Line
Select a language
cURL
Stripe CLI
Ruby
Python
PHP
Java
Node.js
Go
.NET
No results
This description becomes visible on the charge after you’ve written this field.
Learn more about creating destination charges on your platform.
Separate charges and transfers
To update the description on a payment object that’s visible to your platform’s users, you need to use the Stripe API. This applies to platforms that use separate charges and transfers.
- Use the transfer object to find the destination_payment ID that exists on the transfer.
- Call the Update Charge API to update the description on the destination payment using the destination _ payment ID found in the previous step.
Note
The destination_payment object belongs to the connected account, so you’ll need to set the Stripe-Account header to the connected account’s ID to make this call.
Command Line
Select a language
cURL
Stripe CLI
Ruby
Python
PHP
Java
Node.js
Go
.NET
No results
This description becomes visible on the charge after you’ve written this field.
Learn more about creating separate charges and transfers.