How allocation changes
Explain the role of market selection and rebalancing without making the customer manage the underlying venues.
The purpose of rebalancing is to adapt the underlying allocation as market conditions change. Your product can keep a consistent Earn experience while the configured strategy manages its exposure to approved markets.
Separate the strategy from its visibility
The contract and strategy implementation determine how assets can be allocated. The integration API gives your team information about vaults, recorded rates and decisions. An API response describing a decision does not itself execute a rebalance.
Before launch, agree the eligible markets, risk limits, capacity considerations and operating roles for the deployed strategy. Describe those controls as the chosen configuration rather than assuming every vault shares the same policy.
What to show a customer
Show the current position, its value, relevant activity and the source of the rate. A customer who opens a detailed view can see the market context and an explanation of why allocation may change. The main balance view should stay readable without requiring them to interpret every underlying action.
What your operations team needs
Use the analytics and activity resources to inspect available decision records and related position events. Connect those to the customer-facing explanation and, where applicable, the confirmed transaction record.
The Partner API's analytics use available observations. Some responses can report insufficient data on a new deployment. The sandbox generates a separate simulated history for demonstrating the workflow.
Withdrawal experience
A withdrawal depends on the deployed contracts, liquidity and network state. Plan the pending, confirmed and failed states explicitly. Avoid promising a universal execution time based on how quickly a sandbox endpoint responds.
Continue with positions and activity and launch verification.