Afterpay

Hi @johnback9,

Thank you for your message.

There is a general recommendation to keep the plugin updated in order to benefit from security patches and improvements as quickly as reasonably possible.

Regarding the “412” responses, API network logs indicate that these are occurring as a result of attempting to reprocess a checkout that has already been processed. Possibly, the end user has attempted to resubmit the order form after their payment has already been received. This could just be an unusual consumer behaviour, refreshing or navigating back and resubmitting, or having the checkout open in two tabs and attempting to place the order in both.

If the challenge seems to occur regularly or for a suspiciously high percentage of orders, the team would be happy to assist with an investigation. To facilitate this, please submit a support request including a link to this post using the following web form: https://afterpay.formstack.com/forms/global_merchant_technical_support

A member of the team will then reach out to you within 1 business day.

Thank you.

Hi @websmall,

Thank you for your message.

The team would like to assist with this challenge. To facilitate this, please submit a support request including a link to this post using the following web form: https://afterpay.formstack.com/forms/global_merchant_technical_support

A member of the team will then reach out to you within 1 business day.

Thank you.

Hi @fawadinho,

Thank you for you message and following up on this one.

The Afterpay team is planning to release an update to the Afterpay Gateway for WooCommerce plugin within the next 30 days dependent on tests passing. As always the recommendation is to follow the WordPress guidelines in regard to making backups of the site before applying these updates.

Thank you.

Hi @zenwebcreative,

Thank you for confirming that the challenge is resolved. Glad to hear it’s working as expected now.

All the best.

Hi @zenwebcreative,

Thank you for your message and for sharing the detailed log.

One requirement for the Afterpay plugin is the cURL library for PHP. The provided log does not contain a cURL version, which usually implies that the PHP cURL library is not installed. The recommendation is therefore to review the official PHP reference below for installation instructions.
https://www.php.net/manual/en/book.curl.php

Thank you.

Hi @zenwebcreative,

Thank you for your message.

This challenge usually occurs when the curl module is not installed on the server. Please raise a request with the website administrator or hosting provider to install and enable this library.

Thank you.

Hi diepbui4157,

Thank you for your message.

The team would like to assist with this challenge. To facilitate this, please submit a support request including a link to this post using the following web form: https://afterpay.formstack.com/forms/global_merchant_technical_support

A member of the team will then reach out to you within 1 business day.

Thank you.

Hi @thrivewebdesign,

Thank you for bringing this to our attention.

The correct form can be found here: https://afterpay.formstack.com/forms/global_merchant_technical_support

Thank you.

Hi @evolved,
Thank you for your message.

We consider your fix valid and will be included on our next release and prevent you to lose it again.

Best regards

Hi @thrivewebdesign

Thank you for your message.

The team would like to assist with this challenge. To facilitate this, please submit a support request including a link to this post using the following web form: https://help.afterpay.com/hc/requests/new?ticket_form_id=193406

A member of the team will then reach out to you within 1 business day.

Thank you.

• This reply was modified 1 year, 8 months ago by Afterpay.

Hi @leofx4,

Thanks for the message.

The method for doing so would depend on the consumer journey, but there are two points that matter.

1. The consumer would need to close the Afterpay checkout window / tab, because it was initiated with the original order amount and cannot be changed once initiated.
2. If the consumer changed the cart themselves, then a new Afterpay checkout should be initiated by starting over (i.e. going to the WooCommerce checkout and placing a new order). If it was a store admin that updated an order for a consumer, then the admin should send the ‘pay for order’ link back to the consumer. Once the consumer attempts to pay again, a new checkout will be initiated with the correct order amount.

Thank you.

Hi @leofx4

Thank you for your message.

In case a consumer wants to cancel some of the items after paying for an order, merchants can process a partial refund through the order details page before dispatching the order. Please follow the instructions here:
https://woocommerce.com/document/woocommerce-refunds/

Thank you.

Hi @codenaut,

Thank you for your message.

The team has now added High-Performance Order Storage (HPOS) to the roadmap, and will make the Afterpay plugin compatible with this new feature of WooCommerce as soon as possible. Any updates will be distributed via the WordPress Plugin Directory.

Thank you.

Hi @stylevids,

Thank you for your message.

A new version of the Afterpay plugin is planned to be released by the end of January to ensure its compatibilities with the latest WordPress and WooCommerce. Any updates will be distributed via the WordPress Plugin Directory.

Thank you.

Hi @theozsnowman,

Thank you for your message.

It looks like there is currently unchecked access of that array key in the plugin. A check will be added in a future version to ensure that the code is only reached if it exists. In the meantime, going to the plugin settings (Dashboard > WooCommerce > Settings > Payments > Afterpay) and clicking Save Changes should generate the array key and therefore remove the warning.

If the above does not resolve the challenge, the team would be more than willing to assist with an investigation. To facilitate this, please submit a support request including a link to this post using the following web form: https://help.afterpay.com/hc/requests/new?ticket_form_id=193406

A member of the team will then reach out to you within 1 business day.

Thank you.