Onboarding and screening a customer
| Current solution | ComplyAdvantage Mesh |
|---|---|
| Submit the customer details and search profile identifier using the POST searches endpoint. | Submit the customer details and screening configuration identifier using POST workflows/create-and-screen or POST workflows/sync/create-and-screen |
| API reference | API reference – synchronous API reference – asynchronous |
Key differences
- With the existing solution, a search is created at the time of onboarding, which consolidates all information about the customer, case, and relevant risks.
- This search record drives all ongoing operations. Directly querying a customer, case, or risk is not a concept.
- In ComplyAdvantage Mesh, customers, cases, and alert records are created at the time of onboarding.
- These records can then be queried individually through the API, and several operations can be performed against them.
Asynchronous vs. synchronous onboarding in ComplyAdvantage Mesh
Asynchronous
The asynchronous API enables you to send a screening request and continue without waiting for an immediate response. The server processes the request independently and returns a response when it's ready.
It is best suited for high-volume applications, such as screening many customers in one go and remediating at a later stage.
How to use:
- Call asynchronous onboarding and screening workflow API.
- The response returns a workflow identifier.
- Subscribe to a webhook to receive the payload, or poll the get workflow status endpoint.
- Risks within an alert retrieved from an additional API call.
Benefits:
- Increased efficiency – multiple operations can be handled concurrently on your side.
- Can fire and forget, so you don't need to keep a connection open.
- Guarantees an eventual response.
Synchronous
The synchronous API enables you to send a screening request with an almost immediate response back. You have to wait for the server to finish processing the request before it can receive the response.
Best suited for real-time customer journeys where response time is key.
How to use:
- Call synchronous onboarding and screening workflow API.
- The response includes a payload.
- Risks within an alert retrieved from an additional API call.
Benefits:
- Optimized for low latency.
- Simple to integrate.
- Useful if required operations have to happen in a specific sequence.