Stripe on_behalf_of

Who processed it, whose name is on it, whose money it is

These three come apart in Connect, and each has its own control.

**Who processed it** is the charge type. With a direct charge, Stripe says "the payment appears in the connected account’s balance, not in your platform’s balance". With a destination charge, "the payment appears in your platform’s balance" and a portion transfers onward. That choice decides whose Stripe balance the money lands in, and it is made when you create the charge, not by `on_behalf_of`.

**Whose name is on it** is presentation: statement descriptor, invoice branding, support details, tax IDs on the PDF.

**Whose money it is** in the sense a regulator or a card network cares about is the settlement merchant, and that is what `on_behalf_of` sets.

The combination people find surprising is a destination charge with `on_behalf_of` set. The funds arrive in the platform’s balance, and the connected account is nonetheless the business of record for the payment. Both statements are true at once because they answer different questions.

What Stripe changes the moment you set it

Stripe publishes an explicit list. When `on_behalf_of` is set to the ID of a connected account, Stripe automatically:

- Settles charges "in the country of the specified account to minimize declines and avoid currency conversions". - "Uses the fee structure for the connected account’s country." - Uses "the connected account’s statement descriptor". - Uses "the connected account’s address and phone number (rather than the platform’s) on the customer’s statement if the connected account is in a different country than the platform". - "Pays out a connected account, depending on the days specified in its `delays_days` setting."

Four of those five are about geography. That is the clearest signal of what the field is really doing: it relocates the payment, for processing purposes, to the connected account’s country.

One consequence sits outside that list and lands directly on the platform’s bill. Stripe: "When the `on_behalf_of` field is set, the country of the connected account is used to determine the country specific fees charged to your platform account." The platform still pays, at the connected account’s country rates. If your connected accounts span several countries, your effective processing cost is a weighted average you did not explicitly choose, and [Stripe Fee](/glossary/stripe-fee) is where that arrives.

There is also a routing benefit worth knowing about. Destination charges and separate charges and transfers support cross-region funds flows only in certain regions, and Stripe notes that otherwise "the platform and connected account must be in the same region unless using `on_behalf_of`". The field is sometimes the thing that makes a cross-border arrangement possible at all.

issuer is the neighbouring field, and it is not the same job

On the invoice object, `issuer` sits a few lines away from `on_behalf_of` and is documented as "The connected account that issues the invoice. The invoice is presented with the branding and support information of the specified account."

The second sentence is identical in spirit to the one on `on_behalf_of`, which is exactly why the two get conflated. The first sentences are what separate them. `issuer` is about who the invoice is from. `on_behalf_of` is about where the funds of the payment are intended.

In practice you can use `issuer` to render a connected account’s tax IDs and business details on a customer-facing document without changing anything about settlement. Stripe’s guide on displaying connected account tax IDs offers both as ways to reach the same presentational outcome: specify the connected account "either using the `on_behalf_of` parameter or as the `issuer`". Stripe also pulls default tax IDs "from the invoice `issuer`’s account during finalization" unless `account_tax_ids` is already set.

So if all you need is the right business name and VAT number on the PDF, `issuer` does that job with a narrower blast radius. Reach for `on_behalf_of` when the answer to "whose payment is this?" genuinely needs to change.

What it does not change

This is the half that saves money, because assuming the field carries more than it does is an expensive mistake.

**Dispute liability does not follow it.** Stripe: for disputes on payments created on your platform using destination charges or separate charges and transfers, "with or without `on_behalf_of`", the platform balance "is automatically debited for the disputed amount and fee". The platform can then try to recover the money by reversing the transfer. Making a connected account the business of record does not make it the party whose balance absorbs a chargeback on an indirect charge. See [Stripe Dispute](/glossary/stripe-dispute) for how that debit shows up.

**It does not choose the charge type for you.** Funds still flow according to whether the charge is direct, destination, or separate charges and transfers.

**It does not grant capabilities.** To collect on behalf of a connected account, that account "needs to have account capabilities enabled for the relevant payment methods".

**It narrows payment methods on invoices.** Stripe: "Invoices created on behalf of a connected account don’t support bank transfers payment methods, such as ACH Credit Transfer and paper checks." If an invoice with the field set suddenly cannot offer the payment method your customers use, this line is why.

**It does not settle the tax question.** Stripe’s guidance for invoices with Connect is that "You need to first determine which entity is liable for tax", and that the answer "might be your connected account or the platform, depending on your business model". The field influences what appears on the document. It does not tell you who owes the tax.

It has to be set before the invoice finalizes

Stripe is specific about the window: "You must set `on_behalf_of` in the API before finalizing an invoice", and adds that "the Dashboard doesn’t have an interface for invoices you send on behalf of connected accounts."

That is a real constraint rather than a note. [Stripe invoice finalization](/glossary/stripe-invoice-status) is the point at which the invoice number, the payment intent and the PDF come into existence, and it is the same point at which Stripe pulls the issuer’s default tax IDs. A payment already collected against a finalized invoice cannot be retroactively reassigned to a different business of record by editing a field.

The practical consequence for anyone auditing a Connect setup: if invoices are being created by an automation and finalizing an hour later on their own, the window to set this field is inside the automation, not in anybody’s workflow. The correction after the fact is a credit note and a new invoice, not an update.

Why it matters once the numbers reach your books

Bookkeeping cares about which legal entity earned the revenue and which one owes the tax. `on_behalf_of` is the field where Stripe records an answer to a closely related question, which makes it easy to treat as an accounting instruction. It is not one.

Keep the two apart deliberately. The Stripe balance a payment lands in is decided by the charge type, and that balance is what a payout later moves to a bank account. See [Stripe Transfer](/glossary/stripe-transfer) for how funds move between a platform and a connected account once the charge exists. The business of record designation sits alongside that, and it is what makes the payment look, to the customer and to the card networks, like the connected account’s sale.

For a platform reconciling into one QuickBooks file, the number that has to tie out is still the platform’s own balance and its own payouts, no matter how many payments were taken on behalf of somebody else. For a connected account reconciling its own books, the numbers that matter are the ones in its own Stripe balance. The field that changed the branding on the invoice did not move either one.

The honest summary: read `on_behalf_of` as a statement about identity and settlement, and read the charge type as the statement about money. Answering the accounting question with the wrong one of the two produces books that describe a business other than the one that was paid.