Overview
...
Context
When the user places the order (presses the button), the button state changes to a loading state, blocking the user to press it again. However, the rest of the page do not change or blocked, having the possibility to return to the previous step in the middle of the process (press X to close).
Permitting the user to go back during the payment process is a risk, because the payment process is an important step in which Payment and RBI platforms are involved. Their interruption leads to several errors, depending on when the user closes the page. Once the user comes back to the Checkout, these errors may occur:
If the user presses the Continue button to place the same order again, the page informs the user that they have already placed the order (duplication) when it has not.
...
Goal
By blocking the ability to close the page during payment processing, it is expected that there will be a significant reduction in the volume of errors and, consequently, a decrease in Customer Support incidents.
...
| Info |
|---|
This feature has a flag called Enable Processing Payment Splash Screen which should be enabled to be used. Key of feature: enable-processing-payment-splash-screen PSP’s can enable this feature with this flag: Paycomet, Paymark, Adyen To enable, this flag please contact your CSM. PSP’s enabled all the time (There isn’t flag): Cybersource, Checkoutdotcom For others PSP’s there isn’t this feature. |
...