SecurePay - the contrib vs authorize.net aim with translator

[tincan]

Hello.

 

We've got an osc store set-up (v2.2 RC2) running and are looking at possibly going with SecurePay for processing credit card transactions. (switching from another company who is less economical for us)

 

SecurePay says that osc works, but talking to a tech support guy, he said to use the provided contrib - looking at the contribs, this module is from June 2003: "SecurePay.com Payment Module (USA)"

 

Searching the forums, I have also found that securepay says that they have an authorize.net translator and you just need to use the authorizenet_cc_aim module and change the gateway path:

simply search the code for this line:

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

and replace it with:

https://www.securepay.com/AuthSpayAdapter/process.aspx

 

Has anyone gone with securepay?

Which method have you used?

Are you satisfied?

Any issues to watch out for?

 

Thanks for any advise you can provide.