Accept a cross-chain contract deposit
Request a custom quote with the calls your destination contract requires. Validate the recipient, token, amount, and encoded calls before funding. The destination-calls guide explains the execution context and failure behavior. The calls execute within the destination fulfillment transaction. Source-chain funding and any later refund are separate transactions, so your application must track the intent lifecycle.Choose a deposit-address flow
Programmable Addresses provide specific supported deposit routes. Use the Solana flow for Base USDC to a Solana recipient, or the Circle Gateway flow for Gateway deposits. Check the selected service’s source tokens, destination, and funding requirements before integrating.Program onchain execution
Use the Sauce SDK to combine reads, conditions and contract calls in one transaction. The first-program guide introduces compiling and simulation. Sauce SDK quickstarts covers payments, conditional swaps, lending positions and balance management. A program can run on its own. For execution triggered by a Routes intent, read Sauce in a route. Your application remains responsible for scheduling any repeated runs and tracking their transactions.Manage application liquidity
Use the treasury-rebalancing guide to plan transfers between your own wallets. Your service chooses thresholds and tracks in-flight transfers before initiating another rebalance.Next steps
- Integrate the Routes API for the transfer workflow.
- Destination calls for contract integration.
- Sauce SDK quickstarts for complete onchain programs.
