ISO Review: A Merchant Entity Change

Why is this more than a trading-name edit?

A merchant may keep the same website and brand while changing the legal company that contracts with customers. The ISO must determine whether the request concerns a display-name edit, a new seller, a business transfer or another arrangement. Do not describe an entity change as a routine account setting before the provider has reviewed it.

Adyen's account-structure documentation illustrates that legal entity, merchant-account structure and acquiring region can be linked within a provider's setup. That is provider-specific evidence, not a universal transfer procedure or a statement about MerchantBridge relationships. The actual provider must confirm what the proposed change requires.

Sources: Adyen: Defining your account structure

What does a before-and-after comparison need?

Start with facts that can be described without confidential ownership files. Record the current seller and proposed seller, their operating jurisdictions, the intended change date and the reason the business is asking for review. Identify any change in products, customers or fulfillment at the same time.

Keep operating address, incorporation, customer location, acquiring region and settlement currency distinct. A new bank account or currency preference does not by itself explain the legal seller. If the merchant is still deciding its structure, label that as a proposal rather than submitting it as completed.

How can a fictional transition expose the unfinished work?

Imagine Company A sold a subscription in October and Company B is proposed as the seller for new subscriptions in December. The website will look the same. The ISO should ask who remains responsible for the October customer obligation and any refund, rather than assuming the new company can process every historical adjustment.

Now add unfulfilled orders and recurring customers. Those facts require separate operational and contractual decisions. A provider's willingness to consider new sales does not establish that saved payment credentials, historical refunds or recurring permissions transfer. Ask for the applicable supported process; do not imply that MerchantBridge can move them automatically. This is a hypothetical planning example, not advice that a transfer is legally effective.

Which checklist supports the receiving partner?

Use a short comparison with an owner for each unresolved question. Do not send full bank statements or beneficial-owner records in the initial introduction.

• Current and proposed legal seller, jurisdiction and trading name.
• What changes in the customer contract, receipt and public terms.
• Which entity receives new sales and which retains historical obligations.
• Outstanding deliveries, subscriptions and refund responsibilities.
• Requested settlement arrangements and the entity named on the bank account.
• Proposed transition date, dependencies and the provider decisions still needed.

When is the referral ready to discuss?

The first conversation can proceed when the ISO can explain the change and distinguish confirmed facts from unresolved decisions. It does not require a finished legal restructuring, but it should not conceal one. If nobody can identify the seller for a transaction date, pause that portion and obtain clarification from the merchant and its advisers.

Ask whether the described new-sales arrangement can be considered and what separate review applies to the transition. Keep any referral terms separate. No approval, acquiring coverage, residual continuity or protection of an existing relationship is implied by sending a comparison to MerchantBridge.