> ## Documentation Index > Fetch the complete documentation index at: https://docs.digitalasset.com/llms.txt > Use this file to discover all available pages before exploring further. # Integration & APIs Applications (such as wallet providers and exchanges) can integrate and interact with the xReserve solution and/or USDCx via API. There are three options for supporting USDCx on the Canton Network: 1. **Transfer & hold USDCx** - Since USDCx is a token standard [CIP-56](https://github.com/global-synchronizer-foundation/cips/blob/main/cip-0056/cip-0056.md) compliant asset then as such any wallet that supports the token standard will have built in support for transfers and holding. See the [Token Standard](#token_standard) section below. 2. **Support xReserve deposits and withdrawals** - Custom API integration is required for applications to support xReserve deposits and withdrawals to and from their parties using the [xReserve UI](https://digital-asset.github.io/xreserve-deposits/). Instructions for doing this are included in the section [Supporting xReserve Deposits and Withdrawals](#support_deposits_withdrawals) below. 3. **Integrating the xReserve UI (Ethereum) into the wallet** - To enable a full end-to-end experience for the user, a wallet can integrate against Ethereum directly for deposits on top of integrating point 2. To provide an example for doing this, the [xReserve UI](https://digital-asset.github.io/xreserve-deposits/) as well as [open-sourced example scripts](https://github.com/digital-asset/xreserve-deposits) are available for reference. This demonstrates the two Ethereum transactions that must be submitted to an Ethereum node: * Approve a USDC spending allowance. * Call `depositToRemote` to deposit USDC into the xReserve contract. ## Supporting xReserve Deposits and Withdrawals The required dar file can be found [here](/usdcx-xreserve/technical-setup#dar-file). There are 3 choices (API calls) a wallet will need to implement in order to fully support the xReserve: ### Onboarding To use the xReserve a party will first need to onboard to the bridge using the below: Example API call: ```json theme={null} { "CreateCommand": { "templateId": "#utility-bridge-v0:Utility.Bridge.V0.Agreement.User:BridgeUserAgreementRequest", "createArguments": { "crossChainRepresentative": "${ADMIN_PARTY_ID}", "operator": "${UTILITY_OPERATOR_PARTY_ID}", "bridgeOperator": "${BRIDGE_OPERATOR_PARTY_ID}", "user": "${USER_PARTY_ID}", "instrumentId": { "admin": "${ADMIN_PARTY_ID}", "id": "USDCx" }, "preApproval": false } } } ``` ### Mint Once a user deposits USDC into ethereum a DepositAttestation is created on the Canton network. In order for the recipient party to claim those funds they will need to call a choice to mint from the DepositAttestation: \#utility-bridge-v0:Utility.Bridge.V0.Attestation.Deposit:DepositAttestation Example API call: ```json theme={null} { "commands": [ { "ExerciseCommand": { "templateId": "#utility-bridge-v0:Utility.Bridge.V0.Agreement.User:BridgeUserAgreement", "contractId": "${BRIDGE_USER_AGREEMENT_CONTRACT_ID}", "choice": "BridgeUserAgreement_Mint", "choiceArgument": { "depositAttestationCid": "${DEPOSIT_ATTESTATION_CID}", "factoryCid": "${FACTORY_CID}", "contextContractIds": "${CONTEXT_CONTRACT_IDS}" } } } ], "disclosedContracts": "${DISCLOSED_CONTRACTS}" } ``` ### Withdraw To withdraw from the Canton Network to Ethereum a user must burn the USDCx on Canton. Specifying the: * destination domain id: Currently only Ethereum is supported (domain id of 0). * Amount: In Decimal to a max 6 decimal precision. * Destination recipient: a valid Ethereum address. * An optional reference. Empty Text field if not provided. In addition the wallet will need to provide: * The available Holding contract Ids * A UUID as the requestId Example API call: ```json theme={null} { "commands": [ { "ExerciseCommand": { "templateId": "#utility-bridge-v0:Utility.Bridge.V0.Agreement.User:BridgeUserAgreement", "contractId": "${BRIDGE_USER_AGREEMENT_CONTRACT_ID}", "choice": "BridgeUserAgreement_Burn", "choiceArgument": { "amount": "${AMOUNT_IN_DECIMAL}", "destinationDomain": "0", "destinationRecipient": "${ETHEREUM_ADDRESS}", "holdingCids": "${HOLDING_CONTRACT_IDS}", "requestId": "${UUID_REQUEST_ID}", "reference": "", "factoryCid": "${FACTORY_CID}", "contextContractIds": "${CONTEXT_CONTRACT_IDS}" } } } ], "disclosedContracts": "${DISCLOSED_CONTRACTS}" } ``` ### Extracting Contract IDs and Disclosed Contracts The utilities backend provides a Burn Mint Factory API Endpoint. Endpoint: ```text theme={null} ${UTILITY_BACKEND_URL}/api/utilities/v0/registry/burn-mint-instruction/v0/burn-mint-factory ``` Example request body: ```json theme={null} { "instrumentId": { "admin": "${ADMIN_PARTY_ID}", "id": "USDCx" }, "inputHoldingCids": "${HOLDING_CONTRACT_IDS_IF_WITHDRAWING}", "outputs": [ { "owner": "${ADMIN_PARTY_ID}", "amount": "${AMOUNT_IN_DECIMAL}" } ] } ``` When you call the Burn Mint factory endpoint, the response contains the contract IDs and disclosed contracts you need for both minting and withdrawing. Note that these values can be cached to reduce api calls as these values change infrequently. As an example for extracting the required contexts and contracts from the response: ```typescript theme={null} // Assume `response` is the parsed JSON from the API call const choiceContext = response.httpResponse.body.choiceContext; // Extract CONTEXT_CONTRACT_IDS const values = choiceContext.choiceContextData.values; const contextContractIds = { instrumentConfigurationCid: values["utility.digitalasset.com/instrument-configuration"].value }; // Extract FACTORY_CID const factoryCid = response.httpResponse.body.factoryId; // Extract DISCLOSED_CONTRACTS const disclosedContracts = choiceContext.disclosedContracts; ``` ### MainNet Environment Variables | Variable | Value | | ---------------------------- | ---------------------------------------------------------------------------------------------------------- | | UTILITY\_BACKEND\_URL | `https://api.utilities.digitalasset.com` | | ADMIN\_PARTY\_ID | `decentralized-usdc-interchain-rep::12208115f1e168dd7e792320be9c4ca720c751a02a3053c7606e1c1cd3dad9bf60ef` | | UTILITY\_OPERATOR\_PARTY\_ID | `auth0_007c6643538f2eadd3e573dd05b9::12205bcc106efa0eaa7f18dc491e5c6f5fb9b0cc68dc110ae66f4ed6467475d7c78e` | | BRIDGE\_OPERATOR\_PARTY\_ID | `Bridge-Operator::1220c8448890a70e65f6906bd48d797ee6551f094e9e6a53e329fd5b2b549334f13f` | ### TestNet Environment Variables | Variable | Value | | ---------------------------- | --------------------------------------------------------------------------------------------------------- | | UTILITY\_BACKEND\_URL | `https://api.utilities.digitalasset-staging.com` | | ADMIN\_PARTY\_ID | `decentralized-usdc-interchain-rep::122049e2af8a725bd19759320fc83c638e7718973eac189d8f201309c512d1ffec61` | | UTILITY\_OPERATOR\_PARTY\_ID | `DigitalAsset-UtilityOperator::12202679f2bbe57d8cba9ef3cee847ac8239df0877105ab1f01a77d47477fdce1204` | | BRIDGE\_OPERATOR\_PARTY\_ID | `Bridge-Operator::12209d011ce250de439fefc35d16d1ab9d56fb99ccb24c18d798efb22352d533bcdb` | ## Supporting Token Standard actions (Holdings & Transfers) for USDCx USDCx is a standard Registry Utility token -- please refer to Utilities documentation for [API examples](/legacy-docs/legacy-docs/how-tos/examples), specifically of interest would be the following sections: * [Retrieve holdings API example](/legacy-docs/legacy-docs/how-tos/registry/holding/retrieve) * [Transfer API example](/legacy-docs/legacy-docs/how-tos/registry/transfer/transfer) * [Transfer Preapproval API example](/legacy-docs/legacy-docs/how-tos/registry/transfer-preapproval/transfer-preapproval)