...
When the user places the order (presses the button), the button state changes to a loading state, blocking the user to press it again and. 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 the appearance of several errors, depending on when the user closes the page. Once the user come 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.
The payment process was completed and registered as paid in Paycomet and the order was charged to the user, but the Order was not registered in RBI systems (DMP).
Important: Everytime Every time the user continues the purchase from the Checkout to the Payment page, a unique Transaction ID is created to track the order. So, if the user cancels the payment (eg.: selects Bizum but presses the “cancel” button), they return to the Checkout Page to create a new Transaction ID.
...
Importance | What do we want to measure? | Description | How are we measuring it? |
|---|---|---|---|
Primary metric | Number of errors produced while processing payment | We would like to decrease this number. Amplitude We expect to see a higher number of conversions. | Amplitude |
Primary Metric | Number of incidences in Customer Support related to Payments issues | We would like to decrease this number. | ?? |
...
About Online/Mobile Payments Apps:
In the PayPal, Waylet, Apple and Bizum user cases in which an i-Frame (App) or a new window is open opened (Desktop), if the user closes or cancels, where do they go? Do they must go to the Checkout page or can they stay on the Order Payment page?
If a PayPal, Waylet, Apple or Bizum payment was not successfully processed, does the user have to return to the Checkout to create a new Transaction ID instead of staying in the Order Payment to select another Payment method?
Is there any other platform to consider besides the Whitelabel-apps for this task?
...
We identified 2 common patterns to block the user from going back during the payment process:·
Pattern 1: the loading state of the payment processing is displayed in a different page (loading page)
Pattern 2: the loading state of the payment processing is displayed on the same page but blocking the whole screen (disabled state). We found two ways:
Loading icon and a black transparency mask covering all screen to indicate the user the screen is blocked (disabled) and they are not able to do any action:
...