Billing

Billing blocks are the screens where a product asks for money and accounts for it: the pricing page, the comparison, the upgrade, the subscription, the usage, the invoices and the checkout. Orvain's Billing family holds seven, all priced around the team: a pricing table where the number of editors picks the plan, a plan comparison with your team marked on every limit, an upgrade card for the moment a seat runs out, a subscription panel that changes seats in place, usage billed day by day with a spending cap, a year of invoices beside the open one, and a checkout whose order tray becomes the receipt.

What they share is that every number explains itself. A total says what it is made of, a proration says which days it covers, a projection says what pace it assumes and a failed payment says when it will be tried again. People pay more calmly when they can see why, so the blocks put the reason next to the amount and let the amount change in place as they change the team, the period or the cap.

7 blocks

Pricing table

A pricing page priced per editor, where the team size picks the plan

Plan comparison

Comparing every limit and feature across plans for your team size

Upgrade card

Asking to upgrade at the moment a seat limit is hit

Subscription panel

Managing the plan you are on, and changing the team in place

Usage billing

Showing metered usage and the bill it is heading for, day by day

Invoices

A year of invoices beside the open one, with a failed payment to fix

Checkout

Paying for a plan, with the order turning into the receipt

01

Using Billing

Reach for it when

  • Pricing priced per seat, where the right plan depends on how many people will use it.
  • Account billing pages, where people change seats, read usage and fix a failed payment without writing to support.
  • Metered products, where the bill moves during the month and people want to know where it is heading.
  • A self-serve checkout for a plan, with promo codes, VAT and a receipt someone can forward to finance.

Reach for something else when

  • A shop with a cart of products. The checkout here pays for a plan and a team, not a basket of items.
  • One flat price with no seats or usage. A single price and a button says it all.
  • Enterprise contracts negotiated by hand. Point those to sales; the pricing table's Enterprise line does that.
02

Where it shows up

01

Design tool pricing

A team of two starts free on Starter. When a fourth editor is invited, the upgrade card appears with the person waiting, shows the limits growing to Pro's and charges only the twelve days left in the month, so the invite goes through in one step.

02

API platform billing

Usage billing shows API calls day by day against the included 100,000, with the day the allowance ran out flagged and a projection to the month's end. A spending cap dragged along the bill stops the projection where finance wants it, and the invoices list shows October's declined payment with Pay now.

03

Questions

How should a pricing page handle per-seat pricing?

Ask for the team size first and price every plan for that team, rather than listing a per-seat price people have to multiply. The plan that fits becomes the obvious choice, a plan that is too small says so instead of letting someone buy it, and the per-seat price moves to a caption under the total.

What should an upgrade prompt show?

All blocks
The Orvain Dispatch

Premium components, free in your inbox.

Join the Orvain Dispatch and get production-ready components, free to keep: React and Vue code plus the Figma frame, yours to ship.

Just components, never spam. You can unsubscribe anytime.