← Back to the directory

Payment channel profile

Orange Money Maroc

Wallet / user payment entry · Morocco

MoroccoPrimary marketMain service market
Wallet / user payment entryRole / typeMobile money, Digital wallet
Usually requires a local entityEntity requirementOnboarding conditions
Real-time / T+0SettlementPayout timing

Overview

Orange Money Maroc is listed as mobile money, digital wallet in the LocalPayMap public directory. Use this page to prepare due-diligence questions; product availability and terms must be verified directly.

This is a market-specific Orange Money record, not a duplicate of the brand overview and not the only official onboarding or pricing route. The brand page aggregates related countries and PSP contact leads; this page keeps the local payment scenario visible.

Role in the payment stack

Wallet / user payment entry

This is usually a wallet or consumer payment entry. Foreign merchant access often depends on a PSP, aggregator, platform partnership, or local entity setup.

Merchant usage and connection route

Orange Money in the payment stack

Orange Money matters for merchants selling in specific African and Middle Eastern markets where the local Orange wallet is part of customer payment behavior. Merchants should treat each country operation separately and evaluate wallet acceptance, QR or USSD/app flow, cash-in context, refunds, exceptions, and reconciliation.

Connection route

Merchant access may be direct through the local Orange Money operation or indirect through a PSP, mobile-money aggregator, bank, gateway, platform, or local partner. Confirm the country-specific merchant product, contracting party, customer flow, settlement account setup, refund process, and support ownership.

Verification questions

  • Which country-specific Orange Money operation and merchant product is being evaluated?
  • Is onboarding direct with Orange Money or through a PSP, aggregator, bank, gateway, or partner?
  • Is the customer flow wallet app, USSD, QR, merchant code, ecommerce checkout, or in-person payment?
  • How are successful, pending, failed, reversed, disputed, and refunded transactions reported?
  • What merchant entity, store, KYC, business category, and operational review requirements apply?

Merchant caveats

  • Orange Money is country-specific; one market route should not be generalized to another.
  • Direct wallet onboarding and aggregator access can have different responsibilities.
  • Mobile money flows may differ from card, bank-transfer, or tokenized wallet checkout.
  • Do not infer pricing, settlement, or coverage from discovery examples.

Provider examples to verify

Orange Money Cote d'IvoireOrange Money JordanOrange Money SenegalpawaPayPayTech SenegalOrange Money Marocinwi moneyCMI-equipped merchant acceptance route requires verificationMorocco wallet aggregators require verification

Related markets

Cote d'IvoireJordanMoroccoSenegal

Keep researching

This explanation separates payment methods, PSPs/aggregators, acquirers/banks, wallets, and networks/schemes. It does not publish coverage, eligibility, pricing, settlement timing, or onboarding guarantees.

Sources

What merchants should confirm

  • Whether the product is available to merchants incorporated outside the target country.
  • Whether a local entity, local bank account, licence, or local tax registration is required.
  • Supported checkout flows, currencies, refunds, disputes, reconciliation fields, and payout options.
  • Industry restrictions, reserve policies, onboarding documents, and implementation support.

Merchant eligibility

A local entity, local account, or additional licensing may be required.

Pricing and settlement

Published pricing is suitable for initial screening only. Actual pricing can vary by country, industry, volume, settlement currency, integration model, and contract terms. Confirm the official pricing page or a provider quote before going live.

Settlement timing, payout currency, foreign exchange, reserves, and withdrawal rules must be confirmed with the provider.

Capability verification checklist

Use this public checklist before you ask for a quote or implementation access. Treat unknown fields as questions to verify, not as unsupported features.

  • Confirm who owns onboarding, KYB review, pricing, settlement, refunds, disputes, reconciliation, reserves, and support for the route you will use.
  • Open the official pricing, developer, support, or website links where available, then verify the exact production terms with the provider or PSP.
  • Do not treat public notes as final approval, final pricing, settlement timing, or a guarantee that your merchant entity can go live.

Official links to open

Commercial terms to confirm

Pricing modelwallet acceptance or psp priced
Pricing basisofficial pricing page or public terms
Fields still to confirm
  • Fee range: confirm with the provider, acquirer, PSP, or official documentation before launch.
  • FX markup: confirm with the provider, acquirer, PSP, or official documentation before launch.
  • Chargeback fee: confirm with the provider, acquirer, PSP, or official documentation before launch.
  • Payout fee: confirm with the provider, acquirer, PSP, or official documentation before launch.
  • Reserve policy: confirm with the provider, acquirer, PSP, or official documentation before launch.

Integration route to confirm

API / checkout routepsp wallet enablement
Fields still to confirm
  • SDK languages: confirm with the provider, acquirer, PSP, or official documentation before launch.
  • Sandbox: confirm with the provider, acquirer, PSP, or official documentation before launch.
  • Webhooks: confirm with the provider, acquirer, PSP, or official documentation before launch.
  • Idempotency: confirm with the provider, acquirer, PSP, or official documentation before launch.
  • PCI scope: confirm with the provider, acquirer, PSP, or official documentation before launch.
  • 3-D Secure: confirm with the provider, acquirer, PSP, or official documentation before launch.

Operational features to confirm

No public field in this group is complete enough to treat as confirmed. Use it as a due-diligence prompt.

Fields still to confirm
  • Recurring billing: confirm with the provider, acquirer, PSP, or official documentation before launch.
  • Marketplace split: confirm with the provider, acquirer, PSP, or official documentation before launch.
  • Partial refund: confirm with the provider, acquirer, PSP, or official documentation before launch.
  • Preauth / capture: confirm with the provider, acquirer, PSP, or official documentation before launch.

Public pricing signals are for initial screening only. Actual quotes can vary by country, industry, transaction volume, settlement currency, integration route, and contract terms.

Visit the official website