Afterpay

Hi @chrissyb,

Thanks for your question.

The Afterpay plugin is configured to display the logo and payment limits in situations where the product or cart total is priced outside of these limits; either below the minimum or above the maximum. The purpose of this is to inform customers that Afterpay is available, but subject to conditions that are not presently being satisfied. Currently, this content is not easily customisable or configurable, but there are plans to improve this in a future release of the plugin.

However, any Afterpay content for the cart page, including the “outside limits” message, is passed through the afterpay_html_on_cart_page filter hook before rendering on the page. It would be possible to attach a method to this hook to perform advanced customisations based on the content.

Please note that any updates to the Afterpay Gateway for WooCommerce plugin will be distributed via the WordPress Plugin Directory; available through the standard update interface within the WordPress admin.

Thank you.

Hi @liam22,

Thanks for your question.

As soon as each payment event is completed, Afterpay calls the WooCommerce core WC_Order::payment_complete method, which sets the Order status to either “processing” or “completed”, depending on whether the Order requires shipping.

See the following code reference for more detail:

• https://docs.woocommerce.com/wc-apidocs/source-class-WC_Order.html#87-140

Since WooCommerce passes the status through the “woocommerce_payment_complete_order_status” filter, coupled with the Order ID, customising the value based on payment method should be possible. Please consult with your web development team for technical assistance exploring these advanced customisations.

Happy to answer any further questions as necessary.

Thank you.

Hi @embercide,

Thank you for your message, and for taking the time to share this suggestion with the team.

It isn’t currently possible to display Afterpay Merchant fees on a per-order basis, for two reasons:

1. Final settlement amount is calculated daily, rather than at the time of each individual order
2. Merchant fee values are not exposed via the current incarnation of the Online API

However, a good idea is always appreciated. A ticket has been created separately to raise this suggestion for inclusion in further internal roadmap discussions.

As always, any updates to the Afterpay plugin will be distributed via the official WordPress Plugin Directory.

Thank you.

Hi @rxsmartgearaus,

Thanks for your message. Please confirm the version of the “Afterpay Gateway for WooCommerce” plugin in use. The latest release (v2.0.5) included an improvement that addresses similar behaviour.

Thank you.

Hi @gutterboy333 and @embercide,

Thanks for following up.

Version 2.0.5 was tested in WordPress 5.2-RC1 and WooCommerce 3.6.2. No changes were needed to support these. Although the recommended headers were updated to inform WordPress and WooCommerce what the plugin was tested in, for future updates an additional note will also be considered for inclusion in the Changelog.

Thanks for highlighting this.

Hi Toni,

Thanks for following up. Using the access provided in the separate support thread it’s clear to see that the “WordPress Address” defined in “Settings > General” contains the “/wordpressBOO” path. This is the actual installation address for WordPress and probably cannot be changed without moving the entire site outside of the subdirectory.

Thanks for suggesting home_url. The team will attempt to modify your instance of the plugin to use get_home_url instead of get_site_url. This will be considered for inclusion in a subsequent official release.

Further support will be provided in the parallel thread.

Thank you.

• This reply was modified 7 years ago by Afterpay.

Hi Daniel,

Thank you for your question. Please find further information below.

The “[AMOUNT]” placeholder is not a shortcode. The Afterpay Gateway for WooCommerce plugin manually performs a case-sensitive search and replacement of this string during the execution of the methods attached to the various WooCommerce hooks.

Therefore, this placeholder can only be used as directed inside the plugin settings page. It’s also a requirement that only uppercase characters be used.

However, the “WC_Gateway_Afterpay::print_info_for_product_detail_page” method that the plugin automatically attaches to the “woocommerce_single_product_summary” hook can be attached to any arbitrary Action hook, provided an instance to the relevant WC_Product is passed to it. This method is responsible for rendering the Afterpay elements defined within the settings page on the individual product pages. The method can also be called directly once the class is instantiated.

Please consult with your web development team for advanced technical assistance with custom implementations.

Thank you.

Hi lalarnz,

Thank you for your message. This item is being handled as part of a separate support thread.

A preliminary investigation has highlighted several points of interest:

1. The outcome described appears to affect only orders where the customer checked out as a guest.
2. This behaviour is not limited to Afterpay; other payment gateways are also affected.
3. The instance of WooCommerce in question appears to be heavily customised, with a number of third-party plugins

There is an item currently open that produces a similar outcome, which may or may not be related. This is caused by the presence of unusual characters in the customer’s shipping or billing address information. A resolution for this challenge has been developed, but has not yet been approved for public distribution.

If you would like to request early access to a copy of this beta version (2.0.4.2) please submit a request to the team in response to the other support thread. The team can then contact you directly with further assistance if necessary.

Thank you.