Create Wallet User

Registers a user for the wallet (virtual account) flow with a minimal flat body. Background compliance checks run asynchronously.

Recent Requests
Log in to see full request history
TimeStatusUser Agent
Retrieving recent requests…
LoadingLoading…

Email validation

email must be printable ASCII across the whole address — local part and domain. Unicode look-alike characters (e.g. Cyrillic а for Latin a) and invisible control characters are rejected, even when the rest of the address is otherwise valid, because they would let two visually identical addresses create two different users.

A rejected email returns a 400 with correctPattern: [email protected]:

{
  "internalStatus": "BAD_REQUEST",
  "message": "Bad request.",
  "errors": [
    "email has wrong value john@gmаil.com. Value should be [email protected]."
  ]
}

If both email and phoneNumber are sent and the email fails this check, the request is rejected outright — it does not fall back to registering the user with just the phone number.

Body Params

Which fields are required depends on type. Always required: legalId, legalIdNationality, and at least one contact — email or phoneNumber (sending both is allowed). For an INDIVIDUAL user, name and surname are also required. For a BUSINESS user, omit name/surname — the company name is carried by personalData.legalName, and personalData, shareholders and beneficiaries are required instead.

string
Defaults to ext-123

Your own identifier for the user (optional, for idempotency).

string
^[\x21-\x7E]+$
Defaults to [email protected]

Contact email. Required unless phoneNumber is sent — at least one of the two is required, for both INDIVIDUAL and BUSINESS users. Only printable ASCII characters are accepted, across the whole address (local part and domain) — an address containing Unicode or control characters is rejected with a 400, even if otherwise RFC-valid. If both email and phoneNumber are sent and the email fails this check, the request is rejected outright rather than silently falling back to phoneNumber.

string
Defaults to Jorge

First name. Required for INDIVIDUAL users. Omit for BUSINESS — the company name goes in personalData.legalName.

string
Defaults to Ramirez

Last name. Required for INDIVIDUAL users. Omit for BUSINESS — the company name goes in personalData.legalName.

string
required
Defaults to 20-41565338-8

Legal identifier of the user. When a validator exists for the nationality (ARGENTINA, CHILE, BRAZIL, MEXICO, PANAMA, COLOMBIA, COSTA_RICA, GUATEMALA, PHILIPPINES, BOLIVIA, PERU, PARAGUAY) the value is regex-checked; otherwise it is accepted as opaque text.

string
Defaults to CUIT

Free-text document type (e.g. CUIT, DNI, PASSPORT, RFC, CEDULA, NIE). Forwarded verbatim to compliance; unrecognised values are accepted without error and stored generically. Optional.

string
enum
required
Defaults to ARGENTINA

Country that issued the legalId. Determines which exchange the user is created on — ARGENTINA → ARGENTINA; countries without a dedicated regional exchange fall back to GLOBAL.

documents
object

Identity document files (selfie, ID front, ID back) required by some jurisdictions when operating above AML thresholds. Files must be pre-uploaded to Manteca's S3 bucket. Max 20 MB per file (JPEG or PDF).

string
enum

User type. Defaults to INDIVIDUAL. Set BUSINESS to onboard a company (Brazil / CNPJ); this requires personalData, shareholders and beneficiaries. For a BUSINESS user, legalId is the company CNPJ and the company name lives in personalData.legalName (not the top-level name/surname).

Allowed:
string

Contact phone. Required unless email is sent — at least one of the two is required, for both INDIVIDUAL and BUSINESS users.

address
object

INDIVIDUAL only. Optional at signup, but needed before the user can be activated for a virtual account. Send it here, or later with POST /wallet/v1/onboarding-actions/define-personal-data. If you send it, street, numeration, postalCode, locality and province must all be present; floor and apartment are optional and accept "".

string

INDIVIDUAL only. The person's nationality — any nationality is accepted, not just the country that issued the legalId. Do not confuse it with legalIdNationality, which is the issuing country of the document. Optional at signup, but needed before the user can be activated for a virtual account; send it here or later with POST /wallet/v1/onboarding-actions/define-personal-data.

date

INDIVIDUAL only. Date of birth in YYYY-MM-DD format. Optional at signup, but required before the user can be activated for a virtual account; send it here or later with POST /wallet/v1/onboarding-actions/define-personal-data.

boolean

Optional. Declares whether the user is a Politically Exposed Person. true is trusted as confirmed immediately — the PEP documentation task is raised right away, without waiting for our own screening. true is sticky: it is never reverted by a later screening result. false does not exempt the user from screening — it behaves exactly as if the field were omitted.

boolean

Optional. Declares whether the user is a Politically/Financially Exposed Person under FEP rules. Same asymmetric semantics as isPep: true is trusted immediately and raises the FEP documentation task right away, without waiting for screening, and is never reverted by a later screening result. false does not exempt the user from screening.

personalData
object

BUSINESS only. Corporate data for the company. Most fields are auto-populated from the CNPJ — send one only to override. Registry codes (cnae, legalNatureCode, stateRegistration) are always derived from the CNPJ and are NOT part of the payload.

shareholders
array of objects

BUSINESS only. Ownership structure (quadro de sócios). At least one shareholder is required and the sum of participationPercentage must not exceed 100.

shareholders
beneficiaries
array of objects

BUSINESS only. Legal representatives — the natural persons who act for the company. Each is created as its own user and completes a full identity verification. The link to the shareholders they act for is resolved automatically when a single representative is declared; see the shareholder representedBy field otherwise.

beneficiaries
Headers
string
Responses

Language
Credentials
Header
URL
LoadingLoading…
Response
Click Try It! to start a request and see the response here! Or choose an example:
application/json