FYNDNA retail banking suite
  1. Party deduplication
FYNDNA retail banking suite
  • Party deduplication
    • Dedupe configuration
      • Create dedupe configuration
      • Retrieve all dedupe configurations
      • Update a dedupe configuration
      • Delete a dedupe configuration
      • Modify a dedupe configuration
      • Update a specific criterion in a dedupe configuration
      • Retrieve a specific dedupe configuration
      • Delete a specific dedupe configuration
      • Retrieve the dedupe configuration for a party type
    • Dedupe execution
      • Initiate synchronous dedupe
      • Initiate asynchronous dedupe
    • Dedupe results
      • Retrieve dedupe results
  1. Party deduplication

Dedupe execution

You can initiate a dedupe call in two ways.
Synchronous - A synchronous dedupe call refers to a process where the system performs a real-time duplicate check during customer creation or existing customer's data update. The system waits for the deduplication result before proceeding. The synchronous deduplication process is integrated into the party onboarding or party update workflow.
Asynchronous - An asynchronous dedupe call refers to a process where the deduplication check is performed in the background, independently of the primary operation. This means the system continues the primary operation without waiting for the deduplication results. Once the deduplication process is complete, the result is shown in the response with a unique ID. You can fetch this result using the Retrieve dedupe results endpoint.
The system always executes the check against the confirmed criteria first. If a match is found, it does not check against the potential criteria.
The following endpoints are available for dedupe execution:
Initiate synchronous dedupe
Initiate asynchronous dedupe
Modified at 2025-03-04 09:48:56
Previous
Retrieve the dedupe configuration for a party type
Next
Initiate synchronous dedupe
Built with