GENESIS ACCESS
One account. One entitlement path. Your choice of payment rail.
Every self-serve Genesis purchase resolves here first so identity, payment evidence, and access stay attached to the same account. Card checkout is account-bound server-side. Wallet payments require a wallet you explicitly linked and are activated only after the chain transaction independently verifies.
NO PRIVATE KEY CUSTODYNO REDIRECT-BASED ENTITLEMENTACCOUNT-BOUND ACCESSVERIFIED SETTLEMENT
SELECTED ACCESS · —
Resolving access…
—
Loading the canonical commercial projection.
A payment provider or wallet can move value; neither can grant Genesis authority. Access becomes active only when the commercial entitlement ledger records verified payment evidence for this account.
CANONICAL PLANS
Choose where to start
YOUR ACTIVE ACCESS
Entitlements on this account
Checking account-bound access…
EDGE MESH WEB
Account membership and device state
Checking server-verified membership…
PAYMENT PATH
What happens when you pay
1 · Identity
Your authenticated Genesis account is the entitlement subject. The browser cannot substitute a different account id.
Your authenticated Genesis account is the entitlement subject. The browser cannot substitute a different account id.
2 · Payment
Use configured Stripe Checkout or explicitly authorize an exact transaction from a wallet whose ownership you verified.
Use configured Stripe Checkout or explicitly authorize an exact transaction from a wallet whose ownership you verified.
3 · Verification
Stripe must deliver a signed webhook, or the configured chain adapter must independently verify payer, recipient, amount, calldata, success, and confirmation depth.
Stripe must deliver a signed webhook, or the configured chain adapter must independently verify payer, recipient, amount, calldata, success, and confirmation depth.
4 · Access
Only verified settlement can transition the entitlement to ACTIVE. Redirects, screenshots, and client-side claims do not.
Only verified settlement can transition the entitlement to ACTIVE. Redirects, screenshots, and client-side claims do not.