My Merchant Left Their Processor. Do I Need to Explain Why?

Last Updated on July 1, 2026

No. A good acquirer doesn’t ask why a merchant left their prior processor, and you shouldn’t volunteer an explanation either. The processing statements contain the actual story. Any narrative you add around them is, at best, redundant, and at worst, it raises questions that don’t need to be addressed.

This is one of the questions agents ask most often, and the instinct behind it is understandable. You’re trying to get ahead of a concern you assume the underwriter will have. But the concern you’re anticipating isn’t how underwriters actually evaluate processor transitions. Here’s what they’re actually looking at and what you should be focused on instead.

Why Processor Transitions Happen & Why the Reason Doesn’t Matter

Merchants change processors for all kinds of reasons. Better rates. Better service. A platform that fits their vertical. A referral from a trusted contact. Sometimes a termination. Sometimes a freeze. Sometimes just an expiring contract and a decision to shop around.

None of those reasons are, on their own, a signal that tells an underwriter anything useful about the merchant’s risk profile. An underwriter who needs to understand a merchant’s risk profile doesn’t ask why the merchant changed processors. They read the processing statements. Those statements contain everything that actually matters:

• Chargeback ratios by count, month over month
• Refund ratios and trends
• Volume trajectory and consistency
• Reserve activity
• Average ticket behavior

If those numbers are clean, the transition history is irrelevant. If those numbers show a problem, the narrative explanation of why the merchant left doesn’t fix it. In either case, the explanation isn’t doing any analytical work. The data is.

The Problem with Offering an Explanation Anyway

When an agent volunteers an explanation for a processor transition (even if it’s favorable) it can create friction that wouldn’t otherwise exist.

Consider what happens when you write something like: “The merchant left their prior processor because they were unhappy with service and felt they could get better rates elsewhere.”

That sentence raises a question it doesn’t answer: were they terminated, or did they leave voluntarily? A statement like that is indistinguishable from a softened version of a termination narrative. Now the underwriter is wondering whether there’s something to look for when, without the explanation, they would have simply read the statements and moved on.

The same dynamic applies to more specific explanations. “The merchant had some elevated chargebacks in Q3 but they addressed it.” That sentence is now doing the work of flagging Q3 as a problem period, inviting scrutiny of exactly the months you’d rather have read in context. Without the explanation, Q3 is just another set of numbers in the statements that are evaluated on what the trajectory looks like before and after, not on the weight of a call-out that signals something was wrong.

This isn’t about withholding information. It’s about understanding that the processing statements are the complete, verifiable record. Narrative around them introduces a self-serving layer that underwriters are trained to discount, and that can actively draw attention to the wrong things.

What Underwriters Are Actually Looking For

When a processor transition is visible in a submission, either because the merchant disclosed it, or because the bank statements show deposit credits from a prior processor, here’s what a good underwriter actually wants to know:

Are the processing statements from the right entity? Before relying on statements as evidence of a merchant’s history, underwriters verify that the DBA name, legal entity name, and MID number on the statements match the applicant. History from a prior entity under the same principal isn’t automatically transferable. This is an internal check, not something agents need to provide an explanation for.

What do the most recent months show? The most recent statements are the controlling evidence. A merchant whose older statements show elevated chargebacks but whose recent months are clean is evaluated on the current trajectory, not the worst point in the history. The data does that work automatically, without any narrative needed.

Are there processors in the bank statements that aren’t represented in submitted statements? Underwriters look for processor deposit credits in bank statements and cross-reference them against submitted processing statements. If a processor appears in deposits but no statements were submitted for that relationship, it gets flagged — not because the merchant owes an explanation, but because the coverage question gets addressed in the underwriting process. The right response, as an agent, is to collect statements from every processor showing up in the bank deposits, not to explain why a particular relationship ended.

Is there reserve activity visible in the statements? If a prior processor was holding a reserve against the merchant, it appears in the statement data. That’s worth understanding, but again it’s a data question, not a narrative question.

Different Transition Scenarios & What They Actually Mean

The merchant chose to leave. No flag. Standard submission with three months of processing statements. The underwriter evaluates the statements. Move on.

The merchant was terminated for chargebacks. The statements show what the chargeback picture looked like. If current metrics are clean, the termination history doesn’t control the outcome. If current metrics are still elevated, the deal has a chargeback problem that needs to be addressed through remediation evidence instead of being explained away. The termination itself isn’t what matters; the current state of the metrics is.

The merchant was frozen or terminated by Stripe or Shopify. As covered separately, these platforms have significantly more conservative risk tolerances than traditional acquirers. A freeze or termination from either platform is not a MATCH event and doesn’t carry the same weight as a termination by a registered acquirer. Submit the statements or dashboard export and let the numbers speak.

The merchant was terminated for a policy violation. This is the scenario where the reason for the transition is most relevant, but even here, the right approach is to address it through documentation, not narrative. The question is whether the merchant’s current operations still involve the practice that caused the violation. The answer comes from the site review and the operational picture, not from an explanation of what happened with the prior processor.

The merchant has statements from multiple processors. Common practice. Merchants distribute volume across processors for capacity, redundancy, or commercial reasons. This isn’t suspicious and doesn’t need explanation but it does mean you should submit statements from all of them. Underwriting evaluates the merchant’s overall processing health across every active processor, since the combined chargeback and refund picture is what determines whether the merchant is within threshold and whether a reserve or chargeback mitigation plan is warranted. Any processor visible in the bank deposits that isn’t covered by submitted statements will be requested anyway, so submitting the full set upfront is faster than a follow-up round.

The One Thing That Replaces Every Explanation

Three months of clean processing statements from the current or most recent processor.

That’s the submission that moves a processor transition from an open question to a non-issue. Not a cover letter explaining the circumstances. Not a written narrative from the merchant about why things are different now. The statements.

If the statements show consistent volume, chargeback ratios in range for the vertical, and no unusual reserve activity, there’s nothing for the underwriter to pursue. The transition becomes background context, not a finding.

If the statements show something that needs to be addressed, such as elevated current chargebacks or a reserve that suggests the prior processor had concerns, then the work is in resolving the underlying issue, not in crafting a better explanation of it. No narrative substitutes for clean current metrics.

What to Actually Submit When a Merchant Has Changed Processors

The standard document ask doesn’t change because a merchant changed processors. Here’s what a complete submission looks like:

• Signed merchant application. The application is where the merchant discloses their current processing relationship and volume. It answers the “are they currently processing?” question directly, so the statements-ask can be scoped to what’s current.
• Three most recent monthly processing statements from the current or most recently used processor. If the merchant was using Stripe or Shopify Payments and doesn’t have formal monthly statements, a dashboard export showing chargeback ratios, transaction counts, and payout history through a recent date is acceptable for most deals.
• Three months of business bank statements. These allow the underwriter to cross-reference processor deposits, identify other processors in the transaction history, and complete the revenue substantiation picture.
• Financial statements if monthly volume is above $250K.

That’s the package. The transition history doesn’t add a document. It doesn’t add a narrative section. It surfaces through the statements themselves, and the statements answer it.

A Note on What a Good Acquirer Looks Like

Part of what distinguishes acquirers who are actually useful to agents is what they don’t ask for. An underwriter who asks merchants to explain why they left a prior processor is substituting a self-serving narrative for data they already have access to. Processing statements are a verifiable record. A merchant’s explanation of why they left isn’t.

When you’re evaluating an acquirer relationship, the length and composition of the pending list is one of the clearest signals of underwriting discipline. A processor who asks for explanations and narratives alongside documents is running a less efficient process and creating more friction for your merchant relationship. A processor who reads the documents and asks only for what they can’t source independently is respecting your time and your merchant’s.

The processing statements tell the story. That’s not a simplification. It’s how good underwriting works.

Frequently Asked Questions

Do I need to disclose that my merchant was terminated, or can I let the statements speak for themselves? The merchant application asks about processing history, and it should be filled out accurately. What you don’t need to do is add a written explanation or narrative around a termination. The application captures the disclosure; the statements provide the evidence. The narrative in between doesn’t add anything the underwriter can act on.

What if the underwriter asks me why the merchant left? That’s a signal worth noting. A well-structured underwriting process routes that question back to the statements, not to the merchant or agent. If you’re asked, a clean response is: “The statements reflect the full picture of their processing history.” Then let the underwriter tell you what specific finding in the statements is driving the question — because that’s the thing worth addressing.

My merchant was terminated and doesn’t have statements from the last processor. What now? This is worth addressing directly rather than hoping it doesn’t come up. If the termination happened mid-cycle and formal statements aren’t available, bank deposits from that period may provide partial visibility. If statements simply don’t exist because the relationship was short or the termination was immediate, that context — disclosed on the application — is the appropriate place for it. No additional narrative is needed.

My merchant voluntarily left a processor mid-month. Will that look like a termination? Not if the application is completed accurately and the bank statements reflect consistent, normal deposit activity through the end of the relationship. A mid-month transition shows up as a natural break in deposit credits, not as anything that needs explaining.

Can I include a brief cover note with my submission to give context on the merchant? Cover notes that describe the merchant’s business, summarize their history with your agency, and orient the underwriter to what’s in the package are useful. Cover notes that explain processor transitions, characterize prior chargeback problems, or get ahead of expected underwriting concerns are doing work the documents should be doing — and as noted above, they can introduce friction by calling attention to things that might otherwise have read cleanly from the data.

What if the merchant has statements from three different processors in the last year? Submit statements from all of them. Underwriting evaluates the merchant’s overall processing health across every active processor — the combined chargeback and refund picture across all of them is what determines whether the merchant is within threshold and whether an ongoing reserve or chargeback mitigation plan is needed. A single processor’s statements only tell part of the story. And because the bank statements reveal deposit credits from every processor, any relationship not covered by submitted statements surfaces and gets requested anyway. Submitting the full set upfront is both faster and the transparency underwriting expects on processing history.

Back