Pricing

Integration · Billing

$

Stripe

Stripe is the canonical source of truth for subscription state — trial starts, conversions, downgrades, churn. Metapolicy ingests these as reward events and writes outcome-priced invoices back into Stripe so customers see one bill per month, denominated in measured incremental revenue.

The contract

What flows in

  • Subscription created / updated / cancelled webhooks → trial_start, conversion, downgrade, churn reward signals
  • Invoice payment_succeeded events → revenue confirmation
  • Customer object → user_id mapping for cross-surface lift attribution

What flows out

  • Monthly outcome-priced invoice via Stripe Billing — line items show measured incremental revenue per shipped policy snapshot
  • Optional: line-item-level write-through of LiftReadout case IDs into invoice metadata for procurement audit

Setup

  1. 01In Stripe Dashboard → Webhooks, add the Metapolicy endpoint and select customer.subscription.* + invoice.payment_succeeded
  2. 02Provide your Stripe Publishable + Secret keys in the Metapolicy dashboard (scoped to read-only on customer/subscription, write on invoice)
  3. 03Map Stripe customer.metadata.user_id to your internal user_id so cross-surface decisions match the right subscription
  4. 04Verify the first reward event arrives by triggering a test subscription event in Stripe's test mode
  5. 05Switch the integration to live mode once a real invoice clears reconciliation

Why this is the canonical reward source

Every other source of revenue truth (analytics events, in-app receipts, manual reconciliation) drifts. Stripe's invoice record is the bookkeeping primitive for subscription businesses — it's what the CFO references. Our reward signal is derived from the same event your finance team uses to close the books.

The DR + ESS guardrail means we never invoice on lift that fails to clear the threshold; the lift that does clear is the same number your finance team will see post-reconciliation.

Test-mode workflow

Test-mode webhooks fire reward events into your Metapolicy test environment. You can replay an entire month of test subscriptions to validate the decision policy before flipping to live.

Test-mode invoices are never written back — only the lift readout is computed and displayed in your dashboard.

Wire Stripe in a 30-minute call.

We pair with your engineer, ship the integration live, and run the first decision on your stack.

Book the call