Protx Changes from August 1

[bekyed]

Hi Bill,

I installed the new psps setup and still had the 2.20 protocol, so i swapped this for a copy of the 2.22 protocol from a link on here.

Wayne.

[hammocks]

Integrating Actinic 7.0.7 with Protx

Hi

Can anyone help me - I have Actinic 7.0.7 and am trying to integrate this with Protx. My site is presently set up to capture card payments using a secure server.

I have followed all the steps as directed in the earlier part of this thread by Bruce.

After I put in the card information a message comes up saying that I will now be transferred to Protx where the card information will be captured. After clicking next the following message comes up:

'This transaction attempt has failed. We are unable to redirect you back to the web store from which you were purchasing. The details of the failure are given below.


Status: INVALID


Status Detail: 5030 : Unable to decrypt the request message. This might be caused by an incorrect password or invalid encoding.'

Any ideas?

[Darren B]

Before someone else mentions it, please read the sticky for new users, please search the forum, you might be supprised what you find, welcome on board but believe me when i say 95% of the problems people have already have the answers to

http://community.actinic.com/showthread.php?t=32137

[oracle]

This is the V8 solution:

http://community.actinic.com/showpos...86&postcount=9

I found this by searching for 5030

Not sure about V7 though.

[mington]

Hi

My customers have been receiving an error message from sage pay when completing a transaction.
-------------------------------
error number - 2147483638

you have been charged for this transaction although the vendor may not be aware of this
-----------------------------------

we're using v9
www.paramountbathrooms.co.uk

trawling both the actinic and sagepay forums i found that the problem was sorted way back in 2007 and no ones mentioned it since.

I've looked in my OCCUpgrade.ini file:

[OCCProvider:22]
ID=22
ProviderName='Sage Pay'
TestModeAvailable=1
PreAuthorizedAllowed=1
AuthorizedAllowed=1
ClassID='{AC090055-2C97-11D3-97D6-080000511272}'
ClassIDManager='{AC090055-2C97-11D3-97D6-080000511272}'
PlugInScriptName='OCCPROTXScriptTemplate.pl'
ProviderURL='https://live.sagepay.com/gateway/service/'
RemoteProcessScript='vspform-register.vsp'
DBPlugInScriptName='OCCPROTXScriptTemplate.pl'
DBProviderURL='https://test.sagepay.com/gateway/service/'
DBRemoteProcessScript='vspform-register.vsp'
Debugging=?1
TechnicalFailAllowed=0
FinancialFailAllowed=0
OnlyAuthorize=?0
TemplateName='Act_OCCPROTXTemplate.html'
SiteSubDirectory='CommonOCC'
MaxURLLength=-1
AvailableOffline=1
AvailableOnline=1
AccountRegistrationURL='http://www.actinic.co.uk/psp/protx/index.htm'


I've spoke to actinic, and they told me that it was a problem with sagepay, and that they had made a fix but had not informed actinic as to what it was.

so now i'm waiting for a reply from the sage pay support and forum.....

Could any one help me on here, it would be greatly appreciated if anyone has knowledge of why this is happening.

Apparently our site has lots of traffic and we're planning on moving up to actinincs bigger/faster server

could our customers be receiving this message because our sites to busy?

thank you