Instantly share code, notes, and snippets.

Embed
What would you like to do?
Billing flow proposal

Proposal: Single flow to unlock Premium features

User actions

  1. User identified by john.doe@gmail.com registers upon https://case.unee-t.com/
  2. User wants to unlock premium features
  3. User goes to or is directed to /billing form which asks for the billing contact information. This looks like https://config.webconverger.com/quote/ Lets assume the billing contact is billing@example.com.

Billing actions

  1. Once the form is submitted an invoice is raised and submitted to billing@example.com, e.g. https://case.unee-t.com/account/billing@example.com
  2. On this URL, the request to make payment is made and the associated users are listed, in this case, john.doe@gmail.com for approval.
  3. Billing makes payment and approves that john.doe@gmail.com is part of the organsation.

User actions

  1. john.doe@gmail.com is notified his account is now premium and features are unlocked.

Notes

billing@example.com and john.doe@gmail.com could be the same person. Doesn't matter.

A billing organisation can support several accounts, by tweaking the email address:

An account is identified as a customer in Stripe. Subscriptions are not limited to a single type, different plans and quantities of that plan can all be accomodated under customer.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment