RentOnCloud

http://3.9.115.83:8080/Equifaxapi/webresources/

Deployed URL

http://ec2-18-130-37-209.eu-west-2.compute.amazonaws.com:8787/Equifaxapi/webresources

 http://3.9.115.83:8080/Equifaxapi/webresources/info.rocsearchinput/search

{
"applicantType":"single",
"bldgName":"1865",
"dateOfBirth":"1986-10-06",
"firstName" :"JANICE",
"lastName":"JONED",
"postTown":"ELY",
"postcode":"CB6 1AU",
"searchType":"AML",
"street1":"BERNARD ST",
"middleName":"",
"dateCreated":""
}

Sample response message

Status code: 200 OK (Successfully inserted) what are other status codes and means?

1. Does this status code '200' means zyPass has successfully analyse all xml attribute output received from EquiFax and stored parsed raw and summary result data in table hosted in SQL dB with searchID and later step is just to retrieve result summary data? 

2.  OR, is this just a connection test to validate test data of name and address? 

3. What if this is failed, then what are error code and any other messages? how to deal with that, to contact Equifax or Zypass Support? in case of failed or error code, will that count in AML / TV paid search if its not success at step 1.

4.  Is this searchId example '381' created by Equifax? or zyPass?  Can this result be retrievable by calling again same test URL http://3.9.115.83:8080/Equifaxapi/webresources/info.rocsearchinput/aml/381? Will it trigger to Equifax service layer again or will this search response from existing SQL test stubbed data? I am thinking of cost perspective if this is relevant or can we do N number of searches with existing IDs tested in past?

5. Is this field name "bldgName" used for building number? If address has Flat number or building name , which field to input search and in what format? 

6. In test first endpoint URL search do we need to always put “Search Type” : ‘AML’ ? and then step 2.a with AML or TV result link? OR step 1 create search ID for TV we can insert 'TV' and run TV result URL?

7. “Application type “ : ‘Single’ : will it be fixed search input for all test cases? if not what are other possible input accepted?

{
    "searchId": 381,
    "message": "success"
}

 http://3.9.115.83:8080/Equifaxapi/webresources/info.rocsearchinput/aml/381

{
"address":{
"result":"Pass",
"message":"Supplied address found",
"value":"2"
} ,
"pepCheck":{
"result":"Pass",
"pepMsg":"No data matched",
"value":"0"
},
"identity":{
"result":"Pass",
"message":"Confirmed",
"value":"1"
},
"sipCheck":{
"result":"Pass",
"pepMsg":"No data matched",
"value":"0"
},
"message":"success",
"sanctions":{
"result":"Pass",
"message":"No data matched",
"value":"false"
},
"rcaCheck":{
"result":"Pass",
"pepMsg":"No data matched",
"value":"0"
},
"status":true
}

 http://3.9.115.83:8080/Equifaxapi/webresources/info.rocsearchinput/tv/381

{
"judgement": {
"judgeValue": 1,
"judgement": "Fail",
"judgementMsg": "Judgement - active (Amount last 6 year) 14 and Judgement - satisfi
ed (Amount last 6 year) 0"
},
"address": {
"result": "Pass",
"message": "Supplied address found",
"value": "2"
},
"adverseDebt": {
"adverseDebtMsg": "no adverse findings",
"adverseDebt": "Pass",
"adverseValue": 0
},
"disputesAndCorrection": {
"dispute": "Caution",
"disputeValue": "false",
"disputeMsg": "Notices of dispute or corrections found"
},
"message": "success",
"rcaCheck": {
"result": "Pass",
"pepMsg": "No data matched",
"value": "0"
},
"pepCheck": {
"result": "Pass",
"pepMsg": "No data matched",
"value": "0"
},
"identity": {
"result": "pass",
"message": "Confrmed",
"value": "1"
},
"insolvencies": {
"insolvancy": "Fail",
"value": 2,
"insolvancyMsg": "1 Bankruptcies were found"
},
"alias": {
"firstname": "",
"aliasMsg": "Alias not found",
"lastname": ""
},
"sipCheck": {
"result": "Pass",
"pepMsg": "No data matched",
"value": "0"
},
"sanctions": {
"result": "Pass",
"message": "No data matched",
"value": "false"
},
"status": true
}

https://rentoncloud.s3.eu-west-2.amazonaws.com/aml.json

https://rentoncloud.s3.eu-west-2.amazonaws.com/tv.json

http://ec2-18-130-177-247.eu-west-
2.compute.amazonaws.com:3000/api/ScreeningData

"uId": this.state.userId,
"id": "",
"addResult response.data.address.result,
"addMsg": response.data.address.message,
"addValue": response.data.address.value,
"pepcheckResult":response.data.pepCheck.result,
"pepcheckMsg": response.data.pepCheck.pepMsg,
"pepcheckValue":response.data.pepCheck.value,
"identityResult": response.data.identity.result,
"identityMsg": response.data.identity.message,
"identityValue": response.data.identity.value,
"sipcheckResult": response.data.sipCheck.result,
"sipcheckMsg": response.data.sipCheck.pepMsg,
"sipcheckValue":response.data.sipCheck.value,
"message": response.data.message,
"sancResult": response.data.sanctions.result,
"sancMsg": response.data.sanctions.message,
"sancValue":response.data.sanctions.value,
"rcaResult": response.data.rcaCheck.result,
"rcaMsg": response.data.rcaCheck.pepMsg,
"rcaValue": response.data.rcaCheck.value,
"status": response.data.status

var payload={
"uId": this.state.userId,
"id": "",
"judgement":response.data.judgement.judgement,
"judgementMsg": response.data.judgement.judgementMsg,
"judgeValue": response.data.judgement.judgeValue,
"addressMsg":response.data.address.message,
"addressResult": response.data.address.result,
"addressValue":response.data.address.value,
"identityResult": response.data.identity.result,
"identityMsg": response.data.identity.message,
"identityValue": response.data.identity.value,
"adverseDebtMsg": response.data.adverseDebt.adverseDebtMsg,
"adverseDebt": response.data.adverseDebt.adverseDebt,
"adverseValue":response.data.adverseDebt.adverseValue,
"message": response.data.message,
"dispute": response.data.disputesAndCorrection.dispute,
"disputeValue": response.data.disputesAndCorrection.disputeValue,
"disputeMsg":response.data.disputesAndCorrection.disputeMsg,
"insolvancy": response.data.insolvencies.insolvancy,
"insolvancyValue": response.data.insolvencies.value,
"insolvancyMsg": response.data.insolvencies.insolvancyMsg,
"aliasFirstName": response.data.alias.firstname,
"aliasMsg": response.data.alias.aliasMsg,
"aliasLastName": response.data.alias.lastname,
"status": response.data.status
}

This can be found in ROC code in src/renter/RenScreeningreview.jsx

In submit() method

2. what is current DB storing strategy of Zypass built for parsed data and calculation of tables you have shown on Zoom call? Do you store the inflight data / attribute/characteristics result value in DB or its just server based calculation for user transaction session?

3. In your latest API sample document you had mentioned that ROC app (external consumption user) to store data in rentoncloud database using loopback api (ec2-18-130-177-247.eu-west-2.compute.amazonaws.com:3000/api ) following to receipt of Jason result file from Zypass API. Do we have to call the old loopback-api to save data to the db, as mentioned, everytime?