Separate legal entities sharing one payment account

Follow the sale to its seller

Start with the customer-facing agreement, invoice and order record for each real sales flow. Write which legal entity those records identify as the seller, which company holds the processing agreement and which entity receives the funds. Keep the public brand and the owners in separate fields. Shared directors, staff or branding do not answer which company contracted with the buyer.

If the documents name different companies, preserve the disagreement. Do not choose the processing-account name simply because that would make the map line up. Identify the person who can establish the actual contractual arrangement from the business records. If seller identity remains uncertain, that is the unresolved input to take to the appropriate adviser before describing the arrangement to a provider.

This comparison is narrower than an inventory of every brand or domain. Several names can belong to one entity, while two entities can have the same owners. The question here is whether the company responsible for a sale matches the account arrangement proposed for that sale.

Apply Stripe's account rule only to Stripe

Stripe's multiple-account documentation associates each account with the tax ID and legal entity of one business. It also says independent projects, websites or businesses need separate accounts. Common ownership does not turn separate legal entities into the single entity associated with that account. The same legal entity can use its tax ID across multiple Stripe accounts where the documented public-information conditions fit; that does not allow several entities to become one account entity.

A newly activated Stripe account does not inherit special status from an existing account. Separating the accounts therefore addresses the entity mapping, but does not establish that Stripe will approve the new company's research-only catalog or provide the same terms. Technical access to an account and successful processing are different from an eligibility decision.

Stripe's recorded restricted-business policy prohibits misleading descriptions of the business and processing for undisclosed products, and describes approvals as service-specific and subject to change or revocation. Use the actual entity and catalog in the inquiry. Do not describe one company's products as another company's activity just to match the account already available. These Stripe statements do not establish the account rules of an unrelated provider.

Put the proposed arrangement into one answerable request

For each selling entity, give the provider a concise description of the customer contract, sales channels, research-only catalog, proposed account holder and intended recipient of funds. Ask which entity must hold each account, whether the proposed flow is supported and what separate review or onboarding is required. Identify the existing agreement or account through the provider's authorized channel rather than exposing account details in a public form.

A reply about the parent company's existing account does not close a question about sales made by its subsidiary unless the reply actually addresses that arrangement. File the answer with the entities, domains, product scope and services it names. If the provider answers only part of the request, mark the remaining part unanswered. Do not treat a general statement about shared ownership as a specific account decision.

Where the provider describes a platform or another structured arrangement, request its documentation and responsibilities for that exact product. Do not implement an informal funds-routing workaround and call it the provider's approved arrangement. This worksheet identifies the decision needed; it does not design a payment platform or settle tax and contractual treatment.

Choose the next step from the unresolved mismatch

If all the sales you mapped belong to the account's entity, you have closed that identity comparison, but still need to confirm coverage of the actual business and services. If a sale belongs to another entity, do not treat the existing account as covering it by association. For Stripe, use the documented separate-account requirement as the starting point for the inquiry. For another provider, keep the proposed use unresolved until its answer addresses the entities and flow.

If the arrangement is already operating, preserve the true order, account and settlement records and seek instructions about the identified mismatch. Renaming historical sales would erase the facts the provider needs. For a Prism processing consultation, summarize the entities and the question you need organized. Prism can discuss accurate preparation; the provider decides eligibility and account terms. Scope, responsibilities, fees and terms for any assistance are confirmed before work.

Entity-to-sale responsibility map

Complete one copy for each actual selling entity and sales flow. Use document references and entity names, not tax IDs or bank details. Read across for mismatches; an empty provider-answer field means the proposed arrangement remains unconfirmed.

Worksheet entries are not submitted by Prism’s worksheet and are not saved by the site. Use record types, availability, anonymized observations, or match/mismatch results. Do not enter government identifiers, customer names or addresses, customer messages, receipt-access links, card or bank details, passwords, or keys. Send sensitive documents only through the provider’s verified secure channel.

These are temporary notes. Leaving or reloading this page may clear them. Worksheet entries are not sent automatically. If you copy notes into the consultation message and submit the form, Prism receives them as part of your request.