An Exchange Has Two Banking Problems, Not One
Every crypto exchange needs two distinct things from the banking system, and they are placed separately at different institutions under different rules. Confusing them is the most common structural mistake in exchange launches.
MiCA Article 70 requires a crypto-asset service provider holding client funds to place them with a central bank or a credit institution by the end of the business day following receipt, held in a way that identifies them separately from the firm’s own assets.[1] The practical effect is that an exchange cannot satisfy the requirement with an EMI relationship alone, however good that relationship is, because an EMI safeguards rather than takes deposits.
This produces the circularity operators run into: the regulator will not authorise without a credible safeguarding arrangement, and many credit institutions will not open the account without the authorisation. The resolution is a conditional or parallel process, where the institution issues an in-principle confirmation and the account activates on authorisation. That is a routine arrangement for institutions that serve the sector and an impossible request for those that do not, which is why the institution list matters more than the application quality.
The Working Stack Is Four to Six Relationships, Not One Bank
That is not redundancy for its own sake; each layer carries a flow the others cannot, and each is opened at a different institution.
| Layer | Institution type | What it carries | Placement difficulty |
|---|---|---|---|
| Client-fiat safeguarding | Credit institution (MiCA Art 70) | User balances, segregated, and identified | Hardest; gates the licence |
| Corporate operating | Bank or EMI | Payroll, suppliers, fees, treasury | Routine once licensed |
| SEPA and SEPA Instant | EU EMI or bank | User deposits and withdrawals in EUR | Moderate; volume-sensitive |
| Correspondent USD | Correspondent bank | USD clearing for non-EU flows | Scarce; the real bottleneck at scale |
| Card acquiring | Acquirer under MCC 6051 | Card-funded purchases (quasi-cash) | Narrow panel, high reserves |
| Stablecoin settlement | Authorised EMT issuer or PI | Institutional and B2B settlement | Depends on issuer authorisation status |
Correspondent USD access is the constraint that binds at scale and the one most often discovered late. Active correspondent banking relationships declined by roughly 30% globally between 2011 and 2022, with USD correspondent relationships falling faster than the all-currency average in most regions.[2] An exchange whose growth plan assumes USD pairs should confirm the clearing route before the trading engine, not after.
The card layer is a narrower constraint of the same kind. Card-funded crypto purchases code to MCC 6051 under the card schemes’ merchant data standards, which treat them as quasi-cash rather than ordinary e-commerce.[5] That coding, not the exchange’s own risk profile, is what narrows the acquiring panel and sets the reserve terms in the cost table below.
Analytics, Travel Rule, and Wallet Architecture Decide the File
Exchange onboarding is the most documentation-heavy placement in this sector, because the institution is underwriting a business whose counterparties it cannot see. Three areas carry disproportionate weight.
On-chain analytics. A contract with an institutional-grade blockchain analytics provider, configured, and live, is effectively a precondition. Stated intent does not satisfy it. The New York Department of Financial Services set out supervisory expectations for blockchain analytics use in September 2025, and European institutions apply comparable expectations through the EBA money-laundering risk-factor guidelines as amended for crypto-asset service providers.[3]
Travel Rule implementation. The EU applies a zero de minimis threshold for transfers between crypto-asset service providers, so every transfer carries originator and beneficiary information regardless of value.[4] Institutions ask which protocol the exchange uses, how it handles counterparties that do not support it, and what happens to transfers involving self-hosted wallets.
Wallet architecture. Segmentation across hot, warm, and cold storage, multi-signature arrangements, and documented key management. This reads to a bank as operational risk rather than compliance: the question behind it is whether a single compromise can drain user balances the bank is safeguarding.
Beyond those, the file carries the standard licensing pack plus proof-of-reserves methodology where the exchange publishes one, market-surveillance arrangements, and a listing policy that shows how assets are screened before they are traded.
Jurisdiction Is a Banking Decision Too
Where an exchange incorporates and where it licenses are decided for regulatory reasons. Where it banks is a different question, and it should be answered on its own terms rather than assumed to follow the licence. A Lithuanian or Estonian operating EMI paired with a credit-institution safeguarding account in another member state and a correspondent relationship elsewhere is a normal architecture, not a workaround.
Within the EU the binding variable is which credit institutions in the licensing jurisdiction will take safeguarding business at all. Markets with a deep EMI layer are not automatically markets with willing safeguarding banks, and the two are frequently confused because both are described as “good for fintech”. Jurisdiction-level banking detail sits on the banking overview, and licensing pathways on the crypto licensing pages.
Outside the EU the pattern differs: Switzerland has dedicated digital-asset banks, the UAE has banks running digital-asset units under Central Bank of the UAE approvals, alongside the VARA and ADGM licensing frameworks for the operators themselves, and Singapore has banks serving licensed digital payment token holders. Each of those is a smaller set of institutions than it appears, and each applies its own minimum relationship size.
Costs and Timelines Are Set by the Two Slowest Items
| Component | Typical range | Timeline |
|---|---|---|
| Client-fiat safeguarding account | Relationship minimums from €25,000 to €500,000+ | 8–16 weeks, longer with conditional authorisation |
| Corporate operating account | €100–€500 monthly | 2–6 weeks (EMI) |
| SEPA and SEPA Instant rails | Per-item, low | 2–6 weeks |
| Correspondent USD | Negotiated; volume-gated | 3–9 months |
| Card acquiring (MCC 6051) | 3.5–8% charged to the exchange, reserve 5–10% for 180 days | 4–12 weeks |
Ranges are indicative across the partner network as of . The two slowest items, safeguarding and correspondent USD, are also the two that cannot be started late, so both should run in parallel with the licence application rather than after it.
Through the placement model the pricing the exchange sees is the institutional rate. Jagelski & Partners is paid by the institution, not by the client, and does not mark up banking pricing.
How Jagelski & Partners Helps
Exchange placement is sequenced around the safeguarding account, because it gates the licence and takes the longest. The assessment establishes which credit institutions will engage on a conditional basis in the target jurisdiction, then builds the operating, rail, correspondent, and acquiring layers around that anchor so the slow items are already running when the regulator asks about them.
It also covers the parts of the file institutions actually weigh: analytics provider and configuration, Travel Rule implementation including the self-hosted-wallet case, wallet architecture and key management, listing and surveillance policy, and the merchant category code position if card funding is planned.
What we do not do. We do not place unlicensed exchange operations in jurisdictions where authorisation is required. That is screened at discovery, before the placement process begins.
Frequently Asked Questions
Because client money and company money are different in law. The corporate account holds the exchange’s own funds for payroll, suppliers and treasury. The client-fiat safeguarding account holds user balances, and MiCA Article 70 requires those to sit with a central bank or credit institution by the end of the business day following receipt, identified separately from the firm’s own assets.
The safeguarding account is the harder placement and the one that gates the licence, so it should be started first rather than last.
Generally no. An EMI safeguards funds rather than taking deposits, and MiCA Article 70 requires client funds at a central bank or credit institution. However good an EMI relationship is, it does not satisfy the safeguarding requirement on its own.
EMIs remain the right answer for operating accounts, SEPA rails and multi-currency treasury, which is why most exchanges run both rather than choosing between them.
With a conditional or parallel process. The credit institution issues an in-principle confirmation of the safeguarding arrangement, the regulator accepts that as evidence, and the account activates on authorisation.
That is routine for institutions that already serve the sector and an impossible request for those that do not, which is why the institution list matters more than how well the application is written. Applying cold to banks that have never done it produces a decline rather than a negotiation.
Correspondent USD clearing. Active correspondent banking relationships fell roughly 30% globally between 2011 and 2022, with USD corridors declining faster than the all-currency average in most regions, so the route is scarce and volume-gated.
An exchange whose growth plan assumes USD pairs should confirm the clearing route before building the trading engine. Onboarding runs three to nine months, which is longer than most launch plans allow for.
Beyond the standard licensing pack, three areas carry disproportionate weight: a live, configured contract with an institutional-grade blockchain analytics provider; documented Travel Rule implementation, including how the exchange handles counterparties that do not support the protocol and transfers involving self-hosted wallets; and wallet architecture covering hot, warm and cold segmentation with multi-signature and key management.
Stated intent does not satisfy the analytics requirement. Institutions ask for the contract and the configuration.
No. The EU applies a zero de minimis threshold for transfers between crypto-asset service providers, so every transfer carries originator and beneficiary information regardless of value. Transfers involving self-hosted wallets are treated separately and attract their own verification obligations.
Institutions test this specifically, because a gap in it is a gap in their own supervisory position rather than only the exchange’s.
Not necessarily, and frequently not. Licensing and banking jurisdiction are separate decisions. A common architecture pairs an operating EMI in one member state with a credit-institution safeguarding account in another and a correspondent relationship elsewhere.
The variable that matters is which credit institutions in the licensing jurisdiction will take safeguarding business at all. A deep EMI market is not the same thing as a willing safeguarding market, and the two are often confused because both get described as good for fintech.
Card-funded crypto purchases code to MCC 6051, quasi-cash, which carries a narrow acquiring panel. Rates charged to the exchange run 3.5–8% with rolling reserves of 5–10% held 180 days, and issuer authorisation rates are lower than for standard e-commerce because many issuers restrict quasi-cash. An exchange routing card funding through an at-scale on-ramp provider instead pays that provider’s pricing, which is where the lower published end-customer rates come from.
Ranges are indicative across the partner network as of June 2026 and move with processing history and market mix.
Plan on the two slowest items rather than the average. Safeguarding runs 8 to 16 weeks and longer under conditional authorisation; correspondent USD runs three to nine months. Operating accounts and SEPA rails are 2 to 6 weeks, and card acquiring 4 to 12 weeks.
Both slow items should run in parallel with the licence application, not after it, which is the single biggest scheduling decision in an exchange launch.
No. Jagelski & Partners is paid by the institution that takes the business, through a referral or revenue-share arrangement, not by a fee billed to the client. The pricing the exchange sees is the institutional rate, with no markup and no onboarding fee.
Ready to Place Safeguarding Before It Blocks the Licence?
Book an assessment. We establish which credit institutions will engage on a conditional basis in the target jurisdiction, then place the operating, SEPA, correspondent, and acquiring layers around that anchor so the slow items are already running when the regulator asks. No markup on institutional pricing. No onboarding fee.
References
Show all references
- European Union, Regulation (EU) 2023/1114 on Markets in Crypto-Assets (MiCA), Article 70 (safeguarding of clients’ funds and crypto-assets: deposit with a central bank or credit institution by the end of the following business day, held separately identifiable); Title V applicable from , eur-lex.europa.eu, accessed .
- Bank for International Settlements, CPMI quantitative review of correspondent banking data (end-2022); approximately 30% global decline in active correspondent banking relationships 2011–2022, with USD-denominated corridors declining faster than the all-currency average in most regions, bis.org, accessed .
- New York State Department of Financial Services, Industry Letter: Notice on Use of Blockchain Analytics by NY Banking Organisations (); European Banking Authority, Guidelines EBA/GL/2024/01 amending EBA/GL/2021/02 on customer due diligence and ML/TF risk factors, including for crypto-asset service providers (applicable from ), eba.europa.eu, accessed .
- European Union, Regulation (EU) 2023/1113 on information accompanying transfers of funds and certain crypto-assets (the Transfer of Funds Regulation), applying a zero de minimis threshold to transfers between crypto-asset service providers, eur-lex.europa.eu, accessed .
- Visa Inc., Visa Merchant Data Standards Manual (integrity-risk MCC provisions) (April 2026 edition), MCC 6051 quasi-cash treatment and registration requirements, corporate.visa.com, accessed .