Eternet Portal Documentation
Billing
Current state
The page currently displays informational cards for plan, usage, and invoices. Its own copy says billing and wallet actions remain behind the Cloud API boundary; it does not currently demonstrate live invoice retrieval, payment, or wallet management.
Integration requirement
Live billing requires Cloud API contracts for account plan, metering, invoices, and payment actions, plus verified authorization and error handling. Do not present the static cards as live account data.
Billing information customers expect
A complete billing workspace would normally help an account owner understand the current plan, usage against allowances, invoices, payment state, renewal terms, and the effect of purchasing or changing resources. The current portal route reserves a place for this experience and displays cards labeled Current plan, Usage, and Invoices. Its own copy makes clear that those actions remain behind the Cloud API boundary. The cards are informational placeholders rather than live billing records. This distinction should be preserved in any product presentation so customers do not assume that an amount, invoice, plan status, or payment has been retrieved from their account.
Billing is sensitive account data. A production integration must bind every request to the authenticated organization and user permissions, avoid leaking invoices across tenants, and make currency, tax, billing period, and status explicit. Payment actions require strong confirmation and a clear record of the result. The UI should distinguish an invoice that is due, paid, overdue, void, or still processing only when the billing service returns those states. An optimistic success banner is not sufficient proof that a payment processor captured funds.
Integration needed to make it live
To turn the placeholder into a customer-ready module, the Cloud API needs stable endpoints for account plan, metered usage, invoice list and detail, payment methods, wallet or credit balance if applicable, and supported billing actions. The portal then needs typed response mapping, pagination, date and currency formatting, empty and failure states, authorization checks, and tests that cover denied access and duplicate submissions. Billing events should be traced to a transaction or invoice ID so support teams can reconcile the display with the authoritative system.
Because pricing may vary by resource, location, discount, or billing cycle, the Compute page’s frontend calculator should not be treated as a billing source. Any estimate must identify its assumptions and should be confirmed by the billing service before purchase. This keeps product comparison separate from actual account charges.
How to present the current state
For now, introduce Billing as a planned or reserved portal surface and show that the portal navigation has a dedicated location for account billing information. Be explicit that live usage, invoices, wallet actions, and payment workflows are not currently verified here. This honest framing prevents customer confusion and sets a clear integration roadmap. The customer value once connected is straightforward: account owners can understand costs and usage in context with the cloud resources and IoT workloads they operate. The Cloud billing service, not this page, must remain authoritative for balances, charges, and payment status.