Scrip runs the rewards ledger behind card and banking programs. Cashback, points, and tier bonuses stay correct for every customer, through authorization, settlement, reversal, and expiration. You keep your stack. Scrip keeps the books.
Scrip fits when rewards are core to the product and have to stay correct. You’re a fit if:
Card swipes, refunds, deposits, statement cycles: each enters Scrip as an event, and your rules decide what it earns. The shapes below are common, not a fixed menu. Scrip runs whatever rules you define.
A card charge isn’t a single number. A restaurant check authorizes at $130, then settles at $150 once the tip is added. Reward on authorization and it feels instant, but the amount can still change; wait for settlement and the customer wonders where their points went. Scrip does both: it holds the reward on authorization, then trues it up when the final amount settles. Every step is a journal entry, so the balance stays correct.
Your issuer processor or BaaS provider issues cards, authorizes, settles, and holds deposits. Scrip runs the rewards program on top: you send the events you already receive, Scrip resolves the customer, runs your rules, and writes to the ledger. Scrip never moves money. When a reward is redeemed, it records the entry and emits the event your statement-credit, payout, or fulfillment partner acts on.
Works with any issuer processor, BaaS provider, or core banking platform that can send an event. Their built-in rewards are usually basic; Scrip is for programs that need programmable rules, tiers, expiration, reversals, and an audit trail.
Tell us how your program earns and redeems today, and we’ll map it to Scrip. Request access for a founder conversation, or read the docs.
Cards and banking are where rewards, transactions, and accounting collide first. The same ledger runs marketplaces & platforms, retail & ecommerce, and subscriptions & SaaS programs too.