V6126: Invalid encrypted card number, decryption failed Order status changed fro

  • Resolved robadeedoo123

    (@robadeedoo123)


    2 years, 4 months ago

    V6126: Invalid encrypted card number, decryption failed Order status changed from Pending payment to Failed.

    From time to time this happens at check out. Same person will then check out ( using eway) and its fine. Sometimes they abort. Reading the error logs on eway it states that this is a private key type issue but as most orders process fine and it only happens now and again and then the same people on the same device and the same browser then reprocess fine I am wondering if you have any pointers for me on how to resolve this?

    https://www.characterparties.com.au

    Cheers have a good day.

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

    (@webaware)

    G’day robadeedoo123,

    I’ve looked at all the things I can look at, and the only thing I can suggest is that you investigate the JavaScript errors that are happening on your checkout page. They look to be coming from the Afterpay integration. It could be messing with the encryption script from Eway in some way. If you can stop the errors, it might stop messing up the encryption.

    cheers,
    Ross

    Thread Starter robadeedoo123

    (@robadeedoo123)

    Cheers Ross. I did notice this and they are actually coming from Humm I think. I have sent copies to the Humm Dev team. No doubt they will blame anyone but themselves as usual. It only happens now and again.

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘V6126: Invalid encrypted card number, decryption failed Order status changed fro’ is closed to new replies.