Payment service provider and acquiring agreements sit at the intersection of contract law, payment regulation, and the specific compliance standards that govern digital-asset businesses. When a PSP (payment service provider) or acquiring bank terminates a relationship with a crypto company, the consequences are immediate and severe: card processing stops, fiat settlement halts, and customer onboarding collapses. Understanding the legal architecture of these agreements – and where disputes actually arise – is the first step toward protecting the rails your business depends on.
With fiat rails (the bank accounts and payment channels that connect crypto platforms to the traditional financial system) growing harder to secure and easier to lose, operators across the spectrum – exchanges, custodians, token issuers, EMI-backed fintechs – face a recurring structural risk: the agreement they signed contains termination, reserve, and liability clauses they did not fully map at onboarding. By the time the dispute materialises, options narrow quickly. This analysis maps the key dispute vectors, the cross-border complications that amplify them, and the strategic choices available to a business when the relationship breaks down.
What Is a PSP or Acquiring Agreement, and Why Do Disputes Concentrate There?
A PSP or acquiring agreement is a commercial contract under which a licensed payment institution agrees to process transactions on behalf of a merchant or platform – but the document's real legal weight lies in the unilateral termination, rolling-reserve, and chargeback-liability provisions that typically favour the provider. For a crypto business, these provisions interact with a regulatory overlay that most standard agreement templates do not contemplate. The acquiring bank or PSP is itself regulated – under the Payment Services Directive framework in the EU, under the FCA in the United Kingdom, or under equivalent national regimes – and its compliance obligations flow directly into the contractual relationship with the merchant.
Disputes arise when the provider invokes a compliance or risk clause to freeze settlement, withhold reserves, or terminate the agreement entirely. Crypto businesses face this disproportionately because the provider's internal risk policy – which is not the same as law – often treats digital-asset activity as elevated risk regardless of the platform's own regulatory status. The result is a structural mismatch: the crypto operator may hold a valid VASP (virtual asset service provider) authorisation or even a full CASP (crypto-asset service provider) licence under MiCA, yet still face account termination on the basis of a risk-category decision the provider is not required to explain.
In our cross-border practice, we regularly advise businesses at the point of contract signature and at the point of crisis. The disputes we see most often are not primarily about fraud or customer harm. They are about ambiguous contract language applied to a sector the drafter did not anticipate.
Contact OBOLUS before signing or before the clock runs on a termination notice. The process above describes the standard path. Your facts – the entity, the user base, the banking – change the analysis entirely. Map your options.
What Are the Core Legal Dispute Vectors in PSP and Acquiring Relationships?
The five most active dispute vectors in PSP and acquiring relationships for digital-asset businesses are: unilateral termination, rolling-reserve disputes, chargeback liability, transaction monitoring holds, and misrepresentation at onboarding. Each involves a different mix of contract law and regulatory context, and each requires a different response strategy.
Unilateral termination is the most common. Most standard acquiring agreements reserve a right to terminate immediately for breach of an acceptable-use policy, for a change in the merchant's business, or on notice periods ranging from zero to thirty days. The trigger is almost always a compliance finding by the provider's own risk team. For a crypto business, that trigger may be as simple as a new product line, a change of beneficial ownership, or the provider updating its internal risk appetite. The contract may not require reasons to be given. Whether reasons are required – and whether those reasons are challengeable – depends on the governing law of the agreement and the regulatory regime applicable to the provider.
Rolling reserves – funds withheld by the provider to cover potential chargebacks – become a dispute when the provider holds the reserve beyond the contractual release period, or expands the reserve unilaterally following a risk review. We have seen reserves that were contractually capped turn into indefinite holds when the provider issued a notice of termination at the same time. The legal question is whether the termination triggers a different reserve regime or whether the original cap survives.
Chargeback liability is a third vector. Card-scheme rules flow through the acquiring agreement, and a crypto platform processing fiat payments for digital-asset purchases carries a chargeback exposure that many operators underestimate at the point of onboarding. High chargeback ratios – measured against card-scheme thresholds, which vary – can trigger fee penalties, scheme monitoring programmes, and ultimately termination. The scheme rules themselves, incorporated by reference, are rarely read alongside the acquiring agreement at the time of signature.
Transaction monitoring holds – where the provider pauses settlement pending a compliance review – occupy a legally ambiguous space. The provider will characterise the hold as a legitimate risk-management measure. The merchant will characterise it as breach of the settlement obligation. Resolution depends on whether the agreement contains an express right to hold and on whether the hold period is proportionate. Courts applying English law, which governs a significant proportion of PSP agreements, have generally required a contractual basis for settlement withholding, not merely a compliance justification.
Misrepresentation at onboarding is an underappreciated vector. A business that described its activity at a higher level of abstraction during the application – for instance, characterising itself as a "payments technology company" rather than a crypto exchange – faces rescission risk if the provider later discovers the full picture. The risk is real in both directions: the provider may rescind; and the operator may have grounds to challenge a termination that was itself based on facts the provider had access to but chose not to review at onboarding.
How Does the Cross-Border Structure of a Crypto Business Complicate the Dispute?
Cross-border structure is the single greatest amplifier of PSP and acquiring disputes for digital-asset businesses, because the governing-law and jurisdiction clauses in the agreement rarely match the operational reality of the platform. A crypto exchange incorporated in a third-country jurisdiction, licensed in another, processing transactions through a PSP governed by EU law, and banking through a third entity creates at least three parallel legal questions the moment a dispute begins.
First, which law governs the agreement? Most PSP and acquiring agreements for EU-licensed operators choose the law of the provider's home member state. A business that signed an agreement governed by Lithuanian law but is now disputing a termination needs to understand Lithuanian contract law, not English law – even if its own lawyers are in London. This is not an academic distinction. The implied duty of good faith in civil-law systems operates differently from its common-law equivalent, and the remedies available for arbitrary termination differ accordingly.
Second, which forum has jurisdiction? An exclusive jurisdiction clause in favour of the provider's local court is standard. Challenging that clause requires an argument about mandatory rules, consumer protection (not available to a business claimant) or public policy – arguments that are rarely successful and costly to run. The practical implication is that the business must be prepared to litigate in the provider's jurisdiction, often against a well-resourced counterpart with home-court advantage.
Third, does the regulatory regime of the operator's own licence affect the dispute? A CASP authorised under MiCA and passported across the EU/EEA has a regulatory status that a provider cannot simply ignore in a termination decision. Regulatory status does not immunise the operator from contractual termination, but it may be relevant to a regulatory complaint – filed with the relevant national competent authority under the MiCA regime – alleging that the PSP is acting in a manner inconsistent with the operator's legitimate licensed activity. Whether such a complaint has practical effect varies considerably by member state.
We regularly advise on structures where the fiat-processing entity and the licensed crypto entity sit in different jurisdictions. The banking and EMI onboarding layer requires the same structural analysis as the licence stack itself. A business that optimises its crypto licence without mapping its fiat rails to the same regulatory layer is building on an incomplete foundation.
What Is the Regulatory Dimension of a PSP Dispute – and Does the Regulator Care?
The regulatory dimension of a PSP dispute turns on whether the provider's conduct can be characterised as a breach of its own regulatory obligations, not just its contractual ones – and the answer, in most jurisdictions, is that a regulatory complaint is available but rarely determinative on its own. Regulators oversee payment institutions for systemic and consumer-protection purposes. A commercial dispute between a PSP and a business client is generally outside the regulator's enforcement priority, unless the conduct involves a systemic failure or a discriminatory pattern.
That said, the regulatory complaint has tactical value. Under the UK's FCA regime, a payment institution is subject to conduct standards that require fair and transparent communication with business customers. The FCA's approach to algorithmic de-risking – where an institution uses automated risk scoring to terminate accounts without case-by-case review – has been the subject of supervisory guidance, and a complaint that documents a termination made without individual assessment may attract supervisory attention even if it does not produce a direct remedy. Similar considerations apply under the Bank of Lithuania's supervisory oversight of EMI and payment institution licences granted under the Lithuanian framework, which historically served as an EU entry point for many crypto businesses.
In the EU context, MiCA introduces a regulatory expectation that banks and payment institutions serving CASPs do so in a manner consistent with the broader goal of an integrated crypto-asset market. Whether this translates into an enforceable right for the CASP to maintain banking access is a developing question. ESMA and the European Banking Authority have both noted the access-to-payment-services issue in their published work, though the regime does not yet contain a bright-line obligation on payment institutions to serve licensed CASPs.
The practical message: a regulatory complaint is one tool, not the whole strategy. It runs in parallel with contractual claims, not in substitution for them. Building the regulatory record – a documented letter to the provider requesting reasons, a formal complaint lodged with the relevant authority, evidence of the operator's licensed status – strengthens the overall position even when the regulator does not intervene directly.
If a termination notice has arrived or settlement has been paused, the window to preserve your position is short. If a prior application stalled or an account was closed, a second read can surface the structural reason and the route back. Map your options.
What Remedies Are Available When a PSP Terminates or Withholds Settlement?
The available remedies when a PSP terminates or withholds settlement fall into three categories – contractual, regulatory, and structural – and the most effective response combines elements of all three, sequenced by the urgency of the business need. Contractual remedies are typically the fastest route to recovering held funds; structural remedies are the most durable solution for preventing recurrence.
On the contractual side, the first question is whether the termination or hold was contractually valid. A termination that did not follow the notice procedure, that invoked a clause incorrectly characterised as applicable, or that breached an implied duty of good faith (in a civil-law-governed agreement) may be wrongful. Wrongful termination gives rise to a damages claim for lost profits during the notice period and potentially beyond. Withheld reserves held beyond the contractual release date give rise to a debt claim, which in most jurisdictions can be pursued with relative speed in the commercial courts. The governing-law clause determines the forum and the limitation period.
Interim injunctive relief – requiring the provider to release held funds or to continue processing pending determination of the dispute – is available in principle but difficult to obtain in practice. English courts and courts in most EU jurisdictions require a serious question to be tried, a balance of convenience favouring the claimant, and a cross-undertaking in damages. For a crypto business, demonstrating that damages are an inadequate remedy – a precondition for injunctive relief – is complicated by the fact that withheld funds, unlike reputational harm, are quantifiable.
Regulatory remedies, as discussed, have tactical rather than primary value. They are most effective when used to create a documented record and to signal that the operator is regulated and is not going away. In some jurisdictions, a formal complaint to the payment-institution supervisor also triggers an obligation on the provider to respond to the regulator, which can itself generate information useful to the contractual claim.
Structural remedies – onboarding an alternative PSP or EMI, restructuring the fiat-processing entity, or migrating to a different acquiring arrangement – are the long-run solution. In our practice, we advise businesses to maintain at least one backup fiat-processing relationship at all times. The regulatory and onboarding lead time for a new PSP or EMI relationship means that a business that begins that process only after termination is already operating without a safety net for the window it takes to close a new arrangement.
Which Response Strategy Fits Which Operator Profile?
The right response to a PSP dispute depends heavily on the operator's profile, the stage of the relationship, and the amount in dispute relative to the cost of litigation. No single strategy works for every business. The following analysis maps four common profiles to the appropriate response path.
A licensed CASP or VASP with a MiCA authorisation, disputing a termination by an EU-regulated PSP, holds the strongest regulatory position of any profile. The operator's licensed status is a material fact for any regulatory complaint, and the MiCA passporting framework creates a legal expectation of market access that is directly undermined by a PSP refusal. The recommended sequence for this profile is: send a formal written request for reasons (to build the record), file a supervisory complaint in the PSP's home member state, and pursue the contractual claim for wrongful termination or reserve-retention in parallel. Timeline to resolution is typically several months for the contractual track; the regulatory track may produce supervisory dialogue more quickly.
A crypto business operating under an offshore registration – BVI FSC, CIMA, or a similar framework – and banking through a European EMI faces a different position. The regulatory complaint route is less available because the operator's own regulatory status is outside the EU regime. The contractual track is the primary avenue. The key risk is that the EMI agreement may contain an acceptable-use clause that explicitly excludes or limits digital-asset businesses, which would make the termination contractually valid even if commercially harsh. The strategic focus for this profile is on the reserve-release claim (which is independent of the termination's validity) and on accelerating a parallel onboarding process with an alternative provider. The VASP Act frameworks in BVI and Cayman are registered with the BVI FSC and CIMA respectively, but those regulatory credentials carry less weight in a European PSP's risk assessment than an EU-equivalent licence.
A startup or early-stage operator with no prior banking relationship and no regulatory authorisation is in the weakest position. Its agreement, if it managed to sign one at all, is likely to contain the widest termination rights and the highest reserve percentages. Dispute resolution for this profile is more likely to focus on preventing the termination in the first place – by engaging the provider's risk team before a decision crystallises, by presenting regulatory progress (a pending application, a letter of intent from a regulator) as a mitigating factor, and by avoiding the triggers – high chargeback ratios, unusual transaction patterns, undisclosed product changes – that most commonly prompt termination decisions for newer operators.
A multi-jurisdictional exchange with operations across several regulatory zones and multiple PSP relationships in parallel is in the most defensible operational position. For this profile, a single PSP termination is a business disruption rather than an existential event, provided the onboarding work was done correctly at the outset. The dispute strategy is typically to pursue the contractual claim for wrongful termination and withheld reserves as a matter of principle and commercial discipline, while migrating volume to the surviving processing relationships. The cross-border complication for this profile is that disputes across multiple jurisdictions may need to be managed simultaneously, with different governing laws, different forums, and different regulatory authorities involved.
A Practical Illustration: Termination and Reserve Withheld
In a recent matter, a regulated digital-asset exchange operating under a licence in a leading EU jurisdiction had its PSP relationship terminated by its primary acquiring bank without prior notice, on the stated basis of a revised internal risk policy. Approximately three months of rolling reserves remained withheld at the point of termination. The platform's licence was current and its transaction records clean. We were instructed within days of the termination notice arriving.
Our initial review identified three issues: the termination notice was issued under an incorrect clause of the agreement; the reserve-retention provision was time-limited and had already expired as to the oldest tranche; and the acquiring bank had not followed its own internal escalation procedure before issuing the notice. We sent a formal written reservation of rights letter, filed a supervisory complaint with the relevant national competent authority, and initiated pre-action correspondence on the reserve-release claim. Within several weeks, the provider released the time-expired portion of the reserve without admission of liability. The balance of the dispute – the wrongful-termination claim and the remaining reserve – progressed to formal dispute resolution. The platform had an alternative PSP relationship operational before the quarter ended.
The outcome depended on speed, documentary preparation, and the operator's ability to demonstrate its licensed status clearly and early. Businesses that arrive at a PSP dispute without the regulatory record – the licence documents, the onboarding correspondence, the transaction data – are operating at a disadvantage from the first letter.
English Law vs. EU Civil Law: Contrasting Positions on PSP Termination
The governing-law clause in a PSP or acquiring agreement is not a formality – it is a material determinant of the remedies available in a termination dispute, and the difference between English law and continental EU civil law is significant enough to affect strategy from the outset. The contrast is sharpest on two points: the basis for challenging a termination, and the role of good faith.
Under English law, a PSP agreement is treated as an ordinary commercial contract. The court will give effect to the express termination clause as written. English courts do not impose a freestanding duty of good faith in commercial contracts, although a duty not to exercise a contractual discretion capriciously or irrationally has been recognised in recent case law. The result is that challenging a termination under English law requires identifying a specific breach: a defect in the notice procedure, a mischaracterisation of the triggering event, or an exercise of discretion so arbitrary as to be outside the contractual power. This is a harder task than it sounds, and the quantum of a successful claim is typically limited to loss during the notice period.
Under civil-law systems – French, German, Belgian, and most other EU member-state frameworks – the position is different. A general obligation of good faith in contract performance operates as a substantive constraint on both parties. A termination that is technically within the contract's terms may still be challengeable if it was exercised without reasonable cause, without adequate notice, or in a manner that frustrated the other party's legitimate expectations. For a crypto business that invested significantly in compliance infrastructure specifically to meet the PSP's requirements, this doctrine may support a damages claim that goes beyond the notice period.
Lithuanian law – relevant because the Bank of Lithuania has historically licensed a significant proportion of EU-oriented EMI and payment institutions – is a civil-law system with a codified obligation of good faith. A termination of an EMI relationship governed by Lithuanian law, made without any stated reason, carries more legal risk for the terminating party than the same termination under English law. This is one reason that mapping the governing-law clause at onboarding – not after the crisis – is part of the structural analysis we bring to every PSP and EMI arrangement.
A Common Assumption: One Licence Covers Everything
A common assumption among digital-asset operators entering new markets is that a single offshore licence – issued by a respected registry such as the BVI FSC or CIMA – is sufficient to maintain banking and payment relationships globally. The assumption is understandable but consistently incorrect, and the point at which it fails is often a PSP or acquiring dispute.
PSPs and acquiring banks apply their own risk classifications, which track regulatory regimes but are not identical to them. A BVI-registered VASP is a recognised regulatory category, but it does not carry the same weight in a European provider's risk model as a MiCA-authorised CASP or a payment licence issued by a home-jurisdiction EU regulator. The practical consequence is that an operator relying on a single offshore registration to maintain its full range of fiat-processing relationships is exposed to termination risk whenever the provider updates its risk appetite – and providers update their policies frequently.
The more durable structure is a layered one: the crypto licence in the primary operating jurisdiction, a separate EMI or payment institution licence (or access through an EMI partner) for the fiat layer, and a subsidiary or branch structure in each material market that generates compliance risk. This structure requires more work at the outset. It also makes PSP and banking relationships materially more stable, because each entity in the structure presents a clean regulatory profile to the providers it works with, rather than relying on a single entity to carry the entire risk profile of a multi-activity digital-asset group.
We map the licence, banking, and tax stack across operating, custody, and payment layers before the business commits to a structure. The objective is to identify the termination and dispute risks before they materialise, not to manage them after the accounts are closed.
Related at OBOLUS
- Banking, Payments and EMI Onboarding for Digital-Asset Businesses – how we structure fiat-rail access and manage provider onboarding across jurisdictions
- Fiat On/Off-Ramp Banking in Lithuania – the Bank of Lithuania regime and its role in EU crypto banking access
- VASP Licensing in Switzerland – FINMA's token taxonomy and the licence routes available to digital-asset businesses
FAQ
Why do banks close crypto company accounts?
Banks close crypto company accounts primarily because of internal risk-classification policies that treat digital-asset activity as elevated risk, irrespective of the operator's regulatory status. The decision is typically commercial, not regulatory. Contributing factors include high chargeback ratios, undisclosed changes in business activity, the operator's use of a high-risk jurisdiction for incorporation, or the bank's own exposure to card-scheme monitoring programmes. A licensed CASP or VASP may still face closure if the bank's internal policy has not been updated to reflect the operator's licensed status. Documenting that status early and clearly is the most effective preventive measure.
How can a VASP onboard with an EMI?
A VASP can onboard with an EMI (electronic money institution) by meeting the EMI's own know-your-business and AML requirements, presenting its regulatory authorisation and compliance documentation, and matching its business description at onboarding precisely to its actual activity. Many EMIs have developed specific onboarding tracks for licensed VASPs. The key risk at onboarding is understatement – describing the business at a level of abstraction that does not reflect the full activity. If the EMI later discovers the gap, the account is vulnerable to immediate termination. Engaging counsel to prepare the onboarding pack significantly reduces this risk.
What does client-money safeguarding require?
Client-money safeguarding requires a payment institution or EMI to hold funds belonging to users in segregated accounts, separated from the institution's own funds, so that user balances are protected in an insolvency. The specific rules vary by jurisdiction: the EU Payment Services Directive framework and the UK's FCA regime both impose safeguarding obligations on licensed payment institutions, but the mechanics – which accounts, which banks, what documentation – differ in detail. For a crypto business that relies on an EMI to hold customer fiat, the EMI's safeguarding compliance is a direct counterparty risk. Operators we advise routinely review EMI safeguarding arrangements as part of their onboarding due diligence.
OBOLUS is an independent digital-asset law boutique acting only for businesses. We advise exchanges, custodians, token issuers and funds on licensing across 70+ jurisdictions, on disputes and on-chain asset recovery across 25+ forums, and on the tax, banking and compliance that sit around them. Digital assets are the entirety of our practice, and we act only for businesses – not retail investors. We map the licence stack across operating, custody and payment layers before you commit, and we advise on disputes when the relationship breaks down. To discuss your situation, contact info@oboluslaw.com.
By Glen Sorensen, Disputes & Recovery Analyst – specialising in PSP and acquiring disputes, on-chain asset recovery, and cross-border enforcement for digital-asset businesses.
This publication is general information about the law and does not constitute legal advice. It is not a substitute for advice tailored to your circumstances. OBOLUS accepts no liability for action taken or not taken on the basis of this material. For advice on your situation, contact info@oboluslaw.com.