Gpay and Apple pay loading the popup even if the woocommerce validation fails

Hello @scrivio

Could you supply us with a link where we could test out this behaviour?

Kind regards,
Matas from Revolut Business

you can simulate an order on gricon.it, the form validation is being triggered but the popup of gpay/apple pay still loads over the screen, the customer makes the payment but the order won’t process. Kinda a pain.

Also, since the last update there are tons of problems with payment by credit card during revolut order and client creation. Like 1 order out of 4 has payment problems.

Here are some logs:
2024-11-18T19:11:34+00:00 Errore Failed request to URL PATCH https://merchant.revolut.com/api/1.0/orders/673B9124-3848-ACFB-9BAD-6676F7F919DC 2024-11-18T19:11:34+00:00 Errore {“timestamp”:1731957094601,”errorId”:”c66232ae-7263-4285-8f43-e80d2410239a”} 2024-11-18T19:11:34+00:00 Errore Something went wrong: PATCH https://merchant.revolut.com/api/1.0/orders/673B9124-3848-ACFB-9BAD-6676F7F919DC {“timestamp”:1731957094601,”errorId”:”c66232ae-7263-4285-8f43-e80d2410239a”} 2024-11-18T19:11:35+00:00 Errore Failed request to URL PATCH https://merchant.revolut.com/api/1.0/orders/673B9124-3848-ACFB-9BAD-6676F7F919DC 2024-11-18T19:11:35+00:00 Errore {“timestamp”:1731957095344,”errorId”:”43214f2e-81f3-4ef1-bbc3-aa8e56e9e083″} 2024-11-18T19:11:35+00:00 Errore Something went wrong: PATCH https://merchant.revolut.com/api/1.0/orders/673B9124-3848-ACFB-9BAD-6676F7F919DC {“timestamp”:1731957095344,”errorId”:”43214f2e-81f3-4ef1-bbc3-aa8e56e9e083″} 2024-11-18T19:11:35+00:00 Errore Failed request to URL PATCH https://merchant.revolut.com/api/1.0/orders/673B9124-3848-ACFB-9BAD-6676F7F919DC 2024-11-18T19:11:35+00:00 Errore {“timestamp”:1731957095466,”errorId”:”127d9df2-7c58-4fdc-a9f8-eda83625df49″} 2024-11-18T19:11:35+00:00 Errore Something went wrong: PATCH https://merchant.revolut.com/api/1.0/orders/673B9124-3848-ACFB-9BAD-6676F7F919DC {“timestamp”:1731957095466,”errorId”:”127d9df2-7c58-4fdc-a9f8-eda83625df49″} 2024-11-18T19:42:59+00:00 Errore Can not update wc_order_id for Revolut order record on DB: Duplicate entry ‘g;\x98\xAC’9\xA0\xBD\x95iXc\xD8%OR’ for key ‘PRIMARY’ 2024-11-18T19:44:38+00:00 Errore Can not update wc_order_id for Revolut order record on DB: Duplicate entry ‘g;\x99\x0F\xA0l\xA2″\x95d\xD2\xAE0wc\xFD’ for key ‘PRIMARY’

2024-11-18T19:45:53+00:00 Errore Can not update wc_order_id for Revolut order record on DB: Duplicate entry ‘g;\x99\x0F\xA0l\xA2″\x95d\xD2\xAE0wc\xFD’ for key ‘PRIMARY’ 2024-11-18T19:59:26+00:00 Errore Exception: Missing revolut_public_id parameter in /notsharingmyfolder/wp-content/plugins/revolut-gateway-for-woocommerce/includes/abstract/class-wc-payment-gateway-revolut.php:677 Stack trace: #0 /notsharingmyfolder/wp-content/plugins/woocommerce/includes/class-wc-form-handler.php(545): WC_Payment_Gateway_Revolut->add_payment_method() #1 /notsharingmyfolder/wp-includes/class-wp-hook.php(324): WC_Form_Handler::add_payment_method_action() #2 /notsharingmyfolder/wp-includes/class-wp-hook.php(348): WP_Hook->apply_filters() #3 /notsharingmyfolder/wp-includes/plugin.php(565): WP_Hook->do_action() #4 /notsharingmyfolder/wp-includes/class-wp.php(830): do_action_ref_array() #5 /notsharingmyfolder/wp-includes/functions.php(1336): WP->main() #6 /notsharingmyfolder/wp-blog-header.php(16): wp() #7 /notsharingmyfolder/index.php(17): require(‘…’) #8 {main}

2024-11-18T20:36:58+00:00 Errore Failed request to URL POST https://merchant.revolut.com/api/1.0/customers 2024-11-18T20:36:58+00:00 Errore {“timestamp”:1731962218337,”code”:1018,”errorId”:”418da4bf-c019-4361-94f7-9fa940fef7c4″} 2024-11-18T20:36:58+00:00 Errore create_revolut_customer: Something went wrong: POST https://merchant.revolut.com/api/1.0/customers {“timestamp”:1731962218337,”code”:1018,”errorId”:”418da4bf-c019-4361-94f7-9fa940fef7c4″}

Hello @scrivio,

we’ve forwarded this issue to our developers and we’ll keep you updated on any news regarding this.

Kind regards,
Matas from Revolut Business

Hello @scrivio,

we’ve done an investigation and concluded that:

• The claim regarding Apple/Google Pay validation seems to be incorrect. For standard checkout, the validation happens immediately after the customer presses on the A/G Pay button, however, in the Blocks version of the checkout the validation only happens after the customer clicks on the Pay button inside the A/G Pay popup window

In regards to the errors from your logs:

• Errore Something went wrong: PATCH: This error has now been fixed
• Can not update wc_order_id for Revolut order record on DB: Duplicate entry ‘g;\x98\xAC’9\xA0\xBD\x95iXc\xD8%OR’: We’ve concluded that this error is harmless and can be safely ignored
• Errore Exception: Missing revolut_public_id parameter in: We’d like to investigate this further, but for that we’d need a staging environment. In case you are able to provide this:
  
  Please reach out to our in App Help section and ask for your case to be escalated, since we’re going to need information that should not be shared on a public forum.
  Follow these steps to reach out to our help section:
• – Open the Revolut Business App
• – Click on your account name on the top left of your screen.
• – Open “Help” section.
• – Scroll down until you see “Chat” option.
• – Click on “Start new chat” (chat bubble icon)

well, the validation happens, but the popup is not being closed and it still opens.
So the validation is useless, since the customer will see the popup loaded immediatly, and it covers the checkout page he’s on. That means the customer will not know of the errors (especially from mobile devices) and proceed with the payment, and than when the popup closes the order won’t be created since there are previous validation errors.

Doing the validation is not enough, you should prevent the popup from opening until the validation is complete or force it’s closing if the validation fails, otherwise it’s useless.

Hi @scrivio

I’m sorry to hear you’re experiencing issues with the plugin. We’ll continue investigating to find a solution. However, I want to clarify that the behaviour you just described should not happen and rather unexpected. On both mobile and desktop, validation occurs either immediately or when the pay button inside Google Pay/Apple Pay is clicked. If validation fails, the pop-up should close, and customers should be directed to the invalid fields, which does not happen in your case.

To help us look into this further, could you please share a screen recording of the issue? Additionally, it would be very helpful if you could provide access to a staging environment where we can test this behaviour.

Please email us at [email protected] if you want to share any sensitive information like store address, staging environment access, etc…

Kind regards

Hi?@scrivio

We have made some adjustments that should completely solve your issue, please update your plugin to the latest version.

Regards