Can a PSP increase my rolling reserve after I've signed the contract?

Yes. Most PSP agreements allow reserve adjustments based on chargeback rates, fraud signals, or general risk reassessment — often with as little as 5 business days notice. The initial reserve percentage in your contract is a floor, not a ceiling.

What happens to my card tokens if I switch PSPs?

In most cases, PSP-issued tokens cannot be transferred. The card data vaulted by your PSP belongs to them — not you. Migrating requires either a raw card data export (PCI-intensive) or re-authorisation campaigns that typically see 10–25% subscriber churn.

How long can a PSP hold my funds?

Legally, timeframes vary by jurisdiction. Commercially, most agreements allow 90–180 day reserve holds. If your account is terminated for cause, funds may be held for the full rolling reserve period plus 120 days to cover potential chargebacks.

Is the 'interchange plus' pricing model actually transparent?

Interchange itself is passed through at cost in a genuine interchange-plus model. The red flag is undisclosed markup on scheme fees — assessment fees, FANF, cross-border fees — which are added on top and often not itemised in statements.

Can I negotiate PSP contract terms?

Yes, above roughly $1M monthly volume. Below that, most processors offer take-it-or-leave-it terms. Above $5M, exit terms, reserve mechanics, and pricing escalators are all negotiable. Above $25M, you should have legal counsel review and redline the full agreement.

Psp And Infrastructure 12 min read

14 PSP Contract Red Flags That Cost Merchants Millions

The clauses most operators sign without reading — and why they're expensive. A practical guide to the PSP agreement terms that shift liability, lock up cash, and limit your exit options.

By Shaun Toh May 12, 2026

TL;DR

Most operators sign PSP contracts without redlining a single clause. These 14 terms are where processors shift risk to merchants — on reserves, pricing, exit rights, and liability.

Most merchants sign PSP contracts the same day they receive them. The platform onboarding flow deposits a 40-page agreement at the end, next to a “Sign and get started” button. Most operators click through.

Those 40 pages are where processors concentrate risk transfer. The product team built an API. The legal team built the contract. The contract usually wins.

These are the 14 clauses worth reading before you sign — and redlining before you agree.

Reserve and Cash Flow

1. Rolling reserve with no defined release trigger

A rolling reserve is a percentage of each transaction held back as a buffer against chargebacks. Legitimate risk management. The red flag is when the release schedule is undefined or contingent on unspecified “risk conditions.”

Standard terms: 5–10% of transactions held for 90–180 days. On a business processing $50K per month at 10% over 180 days, that’s roughly $30K of working capital permanently sitting in your processor’s account at steady state — not yours.

Push for: A defined release schedule tied to specific metrics (chargeback rate below 0.5%, account age over 6 months), with automatic release at the end of the stated period without requiring merchant action.

2. Reserve increases after onboarding — with minimal notice

Most agreements include a clause allowing the processor to increase your reserve percentage based on “risk assessment,” “changes in chargeback volume,” or similar language. The baseline reserve in your signed agreement is a floor, not a ceiling.

The risk: a single elevated chargeback month can trigger a reserve increase that persists long after chargebacks normalise.

Push for: Written notice of minimum 30 days before any reserve increase takes effect, and a defined process to contest increases with supporting data.

3. Settlement timelines buried in general terms

Standard settlement for low-risk merchants is T+2. Many agreements include a broader clause allowing the processor to extend settlement “during periods of elevated risk” or “at the processor’s discretion.” This language can stretch T+2 to T+7 or longer with no breach of contract.

Push for: An explicit settlement SLA (e.g. T+2 for standard transactions) with a defined escalation process and maximum hold period stated in the contract, not just in a help article.

4. Pooled or aggregated settlement

Some processors — particularly those using a platform or payment facilitator structure — settle funds into a shared account before distributing to sub-merchants. If your processor operates this way, your funds are commingled with other merchants’ funds. Reconciliation becomes difficult, and your dispute rights against a third-party payer are less clear.

Push for: Direct settlement into your own merchant account, or explicit documentation of the sub-merchant structure and your rights within it.

Pricing

5. FX markup declared as a “conversion rate,” not a fee

If you accept cross-border cards, your processor converts from the transaction currency to your settlement currency. The rate they use will typically include a margin — often 0.5–2.5% — above the mid-market rate. In most agreements, this margin is not declared as a fee. It appears as a slightly unfavourable conversion rate.

This matters because: interchange-plus pricing is often quoted exclusive of FX, and because FX margin is not itemised in most settlement reports. Cross-border merchants are frequently surprised to find their effective cost of acceptance significantly higher than their quoted rate.

Push for: Explicit disclosure of the FX margin as a named fee, benchmarked against the European Central Bank mid-market rate or equivalent. Alternatively, negotiate a fixed spread rather than an exchange-rate discretionary margin.

6. Scheme fee pass-through with undeclared markup

Genuine interchange-plus pricing passes interchange at cost and adds a transparent PSP margin. The less obvious component: scheme fees. Visa and Mastercard charge assessment fees, cross-border fees, FANF (Fixed Acquirer Network Fee), and other per-transaction or periodic charges. In many “interchange-plus” contracts, these fees are passed through with a markup that is not disclosed as a separate line item.

Push for: A full breakdown of scheme fee components in the pricing schedule, with an explicit statement of whether fees are passed at cost or with a markup. Request sample itemised settlement reports before signing.

7. Annual pricing escalation with no cap

Standard industry language allows the processor to increase pricing annually, typically with 30–60 days written notice. On a three-year contract with uncapped annual increases, a 3–5% annual escalation compounds significantly over the term.

Push for: A cap on annual increases (e.g. CPI or a fixed maximum percentage), or a right to exit the contract at no penalty if pricing increases exceed a defined threshold.

Account Control

8. Unilateral MCC reclassification

Your Merchant Category Code determines how your transactions are classified for interchange purposes, scheme rules, and risk monitoring. Most agreements allow the processor to reclassify your MCC if your business model changes — but some language is broad enough to permit reclassification based solely on the processor’s risk review.

Reclassification to a higher-risk MCC can trigger reserve requirements, affect your interchange rate, and flag your account for enhanced monitoring — all without your consent.

Push for: A requirement for written notice and a right to dispute before MCC reclassification takes effect. Ask the processor to specify the exact MCC assigned at signing.

9. Vague acceptable use policy with retroactive enforcement

Acceptable use policies define what businesses, products, and transaction types the processor will support. The red flag is when the AUP is written with broad discretionary language — “activities we deem inappropriate,” “businesses that create reputational risk” — rather than a specific prohibited category list.

Vague AUP language allows termination for any reason the processor can frame as an AUP breach. It also means your account can be terminated for activities that were permitted when you signed but are later deemed problematic — without the AUP being formally amended.

Push for: A specific, exhaustive prohibited activities list. Avoid agreements where AUP violations are defined by the processor’s “sole discretion” without appeal. Request a right to cure period for alleged violations before termination.

10. Audit rights asymmetry

Most PSP agreements include a clause permitting the processor to audit your business, request documentation, inspect transaction records, and review compliance with their terms. Almost none include a reciprocal right for merchants to audit the processor.

This matters particularly for scheme fee pass-through, reserve management, and settlement accuracy. Without an audit right, you have no contractual mechanism to verify that what you’re being charged reflects what was agreed.

Push for: Reciprocal audit rights covering fee reconciliation, reserve calculations, and settlement accuracy. At minimum, negotiate access to raw scheme fee invoices alongside your settlement statements.

Exit Terms

11. Long termination notice plus immediate suspension

Standard termination notice is 30–60 days. But most PSP agreements also include a clause permitting immediate suspension — of your ability to accept payments and access funds — for “cause,” broadly defined. The practical result: your legal notice period is 60 days, but your effective exit can be immediate and involuntary.

Push for: Clarity on what constitutes “cause” for immediate suspension (specific triggers, not discretionary language). A cure period of at least 10 business days before suspension for non-emergency compliance issues. Written notice requirements for any suspension action.

12. Token vault ownership

When customers store a payment method with you, the card details are typically vaulted by your PSP — not you. PSP-issued tokens are processor-specific. When you leave, those tokens do not travel with you.

Network tokens (Visa Token Service, Mastercard Digital Enablement Service) are scheme-issued and more portable — but even these are bound to the merchant ID the PSP operates on your behalf. A full migration requires either a raw card data export (a PCI-intensive process) or a subscriber re-authorisation campaign.

This is the single most underestimated migration cost. A 10–25% failed re-authorisation rate on active subscribers represents real ARR loss that should be modelled in any PSP switch decision.

Push for: Explicit contractual confirmation that you own the right to export your customers’ vaulted payment data in a portable, PCI-compliant format. Confirm who holds the vault — the PSP or a third-party tokenisation provider — and what portability rights exist in each case.

13. Data export limitations

Beyond card vaults, most PSP agreements contain limited language about data portability on exit. Transaction history, customer profiles, dispute records, and reconciliation data may be accessible for a limited time after termination — or may not be available in a format that integrates with other systems.

Push for: A minimum 24-month data retention and export right post-termination, in machine-readable format. Define the format explicitly (CSV, JSON, structured API access) rather than leaving it to the processor’s implementation.

Liability

14. Force majeure that covers routine outages

Force majeure clauses excuse performance during extraordinary events — natural disasters, war, government action. The red flag is when the clause is written broadly enough to include “technical failures,” “infrastructure outages,” or “service disruptions” — effectively covering the processor for routine downtime.

If your checkout goes dark because your PSP has an infrastructure failure, a broadly written force majeure clause means you have no SLA remedy, no credits, and no breach claim.

Push for: A carve-out from force majeure for ordinary infrastructure failures, with an explicit uptime SLA (e.g. 99.9%) and defined compensation for SLA breaches. Review the SLA carefully — many are written as targets rather than commitments.

The negotiation reality

These 14 terms are negotiable — see the PSP negotiation playbook for how to use that leverage. Most operators don’t negotiate because they don’t know they can — or because the friction of asking feels disproportionate to the perceived risk of signing.

The leverage calculus is roughly:

Under $1M monthly volume: Limited leverage. Standard terms are largely take-it-or-leave-it. Focus on exit terms and token vault language.
$1M–$10M monthly: Pricing escalators, reserve mechanics, and data portability are negotiable. Request redlines.
Above $10M monthly: Full legal review is warranted. Every term in this list is negotiable. The processor needs your volume more than you need their specific platform.

The contracts that cost operators the most are not the ones they negotiate poorly. They are the ones they sign without reading.