ecart and Protx

[bobwales349753]

Anyone else troubled by this problem?
Protx upgraded their protocol to 2.23 on 3rd March and so their testing servers will no longer accept the eCart fields, even if you change the protocol version from 2.22 to 2.23.

Fields that were optional have now become compulsory.

If anyone has a fix for this I'd be grateful to hear about it.

Explanation: https://support.protx.com/forum/FindPost7777.aspx

[bobwales349753]

It appears that only the testing server at Protx requires protocol 2.23

If a full Protx account has been granted, then carts can be tested against a test server which WILL process protocol 2.22, for the time being.

So, Ecart will work with Protx, but only after a formal application is made and approved.

The free test server, which is available without any committment or merchant number, will not work until Ecart is configured for protocol 2.23

Hope this helps

[sales356151]

Protx has now changed to SagePay is there going to be an update for ecart checkout wizard?

[Ray Borduin]

Yes we are already working on the protx updates.

[steve365364]

Is there any word on when an update will be available - as nothing i do can get the cart to work with sagepay - therefore my website does not work...

[Ray Borduin]

It is my understanding that our current proTX solution should still work. It just doesn't work with thier sandbox any more. Did you actually have a site stop working because of this issue?

[steve365364]

Yes - the site I have has stopped working now - the information that sagepay is requiring is not in anyway the same as is being output by the cart plugin for dreamweaver. I have been in contact with sagepay - they agree.

[Ray Borduin]

I was under the impression that they would continue to support their old API for some time. I know we don't match the new sagepay technique, but the old proTX technique shoudl still work.

Please post a support incident and we can get an engineer to work with you directly to try to resolve this problem.