A three-vendor checkout with a 4% commission and a reviewed payout policy.
1. Prepare the project
Open Project → Marketplace → Settings. Enable Marketplace and select participating stores. Keep payouts paused for now. Back up the project wallets and enable Bitcoin or supported EVM methods in each store.
Customers pay these project wallets first. You control the keys and owe the recorded balances to vendors. Keep separate free native coins for fees. Ordinary sweeps cannot spend Marketplace receiving addresses.
2. Add and approve three vendors
In Vendors, add each seller and a Bitcoin mainnet address. Independently confirm the address with the seller before approving it. For EVM tokens, each seller also needs an approved address on that exact network.
Set the project commission to 4%. Store, vendor and authorized invoice overrides are snapshotted, so later edits do not change an existing allocation.
3. Create the shared invoice
In Marketplace → Invoices, create a 300 USD invoice with three gross vendor shares of 100 USD. Their total must match exactly. Send the customer the checkout link.
For API integration, use a separate Marketplace key and send decimal strings to /v1/marketplace/invoices. Save the idempotency key before the request and reuse it after a timeout. Request examples →
4. Review and send
Wait for verified allocations to become available. At the locked quote, each seller gets 96 USD-equivalent in the paid asset and you retain 12 USD-equivalent commission. The existing 1% processing charge, if configured, costs 3 USD in prepaid credits. Chain fees are separate.
In Payouts, prepare the available allocations and cap native fees and gas. Bitcoin requires every unpaid share of a selected invoice in the same batch. Review the exact recipients and plan, then approve once. Follow it until Paid, not just Broadcast.
5. Enable automation carefully
In Settings, add a policy for one asset: minimum payout, per-payout and daily principal limits, native fee and gas budgets, interval and confirmations. Enable it only after reviewing those limits and destinations, then unpause payouts.
Automatic policies can send without further clicks. Low credits or the server’s transfer gate still pause spending. Monitoring and the ledger continue.
6. Handle exceptions without duplicate sends
- Underpaid: checkout tolerance does not create unfunded vendor balances. Wait for more payment, refund, or explicitly approve a smaller fully backed split.
- Missing token gas: add free native coins to the project wallet and review the retained payout. Do not create a second payout to bypass it.
- Webhook timeout: retry the same signed event. Verify its raw signature and project, save event_id uniquely, then acknowledge. An invoice-settled event is not payout completion.
- Refund after vendors were paid: fund the primary wallet separately, verify the customer address, prepare a full same-asset refund and approve it. Vendors are not automatically debited.
- Restore or uncertain broadcast: keep payouts paused and reconcile the retained transaction hashes before resuming. Never assume a timeout means nothing was sent.