Overview
In Manteca's B2B platform, user onboarding serves as the foundational layer of the system. To complete onboarding, users can follow one of two integration paths: an API-based approach that allows full control over each step of the process, or a pre-built onboarding widget that can be embedded into your product with minimal implementation effort. Some services do not require a separate onboarding flow; for example, QR payment services can be used by providing the required user information directly in the payment endpoint, without creating a standalone user beforehand.
The onboarding state of a user is defined by two core fields:
-
Status: Indicates the current phase of the user's onboarding process. It can be set to
ONBOARDINGwhen the user is still completing the required steps,ACTIVEwhen onboarding is complete and the user can access production features, orINACTIVEwhen the account is blocked. -
Onboarding tasks: A list of tasks assigned based on the user's country. Each task includes a required flag (to indicate if it's mandatory for activation) and a status that reflects its progress —
PENDING,IN_PROGRESS,COMPLETED,FAILED, orEXPIRED. When a task is rejected (e.g., due to a missing or unacceptable document), the status is set toFAILEDand arejectionReasonfield provides additional context. Common rejection reasons include: blurry or unreadable photo, expired document, data mismatch between document and declared identity, or unsupported document type. To resolve a failed task, re-upload the correct documentation — the task will transition back toIN_PROGRESS.EXPIREDindicates a previously completed task that requires renewal.As long as the user's status is
ONBOARDING, the platform restricts access to core functionality. The system uses the task list to track progress and determine when the user becomes eligible for activation. Once every requiredONBOARDING_TASKis completed, the user is automatically set toACTIVE.
flowchart LR A[ONBOARDING] -->|Onboarding tasks completed| B[ACTIVE] A -->|Onboarding failed or rejected| C[INACTIVE]
Broker onboarding runs on a separate API surface (https://api.manteca.dev/broker, endpoints under /v1/api/...). A user is created with their personal data and bank accounts, optionally uploads identity documentation, and is registered against the market infrastructure before they can operate.
The user's progress is tracked by a single status field:
EMAIL_VALIDATED— user just created; more personal data required.PERSONAL_DATA_COMPLETE— personal data complete; banking information required.USER_DATA_COMPLETE— personal and banking data complete; identity documents required.VALIDATING— documents uploaded; data under validation.VALIDATION_FAILED— identity/document validation failed; re-upload required.VALIDATED— validation passed; registration against external systems (e.g. Caja de Valores) in progress.ONBOARDING_FAILED— an external onboarding step failed; requires manual intervention by Manteca.ACTIVE— validated and onboarded across all systems; ready to operate.BLOCKED/INACTIVE— user blocked or deactivated.
flowchart LR A[EMAIL_VALIDATED] --> B[PERSONAL_DATA_COMPLETE] --> C[USER_DATA_COMPLETE] --> D[VALIDATING] --> E[VALIDATED] --> F[ACTIVE] D -->|rejected| G[VALIDATION_FAILED] E -->|external step failed| H[ONBOARDING_FAILED]
Identity documentation depends on the entity type — individuals upload DNI_FRONT, DNI_BACK, and SELFIE; companies upload BYLAWS, AUTHORITIES, STAKEHOLDERS, and BALANCE (see Onboarding a company). Compliance is enforced at the person (tax ID) level — see Operating model.
Continue with Create user (Broker tab) for the step-by-step flow.
Onboarding tasks
Onboarding tasks define the compliance checks and data validations needed for a user to reach ACTIVE status.
Some tasks are not always required and depend on specific user conditions.
Manual tasks (require API calls)
| Task | Description | Always required |
|---|---|---|
| IDENTITY_DECLARATION | Declaration of the user's legalId. Required to initiate onboarding and validate the user's tax identity. | ✓ |
| BASIC_PERSONAL_DATA_DEFINITION | Definition of the user's personal information, including name, gender, phone number, and other relevant personal data. | ✓ |
| BANK_ACCOUNT_DEFINITION | Definition of the user's bank accounts. This information may be preloaded from the initial endpoint and is not always required. | — |
| PEP_DOCUMENTATION_VALIDATION | Additional documentation required for users identified as Politically Exposed Persons (PEP). Not required if the user is not classified as PEP. This task is triggered automatically when the user is flagged as PEP during identity validation. Once the required sworn declaration is uploaded and approved, any operations held pending compliance review are released automatically. | — |
| FEP_DOCUMENTATION_VALIDATION | Documentation required for users classified as obligated subjects under UIF regulations. | — |
| IDENTITY_VALIDATION | Identity verification using images of the national ID (front and back). Usually automatic once images are uploaded and validated. Not always required. | — |
| SELFIE_VALIDATION | Selfie captured for biometric identity matching, uploaded alongside the identity document. Not always required. | — |
| BASIC_PERSONAL_DATA_DEFINITION_VA | Brazil only. Completed once the user's personal data includes everything the liveness check needs. Required before the liveness check, not to become ACTIVE. See Brazil requirements. | — |
| EXTERNAL_LIVENESS_VALIDATION | Brazil only. Liveness check the user completes through the link returned by POST /crypto/v2/onboarding-actions/perform-external-liveness. Optional: the user becomes ACTIVE without it. | — |
Automatic tasks (no intervention required)
Some tasks you may see are automatic and don't need any intervention to be completed. You may need to wait for the process to finish if they are still on pending.
| Task | Description | Always required |
|---|---|---|
| POLITICAL_CONSTRAINTS_VALIDATION | Automatic validation to determine whether the user is classified as a Politically Exposed Person (PEP). | ✓ |
| SECURITY_VALIDATION | Compliance and security checks against sanctions lists, watchlists, and other regulated sources. | ✓ |
Next step
Ready to onboard your first user? Continue with Create user for the step-by-step flow, or review Country requirements to confirm the payload expected for your jurisdiction.
Updated 16 days ago