Invoices & Payment
Download invoices, change payment method, handle failed charges.
Every charge has a downloadable PDF — Stripe-hosted, so the PDF format is whatever Stripe ships, which is what your accounting team is used to. Settings → Billing → Invoices. We keep history for seven years, which matches what most jurisdictions require for financial records.
Payment method
Card via Stripe Checkout. To swap a card, Settings → Billing → Update payment method opens the Stripe-hosted form. We never see your card number; Stripe holds the token, we hold a reference.
If you're on Enterprise with invoice billing, the Update payment method link is hidden — you're on net-30 against bank transfer, and changes go through accounts receivable. Email [email protected] if you need to update banking details.
When a charge fails
Stripe runs its smart-retry schedule across four days. You get email at every attempt. After the final retry fails, the org flips to past_due:
- Read access to historical data continues — the dashboard isn't locked.
- New ingestion pauses. The collector keeps trying but new snapshots are dropped.
- Alerts pause. (You don't want a billing problem to also page you about a missing-snapshots alert.)
To recover: update the payment method and click "Retry now." Service resumes within five minutes — we keep the org config alive during past_due, so nothing has to be rebuilt.
Refunds and proration
Upgrades are prorated automatically. If you go from Pro to Business mid-cycle, we charge the difference for the remaining days, not a full month. Downgrades work the other way: you keep the higher tier until the cycle ends, then drop down — no refund. If you need a one-off refund (bought wrong tier, double-paid), email [email protected] with the invoice number and we'll process it through Stripe within a couple of business days.
Tax
VAT and GST are applied automatically based on your billing country. EU B2B customers can enter a VAT number for reverse-charge; we validate it against the EU VIES service at save time. If VIES is down (it has bad days), retry — we don't store stale validations.