Payload · Revenue Infrastructure
Your payment system moves the money.
RevRule decides who earns what.
RevRule is a revenue rules engine for businesses where more than one party earns from the same revenue. Define your contract rules once: who gets what share, what gets recouped first, how a waterfall flows. Every time revenue comes in, RevRule calculates each participant's entitlement and records it in an auditable ledger.
RevRule calculates entitlements and records the results. It never holds your funds and never executes payments. Your payment system still moves the money.
ACCURATE CONTRACT CALCULATIONS · RECOUPMENT AND WATERFALLS BUILT IN · HASH-CHAINED AUDIT LEDGER · NO FUNDS HELD, EVER
How it works
Define the rules once. RevRule runs them on every payment.
Three steps replace the spreadsheets, the hand-tracked recoupment, and the payout logic scattered across your codebase.
Step 1
Define a Revenue Graph
Encode the economics of a deal as a persistent rule set: percentages, recoupment, waterfalls, caps, and attribution. The rules belong to the relationship, not to one payment.
Step 2
Send revenue events
When revenue happens, your product sends one event. Stripe, x402, or any other rail: the rail can change, the economics persist.
Step 3
RevRule calculates and records
Each participant's entitlement is calculated against the current state of the rules and written to a hash-chained ledger you can query and export as JSON.
$1.00 API PAYMENT
Drag to change the rules. The split recomputes instantly. This is what RevRule computes on every event, automatically.
Try the full engine with recoupment and waterfalls in the RevRule sandbox or the live example scenarios. No sign-up, no credit card.
Example ledger entry · synthetic data
EVENT api_payment $1.00
Recorded in a hash-chained ledger and returned as JSON. Every entry links to the one before it, so any entitlement can be re-verified later.
entry_hash 9f2c…a41b · prev_hash 77d0…3e9c (illustrative values)
Normal splitter
70% → A
30% → B
Done. Nothing persists. Nothing changes. The next payment is a blank slate.
RevRule
70% → A until $50,000 is recouped, then 55%
10% → B only on attributable customers
5% → C for qualifying revenue
3% → platform, always
Rules persist across every future economic event. The engine remembers where every rule stands.
Use cases
Built for revenue that is shared
One engine, one Revenue Graph model. If your revenue has more than one name on it, RevRule keeps the math straight.
An API earns $1
RevRule distributes the economics across developer, platform, referrer, and contributor on every call.
Reward everyone who helped
Developer, salesperson, partner, or referrer gets their share calculated automatically on every subscription.
Program the whole split
Seller, platform, referral, and contributor economics in one persistent rule set instead of scattered code.
Royalties that stick
Keep royalties and residuals attached to qualifying revenue across every future event. See RevRule for music labels and publishers.
Commissions without spreadsheets
Partner shares, commissions, and recoupment rules that calculate themselves instead of living in a spreadsheet.
Continuing participation
Apply ongoing economic participation across every qualifying sale of licensed work, with the state remembered.
Pricing
Start free. Pay when it earns.
Try the full engine free in the sandbox, with no credit card and no trial clock. For production, choose the one-time perpetual license or a managed monthly plan. Every option runs the same engine and the same rules.
The $99 one-time license
A perpetual license. It never expires and is never metered: production access, unlimited Revenue Graphs, and no monthly operations cap, with one API key. Buy it once and it keeps everything it includes today.
A managed monthly plan
An ongoing hosted service on Payload infrastructure, billed monthly. A plan adds a structured capacity tier: a set monthly operations allowance, set allowances for Revenue Graphs and API keys, and multiple keys on the higher tiers. Choosing or cancelling a plan never reduces a one-time license.
Starter
Managed plan
$29
per month
Hosted RevRule with room for a first production workload.
- 10,000 operations per month
- 10 Revenue Graphs
- 1 API key
- Email support, best effort
Professional
More capacity
$79
per month
For growing revenue volume and a small team of integrations.
- 100,000 operations per month
- 50 Revenue Graphs
- 3 API keys
- Email support, best effort
Business
Managed plan
$199
per month
For platforms and marketplaces running serious shared revenue.
- 1,000,000 operations per month
- Unlimited Revenue Graphs
- 10 API keys
- Email support, best effort
One-Time License
Perpetual
$99
one-time, never expires
The full engine, owned outright. No subscription, no metering.
- No monthly operations cap
- Unlimited Revenue Graphs
- 1 API key
- Never metered, never expires
- Email support, best effort
| Compare | One-Time | Starter | Professional | Business |
|---|---|---|---|---|
| Price | $99 once | $29/month | $79/month | $199/month |
| Operations per month | No monthly cap | 10,000 | 100,000 | 1,000,000 |
| Revenue Graphs | Unlimited | 10 | 50 | Unlimited |
| API keys | 1 | 1 | 3 | 10 |
| Term | Perpetual license, never expires | Monthly, while subscribed | Monthly, while subscribed | Monthly, while subscribed |
| Support | Email support, best-effort response, no guaranteed response times | Email support, best-effort response, no guaranteed response times | Email support, best-effort response, no guaranteed response times | Email support, best-effort response, no guaranteed response times |
Every paid option, one-time and managed, runs at the same engine fee tier. Additional API keys within a plan allowance are issued by Payload support on request. Free evaluation: test Revenue Graphs, simulations, sample rules, and blueprints in the sandbox, or get a free API key from the console. New free accounts include a bounded demo of 1,000 operations per month and 3 Revenue Graphs.
Managed plans bill monthly and can be cancelled at any time. Cancellation takes effect at the end of the current billing period, plan allowances stay active until that date, and partial-period payments are not refunded. Charges made in error are refunded in full. Purchases on Payload controlled surfaces carry a 7-day refund window for eligible new purchases; on marketplaces, the marketplace's own refund rules govern.
RevRule establishes what is owed and verifies payouts against genuine entitlements. RevRule does not execute payments and does not hold customer funds.
Enterprise: volumes beyond Business, or custom terms. Contact us and we will scope it with you.
FAQ
Straight answers
What RevRule does, what it does not do, and exactly how buying it works.
What does RevRule do?
Does RevRule hold my money?
What is the difference between the $99 license and a managed plan?
How do I cancel a managed plan?
What is the refund policy?
What support is included?
Do I need crypto?
Can I use it with normal software?
Is it only for royalties?
Is it only for x402?
Is it only for large companies?
Do I have to replace my payment provider?
Documentation
Verify it yourself
Developers trust what they can inspect. The engine, the API, and a recorded payout verification are all public.
Problem guides
Written for the person who runs the numbers. Verified explanations with synthetic, labeled demonstrations: royalty recoupment calculation, a renegotiated split applied late, revenue-share reconciliation spreadsheet risks, contractual waterfall calculation, creator commission splits.
Your payment rail moves money.
RevRule decides who earns.
Support: contact@payloadhq.dev