eWAY: PCI checks are failed error on submit

  • Profile Image
    amitchell
    Asked on April 25, 2019 at 10:35 PM

    Hi support,

    We are getting this error on all our forms that have a payment gateway.

    Can you please confirm if there are any issues at Jotform end.  


    We get the error when we press Submit after putting our CC details in


    https://submit.jotform.co/submit/90548232205855/


  • Profile Image
    amitchell
    Answered on April 25, 2019 at 11:31 PM

    Please note I have checked with Eway and they have confirmed they can see Jotform trying to connect however drops.  Eway have confirmed not there end


  • Profile Image
    BJoanna
    Answered on April 26, 2019 at 03:00 AM

    Sorry for the inconvenience this may have caused you. The issue is on our end. Our developers are already informed and they are working on it. We will update you via this thread once this issue is resolved. 

  • Profile Image
    qrme
    Answered on April 28, 2019 at 08:58 PM

    We are also experiencing this error. Has it been resolved?
  • Profile Image
    ADYO
    Answered on April 28, 2019 at 10:55 PM

    We are also experiencing this problem - Has it been resolved - Adelaide Youth Orchestras 
  • Profile Image
    roneet
    Answered on April 29, 2019 at 12:44 AM

    @qrme & @ adyo

    I have moved your concerns to a separate thread.

    We will address it shortly.

    Thanks.


  • Profile Image
    cheerbrandz1
    Answered on April 29, 2019 at 12:56 AM

    Any update on this as now getting this error.
  • Profile Image
    BJoanna
    Answered on April 29, 2019 at 02:08 AM

    @cheerbrandz1

    I moved your question to a separate thread. 

    https://www.jotform.com/answers/1806734

  • Profile Image
    olivia
    Answered on April 29, 2019 at 08:25 AM

    Hi @amitchell,

    The issue is fixed. I tested your form and it is working fine. Please check your form and back to me if you replicate the issue.

  • Profile Image
    amitchell
    Answered on May 01, 2019 at 10:46 PM

    Hi support, this is now fixed.

    Thankyou