Billing

Client billing lives at /billing. You pay marketplace providers for compute — not the NodeRings platform subscription (that is for provider orgs only).

Dashboard shortcut: /dashboard?tab=billing.

Tabs

Tab	URL	Purpose
Invoices	`?t=invoices-documents`	PDF/HTML invoices for your org
Payments	`?t=payments`	Payment history and status
Billable usage	`?t=billable-usage`	Usage breakdown (UI may be limited while product evolves)
Payment methods	`?t=payment-methods`	Cards and default payment method
Subscriptions	`?t=subscriptions`	Active subscriptions to provider plans
Subscription usage	`?t=usage`	Meters for usage-based subscriptions

Payment methods

A default payment method is required before you can launch a VM from the marketplace.

Add a card

Payment methods tab → Add payment method → complete Stripe flow.

Set default

Mark one method as default. Charges for new VMs and renewals use this method.

If launch fails with a payment error, see Troubleshooting → Payment method.

How charges work

Plan billing type	When you are charged
Subscription (fixed)	At the start of each billing period for the plan base price
Usage-based	Metered over the period (hourly compute, addon usage), invoiced at period end

Purchasing a VM typically creates a subscription (or usage record) linked to that asset. Addons (extra IPv4 addresses via Additional IPv4 addresses, backups, snapshot storage) bill according to their template and the plan's billing type.

Invoices and payments

Invoices list documents you can download. Payments shows charges succeeded, failed, or refunded. Failed payments may suspend new launches until resolved.

What clients do not see

Provider-only billing surfaces are hidden or redirect for client orgs:

Payout / revenue dashboard
Customers (end users who bought from you)
Platform plan upgrade (NodeRings seller subscription)

If you operate as a provider too, switch to a provider org for those views — Provider Guides → Billing.

Marketplace — launch VMs
Get started → Payment method