Plugin Conflict with Afterpay

  • Hi there. We notice that sometimes customers will use Afterpay to pay for orders and sometimes this payment will fail ( normal behaviour). If the customer then tries to pay by credit card using the eway gateway then the payment errors as follows:

    Transaction failed
    V6111: Unauthorised API Access, Account Not PCI Certified
    V6010: Invalid TransactionType, account not certified for eCome only MOTO or Recurring available Order status changed from Pending payment to Failed.

    Usual payments via eway credit card function normally without the error message above it only happens if the customer has tried first with Afterpay. We have contacted eway who have looked at their logs. they are telling us that the payments are failing in these instances as once they have tried Afterpay the payments are then being sent to them unencrypted and they fail them using the message above. they have told us to contact you via this method to advise you of the issue and for you to make code amendments to resolve the issue. the issue is fairly infrequent but is none the less an issue. Thanks!

Viewing 8 replies - 1 through 8 (of 8 total)
  • Plugin Author webaware

    (@webaware)

    G’day robadeedoo123,

    Sounds like the Afterpay add-on is stuffing up the script on the page. Can you tell me which Afterpay add-on please, and if it’s free? If I can load it locally, I can see what it’s doing wrong and maybe work out what to do about that.

    cheers,
    Ross

    Thread Starter robadeedoo123

    (@robadeedoo123)

    Hi ross!

    We are using “Afterpay Gateway for Woocommerce” version 3.3.1 all up to date.

    It is a free plugin provided by Afterpay to facilitate their services.

    Thread Starter robadeedoo123

    (@robadeedoo123)

    This issue is still unresolved and still occuring. When do you propose to fix it?

    Plugin Author webaware

    (@webaware)

    I’m unable to test the Afterpay integration without a sandbox account, and can’t see how to apply for one without being a merchant. I’ve asked Afterpay for assistance, please bear with me.

    If the script problem is caused by something Afterpay is doing, then you will need to ask for their assistance. Have you contacted them about this problem?

    cheers,
    Ross

    Thread Starter robadeedoo123

    (@robadeedoo123)

    Yes they said to contact you so I am the meat in the sandwhich….

    Plugin Author webaware

    (@webaware)

    Seems to be a two-meat sandwich currently, awaiting a sandbox account with Afterpay.

    cheers,
    Ross

    Plugin Author webaware

    (@webaware)

    G’day @robadeedoo123,

    Please contact Afterpay support again and tell them you are the merchant related to their support ticket reference 14511869. They need a relevant merchant in order to set up a sandbox account.

    Alternatively, if you can set up a staging website with both the Afterpay and Eway extensions running in sandbox mode, I can examine that. It very much sounds like the problems are all browser-side with a JavaScript problem, so I should be able to diagnose from a staging website.

    cheers,
    Ross

    • This reply was modified 3 years, 2 months ago by Afterpay. Reason: wrong post
Viewing 8 replies - 1 through 8 (of 8 total)
  • The topic ‘Plugin Conflict with Afterpay’ is closed to new replies.