Account holder onboarding

account_holder is the onboarding type for opening a client Entity as an account holder. After Fintoc approves the review, the Entity can own Account objects. This page documents the schema you send in data when you create an account_holder onboarding and the document slots the onboarding opens, for each country. For the end-to-end flow, from creating the Entity to submitting for review, follow Onboard an entity by API. This page covers only what is specific to the account_holder type.

Availabilityaccount_holder supports companies in Chile and Mexico. The Entity’s country_code selects the schema: see Chile or Mexico. Creating an account_holder onboarding for an Entity in any other country returns 422 Unprocessable Entity with the code country_not_supported. An Entity whose holder_id identifies an individual returns 422 Unprocessable Entity with the code holder_type_not_supported.

The request shape

Send type and data at the top level of the create request. The keys inside data depend on the country, and every key is required:

{
  "type": "account_holder",
  "data": {
    "company_basics": { },
    "company_information": { },
    "senior_management": { "senior_management": [ ] },
    "legal_representatives": [ ],
    "shareholders": [ ],
    "transactional_profile": { },
    "plaft": { }
  }
}

{
  "type": "account_holder",
  "data": {
    "company_information": { },
    "legal_representatives": [ ],
    "transactional_profile": { },
    "shareholders": [ ]
  }
}

The API reference describes data as a free-form object, because its shape depends on type and on the country; this page is the schema for account_holder.

Validation errors

A request with invalid data returns 400 Bad Request with a single error, even when several fields fail. Fix the reported field and resend to find the next one. param names the failing field with its full path, using a dot for each nested key and brackets for each array index, such as legal_representatives[0].email. Some errors carry a code:

`code`	Cause
`invalid_enum`	A value outside the accepted list. The error lists the accepted values.
`invalid_rut`	A Chilean tax ID (RUT) that fails validation. Chile only.
`invalid_shareholder_structure`	A shareholder tree that breaks a structure rule. The `reason` field names the rule.
`missing_parameter`	A required field that the request omits.

Other validation failures, such as an empty legal_representatives array, return 400 Bad Request with param set to the failing field and no code.

Chile

A Chilean account_holder onboarding sends seven blocks in data: company_basics, company_information, senior_management, legal_representatives, shareholders, transactional_profile, and plaft. Fintoc’s compliance team reviews the documents and answers described in Know Your Customer (KYC) requirements in Chile.

company_basics

How the company was incorporated and the name it trades under:

Field	Type	Required	Description
`fantasy_name`	string	Optional	Trading name of the company. Accepts `null`. In `test` mode, this field also selects the simulated review outcome. See Force a review outcome.
`incorporation_type`	string	Required	Incorporation method. One of `one_day_company` (registered through Empresa en un Día) or `traditional` (incorporated before a notary). Selects the company document slots.

When incorporation_type is one_day_company, Fintoc verifies at submission that the company’s RUT is registered as an Empresa en un Día company. If the company is not, submitting returns 422 Unprocessable Entity with the code not_one_day_company.

company_information

The company’s activity, legal structure, and addresses. Every field is required:

Field	Type	Required	Description
`activities_start_date`	string	Required	Date the company started activities before the Chilean Internal Revenue Service (SII), as an ISO 8601 date such as `2019-03-01`.
`business_activity_code`	string	Required	Six-digit economic activity code from the SII catalog, such as `620200`. A code outside the catalog returns `invalid_enum`.
`business_address`	string	Required	Physical address where the company operates.
`company_type`	string	Required	Legal structure of the company. One of `colectiva` (Sociedad Colectiva), `eirl` (Empresa Individual de Responsabilidad Limitada), `en_comandita` (Sociedad en Comandita), `ltda` (Sociedad de Responsabilidad Limitada), `sa` (Sociedad Anónima), or `spa` (Sociedad por Acciones).
`fiscal_address`	string	Required	Address registered with the SII.

senior_management

The company’s senior management. senior_management is an object with a single key, also named senior_management, that holds an array of members. Declare at least one member. Every field is required for every member:

Field	Type	Required	Description
`identification_number`	string	Required	Identification number of the member. Must be a valid RUT when `nationality` is `cl`; otherwise returns `invalid_rut`.
`name`	string	Required	Full name of the member.
`nationality`	string	Required	Two-letter ISO 3166-1 alpha-2 country code of the member’s nationality, in either case. The response returns the value in lowercase.
`position`	string	Required	Position the member holds in the company, such as `Gerente General`.

An empty array returns 400 Bad Request with param set to senior_management.senior_management.

legal_representatives

The people authorized to act for the company. Declare at least one. Fintoc enforces no maximum:

Field	Type	Required	Description
`email`	string	Required	Email address of the legal representative, in RFC 5322 format.
`first_name`	string	Required	Given name of the legal representative.
`identification_number`	string	Required	Individual RUT for a Chilean national, or passport number for a foreign national. A company RUT returns `invalid_rut` when `nationality` is `cl`. Must be unique within the onboarding.
`last_name`	string	Required	Family name of the legal representative.
`nationality`	string	Required	Two-letter ISO 3166-1 alpha-2 country code of the legal representative’s nationality, in either case. The response returns the value in lowercase.
`phone`	string	Optional	Contact phone number in E.164 format, such as `+56911111111`. Accepts `null`.
`position`	string	Optional	Role the legal representative holds in the company. The response returns `null` when you omit it.

An empty array returns 400 Bad Request with param set to legal_representatives. Two legal representatives with the same identification_number return 400 Bad Request with param set to the second entry, such as legal_representatives[1].identification_number.

shareholders

The company’s ownership tree. Declare at least one shareholder; an empty array returns invalid_shareholder_structure with reason set to shareholders_required. Every node in the tree, at the root and at any depth, takes these fields:

Field	Type	Required	Description
`address`	string	Required	Address of the shareholder.
`children`	array of shareholder	Optional, `legal_entity` only	Shareholders that own this shareholder. Send this only when `type` is `legal_entity`.
`effective_controller`	boolean	Required	If `true`, the shareholder is an effective controller of the company. Send a JSON boolean.
`fiscal_address`	string	Required	Address of the shareholder registered with the SII.
`holder_id`	string	Required	Identification number of the shareholder. Must be a valid RUT when `nationality` is `cl`; otherwise returns `invalid_rut`.
`last_name`	string	Optional, `natural_person` only	Family name of the shareholder. Send this only when `type` is `natural_person`. Sending it for a `legal_entity` returns `invalid_shareholder_structure` with `reason` set to `invalid_name`.
`name`	string	Required	Given name when `type` is `natural_person`, or business name when `type` is `legal_entity`.
`nationality`	string	Required	Two-letter ISO 3166-1 alpha-2 country code of the shareholder’s nationality.
`percentage`	number	Required	Participation the shareholder holds, from `0` to `100`. Send a JSON number; the API rejects a numeric string.
`type`	string	Required	Kind of shareholder. One of `natural_person` or `legal_entity`.

Four rules constrain the tree. Each structure error returns the code invalid_shareholder_structure, with reason set to the value in parentheses:

Each level sums to 100 or less. Chile sets no minimum sum. A level above 100 fails (shareholder_participation_exceeded).
Only a legal_entity nests. A natural_person carrying children fails (only_legal_entity_can_nest). Fintoc sets no limit on nesting depth.
Each holder_id is unique within its level. Two shareholders at the root, or under the same parent, with the same holder_id fail (duplicate_shareholder). The same holder_id can appear at different levels.
At least one effective controller. Fintoc checks this rule when you submit, not when you create the onboarding. With no shareholder set to effective_controller: true, submitting returns 422 Unprocessable Entity with the code effective_controller_required.

transactional_profile

The sources of the company’s equity and funds, and how the company uses Fintoc. Every field is required, and each one is an array that takes at least one value:

Field	Type	Required	Description
`business_relationship_purposes`	array of string	Required	Ways the company uses Fintoc. Values in the table below.
`equity_origins`	array of string	Required	Sources of the company’s equity. Values in the table below.
`resource_origins`	array of string	Required	Sources of the funds the company moves through Fintoc. Values in the table below.

business_relationship_purposes accepts these values:

`business_relationship_purposes` value	Purpose
`customer_collections`	Collect payments from customers.
`customer_payouts`	Pay out funds to customers.
`payroll_payments`	Pay salaries.
`supplier_payments`	Pay suppliers.
`tax_payments`	Pay taxes.
`treasury_management`	Manage the company’s treasury.

equity_origins accepts these values:

`equity_origins` value	Source of equity
`asset_sales`	Proceeds from selling assets.
`capital_contributions`	Capital contributed by the partners.
`external_financing`	Financing from banks or third parties.
`inheritance_or_donations`	Inheritances or donations.
`investment_returns`	Returns on investments.
`retained_earnings`	Retained earnings.

resource_origins accepts these values:

`resource_origins` value	Source of funds
`asset_sales`	Proceeds from selling assets.
`capital_contributions`	Capital contributions.
`donations_or_subsidies`	Donations or subsidies.
`external_financing`	Financing from banks or third parties.
`investment_returns`	Returns on investments.
`operating_income`	Operating income of the company.

A value outside these lists, including a Mexican value such as trusts, returns invalid_enum.

plaft

The company’s declaration on anti-money laundering and terrorist financing prevention (PLAFT):

Field	Type	Required	Description
`uaf_obligated`	boolean	Required	If `true`, the company must report to Chile’s Financial Analysis Unit (UAF), and the onboarding requires the `uaf_registration_certificate` and `plaft_manual_and_policies` slots.

Chilean document slots

Creating the onboarding opens every company slot that company_basics.incorporation_type selects, each one reporting missing until you upload a file. The maximum file size is 20 MB for every slot. Fintoc reads the content type of a company slot from the file bytes, and every company slot accepts application/pdf only. The top-level documents array lists these company slots:

`slot_key`	Opens when	Required to submit	Files	Document
`activities_start_certificate`	`incorporation_type` is `traditional`	Yes	One	SII certificate of commencement of activities.
`current_shareholders_certificate`	`incorporation_type` is `one_day_company`	Yes	One	Current shareholders certificate from the Registro de Empresas y Sociedades.
`e_rut`	Always	Yes	One	Company electronic RUT card (e-RUT) issued by the SII.
`good_standing_certificate`	`incorporation_type` is `traditional`	Yes	One	Certificate of good standing with marginal annotations, issued within the last 90 days.
`incorporation_amendments`	Always	No	Multiple	Amendment deeds and their Diario Oficial publications.
`incorporation_deed`	Always	Yes	One	Public deed of incorporation.
`plaft_manual_and_policies`	Always	If `uaf_obligated` is `true`	Multiple	Anti-money laundering prevention manual and policies.
`power_of_attorney`	Always	No	One	Certificate of authority (personería) stating the legal representatives’ powers.
`uaf_registration_certificate`	Always	If `uaf_obligated` is `true`	One	UAF registration certificate.

Each legal representative gets its own documents array with two slots. Fintoc checks the part’s declared Content-Type for these slots, so send it as one of the accepted types:

`slot_key`	Accepted content types
`identification_back`	`application/pdf`, `image/jpeg`, `image/png`
`identification_front`	`application/pdf`, `image/jpeg`, `image/png`

Chilean shareholders have no document slot. Each shareholder returns document set to null. A traditional company with uaf_obligated set to false and one legal representative needs six files to submit: e_rut, activities_start_certificate, good_standing_certificate, incorporation_deed, and the two identification sides.

Chilean example

This payload declares one legal representative, one senior manager, and two root shareholders. One root shareholder nests a third shareholder. Every value is test data that belongs to no real company or person.

{
  "type": "account_holder",
  "data": {
    "company_basics": {
      "incorporation_type": "traditional",
      "fantasy_name": "Test Company"
    },
    "company_information": {
      "activities_start_date": "2019-03-01",
      "business_activity_code": "620200",
      "company_type": "spa",
      "business_address": "Av. Apoquindo 100, Santiago",
      "fiscal_address": "Av. Apoquindo 100, Santiago"
    },
    "senior_management": {
      "senior_management": [
        {
          "name": "Test Customer 1",
          "nationality": "cl",
          "identification_number": "11.111.111-1",
          "position": "Gerente General"
        }
      ]
    },
    "legal_representatives": [
      {
        "first_name": "Test Customer 1",
        "last_name": "Customer",
        "email": "jon@snow.com",
        "nationality": "cl",
        "identification_number": "11.111.111-1",
        "position": "Representante legal",
        "phone": "+56911111111"
      }
    ],
    "shareholders": [
      {
        "type": "natural_person",
        "name": "Test Customer 1",
        "last_name": "Customer",
        "holder_id": "11.111.111-1",
        "nationality": "cl",
        "percentage": 60,
        "address": "Av. Apoquindo 100, Santiago",
        "fiscal_address": "Av. Apoquindo 100, Santiago",
        "effective_controller": true
      },
      {
        "type": "legal_entity",
        "name": "Test Entity 2",
        "holder_id": "88.888.888-8",
        "nationality": "cl",
        "percentage": 40,
        "address": "Av. Apoquindo 100, Santiago",
        "fiscal_address": "Av. Apoquindo 100, Santiago",
        "effective_controller": false,
        "children": [
          {
            "type": "natural_person",
            "name": "Test Customer 2",
            "last_name": "Customer",
            "holder_id": "22.222.222-2",
            "nationality": "cl",
            "percentage": 100,
            "address": "Av. Apoquindo 100, Santiago",
            "fiscal_address": "Av. Apoquindo 100, Santiago",
            "effective_controller": false
          }
        ]
      }
    ],
    "transactional_profile": {
      "equity_origins": ["capital_contributions"],
      "business_relationship_purposes": ["customer_collections", "supplier_payments"],
      "resource_origins": ["operating_income"]
    },
    "plaft": {
      "uaf_obligated": false
    }
  }
}

Mexico

A Mexican account_holder onboarding sends four blocks in data: company_information, legal_representatives, transactional_profile, and shareholders. Fintoc’s compliance team reviews the documents and answers described in KYC requirements in Mexico.

company_information

The company’s identity and settlement details. Every field is required:

Field	Type	Required	Description
`business_activity`	string	Required	Primary business activity of the company. In `test` mode, this field also selects the simulated review outcome. See Force a review outcome.
`business_address`	string	Required	Physical address where the company operates.
`fiscal_address`	string	Required	Address registered with the Mexican tax authority.
`incorporation_date`	string	Required	Date the company was incorporated, as an ISO 8601 date. The response returns this value as an ISO 8601 datetime in UTC.
`phone`	string	Required	Contact phone number in E.164 format: a leading `+` followed by 8 to 15 digits, the first of which cannot be `0`.
`sector`	string	Required	Industry the company operates in. Values in the table below.
`settlement_account`	string	Required	Account that receives settlements, as an 18-digit standardized Mexican bank account number (CLABE).

sector accepts these values:

`sector` value	Industry
`betting_gaming`	Betting and gaming.
`cross_border_payments`	Cross-border payments.
`direct_sales`	Direct sales.
`ecommerce`	E-commerce.
`education`	Education.
`insurance`	Insurance.
`lending`	Lending.
`other`	Any other industry.
`property_management`	Property management.
`psps`	Payment service providers.
`subscription_businesses`	Subscription businesses.
`telecommunications`	Telecommunications.
`ticketing`	Ticketing.
`utilities`	Utilities.
`wallets_neobanks`	Digital wallets and neobanks.

CLABE validation differs by modesettlement_account must have 18 digits. Fintoc accepts the value when the first three digits match a supported Mexican institution and the CLABE control digit checks out. Fintoc also accepts its own CLABEs and skips the control digit for them. In test mode, this applies to sandbox bank codes. In live mode, this applies to Fintoc’s own bank code. A CLABE at a supported Mexican institution behaves the same in both modes. A sandbox CLABE that works in test returns an error in live. An invalid value returns 400 Bad Request with param set to company_information.settlement_account.

legal_representatives

The people authorized to act for the company. Declare at least one. Fintoc enforces no maximum, and every field is required for every entry:

Field	Type	Required	Description
`email`	string	Required	Email address of the legal representative, in RFC 5322 format.
`first_name`	string	Required	Given name of the legal representative.
`identification_number`	string	Required	Mexican Unique Population Registry Code (CURP) of the legal representative.
`last_name`	string	Required	Family name of the legal representative.
`nationality`	string	Required	Two-letter ISO 3166-1 alpha-2 country code of the legal representative’s nationality, in either case. The response returns the value in lowercase.
`position`	string	Required	Role the legal representative holds in the company, such as `Director General`.

An empty array returns 400 Bad Request with param set to legal_representatives. An invalid entry returns param with the index of the failing entry, such as legal_representatives[0].email.

transactional_profile

The volume, the source, and the purpose of the money the Entity expects to move:

Field	Type	Required	Description
`account_purpose`	string	Required	Main use of the account. Values in the table below.
`account_purpose_details`	string	Required if `account_purpose` is `other`	Description of how the company uses the account. Omitting it when `account_purpose` is `other` returns `400 Bad Request` with `param` set to `transactional_profile.account_purpose_details`.
`monthly_amount_range`	string	Required	Expected monthly transacted amount in Mexican pesos (MXN). One of `1_2000000` for up to 2,000,000, `2000001_10000000` for 2,000,001 to 10,000,000, or `gt_10000000` for more than 10,000,000.
`monthly_operations_range`	string	Required	Expected monthly number of operations. One of `1_15000` for 1 to 15,000, `15001_50000` for 15,001 to 50,000, or `gte_50001` for 50,001 or more.
`resource_origins`	array of string	Required	Where the money the `Entity` moves comes from. Send at least one value from the list below.

Former monthly_amount_range valuesFintoc still accepts the former values 1_500000, 500001_1000000, and gt_1000000, which counted amounts in US dollars. Fintoc maps 1_500000 to 2000001_10000000; it maps both 500001_1000000 and gt_1000000 to gt_10000000. The response returns the converted value. Send the MXN values in new integrations.

account_purpose accepts these values:

`account_purpose` value	Main use of the account
`betting_gaming`	Run a betting, raffle, lottery, or similar gaming business.
`collection_and_dispersion`	Collect payments for your own products or services, and pay suppliers, contractors, or payroll.
`marketplace`	Collect from buyers and settle to sellers or service providers, as a marketplace or platform.
`other`	Any other use. Describe it in `account_purpose_details`.
`own_sales_collection`	Collect payments for your own products or services.
`psp_aggregator`	Process payments on behalf of other merchants, as an aggregator, payment service provider, or payment gateway.
`third_party_dispersion`	Disburse third-party funds to people or companies, such as loans, prizes, commissions, or refunds.

resource_origins accepts these values:

`resource_origins` value	Source of funds
`asset_sales`	Proceeds from selling assets.
`budget_allocations`	Budget assigned by another organization.
`donations`	Donations received.
`investments`	Returns on investments.
`profits`	Operating profits of the company.
`royalties`	Royalty payments.
`sales_income`	Sales or income from the business activity.
`trusts`	Distributions from a trust.

The response echoes transactional_profile with declaration_accepted set to true, which Fintoc adds when it creates the onboarding. Do not send declaration_accepted; the API ignores it.

shareholders

Field	Type	Required	Description
`children`	array of shareholder	Optional, `legal_entity` only	Shareholders that own this shareholder. Send this only when `type` is `legal_entity`.
`holder_id`	string	Required	Mexican tax ID (RFC) of the shareholder.
`last_name`	string	Optional, `natural_person` only	Family name of the shareholder. Send this only when `type` is `natural_person`. Sending it for a `legal_entity` returns `invalid_shareholder_structure` with `reason` set to `invalid_name`.
`name`	string	Required	Given name when `type` is `natural_person`, or business name when `type` is `legal_entity`.
`nationality`	string	Required	Two-letter ISO 3166-1 alpha-2 country code of the shareholder’s nationality, in either case.
`percentage`	number	Required	Participation the shareholder holds, from `0` to `100`. Send a JSON number; the API rejects a numeric string.
`type`	string	Required	Kind of shareholder. One of `natural_person` or `legal_entity`.

Two rules constrain the tree. Each structure error returns the code invalid_shareholder_structure, with reason set to the value in parentheses:

The root sums to between 76 and 100. The root percentages must sum to at least 76 (participation_below_threshold) and at most 100 (shareholder_participation_exceeded). Each children array must sum to 100 or less, with no minimum.
Only a legal_entity nests. A natural_person carrying children fails (only_legal_entity_can_nest). A legal_entity with no children is valid. Fintoc sets no limit on nesting depth.

Mexican document slots

Creating the onboarding opens every slot the type requires, each one reporting missing until you upload a file. Every slot is required before you can submit. The maximum file size is 20 MB for every slot. For company slots and shareholder documents, Fintoc reads the content type from the file bytes. The content type your upload declares does not matter. The two legal representative slots check both values. Send the part’s Content-Type as one of the accepted types for that slot, because Fintoc rejects the upload before it inspects the bytes. The onboarding opens five company slots, listed in the top-level documents array:

`slot_key`	Accepted content types
`articles_of_incorporation`	`application/pdf`
`proof_of_address`	`application/pdf`, `image/jpeg`, `image/png`
`settlement_bank_statement`	`application/pdf`
`shareholder_structure`	`application/pdf`
`tax_registration_certificate`	`application/pdf`

Each legal representative gets its own documents array with two slots:

`slot_key`	Accepted content types
`identification`	`application/pdf`, `image/jpeg`, `image/png`
`power_of_attorney`	`application/pdf`

Each shareholder gets a single document object rather than an array, because a shareholder holds exactly one document. Fintoc picks the slot from the shareholder’s type, so the upload path carries no slot_key:

Shareholder `type`	`slot_key`	Accepted content types
`legal_entity`	`articles_of_incorporation`	`application/pdf`, `image/jpeg`, `image/png`
`natural_person`	`identification`	`application/pdf`, `image/jpeg`, `image/png`

A company with one legal representative and three shareholders therefore opens ten slots: five company slots, two for the representative, and one per shareholder. Every Mexican account_holder slot accepts a single file, so uploading again with PUT replaces the existing file. Each uploaded entry in the top-level documents array carries an id that you can pass to DELETE .../documents/{slot_key}/{document_id} to remove the file. See Manage files in a slot.

Mexican example

This payload declares one legal representative and two root shareholders. One root shareholder nests a third shareholder. Every value is test data that belongs to no real company or person. The settlement_account is a documented test CLABE. Fintoc accepts it because its bank code and control digit are valid. An all-zeros CLABE returns 400 Bad Request, because 000 is not a supported bank code.

{
  "type": "account_holder",
  "data": {
    "company_information": {
      "business_activity": "Servicios financieros",
      "sector": "ecommerce",
      "business_address": "Av. Insurgentes 456, CDMX",
      "fiscal_address": "Av. Reforma 123, CDMX",
      "incorporation_date": "2020-01-15",
      "phone": "+521111111111",
      "settlement_account": "646969000000000000"
    },
    "legal_representatives": [
      {
        "first_name": "Test Customer 1",
        "last_name": "Customer",
        "email": "rep@example.com",
        "nationality": "mx",
        "identification_number": "AAAA010101HDFAAA01",
        "position": "Director General"
      }
    ],
    "transactional_profile": {
      "resource_origins": ["trusts", "investments"],
      "monthly_amount_range": "1_2000000",
      "monthly_operations_range": "1_15000",
      "account_purpose": "own_sales_collection"
    },
    "shareholders": [
      {
        "type": "natural_person",
        "name": "Test Customer 2",
        "last_name": "Customer",
        "holder_id": "AAAA010101AAA",
        "nationality": "mx",
        "percentage": 60
      },
      {
        "type": "legal_entity",
        "name": "Test Entity 2",
        "holder_id": "AAA010101AAA",
        "nationality": "mx",
        "percentage": 40,
        "children": [
          {
            "type": "natural_person",
            "name": "Test Customer 3",
            "last_name": "Customer",
            "holder_id": "AAAA010101AAA",
            "nationality": "mx",
            "percentage": 80
          }
        ]
      }
    ]
  }
}

What’s next

Onboard an entity by API for the full flow, including the uploads, the submission, and the review.
KYC requirements in Chile and KYC requirements in Mexico for the documents Fintoc’s compliance team reviews.
The Onboarding object for the response attributes.

Home

Resources

Payments

Business Accounts

Movements

Skeleton group medium 9

Account holder onboarding

The request shape

Validation errors

Chile

company_basics

company_information

senior_management

legal_representatives

shareholders

transactional_profile

plaft

Chilean document slots

Chilean example

Mexico

company_information

legal_representatives

transactional_profile

shareholders

Mexican document slots

Mexican example

What’s next

Home

Resources

Payments

Business Accounts

Movements

Skeleton group medium 9

​The request shape

​Validation errors

​Chile

​company_basics

​company_information

​senior_management

​legal_representatives

​shareholders

​transactional_profile

​plaft

​Chilean document slots

​Chilean example

​Mexico

​company_information

​legal_representatives

​transactional_profile

​shareholders

​Mexican document slots

​Mexican example

​What’s next

The request shape

Validation errors

Chile

company_basics

company_information

senior_management

legal_representatives

shareholders

transactional_profile

plaft

Chilean document slots

Chilean example

Mexico

company_information

legal_representatives

transactional_profile

shareholders

Mexican document slots

Mexican example

What’s next