Thread Starter
emw
(@emw)
I have also tried regenerating the Transaction Key and Response Key. Didn’t change anything. Global Gateway says to put the Response Key in the MD5 hash field in the the eShop settings, does that sound right?
FYI, if you have not seen these pages …
eShop is THE plugin that they mention for use with their gateway
https://firstdata.zendesk.com/entries/459000-shopping-carts-that-work-with-first-data-global-gateway-e4sm
but the latest testing looks like it was done with WordPress 3.0.1 and eShop 5.7.7, might there have been any interesting changes in the time since then?
https://firstdata.zendesk.com/entries/459000-shopping-carts-that-work-with-first-data-global-gateway-e4sm
It’s a nice plug for eShop, but if it’s outdated …
Thank you
Anonymous User
(@anonymized-3085)
There have been changes since then – in eShop and authorize.net
All I can suggest is that you double check all settings, and ensure no other plugins are active when you test.
Thread Starter
emw
(@emw)
actually using Global Gateway e4, if that makes any difference … I doubt it does … I am still trying to get feedback from them, since I followed their set up instructions …
does it sound right to put the Response Key in the eShop MD5 hash field?
if I sent you the response email with all the detail data, might you be able to take a quick scan of it to see if there is an obvious error?
Thank you
actually using Global Gateway e4, if that makes any difference
Yes it does. The plugin does not support that gateway.
Thread Starter
emw
(@emw)
I modified the authorizenet.php file to work with Global Gateway (see mods in my first posting), and the transaction actually goes through perfectly … it’s just something in the “after the transaction” feedback that is generating the fail message …
Please understand that we cannot provide free support for hacks to any of the eShop scripts. Nor can we help you troubleshoot your hacks. We simply don’t have the time. The plugin is free but we have to spend most of our time trying to earn a living.
If you are a coder, all we can suggest is that you refer to the code & its comments.
Thread Starter
emw
(@emw)
I totally understand … and I am more of a wannabe than a coder (actually I don’t really want to be … I’m the graphics guy)
anyway, I ended up with eShop because the Global Gateway folks recommend it on their support pages … thought you might want to know ‘cuz it could be good for you (if it can work smoothly … which it mostly does …)
I ended up with eShop because the Global Gateway folks recommend it on their support pages
That’s news to us. Have they created an add-on plugin for their gateway? We’re actually reducing the number of the gateways supported by the core plugin.
Thread Starter
emw
(@emw)
no, no plug-ins, just modify the authorizenet.php … I think they say you can use any cart software (in theory) that is compatible with Authorize.net SIM
FYI: check out WordPress tutorial …
https://firstdata.zendesk.com/entries/459000-shopping-carts-that-work-with-first-data-global-gateway-e4sm
That’s referencing a very old copy of eShop – 5.7.7. The current version is 6.2.12
Thread Starter
emw
(@emw)
yep
for my conversations with them, how old is 5.7.7?
Off the top of my head, about 2 years old.
Thread Starter
emw
(@emw)
any words you would like passed on to Global Gateway (aka First Data) … they did just recently come out with the e4 product which is designed to be easy enough for people like me to use … and is (theoretically) a nice solution for integrating a shopping cart into WordPress
Thread Starter
emw
(@emw)
still trying to figure this out … it is so close …
in doing some further reading, I found a recommendation that if using Fatcow.com as host, I should visit my php.ini and increase memory limit to 64 and check the session save path … done, didn’t help
I had never tried a cash payment … that went through fine
it really does seem as though the problem is in eshop receiving/understanding the message that the transaction went through … either my gateway is sending a message that eshop does not understand, or eshop is not able to hear the message …
should I ask the gateway folks to look at the file: eshop/authorizenet/authorizenet.class.php … is this where the magic should be happening?
thank you
Thread Starter
emw
(@emw)
There appears to be an error in the generation of the response hash, the generated code converts all alpha characters to upper case … the original is lower case. Is this something that could be fixed? Thanks.
Below is from Global Gateway support:
To sum up what we discussed via phone, the eShop plug is converting the
generated “response hash” to all upper case letters, as seen below in
the line: mycheckmd5: F49D32A181AF5C2BD9E45EC0FC71BE18. The string it
is attempting to match is the one returned from the E4 gateway in the
line: x_MD5_Hash: f49d32a181af5c2bd9e45ec0fc71be18. I do believe the
removal of the function to convert the md5 string to all uppercase
(STRTOUPPER()) should resolve this issue.
