Scrip runs the incentive ledger behind marketplaces and platforms. Milestone bonuses, credits, and referral rewards stay correct for sellers, creators, and drivers, through every payout, refund, and reversal. You keep your stack. Scrip keeps the books.
Scrip fits when incentives are how you grow supply or demand, and they have to stay correct. You’re a fit if:
Orders, payouts, sign-ups, listings, completed rides: each enters Scrip as an event, and your rules decide what it earns and who it pays. The shapes below are common across marketplaces, not a fixed menu. Scrip runs whatever rules you define.
A marketplace incentive isn’t a single moment. An order completes and moves a seller toward a milestone, the bonus pays out, then days later the order is refunded. Now the bonus has to come back, the counter has to roll back, and it all has to land on the right recipient and budget. Scrip ties every incentive to the event that created it and reverses the exact amount when that event reverses. Every step is a journal entry, so the balance always ties out.
Engineering integrates once: send the events you already emit, like order.completed or payout.released, to the API. From there, ops launches and edits campaigns, budgets, cohorts, and rates from the dashboard, no deploy required. Both run on one ledger, so an ops-launched promo is as auditable and reversible as anything your engineers build.
Scrip works alongside any payments or payouts stack that can send an event, and never moves money itself. Built-in incentives from those providers are usually basic; Scrip is for programs that need programmable rules, budgets, cohorts, reversals, and an audit trail.
Tell us how your incentives are earned, paid, and reversed today, and we’ll map it to Scrip. Request access for a founder conversation, or read the docs.
Marketplaces and platforms push incentives, multi-party payouts, and accounting together at scale. The same ledger runs cards & banking, retail & ecommerce, and subscriptions & SaaS programs too.