Skip to main content

Overview

Enhanced due diligence (EDD) is the process financial institutions use to check and monitor high-risk customers and unusual transactions for potential money-laundering activity. The information required varies by scenario, so Synctera’s EDD API accepts a different set of fields for each type of resource. An EDD submission attaches extra information to an existing resource. Combined with the data gathered during KYC/KYB, it feeds Synctera’s Customer Risk Rating (CRR) and supports responses to requests for information (RFIs). Key characteristics:
  • Typed by resource — each submission targets a CUSTOMER, BUSINESS, ACCOUNT, or TRANSACTION, and the accepted fields differ per type.
  • Reason-driven — the reason field (CASE_REQUEST or STANDARD_SUBMISSION) records why the EDD was created; a CASE_REQUEST also requires a case_id.
  • CRR input — customer and business EDD, together with KYC/KYB data, lets Synctera compute a Customer Risk Rating.
  • Attachable — supporting documents can be linked to an EDD using the Documents API.

Customer EDD

Business EDD

Account EDD

Transaction EDD

When to submit EDD

  • During onboarding — submit additional information right after creating a customer or business.
  • In response to an RFI — answer a request for information on a KYC/KYB, account, or transaction case, referencing the case_id.
  • Recurring updates — periodically refresh a customer’s or business’s information.
  • High CRR outcome — when a customer or business is rated High by the CRR, EDD is required.

Prerequisites

This guide assumes you have: You should also be familiar with:

The EDD object

Every EDD submission shares a common set of fields; the remaining fields depend on related_resource_type. Submit an EDD with POST /v0/edd. The sections below show the additional fields for each resource type.

Submitting EDD

Customer EDD

Customer EDD submits additional information about a personal customer, either after creation or as a response to an RFI on a KYC case. Along with KYC data, it lets Synctera run a Customer Risk Rating.

Business EDD

Business EDD submits additional information about a business, either after creation or as a response to an RFI on a KYB case. Along with KYB data, it lets Synctera run a Customer Risk Rating.

Account EDD

Account EDD submits additional information about an account, typically in response to an account under review or frozen. Beyond the common fields, it accepts additional_questions.

Transaction EDD

Transaction EDD submits additional information about a specific transaction, typically in response to an RFI for a transaction in review.

Best practices

When reason is CASE_REQUEST, always include the case_id. Omitting it means the submission cannot be tied back to the case that requested it.
  • Submit the complete field set — for business EDD, every specific_involvement flag must be provided, even when false.
  • Attach supporting documents — link source documents to the EDD with the Documents API rather than pasting them into answers.
  • Keep information current — submit recurring updates for higher-risk customers and businesses so the CRR reflects the latest data.
  • Answer RFIs specifically — use additional_questions to give clear, reviewable answers a compliance analyst can act on.

Create a Personal Customer

Onboard a person before submitting customer EDD.

Create a Business Customer

Onboard a business before submitting business EDD.

KYC/KYB Verification

EDD complements the data collected during verification.

API reference