Why is the Confirm button needed after payment?
-
Many customers think that their order is completed once they have received confirmation of their payment because this is what they are used to on most merchant sites.
It looks like PayPal Checkout requires an additional action on the “Confirm order” button. This is not intuitive and leads to orders being dropped and increased customer support with “They said I have paid but I don’t see the charge” / “I never received my order” type complaints.
Obviously they don’t receive the order because we are simply not notified that an order has been placed, even though the payment looks like having been processed.
Is there a way to use the standard behavior i.e. order -> payment -> “payment confirmed, thank you for your order”?
Thanks in advance.
-
Hi there,
Thanks for reaching out!
It sounds like after an order is placed with PayPal Checkout on your site, the order status isn’t changed to “processing” or “completed” until a Confirm order button is clicked, does that sound right?
Can you please specify where exactly that Confirm order button is located? I wasn’t able to replicate this behaviour on my test site – after placing an order on the checkout page via PayPal Checkout, I’m redirected to the order confirmation page:
The site is notified about a successful payment and the order status is set to “processing”:
https://docs.woocommerce.com/document/managing-orders/#order-statuses
The order status will only be changed to “completed” automatically if all purchased products are virtual and downloadable.
There is more than one payment option in PayPal Checkout, so please take screenshots, upload those to a service like https://snag.gy and paste links here.
You may also want to make sure that the “Payment action” is set to “sale”, not “authorize”:
https://docs.woocommerce.com/document/paypal-express-checkout/#section-7
I hope this helps!
Hi there,
We haven’t heard from you in a while so I’ll be marking this thread as resolved.
Feel free to open a new thread and link to this one if you have further questions though.
Have a wonderful day ahead!
Hi Grigorij,
Thank you for your reply and sorry for my late answer. I needed to experiment a little before I could follow up.
We are using WooCommerce PayPal Checkout Gateway version 2.1.1.
Here are my settings:
https://snipboard.io/0evDk7.jpg
https://snipboard.io/kGXdOI.jpgHere’s what the customer gets on a single product page:
https://snipboard.io/HfvLpn.jpg“Debit or Credit Card” opens this form below the button:
https://snipboard.io/Q1Zgn2.jpg
https://snipboard.io/CNrDwn.jpgOnce details are entered and payment is validated, the following page opens:
https://snipboard.io/IV69o5.jpgNow here is the issue: usually returning from a successful payment means that the order is over.
Here they still must click on “Place order” (after payment was processed!), otherwise nothing happens. No actual payment, no notification of the order, no pending order on the order page:
https://snipboard.io/7X5CSL.jpgA wonderful day to you too!
Thanks for the details @enode.
Could you please share a copy of your site’s System Status? You can find it via WooCommerce > Status. Select “Get system report” and then “Copy for support”.? Once you’ve done that, paste it here in your response.
If you’d prefer to send this directly, please contact us at WooCommerce.com > My Account > Support. You may need to create an account before you can access that page.
Please include a link to this forum thread, so that we can keep track of what’s already been done.
We will be able to help you further there.
Thank you for your reply.
Please find below the requested information.
Best regards,
Phil### WordPress Environment ### WordPress address (URL): https://www.dareios.fr Site address (URL): https://www.dareios.fr WC Version: 5.4.1 REST API Version: ? 5.4.1 WC Blocks Version: ? 5.1.0 Action Scheduler Version: ? 3.1.6 WC Admin Version: ? 2.3.1 Log Directory Writable: ? WP Version: 5.7.2 WP Multisite: – WP Memory Limit: ? 40 MB - We recommend setting memory to at least 64MB. See: Increasing memory allocated to PHP WP Debug Mode: – WP Cron: ? Language: en_US External object cache: – ### Server Environment ### Server Info: Apache PHP Version: 7.4.20 PHP Post Max Size: 6 MB PHP Time Limit: 30 PHP Max Input Vars: 1000 cURL Version: 7.64.0 OpenSSL/1.1.1d SUHOSIN Installed: – MySQL Version: 5.7.33-log Max Upload Size: 64 MB Default Timezone is UTC: ? fsockopen/cURL: ? SoapClient: ? DOMDocument: ? GZip: ? Multibyte String: ? Remote Post: ? Remote Get: ? ### Database ### WC Database Version: 5.4.1 WC Database Prefix: FFdbPIuS Total Database Size: 9.38MB Database Data Size: 7.19MB Database Index Size: 2.19MB FFdbPIuSwoocommerce_sessions: Data: 2.02MB + Index: 0.06MB + Engine InnoDB FFdbPIuSwoocommerce_api_keys: Data: 0.02MB + Index: 0.03MB + Engine InnoDB FFdbPIuSwoocommerce_attribute_taxonomies: Data: 0.02MB + Index: 0.02MB + Engine InnoDB FFdbPIuSwoocommerce_downloadable_product_permissions: Data: 0.02MB + Index: 0.06MB + Engine InnoDB FFdbPIuSwoocommerce_order_items: Data: 0.02MB + Index: 0.02MB + Engine InnoDB FFdbPIuSwoocommerce_order_itemmeta: Data: 0.05MB + Index: 0.03MB + Engine InnoDB FFdbPIuSwoocommerce_tax_rates: Data: 0.02MB + Index: 0.06MB + Engine InnoDB FFdbPIuSwoocommerce_tax_rate_locations: Data: 0.02MB + Index: 0.03MB + Engine InnoDB FFdbPIuSwoocommerce_shipping_zones: Data: 0.02MB + Index: 0.00MB + Engine InnoDB FFdbPIuSwoocommerce_shipping_zone_locations: Data: 0.02MB + Index: 0.03MB + Engine InnoDB FFdbPIuSwoocommerce_shipping_zone_methods: Data: 0.02MB + Index: 0.00MB + Engine InnoDB FFdbPIuSwoocommerce_payment_tokens: Data: 0.02MB + Index: 0.02MB + Engine InnoDB FFdbPIuSwoocommerce_payment_tokenmeta: Data: 0.02MB + Index: 0.03MB + Engine InnoDB FFdbPIuSwoocommerce_log: Data: 0.02MB + Index: 0.02MB + Engine InnoDB FFdbPIuSactionscheduler_actions: Data: 0.05MB + Index: 0.11MB + Engine InnoDB FFdbPIuSactionscheduler_claims: Data: 0.02MB + Index: 0.02MB + Engine InnoDB FFdbPIuSactionscheduler_groups: Data: 0.02MB + Index: 0.02MB + Engine InnoDB FFdbPIuSactionscheduler_logs: Data: 0.02MB + Index: 0.03MB + Engine InnoDB FFdbPIuSblc_filters: Data: 0.02MB + Index: 0.00MB + Engine InnoDB FFdbPIuSblc_instances: Data: 0.02MB + Index: 0.05MB + Engine InnoDB FFdbPIuSblc_links: Data: 0.02MB + Index: 0.06MB + Engine InnoDB FFdbPIuSblc_synch: Data: 0.02MB + Index: 0.02MB + Engine InnoDB FFdbPIuScommentmeta: Data: 0.02MB + Index: 0.03MB + Engine InnoDB FFdbPIuScomments: Data: 0.09MB + Index: 0.09MB + Engine InnoDB FFdbPIuSlinks: Data: 0.02MB + Index: 0.02MB + Engine InnoDB FFdbPIuSoptions: Data: 3.08MB + Index: 0.08MB + Engine InnoDB FFdbPIuSpostmeta: Data: 0.33MB + Index: 0.22MB + Engine InnoDB FFdbPIuSposts: Data: 0.33MB + Index: 0.06MB + Engine InnoDB FFdbPIuSstatify: Data: 0.09MB + Index: 0.16MB + Engine InnoDB FFdbPIuStermmeta: Data: 0.02MB + Index: 0.03MB + Engine InnoDB FFdbPIuSterms: Data: 0.02MB + Index: 0.03MB + Engine InnoDB FFdbPIuSterm_relationships: Data: 0.05MB + Index: 0.02MB + Engine InnoDB FFdbPIuSterm_taxonomy: Data: 0.02MB + Index: 0.03MB + Engine InnoDB FFdbPIuSusermeta: Data: 0.08MB + Index: 0.03MB + Engine InnoDB FFdbPIuSusers: Data: 0.02MB + Index: 0.05MB + Engine InnoDB FFdbPIuSwc_admin_notes: Data: 0.02MB + Index: 0.00MB + Engine InnoDB FFdbPIuSwc_admin_note_actions: Data: 0.02MB + Index: 0.02MB + Engine InnoDB FFdbPIuSwc_category_lookup: Data: 0.02MB + Index: 0.00MB + Engine InnoDB FFdbPIuSwc_customer_lookup: Data: 0.02MB + Index: 0.03MB + Engine InnoDB FFdbPIuSwc_download_log: Data: 0.02MB + Index: 0.03MB + Engine InnoDB FFdbPIuSwc_order_coupon_lookup: Data: 0.02MB + Index: 0.03MB + Engine InnoDB FFdbPIuSwc_order_product_lookup: Data: 0.02MB + Index: 0.06MB + Engine InnoDB FFdbPIuSwc_order_stats: Data: 0.02MB + Index: 0.05MB + Engine InnoDB FFdbPIuSwc_order_tax_lookup: Data: 0.02MB + Index: 0.03MB + Engine InnoDB FFdbPIuSwc_product_meta_lookup: Data: 0.02MB + Index: 0.09MB + Engine InnoDB FFdbPIuSwc_reserved_stock: Data: 0.02MB + Index: 0.00MB + Engine InnoDB FFdbPIuSwc_tax_rate_classes: Data: 0.02MB + Index: 0.02MB + Engine InnoDB FFdbPIuSwc_webhooks: Data: 0.02MB + Index: 0.02MB + Engine InnoDB FFdbPIuSwpforms_tasks_meta: Data: 0.02MB + Index: 0.00MB + Engine InnoDB FFdbPIuSwpmm_subscribers: Data: 0.02MB + Index: 0.00MB + Engine InnoDB FFdbPIuSyoast_indexable: Data: 0.14MB + Index: 0.11MB + Engine InnoDB FFdbPIuSyoast_indexable_hierarchy: Data: 0.02MB + Index: 0.05MB + Engine InnoDB FFdbPIuSyoast_migrations: Data: 0.02MB + Index: 0.02MB + Engine InnoDB FFdbPIuSyoast_primary_term: Data: 0.02MB + Index: 0.03MB + Engine InnoDB FFdbPIuSyoast_seo_links: Data: 0.02MB + Index: 0.03MB + Engine InnoDB ### Post Type Counts ### attachment: 139 custom_css: 1 nav_menu_item: 6 oembed_cache: 2 page: 7 post: 1 product: 28 revision: 29 shop_order: 57 wpforms: 1 ### Security ### Secure connection (HTTPS): ? Hide errors from visitors: ? ### Active Plugins (15) ### Alfred, the Assistant: by 1&1 IONOS – 5.5.1 Antispam Bee: by pluginkollektiv – 2.9.4 Broken Link Checker: by WPMU DEV – 1.11.15 GDPR Cookie Consent: by WebToffee – 2.0.3 Google Ads & Marketing by Kliken: by Kliken – 1.0.7 Limit Login Attempts Reloaded: by Limit Login Attempts Reloaded – 2.22.1 Statify: by pluginkollektiv – 1.8.2 Advanced Editor Tools (previously TinyMCE Advanced): by Automattic – 5.6.0 Where Did You Hear About Us Checkout Field for WooCommerce: by Wooassist – 1.1.2 Premmerce Permalink Manager for WooCommerce: by premmerce – 2.3.1 WooCommerce PayPal Checkout Gateway: by WooCommerce – 2.1.1 WooCommerce: by Automattic – 5.4.1 Yoast SEO: by Team Yoast – 16.5 WP Maintenance Mode: by Designmodo – 2.4.0 WPForms Lite: by WPForms – 1.6.7.1 ### Inactive Plugins (3) ### Akismet Anti-Spam: by Automattic – 4.1.9 Facebook for WooCommerce: by Facebook – 2.6.0 PayPal Express Checkout Payment Gateway for WooCommerce ( Basic ): by WebToffee – 1.5.8 ### Must Use Plugins (1) ### 1&1 Product Subdomain: by 1&1 – 1.1.0 ### Settings ### API Enabled: – Force SSL: – Currency: EUR (€) Currency Position: left Thousand Separator: . Decimal Separator: , Number of Decimals: 2 Taxonomies: Product Types: external (external) grouped (grouped) simple (simple) variable (variable) Taxonomies: Product Visibility: exclude-from-catalog (exclude-from-catalog) exclude-from-search (exclude-from-search) featured (featured) outofstock (outofstock) rated-1 (rated-1) rated-2 (rated-2) rated-3 (rated-3) rated-4 (rated-4) rated-5 (rated-5) Connected to WooCommerce.com: – ### WC Pages ### Shop base: #6 - / Cart: #7 - /panier Checkout: #8 - /commande My account: #9 - /mon-compte Terms and conditions: ? Page not set ### Theme ### Name: Storefront Version: 3.7.0 Author URL: https://woocommerce.com/ Child Theme: ? – If you are modifying WooCommerce on a parent theme that you did not build personally we recommend using a child theme. See: How to create a child theme WooCommerce Support: ? ### Templates ### Overrides: – ### Action Scheduler ### Complete: 61 Oldest: 2021-06-16 15:06:03 +0200 Newest: 2021-06-24 09:34:07 +0200 Pending: 3 Oldest: 2021-06-24 17:34:22 +0200 Newest: 2021-06-25 10:56:35 +0200 ### Status report information ### Generated at: 2021-06-24 09:35:14 +02:00
Hi Phil,
Thanks for your reply.
From what I’m gathering, when a customer clicks on the “Debit or Credit Card” option from the single product page, a form loads where they can enter in their credit card information. Once they enter this information and click “Continue”, they are then directed to the order page to “Place Order”.
You mentioned that “usually returning from a successful payment means that the order is over.”
I’ve been able to confirm that this is the default behavior of the plugin, and the process you and customers are navigating through is expected. When customers enter in their information on the credit card form, payment is not actually being taken at that point, so they wouldn’t be returning from a successful payment at that point. They would still need to go to the order/checkout screen to officially place the order.
I have tested this on a default installation, and what you are describing is the expected behavior. Here’s a screenshot of the same page I landed on after entering in credit card details on the product page and selecting “Continue”:
I do understand that this is confusing customers, but it would require further customizations to alter this behavior.
I hope this helps clarify, and please do let us know if you have any further questions.
- The topic ‘Why is the Confirm button needed after payment?’ is closed to new replies.