Overview

The Merchant Onboarding process can be divided into 3 distinct phases:

• data acquisition - includes gathering information from merchant that’s required to sign a contract
• due dilligence - includes activites related to screening a merchant, checking against official registries, performing aml/kyc checks, gathering required documents etc
• activation - performed after succesfull due dilligence decision, includes enabling products merchant signed the contract for

The Onboarding domain supports all phases of the Merchant Onboarding process as follows.

Data acquisition

Merchant can initiate an onboarding process in 2 ways:

• self-service - through Merchant Portal,
• assisted - Nexi employee / Partner initates onboarding on merchant’s behalf through Partner Portal or CRM

When an onboarding process is initiated a request for onboarding is created in Signup. The merchant receives info about pending onboarding process and can proceed to fill out all missing information with the Signup form. When all data is provided, a draft contract is signed and a case is created in CMP.

Due dilligence

CMP system provides a workflow for performing all necessary regulatory and risk background checks for a merchant application. This includes AML and KYC.

All checks are attempted to be performed automatically. This involves calling multiple external systems hosted both in public and internal networks.

Sometimes due to low data quality / errors in external systems onboarding agents need to handle validations manually using UI. It also happens that onboarding agents reach out directly to merchants via email requesting required info and documents. Merchant receives a link to Form Service that provides UI for submitting the requested data.

The merchant application can end as:

• approved
• rejected
• closed

When case is approved then activation steps are performed and events are send.

Activation

When merchant application is approved, CMP performs activation tasks. For ECOM onboarding this consists of:

• sending messages to payment method providers / partners / merchants
• calling external systems (e.g. documents API)
• sending events consumed by CRM (SAP) and Checkout domain (MMS)

For other onboarding products the activation tasks might differ. E.g. in TMO CAPS is updated directly as next action after approval.

Componet diagram

Please visit the following page for more details: https://nexigroup-netsnordics.atlassian.net/wiki/spaces/MSECOMM/pages/449183751/CMP+Technical+Overview

Sequence diagrams

Please check the following page for sequence diagram examples: https://nexigroup-netsnordics.atlassian.net/wiki/spaces/MSECOMM/pages/449183751/CMP+Technical+Overview#5.-Actors

Node diagram