Try the model. Before you sign up.
Pick a preset that matches your shape (or customize), pick the traffic tier closest to your scale, and see what the four-way split — site paid · OC fee · user cashback · site rebate — looks like for one month. The simulator runs the same computeFees() that the production verifier runs; numbers below are exact, not approximate.
pick a preset, pick a traffic tier, see the math.
Simulates one month of representative traffic against the chosen integrator config. Updates as you switch presets or scale traffic. Both denominations on every aggregate.
account creation | 2,100 sats | 70% to user |
session opened | 80 sats | 70% to user |
payment authorized | 0.50% of amount | 75% to user |
payment method connected | 420 sats | 70% to user |
> simulation uses representative event volumes per traffic tier. real integration replaces these with your actual telemetry. legacy quotes drawn from auth0 b2c starter, stripe standard 2.9% + $0.30, twilio sms. me.ochk does not do kyc — sybil resistance comes from bonded-identity + paid-action history + integrator-defined gates, not from third-party PII handlers.
Like the math? Copy the JSON below into your oc.config.update() call — the SDK posts it under your project_key. Full reference at docs.ochk.io/me/sdk.
{
"project_key": "sample-lightning-fintech",
"display_name": "Sample · Lightning Fintech",
"domain": "lightning-fintech.sample",
"updated_at": "2026-06-12T02:53:37.611Z",
"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 is doing
For each traffic tier, the simulator generates a representative one-month event mix:
- sessions — MAU × sessions-per-user. Class C billable atom; one envelope per session, free intra-session signins.
- payment authorizations — MAU × payments-per-user. Class B percentage-of-amount events at the chosen rate.
- account creations — proxied by the tier's monthly signup volume. Class A one-time events.
- bond attestations — proxied by the tier's monthly sat-bond attestation volume. Only counted when the integrator config has
attest_bond_increasedenabled. me.ochk does NOT do KYC — bond attestations are BIP-322 signatures the user makes against sats they hold; OC sees only the attestation hash, never the funds or any PII.
Each event runs through the canonical computeFees(cfg, payment_amount?) that /api/platform-fee-policy publishes and that production envelopes are signed against. The platform fee is fixed at 20% of gross. The user cashback comes from the integrator's configured user_share_pct. The site rebate is whatever's left.
Legacy-stack quotes for comparison are based on Auth0 B2C Starter, Stripe Standard (2.9% + $0.30 per payment), and Twilio SMS at $0.008 each. KYC- vendor costs are not in the comparison because me.ochk does not do KYC — sites that previously paid for KYC vendors keep paying them on their own terms; me.ochk replaces auth + cashback rails, not identity verification. Real invoices vary; we'll model your exact stack against your actual statements at /contact.
next step
Like the math? Go to /why#integrators for the integrator pitch and the five-step path, or jump straight to /integrate/quickstart for the drop-in code. Want OC to model against your actual usage? Email /contact with your stack and we'll send back a paired comparison within a business day.