Changing the Shop Name or Owner? Check the Merchant Account First worksheet
A bounded entity-change register separates legal identity, account access, customer labels and provider acceptance without assuming approval transfers.
No signup. Enter reference codes, add records and download a CSV. Entries stay in the browser tab. Filled fields do not establish completion, approval or compliance.
| Change type and internal transaction reference | Current and proposed identity record references | Provider notice and required process | Customer-facing surfaces affected | Approval and effective-date evidence | Historical records and unresolved owner |
|---|---|---|---|---|---|
| Fictional DBA change C-11 | Entity file A, proposed trade-name file B | Awaiting provider classification | Receipt, descriptor, payment page | No approval recorded | Current records preserved, owner assigned |
- Starting values are fictional examples, not merchant or customer records.
- Check the source record before marking a step complete. Unknown is not approval.
- This manual worksheet does not connect to a provider or make account changes.
- Export to approved storage before leaving the page.
After a sale, changing the sign doesn’t transfer the merchant account. Someone changes the payment page heading and assumes the merchant account has transferred too. Those are different things. Before you touch payment details, separate the legal business, trading name, the people with account access and customer-facing labels. Then ask the actual provider which process applies to the proposed change.
Use with this guide
BlueFinch advisor service
Continue with BlueFinch advisor service.
online payment tools
Continue with online payment tools.
Books workspace
Continue with Books workspace.
Repair refunds after a processor change: retain access
Prepare repair refunds before closing an old processor account. Use the access worksheet to track original transactions, funding and provider instructions.
Classify the change before editing fields
A DBA update doesn’t necessarily mean you have a new legal entity. An asset sale, ownership change, new tax identity, and replacement account administrator aren’t interchangeable, either. Have the responsible business adviser establish the facts. This article gives you a notification record, not a legal conclusion about the transaction or an instruction to transfer an account without approval.
Changing the account administrator doesn’t mean the processor has approved a new business owner. Stripe has separate guidance for transferring an account to another entity after a sale and changing its account-owner user. Check the distinction with your own provider. Ask which documents and reviews you’ll need, and whether you need a new account. Another processor’s instructions don’t prove your existing approval transfers to a buyer.
Sources for this section: Stripe: entity changes following a sale or acquisition · Stripe: changing the account user who holds ownership
Give the provider a clear change description
Start with the BlueFinch advisor service to find the right provider contact and confirm the agreed support scope. Explain what’s changing, when it should happen, and which account references are affected, using the approved route. Ask what information to send securely, who’s allowed to submit it, and what evidence will confirm acceptance. Get a clear next step from the support conversation, not a vague instruction to update everything.
Stripe tells merchants to contact support first when an entity changes. It specifically says not to email details about the new owner. Instead, account updates go through a controlled process. That’s a useful example: separate the notification from collecting sensitive documents. Don’t put tax IDs, bank details, personal identity records, or credentials in this public worksheet. Reference approved records instead.
Sources for this section: Stripe: entity changes following a sale or acquisition · BlueFinch: human advisor service scope
Map the labels customers will encounter
List the merchant identity currently shown on receipts, the published payment page and the statement descriptor where applicable. Record the support contact too. Check which system controls each field. The online payment tools include business identity and receipt-contact settings, but editing a design doesn’t mean the provider changed its legal entity or bank-statement description. Verify those changes through the provider’s own supported process.
The same legal entity adopts a new trade name while keeping its ownership unchanged. That’s one fictional shop. Its provider still has to classify the change and approve whatever updates its agreement requires. A second fictional shop gets sold to a different entity. Treating both as the same visual rebrand misses the bigger identity question in the second case. Keep those cases separate on the worksheet before either owner changes payment instructions.
Sources for this section: Stripe: entity changes following a sale or acquisition · BlueFinch: actual online-payment features and activation limits
Preserve the handoff and historical records
Record the provider’s decision, its effective date, and any conditions still unresolved. A submitted request does not mean approval. Keep existing customer obligations, past receipts, and pending adjustments traceable in the right business records. Ask who remains authorized to handle refunds or disputes from before the change. Don’t close the old account or erase its history just because the new logo is ready.
Use the Books workspace for supported financial records, and get the responsible accountant involved in matching accounts. Confirm how you’ll identify old and new processing activity. Don’t assume every business sale gets the same accounting treatment. This review is about identity and notifications, not the broader annual talk about transaction volume, pricing, or new payment methods.
The worksheet captures the change type, identity references, provider process, affected customer surfaces, acceptance evidence, and ownership of historical records. After the required review, test approved customer-facing changes through the provider’s permitted process. Remove obsolete staff access through authorized administration, not shared-password handoffs. Completion means relevant records and approved customer labels agree, with any remaining conditions visible. It does not mean an advisor conversation guarantees underwriting, transfers legal responsibility, or approves every part of the business sale.
Sources for this section: Stripe: changing the account user who holds ownership · BlueFinch: Books setup and reviewed recordkeeping
Primary sources
BlueFinch last reviewed these sources on October 23, 2026. Check the linked sources for current requirements and product details.
- Stripe: entity changes following a sale or acquisition
- Stripe: changing the account user who holds ownership
- BlueFinch: human advisor service scope
- BlueFinch: actual online-payment features and activation limits
- BlueFinch: Books setup and reviewed recordkeeping
Use this page for general business information. It is not legal, tax, or accounting advice.