Stripe Connected Accounts: Standard, Express, Custom, and Whose Name Is on the Charge

Stripe Connect exists because some businesses legitimately sit between a customer and many sellers: marketplaces, platforms, software that lets other firms take payments. It is a product with rules, account types and charge flows. It is not a sticker you put on ordinary account sharing so that a frozen merchant can keep selling.

If you are a platform, you already need Stripe’s documentation and, where your model demands it, Stripe’s agreement to that model. If you are a merchant hoping a friend’s platform login will “run it as Connect”, you do not have Connect. You have someone else’s account.

Two parties, minimum

The platform provides the software or the marketplace. The connected account is the business being paid, onboarded through Connect, with identity information collected to a standard Stripe sets. The customer is a third party, and the card networks care which name they think they paid. Any explanation that cannot name all three without hedging is not ready to charge.

Standard, Express and Custom — the distinction that matters

Standard connected accounts are closest to a normal Stripe account. The seller generally has a direct relationship with Stripe, a full dashboard, and more control over their own settings. The platform is involved, but the seller is not a passenger.

Express accounts use a Stripe-hosted onboarding and a lighter dashboard. The platform has more control over the experience. The seller still goes through Stripe’s checks. You cannot complete those checks with a story about a different business.

Custom accounts put the most of the experience, and a correspondingly heavy set of responsibilities, on the platform. They are for businesses that have built, and been permitted to build, that responsibility. They are not a way to avoid showing Stripe who the seller is. Identity is still collected. Activity is still monitored. A custom account whose true seller was never disclosed is a worse fact, not a clever structure, because the platform took more of the duty and then broke it.

Whose name is on the charge

Direct charges, destination charges, and separate charges and transfers are different ways the payment and the movement of funds can be arranged. The details belong in Stripe’s current Connect docs, and they change. The commercial question does not change. Who does the customer think they paid? Whose name can appear on the statement? Which account is debited if the customer disputes? Who is allowed to receive the payout bank transfer?

• If the statement shows the platform, the customer will call the platform. The platform needs a true support path and a true reason to be the name on the charge.
• If the statement shows the seller, the seller has to be the seller Stripe onboarded, not a brand invented for the campaign.
• If funds settle to the platform and the seller is paid afterwards, that is a treasury design with licensing and safeguarding questions in some countries. It is not “just a split”. RevRouters is not that treasury.
• If funds settle to the seller, the platform still needs authority for the charge it created. Authority is a Connect relationship, not a shared password.

When a connected account is frozen or rejected

Platforms see connected accounts restricted, rejected or disabled for the same family of reasons as any merchant: identity, unsupported activity, disputes, mismatched websites. The platform’s job is to stop routing sales to an account that cannot take them, tell the seller the truth, and not quietly re-onboard the same seller under a relative’s details.

A freeze at platform level is a different incident. Every connected account’s payouts, or the platform’s own charges, can be affected together. The notice will say which. Do not infer from a single seller’s missing payout that the whole platform is closed, and do not infer the opposite from one successful test charge.