There is no perfect gateway for every store. The right option depends on your legal entity, customers, average order value, currencies and the level of support you expect.
Start with your merchant profile
Before comparing names, confirm your status: freelancer, Moroccan company, foreign entity or organization. Define target countries, settlement currency, expected volume, product categories and refund policy. Some providers require trading history, a live website or additional compliance documents.
Ten options worth comparing
A comparison list can include CMI / Attijari Payment, Payzone, Fatourati, YouCan Pay, PayPal, Stripe, Payoneer Checkout, Verifone / 2Checkout, Checkout.com and Adyen. Availability varies by entity, industry, currencies and contract. Do not assume an international provider automatically accepts Moroccan merchants.
Compare costs and responsibilities
Ask for setup, subscription, transaction, conversion, chargeback and payout fees. Check settlement currency, payout timing, fraud tools and support for pre-authorization or capture. A rich API is useful only if your team can maintain the integration.
Validate the experience, not just the technology
Test the mobile journey, error messages, language, 3-D Secure and the path after a failed attempt. Your website should create the order server-side and confirm payment through a verified notification. A professional integration also covers refunds, disputes and audit logs.
Local options: CMI, Payzone, Fatourati and YouCan Pay
CMI / Attijari Payment is often the first option considered for accepting card payments in MAD through a hosted payment page. It is particularly relevant when you need a local banking process and a verifiable server notification. Payzone may be evaluated depending on the services, collection points or workflows available for your sector. Fatourati has historically been associated with bill payment and certain collection journeys. YouCan Pay can suit merchants already working inside the YouCan ecosystem.
The right choice depends on your contract, volume, industry and the exact features available. Always request current technical documentation, refund conditions, payout timing and compliance requirements instead of choosing a familiar name.
International options to review carefully
PayPal can answer some international requirements, but merchant eligibility, currencies, withdrawals and dispute handling from Morocco must be verified. Stripe offers a recognized developer experience, but availability depends on the country where the legal entity is registered. Payoneer Checkout, Verifone / 2Checkout, Checkout.com and Adyen may suit international volumes or markets, often with stricter acceptance criteria.
Never assume a well-known brand automatically accepts a Moroccan business. An international provider may require a foreign entity, transaction history or enhanced compliance. The issue is not only technical integration; it is also your ability to receive funds, manage refunds and satisfy audits.
Compare providers with an objective scorecard
Create a comparison table covering accepted entities, payment currencies, settlement currency, card and local methods, 3-D Secure, hosted page or API, fixed fees, variable fees, conversion fees, chargebacks, payout timing, refunds, support, documentation and dashboard quality. Add real onboarding time because approval can take time.
| Criterion | Question to ask |
|---|---|
| Eligibility | Are your entity and business category accepted? |
| Settlement | In which currency and how often are funds paid out? |
| Journey | Hosted page, redirect or API integration? |
| Risk | Which fraud tools and thresholds are available? |
| Operations | How are refunds, disputes and reports handled? |
Choose according to the sales model
A COD-first store can introduce card payment progressively. A fixed-price service can use a hosted page with a server-created order. A subscription requires recurring-payment capability that not every setup provides. An international store needs broader analysis of currencies, countries and fraud.
For dropshipping or a first store, onboarding speed should not outweigh stability. For an established business, reporting, reconciliation and support may be the priority. For an agency or service business, a reliable one-time payment flow may be enough.
Secure the integration before opening
The gateway should never receive an amount invented by the browser. Your server creates the order, calculates the price, stores the reference and signs the expected fields. Confirmation comes from a verified server-to-server notification, not from a simple return to a success page. Handle idempotency too: a repeated notification must not trigger a second capture or duplicate emails.
Test failures, delays, closed browsers and invalid signatures. Keep a technical event log without storing card data. Keys remain outside public source code and outside public_html. Our CMI integration checklist covers that process in detail.
Final decision: start with what you can verify
Choose the gateway whose eligibility you can confirm, whose journey you can test and whose fees you can explain. A less famous provider that contractually fits your business can be better than a prestigious name you cannot activate. Document the choice, support contacts and dispute procedures before launch.
If you are planning a store or sales journey, our ecommerce service can frame the architecture, customer experience and technical integration before you commit to a provider.
Questions to ask the provider
Ask for required documents, onboarding delay, accepted currencies, complete fees, refunds, chargebacks, limits, fraud tools and support level. Obtain written confirmation that your entity and activity are eligible. Also check whether the solution supports automatic capture, pre-authorization or recurring payments if needed.
A reasonable action plan
Create a shortlist of two or three options, request documentation and pricing, then test the technical journey in a sandbox. Compare total cost against margin and average order value. Move to production only after a successful transaction, verified notification, correctly stored order and a refund procedure your team understands.
Selection checklist
- Entity and activity eligibility confirmed in writing.
- Currencies, local methods, 3-D Secure, payouts and limits documented.
- Complete fees: setup, transactions, conversion, refunds and disputes.
- Technical documentation, test environment and accessible support.
- Capture, refund and audit-log policy defined.
The sign that a gateway is viable
A gateway becomes viable when your team can explain the flow of funds, test a transaction, handle a refusal and manage a refund. If the integration works but nobody knows how to track orders or disputes, activation is premature. The final choice must cover technology, finance and customer service.