# FYNDNA retail banking suite ## Docs - [Party deduplication](https://apidog.com/apidoc/shared/5142f7db-7daf-45e4-ad7f-38665d2b59f4/party-deduplication-3064259f0.md): - Party deduplication [Dedupe configuration](https://apidog.com/apidoc/shared/5142f7db-7daf-45e4-ad7f-38665d2b59f4/dedupe-configuration-3026279f0.md): - Party deduplication [Dedupe execution](https://apidog.com/apidoc/shared/5142f7db-7daf-45e4-ad7f-38665d2b59f4/dedupe-execution-2856756f0.md): - Party deduplication [Dedupe results](https://apidog.com/apidoc/shared/5142f7db-7daf-45e4-ad7f-38665d2b59f4/dedupe-results-2856757f0.md): ## API Docs - Party deduplication > Dedupe configuration [Create dedupe configuration](https://apidog.com/apidoc/shared/5142f7db-7daf-45e4-ad7f-38665d2b59f4/create-dedupe-configuration-13986881e0.md): Deduplication is based on specific criteria defined in the dedupe configuration. You can define a dedupe configuration using this endpoint. - Party deduplication > Dedupe configuration [Retrieve all dedupe configurations](https://apidog.com/apidoc/shared/5142f7db-7daf-45e4-ad7f-38665d2b59f4/retrieve-all-dedupe-configurations-13986879e0.md): Deduplication is based on specific criteria defined in the dedupe policy. Each policy is a dedupe configuration. You can retrieve all dedupe configurations, using this endpoint. - Party deduplication > Dedupe configuration [Update a dedupe configuration](https://apidog.com/apidoc/shared/5142f7db-7daf-45e4-ad7f-38665d2b59f4/update-a-dedupe-configuration-13986880e0.md): Deduplication is based on specific criteria defined in the dedupe policy. Each policy is a dedupe configuration. You can update a dedupe configuration using this endpoint. For example, if "Aadhar" is already a part of the dedupe criteria, you can add "full name" to it as an additional criterion. This indicates that dedupe check should be performed against the Aadhar number and the full name of the party/prospect. - Party deduplication > Dedupe configuration [Delete a dedupe configuration](https://apidog.com/apidoc/shared/5142f7db-7daf-45e4-ad7f-38665d2b59f4/delete-a-dedupe-configuration-13986882e0.md): Deduplication is based on specific criteria defined in the dedupe policy. Each policy is a dedupe configuration. You can delete a dedupe configuration using this endpoint. - Party deduplication > Dedupe configuration [Modify a dedupe configuration](https://apidog.com/apidoc/shared/5142f7db-7daf-45e4-ad7f-38665d2b59f4/modify-a-dedupe-configuration-13986883e0.md): Deduplication is based on specific criteria defined in the dedupe policy. Each policy is a dedupe configuration. Using this endpoint, you can achieve the following in one go: - Party deduplication > Dedupe configuration [Update a specific criterion in a dedupe configuration](https://apidog.com/apidoc/shared/5142f7db-7daf-45e4-ad7f-38665d2b59f4/update-a-specific-criterion-in-a-dedupe-configuration-13986884e0.md): Deduplication is based on specific criteria defined in the dedupe policy. Each policy is a dedupe configuration. You can update a specific dedupe criterion using this endpoint. For example, you can add incremental attributes like "full name check" to an existing match criterion like Aadhar. This means that the dedupe process should validate the Aadhar number and the full name of the party. - Party deduplication > Dedupe configuration [Retrieve a specific dedupe configuration](https://apidog.com/apidoc/shared/5142f7db-7daf-45e4-ad7f-38665d2b59f4/retrieve-a-specific-dedupe-configuration-13986885e0.md): Deduplication is based on specific criteria defined in the dedupe policy. Each policy is a dedupe configuration. You can retrieve a specific dedupe configuration using this endpoint. - Party deduplication > Dedupe configuration [Delete a specific dedupe configuration](https://apidog.com/apidoc/shared/5142f7db-7daf-45e4-ad7f-38665d2b59f4/delete-a-specific-dedupe-configuration-13986886e0.md): Deduplication is based on specific criteria defined in the dedupe policy. You can delete a specific dedupe policy using this endpoint. Each policy is a dedupe configuration. - Party deduplication > Dedupe configuration [Retrieve the dedupe configuration for a party type](https://apidog.com/apidoc/shared/5142f7db-7daf-45e4-ad7f-38665d2b59f4/retrieve-the-dedupe-configuration-for-a-party-type-13986887e0.md): Deduplication is based on specific criteria defined in the dedupe policy. You can retrieve the dedupe configuration for a specific party type using this endpoint. Each policy is a dedupe configuration. - Party deduplication > Dedupe execution [Initiate synchronous dedupe](https://apidog.com/apidoc/shared/5142f7db-7daf-45e4-ad7f-38665d2b59f4/initiate-synchronous-dedupe-13328810e0.md): A **synchronous** deduplication (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. In this type of operation, the deduplication process is integrated into the party onboarding or party update workflow. You can initiate a synchronous dedupe call using this endpoint. The request body consists of party details received from the external system. The system validates the details in this request against the party data existing in the FYNDNA system. - Party deduplication > Dedupe execution [Initiate asynchronous dedupe](https://apidog.com/apidoc/shared/5142f7db-7daf-45e4-ad7f-38665d2b59f4/initiate-asynchronous-dedupe-13328811e0.md): 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. - Party deduplication > Dedupe results [Retrieve dedupe results](https://apidog.com/apidoc/shared/5142f7db-7daf-45e4-ad7f-38665d2b59f4/retrieve-dedupe-results-13328812e0.md): You can retrieve a specific dedupe result record by passing the unique party ID in the query.