# Design your integration

Start from your customer journey, then connect the product, data and capital flows around it.

An Earn feature works best when it belongs to the product around it. Decide where customers see their balance, how they consent to earn, and how they return funds to an available balance. Then map the API and wallet operations that support that journey.

## Choose the starting point

| Your product | Customer experience | Integration priorities |
| --- | --- | --- |
| Fintech or neobank | Move money into an Earn pocket inside an existing account | Balance semantics, consent, customer support and account reporting |
| Wallet | Discover yield and manage a position beside an existing token balance | Network compatibility, signing, transaction status and share balances |
| Platform with stablecoin users | Offer an Earn destination inside the platform | Attribution, branded flows, activity and partner economics |

Read the [fintech guide](/guides/neobanks/) or [wallet and platform guide](/guides/wallets/) for a complete example.

## Assign the ownership clearly

Your product owns the interface, customer relationship and the balance model presented to users. Your backend authenticates to the Partner API and connects attributed users, reporting and events. Wallets and deployed contracts determine who authorizes the asset movement and where the resulting position is held.

Document these as separate responsibilities. Creating an API user or recording an attributed position is not the same action as submitting and confirming a blockchain transaction.

## Define the first useful release

A focused first release gives a customer four answers: what can I earn on, how do I begin, what is my position worth, and how do I withdraw?

For your team, it also needs a supportable operating view: which customer a position belongs to, the relevant transaction or event, the source of the displayed value, and the next action when something fails.

## Bring these decisions to the integration review

- Customer segment and the existing account or wallet flow.
- Asset, token address, network and expected balance range.
- Wallet custody and signing model.
- The proposed Earn entry, balance display and withdrawal experience.
- Attribution, reporting, event and reconciliation requirements.
- Commercial assumptions and the owners of product, engineering and operations.

Use the [launch checklist](/operate/launch/) as the shared handoff.