Your Processor Raised Rates Mid-Contract: The Notice Window That Lets You Exit Without an ETF

A processor rate increase can sometimes let you cancel without an early termination fee when the merchant agreement gives you a right to reject the pricing amendment. The window is contractual, not universal. You must follow the exact deadline and notice procedure, distinguish processor increases from network pass-throughs, and obtain written ETF confirmation.

If you are researching whether a processor rate increase cancel without early termination fee provision applies to your account, start with the actual merchant agreement and the specific pricing-change notice—not a general rule about how processors are supposed to handle increases.

Question	What to Check
Where was the increase disclosed?	Statement message, insert, email, portal notification, or separate letter
When does it take effect?	Exact amendment effective date
Is there a rejection window?	Amendment or change-in-terms clause in the governing agreement
Does termination avoid the ETF?	Contract wording must support that result
Is the change a pass-through?	Interchange, assessment, network or third-party charge versus processor markup
How must notice be delivered?	Contract-specified mail, courier, email, portal, fax, or other method
What proof should you keep?	Notice, agreement, delivery record, acknowledgment, case number, and final statement
When should the replacement processor go live?	Before the existing processing setup is disabled

The central rule is simple: the merchant’s actual agreement and the specific fee increase notice merchant agreement language control. There is no universal merchant-services rule giving every U.S. merchant 30, 60, or 90 days to cancel after a processing-rate increase.

That distinction matters because the right to terminate after rate change depends on the contract version, the type of increase, the notice language, and whether the merchant follows the required procedure.

Worldpay’s merchant-processing agreement library illustrates why agreement version matters: it states that the governing Terms and Conditions are generally the version in effect when the merchant signed, unless a later amendment expressly superseded them. A currently posted contract therefore should not automatically be treated as the merchant’s controlling agreement. 

A Rate Increase Can Create a Contractual Exit Window — But Not Always

A merchant-services contract commonly gives the processor some ability to change fees or other terms. The important question is what happens after the processor exercises that authority.

Some agreements pair amendment authority with a merchant rejection or termination mechanism. Others permit specified increases with notice but do not create a special ETF waiver rate increase right. Still others separate processor-controlled pricing changes from interchange, network assessments, taxes, or other pass-through costs.

The language can change significantly between processors and between different versions, sales channels, ISO relationships, acquiring banks, and products offered by the same processor.

For example, an October 2024 Worldpay Merchant Processing Agreement stated that certain increases or newly introduced fees could trigger a penalty-free termination right if the merchant submitted written notice within the period specified by that agreement; Worldpay also retained a contractual opportunity to rescind or waive the increase.

That example should not be interpreted as an industry-wide cancellation period.

A different Worldpay agreement version can contain materially different amendment, notice, acceptance, and pass-through language. This illustrates why a merchant reviewing a processing rate increase letter must retrieve the agreement version that actually governs its account.

Stripe’s current U.S. Services Agreement provides another example of contractual variation. Its terms include provisions governing notice of certain fee increases, modification of the agreement, continued use after amendments become effective, and termination.

Again, those are Stripe’s contractual provisions. They do not establish a universal merchant-account rule.

Before committing to a replacement provider, review the existing contract, cancellation procedure, equipment obligations, and potential early termination costs. Those ordinary switching considerations remain separate from any special right created by a mid-contract pricing amendment.

Where to Look for a Processor Rate-Increase Notice

A processing rate increase letter may never arrive as a traditional mailed letter.

Depending on the merchant agreement and the processor’s communication practices, a pricing change notice might appear in:

• monthly statement messages;
• statement inserts;
• email notices;
• mailed letters;
• processor dashboards;
• merchant portals;
• terms-update pages;
• account notifications; or
• separate contractual amendments.

Whether a particular delivery method is sufficient depends on the merchant agreement’s notice provision and applicable law.

Some processor agreements expressly permit notices through electronic communications, statements, reports, portals, invoices, or postal delivery. The same agreement may impose different requirements on notices sent by the merchant to the processor.

That distinction is easy to miss.

Why Rate-Increase Notices Get Missed

Many finance teams automatically download monthly statements, reconcile deposits and total fees, and never examine the message area.

Other common problems include:

• processor email going to a former owner or controller;
• notices being sent to an outdated administrative email address;
• paper statement inserts being discarded;
• portal alerts going unread;
• multiple locations having different account contacts; and
• staff reviewing totals without comparing individual fee lines.

A merchant statement message should therefore be treated as part of the monthly contract-monitoring process, not just as decorative statement content.

Statement Review Checklist

Each month, confirm that someone checks:

• statement messages and inserts;
• new fee names;
• changed per-item charges;
• changed percentage markups;
• monthly and annual fees;
• gateway or software charges;
• PCI-related charges;
• assessment changes;
• announced effective dates; and
• instructions describing how the merchant may object, reject, or terminate.

Do not assume that a statement notice is automatically ineffective. If the agreement permits statement-based notice, it may satisfy the agreed notice mechanism.

Tracking your effective processing rate across several monthly statements can reveal increases that are difficult to notice from individual fee lines alone. A rising effective rate should trigger a comparison of processor markup, interchange, assessments, recurring fees, and newly added charges.

The Amendment Clause Controls the Cancellation Window

The most important document for a merchant investigating a processor rate increase cancel without early termination fee option is usually the amendment or change-in-terms provision.

Do not search only for “early termination fee.”

Instead, identify four separate elements.

1. Notice Date

The notice date is when the processor communicates that pricing or another contractual term is changing.

The contract may also specify when notice is deemed delivered. That date may differ from the date an employee actually opens an email or reads the monthly statement.

2. Effective Date

The amendment effective date is when the new pricing or fee becomes operative.

Do not automatically treat that date as the rejection deadline.

3. Rejection or Termination Deadline

The agreement may identify a date by which the merchant must act if it wants to exercise a right to terminate after rate change.

Some contracts measure that period from notice. Others use the effective date. Some may contain an entirely different trigger, and some may provide no special amendment rejection mechanism at all.

This is why there is no universal 30-, 60-, or 90-day merchant agreement amendment window.

4. Required Delivery Method

A merchant may have the correct contractual argument and still create a preventable dispute by sending notice through the wrong channel.

The agreement may specify:

• postal mail;
• certified mail;
• courier;
• a designated email address;
• fax;
• a processor portal;
• a specific department; or
• another contractually defined method.

Hypothetical Example

Assume:

• pricing notice issued: March 1;
• increase effective: April 1; and
• The hypothetical agreement states that the merchant must terminate before the effective date to reject the amendment.

Under that hypothetical contract, March 31 would be operationally important.

It does not mean every merchant receives 30 days to cancel.

Clause Language to Find	Why It Matters
“We may amend…”	Establishes processor amendment authority
“Notice will be provided…”	Identifies the agreed delivery method
“Effective on…”	Establishes when the change begins
“Merchant may terminate…”	May create a rejection or termination right
“Without penalty…”	May address ETF treatment
“Continued use constitutes acceptance…”	May make inaction or continued processing important
“Pass-through fees…”	May apply different treatment to network costs
“Early termination fee…”	Determines whether normal termination charges remain applicable

These phrases are illustrative search concepts, not universal contract language.

Is It Really a Processor Rate Increase, or a Network Pass-Through?

This distinction can determine which part of the merchant services contract needs to be analyzed.

Processor-Controlled Pricing Changes

Examples can include increases to:

• processor markup basis points;
• processor per-transaction markup;
• monthly account fees;
• statement fees;
• gateway markup;
• compliance-program charges; and
• annual account fees.

A new processor-controlled charge may constitute a merchant agreement amendment under one contract but be handled differently under another.

Pass-Through or Third-Party Changes

Potential external changes can include:

• interchange changes;
• Visa network assessments;
• Mastercard network assessments;
• card-brand program fees; and
• certain gateway or third-party technology costs.

Visa explains that interchange reimbursement fees are transfers between acquiring and issuing financial institutions, while merchants negotiate and pay their merchant discount to their financial institution. That distinction is useful when testing whether an increase truly originated in interchange or instead came from the processor’s own pricing.

Mastercard similarly distinguishes its interchange rates from the merchant discount rate and merchant pricing arrangement established through the acquiring relationship.

That distinction is important when a processor describes a processor fee increase simply as “Visa/Mastercard costs.”

When reviewing the statement, separate card-network pass-through fees from processor-controlled markup and account charges. That distinction helps determine whether the notice reflects an external cost change, a processor pricing amendment, or a combination of both.

Why the Distinction Matters Contractually

A merchant agreement may permit changes in external costs to flow through automatically without creating the same rejection right that applies to a processor-created pricing amendment.

But that treatment depends on the contract.

Do not assume every network increase is excluded from amendment rights. Likewise, do not assume every new charge appearing near interchange is actually an interchange increase.

Pass-Through Verification Workflow

1. Identify the exact fee name: Do not stop at descriptions such as “card-brand adjustment.”
2. Compare it with the prior statement: Determine precisely which percentage, basis-point markup, or per-item charge changed.
3. Identify how the processor categorizes the charge: Is it interchange, an assessment, a network fee, third-party expense, or processor markup?
4. Verify network claims through official materials: If the processor claims Visa or Mastercard imposed the change, compare the explanation with current official network materials.
5. Compare the amount and effective date: Look for whether the claimed external change aligns with the amount and timing appearing on the statement.
6. Review the pass-through clause: Determine what the merchant agreement says about interchange, assessments, network charges, and third-party expenses.
7. Ask the processor in writing: Request the underlying fee name and confirmation of which portion is processor-controlled and which portion is externally imposed.

Merchants should not have to rely solely on a vague statement such as “card brands raised costs” when reviewing whether a pricing amendment occurred.

How to Use a Processor Rate Increase to Cancel Without an Early Termination Fee

When the contract actually provides a qualifying rejection right, using the processor rate increase cancel without early termination fee window requires more than telling a salesperson that you are leaving.

The process should combine contract review, replacement processing, documented cancellation, and a final account audit.

Step 1: Save the Notice

Preserve the complete source of the notice.

Keep:

• the full statement;
• email and headers;
• mailed letter;
• portal screenshot;
• attachments; and
• date received.

Do not retain only one cropped paragraph.

Step 2: Retrieve the Current Agreement

Collect:

• merchant application;
• terms and conditions;
• program guide;
• pricing schedule;
• amendments;
• equipment agreement;
• gateway agreement; and
• separately contracted software or payment services.

Do not assume that the merchant agreement currently available on a processor’s website is the agreement you signed.

Step 3: Find the Amendment and Termination Clauses

Search the documents for:

• amend;
• amendment;
• modification;
• change in terms;
• notice;
• pricing;
• termination;
• early termination;
• liquidated damages;
• cancellation; and
• deconversion.

Read the surrounding provisions rather than relying on a single keyword result.

Step 4: Calculate the Deadline

Determine the exact contractual termination window using the actual agreement and notice.

Do not guess.

Also identify whether the agreement says notice must be:

• mailed by a date;
• delivered by a date;
• received by a date; or
• submitted before the amendment becomes effective.

Step 5: Secure a Replacement Processing Account

Begin replacement underwriting before closing the existing account.

That does not mean the merchant should let the merchant agreement amendment window expire while negotiating with the replacement provider.

Run both tasks simultaneously.

Step 6: Test the New Setup

Before directing normal payment volume to the new provider, test:

• authorization;
• capture;
• settlement;
• refunds;
• POS terminals;
• gateway connectivity;
• e-commerce checkout;
• recurring billing;
• accounting reconciliation;
• reporting; and
• token migration where supported and permitted.

While the amendment deadline is being tracked, the finance and operations teams can begin preparing the replacement payment-provider transition by reviewing hardware compatibility, integrations, recurring billing requirements, contract obligations, and expected processing costs.

Step 7: Send Written Rejection or Termination Notice

Follow the contract’s notice procedure exactly.

A phone conversation may help create a support record, but it should not replace written termination notice where the contract requires written delivery.

Step 8: Request ETF-Waiver Confirmation

Ask the processor to confirm in writing:

• which pricing amendment is being rejected;
• the requested account closure date;
• the clause under which termination is requested; and
• that no ETF or liquidated-damages charge will apply if the agreement establishes an early termination fee waiver under those circumstances.

Do not treat the waiver as guaranteed until the contractual basis has been established.

Step 9: Preserve Proof

Save:

• tracking numbers;
• delivery receipts;
• timestamps;
• email acknowledgments;
• portal ticket numbers;
• support case numbers; and
• written processor confirmations.

Step 10: Review the Final Statements

After termination, check for:

• early termination fees;
• annual charges;
• final monthly fees;
• gateway billing;
• software charges;
• equipment charges;
• chargeback debits; and
• residual processing activity.

What Should the Written Termination Notice Contain?

A practical amendment-rejection notice normally identifies:

• legal business name;
• DBA;
• merchant ID;
• relevant account number;
• notice date;
• specific pricing amendment;
• amendment effective date;
• statement that the merchant rejects the amendment;
• contract clause relied upon;
• requested termination date;
• request for confirmation that the ETF does not apply;
• authorized signer’s name and title; and
• current contact information.

Including these details improves clarity, but it does not itself create a cancellation right that is absent from the agreement.

Sample Notice Opportunity: Add a short attorney-reviewed merchant termination template referencing the specific amendment clause, amendment date, rejection of the new pricing, requested termination date, and request for written confirmation that the early termination fee will not apply.

Where the clause is ambiguous or the amount at stake is substantial, consider having counsel review both the agreement and the proposed rejection notice.

Do Not Lose the Window Over the Delivery Method

A fee increase notice merchant agreement analysis is incomplete if you review the amendment clause but ignore the notices provision.

Potential contract-approved delivery methods may include:

• certified mail;
• trackable courier;
• designated email;
• processor portal ticket;
• fax where still permitted; or
• another expressly specified method.

Do not assume certified mail is always necessary. More importantly, do not assume that an informal email to an account representative satisfies a contract requiring notice to a designated department or address.

Some published processor agreements demonstrate how detailed these provisions can be, including specific addresses, delivery services, departments, and rules about when notice becomes effective.

Your agreement may be completely different.

Proof File Checklist

Retain:

• full rate-increase notice;
• governing merchant agreement;
• relevant amendment provision;
• relevant notice provision;
• signed rejection or termination notice;
• postal or courier receipt;
• delivery confirmation;
• email headers where email is authorized;
• portal confirmation;
• fax confirmation where applicable;
• support case numbers;
• processor acknowledgment; and
• ETF-waiver confirmation.

Illustrative Rate-Increase Exit Timeline

The following timeline is hypothetical. It is not a universal cancellation schedule.

Date	Action
March 1	Pricing change notice received
March 3	Agreement and amendments retrieved
March 5	Replacement-provider underwriting started
March 12	New processing account approved
March 15	Gateway and terminals configured
March 18	Test transactions completed
March 20	Written rejection of amendment sent
March 22	Contract-compliant delivery confirmed
March 25	ETF treatment confirmed in writing
March 31	Processing moves away from old account
April 1	New pricing would have taken effect

Waiting until the final day leaves little room for delivery failures, incorrect addresses, rejected emails, underwriting delays, processor escalations, or disagreement about the notice procedure.

Do Not Confuse These Dates

At least four dates may matter when analyzing a processor rate increase:

1. Amendment notice date — when the change is communicated.
2. Rejection or termination deadline — when merchant action is required.
3. Amendment effective date — when the changed pricing begins.
4. Merchant-account closure date — when processing actually stops.

They are not necessarily the same.

Also distinguish between:

• the date the merchant must send notice;
• the date the processor must receive notice; and
• the date payment processing actually terminates.

Language such as “received by,” “given within,” “effective upon receipt,” and “effective on” can materially affect contract rights.

Auto-Renewal Is a Different Exit Trigger

A merchant rejecting a contract modification is not necessarily using the same termination mechanism as a merchant leaving at the end of a contractual term.

The merchant services contract may separately contain:

• a contract anniversary;
• an auto-renewal period;
• standard termination notice requirements;
• end-of-term cancellation rules; and
• amendment-specific rejection rights.

Do not confuse:

“I am rejecting this new pricing amendment under the amendment clause”

with:

“I am cancelling at the normal end of my contract term.”

Those may involve entirely different deadlines and consequences.

A normal contract renewal can create a separate opportunity to review and renegotiate payment processing rates, but that renewal process should not be confused with rejecting a specific mid-contract pricing amendment.

How to Switch Processors Before the Notice Window Closes

The operational problem is not simply deciding whether to leave. A merchant must preserve payment acceptance while also protecting any contractual right to terminate after rate change.

Run four tracks at the same time.

Track 1 — Contract Deadline

Determine the final date and valid method for submitting rejection.

Put the deadline in writing and assign responsibility to a specific person.

Track 2 — Replacement Underwriting

Prepare:

• recent processing statements;
• bank information;
• ownership documents;
• business licenses where applicable;
• website information;
• refund policies;
• chargeback history;
• processing volume;
• average ticket;
• highest ticket; and
• card-present/card-not-present mix.

Track 3 — Technical Cutover

Prepare:

• POS hardware;
• gateway;
• API connection;
• hosted checkout;
• recurring billing;
• token migration where possible;
• accounting integrations; and
• settlement reconciliation.

Track 4 — Exit Notice

Do not miss the contractual deadline while negotiating the replacement agreement.

Depending on the contract, the merchant may need to deliver its rejection before every implementation task has been completed.

That does not mean the existing processing account should be shut down prematurely. Keep the old environment operational until the replacement is live and adequately tested where the contractual timeline permits.

Before signing the replacement agreement, compare processing offers beyond the advertised transaction rate by checking cancellation terms, early termination penalties, gateway charges, equipment requirements, pricing structure, integrations, and total expected cost.

What to Do If the Processor Bills the ETF Anyway

An early termination fee appearing on the final statement does not automatically establish that the merchant owes it—or that the merchant does not.

The contract and the evidence still control.

Use the following escalation workflow:

1. Compare the ETF with the governing agreement.
2. Retrieve the original notice of fee increase.
3. Provide proof that rejection or termination was timely.
4. Reference the specific amendment clause.
5. Provide the required delivery documentation.
6. Request a written reversal.
7. Escalate to retention, contract administration, compliance, or executive resolution where available.
8. Preserve every support ticket and reference number.
9. Ask about an acquiring-bank or sponsor-bank escalation path where appropriate and available.
10. Consult counsel if the amount is material or contractual interpretation remains disputed.

Do not assume that every merchant-service contract dispute belongs with the same government regulator or bank.

Regulatory jurisdiction and available legal remedies depend on the parties, agreement, governing law, transaction, and specific dispute.

Evidence	Why It Helps
Original rate-increase notice	Establishes amendment terms and timing
Merchant agreement	Establishes contractual rights
Termination notice	Documents rejection
Delivery receipt	Helps prove timing
Processor acknowledgment	Supports the waiver request
Final statement	Shows the disputed ETF
Support case numbers	Documents escalation
Replacement activation date	Shows the operational transition

Processor Rate Increase vs Other Contract Events

Situation	Likely Question	What Controls
Processor raises markup	Can the merchant reject the amendment?	Agreement and amendment clause
Card network changes interchange	Does a rejection right apply?	Pass-through clause plus agreement
Monthly fee increases	Is this a pricing amendment?	Contract language
Auto-renewal date approaches	Can the merchant exit normally?	Renewal and termination clause
New software fee appears	Who imposed it?	Processor, gateway, or software agreement
ETF charged after timely rejection	Was the waiver right triggered?	Contract, notice, timing, and proof

How easily a merchant can isolate an increase partly depends on its pricing structure. Understanding the differences among tiered, flat-rate, and interchange-plus pricing can help the finance team determine whether network costs and processor markup are separately visible or bundled into broader pricing categories.

How to Make Sure the Next Increase Does Not Slip Past

A permanent statement-monitoring procedure can prevent a future processor fee increase from going unnoticed until after the amendment deadline.

Every Month

Review:

• statement message box;
• effective processing rate;
• processor markup;
• per-item charges;
• monthly fees;
• PCI-related fees;
• gateway charges;
• new line items;
• network assessments; and
• separately identified third-party costs.

Every Quarter

Compare the current statement against:

• prior-quarter statements;
• original pricing schedule;
• current merchant agreement; and
• subsequent amendments or fee schedules.

The purpose is not merely to find a higher total. It is to identify what changed.

Annually

Review:

• contract anniversary;
• auto-renewal deadline;
• annual fees;
• pricing escalators;
• gateway contracts;
• software agreements;
• equipment obligations; and
• opportunities to reassess processor markup.

Maintain a simple Rate Change Log:

Date Detected

Fee

Old Amount

New Amount

Source Claimed

Notice Date

Effective Date

Action Taken

An unexplained increase in effective rate can provide an early signal that statement line items need closer review. Regular effective-rate comparisons make it easier to identify when an increase came from transaction mix, pass-through costs, or a processor pricing change.

Frequently Asked Questions

The Bottom Line

When a processor raises rates during an active contract, do not assume the increase automatically releases the merchant from the agreement.

The safest processor rate increase cancel without early termination fee strategy begins with the specific notice, the agreement version governing the account, the change-in-terms provision, the notice clause, the pass-through language, and the early termination fee provision.

Some merchant agreements create a limited right to terminate after rate change without the ordinary termination penalty. Others may permit the processor to pass through certain network or third-party changes without creating the same right.

The merchant should therefore identify the exact fee that changed, calculate the contractual termination window, preserve the rate-change notice, send any rejection using the required delivery method, establish replacement processing in parallel, retain proof, and obtain written confirmation of ETF treatment.

A processor’s current website terms, another merchant’s cancellation experience, or a salesperson’s memory of a 30-, 60-, or 90-day rule cannot replace the merchant’s actual agreement.