Your exchange or on-ramp business has a MiCA application in progress, clean AML tooling, and a growing user base, but the merchant-account quote that came back has a reserve nearly triple what a same-size iGaming operator would see, held for six months instead of ninety days. That gap is not a pricing error; it is how acquirers treat MCC 6051 specifically.
A crypto merchant account for genuine exchange or on/off-ramp activity is priced and reserved more conservatively than almost any other high-risk vertical, and it is a fundamentally different risk file from an ordinary retail business that simply also accepts crypto as a payment method, a distinction acquirers draw sharply.
This guide covers which businesses actually fall under the strictest crypto underwriting, why licensing now sits alongside standard documentation as a prerequisite, what reserves and holds genuinely look like, and how the MiCA authorization deadline that effectively concluded around July 1, 2026 has reshaped which providers EU-facing crypto merchants can even work with.
Direct Answer
A crypto merchant account for genuine exchange or on/off-ramp activity typically falls under MCC 6051 (Digital Currency Services / quasi-cash), the most conservatively reserved high-risk category researched: reserves run 2 to 5 times higher than other high-risk verticals, with holds of 6 to 12 months rather than the standard 90 to 180 days. Licensing (VASP, CASP, or money transmitter) is now a practical prerequisite.
This sits beneath BankMyCapital's crypto banking work; for the fuller picture on structuring accounts, see BankMyCapital's types of crypto banking solutions guide. Here the focus is narrowly the merchant-account and processing side.
Know Whether You Actually Need a Crypto Merchant Account
Acquirers draw a sharp line between two very different businesses that both get loosely called "crypto." A genuine exchange, on-ramp, or off-ramp service, converting fiat to crypto and back, moving between wallets, providing custody-adjacent services, sits under MCC 6051 and faces the strictest underwriting in the high-risk landscape.
An ordinary retail or service business that simply also accepts crypto as a payment method is treated far more leniently by Visa and Mastercard alike, often processed closer to standard retail risk, because the underlying business model carries none of the custody, conversion or AML complexity of an exchange.
What to Consider:
- Classify your business honestly against this distinction before applying, since misclassifying an exchange as a retail crypto-acceptor invites a compliance review that finds the mismatch later, on worse terms.
- Separate entities if you run both models, an exchange arm and a merchant-facing payment product, so one does not inherit the other's reserve treatment.
- Expect the MCC 6051 conversation to start with licensing, not chargeback history, since that is where acquirers begin their review.
Example
A company running both a small exchange product and a merchant-facing crypto-payment plugin applied for a single blended merchant account. The acquirer's underwriting defaulted to the stricter MCC 6051 terms for the entire relationship until the two product lines were legally separated, at which point the merchant-facing side qualified for standard high-risk terms instead.
Final Takeaway: Know which side of the exchange-versus-acceptor line your business actually sits on before you apply, since it determines almost everything downstream.
Get Licensed Before You Apply: VASP, CASP, or Money Transmitter
For genuine exchange and on/off-ramp activity, a money transmitter license, VASP registration, or MiCA CASP authorization (Crypto-Asset Service Provider, under the EU's Markets in Crypto-Assets regulation) now functions alongside your standard high-risk documentation as a practical prerequisite, not an optional strengthening step.
Acquirers active in MCC 6051 increasingly ask for licensing status before reviewing anything else, because an unlicensed exchange-type business represents a category of legal and reputational risk no reserve percentage adequately prices.
What to Consider:
- Identify which license applies in each jurisdiction you serve, since VASP, money-transmitter and CASP regimes are not interchangeable and cover different scopes.
- Apply for licensing in parallel with your merchant-account search, not sequentially, since both processes run on multi-month timelines.
- Keep your licensing status current and visible, since a lapsed or pending-renewal license is treated similarly to no license at all by a cautious acquirer.
Example
An exchange with a pending CASP application, well underway but not yet granted, found most acquirers unwilling to finalize terms until authorization actually came through, despite an otherwise strong compliance file, illustrating how binary the licensing gate has become for MCC 6051 processing.
Final Takeaway: Treat licensing as the first gate for a crypto merchant account, not a parallel nice-to-have alongside standard documentation.
| License Type | Typical Scope | Applies To |
|---|---|---|
| VASP registration | Registration-based, jurisdiction-specific | Exchanges and wallet providers in VASP-recognizing jurisdictions |
| Money transmitter license | State-by-state or country-by-country licensing | On/off-ramp and money-transmission providers |
| MiCA CASP authorization | EU-wide, passportable across member states | Crypto-asset service providers serving the EU |
Price the Real Reserve Structure: 2 to 5x Higher, 6 to 12 Month Holds
MCC 6051 carries the most conservative reserve treatment of any high-risk vertical researched: reserves commonly run 2 to 5 times higher than other high-risk categories, with holds extending to 6 to 12 months, compared with the 90-to-180-day standard elsewhere.
| Vertical Comparison | Typical Reserve Range | Typical Hold Period |
|---|---|---|
| Standard high-risk baseline (iGaming, adult, dating) | 5-15% | 90-180 days |
| Forex | 5-15% | 90-180 days |
| Crypto exchange / on-off-ramp (MCC 6051) | Reported 2-5x the standard-vertical reserve level | 6-12 months |
What to Consider:
- Model liquidity around a 6-to-12-month hold explicitly, since this materially changes working-capital planning compared with the 90-to-180-day norm elsewhere.
- Ask for the reserve calculation basis in writing, since a multiplier-based reserve compounds quickly at volume and needs to be modeled precisely, not estimated.
- Do not assume a strong compliance file shortens the hold period the way it can reduce reserves elsewhere — the hold length in this category tends to be structural, tied to the vertical, more than to individual merchant performance.
Example
An on-ramp business budgeted using a standard high-risk reserve assumption from a prior, unrelated business line, then discovered its actual MCC 6051 terms held nearly a third of monthly volume for close to nine months, a liquidity gap that required a bridge facility to cover operating costs during the transition period.
Final Takeaway: Build your financial model around the 6-to-12-month hold and the higher reserve multiplier from day one, not as a later correction.
Understand the July 2026 MiCA Cliff and Its Effect on Your Acquiring Options
The EU's MiCA transition period for existing crypto-asset service providers effectively concluded around July 1, 2026. Of roughly 1,200 providers that had been operating under national transitional regimes, only around 230 secured full CASP authorization by the deadline.
Providers that did not secure authorization face onboarding restrictions or exit from the EU market. For a merchant-facing crypto business, this has materially reshaped which stablecoins and which providers acquirers and EU-facing merchants will still support, since an acquirer working with an unauthorized provider now carries direct regulatory exposure.
Reality Check
No acquirer or introducer can place you with a crypto provider that lacks genuine authorization and make that arrangement durable. The MiCA deadline was a hard authorization event, not a negotiable compliance target, and a provider relationship built on a provider that did not clear it is a relationship that ends, possibly with your funds caught in the transition.
What to Consider:
- Verify your counterparties' actual CASP authorization status directly, rather than relying on a provider's own marketing claim of compliance.
- Reassess any stablecoin or provider relationship that predates the July 2026 cutoff, since the authorized-provider landscape has narrowed meaningfully.
- Build a contingency plan for a provider transition, since the post-deadline market has fewer authorized counterparties than existed a year earlier.
Example
A merchant relying on a provider that had operated under a national transitional license for over a year lost that provider's services when authorization did not clear by the deadline, forcing an emergency migration to one of the smaller pool of authorized CASPs mid-quarter.
Final Takeaway: Confirm CASP authorization status directly and rebuild any relationship resting on a provider that did not clear it, before it becomes an emergency.
Build Documentation That Satisfies Both Crypto and Standard High-Risk Underwriting
A crypto merchant account application effectively has to satisfy two underwriting layers at once: the standard high-risk documentation set (AML/KYC file, source of funds, beneficial ownership) plus a crypto-specific layer covering licensing status, wallet and custody arrangements, and travel-rule compliance, the cross-institution data-sharing standard for qualifying transfers set out in the FATF recommendations.
What to Consider:
- Prepare both documentation layers before applying, rather than treating the crypto-specific pieces as an add-on request that surfaces mid-review.
- Document your travel-rule compliance process explicitly for any qualifying cross-institution transfers, since this is now a standard underwriting question, not an edge case.
- Keep custody and wallet-security documentation current, since this is one of the fastest-moving areas of underwriter expectation in this vertical.
Example
An exchange's merchant-account application stalled for weeks because its AML file was strong but its travel-rule documentation for cross-border transfers was incomplete. Providing a dedicated travel-rule compliance memo, separate from the general AML policy, resolved the gap within days.
Final Takeaway: Prepare a dedicated crypto-compliance documentation set alongside your standard AML/KYC file, not folded into it.
Structure for Resilience: Don't Rely on One Licensed Provider
Given how few providers cleared MiCA authorization and how concentrated the post-deadline landscape has become, relying on a single licensed processing relationship is a materially riskier structure in crypto than in most other high-risk verticals.
What to Consider:
- Maintain relationships with more than one authorized provider where volume justifies it, rather than consolidating for simplicity.
- Review your provider concentration risk on a quarterly cadence, given how quickly the authorized-provider landscape has shifted around the MiCA deadline.
- Treat provider authorization status as a recurring check, not a one-time verification at onboarding.
Final Takeaway: In a market this concentrated post-MiCA, provider diversification is a resilience measure, not an over-engineering exercise.
Conclusion: The Most Conservative Vertical, for a Reason
A crypto merchant account for genuine exchange or on-ramp activity is priced more conservatively than any other high-risk vertical researched, and for good reason: MCC 6051 sits at the intersection of card-network risk policy and evolving crypto-specific regulation, most visibly the MiCA authorization event that reshaped the EU provider landscape around July 2026.
The businesses managing this well treat licensing as the first gate, model their finances around genuinely long holds rather than the 90-to-180-day norm elsewhere, and never let a single provider relationship be their only path to processing.
None of this is unique to crypto in kind, only in degree: the same discipline of honest classification, current documentation, and structural resilience applies across every high-risk vertical. Crypto simply asks for more of it, and asks sooner.
How BankMyCapital Helps
BankMyCapital is not an exchange, custodian, or CASP, and does not hold client crypto assets or funds. On the merchant-account and banking side, BMC assesses a crypto business's classification, licensing status and documentation readiness, then makes introductions to providers with genuine, verified authorization, rather than routing clients toward relationships that carry post-MiCA exposure. See BankMyCapital's payment processing service for how this connects to the broader banking picture.