KYC Document Submission API

This endpoint is intended for submitting documents for KYC verification processes handled by our Compliance team.

Document Submission

To submit a compliance document, you need to send a POST request to the following endpoint:

POST /api/v1/kyc/document
Host: binance.latamgateway.com
Content-Type: "multipart/form-data"
ACCOUNT_TOKEN: "<token>"

Request Format (multipart/form-data)

customer_name: "John Doe"
customer_document: "12345678901"
file: [binary file content of encrypted document]
file_document_number: "-----BEGIN PGP MESSAGE-----\n...encrypted content...\n-----END PGP MESSAGE-----"
file_expiration_date: "2025-12-31T23:59:59Z"
file_type: "DRIVER_LICENSE"

Note: The ACCOUNT_TOKEN is generated in the Authentication EP.

Params descriptions

Field	Description	Value Type	Requirement
customer_name	Customer’s full name	String	Required
customer_document	Customer’s document number	String	Required
file	Encrypted document file (PGP)	File (binary)	Required
file_document_number	Encrypted file document number (PGP)	String (PGP)	Required
file_expiration_date	Expiration date of the document	ISO 8601 String	Optional
file_type	Type of file being submitted	String (CPF, CNPJ, RG, DRIVER_LICENSE, INCOME_PROOF, ADDRESS_PROOF,SELFIE, SALES_RECEIPT.)	Required

Note: Encrypted fields must follow the PGP protocol, using RSA 2048 and AES-256 algorithms. The public key can be obtained from your account manager.

A successful request HTTP 200 status code, the response will include the following parameters:

{
  "message": "Document received successfully.",
  "document_id": "doc-12345"
}

Business errors due to incorrect or missing parameters are returned with an HTTP 400 status code. The response will indicate which parameter is invalid or missing.

{
  "message": "The 'customer_document' field is required."
}

Encryption errors are returned an HTTP 400 status code along with the following parameters:

{
  "message": "Decryption failed. An error occurred during the cryptographic process. Please verify that your encrypted data is correctly formatted and try again."
}