Ben from Afterpay
Forum Replies Created
-
Forum: Plugins
In reply to: [Afterpay Gateway for WooCommerce] square-marketplace.jsHi @briannanda007,
Thank you for reaching out on this topic. Currently no updates are available from the Afterpay team.
Please note that there is no action for merchants using the Square Marketplace JS library in WooCommerce, as updates and improvements are handled via the Square CDN and do not require a plugin update.
For best practice and conversion rates, the Afterpay team highly recommend merchants implement both PDP and cart page messaging, which has a proven track record of success with merchant partners using the Afterpay service.
The Afterpay team will frequently and consistently update both branding and language used and as a result it is vital that merchants continue to implement and use dynamic messaging solutions for when these updates are made to remain consistent, relevant and up-to-date.
Please note that should merchant partners choose to implement static assets they will be responsible for any misrepresentation of the Afterpay service and the Afterpay team will not be able to provide support or troubleshooting should challenges arise.
Thank you.
Hi @kds26,
It has now been confirmed that this is caused by Firefox’s tracking protection. The team are still exploring solutions. This may take some time to completely resolve, as it may require several domain migrations. However, the JS Library itself is hosted on squarecdn.com rather than afterpay.com, so the solution is unlikely to require an update to the Afterpay Gateway for WooCommerce plugin.
Thank you.
Hi @kds26,
Thanks for following up. Yes, the team were able to replicate the reported behaviour and are currently investigating potential solutions. They suspect that it has something to do with top-level cookies on the afterpay.com domain causing Mozilla to deem the messaging’s Placement API as a potential cross-site tracker (which it is not).
Has this been reported by any customers, or internal testing only?
Thank you.
Hi @kds26,
Thanks for raising this concern. The team would be happy to help troubleshoot this with you. Please provide a link to the website where the reported behaviour can be replicated.
Thank you.
Hi @kristinubute,
Thanks for following up. Really appreciate your patience here. You’ll receive a response via email as soon as someone is available to take a look.
There’s not much more detail I can share on a public forum due to the this being credential related. But I’ll talk to the team about any open cases relating to this thread. Is there a business name or something else non-sensitive that could help us to identify the tickets you’ve raised?
Please don’t share an email address or any other personal information, but a business name or website URL is generally considered safe to publish on this forum.
Thank you.
Hi @smgdarien,
Thanks for reporting these errors.
Since source maps are intended to load only when the browser’s developer tools are open, and do not impact the functionality of the scripts they correspond to, these are not likely to have any impact on customers. Nonetheless, an internal ticket has been lodged with the engineering team for further investigation. Potential solutions will be discussed and considered for inclusion in subsequent updates.
Thank you.
Hi @kristinubute,
Thank you for reaching out with these questions.
Each merchant has a unique Secret Key corresponding to their individual Merchant ID. It would have been provided by Afterpay to the merchant when their account was first provisioned. It’s a very long string of numbers and letters. Please try to copy and paste to avoid typographical errors.
The team can confirm that a 401 Unauthorized response from the Merchant API indicates that either the Merchant ID or Secret Key are incorrect.
For individual assistance configuring the plugin settings in the WordPress admin, you can share temporary access with a member of the Afterpay team. 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.
Forum: Plugins
In reply to: [Afterpay Gateway for WooCommerce] Critical Error in update to 3.8.1Hi @hirliman,
Thanks for reporting this error. The team are looking into this with a view to releasing a patch within the next hour.
It’s not clear why the file containing the function declaration would be included more than once, so we’d like to continue working with you in parallel to understand the cause. Did you ever observe duplicated Afterpay content at the checkout prior to version 3.8.1?
Thank you.
Hi @avong,
Thanks for following up.
Can you please confirm the details of the challenge you’re experiencing? Is it that some of your theme’s required scripts are not loading while the Afterpay plugin is activated? Is this only in conjunction with the WP Optimize plugin being activated?
In order for the Afterpay team to assist with the investigation, they will need access to the WordPress environment where the behaviour can be replicated. However, we cannot exchange access details via a public forum. Thus, we request that you please complete the form to raise a private ticket.
Thank you.
Forum: Plugins
In reply to: [Afterpay Gateway for WooCommerce] Large amount of scriptsHi @rochow and @seanconklin,
Thank you for your reports.
The team is aware of this challenge and looking into it. In the meantime, if this is impacting the store in a meaningful way, the team suggest taking a full site backup and rolling back to v3.6.1. If assistance to do so would be welcomed, 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 @avong,
Thanks 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 @galapogos01,
Thank you for your response, and for taking the time to explain some of the relevant details of your individual implementation. Particularly with regard to the WAF configuration, that’s very useful insight.
While we’re not able to disclose any specific details about our internal testing processes, we can confirm that your valuable feedback has been recorded in the appropriate place and brought to the attention of the appropriate people.
In the meantime, to further minimise risk as much as possible moving forward, please remember to perform your own testing in an isolated staging environment before deploying any changes to your production environment.
Please contact our support if you would like to pursue further investigation in this case.
Thank you.
Hi @galapogos01,
Thank you for your query and for expressing your concerns regarding the potential impacts of poor-quality software on your sales. We understand the importance of providing top-notch integrations for our merchants and continually strive to maintain the highest possible standards in all our releases.
Whilst we have robust quality control measures in place to ensure that our releases are functional and reliable, unforeseen issues that may not have been anticipated during testing can arise from time to time. We proactively monitor for issues and actively update our plugins, addressing them promptly and precisely.
Regarding the specific issue you raised regarding error logs, we believe this error would not have impacted orders, but please do not hesitate to contact our support if you would like this to be investigated.
Thank you.
Hi @japenz,
Thank you for your message.
There is no current method for implementing this, but a feature request has been raised internally. The team will review and prioritise the request and any future updates will be shared here.
Thank you.
Hi @galapogos01,
A fix for this issue has been released with version 3.7.1.
Please follow up if there are any further challenges.
Thank you.