Product documentation · v0.1

The boundary is the product.

Zoryox starts with a useful, auditable service-credit ledger. On-chain verification and future card infrastructure are separate layers with separate gates.

ZORYC Credits

Account-bound service credits for eligible Zoryox software and services.
USD Checkout is settled before paid Credits are issued.
No peer-to-peer transfer, DEX, cash redemption, yield, or card funding.

Billing lifecycle

Top up: signed Stripe event → ledger recharge → mint outbox.
Use: reserve → settle actual usage → burn outbox.
Failure: release the reservation; refunds revoke paid Credits or enter manual review.

Zoryox Spend

Separate USD cent balance for a future regulated card program.
Partner settlement funds Spend; authorizations reserve, capture, or release it.
ZORYC and Spend are separate assets with separate reconciliation.

Current API contract

POST /v1/zoryox/credits/top-up-sessionGET /v1/zoryox/credits/balance/...POST /v1/zoryox/credits/reservationsPOST /v1/zoryox/credits/reservations/:id/settlePOST /v1/zoryox/credits/reservations/:id/releasePOST /v1/zoryox/credits/spend

These contracts are internal bearer-token APIs behind billing-service. The browser never receives a service token; the public console stays fail-closed until a server-side account session and product membership are enabled.

Before public launch

US legal classification, customer terms, Stripe review, contract audit, wallet custody, chain reconciliation, KYC/AML, card partner approval, and PCI scope remain required gates. The zoryox.com domain and Cloudflare/NPM TLS path are live and monitored separately.

Read the draft legal baseline →