Requirements for the Unified purchase flows

Summary

This issue is to collect all feedback around the checkout purchase flows and have is documented in one place.

Requirements

Must haves

All products

• Capture subscription details:
  • GitLab plan
  • Group (not on Self-Managed)
  • Seats
• Customer information:
  • Billing address
  • Company name
  • Tax ID (if applicable based on country)
• Payment information:
  • New card/customer:
    • Cardholder name
    • card number
    • expiration date (MM/YY)
    • CVV
  • Existing customer:
    • Show dropdown with two options:
      • Add new credit card
      • Select existing card
• Subscription term dates
• Taxes
• Subtotal
• Final total
• List prices in USD (reference)
• Acceptance of privacy policy and TOS
• Promo code entry (for promotions)

Self-managed Premium/Ultimate

• Show GitLab version 14.1 or later required. (reference).
• Plan selection
• Enter seat quantity
• Information about overage billing (QSR)

SaaS Premium/Ultimate

• Plan selection
• Select group
• Enter seat quantity
• Information about overage billing (QSR)

Compute minutes

• Enter quantity of compute minute packs
• Display group information (group that purchase will apply to)

Storage

• Enter quantity of storage packs
• Display group information (group that purchase will apply to)

Duo

• Plan selection
• Enter seat quantity
• Information about SM version requirements (SM only)
• Display group information (SaaS only)

Community programs

• Enter community programs coupon code
• Skip payment entry ($0 subscription, no payment required)
• Select group (SaaS only)

Nice to haves

• Ability to purchase multiple products (not MVC, but something to consider as we build out the checkout template)

General feedback