Overview
CMP (Case Managment Platform) is a workflow system for handling due dilligence in merchant onboarding.
From a black box perspective CMP has 2 inputs and 1 output. 
Inputs:
- API - allows to create new cases and get info on their progress
- UI - used by onboarding agents / escalation team / support team to handle human tasks in case automatic prorgression is not possible (e.g. due to data quality / error etc)
The output of CMP is determined by the specific case type being processed. Currently for ECOM Onboarding it’s one of 4 events:
- Merchant Application Created
- Merchant Application Risk Scored
- Merchant Application Approved
- Merchant Application Rejected
See links in the side panel for event details.
In addition to sending events CMP also performs the following after case is processed:
- Send emails to interested parties
- Call CRM document api to upload contract / email summaries
End actions of case processing are fully customizable.
More technical details: https://nexigroup-netsnordics.atlassian.net/wiki/spaces/MSECOMM/pages/449183751/CMP+Technical+Overview
API
CMP’s api allows to:
- create new cases (merchant applications) that require due dilligence checks (aml, kyc, regulatory, risk related)
- check case status
CMP’s API is currently called directly only by Signup system. Other external systems (CRM, Merchant Portal, Partner Portal) call Signup’s API and use it as a proxy to create a case. This is because:
- The mentioned systems do not have all required information for performing due dilligence and merchant needs to provide the missing parts with the help of Signup forms,
- Before starting due dilligence the merchant needs to sign an initial agreement. Signup helps with this by providing esigning functionality.
It is also possible for other external systems to call the CMP’s api directly (bypassing Signup) although they need to provide all required data in input. Doing background checks needs to also be legally justified.
API’s details: https://nexigroup-netsnordics.atlassian.net/wiki/spaces/MSECOMM/pages/449183751/CMP+Technical+Overview#6.-Case-Managment-Platform-API
EMO migration 2025
In 2024 decision was made to replace EMO running on Oracle Fusion with an open source based solution.
Goals:
- Lower operational cost + risk
- Futureproof the solution
After discussions DSL approach was selected with Spring Framework as backbone. It’s widely known tech and zero license fee.
Camunda was dismissed as too costly in upkeep and mantainance
Azure Functions was dismissed for lack of support for human tasks.
In 2025 CMP replaced EMO. CMP is functionally 1-1 equivalent with EMO.
