Transitions and provider reviews

The legal company on the processing contract changes

Compare the legal party on your existing agreement with the party named in the notice, then identify the accounts, services, dates and instructions the notice actually changes. Confirm the notice through an established provider channel before redirecting payments or sensitive records. A familiar brand does not establish that the new company holds your agreement, and confirmation of a company change does not by itself verify new bank instructions. Keep the original documents and a dated confirmation together.

For: An owner or authorized representative of a research-only merchant whose processing provider has announced a different contracting company under the same brand.

Updated 2026-10-01

Build a before-and-after record of the provider party

Start with the agreement that names the company providing the affected service. Copy that legal name exactly, including its suffix, and distinguish it from the public brand and the merchant's own legal entity. Next, copy the new party as printed in the notice. Retain both names in the history rather than replacing the old one throughout your records.

Identify what the notice says happened: a name change, an assignment, a replacement agreement or another stated event. Treat this as the provider's description until the relevant documents establish the relationship. If the notice only names a new invoice issuer, that is the change you can record; it does not establish that the gateway, acquirer and every service agreement have all moved. List the affected account and service by a non-sensitive internal label.

Read the notice alongside the applicable agreement

Keep the notice's issue date, the date you received it, its stated effective date and its delivery channel separate. Attach the agreement version and any service addendum it references. Record a requested signature or response as a requested action; do not infer that silence constitutes consent or that the change is ineffective without your signature.

Stripe's Services Agreement illustrates why these checks need separate entries. Its general, service and incorporated terms form the agreement, with regional terms depending on the account country. Section 11.2 addresses notice channels and deemed receipt, section 11.8 addresses amendments, section 11.9 addresses priority among terms, and section 11.10 addresses assignment, including consent and a conditional successor route. None of these headings alone decides whether a particular provider-side change is effective. Read the actual party, clause and applicable regional text, and do not import a fee-change notice period into an entity-change question.

For another provider, use that provider's agreement. Where the documents leave the covered service or effective date unclear, record the two conflicting references and ask the established provider contact which applies. Questions about legal effectiveness, consent or your contractual rights belong with qualified counsel.

Verify each operational instruction separately

Use the provider dashboard or contact route already established in your records to confirm the notice reference, new legal name and affected service. Do not rely solely on a reply to the incoming message or on a phone number introduced by that message. Keep the confirmation date and case reference so another authorized person can see what was confirmed.

Then separate the operational instructions: invoice payee, payment destination, document-upload destination and support route. An authentic announcement can still leave one of these unspecified. Compare complete bank details only within your business's authorized payment controls and the provider's verified channel; record only the verification status in this worksheet. Do not redirect a payment or send records to a new destination while that instruction remains unverified. This check does not decide whether an existing amount is due or authorize withholding it.

Ask explicitly whether the announcement changes any of these instructions or only the named contracting party. A notice silent about payment routing is not an instruction to invent a new route. Likewise, a request for documents needs a stated purpose and verified destination even when the company change itself is confirmed.

Close the factual gaps before updating the working record

Your result should identify what is confirmed, what remains disputed or undocumented, and who owns each next action. Update the working vendor record only for the confirmed change, preserving the old agreement and the dated confirmation. Keep legal questions separate from operational questions so a provider's explanation of its intended change is not recorded as a legal opinion.

For a Prism processing consultation, summarize the affected service, the company-name discrepancy and the question that remains open. The related processing service page describes the consultation scope; any document-review work, responsibilities, fees and terms must be agreed. Send a summary through the inquiry form, keeping contracts containing private details, bank records and customer records in your authorized systems.

Contracting-entity change check

Complete this for one actual notice. Use document references and confirmation status, not bank details or private account identifiers. An unresolved row identifies the specific question to close before acting on that instruction; it does not determine legal validity.

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.

Contracting-entity change check. The last column is for temporary notes.
Change to checkRecord to compareDecision the comparison supportsYour finding
Previous legal partyExact party named in the existing agreement and its version or date.Establish the original counterparty without substituting the provider brand.
New legal partyExact party in the notice and the stated nature of the change.Separate a documented new name from an unexplained company relationship.
Actual notice referenceNotice date, receipt date, channel and reference; retain the original privately.Identify the same announcement when seeking confirmation through an established channel.
Affected agreement and serviceAgreement, addendum, account label and regional scope named in the notice.Identify which relationship changes and which relationships remain unconfirmed.
Effective date and requested actionThe notice's stated date and any signature or response request, beside the referenced clause.Record the provider's instruction without deciding its legal effectiveness.
Payment or document instructionWhether a payee, payment route or document destination is actually changing; compare private details only through authorized channels.Keep each new destination unverified until it has its own confirmation.
Verified provider confirmationEstablished contact route used, date, case reference and exact points confirmed.Update only confirmed facts; assign any remaining operational or legal question to its appropriate owner.

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.

Limits

  • Stripe's agreement clauses are Stripe-specific and depend on the applicable terms and account country; they do not establish another provider's rights or deadlines.
  • This record comparison does not determine assignment validity, consent requirements or the authenticity of bank instructions from a message alone.
  • Keep full bank details, identity documents, credentials and customer records out of the worksheet and ordinary consultation form. A consultation does not approve a processing account.

Sources

  • Stripe Services Agreement general terms — checked 2026-09-29. The agreement combines general, service and incorporated terms with regional scope. Sections 11.2, 11.8, 11.9 and 11.10 address notices, amendments, term priority and assignment. These clauses do not establish the effectiveness of an unseen entity-change notice.
  • Prism contact — checked 2026-09-21. The inquiry requests the website, products and question, excludes sensitive payment and customer records, and does not submit a processing application. Scope, fees and terms are discussed before work.

Discuss my processing options

Want to talk through your own processing situation?