Docs
User Billing Payor
Each user has a User Billing Payor setting in the billing options section of their profile. It applies to the user, not to any single tool.
| Option | What happens |
|---|---|
| Company (default) | Every tool they buy is billed using the organization’s billing information |
| User | Every tool they buy is billed using the user’s own billing information. The user is prompted to add it |
This lets a company pay for its employees’ tools while contractors pay for the tools they are asked to use. It also lets outside users in a carrier and agency relationship load their own billing information when collaborating on large datasets.
The setting is stored on each user’s membership (billing_payor: COMPANY or USER). Stripe customers are set up as:
- One per organization
- One per user, if that user is a payor
Billing and Usage pages
Add the location in settings for adding payment methods and managing subscriptions, similar to Zapier. For this build:
- Add the HTML pages to the Django customer app: Billing and Usage, Payment Method, and Subscriptions.
- Connect the Payment Method page to our Stripe account to store billing information.
- For users set to “User Billing Payor”, show a way to add their personal billing information in settings.
- Connect the roles from Section 04 to the company org’s Billing and Usage section.
The subscriptions section will later become more complex, because we will sell access in small individual products, similar to how AWS does. For now, this is enough to set up the pages.
Billing information
Handle invoicing information, such as tax info and billing address, through Stripe as much as possible. If that isn’t possible, practical, or is too scary for users, build a custom view in our app, send the info to Stripe, and create PDF invoices.
