gateway question.

General ShopSite user discussion
Post Reply
pixelOneZero
Posts: 4
Joined: Sat Aug 01, 2009 2:41 pm

gateway question.

Post by pixelOneZero »

My client who is using Shopsite has chosen goEmerchant as the gateway provider.

Does shopsite support goEmerchant as a gateway?

On goEmerchant's site they claim that they work with shopsite:
http://www.goemerchant.com/techsupport/gateway.htm
Jim
Site Admin
Posts: 4953
Joined: Fri Aug 04, 2006 1:42 pm
Location: Utah

Post by Jim »

The only ShopSite supported gateways are those listed in the online help at :
http://shopsite.com/help/10.0/en-US/sc/ ... tions.html

goEmerchant mention Authorize.net on their site. It may be that they emulate Authorize.net's interface so it might work with that interface but there is no guarantee.
pixelOneZero
Posts: 4
Joined: Sat Aug 01, 2009 2:41 pm

Post by pixelOneZero »

thanks for the reply, Jim.

I was just IM'ing with a goEmerchant techie, and he said they do offer an emulator for Authorize.net. I'm reading through the documentation now and will report my results back.
pixelOneZero
Posts: 4
Joined: Sat Aug 01, 2009 2:41 pm

Post by pixelOneZero »

Ok, I have some specific information that the technical contact at goEmerchant gave me.

In the shopsite dash, when I click "Configure Processor", the host URL for Authorize.net is: secure.authorize.net

However, the goEmerchant person says it should be: https://secure.goemerchant.com/secure/g ... teway.aspx
instead.

Is it possible to have the current host URL changed to https://secure.goemerchant.com/secure/g ... teway.aspx

?
Jim
Site Admin
Posts: 4953
Joined: Fri Aug 04, 2006 1:42 pm
Location: Utah

Post by Jim »

You would need access to the server the store is hosted on and change tokens in the anet.aa file in the store's data directory. Just which of the tokens you would change would depend on what goemerchant uses.

Again there is no guarantee that changing the settings will actually allow ShopSite to communicate with their gateway.
pixelOneZero
Posts: 4
Joined: Sat Aug 01, 2009 2:41 pm

Post by pixelOneZero »

Wow, I would not have guessed that.

Jim, for expediency (my client really needs to get their site up fast since Halloween approaches) would you suggest that my client just contact Authorize.net, set up an account directly with them, and things should work more smoothly?
Jim
Site Admin
Posts: 4953
Joined: Fri Aug 04, 2006 1:42 pm
Location: Utah

Post by Jim »

Definitely. Or one of the other gateways that is built into ShopSite.
QualityTrading
Posts: 2
Joined: Wed Sep 23, 2009 7:25 pm
Location: USA

Post by QualityTrading »

Jim wrote:You would need access to the server the store is hosted on and change tokens in the anet.aa file in the store's data directory. Just which of the tokens you would change would depend on what goemerchant uses.

Again there is no guarantee that changing the settings will actually allow ShopSite to communicate with their gateway.
I have access to the server. I see 2 .aa files, one of them being "global.aa". I am inexperienced in this area, specifically changing "Tokens". What are these Tokens exactly?

I am trying to use Charge One as our gateway. Charge One supports emulation of Authorize.net and one of the requirements was to change the post URL. Need help please, thank you.
Jim
Site Admin
Posts: 4953
Joined: Fri Aug 04, 2006 1:42 pm
Location: Utah

Post by Jim »

The file would be anet.aa not global.aa. If it doesn't exist go to the Commerce Setup > Payemnt screen and configure Authorize.net with the user id info that you have for your other gateway. Note what the url(s) might be on that screen. Save changes. Then edit the anet.aa file and change the server url(s) to what your other gateway wants.

Note that tokens all end with a : and must have a space after that before the value you insert.

Again there is no guarantee that this will work.
QualityTrading
Posts: 2
Joined: Wed Sep 23, 2009 7:25 pm
Location: USA

Post by QualityTrading »

Jim wrote:The file would be anet.aa not global.aa. If it doesn't exist go to the Commerce Setup > Payemnt screen and configure Authorize.net with the user id info that you have for your other gateway. Note what the url(s) might be on that screen. Save changes. Then edit the anet.aa file and change the server url(s) to what your other gateway wants.

Note that tokens all end with a : and must have a space after that before the value you insert.

Again there is no guarantee that this will work.
I have contacted our hosting company and they informed me that they can make the change for us.

Thank you for the response.
Post Reply