Recurring billing that holds up under fifty sets of state rules.

Flat plans, per seat pricing, tiered and volume usage, hybrid base plus overage, annual prepay with monthly true ups and negotiated enterprise terms, all defined in an admin catalog rather than hard coded. Product managers can launch a new price point or grandfather existing customers on an old one without a developer touching the release. Every price change is versioned, so an invoice from last year can always be explained against the price that applied then.

Upgrades, downgrades, seat additions and mid-cycle switches between monthly and annual terms calculate credits and charges to the day, with a preview the customer sees before confirming. Rules for when a downgrade takes effect, immediately or at renewal, are configurable per plan.

An event pipeline that ingests API calls, minutes, gigabytes, messages or any unit you bill on, deduplicates retries, applies rating rules and rolls usage into the invoice at period close. Customers watch a live meter in the portal so overage never arrives as a surprise.

Retry schedules tuned by decline code, card updater services from the networks, network tokens where your processor supports them, and reminder emails and in-app banners that send the customer to a one-tap card update page. Grace periods and service limits on past due accounts follow rules you set.

Since South Dakota v. Wayfair in 2018, states can require remote sellers to collect tax once they pass an economic nexus threshold. Whether a digital subscription is taxable at all differs by state. We connect a tax engine such as Avalara or Stripe Tax, track nexus by state and store the tax decision on every invoice line.

Clear disclosure of renewal terms beside the checkout button, separate consent capture with a stored record, confirmation emails, renewal and price change reminders, and online cancellation available through the same channel the customer used to sign up. Rules are applied by the customer's state, so stricter requirements can switch on where they apply.

Customers view plans, change seats, download invoices, update cards and cancel from the web or from your iOS and Android app. Where in-app purchase rules apply on Apple and Google stores, we plan the purchase flow with you so app review and billing stay consistent.

Invoices, payments, refunds and credit notes post to QuickBooks, NetSuite or Xero, and deferred revenue schedules follow ASC 606 logic your controller agrees in advance. Monthly recurring revenue, churn and expansion figures come from the same records the ledger uses.

Larger American buyers rarely pay by card. The platform issues invoices with purchase order numbers and net payment terms, accepts ACH debits and credits, and records the recurring debit authorization that Nacha rules expect before you pull funds from a customer's bank account. Payments received by wire or check are matched to open invoices so collections staff see a true aging report rather than a guess.

Card entry runs through your processor's hosted fields or payment page, so raw card numbers never reach your servers. That design keeps your PCI DSS scope small, usually to a self assessment questionnaire rather than a full on-site assessment, and we document the data flows your assessor will ask about.