Douglas I. a11n

Hi @chilliwax and @subscriptiongroup,

We have been able to reproduce the error using the steps in your open GitHub issue. A bug label has been added to it and our developers will look into it.

Thank you for bringing this to our notice and for opening the issue. ??

Hi @subscriptiongroup thank you for spending a lot of time debugging this issue. I have raised this up with the development team as well and will update this thread with feedback.

Hi @rusty1964,

One of my customers won’t do business with me unless they can look at those 4 digits! Darn customers!

I know right?

I have gotten confirmation from our developers that they are adding this feature back and should be available in the next version of Square. I hope this helps.

Also, did you try the rollback option and did it help?

Hi @rusty1964, thank you for confirming.

I checked on our end and I noticed that this feature was removed from in version 3.9.0. I am not sure why but a comment has been dropped for the developers so we get more information on while this was changed.

In the meantime, can you try rolling back to your previous version of Square to see if this starts working again?

Hi @rusty1964,

I am sorry to hear that you the meta tag _wc_square_credit_card_account_four recently stopped working for you.

Can you tell me if this happened after making updates to your plugins (Square especially) or theme?

We look forward to assisting you further with this issue.

Hi @robadeedoo123,

I am sorry to hear that the Eway plugin was putting payments through as recurring subscription payments.

This is quite a strange scenario and I will like to look into this issue further for you. Can you share the ticket number from your last interaction with us? If not you can share open a new ticket and let me know here and I take it from there.

Best,
Douglas.

Hi @cccamuseme, I am sorry to hear that the Square plugin is slow and the digital wallet s freeze on checkout on your site.

Since we cannot replicate this on our end, can you please open a ticket for this issue and we will be happy to look into this for you.

Hi @catalinbaciu,

It is understandable, I noticed the reply did not go through so there is no way you could have seen it. ??

I am happy to hear that we were able to answer your question but I am sorry to hear that our recommendations do not fit your CRM system.

In this regard, I believe the internal communication is necessary. Maybe creating a new order and canceling the previous one may be the best next step.

Please do not hesitate to let us know if you further assistance or clarification with this issue.

Best regards.

Hi @catalinbaciu, thank you for checking in again. My colleague sent a reply to your previous questions but it looks like it never got you. In this regard, I will share the reply here again.

In response to your question about clearing the Square transaction ID from the Transaction ID field in the WooCommerce order edit screen and updating the order, it could be a possible workaround, but there might be unforeseen consequences. Before proceeding, you should consider that it might interfere with the synchronization between Square and WooCommerce, possibly leading to issues with tracking and reconciling transactions.

As an alternative, you may want to look into using the WooCommerce Deposits extension, which allows customers to make partial payments or pay in installments on an order. Moreover, it handles multiple payments for the same order very smoothly.?

There is also the WooCommerce Order Status & Actions Manager extension that may be useful in this case. This extension gives you more flexibility in managing your orders and their statuses.?

Another plugin that might be helpful is the WooCommerce Name Your Price plugin, which allows the customers to pay what they want for products. They could pay their outstanding amount using this feature.?

Please ensure that you thoroughly test any changes to your payment process on a staging or development site before implementing them on your live store.?

As a reminder, we have a 30-day refund policy during which I encourage you to evaluate the plugins to see if they will fit your needs.

You can read more about our refund policy on our website here: https://woocommerce.com/refund-policy/

Please note that it is highly recommended to perform tests on a staging environment before implementing it on your live site. Many hosts provide staging facilities, so it’s worth checking in with them. It’s also possible to do it using the free WP Staging plugin.

Please let us know if this answers your questions or if you need further assistance.

• This reply was modified 1 year, 4 months ago by Douglas I. a11n.

Hi @chandrasekhar2chandu, while Stripe allows you to add Afterpay as a payment method on your dashboard, the WooCommerce Stripe Payment Gateway currently does not accept Afterpay as a payment method.

There is an open feature request for this in the WooCommerce.com marketplace here: https://woocommerce.com/feature-request/add-afterpay-and-klarna-to-the-list-of-payment-methods/. An alternative will be to use the free Afterpay extension to add Afterpay as a payment gateway on your site.

I hope this helps.

Hi @fotinos

Is there a way to know a little more about this? For example, what information about recent transactions and how do I know whether my store got affected?

No credit card information can be accessed with this vulnerability, but email addresses, names, and other customer details.

About knowing whether your store got affected, it will be good to know that at this time, we have no evidence that the vulnerability was exploited beyond identifying it in our own security testing program.

Please note that WooCommerce can’t check on your behalf to see if your site has been compromised. If your shop is hosted on WordPress.com, Pressable, or another Automattic hosting service, then we’ve automatically deployed the patch to your shop.?

For instructions to help check if your site has been compromised, please review this documentation.

Hi @fotinos, thank you for reaching out and for updating the latest version.

I have updated to version 7.4.1 since but could you share more information about the vulnerability?

We recently discovered a potential vulnerability in several WooCommerce extensions focused on payments and payment processing. We immediately started working on a patch for the impacted WooCommerce extensions and began efforts to contact merchants using the extensions that would benefit from such patches.?

This vulnerability can permit unauthorized users to access some information about recent transactions (not credit card details), or possibly allowed for the creation of falsified shop transactions.

Is a site that only allows for guest purchases vulnerable to this?

Yes, even websites that allow only guest purchases are vulnerable.

However, since you have updated to the latest version you do not have anything to worry about.

Hi @peterwithap, I am sorry to hear that you were having issues with the Stripe Payment Gateway extension. Can you open a ticket regarding the issues you are having? We will be happy to assist you with them.

Hi @tomitatsuyoshi, thank you for the kind review. I am happy to hear that you found our advice useful.

If you need help with anything else, feel free to reach out to us again. We will be happy to assist you with it ??

Hi @jaskaranpreetsingh, thank you for the review. I am happy to hear that Stripe Payment Gateway works great for you, and that you find our support replies very responsive.

If you ever need support for this extension, please know that we are always here to assist you with it.