Creating separate charges and transfers
Separate charges and transfers are recommended for Express or Custom accounts where you collect charges that can be a different amount than what’s paid out to your connected accounts. The platform is responsible for Stripe fees, refunds, and chargebacks. For more information about the different types of Connect charges, see the documentation on choosing an approach.
Stripe supports separate charges and transfers in the following regions: Australia, Brazil, Canada, Europe, Japan, Malaysia, New Zealand, Singapore, and the US. Separate charges and transfers are supported if both your platform and the connected account are in the same region (for example, both in Australia). For cross-region support, see the cross-border transfers docs.
To create a charge and set up the associated transfer, create a
transfer_group and assign the charge to the
For the complete flow, see accept a payment.
You can assign any value to the
transfer_group string, but it must represent a single business action. You can also make a transfer with neither an associated charge nor a
transfer_group—for example, when you must pay a provider but there’s no associated customer payment.
Transfer and charge amounts don’t have to match. You can split a single charge between multiple transfers or include multiple charges in a single transfer. You can perform transfers and charges in any order.
By default, a transfer request fails when the amount exceeds the platform’s available account balance. If the transfer has a source_transaction defined, the transfer request automatically succeeds but the transfer itself doesn’t occur until the funds from the
source_transaction become available.
If you use separate charges and transfers, take that into account when planning your payout schedule. Automatic payouts can interfere with transfers that don’t have a defined
When using separate charges and transfers, the platform can collect fees on a charge by reducing the amount it transfers to the destination accounts. For example, consider a restaurant delivery service transaction that involves payments to the restaurant and to the driver:
- The customer pays a 100 USD charge.
- Stripe collects a 3.20 USD fee and adds the remaining 96.80 USD to the platform account’s pending balance.
- The platform transfers 70 USD to the restaurant’s connected account and 20 USD to the driver’s connected account.
- A platform fee of 6.80 USD remains in the platform account.
To learn about processing payments in multiple currencies with Connect, see Working with multiple currencies.
You can refund charges created on your platform using its secret key. However, refunding a charge has no impact on any associated transfers. It’s up to your platform to reconcile any amount owed back to it by reducing subsequent transfer amounts or by reversing transfers (as explained next).
Connect supports the ability to reverse transfers made to connected accounts, either entirely or partially (by setting an
Transfer reversals add the specified (or entire) amount back to the platform’s available balance, reducing the connected account’s available balance accordingly. It is only possible to reverse a transfer if the connected account’s available balance is greater than the reversal amount or has connected reserves enabled.
If the transfer reversal requires the currency to be converted, and the reversal amount results in a zero balance after the conversion, it returns an error.
Optionally, you can set the
on_behalf_of parameter to the ID of a connected account to make that account the business of record for the payment. When using
- Charges are settled in the connected account’s country and settlement currency.
- The fee structure for the connected account’s country is used.
- The connected account’s statement descriptor is displayed on the customer’s credit card statement.
- If the connected account is in a different country than the platform, the connected account’s address and phone number are displayed on the customer’s credit card statement.
- The number of days that a pending balance is held before being paid out depends on the
delay_dayssetting on the connected account.
on_behalf_of is omitted, the platform is the business of record for the payment.
on_behalf_of attribute is supported only for connected accounts with the card_payments capability. Accounts under the recipient service agreement can’t request
When creating separate charges and transfers, your platform can attempt a transfer that exceeds its available balance. Doing so raises an error and the transfer attempt fails. If you’re commonly experiencing this problem, you can use the
source_transaction parameter to tie a transfer to an existing charge. With a
source_transaction, the transfer request succeeds regardless of your available balance and the transfer itself only occurs after the charge’s funds become available.
When using this parameter:
- The amount of the transfer must not exceed the amount of the source charge
- You can create multiple transfers with the same
source_transaction, as long as the sum of the transfers doesn’t exceed the source charge
- The transfer takes on the pending status of the associated charge: if the funds from the charge become available in N days, the payment that the destination Stripe account receives from the transfer also becomes available in N days
- Stripe automatically creates a
- The currency of the balance transaction associated with the charge must match the currency of the transfer
Asychronous payment methods, like ACH, can fail after a subsequent transfer request is made. For these payments, avoid using
source_transaction. Instead, wait until a charge.succeeded event is triggered before transferring the funds. If you have to use
source_transaction with these payments, you must implement functionality to manage payment failures.
When a payment used as a
source_transaction fails, funds from your platform’s account balance are transferred to the connected account to cover the payment. To recover these funds, reverse the transfer associated with the failed