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.

Body Params
string
enum
required

Remittance verification — the allowed value is REMITTANCE.

Allowed:
uri

URL where dLocal will send notifications for verification status changes.

attributes
object
required

Remitter flow — client.type is always REMITTER in this shape.

file
array of files

File with the content of the document to update. Each file name must include an extension, which can be either .jpeg, .png, or .pdf.

DOCUMENT_FRONT and DOCUMENT_BACK. Please refer to the list of acceptable documents.

Responses

Callback
Language
Credentials
URL
LoadingLoading…
Response
Choose an example:
application/json