So with the addition of DocuSign, it has extended the confirmation time when submitting a registration. We believe that this extended wait time, along with no indicator of anything happening has made users impatient while they wait for the registration to submit. Possibly causing them to spam click the confirm button. Lee discovered that there's a small window between once the registration is complete and when the user is navigated to the confirmation page that the confirm button becomes enabled again and the user can press it. This will create a duplicate credit card transaction if pressed, causing the user to be charged twice. Lee and I both reproduced this on staging several times with ease. The solution was to leave the button disabled(unless there's an error with submitting), as they will be redirected to a different page. I also went ahead and added new text and a loading indicator to better reflect the submitting state.
So with the addition of DocuSign, it has extended the confirmation time when submitting a registration. We believe that this extended wait time, along with no indicator of anything happening has made users impatient while they wait for the registration to submit. Possibly causing them to spam click the confirm button. Lee discovered that there's a small window between once the registration is complete and when the user is navigated to the confirmation page that the confirm button becomes enabled again and the user can press it. This will create a duplicate credit card transaction if pressed, causing the user to be charged twice. Lee and I both reproduced this on staging several times with ease. The solution was to leave the button disabled(unless there's an error with submitting), as they will be redirected to a different page. I also went ahead and added new text and a loading indicator to better reflect the submitting state.