Skip to content

Billing · Beta

Billing on the money path.

Subscriptions, meters, invoices. Same key as Payments — so revenue and settlement share one ledger story.

Get StartedDocs

sub_01JXK · Pro

status
active
price
$49 / month
trial
14 days · ends Aug 25
next_invoice
Sep 11 · $49.00

Plans and prices sit on the same settlement path.

How it works

One key. Catalog to collection.

  1. 01

    Define catalog

    Plans, prices, meters as API objects your product owns.

  2. 02

    Subscribe

    Attach a customer. Trials and proration included.

  3. 03

    Collect

    Invoices settle on Vortex Payments — same money path.

Who buys this

Recurring revenue without a second payments stack.

For teams that already think in subscriptions and usage.

  • Founders

    Ship pricing experiments without wiring a separate billing vendor to a separate processor.

  • Developers

    Subscriptions, meters, invoices as API objects. Usage events that actually land on the invoice.

  • Engineering managers

    One integration surface for charge + subscribe. Fewer vendors. Cleaner ownership.

  • Business & ops

    Invoices draft, finalize, collect. Dunning when cards fail. Tax can ride with the charge.

Why Billing

Revenue that settles where payments settle.

Billing that shares the Vortex money path — not a parallel system.

  • Same key as Payments

    No dual onboarding. Catalog and collection live next to charges and settlements.

  • Meters that matter

    Usage events feed invoices. Metered products stop being a spreadsheet job.

  • Dunning included

    Failed collections retry. Ops gets a path — not a silent miss.

  • Tax-ready invoices

    Quote tax with the charge when you need it. Liability boundary stays explicit.

Use cases

Where Billing fits.

  • SaaS seats & plans

    Monthly and annual plans, trials, proration when customers change tiers.

  • Usage-based products

    API calls, seats overage, compute — meter events into the invoice line.

  • Hybrid pricing

    Base subscription + usage. One invoice. One settlement path.

  • Platforms billing end customers

    Your product bills customers; Vortex Payments settles under your brand.

Straight talk

Billing is beta on Payments.

Same honesty contract as the rest of Vortex.

  • Same API key as Payments.
  • Subscriptions, meters, invoices — not a full ERP.
  • Dunning retries on failed collection.
  • Tax is quoted with the charge; you remain liable.

Core

  • Subscriptions

    Plans, prices, trials, proration.

  • Meters

    Usage events that feed invoices.

  • Invoices

    Draft, finalize, collect. Dunning included.

Get a sandbox key.

Same key as Payments. Start with a plan or a meter.

Dashboard Docs