Morocco is entering a new phase of payment competition. For years, merchants accepting cards online defaulted to CMI, the domestic interbank processor, for regulatory and practical reasons. That period is ending. Bank Al-Maghrib has opened the door to a broader set of acquirers and gateways, and international PSPs are now credibly in-market. If you are building a payment-accepting business in Morocco in 2026, the PSP question has become strategic. This is how we think about it.
The two options, fairly framed
Option A. CMI
CMI remains the default for local merchants accepting the dominant Moroccan card schemes and domestic cards. Its strengths include regulator familiarity, settlement in MAD without FX complexity, and strong domestic issuer coverage. Its weaknesses, from a modern merchant perspective, include limited orchestration, conservative 3DS handling, experience gaps on mobile flows, and constrained reporting and API surface relative to global gateways.
Option B. International gateways entering Morocco
Checkout.com, Adyen, Stripe and others are now present in the Moroccan market in varying degrees of maturity. Their strengths include modern APIs, mature orchestration, global fraud and 3DS tooling, cross-border by default, and strong developer experience. Their weaknesses today include evolving local acquiring coverage, commercial terms that are not always favorable versus CMI on pure domestic volume, and real regulatory nuance on settlement and FX.
A decision framework, not a recommendation
The right answer depends on four questions.
- How much of your volume is domestic? The more domestic (MAD, Moroccan-issued cards), the more CMI's value compounds.
- How important is cross-border? If you sell to the Moroccan diaspora or to international customers, you need cross-border coverage that CMI alone typically cannot deliver optimally.
- What is your engineering capacity? Modern gateways demand and reward a team that can use them. If resources are constrained, a more turnkey option wins.
- What are your approval and cost targets? Both paths can be optimized. The relevant question is which one better fits your unit economics.
The hybrid pattern we recommend most often
For serious merchants in Morocco, the winning architecture is usually neither pure CMI nor pure international. It is a primary and redundancy model where one provider owns the majority of volume by cost or approval fit, and a second provider handles specific segments: cross-border, failover, or specific payment methods.
A typical pattern:
- Domestic MAD card volume to CMI (primary). Cost-effective, regulator-trusted, strong domestic issuer approvals.
- Cross-border and foreign cards to an international gateway. Better approval rates on non-Moroccan BINs, modern 3DS and FX handling.
- Failover from primary to secondary on hard-down incidents, tuned per error type.
What to watch on the regulatory side
Bank Al-Maghrib has specific expectations around settlement in MAD, FX and data localization. A thoughtful architecture accommodates these without forcing everything through a single provider. On the commercial side, negotiate MDR tiers on volume forecasts with a review clause if your mix shifts by more than 15 percent.
Common mistakes we see
- Picking a PSP purely on API quality, then discovering that acquiring is routed through a partner whose domestic approval rates are 5 points below CMI's.
- Staying on a single provider out of habit and accepting suboptimal cross-border performance as simply the way things are.
- Building custom orchestration in-house when a mature orchestrator would serve you faster and better.
- Not measuring approval rate per BIN country, leaving the right decision invisible.
The Moroccan payment market is entering its most competitive phase in a decade. Merchants who approach the PSP question strategically, with real data, clear criteria and a multi-provider mindset, will be the ones that compound the advantage.
How we help
We advise Moroccan merchants and regional players expanding into Morocco on exactly this decision. A short Diagnose engagement can quantify, in your own data, what each option would mean for your approval rate, cost per transaction and operational complexity before you commit to a multi-year contract.