MPO Setup

Jump to Section

Installation and configuration

Access your MPO environment.
Click on Create, select From file and add the .json file provided in the connector gitlab repository which you were given access to during the integration process. This will create a new folder for the nCino - Mambu Integration. Open this folder.
Access the 1. Action SPLITTER - linked to nCino process and click on the Start node.
Generate an ApiKey for this process and share the integration folder with the ApiKey.

Auth to MPO Share ApiKey

In the folder that was added to your MPO environment, go to the Setup folder and open the Setup process, switch to View mode, and press New task. Fill in all the required parameters and press Add task. Wait until the task is processed. Alternatively, you can use the following JSON. Modify it and paste into the Code editor tab.

{
    "nCinoCallbackUrl": "nCino callback URL",
    "nCinoCode": "nCino code used to create token and refresh token.",
    "nCinoConsumerKey": "nCino consumer key" ,
    "nCinoConsumerSecret": "nCino consumer secret ",
    "nCinoInstanceUrl": "nCino Salesforce instance url",
    "nCinoSessionTimeout": nCino value from Session Settings page in Salesforce in minutes, /*this has to be a number*/
    "ncinoConfigReference": "configuration",  /* keep value "configuration"*/
    "mambuConfigReference": "mambu", /*keep value "mambu"*/
    "oauthUrl": "oauth Url", /*this can be different for each environment used (sandbox or production)*/
    "mambuPassword": "Mambu password",
    "mambuUrl": "Mambu url",
    "mambuUser": "Mambu user",
    "mambuLoanCFieldSet": "Mambu custom field set id",
    "mambuLoanCFieldId": "Mambu custom field id",
    "mambuLoanCFieldInitialLaId": "Mambu initial loan account id",
    "mambuLoanCFieldPaymentHoliday": "Payment holiday setting",
    "notificationProcessId": "The process id of the custom Notification process. This can be empty if no Notification system is used",
    "notificationConfig":  {
        "[Notification conectivity details of the external system. This can be empty if no Notification system is used]"
    },
    "productList": "Product list object formed from objects containing each product key and its parameters array"
    {
        "[encoded key 1]" :{
            "productDetails": "[add some details for this product]",
            "parameters":
                ["param1", "param2", "param3",...]
            },
        "[encoded key 2]" :{
            "productDetails": "[add some details for this product]",
            "parameters":
                ["param1", "param2", "param3",...]
            },
        ...
    },
    "retryInterval": "retry interval for Api calls",
    "retryLimit": "retry limit for Api calls",
    "limitSizeGetLoans": "the number of loan accounts to retrieve, used in combination with offset to paginate results",
    "timezone": "Mambu tenant timezone"
}

Note: Each loan product key must have the necessary parameter codes for its product type. Consult the table in the slips logic article for more information on which codes are used for the types of loan your institution offers.

productList object working example:

"productList": {
       "8a19a9b6727f4fd001727fabdbb30098": {
           "productDetails": "nCino Personal Loan /Do Not Delete",
           "parameters": [
               "NI",
               "COM",
               "IS.1",
               "DD.1",
               "SS.1",
               "FEE"
           ]
       },
       "8a19a9b6727f4fd001727fcbb85700cf": {
           "productDetails": "nCino DBEI + RNI /Do Not Delete",
           "parameters": [
               "NI",
               "COM",
               "IS.2",
               "DD.1",
               "SS.1",
               "FEE"
           ]
       },
       ....
   }

Setup process

Products configuration

Products will be stored in the productList object in the Mambu config state diagram which you can find in the Setup > Mambu setup folder.

Each loan product key must have the necessary parameters array, containing the parameter codes required for its product type.

For example, a Dynamic Term Loan Product with Fixed Interest Rate and encodedKey 8a19a9b6727f4fd001727fabdbb30098 would be represented by the following object:

{
    "8a19a9b6727f4fd001727fabdbb30098": {
                "parameters": [
                    "NI",
                    "COM",
                    "IS.1",
                    "DD.1",
                    "SS.1",
                    "FEE"
                ]
            }
}

A table of product types and their related parameter codes can be found in the slips logic article.

MPO products mapping example

Notes:

Based on the Parameters configured for each product, the loan accounts will be created with a set of specific data.
The Revolving Credit loans do not allow grace period installments. Also, the supported payment scheduling for these types of loans consists of monthly repayment days predefined at the loan product level.

Mambu Webhooks configuration