> ## Documentation Index
> Fetch the complete documentation index at: https://docs.arco.financial/llms.txt
> Use this file to discover all available pages before exploring further.

# Onboarding and Due Diligence

Mainnet product guide draft · English v1.0 · 7 October 2026

[Docs Home](/index)

Institutional partners review a product's rights, custody, pricing, liquidity and operating responsibilities before defining their participation or integration scope. This page sets out the status of product-specific due diligence materials, information to request, and the sequence for KYB, contracts, settlement and integration.

Product designs, official external product materials and public reference implementations are available below. Actual contracting entities, custody evidence, release-specific audits and mainnet deployment materials applicable to ARCO currently require product-specific confirmation and supporting links. Confirm each material's status and review scope before using it in institutional approval procedures.

## Products and Roles to Review

First select the product to review from ArcoUSD, Savings and Funds, and define the institution's role. Investment and holdings, external asset connections, liquidity provision, and app or API integration have distinct contractual and operating scopes. Where an institution performs several roles, its activities and approval scope are distinguished.

| Product family | Starting point for review | Product guide |
| - | - | - |
| ArcoUSD | Exchange of supported stablecoins, reserves and the party against which holders have claims, and withdrawal and liquidity conditions | [ArcoUSD](/products/arcousd) |
| Savings | Participating strategies, performance, losses and costs, product tokens, and redemption assets and rights | [Savings](/products/savings) |
| Funds | Exact underlying products and classes, external issuance, distribution, management and custody, and their connection to ARCO rights | [Funds](/products/funds) |

See Funds for the three existing DigiFT-linked products, eight products planned for onboarding, the parties' roles and official materials. A listing or external cooperation announcement does not replace an individual institution's participation approval or confirmation of an ARCO product's contracts, custody or deployment.

## Material Status and Links

The status below reflects the Docs as of 7 October 2026. A Docs publication date is distinct from a contract's effective date, a holdings reference date or a security review date.

| Material | Current status | Links and scope |
| - | - | - |
| Product structure and transaction flows | Design explanations available | [Product Guide](/index), [Deposits and Redemptions](/liquidity/deposits-and-redemptions), [Vault Liquidity Architecture](/liquidity/architecture) |
| Operating and legal standards | Common standards available | [Security and Operations](/security/operations), [Terms and Risks](/security/terms-and-risks), [NAV and Returns](/transparency/nav-and-returns) |
| External RWA products and parties | Official external materials linked | Product-specific official links in [Funds](/products/funds), applicable to the relevant external party and product |
| Public code and calls | Reference implementation available | [Integration Guide](/resources/developer-guide), [Smart Contracts and References](/resources/smart-contracts-and-references), [GitHub](https://github.com/LBMike/arco-giwa). Official mainnet deployment, ABI and scope require separate confirmation |
| ARCO product contracts and legal structure | Product-specific confirmation and supporting links required | Original URLs for valid contracts, terms and term sheets covering actual contracting entities, parties against which holders have claims, rights, jurisdictions and eligibility |
| Custody and asset reconciliation evidence | Product-specific confirmation and supporting links required | Custody provider, asset title, control and segregation evidence, and URLs for dated reports on assets, supply and unpaid obligations |
| Release deployment permissions and security review | Product-specific confirmation and supporting links required | Official deployment, implementation and permissions specifications, audit reports applicable to release code, and URLs for findings and remediation materials |
| Pricing liquidity and institutional onboarding specifications | Product-specific confirmation and supporting links required | Specification URLs covering pricing, fees, payout commitments, reserve policies, KYB, contracting and approval owners, and operating contact routes |

## Product Due Diligence Submission Fields

Each material records its product, network and class, actual responsible legal entities and roles, preparer and reviewer, reference date, version and effective date, update frequency and next review date, update owner and original URL. If an original has restricted access, its accessible scope and request route are provided. The preparation roles below identify responsibilities to assign; they do not state that a particular legal entity has already been assigned responsibility.

| Material package | Specific information to submit | Preparation roles and update responsibility |
| - | - | - |
| Review scope and contractual rights | Contracting entities, jurisdiction and user scope, party against which holders have claims, allocation of returns and losses, relationship between authoritative records and tokens, rights for incomplete purchases and payouts pending after burns, claims and returns on insolvency or termination, document precedence and originals | Product owner, contracting parties and legal roles. Actual entities, contacts, effective dates and responsibility for updates after changes require confirmation |
| Custody and fund control | Asset title, custody and settlement entities, control scope per account and wallet, contractual basis for separating customer and operating assets, movement approvals, return procedures and supporting materials | Custody and settlement providers and ARCO operations roles. Actual parties, evidence reference dates, update frequency and reviewers require confirmation |
| Valuation and pricing review | Underlying product, class and currency, valuation data provider and reference time, fee treatment, responsibilities for calculation, cross-checking and onchain publication, price error and data delay handling, and reports | Asset or strategy valuation providers and pricing review and publication roles. Actual owners, valuation frequency, approval records and update responsibility require confirmation |
| Liquidity and payout conditions | Standard price fixing, cutoffs, business days and payout commitments, internal available balances, reserved obligations and replenishment thresholds, OTC counterparties, limits, quotes, token handling and settlement methods, costs, net amounts received and exception handling | Operations, liquidity and settlement roles and contractual parties. Actual owners, condition effective dates and review frequency require confirmation |
| Deployment permissions and security review | Official deployment, implementation, ABI and code version, actual role-holding addresses, administrators and approval configuration, change and emergency controls, audit scope and exclusions, report dates, findings and remediation status | Technical and permissions operations roles and independent reviewers. Release version, actual settings, reviewers and responsibility for updates after changes require confirmation |
| Reconciliation of supply reserves and unpaid obligations | Issuance, burns and remaining supply at the same reference time, held assets, valuations and external custody materials, reserved payouts, pending redemptions, incomplete purchases, fund movements and payout results, differences, causes and resolution status. Distinguish held assets from committed OTC capacity, and remaining arcoUSD backing from completed Funds settlement | Issuance, custody and settlement record preparers and reconciliation reviewers. Actual preparers and reviewers, reference dates, reporting frequency and material URLs require confirmation |
| Participation and operating support | Scope of KYB, eligibility, sanctions and wallet registration, review and renewal parties, institutional approval, contracting and integration responsibilities, routine enquiries, incident notification, recovery and escalation routes | Product, onboarding, compliance, operations and institutional integration roles. Actual owners, contact routes, operating hours and update responsibility require confirmation |

ArcoUSD's T+0 to T+2 day reserve replenishment target, measured from the MMF recovery request date T, is a reserve operating target. It is not a payout commitment to an individual user or a redemption deadline for every product. Day-count conventions, external product business days and submission cutoffs, and applicable payout deadlines are defined in each product's specifications and contracts.

Due diligence materials distinguish statuses such as design or draft, product-specific confirmation and supporting links required, and confirmed materials available, alongside the scope of the originals. External underlying product materials and public code alone do not confirm custody, guarantees, audits or a mainnet launch for the entire ARCO product.

## Institutional Onboarding Stages

Define the responsible contacts, submission materials and approval conditions for the following stages according to the product and the institution's role. Technical application of KYB, settlement and integration is reviewed separately from actual checks and contractual approvals, within their respective responsibility scopes.

| Stage | Matters to agree | Record passed to the next stage |
| - | - | - |
| Product and role selection | Product and class, institutional jurisdiction and user scope, and investment, asset connection, liquidity or app integration roles | Review scope and requested materials |
| KYB and participation review | Applicable entity, beneficial owner, eligibility, sanctions and wallet reviews, material submission routes, and review and renewal responsibilities | Product-specific review results, restrictions and outstanding conditions |
| Rights and contract confirmation | Contracting parties, rights, custody, costs, redemptions and losses, document precedence and responsibility allocation | Valid originals, term sheets and institutional approval records |
| Settlement and integration preparation | Payout assets, recipients and settlement verification, pricing, liquidity and exception handling, official deployment and ABI, and scope of connection to institutional services | Settlement and integration specifications, applied permissions and verification results |
| Availability conditions and operational handover | Participation, contractual, settlement and integration conditions, initial availability scope, treatment of outstanding items, and owners of regular reporting and incident response | Availability decision and scope, contact routes, reporting frequency and change records |

Actual product-specific procedures and approving parties are confirmed in the onboarding specification. App listings and address allowlisting alone are not treated as completion of KYB or legal eligibility review.

## Material Requests and Enquiries

Send the target product, institutional role, requested material packages and required review reference date through the partner contact already in discussions with ARCO. Requests may also cover product-specific original URLs and access scope, preparation owners and schedules for unconfirmed items, and follow-up contact routes.

Official enquiry, material submission and incident notification routes are recorded during onboarding with each contact's name, organization, responsibilities, contact method, operating hours and escalation owner. This page does not list unconfirmed email addresses, telephone numbers or submission portals.

## Related Guides

* [Security and Operations](/security/operations)

* [Terms and Risks](/security/terms-and-risks)

* [Funds](/products/funds)

* [Integration Guide](/resources/developer-guide)

* [Smart Contracts and References](/resources/smart-contracts-and-references)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.