Payment Gateways in Morocco: CMI, Stripe, PayPal and Cash on Delivery, Compared Honestly
Want to accept payments on a Moroccan online store? Your real options are CMI, Stripe (with a workaround), PayPal and good old cash on delivery. Fees, requirements, delays and the mix that actually converts — from someone who integrates them.
"How do I accept payments?" is the first question every Moroccan store owner asks me, and it's the topic with the most outdated forum answers. The landscape in 2026 is specific: one local card gateway, two international giants with caveats, and a cash method that refuses to die because customers genuinely prefer it. Since integrating exactly these is core to my e-commerce development service, here's the honest comparison I give clients — including the parts the sales pages skip.
CMI: the local card standard
CMI (Centre Monétique Interbancaire) is Morocco's interbank payment center, and its gateway is what lets your store accept Moroccan bank cards (and international Visa/Mastercard) in dirhams. The practical facts:
Who can get it: a Moroccan business (or auto-entrepreneur/commercial registration) with a Moroccan bank account — you apply through your bank, which provisions the merchant account.
Costs: setup/annual fees through your bank plus a commission per transaction, typically in the ~1–2% range depending on your agreement and volume. Exact terms come from your bank's quote, not a public price page.
Payouts: settlements land in your Moroccan account on the gateway's schedule (days, not weeks).
The catch: the onboarding is paperwork-and-bank-paced, not a 10-minute signup, and the integration (redirect or hosted page, callbacks, verification) needs a developer who has done it before. Budget the lead time into your launch plan — starting the bank process early is the single best scheduling advice I give.
For a store selling in Morocco, CMI is close to non-negotiable: local cards are what local customers hold, and paying in MAD without foreign-card friction lifts conversion visibly.
Stripe: the best developer experience — with a residency catch
Stripe is the gateway developers dream about: beautiful APIs, every feature you can imagine, pricing that's transparent (~2.9% + fixed fee in supported markets). The catch for Morocco: Stripe doesn't onboard Moroccan businesses directly. The workarounds people use are real but structural:
A company formed in a supported country (US LLC, UK Ltd, EU entity) with its bank account and tax obligations — legitimate, but it's company formation and ongoing compliance, not a plugin.
Platforms that resell Stripe-like access take their own cut and add a layer between you and your money.
My honest take: if you're a Moroccan business selling primarily to Morocco, Stripe-via-foreign-entity is a heavy structure for a payments problem CMI already solves. If you sell digital products globally and the foreign entity makes sense anyway, Stripe is superb — I integrate it happily in that context, and its checkout quality is the benchmark my checkout optimization work measures against.
PayPal: the international supplement
PayPal works for Moroccan merchants as a way to receive international payments, and many customers abroad trust it more than typing a card into an unfamiliar store. The downsides are equally familiar: fees stack up (merchant fee + currency conversion), the buyer experience takes people off your site, and withdrawing to a Moroccan bank has historically been the friction point — verify the current withdrawal path for your account type before building your pricing around it. I position PayPal as a supplement for stores with real international demand, not as a primary gateway.
Cash on delivery: the "gateway" that isn't
COD isn't a gateway at all — the customer pays the courier — yet for Moroccan e-commerce it remains the elephant: a large share of customers simply won't prepay an unfamiliar store, and offering COD converts browsers who'd otherwise bounce at the payment step. The real costs are operational, not technical: failed deliveries and returns eat margin (someone pays for the round trip), cash flow arrives later, and fake orders need filtering. The mitigations are process, not hope: order confirmation by phone/WhatsApp before shipping, clear delivery fees, and tracking your delivery success rate by city and courier. Handled well, COD is a competitive advantage; handled casually, it's a slow leak. I wrote more about the surrounding playbook in selling online in Morocco.
The mix I actually recommend
Selling in Morocco (physical goods): CMI + COD, with WhatsApp order confirmations. This is the combination that covers local cards and local habits, and it's what I build most often for Moroccan stores.
Selling internationally (digital or shipped): Stripe if you have (or justify) a supported entity; otherwise PayPal as the receiving supplement, and be deliberate about pricing in the fees.
Both: all of the above, presented simply at checkout — the customer should see their preferred method in one glance, not a settings page.
One last developer-grade warning: whatever the gateway, verify payments on the server side (signed webhooks/callbacks), never trust the "success" redirect alone, and reconcile orders against settlements weekly. Payment bugs don't look like bugs — they look like missing money.
Choosing and wiring the right mix for your market is part of every build in my e-commerce development & payments service. If you're mid-decision and want the recommendation for your exact situation — products, customers, countries — tell me what you're selling and I'll lay out the shortest path to taking your first payment.