Earn with your Commerce app
Revenue share is included by default for Commerce partners. Earnings belong to the DYLI account that owns your app's Commerce key and appear in Profile → Storefront → Commerce. Withdraw available earnings through Claim.
| Activity completed through your app | Default partner share | Example |
|---|---|---|
| Pack openings | 10% of settled pack profit | $100 in pack sales minus $60 in item costs and buybacks leaves $40 profit: your share is $4. |
| Secondary sales, including accepted offers | 10% of DYLI's collected marketplace fee | A $100 sale with a 5% DYLI fee generates $5 in fees: your share is $0.50. |
| P2P trades involving cash | 10% of DYLI's collected cash-trade fee | A trade with $100 in cash and a 2.5% DYLI fee generates $2.50 in fees: your share is $0.25. |
Secondary and trade shares come out of DYLI's fee. They do not add a fee for the buyer or reduce the seller's proceeds further. Contract fees can change; earnings always use the fee actually collected, not the example rate. Item-only trades and gifts generate no fee share.
Pack earnings
Settled pack profit is base sales minus cash buybacks, the cost of items customers keep, and refunds. A bought-back item does not also incur an item cost. Losses offset gains before the owner's 10% profit share is floored at zero. Unresolved item costs remain pending. Test, free, failed, cancelled and unfinished purchases do not earn revenue share.
An optional fee you add to pack checkout is credited separately as Your pack fee, after applicable discounts and refund checks. It is not part of the pack profit calculation. Pack accounting details.
Pack owner controls
Pack owners can turn Commerce access on or off in Profile → Storefront → Packs → Settings. Packs start opted in. Turning it off stops new Commerce quotes and checkouts. Paid purchases can still finish, and the pack stays available on DYLI. The read API still returns the pack with commerce_off: true; the Commerce catalog leaves it out.
For new checkouts, the pack owner covers their portion of the partner's profit payout as a negative earnings adjustment. For example, $1 in profit gives an owner with an 85% share 85¢. The partner earns 10¢. The owner contributes 8.5¢ as a negative adjustment and keeps 76.5¢; DYLI covers the other 1.5¢. The adjustment follows settled earnings, including buybacks, item costs, refunds and losses.
Secondary sales and cash trades
Use the normal community action flow: prepare the action, have the registered customer wallet submit it on Base, and confirm it with the same transaction hash. No new checkout or payout integration is needed.
The app confirming the completed purchase, accepted offer, or accepted cash trade receives the share. This includes buying an existing DYLI listing through your app. Publishing a listing, making an offer, proposing a trade, or displaying the public feed alone does not earn a share. A transaction earns one partner share, not separate shares for both sides.
The share rate is saved when the settlement action is prepared. DYLI verifies the transaction and the fee payment before crediting earnings. A retry or refresh cannot credit the same transaction twice. If confirmation needs a retry, reuse the existing action and transaction hash; do not submit another payment. Shares apply to eligible actions prepared after revenue sharing is enabled, not older activity or test networks.
The partner receives 10% of the fee, not 10% of the sale or trade's cash value. Cash trade earnings apply only to the cash portion, not the value of the exchanged items. Earnings are recorded to six decimal places per completed action.
Track earnings
The Commerce dashboard separates Pack profit share, Secondary fee share, Cash trade fee share, and Your pack fee, with transaction history for secondary sales and trades.
For your backend, GET /analytics returns summary.secondary_earnings, summary.trade_earnings, and the combined lifetime summary.earnings. community.transactions includes the transaction hash, source, cash volume, collected DYLI fee, applied share rate and earnings. revenue_share describes your app's current rates. These are private owner reports; do not expose them to customers. API fields.
Earnings use the existing Claim flow. Lifetime earnings are not an additional wallet balance; previous claims and reservations are deducted when calculating what you can withdraw. Rotating your API key preserves your history.
Want to discuss custom rates?
Tell us about your app and expected volume, and we can discuss custom rates.
Include your app slug or DYLI username so we can find your account.