> ## 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.

# Deposits and Redemptions

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

[Docs Home](/index)

In ARCO, users select a product, deposit the specified asset or make a purchase, and hold the corresponding product token. ArcoUSD connects supported stablecoins through exchange on a 1:1 basis, Savings provides participation in return-generating strategies, and Funds connects purchases and settlement of external assets. This guide explains what users should check, from preparing to participate through receiving and holding product tokens to redemption payment.

Before starting, review the key conditions for [ArcoUSD](/products/arcousd), [Savings](/products/savings), and [Funds](/products/funds). Even when products use the same payment asset, the token received, price fixing time, fees, and asset recovery schedule vary by product.

## Steps

| Step | What the user should check |
| - | - |
| 1. Select a product | Compare the purpose, deposit asset, token received, and possibility of loss in the product page's key conditions. |
| 2. Prepare to participate | Check the product's eligibility requirements and required procedures, then verify the supported network, assets, and official addresses. |
| 3. Deposit or purchase | Check the expected token quantity, costs, and price fixing time. Distinguish asset spending approval from the actual deposit or purchase. |
| 4. Hold | Check token quantity and valuation separately, together with the price update time and applicable costs. |
| 5. Redeem and receive payment | Compare the payment asset, Standard and Instant conditions, and net amount received. Follow acceptance through to actual payment. |

## Participation flow by product

| Product | Deposit or purchase | Receipt and valuation |
| - | - | - |
| [ArcoUSD](/products/arcousd) | Deposit supported stablecoins | arcoUSD on a 1:1 basis under normal exchange conditions |
| [Savings](/products/savings) | Deposit arcoUSD or the relevant crypto-native asset | sarcoUSD or the asset-specific Savings product token, under its pricing and performance rules |
| [Funds](/products/funds) | Receive and burn arcoUSD, then use treasury reserves for external purchases and settlement | The product token linked to the relevant RWA and the associated contractual rights |

For Funds, burning, reserve movements, purchase settlement, and product receipt are recorded as separate stages. Follow the Funds guide for the detailed flow of funds and conditions for handling incomplete purchases.

## Select a product and prepare to participate

When selecting a product, review its investment exposure, manager, eligibility requirements, and redemption methods together. Products using the same payment asset may have different investment exposures and asset recovery schedules. Complete the procedures required by the product's participation conditions, then connect an EVM wallet supporting GIWA.

The wallet is the address that sends the payment asset and receives the ProductToken. Connecting a wallet does not make a deposit. Asset spending approval and the deposit transaction must each be reviewed and signed. Transactions require network fees.

## Deposits and product token issuance

Enter the payment amount on the deposit or purchase screen to review the expected tokens received and costs. ArcoUSD applies a 1:1 basis for supported assets under normal exchange conditions. Products valued by price use the ratio between the payment asset price and product price. Funds external purchases also display the relevant product's price fixing and settlement conditions.

### Internal instant deposit steps

1. Check the selected product's payment asset and deposit amount.

2. Approve payment asset spending for the official deposit address shown on the product screen.

3. Check the expected issued quantity and recipient address, then sign the deposit transaction.

4. After a successful transaction, check the product token balance in the receiving wallet.

An instant deposit transfers the payment asset and issues ProductTokens in a single transaction. When the vault's execution conditions are met, the payment asset moves to the DepositVault and ProductTokens are issued to the recipient. If the transaction fails, its asset transfer and token issuance are also not completed. Asset spending approval is a separate procedure from the deposit transaction.

## Holdings and valuation

Product tokens are ERC20 tokens representing the quantity held. Once participation is complete, they are held in the user's wallet and burned in direct redemptions. In acquisition-based OTC transactions, the tokens are transferred to the partner. Token transfers and use are subject to the product's participation and transfer policies and operating status. Product agreements define holder rights and the relationship with external tokens or fund interests.

Distinguish token quantity from each product's exchange or valuation basis. General arcoUSD uses a dollar exchange basis. Products valued by price, such as sarcoUSD and Funds, display value by applying the relevant price to the quantity held. Products that reflect performance and costs in their price do not automatically increase the token quantity.

Deposit assets and redemption payment liquidity are managed separately. Instant Redemption uses available assets in the internal sleeve or executable quotes from the OTC Network. Standard Redemption follows the product's asset recovery and settlement schedule. See [Vault Liquidity Architecture](/liquidity/architecture) for each route's conditions.

## Choose a redemption route

On the redemption screen, check the product token quantity to withdraw, payment asset, price, fees, and net amount received. Compare Standard and Instant. For Instant, check the availability conditions for internal direct redemption or OTC settlement.

| Route | Token treatment and payment | Next checks |
| - | - | - |
| Internal direct Instant Redemption | Burn and payment using a valid price and internal liquidity | Successful transaction and actual receipt |
| Instant through the OTC Network | Token acquisition and transfer, or redemption settlement, based on a quote | Execution terms, token treatment, and actual payment |
| Standard Redemption | Product-specific asset recovery, settlement, token treatment, and payment after acceptance | Price fixing, request status, and payment completion |

## Instant Redemption

Direct redemption through the Internal Liquidity Sleeve is available when internal payment balances, pricing, and transaction conditions are valid. The user reviews the quantity, payment asset, fees, and net amount received, then signs the transaction. A successful internal direct redemption burns product tokens and pays the payment asset together.

The payment amount for internal direct redemption is calculated from the valid exchange or valuation basis at execution and the applicable fees. Deposit balances are distinguished from balances available for payment, with redemption limits and reserved payments taken into account.

When using the OTC Network, check the liquidity partner's firm quote, fees, and payment timing. Acquisition-based transactions transfer tokens to the partner. Liquidity provision involving burning connects through a separate redemption settlement process. Show withdrawal as complete when the actual asset payment to the user is verified.

## Standard Redemption

Standard Redemption separates acceptance from payment. Record the request identifier, recipient, quantity, and price fixing status, then recover and settle assets under the product's conditions before payment. The timing of token locking, transfer, or burning follows the relevant contract and interface. Quantities already burned are not included in the balance still held.

When the price is fixed at the request, the payment amount is determined on that basis. When settlement valuation applies, disclose the relevant fixing time and conditions. Operators prepare payment assets according to recorded outstanding obligations and the product's recovery and settlement process.

Cancellation, return, and any required reissuance conditions are set by product. A completed burn record is not reversed. Separate asset or token handling is linked to the required approvals and records. Before requesting redemption, check the product's redemption conditions, price fixing rules, and payment schedule.

| State | Meaning | Display criteria |
| - | - | - |
| Request accepted | Quantity, recipient, pricing, and token treatment status are recorded | Request identifier, recipient, and expected or fixed payment amount |
| Payment in progress | Asset recovery, settlement, payment preparation, or claim procedures are underway | Request status and payment instructions |
| Payment completed | The relevant asset has been paid to the receiving wallet | Payment transaction and actual receipt |

Depending on the product's payment process, payment is made by an operator or claimed by the designated recipient. When a claim is required, the recipient submits a claim transaction from their wallet using the provided procedure. Completion of the request transaction and completion of actual payment are verified as separate stages.

## Verify payment completion

Internal direct redemption is complete after verifying the successful redemption transaction and receipt of the payment asset. For OTC, verify the agreed execution, token treatment, and actual payment. Standard is complete only after verifying the payment transaction and receipt following acceptance. Link request and execution identifiers and transaction history to user support inquiries and settlement records.

Transaction history distinguishes completed deposits, accepted redemption requests, payments in progress, and completed payments. Partner interfaces apply the same distinction and let users follow their requests through to receipt.

## When processing is pending or withdrawal is unavailable

| Observed status | Next action |
| - | - |
| Only asset spending approval is complete | Approval is not deposit completion. Check whether the actual deposit transaction was submitted. |
| A transaction was submitted but its outcome is not yet confirmed | Query the network outcome using the existing transaction identifier. Do not submit the same deposit, purchase, or redemption again before resolving its outcome. |
| Internal Instant Redemption is unavailable | Check liquidity, pricing, limits, and operating status. Compare the conditions of available OTC quotes or the Standard route. |
| A Standard request has been accepted | Check the request identifier, price fixing status, expected schedule, and whether a claim is required. Acceptance alone does not mean payment is complete. |
| OTC execution is complete but payment is not yet verified | Check the quote's payment timing and token treatment status. Keep the transaction incomplete until actual receipt is verified. |
| The stated payment schedule has passed or the amount received differs | Use the product's designated support channel to request a status check on the existing request. Cancellation, return, and reissuance follow that product's conditions. |

For a status inquiry, provide the product name, network, request or quote identifier, transaction hash, recipient address, time, displayed status, expected amount, and actual amount received. Partners use this information to locate the corresponding transaction records.

## Frequently asked questions

### Does connecting a wallet or approving asset spending complete a deposit?

Wallet connection and asset spending approval are preparation steps. Verify that the actual deposit transaction succeeded and the product tokens reached the receiving wallet. For Funds, verify external purchase and settlement and receipt of the relevant product tokens separately.

### Are all products withdrawn in the same asset?

The payment asset varies by product and redemption route. For stablecoin Savings, distinguish redemption of sarcoUSD from exchange of arcoUSD into a supported stablecoin. For Funds and crypto-native Savings, check the product's payment asset and settlement conditions.

### Is Instant Redemption always available?

Internal direct redemption is available when payment liquidity, valid pricing, limits, and operating conditions are met. OTC requires an executable quote and execution and payment conditions. Check available routes and fees before requesting redemption.

### Why have I not received assets after my Standard request completed?

Completion of the request transaction may mean only that redemption was accepted. Asset recovery, settlement, payment preparation, or a recipient claim may still be required, so check the request state and payment transaction. Quantities already burned are linked to outstanding requests separately from the holding balance.

### What price applies to a Standard request?

Distinguish products that fix the price at the request from those that fix the valuation price at settlement. The price fixing time shown on the request screen and in the product specification is the basis. The estimated amount at acceptance is not always the final payment amount.

### Can I cancel a request or change the recipient address?

Availability of cancellation, address changes, and returns depends on the product's conditions and request state. Do not submit a duplicate new request before checking support for the action. Completed burn records are not reversed. Any required return or reissuance uses separate processing and records.

## Product-specific conditions

The relevant product specification defines product-specific values, processing and settlement cycles, valuation sources and price feeds, fees and how they are charged, and redemption deadlines.

## Related guides

* [Funds product lineup](/products/funds)

* [NAV and Returns](/transparency/nav-and-returns)

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

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


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