There are two distinct money flows around a Roadie app. Keeping them separate is the whole point of this page:
  1. You pay Roadie for the gateway you use — a Stripe subscription, metered per request.
  2. Your end users pay you inside your app — your own StoreKit / in-app-purchase flow, which Roadie does not touch.

​
Flow 1 — you pay Roadie (Stripe)

Your organization subscribes to a Roadie plan through Stripe. Billing is owner-only in the dashboard, and both the checkout and the “manage subscription” flows are Stripe-hosted pages: you open a checkout session to subscribe and a billing-portal session to update payment details or cancel. Your subscription and invoices are mirrored into Roadie, so the dashboard renders them instantly and a Stripe outage never breaks a read. Subscription state is only ever written back from Stripe (after a full refetch), never edited directly.

​
What is metered

Roadie bills on requests, not tokens. Every billable request is counted exactly once and rolled up per UTC day into a durable ledger, then reported to Stripe’s usage meter. Reporting is exactly-once: each day’s meter event carries a deterministic identifier, so a retry after a crash is deduped by Stripe and can never double-bill. Token counts and per-request cost still appear in your usage and analytics — they just aren’t the billing unit.

​
Payment problems never hard-stop your app

If a payment fails, Roadie downgrades entitlements rather than shutting you off. A past_due subscription keeps its plan for a grace window; beyond that (or unpaid / canceled) the org’s keys keep working at free-tier limits — they are never hard-blocked for a billing problem. A genuine hard shutdown is a separate administrative action, not a consequence of dunning.

​
Flow 2 — your end users pay you (StoreKit / IAP)

When your users buy a subscription or credits inside your app, that transaction is between them and you, through Apple’s StoreKit, Google Play Billing, or whatever IAP you use. Roadie is not in the payment path and never sees your end users’ payment details. Roadie’s job on this side is to meter, entitle, and limit — not to charge. Your purchase handler (for example, an App Store Server Notification) tells Roadie the outcome by granting the end user an entitlement with your secret key, and Roadie enforces the matching per-plan limits from then on.
Roadie never bills your end users and never issues them refunds. End-user monetization is entirely your StoreKit/IAP relationship; Roadie only records the entitlement you grant.

​
Plans

free is the un-metered default a new org starts on; pro is the paid, metered tier with an included request allowance and graduated overage above it. (A larger scale tier exists in the plan catalog but is not part of the current story.) To move from free to pro, open a checkout session from the billing area of the dashboard. To see what you have used this period, check the subscription view — it sums your finalized billable requests since the current period’s start.