# Common questions

The decisions teams usually need to resolve before building.

## Can Earn live inside our product?

Yes. The integration is designed around your customer experience: account entry point, attribution, balances and activity. Use the [integration paths](/start/integration-paths/) to map your product flow and the wallet transaction work required.

## Does an API call move customer funds?

The Partner API covers attribution and reporting; it does not expose the sandbox's simulated position-creation route. Wallet settlement requires the confirmed contract integration. See [architecture](/concepts/architecture/).

## Which asset symbols should we use?

The current Partner API accepts USDC and USDT0. The sandbox models USDC and USDT. Confirm actual token addresses and networks in your deployment pack.

## Is the displayed yield fixed?

No. Rates change with underlying markets. The API's history fields describe observations over time. Display observation periods and handle missing data. [Yield guide](/concepts/yield/).

## How does a partner earn revenue?

The API models a partner share of protocol fees. It exposes estimates for reporting; those values are not settlement records. [Partner economics](/concepts/revenue/).

## Can users always withdraw immediately?

Completion depends on contract state, market liquidity and the network. Implement pending and unavailable states. The current optimized source includes a withdrawal pause check. [Withdrawal guide](/customer/withdraw/).

## What has been audited?

The October 2025 Hexens report names exact reviewed and remediation commits in the earlier contracts repository. Compare that scope with your deployment. [Audit evidence](/security/audits/).

## Where do we start?

Prototype the account journey in the [sandbox](/start/sandbox/), then use the [Partner API quickstart](/start/quickstart/) with your onboarding details. Bring product, engineering and operations together for the launch review.