Sign in
An image of the Stripe logo
Create account
Sign in
Home
Payments
Business operations
Financial services
Developer tools
No-code
All products
Home
Payments
Business operations
Home
Payments
Business operations
Financial services
Developer tools
Support
Overview
Online payments
Products and prices
Invoicing
Subscriptions
Quotes
In-person payments
Multiparty payments
    Overview
    Get started
    Collect payments then pay out
    Enable other businesses to accept payments directly
    Pay out money
    Explore Connect
    Onboard your accounts
    Choose your account type
    Standard
    Express
    Custom
    Service agreement types
    Payment methods
    Account capabilities
    Additional verifications
    Update verified info
    Connect embedded UIs
    Quickstart
    Get started with Connect embedded UIs
    Accept payments
    Create a charge
      Direct charges
      Destination charges
      Separate charges and transfers
    Create a payments page
    Create payment links with Connect
    Connect integration guide
    Automatic payment methods
    Set statement descriptors
    Connect platforms using the Payment Methods API
    Create subscriptions
    Create invoices
    Debit Express and Custom connected accounts
    Pay out
    Set bank and debit card payouts
    Bank accounts
    Manage payout schedule
    Manual payouts
    Payout reversals
    Instant Payouts
    Cross-border payouts
    Crypto payouts
    Manage funds
    Add money to your platform balance
    Account balance
    Handle multiple currencies
    Manage accounts
    Best practices
    Listen for updates
    Dashboard account management
    Understanding risk offerings
    Platform controls for Standard accounts
    Make API calls for connected accounts
    Set MCCs
    Testing
    Manage tax forms
    Overview
    Get started with tax reporting
    1099 Tax Support and Communication Guide
    Tax form settings
    Calculation methods
    File tax forms
    File tax forms with states
    Identify forms with missing information
    Update tax forms
    Deliver tax forms
    E-delivery for 1099 tax forms
    Correct tax forms
    Split tax forms
    Tax year changeover
    What's new for tax year 2022
After the payment
Add payment methods
Payment Links
Stripe Checkout
Stripe Elements
About the APIs
Regulation support
Implementation guides
Testing
Connect
·
HomePaymentsMultiparty paymentsCreate a charge

Creating separate charges and transfers

With Connect, you can make charges on your platform account on behalf of connected accounts, perform transfers separately, and retain funds in the process.

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 transfer_group.

Command Line
# Create a PaymentIntent: curl https://api.stripe.com/v1/payment_intents \ -u
sk_test_4eC39HqLyjWDarjtT1zdp7dc
: \ -d "amount"=10000 \ -d "currency"="usd" \ -d "transfer_group"="{ORDER10}" # Create a Transfer to a connected account (later): curl https://api.stripe.com/v1/transfers \ -u
sk_test_4eC39HqLyjWDarjtT1zdp7dc
: \ -d "amount"=7000 \ -d "currency"="usd" \ -d "destination"="{{CONNECTED_STRIPE_ACCOUNT_ID}}" \ -d "transfer_group"="{ORDER10}" # Create a second Transfer to another connected account (later): curl https://api.stripe.com/v1/transfers \ -u
sk_test_4eC39HqLyjWDarjtT1zdp7dc
: \ -d "amount"=2000 \ -d "currency"="usd" \ -d "destination"="{{OTHER_CONNECTED_STRIPE_ACCOUNT_ID}}" \ -d "transfer_group"="{ORDER10}"

For the complete flow, see accept a payment.

Transfer options

You can assign any value to the transfer_group string, but it must represent a single business action. You can also make a transfer without either an associated charge or a transfer_group—for example, when you must pay a provider but there’s no associated customer payment.

The platform:

  • Does not have to transfer the same amount as the original charge
  • Can transfer a maximum of the platform’s available account balance (with an exception when using source_transaction)
  • Must be configured to use manual payouts or a combination of automatic payouts and the source_transaction parameter to ensure the account has sufficient funds to cover the transfer

You can group together multiple charges with a single transfer or multiple transfers with a single charge. You can also perform transfers and charges in any order.

Collecting fees

When creating charges on your platform and separately creating a transfer, the platform can earn money by allocating less of the charge amount to the destination Stripe account, as in the above code example. Assuming that represents a delivery service transaction, with a charge to the customer of 100 USD, a transfer of 20 USD to the delivery person, and a transfer of 70 USD to the restaurant:

  • The charge amount less the Stripe fees is added to the platform account’s pending balance
  • When the platform’s available balance is sufficient (at least 90 USD), the transfers can be made, reducing the platform’s available balance by the specified amounts and increasing both connected account’s available balances by that same amount
  • Assuming standard US Stripe fees, the platform retains an additional 6.80 USD (100.00 USD - 70.00 USD - 20.00 USD - 3.20 USD).

If you process payments in multiple currencies, you should also read how that is handled in Connect.

Refunding charges

Charges created on your platform can be refunded using your platform’s 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 your platform by reducing subsequent transfer amounts or by reversing transfers (as explained next).

Command Line
curl https://api.stripe.com/v1/refunds \ -u
sk_test_4eC39HqLyjWDarjtT1zdp7dc
: \ -d charge="{CHARGE_ID}" \

Reversing transfers

Connect supports the ability to reverse transfers made to connected accounts, either entirely or partially (by setting an amount value):

Command Line
curl https://api.stripe.com/v1/transfers/
{{TRANSFER_ID}}
/reversals
\ -u
sk_test_4eC39HqLyjWDarjtT1zdp7dc
: \ -d amount=500

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, you’ll receive an error if the reversal amount results in a zero balance after the conversion.

Using on_behalf_of

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 on_behalf_of:

  • 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_days setting on the connected account.

If on_behalf_of is omitted, the platform is the business of record for the payment.

The on_behalf_of attribute is supported only for connected accounts with the card_payments capability. Accounts under the recipient service agreement can’t request card_payments.

Command Line
curl https://api.stripe.com/v1/payment_intents \ -u
sk_test_4eC39HqLyjWDarjtT1zdp7dc
: \ -d amount=1000 \ -d currency="usd" \ -d "automatic_payment_methods[enabled]"=true \ -d on_behalf_of=
{{CONNECTED_STRIPE_ACCOUNT_ID}}

Transfer availability

When creating separate charges and transfers, your platform can inadvertently attempt a transfer without having a sufficient 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. By using source_transaction, the transfer request succeeds regardless of your available balance and the transfer itself only occurs once the charge’s funds become available.

Command Line
curl https://api.stripe.com/v1/transfers \ -u
sk_test_4eC39HqLyjWDarjtT1zdp7dc
: \ -d amount=1000 \ -d currency="usd" \ -d source_transaction="{CHARGE_ID}" \ -d destination="{{CONNECTED_STRIPE_ACCOUNT_ID}}"

When using this parameter:

  • The amount of the transfer must not exceed the amount of the source charge
  • You may 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 transfer_group for you
  • The currency of the balance transaction associated with the charge must match the currency of the transfer

Certain payment methods, like ACH, can fail asynchronously. For these payments, you should avoid using source_transaction and wait until a charge.succeeded event is triggered before transferring the funds. If you have to use source_transaction with these payments, you’ll have to 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 source_transaction.

See also

  • Creating charges
  • Multiple currencies
  • Custom accounts
  • Cloning saved payment methods
  • Statement descriptors with Connect
  • Understanding Connect account balances
Was this page helpful?
Questions? Contact us.
Watch our developer tutorials.
Check out our product changelog.
Powered by Markdoc
You can unsubscribe at any time. Read our privacy policy.
On this page
Collecting fees
Refunding charges
Reversing transfers
Using on_behalf_of
Transfer availability
See also
Stripe Shell
Test mode
Welcome to the Stripe Shell! Stripe Shell is a browser-based shell with the Stripe CLI pre-installed. Login to your Stripe account and press Control + Backtick on your keyboard to start managing your Stripe resources in test mode. - View supported Stripe commands: - Find webhook events: - Listen for webhook events: - Call Stripe APIs: stripe [api resource] [operation] (e.g. )
The Stripe Shell is best experienced on desktop.
$