A trading-name update is being treated as a new entity

Establish what stayed the same

Start with the legal entity on the existing account and the entity in the current formation or other applicable legal record. Compare them within your authorized records, including whether the entity type or ownership changed. A matching logo, domain, or store operator is not sufficient evidence of entity continuity. Resolve any conflicting records before describing the event as a brand-only change.

The IRS instructions for Form SS-4 distinguish the legal name on line 1 from the trade or doing-business-as name on line 2. That distinction helps explain why a new public name need not be a replacement entity. These are US tax-form instructions, not the provider's update procedure. They also describe a new EIN requirement when a sole proprietorship incorporates or enters a partnership. If that happened, this is more than the trading-name change addressed here.

Build a dated bridge without rewriting history

Put the previous trading name, new trading name, and effective date next to the unchanged entity. Identify which actual record connects each name to that entity: an existing trade-name record, a dated business notice, or an account or trading record that carries the relationship. These are possible evidence locations, not a prescribed document list. If no record establishes the link, mark it unconfirmed rather than manufacturing a document or a date.

Keep older statements and invoices under the names they originally used. An index can explain that those records precede the rebrand, but should not relabel them as documents originally issued under the new name. Distinguish the start of documented operations from the date buyers first saw the new brand. Neither a recent brand launch nor an older formation date proves a period of sales on its own.

Separate public details from legal identity

Stripe's account-setup documentation identifies name, website, support contacts, and statement descriptor as public business information that should clearly identify the business. Inventory the surfaces affected by the rebrand. A changed public-name field does not, by itself, explain why a legal-entity field should change. Record the intended change and the value currently shown; do not overwrite legal identity just to make every field use the brand.

Stripe's restricted-businesses policy prohibits misleading information about the business and processing for undisclosed products. Preserve an accurate description of the research-only catalog throughout the change. If the rebrand also changed products, ownership, or country, disclose those as separate facts. Another provider's update instructions must come from that provider; Stripe documentation does not establish its rules or the merchant's eligibility.

Request the correction the evidence supports

Use the existing provider conversation to identify the field, notice, or document request that treats the business as new. Explain which entity facts remain unchanged, which trading-name details changed, and which dated records connect them. Ask whether the appropriate route is an update to the existing account and what evidence is required. Record the answer and any outstanding condition. Do not open a replacement account merely to escape the mismatch or treat silence as approval.

For a scoped Prism processing consultation, describe the website, research-only products, and identity mismatch in ordinary language. Prism can discuss processing preparation and a provider's website questions; scope, fees, and terms are agreed before work. Keep identity documents, identifier values, passwords, and customer records out of the public inquiry. The request receives follow-up by email and is not a processing application.

Rebrand identity bridge

Complete this from existing records. Reference private documents by a non-sensitive label and keep their originals in authorized storage. An unexplained link stays unresolved. Use the bridge to request the provider's update route, not to declare the account approved.

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.