Skip to main content
Every Aria Compute account holds a prepaid wallet. You top it up with a supported payment provider, and metered usage is drawn from the balance. The wallet currency is fixed by the site domain, regardless of the UI language you browse in.

​
Currency

If you browse the China site in English, prices are still CNY. Wallets are not shared between the two sites: each has its own balance, transactions, and invoices.

​
Top-up flow

  1. The client fetches available providers from GET /api/payments/providers.
  2. You start a top-up with POST /api/billing/payments and receive a Stripe checkout URL, a WeChat Pay QR code, or an Alipay QR code.
  3. You complete the payment in the provider’s flow.
  4. The provider sends a webhook to POST /api/payments/webhook/{provider}; the backend credits the wallet.
  5. You can poll GET /api/billing/payments/{id} for status.
Providers are disabled until their credentials are configured. Use GET /api/payments/providers to see which ones are live in your environment.

​
Usage

Usage is metered and reported via GET /api/billing/usage. Every model call, model download, and GPU-hour is priced against the published rates from GET /api/pricing and drawn from your wallet. You can inspect the resulting transactions via GET /api/billing/transactions.

​
Invoices and receipts

Every paid payment can be turned into a document you can download and store.
  • China site (ariacompute.cn): WeChat Pay and Alipay payments can be turned into an e-invoice (电子发票). Request one with POST /api/billing/invoices and download it from GET /api/billing/invoices/{paymentId}/download. One invoice per payment, idempotent.
  • International site (ariacompute.com): Stripe payments have receipts you can pull from GET /api/billing/receipts/{paymentId}/download.
Both download endpoints accept the session token via Authorization: Bearer or the ?token= query parameter so that browser links work directly.