Sign in

v1

latestOpenAPI 3.1.02026-07-245361280.3 KB
Verifications

Create a verification

Creates a verification. Available and mandatory fields depend on the type of client, country, and industry. The service returns a verification ID for use with Payins and Payouts APIs.

Wire format: the endpoint accepts multipart/form-data with a string field body whose value is a JSON string with the same structure as the application/json body below, and optional file parts (use filenames such as DOCUMENT_FRONT and DOCUMENT_BACK where required). The JSON body below is the reference shape; stringify it to populate the body part when using multipart.

Notifications: status updates will be sent to the notification_url provided in the request. See the Callbacks section below and the Verifications notifications guide for the retries policy and signature recipe.

post/verifications

Request body

OR
OR

Example request

{
  "type": "REMITTANCE"
}

Response

Successful response

typestring

Flow discriminator. Remittance verifications use REMITTANCE. Other examples include STANDALONE, PAYOUT_ON_HOLD, and PAYINS_ON_HOLD — use values provided by dLocal for your agreement.

idstring

dLocal verification ID in UUID format.

notification_urlstring uri

URL where dLocal will send notifications associated with verification status changes. See Verifications notifications for the payload contract.

created_datestring

Creation timestamp (e.g. YYYY-MM-DDTHH:mm:ss with optional fractional seconds).

expiration_datestring

Expiration when applicable; may be empty.

statusstring

Verification status. See details.

status_detailstring

Verification status detail. See details.

attributesobject

Commonly includes external_reference and, when include=client_data is used, client (beneficiary, remitter, payer, etc.) and related nested objects.

Example response

{
  "id": "KV-371ea706-0be6-4088-9693-11f6be6b3240",
  "status": "CREATING",
  "status_detail": "CREATING"
}