This endpoint is a flexible tool designed to collect additional information required for ad-hoc workflows, such as billing or regulatory reporting. The flexibility of the endpoint allows the payload format to be customized according to the specific use case, as agreed upon with the partner.
Key aspects:
Use Case Example: Regulatory Reporting in Argentina
A common use case for this endpoint is to collect information for regulatory reporting, such as meeting compliance requirements for Argentina’s Financial Information Unit (UIF). In this scenario, the required format for the info
field is as follows:
Field Descriptions:
condición_extranjero (boolean)
: Indicates if the person is a foreign resident (true
) or not (false
).cuit (string)
: Unique Tax Identification Code (Clave Única de Identificación Tributaria) of the person.apellidos (string)
: Last name(s) of the person.nombres (string)
: First name(s) of the person.tipo_documento (string)
: Type of document (DNI, PASAPORTE).num_documento (string)
: Document number.nacionalidad (string)
: Nationality of the person.fecha_nac (string)
: Date of birth in the format DD/MM/YYYY.fecha_alta (string)
: Registration date in the format DD/MM/YYYY
.fecha_baja (string | null)
: Deregistration date in the format DD/MM/YYYY
or null
if not applicable.es_pep (boolean)
: Indicates if the person is a Politically Exposed Person (true
or false
).B2B’s White Label API uses OAuth2. Currently there is only one supported authentication flow:
Every call to the API has to be authenticated with an OAuth2 Token. In order to request this token, you will need to have sandbox or production API Keys (client id and client secret) that will be needed to generate a credential in order to negotiate an ephemeral access token.
Every request must be accompianed by an Authorization
header with a value that follows the following schema: Bearer ACCESS_TOKEN
Successful response
The response is of type object
.