KYC Information Requirements
Requirements could be different depending on the verification type, client, country, and user case.
Entity types
| Client type | Description |
|---|---|
| Remitter | The person or entity that sends the money in a payment or transfer; the originator of the payment. |
| Beneficiary | The person or entity that receives the money; the recipient of the payment. |
Request information
| Information | Description |
|---|---|
| Basic account information | The basic account information includes verification type and notification URL. |
| Attributes information | Attributes include specific information for each verification type. The content of the object might be different depending on the use case. It includes external reference and client information. The external reference should be the ID you assigned to the entity in your system. |
| Client information | Clients are either companies or individuals to whom we perform the verification. The content of the object might be different depending on the use case. |
Response detail
Important items we will include in the response:
| Fields | Description |
|---|---|
| Verification ID | It's the unique ID in the dLocal system; make sure you save it in your system. All the following actions and queries should be based on this. |
| Status | It's the status code, message, and details. Please refer to Verification Status for detailed information. |
You can also check the examples.
Manage Documentation
Find comprehensive information on documentation management in the following section: Manage documentation.
Updated about 2 hours ago
