Skip to main content
A successful launch connects four things: a product people can understand, a funded reward policy, a working purchase and delivery flow, and clear responsibility for settlement. Use this guide alongside the merchant walkthrough.

​
Before opening the composer

​
An illustrative launch plan

Suppose a test product costs 20 SDUSD and you choose a 10% reward, a 2 SDUSD per-sale cap, two paid levels, and a 70/30 split. With sufficient funding and a full two-person path, one sale reserves 2 SDUSD: 1.40 for the nearest distributor and 0.60 for their parent. A 40 SDUSD available budget supports at most 20 such reservations before considering other constraints. It does not guarantee 20 sales. Refunded purchases release their reservations; finalized and claimed rewards still count toward the campaign’s lifetime liability usage. Keep the buyer payment separate: each buyer pays 20 SDUSD for the product. The additional 2 SDUSD reward comes from your funded reward budget.

​
Create, fund, then activate

A newly created onchain campaign starts inactive. Funding adds to its available reward balance. Activation requires some available reward funding and merchant authorization. The user interface can guide you through these steps, but each required onchain transaction must succeed. After activation, inspect the public campaign as a buyer would. Confirm the price, product version, reward rate, paid depth, short-path rule, hold, and end time. Create a test link with a different wallet: the merchant cannot be its own distributor.

​
Verify both settlement outcomes

Use separate eligible buyer wallets to exercise the two outcomes. The current prototype allows one purchase per buyer per campaign, even if that purchase was refunded. These are testnet verification steps. Do not use a real mainnet asset or interpret the resulting SDUSD totals as revenue.

​
Monitor the campaign after launch

Watch available rewards, pending reservations, claimable liabilities, campaign expiry, and indexing freshness. A large gross deposit is not the same as a large remaining budget. If the graph is active but purchases fail, inspect caps, available funds, buyer eligibility, and capacity limits before changing the interface. To revise future policy terms, schedule a version with at least 24 hours’ notice. To stop new activity immediately, pause the campaign. Existing refund, finalization, and claim obligations continue. See vault accounting for exact balance movements and refunds and claims for who can perform each action.