Sandbox
Try the model before you sign up.
Pick a preset and a traffic tier to see a month of the split: what the app pays, the platform fee, what users earn and the app's rebate. It runs the same computeFees() the receipts are signed against, so the numbers are exact.
Lightning Fintech
lightning-fintech.sample
- Account creationClass A2,100 sats · 70% to the user
- Session openedClass C80 sats · 70% to the user
- Payment authorizedClass B0.50% of the amount · 75% to the user
- Payment method connectedClass A420 sats · 70% to the user
A month, at 10,000 MAU
120,000 sessions · 20,000 payments · 600 new accounts · 0 bond attestations
Representative volumes for each tier, not your telemetry. USD is at a fixed reference rate of $95,000 per bitcoin, not a quote.
Ship this config
Like the numbers? Put these prices on your project, or check them first with oc.config.validate() from @orangecheck/me-client. The full reference is at docs.ochk.io/me/sdk.
{
"project_key": "sample-lightning-fintech",
"display_name": "Sample · Lightning Fintech",
"domain": "lightning-fintech.sample",
"events": {
"account_creation": {
"enabled": true,
"site_pays": {
"kind": "fixed_sats",
"sats": 2100
},
"user_share_pct": 0.7
},
"session_creation": {
"enabled": true,
"site_pays": {
"kind": "fixed_sats",
"sats": 80
},
"user_share_pct": 0.7
},
"payment_authorization": {
"enabled": true,
"site_pays": {
"kind": "percent_of_amount",
"pct": 0.005
},
"user_share_pct": 0.75
},
"payment_method_connected": {
"enabled": true,
"site_pays": {
"kind": "fixed_sats",
"sats": 420
},
"user_share_pct": 0.7
}
}
}What the simulator does.
For each tier it builds a representative month:
- Sessions: monthly users times sessions each. One receipt per session; signing in inside one is free.
- Payments: monthly users times payments each, priced as a percent of the amount.
- New accounts: the tier's monthly sign-ups, paid once each.
- Bond attestations: the tier's monthly bonds, counted only when the config turns them on.
There is no KYC. A bond attestation is a BIP-322 signature over sats the user holds; orangecheck sees the attestation's hash, never the funds or any personal data.
Every event runs through computeFees(), which /api/platform-fee-policy publishes and production receipts are signed against. The platform fee is fixed at 20% of what the app pays. The user's share is the app's setting. The rebate is what is left.
Next.
Read the quickstart for the code, or send us your stack and we model it against your real usage. We answer within a business day.