API – Update Merchant Processor Group

General

This article explains how to use the API to update merchant processor groups. You can also do this through the UI.

To update the merchant processor group using the LoanPro API, you simply need to update the loan settings. To do this, send a PUT request to the endpoint:

PUT https://loanpro.simnang.com/api/public/api/1/odata.svc/Loans({LoanId})

The payload should look something like this:

{  
"LoanSettings":{
"id":598,
"loanId":639,
"cardFeeAmount":"5",
"cardFeeType":"loan.cardfee.types.1",
"cardFeePercent":"5",
"agent":0,
"loanStatusId":1,
"loanSubStatusId":1,
"sourceCompany":null,
"eBilling":0,
"ECOACode":"loan.ecoacodes.1",
"coBuyerECOACode":"loan.ecoacodes.0",
"creditStatus":"loan.creditstatus.0",
"creditBureau":"loan.creditbureau.00",
"reportingType":"loan.reportingtype.I",
"secured":1,
"autopayEnabled":0,
"repoDate":"",
"closedDate":"",
"liquidationDate":"",
"followUpDate":"2019-01-01",
"isStoplightManuallySet":0,
"merchantProcessorGroupId":0,
"__update":true,
"__id":598
},
"__update":true,
"__id":639
}

You will specifically want to change the merchantProcessorGroupId property. You can find the IDs of your merchant processor groups by navigating to Settings > Company > Merchant > Secure Payments inside your LoanPro account. If the field is left blank, the default group will be applied.

StackBlitz Example

Many of our articles use StackBlitz examples like this. These examples are like a window into a REST client right here in your browser. The window is divided into two sides. Developers can use info in the editor on the left side when configuring your API integration, and the right side shows a preview of a REST client. Click 'Preview' on the bottom, and you'll only see the REST client.

The entire request is set up and connected to a demo API tenant in LMS. Just scroll down and click 'send' and you should get a 200 response. If you want to get some practice with error codes, try editing the endpoint, headers, method and payload to see what responses you get.


How did we do?


Powered by HelpDocs (opens in a new tab)