A crypto exchange signs what looks like a straightforward acquiring agreement with a payment service provider. Six weeks later, the PSP suspends processing with no warning. Settlement funds are withheld. The business cannot pay its users. The question is not whether this happens – in our cross-border practice, we see it regularly – but what the agreement actually said, and where the liability sits when the rails go silent.
The boundary between a PSP agreement (a contract granting access to card and bank-transfer processing infrastructure) and an acquiring agreement (a contract under which an acquirer accepts card transactions on behalf of a merchant and shoulders chargeback exposure) is legally significant and commercially decisive. Both instruments sit within a regulatory regime – typically an EMI (electronic money institution) authorization, a payment institution licence, or a bank licence – and both carry obligations that digital-asset businesses routinely underestimate. With fiat rails tightening across the major hubs and EMI onboarding standards rising in parallel, getting the contractual architecture right before you commit is no longer optional.
This analysis maps the legal lines between PSP and acquiring agreements, traces the cross-border complications that digital-asset businesses face, and identifies where the disputes arise – and how to position the contract before they do.
Two Instruments, One Costly Confusion
A PSP agreement and an acquiring agreement are not interchangeable, and treating them as such is the most common structural error we see in digital-asset payment stacks. A PSP agreement is a service contract: the PSP routes payment instructions, aggregates settlement, and typically holds a payment institution or EMI licence that covers the technical infrastructure. An acquiring agreement is a risk-transfer instrument: the acquirer accepts card transactions directly, becomes the counterparty to the card scheme, and absorbs the chargeback liability unless it has contractually shifted that exposure back to the merchant.
In practice, many crypto businesses sign a combined instrument – a PSP that also acquires – without recognising that the two legal relationships carry distinct obligations. The acquiring relationship is governed by card-scheme rules (Visa, Mastercard) that sit above the bilateral contract, meaning scheme rules override contradictory contractual terms. The PSP relationship is governed primarily by the bilateral agreement and by the payment institution or EMI regulatory regime in the PSP's home jurisdiction. Those two governance layers interact, and the interaction is where disputes live.
Operators we advise regularly discover after termination that the PSP's right to withhold settlement funds derives not from bad faith but from a rolling reserve clause buried in schedule three of the agreement – a clause that, under the applicable payment regulation, the PSP was entitled to invoke without notice if the merchant's chargeback ratio crossed a defined threshold. The threshold was not in the agreement. It was in the card-scheme rules the agreement incorporated by reference.
The Regulatory Floor: Payment Licence and EMI Requirements
Any PSP or acquirer operating in the European Economic Area must hold either an EMI authorisation or a payment institution licence under the applicable payments directive, and those licences carry conduct-of-business obligations that constrain what the contract can and cannot do. That regulatory floor matters to the merchant, not just the provider, because it defines the rights and protections the merchant can rely on – including safeguarding of client money, transparency of fee structures, and limits on the provider's right to terminate without notice.
In our cross-border practice, we work with clients whose acquiring relationships span multiple regulatory regimes simultaneously. A crypto exchange incorporated in the BVI, licensed as a VASP under the BVI FSC's VASP Act 2022, and onboarding with an EMI authorised by the FCA in the United Kingdom faces three overlapping regimes: the BVI VASP rules governing the exchange's own regulated activity, the FCA's rules governing the EMI's conduct, and, if the exchange serves European users, the shadow of MiCA and ESMA guidance on crypto-asset service providers. Each regime asks different questions about the same transaction.
The practical consequence: a contract term that is permissible under the EMI's home-jurisdiction rules may be unenforceable against the exchange if the exchange's users are in a jurisdiction that treats the relationship differently. Governing-law and jurisdiction clauses do not resolve this cleanly. They determine where disputes are litigated, not which substantive rules apply to the underlying payment obligation.
CTA #1
The regime interaction described above changes materially depending on where your entity sits, where your users are, and which card scheme your acquirer operates under. The process above describes the standard path. Your facts – the entity, the user base, the banking – change the analysis. For a scoped assessment of your PSP or acquiring agreement before you sign, contact OBOLUS at our contact page.
Where Do the Legal Lines Actually Sit?
The legal lines in a PSP or acquiring agreement cluster around four points of friction: termination rights, rolling reserves, chargeback allocation, and data and AML obligations. Each is a site of dispute in crypto-business payment relationships, and each is negotiable – but only before execution.
Termination rights. Payment institution and EMI regimes in the major hubs generally require the provider to give reasonable notice before terminating a payment services agreement. What constitutes reasonable notice is not always defined, and the provider's right to suspend immediately – as distinct from terminate – is typically broader. Crypto businesses are disproportionately affected because PSPs classify them as high-risk merchants, and high-risk rider clauses routinely permit suspension on suspicion of a policy breach without any notice obligation. In our practice, we have seen suspension-and-withhold cycles that ran for months while the underlying compliance question was resolved – a cash-flow event that smaller operators do not survive.
Rolling reserves. A rolling reserve is a percentage of settled funds withheld by the acquirer as a buffer against chargeback liability. The reserve percentage, the release schedule, and the trigger events for increasing the reserve are all negotiable. They are also rarely negotiated by crypto businesses at onboarding, because the onboarding pressure is toward speed, not legal precision. When the reserve is invoked at scale – or when the release schedule is extended unilaterally after a compliance review – the withheld balance can represent a significant portion of the business's liquidity.
Chargeback allocation. An acquirer that processes card transactions for a crypto exchange bears primary liability to the card scheme for chargebacks. The acquirer then seeks indemnification from the exchange under the acquiring agreement. The indemnity clause is typically broad; the dispute is about whether a given chargeback category falls within it. Crypto purchases are fertile ground for friendly fraud: a cardholder buys an asset, the asset depreciates, and the cardholder disputes the transaction. The exchange argues the service was delivered; the cardholder argues misrepresentation. The acquirer is caught between both and will draw on the rolling reserve while the dispute runs.
Data and AML obligations. Under the Travel Rule (the FATF obligation to pass originator and beneficiary data with a virtual-asset transfer) and under applicable AML frameworks, both the VASP and its payment counterparty carry data-collection and screening obligations. Where the VASP has not contracted to provide transaction data to the PSP, and the PSP's own compliance team flags a data gap, the result is often a unilateral compliance hold – suspension without termination, pending a review that has no defined timeline.
How Does Crypto Banking Complicate the Analysis?
Crypto banking – the acquisition and maintenance of bank accounts and payment rails by a digital-asset business – is structurally more fragile than equivalent fiat-business banking, and the PSP or acquiring agreement is the instrument that makes that fragility visible. A crypto business that loses its acquiring relationship loses its fiat on-ramp and off-ramp simultaneously. Unlike a fiat merchant that can switch acquirers in weeks, a crypto exchange faces a market in which acquirers willing to process crypto-related transactions are few, compliance diligence takes time, and the window between losing one relationship and establishing another may be measured in months.
The cross-border dimension intensifies the problem. A crypto business serving users in multiple jurisdictions typically requires multiple PSP relationships: one for card acquiring in the EEA under the MiCA/ESMA regime, one for local payment methods in Asia-Pacific, and, depending on the user base, a separate arrangement for USD transfers through a US correspondent bank. Each relationship carries its own termination exposure. Losing one does not trigger the others in law, but in practice the loss of one relationship signals elevated risk to the others – a contagion dynamic that is not contractual but is commercially real.
In our cross-border practice, we structure payment stacks with redundancy as a design principle, not an afterthought. A business that relies on a single acquiring relationship for its primary revenue currency is one compliance review away from a liquidity event.
The EMI Onboarding Process: What Operators Miss
EMI onboarding for a digital-asset business is a due-diligence process that looks like a compliance audit and functions like a negotiation. The EMI conducts a business review, an AML/KYC assessment, and a regulatory-fit analysis before it agrees to onboard. What operators miss is that the outcome of that process – the tier of service offered, the reserve percentage required, the permitted use cases – is almost always negotiable, and that negotiation is conducted before the agreement is signed, not after.
Operators who arrive at EMI onboarding without a pre-prepared compliance package – a clear AML policy, a defined customer risk profile, a VASP licence from a recognised regulator, and a documented transaction-monitoring framework – receive the standard high-risk terms. Those terms include higher reserve percentages, broader termination rights, and narrower permitted-use definitions. The same operator with the same business profile, presenting a structured compliance package through experienced counsel, routinely receives materially better terms.
The regulatory dimension of the onboarding process matters here. An EMI authorised by the FCA assessing a crypto exchange holding a VARA licence from Dubai's Virtual Assets Regulatory Authority will conduct a different risk assessment than one assessing an exchange with no licence at all. The VARA regime – a comprehensive activity-based licensing framework covering advisory, custody, exchange, lending and transfer services – is increasingly recognised by sophisticated EMIs as a credible regulatory counterpart. A VASP licensed under the BVI FSC's VASP Act 2022 may receive a different assessment again. The hierarchy of regulatory credibility directly affects the commercial terms available.
There is also a Travel Rule dimension. EMIs that are themselves subject to AML supervision increasingly require their crypto-business clients to demonstrate Travel Rule compliance – typically evidenced by integration with a recognised Travel Rule solution and a documented chain-of-custody policy for transaction data. Operators who have not built this infrastructure before approaching an EMI will encounter it as a condition precedent to onboarding or as a post-onboarding condition that, if unfulfilled, triggers a compliance hold.
A Decision Matrix for PSP and Acquiring Structures
Not every digital-asset business needs the same contractual architecture. The right structure depends on the operator's profile, the payment volumes involved, and the regulatory environment in which the business sits. The following matrix maps four operator profiles to the appropriate instrument, the principal legal risk, and the key negotiating point.
Profile A: A licensed crypto exchange with significant card-processing volume and a regulated VASP licence. This operator should negotiate a standalone acquiring agreement with a specialist acquirer, separate from any PSP services agreement, with clearly defined chargeback-indemnity caps, a release schedule for the rolling reserve tied to chargeback performance rather than to the acquirer's discretion, and explicit permitted-use language that covers the exchange's full product range. The principal legal risk is chargeback accumulation from friendly fraud. The key negotiating point is the reserve release schedule.
Profile B: An early-stage exchange or token issuer without a VASP licence seeking initial fiat rails. This operator will likely access a combined PSP-acquiring arrangement through an aggregator. The terms will be standard and unfavorable. The priority is to understand the termination-and-suspend clause precisely and to set an internal threshold for regulatory licence acquisition that removes the business from the high-risk aggregator tier. The principal legal risk is suspension without notice. The key negotiating point is the definition of "policy breach" that triggers suspension.
Profile C: A crypto custodian or OTC desk with large-value low-frequency transactions. This operator may not need card acquiring at all. The appropriate instrument is a payment services agreement with an EMI authorised for large-value business-to-business payments, with SWIFT or local payment network access, governed by a master framework agreement that addresses the Travel Rule and correspondent-bank data requirements explicitly. The principal legal risk is correspondent-bank derisking at the EMI's bank level. The key negotiating point is the EMI's own banking-relationship resilience.
Profile D: A multi-jurisdiction exchange serving users in the EEA, Asia-Pacific and the Middle East. This operator requires a coordinated multi-PSP structure with a primary acquiring relationship for card processing in each major region, a fallback EMI relationship, and a clear internal protocol for managing simultaneous compliance reviews across providers. The principal legal risk is contagion between provider relationships. The key negotiating point is the confidentiality clause that prevents one provider from learning of a compliance review initiated by another.
CTA #2
If a prior application stalled, an account was closed, or a compliance hold has frozen settlement funds, a structured second read of the agreement can surface the contractual basis and the route to resolution. If a recovery clock is running, reach our disputes desk now at our contact page.
Micro-Matter: A Withheld Settlement Balance
In a recent matter, a regulated crypto exchange engaged OBOLUS after its primary acquirer invoked a rolling-reserve escalation clause and withheld a seven-figure settlement balance following a spike in chargeback volumes. The acquirer's position was that the chargeback ratio had crossed the card-scheme threshold and that the escalation clause permitted an immediate increase in the reserve percentage with no prior notice. The exchange's position was that the clause was ambiguous on the notice point and that the escalation had been applied retroactively to a period before the threshold was crossed. We reviewed the agreement, the card-scheme rules incorporated by reference, and the acquirer's transaction-level data. The ambiguity was real. We initiated a formal dispute process under the agreement's dispute-resolution clause, presented a forensic reconciliation of the chargeback data, and negotiated a phased release of the withheld balance conditional on a remediated chargeback-management program. The balance was substantially released within the dispute window, and the acquiring relationship was preserved.
The Objection Handler: Common Assumptions and Where They Fail
A common assumption among digital-asset businesses approaching payment onboarding is that a single offshore licence is sufficient to access PSP and acquiring relationships globally. That assumption is wrong, and it is expensive when it fails.
Card schemes operate on a country-by-country basis. A crypto exchange incorporated in the Cayman Islands under the CIMA VASP framework may hold a valid regulatory registration, but Visa and Mastercard assess the acquiring relationship based on the jurisdiction in which the transactions are processed and the domicile of the cardholders, not the domicile of the exchange. A Cayman-incorporated exchange processing European cardholders' transactions needs an acquirer licensed in the EEA, and that acquirer needs to satisfy itself that the exchange meets the applicable regulatory expectations – which, under the MiCA regime and ESMA guidance, increasingly means holding a CASP authorisation or being in a supervised transition period.
A related assumption is that an EMI relationship covers all payment types. It does not. An EMI that provides SEPA credit-transfer services does not automatically provide card-acquiring services. A crypto business that conflates the two will discover the gap when it attempts to enable card deposits and finds that its EMI agreement covers bank transfers only. The fix is an additional acquiring agreement. The cost of that fix, in time and compliance diligence, is higher than the cost of getting the architecture right at the outset.
A third assumption – one that is particularly common in businesses that have come from a pure-crypto background – is that payment-layer contracts are administrative rather than legal instruments. They are not. They are risk-allocation documents, and the risk they allocate includes the risk of regulatory non-compliance, the risk of fraud, and the risk of dispute with the card schemes. Treating them as administrative creates the conditions for the scenario described in the opening of this analysis: six weeks of smooth processing, then silence.
The Cross-Border Layer: Where Entity, Users and Banking Diverge
The most legally complex PSP and acquiring situations we encounter involve a three-way divergence: the entity is domiciled in one jurisdiction, the users are concentrated in another, and the banking and payment rails sit in a third. Each of those locations carries its own regulatory regime, and the interaction between them is the source of most of the structural problems in cross-border digital-asset payment arrangements.
Consider a crypto exchange incorporated under the AIFC in Kazakhstan, using the AFSA framework, whose primary user base is in the European Union and whose acquiring relationship is with an FCA-authorised EMI in the United Kingdom. Post-Brexit, the FCA regime and the MiCA regime are not equivalent. The EMI's FCA authorisation does not confer EEA passporting rights. The exchange's AFSA licence is not a recognised equivalent under MiCA. The users are in the EEA. The question of which regulatory obligations attach to which actor in this structure – and who bears the liability if a payment fails to meet a local regulatory standard – is not answered by the PSP or acquiring agreement alone. It requires a jurisdictional mapping exercise that considers each regulatory regime independently and identifies the points of friction before they become points of dispute.
In our practice, we conduct that mapping before onboarding, not after. The mapping identifies: which jurisdiction's payment regulation governs the PSP's conduct obligations; which jurisdiction's AML rules govern the exchange's customer-due-diligence obligations; which jurisdiction's consumer-protection regime may apply to the end user's claim if a transaction fails; and which forum has jurisdiction over a dispute between the exchange and the PSP if the agreement's governing-law clause is challenged.
Allied counsel in the relevant jurisdiction are engaged where local-law opinions on specific regulatory positions are required. The analysis does not stop at the bilateral contract; it extends to the regulatory environment in which the contract operates.
What Does Client-Money Safeguarding Require in Practice?
Client-money safeguarding – the obligation imposed on payment institutions and EMIs to hold customer funds in segregated accounts separate from the firm's own funds – is a regulatory requirement that appears in PSP and acquiring agreements as an operational obligation, not always as an explicit contractual term. Understanding what it requires, and where it sits in the payment-services contract, is essential for any digital-asset business that holds customer fiat balances as part of its operating model.
Under the payment institution and EMI regulatory regimes applicable in the major licensing hubs, customer funds must be held in a designated safeguarding account with a credit institution, separate from the payment institution's own funds. The payment institution cannot use those funds for its own operational purposes. In the event of the payment institution's insolvency, the safeguarded funds are ring-fenced from the general creditor pool.
For a crypto exchange that holds customer fiat deposits – whether received as card payments through the acquirer or as bank transfers through the EMI – the question is whether the exchange itself is holding those funds in a regulated capacity or whether the PSP is holding them on the exchange's behalf. That distinction determines who bears the safeguarding obligation and, critically, who is liable if the funds are not safeguarded and are lost.
Where the PSP holds funds on behalf of the exchange before settlement, the safeguarding obligation typically sits with the PSP. Where the exchange holds funds received from the PSP before it has satisfied its obligations to the end user, the question of whether the exchange's own holding constitutes a regulated payment service – and whether the exchange therefore needs its own payment licence – arises. In our cross-border practice, we have seen businesses that unknowingly crossed the regulated-payment-service threshold by holding fiat balances for users pending crypto execution, without a payment licence of their own.
The interaction between a VASP licence and a payment institution licence is a structural question that the PSP or acquiring agreement itself cannot answer. It requires a regulatory analysis of what the exchange is doing with fiat funds at each point in the transaction lifecycle.
Related at OBOLUS
- Banking, Payments and EMI Onboarding – how we structure fiat access for digital-asset businesses across licensing jurisdictions
- PSP and Acquiring in Australia under AUSTRAC – local payment regulation and VASP obligations in the Australian market
- Corporate Tax Residency Planning in Estonia – structuring the EU entity that sits behind the payment licence
FAQ
Why do banks close crypto company accounts?
Banks close crypto company accounts primarily for risk-management reasons: the compliance cost of monitoring crypto-related transactions is high, the regulatory expectations around AML and Travel Rule compliance are demanding, and the reputational risk from association with an unregulated or under-regulated crypto business is asymmetric. A VASP that can demonstrate a recognised regulatory licence, a documented AML framework, and clear transaction-monitoring processes materially reduces the risk profile a bank must assess. Where a bank closes an account without notice, the underlying reason is typically a compliance-team determination that the risk cannot be adequately managed – not always a finding of actual wrongdoing.
How can a VASP onboard with an EMI?
A VASP can onboard with an EMI by presenting a structured compliance package at the outset of the due-diligence process. That package should include the VASP's regulatory licence (or a clear roadmap to licensing), a written AML policy, a customer risk-classification framework, evidence of Travel Rule compliance, and a documented transaction-monitoring program. Operators who arrive at EMI onboarding without this preparation receive standard high-risk terms. Those who arrive with it – ideally through experienced counsel who can position the package in terms the EMI's compliance team recognises – typically receive materially better commercial terms and a shorter onboarding timeline.
What does client-money safeguarding require?
Client-money safeguarding requires a licensed payment institution or EMI to hold customer funds in segregated accounts, separate from its own operational funds, with an authorised credit institution. Those funds must not be used for the firm's own purposes and are ring-fenced in insolvency. For digital-asset businesses, the relevant question is whether the business itself is holding fiat funds in a regulated capacity – which may require a payment licence in addition to a VASP licence – or whether the safeguarding obligation sits with the PSP or EMI in the payment chain. The answer depends on what the business does with fiat balances at each stage of the transaction lifecycle.
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 whole of our practice. We map the licence stack across operating, custody and payment layers before you commit – because the businesses we work with understand that operating without the right licence risks enforcement, frozen rails and lost banking. To discuss your payment structure, contact info@oboluslaw.com.
By Glen Sorensen, Disputes & Recovery Analyst – specialising in payment-layer disputes, cross-border asset recovery and PSP contractual analysis 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.