What is KYC Verifications API

KYC Verifications API is a centralized capability to create, fetch, and update compliance verification cases and the required documents/fields across multiple use cases, such as Payouts and Remittances flows. It standardizes statuses, notifications, and document handling to reduce friction for merchants and internal teams, while ensuring compliance with the regulatory requirements of the target markets.

How it works

A verification is created for a given use case and assigned a verification ID.
The system returns the list of required documents/fields, which the merchant can fetch and complete via API using multipart/form-data uploads (files) or values (fields).
Verification status transitions through well-defined states (e.g., CREATING → PENDING → APPROVED/REJECTED/EXPIRED/ERROR) with webhooks on each key change.

Verifications services endpoints

Service	Method & endpoint	Description
Create a verification	POST /verifications	This service can be used to create a verification.
Get verification details	GET /verifications/{verification-id}	This service can be used to retrieve a verification.
Get documents	GET /verifications/{verification-id}/documents	This service can be used to retrieve the required documentation that needs to be sent for a given verification. These documents must be sent and validated by dLocal for the verification to be approved.
Update document	PATCH /verifications/{verification-id}/documents/{document-id}	This service is responsible for updating a specific document associated with a given verification using a multipart/form-data request. Depending on the type of document and its status, the information is allowed to be updated. Operation is only permitted when the document has a status: `PENDING`. Once the document status changes to `COMPLETED`, ERROR, or `APPROVED`, updates via `PATCH` will not be possible.

Use cases

If you need to handle KYC checks for both your customers, end users, and/or sub-merchants, our KYC verification solution will help you manage the end-to-end flow in a simple, compliant, and fast way. We can support different models, not limited to the following examples.

Payouts On Hold: dLocal creates a verification when additional compliance information is needed to release a payout; merchants complete the requested items via API or form-data uploads.
Remittances: Merchants create verifications for remitters and beneficiaries, submitting identity and other required information depending on the country and role.
Standalone (KYC as a Service): Merchants create independent verifications that are not tied to a dLocal entity necessarily; dLocal performs the KYC check and returns the final status for the merchant to consume in their own flows (ex., validate an end user’s tax ID condition and age).