ability access account admin among applying authorize cart centrally-managed code common contact copy don ejunkie files gateway help higher impossible integrate key merchant merchants methods net process replace secure seller service shared shopping software solution system transaction url user users

hello all!

i have authorize.net emulation through eprocessing network and when i test drove the e-junkie shopping cart, after entering corresponding id & transaction key, it said merchant id/pw incorrect or account is inactive.

i spoke to eprocessing and they said that e-junkie is probably pointing to

https://secure.authorize.net/gateway/transact.dll

when it needs to point to

https://www.eprocessingnetwork.com/cgi-bin/an/order.pl

... does anyone know how to do this from seller admin?

thanks so much for your help

I am not sure what you mean by "authorize.net emulation", but E-junkie can only integrate directly with Authorize.Net itself, not with some other service that works like Authorize.Net or as a middleman between you and Authorize.Net.

It's not using authorize.net as a middle man at all. It's using the authorize.net gateway code to process transactions with EPN, as EPN uses the same methods as authorize.net.

Every authorize.net gateway set-up points the user to a secure server to finish the transaction process. All one has to do, as stated above, is replace the authorize.net URL with the EPN url, and voila.

I've never really used eJunkie but I can tell you that if you don't have FTP access to all of your shops files, you're not going to be able to get this to work on your own. You will need to contact someone higher up and see if they can do it for you. The authorize.net module they are using COULD be a shared module among all eJunkie users, which might make the change impossible.


Switch to zencart. lulz.

Yes, since E-junkie is a centrally-managed "software as a service" shared in common among all our merchant subscribers -- rather than a licensed software package where each merchant installs their own copy of the software on their own server (e.g. zencart) -- it's not possible to change how our system works for one seller without applying that same change to every other seller using our service. Our solution spares merchants the technical hassle of installing and configuring software and an SSL cert on their own server, but that necessarily involves tradeoffs, such as giving up the ability to modify the backend software directly.