IncentivPay — The AI Incentive Platform
    The AI Incentive Platform

    Turn every transaction into the next reason to return.

    IncentivPay decides which incentive to use, delivers it across your commerce stack, and proves the incremental profit — starting with Outcome-Based Incentives.

    Design a measured pilotSee how OBI works
    An orbit of merchant moments — purchase, review, return, referral — organized around the incentive decision.
    How we work: Start with one customer behavior, a capped budget, and a pre-agreed measurement plan.
    Pilot
    Decide
    The next-best incentive for a real customer state
    Deliver
    Across the merchant's existing commerce surfaces
    Prove
    Incremental gross profit, measured against a baseline
    Why traditional incentives fail

    Blanket discounts leak margin. Points aren't spendable. Loyalty pays after the fact.

    Merchant teams manage a portfolio of incentives that no one can actually price. The result: budget is spent up-front, attribution is inferred, and the finance team can't tell you what actually worked.

    IncentivPay treats each incentive as a decision — with a hypothesis, a budget cap, a mechanism, and a proof plan agreed before anything ships.

    • Every decision written to an auditable log
    • Merchant-defined budget caps enforced by the platform
    • Measured against a baseline or holdout — not inferred
    Illustrative diagram of a decision moving through decide, deliver, and prove stages.

    Decide · Deliver · Prove

    One platform, three responsibilities. Each is designed to be inspected, capped, and reversed.

    Decide
    Recommend the next-best incentive for the customer state — with confidence, assumptions, and a proof plan attached.
    Deliver
    Execute the decision across the merchant's existing surfaces: post-purchase, messaging, printed QR, POS, and wallet.
    Prove
    Compare exposed customers against a baseline or holdout. Report incremental gross profit — not attributed revenue.
    The Incentive Decision RecordPilot

    Every incentive comes with a proof plan — before it ships.

    Pick a customer behavior. See exactly what the platform would recommend, what it assumes, and how it would measure whether it worked.

    Illustrative example · not customer data

    Incentive Decision Record
    Drive the second purchase
    Confidence: Medium
    Behavior
    Convert first-time buyers into a second purchase within 30 days
    Audience
    First-time buyers, order 1 in the last 14 days, no active discount
    Mechanism
    Merchant-funded value credit, sized to expected margin on next basket
    Budget cap
    ≤ 12% of expected repeat-order gross profit; $8/customer hard cap
    Assumptions
    • Baseline 30-day repeat rate ≈ 14% (from your last 90 days of orders)
    • Redemption occurs on next visit; no stacking with active promotions
    • Contribution margin on next order ≥ 35%
    Proof plan
    • Randomized holdout on 20% of eligible first-time buyers
    • Measurement window: 30 days from first purchase
    • Primary KPI: incremental gross profit per exposed customer
    Expected lift
    +2.4 to +4.1 pts of 30-day repeat rate (illustrative)
    Every recommendation is written to an auditable decision log. Nothing ships without a merchant approval and a pre-agreed measurement window.
    The signature mechanism

    Outcome-Based Incentives: pay for the behavior, not for the impression.

    An Outcome-Based Incentive is merchant-funded value that only settles when a defined customer behavior occurs — a second visit, a completed review, a referred conversion.

    The mechanism, budget, audience, and measurement plan are agreed with the merchant before it ships. Nothing runs unattended, and nothing runs without a proof plan.

    • Merchant-funded value — never a bank payout to customers
    • Budget capped per customer and per campaign
    • Baseline / holdout measurement is the default, not the exception
    Illustrative view of an Outcome-Based Incentive with mechanism, cap, and measurement plan.

    What sits behind each decision

    Six platform layers, each with a defined status and a clear owner in the merchant org.

    Growth Intelligence
    What should happen next for which customer, and why.
    Journey Orchestration
    When and where the experience is delivered.
    Incentive Engine
    Mechanism selection, eligibility, funding, rules.
    Value & Wallet Infrastructure
    IP Cash, holds, redemption, reconciliation.
    Commerce Surfaces
    Post-purchase, messaging, printed QR, POS, marketplace.
    Trust & Governance
    Budget caps, approvals, activity log, separation of duties.
    Works with the stack you already trust

    Delivery surfaces & integrations

    Shopify
    Pilot
    Stripe
    Pilot
    Klaviyo
    Planned
    HubSpot
    Planned
    Toast
    Planned
    Square
    Planned
    See all integrations
    Governance

    Every decision is capped, approved, and logged.

    Merchants define the budget ceiling, the hedge allocation, and the mechanisms allowed. The platform cannot exceed them — the guardrails are enforced in the optimizer itself, not just the UI.

    Every recommendation is written to an activity log that the merchant, an auditor, or a finance controller can read line-by-line.

    • Human approval before autonomous decisions apply
    • Merchant-defined budget caps enforced end to end
    • Auditable decision log — mechanism, mix, and rationale
    Illustrative view of merchant guardrails and an activity log.
    Merchant-defined budget caps
    Auditable decision log
    Baseline / holdout measurement
    Works on your existing stack

    Frequently asked

    Is this a loyalty program?+

    No. Loyalty programs pay after the fact against inferred behavior. IncentivPay defines the behavior first, agrees a budget cap and a measurement plan, and only funds value when the behavior actually happens.

    Do I have to replace my checkout, POS, or ESP?+

    No. IncentivPay is designed to sit on top of Shopify, Stripe and the messaging tools you already run. Availability by integration is labeled on the integrations page.

    What does 'measured pilot' actually mean?+

    One customer behavior, one capped budget, one pre-agreed measurement window with a baseline or holdout. At the end of the pilot you get an incremental gross-profit read — not attributed revenue.

    Where does the Merchant Growth OS fit in?+

    It's our five-year category thesis — the destination this platform points at, not what ships today. The AI Incentive Platform is the entry point.

    Who owns the customer relationship?+

    The merchant does. Value is merchant-funded and spendable at the merchant. IncentivPay does not compete with the merchant for the customer.

    Design a measured pilot.

    One customer behavior. One capped budget. One pre-agreed measurement window. At the end, an incremental gross-profit read you can bring to finance.

    Design a measured pilot See how OBI works