Developers · Base

Build a Base App cash-out flow with standard web tooling.

The route and starter directory keep the base-mini-app name for compatibility, but the target is a standard web app that works in Base App's in-app browser and any modern mobile browser.

Clone the Base templateOpen the sell flow
01

Use the existing starter

  1. 01Clone ADWilkinson/usdctofiat-peerlytics-starters and open templates/base-mini-app.
  2. 02Set NEXT_PUBLIC_APP_URL and deploy the app to a stable public HTTPS origin.
  3. 03Keep the form compact: route, amount, payout handle, wallet connect, and result.
  4. 04Register the deployed URL and app metadata on Base.dev; do not add a Farcaster manifest.
02

Base App requirements

Next.js app
Runs as a standard web app in Base App's in-app browser and regular mobile browsers.
Base Account
Gives users a Base-native connection path through @base-org/account.
Viem WalletClient
The off-ramp SDK signs with the wallet client you provide.
Builder Code
Base.dev registration owns app metadata, discovery, and the issued attribution code.
Real transaction test
A production build is not enough; verify a small Base deposit end to end.
03

Keep it standard and focused

  • Do not add a marketing hero before the cash-out form.
  • Do not hide the payout route, amount, or handle behind onboarding copy.
  • Do not claim guaranteed fill speed; buyer demand still controls liquidity.
  • Do not add a Farcaster manifest or mini-app SDK; Base App discovery uses Base.dev metadata and Builder Codes.

Keep exploring

Offramp SDKPeerlytics APIDeveloper hub

Common questions

What should the Base App integration do first?

It should create a real USDCtoFiat seller deposit from a connected Base Account wallet. Start with amount, route, payout handle, and the deposit result before adding anything else.

Does the Base App integration need a separate backend?

Not for the basic cash-out flow. The wallet signs through the client and @usdctofiat/offramp creates the Base deposit. Add a backend only when you need account state or your own order database.

Does this integration need a Farcaster manifest?

No. Base App uses standard web apps and Base.dev metadata. Register the deployed HTTPS URL, app details, and Builder Code on Base.dev instead.