Pre-sales: Questions about 97/98 errors, caching and customer behaviors.

  • Resolved vpreatr

    (@vpreatr)


    8 years, 1 month ago

    We’re seeing 97 and 98 errors with our current Authorize.Net gateway and despite verifying server time and related factors, all appear in order. What appears to be happening is that customers don’t enter their credit card information at the input screen and then decide to pay hours later, day(s) later and simply re-use the same input screen they never left and as such the time-stamp is likely causing the errors mentioned above.

    How does your gateway handle, a. caching (server/browser), b. customers that don’t pay immediately and just leave the pay input section open (for hours/days) then attempt to pay through that original screen.

    I’m interested in switching to your gateway, although, only if I can resolve some of issues I have with our current gateway.

    Thanks!

Viewing 1 replies (of 1 total)

  • Hi @vpreatr,

    We just analyzed the error 97 and 98.

    Both these errors occur in SIM API.
    However, we currently refer the AIM API in our plugin.

    Hence, we can conclude that these errors should not come up with our plugin.
    You can try using the plugin once and let us know if you face any problem.

Viewing 1 replies (of 1 total)
  • The topic ‘Pre-sales: Questions about 97/98 errors, caching and customer behaviors.’ is closed to new replies.