SaaS Subscription Payments in Morocco: Collecting in Dirhams and Foreign Currencies

Collecting SaaS subscriptions in Morocco is entirely possible, but the path isn't the one described in most English-language guides, which assume a Stripe account opened in three clicks. Between local gateways, international platforms that may or may not accept Moroccan companies, customers who prefer bank transfers and exchange regulations, you have to combine options. This guide presents the concrete choices and how to mix them depending on your customers.

Start with the customer, not the gateway

Before choosing a payment solution, answer three questions: where your customers are (Morocco, Africa, Europe), how they pay today for their other tools (card, transfer, cheque, cash) and how much a subscription represents (a few hundred dirhams a month or several thousand a year). A SaaS sold to Moroccan SMEs isn't billed like a tool sold to European freelancers.

Option 1: a Moroccan payment gateway

To accept Moroccan bank cards in dirhams, your company goes through a gateway connected to the CMI (Centre Monétique Interbancaire), usually offered via your bank or an approved provider. It's the natural solution for a local market: payment in dirhams, funds paid into your Moroccan account, no currency questions.

• Strengths: local cards accepted, settlement in dirhams, a framework your bank and accountant know.
• Points to watch: opening requires paperwork and lead time; automatic recurring payment (charging the card every month without intervention) isn't always offered or depends on your provider's terms; the technical integration is sometimes less documented than international platforms.
• In practice: plan a flow where the customer pays a monthly or annual subscription in one payment, with automatic reminders before the due date, rather than assuming automatic charging.

Option 2: an international platform (merchant of record)

Platforms such as Paddle and other so-called *merchant of record* providers sell your subscription in their name, collect the applicable taxes in each country, handle international cards and pay you the proceeds. For a SaaS targeting Europe or the world, they greatly simplify tax and invoicing. Do check, at the time of your launch, that your country of registration and your bank are accepted: country lists evolve and conditions differ from one platform to another.

• Strengths: recurring subscriptions, trials, invoices and taxes handled; cards from around the world; well-documented integration.
• Points to watch: higher fees; payouts in foreign currency to repatriate; eligibility of Moroccan companies to confirm; often poorly suited to Moroccan customers who want to pay in dirhams.

Option 3: an entity abroad

Some founders set up a company in a country where the major payment platforms (Stripe, for instance) are available, in order to bill their international customers. It's a serious legal and tax decision, with set-up and running costs, to be studied with advisers in Morocco and in the target country. It's justified when most of the revenue is earned abroad, rarely for an MVP.

Option 4: bank transfer and invoice, still useful

For annual subscriptions sold to companies, bank transfer against invoice remains the simplest and most widely accepted payment method in Morocco. Your SaaS must therefore handle this case cleanly: invoice generation, payment tracking, manual or semi-automatic account activation or extension, reminders before the due date. Many Moroccan B2B SaaS companies earn most of their revenue this way.

Currencies, exchange and accounting

Collecting euros or dollars from Morocco is possible, but foreign-currency flows are governed by exchange regulations: repatriation of export earnings, declarations, supporting documents. Likewise, paying your own foreign suppliers (hosting, third-party services) falls within a precise framework. These rules change: have your set-up validated by a chartered accountant before launch, and build invoicing into your SaaS that meets Moroccan requirements (legal mentions, VAT, numbering).

What your SaaS must handle, whichever option you choose

• Plans and limits: features, number of users or records per plan, switching between plans.
• The free trial and its end: reminders, conversion, closure or read-only mode.
• Invoices: generated automatically, compliant, downloadable by the customer.
• Failed payments: automatic reminders, grace period, suspension then reactivation.
• VAT depending on the customer and the country, with the right mentions.
• A back office for your team: see the state of every subscription, grant a discount, extend a trial, activate an account paid by transfer.

Example of a payment journey suited to the Moroccan market

1. Sign-up and trial: the customer creates their workspace and gets fourteen or thirty days of full trial, no card required.
2. Reminders before the trial ends: at D-7 and D-2, an email and, if the customer agreed, a WhatsApp message present the plans.
3. Choice of payment method: card payment through the Moroccan gateway for a monthly or annual subscription, or an invoice request for payment by bank transfer (annual subscription).
4. Activation: immediate after card payment; after confirmation of the transfer from the back office for the invoice.
5. Invoice: generated automatically, compliant, sent by email and available in the customer area.
6. Renewal: reminder thirty days before the annual due date, payment link or new invoice, a grace period of a few days, then read-only mode if nothing is paid.

This journey reflects reality on the ground: customers who happily pay online, others who require an invoice and a transfer, and a team that stays in control from the back office.

Handling unpaid subscriptions without losing the customer

An unrenewed subscription isn't always a lost customer: it's often an expired card, an absent manager or a forgotten invoice. Plan a graduated reminder sequence (reminder, second reminder, suspension warning), a grace period during which the service continues, then a read-only mode that lets the customer view their data without creating new records. Data deletion only comes after a long delay and explicit warnings. This approach recovers a good share of subscriptions that seemed lost and avoids confrontations.

Compliant invoices from day one

Your business customers expect invoices they can book in their accounts. Your SaaS must therefore produce documents with the mentions expected in Morocco: full identification of your company (including the ICE), customer identification, sequential numbering with no gaps, date, description of the service and period covered, amounts excluding tax, VAT and including tax, currency and payment terms. For foreign customers, adapt the currency and VAT treatment. Have the template validated by your chartered accountant before launch: correcting hundreds of invoices afterwards is thankless work.

Monthly or annual, dirhams or euros?

• Monthly lowers the entry barrier and suits small businesses; it multiplies payment operations and opportunities to cancel.
• Annual secures cash flow and simplifies transfer against invoice; offer it with a visible discount.
• Dirhams for Moroccan customers, with no exchange surprises or bank fees.
• Euros or dollars for foreign customers, through a suitable platform, with a separate price list if market price levels differ.

Our recommendation for a launch in Morocco

For most B2B SaaS products starting in Morocco: a local gateway for Moroccan cards, bank transfer against invoice for annual subscriptions, and an international platform added the day foreign customers justify it. All behind a single billing layer in your product, so the rest of the application doesn't depend on any particular gateway. That's how we design billing in our SaaS development projects. To discuss it based on your market and customers, contact us.