PRIVATE ALPHA DOCUMENTATION
Build against what is live today.
billing.io is in pre-launch verification. The dashboard, hosted checkout, watch-only chain watcher, and Stripe usage pipeline are deployed. Public API-key access and broad chain coverage are not yet published.
Current scope
The private alpha is intentionally narrow while real-chain end-to-end evidence and legal review are completed.
| Network | Token | Status |
|---|---|---|
| Tron | USDT | Implemented; final low-value live payment evidence pending |
| Arbitrum | USDC | Implemented; final low-value live payment evidence pending |
| Other chain/token pairs | — | Not available in the private alpha |
Private-alpha integration flow
- 1
Create an account and complete organisation onboarding in the billing.io dashboard.
- 2
Add an account-level extended public key in Wallets. Never provide a seed phrase or private key.
- 3
Create a hosted checkout for Tron USDT or Arbitrum USDC from the authenticated dashboard.
- 4
Open the hosted checkout and send the exact amount to the generated deposit address.
- 5
billing.io detects and confirms the payment, then records the metered billing event.
- 6
Verify the transaction and reconciliation result before using the flow with a customer.
Security boundary
Watch-only and non-custodial
The chain watcher derives deposit addresses from a merchant-owned account-level public key. It does not receive a seed phrase or private key and cannot move merchant funds. Payments settle directly to addresses controlled by the merchant.
Report security issues privately to isaac@contracts.io. Do not email wallet secrets, live credentials, or private keys.
Public API and SDK status
A stable public bearer-token API, versioned SDK contract, and production API hostname are not published yet. Do not build against undocumented dashboard endpoints. Design partners receive a reviewed integration contract directly during onboarding.