Test moving credit card verification as a requirement of namespace creation

Problem

GitLab needs a mechanism for preventing abuse. As we update free usage limits, we need to ensure that when limits are enforced and the namespace is verified to prevent abusive usage. This will help combat rampant abuse of our pipeline servers as well as improve the verification process for being able to utilize pipelines in the first place.

Proposal

Move cc verification into namespace creation.

Test Details

Target

50% of new users and 50 % of new users creating a new namespace should be assigned to the test group.

Metrics

1. Sign-up completion rate
2. Namespace creation completion rate
3. Conversion rate
4. SpO
5. Average user count per namespace
6. Each flow should be able to be analyzed separately (e.g. completion rate for the sign-up flow vs completion rate for namespace creation flow).
7. We should record which flow was used to create the namespace (e.g. sign-up flow vs namespace creation flow)

Proposed Solutions

In App:

• Add an additional page before the "Create Group" step that collects users credit card information.
• Full UX flow can be found here.

Step 1	Step 2

In First Mile:

• Add an additional section to the "Create or import your first project" page that collects users credit card information.
• Full UX flow can be found here.

Step 1	Step 2

Design File

Roll out

Issues:

1. https://gitlab.com/gitlab-org/gitlab/-/issues/350251
2. gitlab-org/gitlab#349857 (closed)

Rollback steps

In case of problems, this experiment can be disabled by running the following Chatops commands:

/chatops run feature set require_verification_for_group_creation false
/chatops run feature set require_verification_for_namespace_creation false