Error messages

  • Is there no better information that can be presented to the user in the case of an error than “Invalid field” or “An error occurred”?

    I recognise there are a wide range of possible error states, but when using the test numbers from here: https://help.trustpayments.com/hc/en-us/articles/4403290773905-Testing-card-payments The error messages are terse and unhelpful to the customer.

    Similarly “Please check the trust payment fields” isn’t particularly consumer friendly. “Please check your card details are correct and try again” might be more helpful.

    Finally – if I test with the test number and security code “214”, the first time I get “Invalid field”, if I repeat with exactly the same details, I get a successful transaction. Shouldn’t the same numbers return the same error code?

    Thanks in advance. I plan on switching to this plugin on Tuesday. Is there an updated version planned in the very near future that I should hold off?

Viewing 1 replies (of 1 total)
  • Plugin Contributor Illustrate Digital

    (@illustratedigital)

    Hi @murrayelliot2, thanks for your feedback – this has been passed on to the development team.

    Regarding the next release, we have a roadmap we are working to for a number of improvements and added functionality, however a release date for this hasn’t been confirmed. This will most likely be in around one to two week’s time however I wouldn’t suggest holding off installing it on that basis, so long as it provides what you need at this time.

    Thanks

Viewing 1 replies (of 1 total)
  • The topic ‘Error messages’ is closed to new replies.