Billing & the unit wallet
What costs units, how the wallet is topped up, and how members' own payments flow.
Two separate money flows run through a tenant, and keeping them apart avoids most of the confusion:
- The unit wallet — what the tenant pays the platform for metered actions, chiefly sending email through the platform's own transport.
- Member and attendee payments — what people pay the tenant for membership dues and paid events.
The unit wallet
Sending email through the platform's shared transport costs units per email. Before a campaign dispatches, the balance is checked against the number of pending recipients — an underfunded send is refused up front rather than stopping halfway through.
Bringing your own SMTP
A tenant that configures its own SMTP under Configuration → Communication sends through that transport instead, and those sends cost no units. The wallet check is skipped entirely.
Member and attendee payments
Tenants collect through their own payment configuration, so money reaches the
organisation's account rather than the platform's. Paid events hold a
registration at pending until payment reports paid; membership invoices
advance the member's dues date when settled.
Use cases
Budgeting a newsletter
A monthly newsletter to 4,000 members is 4,000 units. Top up ahead of the send, or move to your own SMTP if volume makes that cheaper.
Charging for a conference in two currencies
Price each tier per currency across the currencies the tenant has enabled; attendees pay in theirs.