Afterpay

Hi @bob33,

Again, thank you for the feedback.

To answer your question, yes the gateway has been tested in local environments by the engineering team. Given the nature of WordPress / WooCommerce and the many different combinations of configurations, themes and plugins, compatibility with every installation cannot be guaranteed.

On the point of being added to the list of block compatible gateways, the team are investigating this internally. Again, the feedback around that is appreciated and validates prioritising this.

Thank you.

Hi @sabinauni,

Thank you for your message.

The team would very much like to assist with resolving 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

Thank you.

Hi @parhamm,

Thanks for your message.

Based on the description provided above, this type of integration is not offered by the Afterpay Gateway for WooCommerce plugin. Afterpay stores consumers’ credit card information securely in their Afterpay accounts, and would not capture any payment until the payment schedule and amounts have been reviewed and confirmed on the checkout.

Thank you.

Hi @lulustone,

Thank you for your message and positive review.

Upon investigation this looks likely to be an accidental or temporary account issue. The team is looking into the root cause of the challenge and will communicate the resolution shortly.

Thank you.

Hi @bathroo,

Thank you for your message. It appears that the Afterpay client side script file has been concatenated with the other site scripts using the SiteGrounds Optimizer plugin. This is known to cause errors with the Afterpay plugin. Two options are outlined below for resolving this challenge.

1. Turn off javascript file concatenation.
To achieve this, go to the Frontend settings of the SiteGrounds Optimizer plugin. Click the Javascript tab and turn off Combine Javascript Files.

2. Use the SiteGrounds Optimizer hook to disable Afterpay Javascript concatenation.
This option allows for more control over the scripts as it only disables concatenation of the Afterpay files. The engineering team recommends engaging the websites development team as it requires editing files. Adding the following code will achieve this.

add_filter( 'sgo_javascript_combine_excluded_external_paths', 'js_combine_exclude_external_script' );
function js_combine_exclude_external_script( $exclude_list ) {
    $exclude_list[] = 'js.afterpay.com';

    return $exclude_list;
}

Thank you.

Hi @koromanoj,

Thanks for your message and for providing the logs. Based on these it appears that curl is not enabled on the website server. The engineering team have been able to replicate this error by turning off the curl php module locally. The team recommends reaching out to the server host for assistance in enabling the curl module.

Thank you.

Hi @btbau,

Thanks for your question.

The code snippet is usually pasted into the functions.php file of the active theme. Please be mindful that it may need to be pasted again if the theme gets updated.

This is something that is recommended for the site development partner to action. As always with these types of changes a full site backup (database and files) before commencing is strongly recommended.

Thank you.