Stripe Payment Processing

LEAD integrates Stripe in order to process payments and generate invoices for premium items, and to manage subscriptions which charge Users on a recurring interval.

Premium Learning Path Example

Use case: User wants to buy Premium Learning Path

1. User visits checkout page in LEAD

2. User enters payment information in embedded Stripe form and submits
   All information remains secure and encrypted

3. A Payment Intent is created in Stripe, with the following information:

   1. Charge amount

   2. User’s Stripe Customer
      Note: Stripe Customers are created and assigned to Users upon registration

   3. Description containing Learning Path information using the following format:
      “LEAD - Premium Learning Path - {Learning Path Name} (ID {LP ID})”

   4. Metadata:

      1. platform : LEAD

      2. learning_path_id : {LP ID}

      3. user_id : {User ID}

4. The credit card info from the form submission is used to pay the Payment Intent above and Stripe sends feedback for the charge to a configured webhook

5. LEAD receives the information from the webhook and unlocks the Learning Path for the User

6. User receives feedback that their payment was successful and is automatically redirected to the unlocked Learning Path’s curriculum view

Premium Group Registration Example (One-time Payment)

Use case: User wants to pay a Group’s required registration fee to become a member

1. User visits Group Registration page in LEAD

2. User enters payment information in embedded Stripe form and submits
   All information remains secure and encrypted

3. A Payment Intent is created in Stripe, with the following information:

   1. Charge amount

   2. User’s Stripe Customer
      Note: Stripe Customers are created and assigned to Users upon registration

   3. Description containing Group information using the following format:
      “LEAD - Premium Group - {Group Name} (ID {Group ID})”

   4. Metadata:

      1. platform : LEAD

      2. group_id : {Group ID}

      3. user_id : {User ID}

4. The credit card info from the form submission is used to pay the Payment Intent above and Stripe sends feedback for the charge to a configured webhook

5. LEAD receives the information from the webhook and marks the Group Registration as paid for the User

6. User receives feedback that their payment was successful and can access their receipt via the Group Registration page

Product Subscription Example

Use case: User wants to subscribe to a Product

1. User visits Subscribe and Save page in LEAD

2. User selects a Product to subscribe to and is redirected to the Subscription Checkout page

3. User enters payment information in embedded Stripe form and submits
   All information remains secure and encrypted

4. A Payment Method is created in Stripe and associated with the User’s Stripe Customer
   Note: Stripe Customers are created and assigned to Users upon registration

5. A Subscription is created in Stripe, with the following information:

   1. Product’s Price (charge amount and recurrence interval)

   2. Quantity

   3. User’s Stripe Customer

   4. Newly created Payment Method

6. The Subscription is created and paid for and Stripe sends event data related to Subscription creation to a configured webhook

7. LEAD receives the information from the webhook and tracks the Subscription

8. User receives feedback that their payment was successful and can manage their Subscription on a dedicated view in LEAD

Premium Group Registration Example (Recurring Payment)

Use case: User wants to subscribe to become a member of a Group

1. User visits Group Registration page in LEAD

2. User enters payment information in embedded Stripe form and submits
   All information remains secure and encrypted

3. A Payment Method is created in Stripe and associated with the User’s Stripe Customer
   Note: Stripe Customers are created and assigned to Users upon registration

4. A Subscription is created in Stripe, with the following information:

   1. Product’s Price (charge amount and recurrence interval)

   2. Quantity

   3. User’s Stripe Customer

   4. Newly created Payment Method

   5. Metadata:

      1. cart_id : {Cart ID}
         Note: The Cart is what LEAD uses to track the specific Group Registration data for the User

5. The Subscription is created and paid for and Stripe sends event data related to Subscription creation to a configured webhook

6. LEAD receives the information from the webhook, tracks the Subscription, and marks the Group Registration as paid for the User

7. User receives feedback that their payment was successful and can manage their Subscription on a dedicated view in LEAD

Additional notes:

• A Group that has Premium Type “Recurring” will have an accompanying Product in Stripe

• This Product is automatically created when the Group is created

• The Product has the following information set:

  • Name: “Group - {Group Name}”

  • Description: ‘Product for “{Group Name}” Group on {App Name} ({App URL})’

  • Metadata:

    • group_id: {Group ID}

• The Product has a Price associated with it, with the following information set:

  • Amount

  • Recurrence interval

  • Nickname: “Price for {Group Name} Group on {App Name} ({App URL})”

  • Metadata:

    • group_id: {Group ID}

Connected Accounts

If payments need to be disbursed to other accounts for purchases and subscriptions related to specified Groups, LEAD can facilitate this with the setup of Connected Accounts – this is detailed on the Stripe Connect page.