Zach

Hi there @wpsupacc ,

I can appreciate the concern and understand where you are coming from as far as a resolution. There is a report out to our development team at this time.

Per your request, I will leave this thread open until a new update has been released.

Best wishes,

Hey @wpsupacc,

It has been a long time since we heard back from you, so I’m going to mark this topic as resolved.

Please know that I have gotten this up to our plugin to team to look into updating the plugin.

If anything else comes up with the plugin, please feel free to reach out on our forum again!

Thanks,

Zach at SkyVerge ??

Hey there @wpsupacc ,

Thank you for getting back to us on this! We definitely do not want deprecation notices that would turn into errors for our plugins. Nor do we want any sort of compatibility or testing issues in regards to the WordPress version. I spoke with our support engineering team and I am going to create a bug report regarding the status of our Sequential Order Numbers plugin so that we can make sure that everything is up to date on it. While I do not have a timeframe currently, please know that our team is going to review the plugin and apply changes where needed to keep it up to date. I appreciate you bringing the age of the last up date to our attention. Keep an eye out for an update on the plugin. ??

Again, thank you for the report! Is there any other questions or concerns you have at this time?

Best wishes,

Hey there,

It has been a long time since we heard from you, so I’m going to mark this topic as resolved.

If you’re still experiencing issues please take a look at our FAQs for more information and create a new thread if you have further questions.

Thanks,
Zach @ SkyVerge ??

Hey there,

It has been a long time since we heard from you, so I’m going to mark this topic as resolved.

If you’re still experiencing issues please take a look at our FAQs for more information and create a new thread if you have further questions.

Thanks,
Zach B ??

Hey there @jlev00 ,

It has been a long time since we heard from you, so I’m going to mark this topic as resolved.

If you’re still experiencing issues please take a look at our FAQs for more information and create a new thread if you have further questions.

Thanks,
Zach @ SkyVerge ??

Hey there @forusak ,

Thank you for the additional details! I would definitely recommend reaching out to plugin creator of the exporter plugin to see if they support a formatted order number. We have some notes for developers to achieve this noted on our plugin page as well.

Please let me know if you have any other questions or concerns at this time!

Best wishes,

Zach @ SkyVerge

Hello there @forusak ,

Thank you for reaching out about our plugin, Sequential Order Numbers for WooCommerce! I’m happy to assist you with this. ??

I understand that you wanted to know the status of the plugin and that you are having issues with exports on your site. I can confirm that we are still supporting and maintaining the plugin. ??

Our plugin does not have a built-in export option. Could you tell me more about the issue you are experiencing with the export so I can direct you to the best assistance or resolution there?

Best wishes,
Zach @ SkyVerge

Hello there,

Thank you for reaching out about our plugin, GoDaddy Payments for WooCommerce! I’m happy to assist you with this. ??

Thank you for providing screenshots of the issues you are seeing! I understand that on the form you are getting an “OpenSSL” error, but you are also getting a fatal error when attempting to save changes to the plugin’s setting. While CloudFlare’s CDN and caching can cause issues for gateways at times, I would like to tackle some initial testing. Since you are getting a critical error, that is usually at the code level rather than the API level of the plugin so debug mode for the plugin may not help us just yet.

I would like to enable WP Debug mode to get some more information from your site to help determine the cause of this issue.

You would need to edit the wp-config.php file. Near the bottom of this file you’ll find a line that looks like the following:
define( ‘WP_DEBUG’, true );

What we’d need to see here is the following three lines:
define(‘WP_DEBUG’, true);
define(‘WP_DEBUG_LOG’, true);
define(‘WP_DEBUG_DISPLAY’, false);

If you already have those three lines in your wp-config.php file, would you please ensure that WP_DEBUG and WP_DEBUG_LOG are set to true and WP_DEBUG_DISPLAY is set to false?

Alternatively, you can try installing a plugin such as the free Debug plugin. I’d like to note that plugins aren’t able to enable debug mode in all server environments so editing the wp-config.php file is the preferred method.
1) Once debug mode is turned on WordPress will start logging all PHP errors to a file called wp-content/debug.log.
2) Run through duplicating the error by attempting to place an order.
3) Then check the debug.log, and if anything recorded in it, send it on over to us for review.

Could you give the WordPress Debug Mode a try and let me know if it logs anything for us to review?

Best wishes,

Zach B

Hello there @jlev00 ,

Thank you for reaching out about our plugin, Extra Product Sorting Options for WooCommerce! I’m happy to assist you with this. ??

I understand that you are wanting to know when Extra Product Sorting Options for WooCommerce will have HPOS support. As of the latest version of the plugin, 2.10.0, HPOS support has been implemented.

So with that said, if you are on the newest release you should be able to use HPOS on your site. If you are finding that not to be the case, we would definitely want to review the issue further.

Best Wishes,

Zach @ SkyVerge

Hey @antoniorios88,

It has been a long time since we heard from you, so I’m going to mark this topic as resolved.

If you’re still experiencing issues please take a look at our FAQs for more information and create a new thread if you have further questions.

Thanks,
Zach ??
_____________________________

Hola @antoniorios88,

Ha pasado mucho tiempo desde que supimos de usted, así que marcaré este tema como resuelto.

Si aún tiene problemas, consulte nuestras preguntas frecuentes para obtener más información y cree un nuevo hilo si tiene más preguntas.

Gracias,
Zach ??

Hey there @marekop,

I am glad I could help! I’m going to mark this topic as resolved now, but if you end up experiencing another issue please take a look at our FAQs for more information and create a new thread if you have further questions on the issue. We are always here to help! ??

Best wishes,

Zach | SkyVerge Support

Hey there @marekop,

I am glad I could help shed some light on the situation for you! An address verification plugin, could work as it is going to typically give the most recognized form, but ultimately the address needs to match what is on file with the issuing bank in order to proceed successfully. So it could help, but it could also correct addresses that are already correct if there not what the address verification would deem correct. Because of that I do not know that I could safely recommend that route unfortunately.

Do you have any other questions or concerns on this?

Best wishes,
Zach |SkyVerge Support

Hello @marekop,

I understand you have customers letting you know they are getting an error at checkout that their billing address is incorrect. I’d like to share a bit more information on why that might be happening for them.

In September, GoDaddy Payments added an additional address verification check (known as AVS check) for exact billing address matching. Originally they were only using the billing postal code, and found that merchants were getting a large amount of fraudulent orders placed and then chargebacks made to collect the funds from those transactions. Once they added the billing address matching, those charges have been almost eliminated for most of our merchants. It is much more difficult to find an address that exactly matches what a bank has on file for a credit card than it is for a matching postal code.

That said, it has created more instances of what your customers are seeing, due to formatting, casing of words, and abbreviations. We do find that one of the most common reasons for Canadian and European mismatches are the postal codes (maybe the bank doesn’t include the space or replaces it with a dash), and for US addresses that customers are not using an Upper Case Letter at the beginning of their street names. In addition, “Ave.” is considered different than “Avenue” or “Ave” for some of these banks, which then leads to many more declines if those kinds of road type abbreviations do not match.

The issue seems to be more prominent with those outside the USA because a bank can have a postal code stored in the customer’s account in a different format than what the customer may expect, such as removing/adding the space, lowercase letters instead of capital, or even putting in a hyphen. All of those could potentially cause the mismatch alert if the bank holds strict rules on what percent of the AVS check needs to match. From what I have heard from our GoDaddy Payments support engineers, most banks require an 85% match, but some can be up to 98-100% match to be accepted.

To be sure this is what is happening, you can enable the debug log for your gateway, which can be found at WooCommerce > Settings > Payments > GoDaddy Payments > Debug Mode. This will keep a record of your orders and will also let us know if the mismatch is with the postal code, the address, or both. You can view these logs at WooCommerce > Status > Logs, then search for logs starting with “godaddy”. Within that log, you can search (Ctrl+F or Cmd+F) for NO_MATCH and see if those come up in the log, which confirms that this is the issue happening to your customers. It seems that you already have done this and confirmed this is what is occurring.

If you are finding this is happening more than it is not, I would encourage you to do two things. First, you can create a note on your checkout page to remind customers that all of their billing information must match what their bank has on file for their credit card. If you use a page builder like Elementor or Beaver Builder, you can edit the Checkout page to add a text box at the top with this notice.

Second, you can set up and enable the GoDaddy In Person gateway under WooCommerce > Settings > Payments. This will create an additional payment button in the Order Details for an order where you can “Charge with Virtual Terminal.” This way you can reach out to the customer if their order remains in Pending Payment, and take their payment information over the phone, submitting it via that button. Charge with Virtual Terminal button We find that the same address information can be accepted most of the time with the Terminal where the gateway may not succeed. To allow you to catch these orders, you may want to extend the “Hold Stock” value you have for your Inventory to at least 180 minutes or remove it altogether if you find you don’t need it. Once that Hold Stock time is reached, any Pending Payment orders will move to Cancelled and then you will no longer be allowed to take payment via the Charge with Virtual Terminal button.

Would you please let me know if that is helpful information, and what further questions you have?

Best wishes,
Zach | SkyVerge Support

Hello there @riseofweb ,

Thank you for reaching out about our plugin, Godaddy Payments! I’m happy to assist you with this. ??

I am sorry to hear about the issues you are seeing with the plugin. Given that the fatal error involves the WooCommerce Fedex Shipping plugin. Could you try disabling the plugin and check if there is still multiple configure buttons for the gateway? Also would it be possible to send a screenshot of the current settings for the payment method. Please be sure to blur or block any account details.

Best,