We use the Converge / Elavon / Virtual Merchant - myvirtualmerchant.com extension by Robert Mullaney. While testing to be sure that our cart would still work on Nov. 1st after the SHA2 switch, I discovered that we are supposed to be submitting the data to a url other than the one used by the extension.
The information I found was here: http://www.besha2ready.com/converge
You'll see that to conduct a test transaction, you submit data to the url: https://api.demo.convergepay.com/Virtua ... cessxml.do
Once you've verified that it works, you can switch to the production url: https://api.convergepay.com/VirtualMerc ... cessxml.do
Currently the extension (and even the Converge developer guide!) use the url: https://www.myvirtualmerchant.com/Virtu ... cessxml.do
I emailed their tech support to ask if we needed to switch to the new url, or will the old one continue working. They replied today that we do need to switch. They are leaving the old one working for now, but as of October 31 everyone should have switched, and they don't guarantee how long they'll leave the old urls active.
If you care to give me a contact email, I can forward the email to you. (Please note that the support url included in your extension readme file does not work.) I can mod the extension to use the new URL, but wanted to be sure this was noted by the developer, because I saw in a comment on the extension page that he says the SHA2 switch has nothing to do with his extension, it's about your browser and SSL certificate and host. Which is mostly true, except for what tech support said regarding the url we are using.
Who is online
Users browsing this forum: No registered users and 3 guests
