Skip to main content
Partner integration guide draft · English v1.0 · 20 October 2026 Distribution OS · Getting Started · Savings product guide Distribution OS connects every ARCO Savings product to partner applications, and this page covers them in one integration guide: Stablecoin Savings (sArcoUSD) and Crypto-native Savings for XRP, ETH and BTC, the Arco Saving Vault family. The Savings product guide defines each product’s treasury or strategy, valuation and risks; this page describes what a partner integrates and displays. The selected product’s deposit asset, strategy and payout asset remain separate integration fields. sArcoUSD belongs to Stablecoin Savings; crypto-native products use their own positions and valuation units.

​
Stablecoin Savings

Partners offer sArcoUSD, an ERC-4626 vault share over ArcoUSD, so their customers can earn the returns of the Arco-managed Savings treasury inside the partner’s own service. The Stablecoin Savings product guide defines the treasury, valuation and risks.

​
Product at a glance

​
Deposit flow

  1. The customer holds ArcoUSD, or holds a supported stablecoin (USDC, USDT or RLUSD) that is first converted into ArcoUSD on a 1:1 basis.
  2. The partner shows the current exchange rate and the expected sArcoUSD quantity.
  3. The customer or authorized signer approves ArcoUSD spending and signs the deposit.
  4. sArcoUSD is issued to the recipient at the exchange rate at deposit.
  5. The partner confirms the issued shares in the recipient’s wallet before showing the deposit as complete.
A partner can combine the stablecoin-to-ArcoUSD conversion and the Savings deposit into one customer screen. These remain two operations: each keeps its own quote, transaction and record.

​
Redemption flow

The T+1 objective describes capital recovery under the applicable day-count and cutoff rules. It is not a guaranteed payout time. A request receipt or share burn alone does not establish payment; show the redemption as complete only after the ArcoUSD reaches the recipient. To exit into a stablecoin, the customer redeems sArcoUSD into ArcoUSD, then redeems ArcoUSD. The ArcoUSD step is paid immediately from the ArcoUSD stablecoin reserve: USDC is paid 1:1 with no fee, and other supported stablecoins include a conversion fee shown in the quote. A combined withdrawal screen shows the amount and costs of each step and the final amount received.

​
Positions and returns

Display sArcoUSD holdings with the definitions in Positions & Performance. Show the current exchange rate and the applicable Savings rate separately from observed performance. A displayed or historical rate identifies its observation period, capital basis and cost treatment. It is not a fixed rate or a future payout commitment.

​
Interface notes

  • The product design specifies sArcoUSD as an ERC-4626 vault over ArcoUSD. The pinned public reference implementation described in the Integration Guide predates that design and uses separate deposit and redemption vaults. Use the sArcoUSD release specification for the actual interface.
  • Convert quantities to integers in each token’s smallest units. Do not use a rounded display value or a displayed exchange rate as a transaction argument.
  • Store the transaction and request identifiers for every deposit and redemption. After a timeout, resolve the original transaction or request before submitting another.

​
Risks to disclose

Dollar denomination does not guarantee principal, a fixed exchange rate or uninterrupted redemption. MMF settlement terms and the unborrowed liquidity of the Morpho markets can delay recovery for amounts above the liquidity reserve. Borrower behaviour, collateral price changes, liquidation performance or oracle failures in a Morpho market can reduce recovery. See Access & Risk and the Stablecoin Savings product guide.

​
Crypto-native Savings

Arco Saving Vault is Arco’s own strategy vault family for XRP, ETH and BTC. Partners integrate the selected vault’s investment exposure and transaction experience into their services through Distribution OS. The asset name identifies the product family. The individual vault’s specification defines how assets are received, deployed, valued and returned. An XRP or BTC product name does not imply native staking, and an ETH product need not be a staking-only strategy. The product guide describes the Crypto-native (Staking) and Crypto-native (Static Asset) categories.

​
Describe the complete product

Deposit and redemption networks are distinct from the networks used by the strategy. A native asset, a wrapped token and a custody balance are different representations; they must not be presented as interchangeable merely because they share an asset label.

​
Strategy and returns

Explain the selected strategy’s actual source of returns and risk using its product materials. Asset price appreciation, lending income, staking rewards and other strategy income have different meanings. Use only the sources that apply to the selected vault. An increase in USD value can reflect the underlying asset’s market price rather than an increase in asset quantity. Show the asset-based performance measure separately from currency valuation, and label historical performance, target returns and estimated annualized returns separately. Include the observation period and treatment of fees and incentives. The product’s return mechanism determines whether performance changes the position price, quantity, separately claimable rewards or distributions. Apply losses and costs on the same stated basis. Do not assume every vault rebases, compounds automatically or distributes rewards separately.

​
Deposits, redemptions and risk

Use the partner integration lifecycle to distinguish transaction preparation, authorization, funds confirmation, position allocation and payout. Determine completion from the selected route’s execution evidence. Strategy losses, asset price changes, counterparty exposure, asset representation, custody, operational permissions and liquidity constraints affect the product differently. Instant liquidity, principal protection and participation rights follow the product’s actual terms. See Access & Risk.

​
ETH staking product case

ETH Staking Vault applies the Arco Saving Vault design to GIWA deposits and share issuance with institutional validator operations on Ethereum. The GIWA vault and Ethereum allocation use MPC-based custody. Arco retains withdrawal and recovery authority within the custody and approval framework; the institutional operator also participates with Arco in the Security Council multisig for its assigned actions. Partners connect confirmed GIWA holdings, ETH share valuation and net APR separately from Council approval, custody execution, transfer, activation, recovery and payout status. The detailed Savings guide explains these product relationships, the Standard and Instant liquidity routes, and a hypothetical numerical example. Example amounts and rates must not be presented as actual product performance or quotes. The guide does not replace the product’s actual release interface or expand the pinned EVM examples to Ethereum staking operations.

​
Static Asset product case

Crypto-native (Static Asset) uses the MM-managed account model: vault capital is transferred to the market maker’s designated investment accounts under the management and capital-return arrangements. Arco connects confirmed shares, reconciled net assets and observed net performance to capital recovery and customer settlement. “Static” is a category name and does not establish a fixed price or yield. Partners display share allocation, MM receipt, valuation, return progress, vault receipt and customer payout as separate outcomes. A reported MM return is not automatically a share-price update, and a return instruction is not recovered capital. Vault custody controls and external MM permissions are identified separately; the ETH design’s MPC and Council arrangements do not automatically apply to this product. Its documentation does not establish a released execution API, provider, address or supported market.

​
Continue the integration