Electronic signatures in Morocco: 9 decisions before integrating them into your customer journey

Nine decisions for integrating electronic signatures into a customer journey in Morocco: level, identity, consent, API, evidence, and reversibility.

Electronic signatures in Morocco: 9 decisions before integrating them into your customer journey

Electronic signatures in Morocco are not just a “Sign” button inside a customer portal. A reliable integration must connect the correct document to the correct signer, select a signature level that fits the risk, capture explicit consent, retain useful evidence, and synchronize the outcome with the CRM or business application.

Before choosing a provider or API, make nine decisions. They determine the intended evidential value, signer experience, transmitted data, workflow states, failure recovery, and ability to change providers. This guide explains the method without replacing legal analysis of the document and sector concerned.

Team in Morocco planning an electronic signature integration for a customer journey
The signature journey starts with the document, signer, and risk level — not the API.

Quick answer: what exactly should be integrated?

Most business applications integrate an appropriate trust service provider rather than building their own cryptographic signing engine. The application prepares and freezes the document, identifies the journey and signers, calls the chosen service, follows events, retrieves the signed document, and retains the required evidence.

Morocco’s Law No. 43-20 governs trust services for electronic transactions. The official DGSSI FAQ explains signature levels, legal effects, validation, preservation, and remote signing. Verify the applicable version and formal requirements for the specific instrument before production.

Three distinctions to understand before choosing technology

ConceptQuestionExpected evidence
IdentificationWho is the person or organization?Data and method appropriate to the risk
AuthenticationHow do they confirm access or action?A verifiable event with appropriate controls
SignatureHow is the action linked to the signer and instrument?Integrity, consent, and evidence of the process

A code received by SMS may contribute to authentication, but it does not define the legal level by itself. The level depends on the complete process, identity, any certificate, document integrity, and provider.

Nine decisions before integrating electronic signatures

1. Define the document and when it becomes final

Name the instrument: contract, purchase order, mandate, minutes, amendment, or internal approval. Define who creates the final version, which appendices form part of it, which identifier links it to the business case, and what prevents changes after sending. The signer must see the exact document before consenting.

If content changes, create a new version instead of overwriting the one already sent. Retain its fingerprint, version number, and relationships. Kanteek’s guide to approval workflows in Morocco helps separate internal approval from external signature.

2. Assess risk and applicable formalities

Estimate the likelihood of a dispute and its consequences: value, duration, reversibility, parties, sector, and special formalities. The DGSSI explains that several levels can be used for many documents, while some instruments follow specific formal rules. The greater the likelihood and severity of a dispute, the stronger the case for a level with higher evidential assurance.

Document the decision with business owners and legal counsel. One matrix for every document would be misleading: an acknowledgement and a significant financial commitment do not necessarily require the same mechanism.

3. Choose simple, advanced, or qualified signing

Law 43-20 provides different levels. A qualified electronic signature benefits from a presumption of reliability similar to a handwritten signature; when combined with a qualified timestamp, it may produce the effect specified by law for a legalized handwritten signature. A non-qualified signature is not deprived of effect simply because it is electronic, but its reliability may need to be demonstrated through an evidence file.

Do not choose a level from the commercial name of an offer. Ask the provider for the exact status of the service, the certificate used, identification steps, evidence delivered, and reference to the authority’s declarations or trusted lists.

4. Design identity, authentication, and consent

Decide whether the signer is already known to the CRM, whether they represent a legal entity, and which checks are necessary. The experience should present the document, declared identity, requested action, and a clear expression of consent. A preselected box or ambiguous action weakens the journey.

Support refusal, expiry, signer replacement, and assistance. In a multilingual journey, French, Arabic, and English must preserve the same legal meaning and essential information.

5. Verify the provider and ownership of assets

Check the provider and service status in DGSSI resources: qualified service or another declared service, scope, and validity. The national trusted-list requirements describe publication of qualified services; other services use a declarative list.

The contract should allocate ownership of accounts, data, documents, logs, templates, domains, API keys, and environments. Require export, return, and provider-change procedures. Dependency is not measured only by whether a PDF can be downloaded.

6. Model every workflow state

A request is not merely “sent” or “signed.” Use explicit states: draft, ready, sent, viewed, identification pending, signing, signed, declined, expired, cancelled, and failed. Define who may cause every transition and how the CRM reflects it.

The guide to API integration in Morocco covers contracts, webhooks, and recovery. A webhook may arrive more than once or out of order: retain the event ID, verify authenticity, and make processing idempotent.

7. Reconcile the provider and business system

Imagine the provider completes the signature but your server fails before recording the status. The provider considers the document signed while the CRM still shows it as pending. Schedule reconciliation that rereads open requests and compares states.

The browser must never mark a contract as signed on its own. The server confirms important transitions from an authenticated event or a direct provider API lookup.

8. Build an evidence file and suitable preservation

The signed document may not tell the whole journey. Depending on the level and use case, the evidence file can include identifiers, versions, timestamps, events, identification method, consent, certificate, validation result, and document delivery. Retain only what is needed and protect it from alteration.

Law 43-20 also covers validation and preservation services. Decide who validates the signature over time, how the organization will show that it was valid at creation, and how certificate expiry or revocation is handled.

9. Govern personal data and reversibility

The journey may process name, contact details, identifiers, documents, IP addresses, authentication evidence, and logs. Define purpose, basis, recipients, processors, security, retention, and rights. Morocco’s CNDP requires sufficient safeguards from processors and appropriate handling of international transfers.

Test return of documents, evidence, states, and identifiers in a usable format. A provider-independent business layer makes migration easier: the application calls actions such as create request, add signer, cancel, retrieve document, and verify status; an adapter translates them to the chosen API.

A minimal reliable architecture

  1. The business application freezes the document and creates a request with a unique ID.
  2. An orchestrator selects the journey and calls the appropriate provider.
  3. The signer views the document, identifies, authenticates, and consents through the selected mechanism.
  4. The provider emits events; the server verifies, deduplicates, and updates the case.
  5. A reconciliation job compares open requests with provider state.
  6. The document, necessary evidence, and validation results are preserved under defined rules.

Kanteek’s Web & Mobile service covers portals and business applications; Automation orchestrates states and integrations; Consulting & Strategy frames risk, accountability, and the roadmap.

Common mistakes to avoid

  • selecting a provider before defining the document and risk;
  • confusing OTP, authentication, and signature level;
  • allowing the document to change after sending without a new version;
  • treating the signed PDF as the only evidence;
  • trusting a status set by the browser;
  • processing the same webhook twice and triggering duplicate actions;
  • collecting excessive logs without a retention rule;
  • discovering export limitations during provider replacement.

Checklist before the pilot

  • mapped documents, signers, and versions;
  • validated risk and formality for each journey;
  • justified signature level and verified service;
  • tested identification, authentication, consent, and refusal;
  • documented workflow states and permissions;
  • tested webhooks, idempotency, failures, and reconciliation;
  • defined evidence file, validation, and preservation;
  • reviewed personal data, processors, and transfers;
  • demonstrated export and provider change.

FAQ about electronic signatures in Morocco

Is a simple electronic signature valid in Morocco?

It cannot be rejected solely because it is electronic or not qualified. Its reliability and evidential weight depend on the process and may need to be demonstrated. The specific document and risk require review.

Is an SMS OTP enough for an advanced signature?

No, not by itself. An OTP can contribute to authentication, but the level follows the complete system: identity, control, link to the document, integrity, any certificate, and legal requirements.

Can a person sign from a phone?

Yes. The DGSSI describes remote or cloud signatures, where a provider can manage the creation environment for the signer. Verify the actual level delivered and test the experience on target devices.

Is the signed PDF enough evidence?

Not necessarily. Depending on the process, events, certificates, timestamps, validation results, and consent evidence may also be required. Retention and preservation depend on the use case.

How should electronic signatures connect to a CRM?

Use a shared identifier, explicit states, verified idempotent webhooks, and reconciliation. The CRM stores the business state; the provider supplies the signing event, confirmed server-side.

Integrate evidence, not only the button

Electronic signatures in Morocco become reliable when document, trust level, identity, consent, technical states, and preservation form one journey. To frame the application, API, and pilot without locking the system to one provider, contact Kanteek.