Filtering start

The filtering is launched as soon as the identity is validated.The maximum treatment time is 8 minutes, if no hits appear.If a hit appears, an operator has to manually validate the accuracy of the hit before the workflow can continue.

Filtering results

Xpollens results are shared through the attributs "IsPoliticallyExposedPerson" in the callback named PoliticallyExposedPersonStatusCreatedOrUpdated.It is important to note that the filtering is done automatically, but that the decision to enter into a relationship following a hit is manual. The delay is therefore longer in this case.

Filtering sequence diagram

As soon as the identity is validated, the Political Exposed Person filtering starts.

Best scenario

sequenceDiagram
  
autoNumber
Actor User
Participant Partner
Participant XPO

XPO --) Partner : Callback 4 - KYC Demand<br/>status:Completed <br/>receivedDiligences[{diligenceType Identity, status:Validated}],<br/>expectedDiligences [{diligenceType Complementary}, status:XXX]
XPO --) XPO: filtering [3 to 8 minutes]

alt PPE Sanction is false
    XPO --) Partner : Callback PoliticallyExposedPersonStatusCreatedOrUpdated - results of PPE filtering and penalties <br/> {isPoliticallyExposedPerson:false,<br/> finalDecisionPep:null}
	note over Partner, XPO: onboarding process continues

else Hit PEP or sanction
note over Partner, XPO: manual process 
end

PEP Hit

sequenceDiagram
  
autoNumber
Actor User
Participant Partner
Participant XPO
Title Hit PEP

XPO --) XPO: filtering [3 to 8 minutes]
XPO --) Partner : Callback PoliticallyExposedPersonStatusCreatedOrUpdated {riskAnalysisStatus:InProgress}
break Waiting for internal decision
 	XPO-->XPO: Hit analysis
end

alt PEP false
    XPO --) Partner : Callback PoliticallyExposedPersonStatusCreatedOrUpdated - results of PPE filtering and penalties <br/> {isPoliticallyExposedPerson:false,<br/> finalDecisionPep:null,<br/> riskAnalysisStatus: Done}

else PEP true, but continuing the relationship
        XPO --) Partner : Callback PoliticallyExposedPersonStatusCreatedOrUpdated - results of PPE filtering and penalties <br/> {isPoliticallyExposedPerson:true,<br/> finalDecisionPep:null,<br/> riskAnalysisStatus: InProgress}
		XPO --) User: Request for additional document
		User --) XPO: Document completed
        XPO --)XPO: Internal validation <br/> finalDecisionPep:true
        XPO --) Partner : Callback PoliticallyExposedPersonStatusCreatedOrUpdated - results of PPE filtering and penalties <br/> {isPoliticallyExposedPerson:true,<br/> finalDecisionPep:true,<br/> riskAnalysisStatus: Done}

      Partner ->> XPO: GET /api/v3.0/users/{appUserId}/anti-money-laundering
    XPO --) Partner: {isPoliticallyExposedPerson: true,<br/> isPoliticallyExposedPersonTrueAuthorized: true,<br/> riskAnalysisStatus:Done }	

else PEP true, and end of relationship
    XPO --) Partner : Callback PoliticallyExposedPersonStatusCreatedOrUpdated - results of PPE filtering and penalties <br/> {isPoliticallyExposedPerson:true,<br/> finalDecisionPep:null,<br/> riskAnalysisStatus: InProgress}
    XPO --)XPO: Final decision false
    XPO --) Partner : Callback PoliticallyExposedPersonStatusCreatedOrUpdated - results of PPE filtering and penalties <br/> {isPoliticallyExposedPerson:true,<br/> finalDecisionPep:false,<br/> riskAnalysisStatus: Done}
    XPO --) Partner : Callback 34 - UserRecordStatus: Refused
    Partner ->> XPO: GET /api/v3.0/users/{appUserId}/anti-money-laundering
    XPO --) Partner : {isPoliticallyExposedPerson: true,<br/> isPoliticallyExposedPersonTrueAuthorized: false,<br/> riskAnalysisStatus:Done }

end

👍

The user is contacted directly by Xpollens to request additional documents

🔗Formulaire_Client_PPE_v4.pdf

If the PEP document is not received within 3 weeks, the account will be permanently blocked.

As long as the hit is being processed, the user's status will remain at InProgress; and as long as the status is in progress, the customer cannot carry out transactions or receive money.

Sanction Hit

sequenceDiagram
  
autoNumber
Actor User
Participant Partner
Participant XPO
Title Hit Sanction
XPO --) XPO: filtering [3 to 8 minutes]
alt hit Sanction, final decision true (relationship accepted)
		XPO --)XPO: Internal validation: validated
   Note over User, XPO: onboarding can continue
    XPO --) Partner : Callback PoliticallyExposedPersonStatusCreatedOrUpdated - {isPoliticallyExposedPerson:false,<br/> finalDecisionPep:null,<br/> riskAnalysisStatus: Done}
	

else hit Sanction, final decision false (relationship refused)

		XPO --)XPO: Internal validation: 
		XPO --) Partner : Callback PoliticallyExposedPersonStatusCreatedOrUpdated - {isPoliticallyExposedPerson:false,<br/> finalDecisionPep:null,<br/> riskAnalysisStatus: Done}
		XPO --) Partner : Callback 34 - User Onboarding<br/>status:Refused
	Note over User, XPO: end of the relationship
end

Unlike PPE filtering, if a hit sanction is proven, the user is irremediably refused.

🚧

no information is displayed during a hit sanction, for compliance reasons.

Filtering duration

Production and unmocked environment vs. mocked environment (preproduction)

APIs, callbacks and technical items

GET /api/v2.1/user/compliance/appUserId

🔗AML status

Callback

🔗PoliticallyExposedPersonStatusCreatedOrUpdated

Mapping fields API / callback

Mapping API / callback

Cas not hit

\{  
"isPoliticallyExposedPerson": false,
"isPoliticallyExposedPersonTrueAuthorized": null,
"riskAnalysisStatus": "InProgress"
}

{
"appUserId": "{{appUserId}}",  
"type": "PoliticallyExposedPersonStatusCreatedOrUpdated",
"isPoliticallyExposedPerson": false,
"finalDecisionPep": null,
"riskAnalysisStatus": "InProgress"
}

{  
"isPoliticallyExposedPerson": false,
"isPoliticallyExposedPersonTrueAuthorized": null,
"riskAnalysisStatus": "Done"
}

{  
"appUserId": "\\{\\{appUserId}}",
"type": "PoliticallyExposedPersonStatusCreatedOrUpdated",
"isPoliticallyExposedPerson": false,
"finalDecisionPep": null,
"riskAnalysisStatus": "Done"
}

Cas hit PPE

{
"isPoliticallyExposedPerson": null,
"isPoliticallyExposedPersonTrueAuthorized": null,
"riskAnalysisStatus": "InProgress"
}

{
"appUserId": "{{appUserId}}",
"type": "PoliticallyExposedPersonStatusCreatedOrUpdated",
"isPoliticallyExposedPerson": null,
"finalDecisionPep": null,
"riskAnalysisStatus": "InProgress"
}

{
"isPoliticallyExposedPerson": true,
"isPoliticallyExposedPersonTrueAuthorized": null,
"riskAnalysisStatus": "InProgress"
}

{
"appUserId": "{{appUserId}}",
"type": "PoliticallyExposedPersonStatusCreatedOrUpdated",
"isPoliticallyExposedPerson": true,
"finalDecisionPep": null,
"riskAnalysisStatus": "InProgress"
}

{
"appUserId": "{{appUserId}}",  
"type": "PoliticallyExposedPersonStatusCreatedOrUpdated",
"isPoliticallyExposedPerson": false,
"finalDecisionPep": null,
"riskAnalysisStatus": "InProgress"
}

{
"appUserId": "{{appUserId}}",  
"type": "PoliticallyExposedPersonStatusCreatedOrUpdated",
"isPoliticallyExposedPerson": false,
"finalDecisionPep": null,
"riskAnalysisStatus": "InProgress"
}

{
"isPoliticallyExposedPerson": true,
"isPoliticallyExposedPersonTrueAuthorized": false,
"riskAnalysisStatus": "Done"
}

{
"appUserId": "{{appUserId}}",
"type": "PoliticallyExposedPersonStatusCreatedOrUpdated",
"isPoliticallyExposedPerson": true,
"finalDecisionPep": false,
"riskAnalysisStatus": "Done"
}

Cas hit Sanction

{
"isPoliticallyExposedPerson": null,
"isPoliticallyExposedPersonTrueAuthorized": null,
"riskAnalysisStatus": "InProgress"
}

{
"appUserId": "{{appUserId}}",
"type": "PoliticallyExposedPersonStatusCreatedOrUpdated",
"isPoliticallyExposedPerson": null,
"finalDecisionPep": null,
"riskAnalysisStatus": "InProgress"
}

{
"isPoliticallyExposedPerson": false,
"isPoliticallyExposedPersonTrueAuthorized": null,
"riskAnalysisStatus": "Done"
}

{
"appUserId": "{{appUserId}}",
"type": "PoliticallyExposedPersonStatusCreatedOrUpdated",
"isPoliticallyExposedPerson": false,
"finalDecisionPep": null,
"riskAnalysisStatus": "Done"
}

📘

Note that the first two fields are false and null because they point to the PPE characteristic.

We can not display sanction data for compliance reasons.

How to test

1- Create a user with one the previous identity regarding the expected case

🔗Create a User

{
  "appUserId": "{{appuserid}}",
  "profile": {
    "civility": "{{civility}}",
    "firstName": "{{firstName}}",
    "lastName": "{{lastName}}",
    "birthName": "{{lastName}}",
    "birthDate": "1965-12-06",
    "birthCity": "Paris",
    "birthZipCode": "75001",
    "birthCountry": "FR",
    "nationality": "FR",
    "phoneNumber": "+33675449988",
    "email": "{{firstname}}_{{lastname}}[email protected]",
    "address": {
      "street": "51 Pender Street",
      "supplementIn": "Access by the garden",
      "supplementOut": "Corner House",
      "zipCode": "3071",
      "city": "Paris",
      "country": "FR",
      "area": "East-Thornbury"
    }
  }/*,
  "roles": [
    {
      "dependenceId": "{{legalEntityId}}",
      "types": [
        "LegalRepresentative",
        "BeneficialOwner"
      ]
    }
  ]

2- Create the KYC 🔗 Create a KYC

{
   "workflowCode":"Electronic_Sign"
}
````3- Scan Corinne Bethier's identity document and scan a face (see "0-Create and validate a user" if you don't want to scan yours).3- Ask your Customer Integration Manager to force the identity in the Netheos backoffice.
The post user does not contain the same values as the identity card. You will therefore receive  errors (inconsistent firstName inconsistent lastName, ...).4- As soon as this action is done, the following step are automatics. An hit is automatically generated.5- In the case of a proven PPE hit, ask your Customer Integration Manager to validate or refuse the relationship.

* * *

## FAQ



### FAQ1: Is it possible to reopen a user in Refused status?

The "refused" user status is a final status. It is therefore no longer possible to reopen it.