Onboarding a company
Onboarding a company
Open a Broker account for a company (a legal entity / persona jurídica) instead of an individual. The flow uses the same endpoints as an individual user, with three differences: the company's data replaces the individual fields, the company uploads its corporate documents instead of a DNI and a selfie, and Manteca compliance reviews those documents before the account is enabled.
Available for Argentine companies identified by theirCUIT. AlegalIdthat starts with3(30,33,34) is onboarded as a company, withtype: "BUSINESS"; any otherlegalIdis onboarded as an individual.
Flow
- Create the user with
POST /broker/v1/api/onboarding/initial, sending the company'sCUITaslegalId, its data inpersonalData(see Company data), its legal representative and at least one bank account inbanking.accounts. - Complete the company data. Part of it is retrieved from AFIP with the
CUIT(see Data auto-population). If something is still missing,GET /broker/v1/api/onboarding/status/USERANYIDlists it, and you complete it withPUT /broker/v1/api/compliance/person/{legalId}. - Upload the company documents: articles of incorporation, appointment of authorities, shareholding structure and financial statement (see Upload company documents).
- Manteca compliance reviews the documents and approves the company. The user moves to
VALIDATEDand Manteca registers it with the market (custody, clearing, order routing and back office). - Once those registrations finish, the user moves to
ACTIVEand can operate.
flowchart LR A[EMAIL_VALIDATED] --> B[PERSONAL_DATA_COMPLETE] --> C[USER_DATA_COMPLETE] --> D[VALIDATED] --> E[ACTIVE] D -->|external step failed| F[ONBOARDING_FAILED]
A company never goes through VALIDATING or VALIDATION_FAILED: those statuses belong to the DNI check of an individual. While compliance reviews the documents, the company stays in USER_DATA_COMPLETE.
Company data
For a company, personalData carries the corporate data instead of the individual fields:
| Field | Required | Description |
|---|---|---|
name | From AFIP | Legal name (razón social). |
birthDate | From AFIP | Incorporation date (fecha del contrato social), ISO 8601. |
address | From AFIP | Registered address: street, numeration, postalCode, locality, province (floor optional). |
taxType | From AFIP | Tax category, same values as for individuals. |
earningType | From AFIP | How the company's earnings are taxed. Affects the fees applied to its orders. |
phoneNumber | Yes | Company contact phone. AFIP does not return it. |
businessType | Yes | Legal form: LIMITED_LIABILITY (SRL), PUBLIC_LIMITED (SA) or SIMPLIFIED_JOINT_STOCK (SAS). |
businessSize | Yes | Size bracket: MICRO, SMALL, MEDIUM or LARGE. |
capital | Yes | Declared share capital, as a numeric string (for example "1500000"). |
legalRepresentative | Yes | The person who acts for the company. See Legal representative. |
investorExperience | Yes | Declared experience with financial instruments, same values as for individuals. |
investorType | Yes | Investor profile, from the investor quiz. |
isPep, isFatca, isUif | No | Declarations, false when omitted. pepData is required when isPep is true. |
"From AFIP" means you do not need to send the field when AFIP returns it; send it to fill what AFIP leaves empty. The individual-only fields (surname, sex, maritalStatus, work) do not apply to a company and can be omitted.
The request is rejected with 400 when businessType, businessSize, capital, legalRepresentative, investorExperience or investorType is missing for a company legalId.
Legal representative
legalRepresentative identifies the natural person who acts on behalf of the company:
| Field | Description |
|---|---|
legalId | Representative's CUIT or CUIL. |
email | Representative's contact email. |
phoneNumber | Representative's contact phone. |
The representative is declared, not onboarded: it is not a user of its own and it does not upload identity documents.
Request example
curl -X POST https://sandbox.manteca.dev/broker/v1/api/onboarding/initial \
-H "md-api-key: $MD_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"email": "[email protected]",
"legalId": "30712345678",
"externalId": "company-001",
"personalData": {
"phoneNumber": "1145678900",
"businessType": "PUBLIC_LIMITED",
"businessSize": "SMALL",
"capital": "1500000",
"legalRepresentative": {
"legalId": "20123456789",
"email": "[email protected]",
"phoneNumber": "1123456789"
},
"investorExperience": "Buena",
"investorType": "Moderado",
"isPep": false,
"isFatca": false,
"isUif": false
},
"banking": {
"accounts": [
{ "cbu": "0000003100012345678901", "currency": "ARS", "description": "Cuenta corriente ARS" }
]
}
}'name, birthDate, address, taxType and earningType are not sent here because AFIP returns them for this CUIT.
The response has the same shape as for an individual, with user.type set to BUSINESS:
{
"user": {
"id": "6596e960e140a030749b4e23",
"companyId": "658dd9502accccd05acc3ce9",
"legalId": "30712345678",
"numberId": "10417",
"email": "[email protected]",
"type": "BUSINESS",
"status": "EMAIL_VALIDATED",
"banking": {
"accounts": [
{
"cbu": "0000003100012345678901",
"currency": "ARS",
"description": "Cuenta corriente ARS",
"bank": { "code": "031", "name": "Banco Ejemplo" },
"virtual": false
}
]
},
"externalId": "company-001",
"creationTime": "2026-10-27T14:22:40.166-03:00"
},
"person": {
"legalId": "30712345678",
"email": "[email protected]",
"personalData": {
"name": "EMPRESA EJEMPLO S.A.",
"birthDate": "2015-06-10T00:00:00.000Z",
"address": {
"street": "AV CORRIENTES",
"numeration": "1234",
"floor": "",
"postalCode": "1043",
"locality": "CIUDAD AUTONOMA BUENOS AIRES",
"province": "Capital Federal"
},
"taxType": "Responsable inscripto",
"earningType": "Inscripto",
"phoneNumber": "1145678900",
"nationality": "Argentina",
"businessType": "PUBLIC_LIMITED",
"businessSize": "SMALL",
"capital": "1500000",
"legalRepresentative": {
"legalId": "20123456789",
"email": "[email protected]",
"phoneNumber": "1123456789"
},
"investorExperience": "Buena",
"investorType": "Moderado"
},
"flags": { "isPEP": false, "isFATCA": false, "isUIF": false, "isOCDE": false }
},
"causedConflict": false
}Store the numberId: it is the associatedSubId of every document you upload for the company.
Data auto-population
When the user is created, Manteca queries AFIP with the CUIT and takes the legal name, incorporation date, registered address, tax category and earnings type from it. AFIP data takes precedence: a value you send for one of those fields is used only when AFIP leaves it empty.
If AFIP is unavailable or does not return a field, the company stays in EMAIL_VALIDATED and GET /broker/v1/api/onboarding/status/USERANYID lists the missing fields under MISSING_PERSONAL_DATA. Complete them with PUT /broker/v1/api/compliance/person/{legalId}, sending only the fields to change in personalData. As soon as the data is complete the company advances to USER_DATA_COMPLETE (or PERSONAL_DATA_COMPLETE if it still has no bank account).
Upload company documents
Each document is uploaded in two steps: request a pre-signed URL with POST /broker/v1/api/compliance/documentation/uploadUrl, then PUT the file binary to that URL (see Operating model for the two-step mechanics). Upload them against the company: associatedId is the company CUIT and associatedSubId its numberId.
docType | Document |
|---|---|
BYLAWS | Articles of incorporation (estatuto social / contrato social). |
AUTHORITIES | Minutes appointing the current authorities (acta de designación de autoridades). |
STAKEHOLDERS | Shareholding structure (composición societaria). |
BALANCE | Latest financial statement (último balance). |
curl -X POST https://sandbox.manteca.dev/broker/v1/api/compliance/documentation/uploadUrl \
-H "md-api-key: $MD_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"associatedId": "30712345678",
"associatedSubId": "10417",
"fileName": "estatuto.pdf",
"docType": "BYLAWS",
"externalId": "company-001-bylaws"
}'- Company documents are not limited to image formats: a PDF is accepted. The
.jpg/.jpeg/.png/.webprestriction applies only to DNI images. - Only one document per
docTypecan be under review or approved at a time. A second upload returns409 DOCUMENTATION_PENDINGwhile the first is under review, and409 DOCUMENTATION_EXISTSonce it is approved. - Each document reports its result with the
documentation-status-updatewebhook:PENDINGon upload, thenVALIDATEDorREJECTED. You can also read them withGET /broker/v1/api/compliance/documentation, filtering byassociatedIdanddocType. - If a document is
REJECTED, request a new upload URL for the samedocTypeand upload the corrected file.
The company does not upload DNI_FRONT, DNI_BACK or SELFIE, and neither does its legal representative.
A proof of source of funds (FUNDS) works the same as for an individual: it is not part of the onboarding and raises the company's deposit ceiling once validated. See Operating model → Deposit limits and source of funds.
Compliance review and activation
Manteca compliance reviews the company documents. The review is not a step you trigger: once the documents are uploaded, the company waits in USER_DATA_COMPLETE until compliance approves it, and then:
- The user moves to
VALIDATEDand Manteca registers the company with the market. - When every registration finishes, the user moves to
ACTIVE. - If a registration fails, the user moves to
ONBOARDING_FAILEDand Manteca has to intervene.
Each change is reported with the user-status-update webhook. The company can operate only when it is ACTIVE.
Checking onboarding status
GET /broker/v1/api/onboarding/status/USERANYID returns the pending steps for the company, using its numberId, its externalId or its user id. For a company the response never includes the DNI steps (AWAITING_DNI_UPLOAD, DNI_UPLOADED, DNI_VERIFIED, DNI_VERIFICATION_FAILED).
[
{
"code": "MISSING_PERSONAL_DATA",
"message": "needs to modify person with missing data",
"fields": ["personalData.businessType", "personalData.legalRepresentative.legalId"]
},
{
"code": "ARS_BANKING_COMPLETED",
"message": "ARS banking info complete, USD account is optional but required for some operations",
"fields": ["banking.accounts.USD"]
}
]The compliance review does not appear as a step: while it is pending, the response shows only the banking step. Use the user status (USER_DATA_COMPLETE while under review) and the documentation-status-update webhook to know where the company stands.
Operating as a company
Once ACTIVE, a company operates through the same endpoints as an individual, with these differences:
- Dólar MEP caps. USD bought through Dólar MEP counts against a cap of USD 6,000,000 per month and USD 50,000,000 per year per company. Purchases still in progress count too. A purchase that would exceed a cap is rejected at creation with
403 PERSON_MONTHLY_OPERATION_LIMITor403 PERSON_YEARLY_OPERATION_LIMIT.GET /broker/v1/api/compliance/person/{legalId}/limitsreturns the caps in force (monthlyLimit,yearLimit) and what was bought in the current month and year (monthlyOperated,yearlyOperated), all in USD. Manteca can raise the caps for a specific company. - Dólar MEP waiting window. Between buying the bond in ARS and selling it in USD, a company waits one business day more than an individual. The synthetic shows
WAITINGmeanwhile and resumes by itself. - Deposit ceiling. Same as an individual:
govLimit + verifiedLimit, see Operating model. - Deposits must come from a bank account owned by the company (same
CUIT).
Related
Updated 22 days ago