Skip to main content
GET
Retrieve KYC Requirements
KYC requirements are determined by the country your account is configured for — you do not need to filter by country, the response is already scoped to it. For example, an account operating in Argentina returns the fields and document types required by Argentine regulations, while a Brazil account additionally requires the net_income field (income bracket).For every field returned as a CHOICE, submit the exact value from choices, never the label: MX.JA for Jalisco, BR.SP for São Paulo, AR.A for an income bracket. Labels are rejected. See KYC fields by country for what each field means and how it is validated.
requiredIf — a field required only for certain values of another field. Entries in kycRequiredFields may carry a requiredIf object naming the field they depend on and the values that make them required. Today it appears on Argentina’s personal_activity_other:
The key is additive — a parser that ignores it still works — but a form built only on required will let the customer submit without a field the API then rejects.
Two fields are validated but not published in kycRequiredFields, so read their accepted values here rather than from the response: id_number_type for Argentina (DNI, R_P, OTHER; optional, defaults to DNI) and for Mexico (not used — the document is always a CURP).For Mexico, address_photo is published as required but is only enforced for accounts configured for the Ripio-provider widget flow.For Argentina, net_income and personal_activity are published as required but a payload that omits them is still accepted today, so that integrations already live are not turned away. Build the form as if they were required — that is the regulatory intent and the API will start refusing payloads without them. When the value is present it is validated against the catalog either way.
nationality carries its own catalog. It is returned as a CHOICE with every accepted ISO 3166-1 alpha-2 code, so a form built from this response cannot offer one of the codes the identity provider refuses. Mexico’s birthday_place — the country of birth — carries the same catalog.
For Brazil, identity documents (ID front/back and selfie) are collected through the KYC provider’s document-upload flow, not submitted as inline base64 fields in the KYC request.

Authorizations

Authorization
string
header
required

Access token obtained via /oauth2/token/. Use as Authorization: Bearer <access_token>.

Response

Successfully retrieved KYC requirements.

kycRequiredFields
object[]
required