Appearance
Enterprise and invoicing
Self-service plans are paid by card through Stripe. For organisations that buy differently, the platform supports invoicing, negotiated terms and a late-payment policy that is set per organisation rather than imposed.
Invoice billing
An organisation can be billed by invoice instead of card, on net terms of 15, 30 or 60 days, with a purchase-order number carried on every invoice. Stripe issues the invoice and its reminders; payment by bank transfer or card on the hosted invoice page clears it, and a payment that arrives some other way can be recorded by an operator.
Late payments, staged and told in advance
A failed payment or an overdue invoice never cuts access on the spot. The default schedule is four stages, each announced by a banner in the app and an email to the organisation's owners and admins, with the date of the next step:
| Day | Stage | Access |
|---|---|---|
| 0 | warning | full |
| 7 | final warning | full |
| 14 | limited: no overage, no new API keys, no plan changes except paying | the plan's allowance keeps working |
| 21 | suspended: Free plan's limits until paid | nothing is deleted; read, export and delete always work |
Paying at any stage restores full access at once.
Terms for a partner or a larger organisation
The schedule above is a default. For an organisation on negotiated terms we can set, with an audit trail and the contract reference on every change:
- longer stage days, or no automatic suspension at all;
- which limits apply in the limited stage, for example keeping API keys working;
- allowance and rate-limit overrides beyond the listed plans;
- invoice terms and the PO number.
Two safety limits always apply, so no organisation is ever cut off from what it already pays for and none runs up an unbounded unpaid tab: a maximum number of days overdue, and a maximum amount outstanding, past which overage stops while the plan's own allowance keeps working.
How a deal becomes an account
Enterprise deals are sold, billed and served by three systems, each in charge of one kind of fact: the deal (account, contract, price, renewal) in the CRM; the money (subscription, invoices, payments) in Stripe; and access (plan, seats, allowance, overrides) in MatterWave. Every commercial change reaches MatterWave through one audited path, so the seats you pay for are the seats you get.
Talk to sales
To start: sales@matterwave.dev.