Buying a store with an existing processing account

Identify what the purchase actually changes

Begin with the asset schedule and transaction description. A domain, store files, inventory and a public brand can appear in a purchase without establishing who becomes the party to the payment agreement. Compare the legal entity named on the processing agreement with the entity expected to sell through the site after handover. Keep a change in ownership of an existing entity separate from a proposal for a different entity to take over its account.

Record those facts as stated in the transaction documents. If the documents do not make the distinction clear, that is a transaction question for the parties and their adviser. Website administrator access, possession of a payment plugin and a seller’s ability to show a successful payment do not resolve it. Those observations show access or past operation, not the provider’s instructions for this acquisition.

Read the assignment route for the actual agreement

Stripe’s general terms, recorded as checked on September 29, 2026, contain both consent requirements and a conditional successor-assignment route in section 11.10. The agreement also includes service and incorporated terms, and regional terms depend on the account country. Use the version and documents applicable to the seller’s account when identifying what must be addressed. This page does not determine whether a particular purchase meets the conditions.

Ask the provider to address the described transaction and the proposed account owner, rather than asking only whether a website can be sold. The useful response identifies the applicable process, any consent or notice steps, required information and the point at which the buyer may operate the proposed arrangement. A seller’s statement that the account is transferable remains separate from that response. If the provider requires a replacement account, record that as a dependency rather than treating the existing checkout connection as a substitute.

For another provider, use that provider’s agreement and instructions. Stripe’s successor language does not determine the outcome for a different processing contract, and this worksheet does not decide the legality or enforceability of the sale.

Separate account identity from inherited performance

Stripe’s multiple-account documentation associates an account with the tax ID and legal entity of one business. It also says a new account does not inherit special status from an existing account. A seller’s processing history can describe the seller’s past activity; it cannot establish the buyer’s future account availability, pricing or limits.

Stripe’s business-information requirements describe verification of business identification, including website ownership and bank information, what the business sells and risk. Compare the proposed legal entity, website, research-only catalog and settlement-bank ownership with the information the provider has requested. Record which items need updating or confirmation without putting tax identifiers or bank details into this worksheet.

Changing a payout destination or handing over a login is not evidence that these questions were resolved. Keep the provider’s documented account process separate from the implementer’s work to connect the storefront. A working connection does not establish permission for the successor to accept payments.

Give old orders and new sales separate handover decisions

Inventory the open orders, refund requests, disputes, balances and other unresolved obligations visible in the seller’s records. For each category, identify what the purchase documents say, what the provider says and who will retain authorized access to respond. If the documents disagree or leave responsibility unstated, mark that issue unresolved. Do not infer that acquiring the website extinguishes a liability or transfers it to the buyer.

Use the table to separate confirmed handover work from processing dependencies that remain open. A scheduled website transfer can be a real date while successor processing remains unconfirmed. Give whoever controls the handover the provider response, the unresolved conditions and the responsibility map before treating the store as ready to take the buyer’s sales.

For a Prism processing consultation, summarize the public store, the proposed entity change and the specific unanswered processing question. Keep the purchase agreement and private account records in authorized channels. The consultation can help organize the business description and questions; scope, responsibilities, fees and terms are agreed before work. Account decisions remain with the provider.

Acquisition processing dependency table

Complete this from the transaction documents and the provider’s response. Use document references, match results and unresolved questions. A row is confirmed only to the extent the named record addresses this acquisition; an empty or silent term remains unresolved. Keep private identifiers and agreement contents out of the public form.

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.