> ## 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. # Savings Partner integration guide draft · English v1.0 · 20 October 2026 [Distribution OS](/distribution-os/overview) · [Getting Started](/distribution-os/getting-started) · [Savings product guide](/products/savings) 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](/products/savings) defines each product's treasury or strategy, valuation and risks; this page describes what a partner integrates and displays. | | [Stablecoin Savings](#stablecoin-savings) | [Crypto-native Savings](#crypto-native-savings) | | - | - | - | | Deposit asset | ArcoUSD on GIWA | XRP, ETH or BTC, in the representation the vault specifies | | Position | sArcoUSD, an ERC-4626 vault share | The vault's own share or position | | Return basis | Per-second accrual through the exchange rate to ArcoUSD | Measured in the vault's reference asset, defined per vault | | Redemption asset | ArcoUSD | Defined per vault | | Liquidity | 10% liquidity reserve for immediate redemption; capital recovery for larger amounts | Defined per vault, including network withdrawal or exit queues where applicable | 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](/products/savings/stablecoin) defines the treasury, valuation and risks. ### Product at a glance | Integration field | Stablecoin Savings | | - | - | | Deposit asset | ArcoUSD on GIWA. The vault accepts ArcoUSD only. | | Position received | sArcoUSD, an ERC-4626 vault share | | Return treatment | Returns accrue per second through the sArcoUSD exchange rate to ArcoUSD. The share count does not change; losses and costs are also reflected in the exchange rate. | | Valuation basis | Net assets attributable to sArcoUSD holders ÷ sArcoUSD shares outstanding, in ArcoUSD | | Treasury | MMFs (largest allocation), an Arco-curated Morpho vault supplying crypto-backed and RWA-backed lending markets (smaller than the MMF allocation), and a 10% liquidity reserve | | Redemption asset | ArcoUSD, paid to the recipient's wallet | | Liquidity | Redemptions within the 10% liquidity reserve are paid immediately. Larger amounts follow capital recovery, with a T+1 recovery objective. | | Payout | Automatic. There is no claim step. | | Customer information | Deposits through ARCO vaults do not require the partner to submit customer identification information. | | Costs | Fees and minimums are supplied in the offering terms. Any applicable fee is shown in the quote. | ### Deposit flow 1. The customer holds ArcoUSD, or holds a supported stablecoin (USDC, USDT or RLUSD) that is first converted into [ArcoUSD](/products/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 | Route | When it applies | What happens | Completion evidence | | - | - | - | - | | Immediate | The amount is covered by the 10% liquidity reserve | sArcoUSD is burned and ArcoUSD is paid to the recipient in the same transaction | Successful transaction, share burn and ArcoUSD receipt | | Standard | The amount exceeds the available liquidity reserve | The request is recorded; ArcoUSD is paid to the recipient automatically once the required assets are recovered, with a T+1 recovery objective | The payout transaction and ArcoUSD receipt | 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](/transparency/nav-and-returns#partner-positions-and-performance). | Display item | How to derive it | | - | - | | Confirmed holding | sArcoUSD shares held by the recipient, read from the token balance | | Holding value | Shares × the current exchange rate, shown with the rate's reference time, in ArcoUSD | | Redemption in progress | Shares burned for a Standard request and the ArcoUSD owed; do not also count them as a holding | | Confirmed payout | ArcoUSD actually received for a completed redemption | 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](/resources/developer-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](/security/terms-and-risks#partner-access-and-product-eligibility) and the [Stablecoin Savings product guide](/products/savings/stablecoin#liquidity-eligibility-and-risk). ## 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)](/products/savings/staking) and [Crypto-native (Static Asset)](/products/savings/static-asset) categories. ### Describe the complete product | Product dimension | What the partner displays or verifies | | - | - | | Deposit asset | The accepted asset, its native, wrapped or custody representation, units and deposit network | | Strategy exposure | The assets and activities used by the Arco strategy, its objectives, counterparties and constraints | | Performance basis | Whether returns are measured in XRP, ETH, BTC or another reference asset, with a separate currency valuation where applicable | | Redemption asset | The asset and representation paid to the customer, payout network and recipient requirements | | Position | The token or account record the customer receives, and the rights it represents | | Return treatment | How gains, losses and costs affect NAV, share price, balances, rewards or distributions under that vault’s terms | | Liquidity | The offered redemption routes, price fixing point, limits and recovery or settlement conditions | | Access and authority | Investor and partner conditions, custody arrangements, and who approves, signs and operates each step | 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](/liquidity/deposits-and-redemptions#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](/security/terms-and-risks#partner-access-and-product-eligibility). ### ETH staking product case [ETH Staking Vault](/products/savings/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](/products/savings/eth-staking-vault#illustrative-example-deposit-to-redemption). 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)](/products/savings/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 * [Getting Started](/distribution-os/getting-started) * [Deposits & Redemptions](/liquidity/deposits-and-redemptions#partner-integration-lifecycle) * [Positions & Performance](/transparency/nav-and-returns#partner-positions-and-performance) * [Vault Liquidity Architecture](/liquidity/architecture) This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.