Move workflows to relevant pages and delete GitLab purchase workflow

1. Click the `Pay for invoice` button on the invoice.

1. Complete and submit the payment form.

Unlike adding a credit card during the purchase flow, payment methods entered here are not stored for future purchases, as this is an [on-session](https://support.stripe.com/questions/what-is-the-difference-between-on-session-and-off-session-and-why-is-it-important)/[one-time](https://knowledgecenter.zuora.com/Zuora_Payments/Process_payments/Payment_Pages_2.0/J_Implement_Payment_Pages_2.0_to_support_one-time_payment_flows/Z_Implement_one-time_payment_flows_for_processing_payments_in_India) payment. However, this process accepts cards that [require 3DS authentication on all transactions](/handbook/support/license-and-renewals/workflows/troubleshoot_purchases_on_gitlab.md#3d-secure-authentication-3ds) and [cards issued in India](https://docs.gitlab.com/subscriptions/gitlab_com/gitlab_subscription_troubleshooting/#error-transaction_not_allowed).

Unlike adding a credit card during the purchase flow, payment methods entered here are not stored for future purchases, as this is an [on-session](https://support.stripe.com/questions/what-is-the-difference-between-on-session-and-off-session-and-why-is-it-important)/[one-time](https://knowledgecenter.zuora.com/Zuora_Payments/Process_payments/Payment_Pages_2.0/J_Implement_Payment_Pages_2.0_to_support_one-time_payment_flows/Z_Implement_one-time_payment_flows_for_processing_payments_in_India) payment. However, this process accepts cards that [require 3DS authentication on all transactions](/handbook/support/license-and-renewals/workflows/customersdot/troubleshoot_errors_while_making_purchases/#3d-secure-authentication-3ds) and [cards issued in India](https://docs.gitlab.com/subscriptions/gitlab_com/gitlab_subscription_troubleshooting/#error-transaction_not_allowed).

Additionally, existing payment methods cannot be accessed in this flow.

Alternative payment methods aren't supported at this time, so requests to do so need to be [passed over to Accounts Receivable team](#requests-to-make-a-paymentpayment-failed)

Sentry for a relevant error and file an issue in the

[CustomersDot tracker](https://gitlab.com/gitlab-org/customers-gitlab-com/-/issues/) as necessary.

### 3D Secure Authentication 3DS

> Transaction declined.generic_decline - Your card was declined

Our product purchase integration with Zuora does not support the authorization of payment methods that mandate [require 3DS authentication on all transactions](https://docs.stripe.com/testing#authentication-and-setup).

At this moment, an alternative is to ask the user to use a different card. Additionally, you can [reach out to Sales](/handbook/support/license-and-renewals/workflows/working_with_sales#specific-workflows-to-pass-to-sales) to offer the user [payment through invoice](/handbook/support/license-and-renewals/workflows/billing_contact_change_payments.md#paying-invoices).

> card_error/authentication_required/authentication_required

Our product purchase integration with Zuora does not support the authorization of payment methods that mandate [require 3DS authentication on all transactions](https://docs.stripe.com/testing#authentication-and-setup). Such transactions will fail after the card is added.

At this moment, an alternative is to ask the user to use a different card. Additionally, you can [reach out to Sales](/handbook/support/license-and-renewals/workflows/working_with_sales#specific-workflows-to-pass-to-sales) to offer the user an alternative payment method.

> invalid_request_error/setup_intent_authentication_failure

The 3DS authentication failed.

The first option is to request the user to try again, or with a different another card.

You can also [reach out to Sales](/handbook/support/license-and-renewals/workflows/working_with_sales#specific-workflows-to-pass-to-sales) to offer the user an alternative payment method.

### India issued cards

> Transaction declined.402 - [card_error/card_declined/transaction_not_allowed]

> Your card does not support this type of purchase.

Please direct the customer to [the troubleshooting page](https://docs.gitlab.com/subscriptions/gitlab_com/gitlab_subscription_troubleshooting/#error-transaction_not_allowed) to purchase through a reseller or [reach out to Sales](/handbook/support/license-and-renewals/workflows/working_with_sales#specific-workflows-to-pass-to-sales) to offer the user [payment through invoice](/handbook/support/license-and-renewals/workflows/billing_contact_change_payments.md#paying-invoices).

### Getting error message from Sentry

To find the error specifically related to a customer on sentry, try the following:

Sometimes a customer reports that they did not receive an email from the portal, such as a password reset request or new account confirmation.  GitLab uses Mailgun as a service to send outgoing mail. We can login to Mailgun to view the message logs, and when appropriate, remove suppressions.

The general workflow that Support uses for this process is documented in the [Support handbook page on confirmation emails](/handbook/support/workflows/confirmation_emails#check-mailgun), and that page has a full description on navigating the Mailgun dashboard and searching through the logs.

The general workflow that Support uses for this process is documented in the [Support handbook page on confirmation emails](/handbook/support/workflows/confirmation_emails/#checking-mailgun-logs), and that page has a full description on navigating the Mailgun dashboard and searching through the logs.

The process here is much the same, but since we are investigating mail from CustomerDot, in Step 4 of the general workflow ensure that `customers.gitlab.com` is selected as the domain to search under.

=> "{\"status\":\"success\",\"message\":\"namespace members are now enabled to run compute minutes\"}"

```

### Handling failed credit card verifications

To use compute minutes on shared runners, customers might need to verify their identity. Some customers might need to use a credit card for that purpose. If a customer contacts Support to report that they received an error when they tried to use their credit card for verification, then you should follow the steps below. Please note that the verification process does not place any charge on the credit card. Instead uses a one-dollar authorization transaction.

1. Respond to the ticket by using the Zendesk Macro `Support::L&R::Credit Card Authorisation Failed'

1. If the customer comes back after 24 hours and confirms they are still unable to proceed, but they have verified their credit card works outside of GitLab.com, then refer them to Trust and Safety for further guidance. The Trust and Safety Team contact details can be found in the handbook: [Working with the GitLab Trust and Safety Team](/handbook/security/security-operations/trustandsafety/#working-with-gitlab-trust-and-safety-team).

1. Follow these [steps to ensure their GitLab.com account is linked](https://docs.gitlab.com/subscriptions/customers_portal/#change-the-linked-account).

1. Follow these [steps to update the linked namespace](https://docs.gitlab.com/subscriptions/gitlab_com/#change-the-linked-namespace).

If a customer is an [Unlinked CustomersDot account](/handbook/support/license-and-renewals/workflows/troubleshoot_purchases_on_gitlab/#unlinked-customersdot-account-for-purchases-via-sales) and you need to act on their behalf, you can try [Force Association of the subscription](/handbook/support/license-and-renewals/workflows/customersdot/mechanizer#force-associate) as a workaround.

If the customer's CustomersDot account is not linked to their GitLab.com account (`uid` and `Gitlab user` in the CustomersDot account is empty) and you need to act on their behalf, you can try [Force Association of the subscription](/handbook/support/license-and-renewals/workflows/customersdot/mechanizer#force-associate) as a workaround.

If neither of the above resolves the issue for the customer, [contact the on-call Support Manager](#optional-contact-the-on-call-support-manager) requesting further guidance.