Proxt VPS Direct Payment Module for Magento
UPDATE: ProTX is now known as Sagepay
We are happy to announce the launching of our first Magento Contribution: Proxt VSP Direct Payment Module.
This module provides access to the payment API provided by the best of the Protx services: VSP Direct Payment. VSP Direct Payment processes payments submitted from the vendor’s website providing a fast, secure and transparent way to purchase in internet. In addition, it can provide extra validation through 3DSecure validations redirections. For further information about Protx Gateway Payment and VSP Direct Payment please visit http://techsupport.protx.com/vspdirecthome.asp
Our implementation allows to Magento website owners to use this Protx product, and this module is a complement to other Protx Payment Payment Module created by Magento Team which has support for the product VSP Form of Protx. Both modules are available in MagentoConnect, the place to find the Magento Contributions to improve your Magento e-commerce experience.
You’re invited to try our module! You can download it from: http://www.magentocommerce.com/extension/163/protx-direct-payment-module and also you are able to read reviews, share your experiences, post comments and request new features.


Hi, I’m using protx-direct module in my magentoshop. I want to customize look n feel like putting my company logo etc. How I can do that.
Thanks in advance. Waiting for ur response.
Hi Anand,
You will find the html template of the payment form here:
app/design/frontend///template/payment/form/protxDirect.phtml
You can customize the look & feel easily by editing this file (if you know html & css).
Regards,
Jorge
Hi,
I am having problems with the module, it is not taking the config values from the website in a multiple website setup, but from the default. Any idea how I can fix this on V 1.1.6.
Thanks in advance.
John
Hi John,
We didn’t see errors with the config values from multiple websites with the Protx module, testing in the latest Magento version 1.1.6.
In case you can provide more details of your Protx configuration for each website, please post again so maybe I can figure out what is wrong.
Thanks for using Protx Direct Magento module!
Regards,
Jorge
Hi,
The problem is only when try to place an order through the admin, the payment methods/config are taken from the default config rather than the website config.
I am running two websites, one which hosts magento, the other which has a document root of websites/deadsea/ within the magento installation. The base url is set to the main website and the base link url is http://www.deadseaskincare.co.uk.
I have setup protx direct module and overridden all config values for the second website.
When placing an order through the admin for the second website (not on the front-end) the payment method and so config is taken from the default configuration for magento.
If you need any more info, please let me know.
One other behaviour I have noticed, if the payment method is disabled for the website then this is reflected in the available methods in the admin create order, so this setting at least is working!
Thanks,
John
Hi John,
We have just fixed this issue in the create order admin. However, we aren’t going to upload this modification in Magento Connect right now.
I have to mention this module will fail processing payments from admin in case of 3DSecure validation is required.
The following are the changes that you have to do manually in the file “app/code/local/B4Before/ProtxDirect/Model/ProtxDirect.php” in order to solve the configuration values issues in new order admin (you can mail me in case you want I send you the modified version of the file, jorge@ebizmarts.com)
—————————
Line 148, change from:
$result = $this->_postRequest($request);
to:
$result = $this->_postRequest($request, $payment);
—————————
Line 192, change from:
$result = $this->_postRequest($request, true);
to:
$result = $this->_postRequest($request, $payment, true);
————————
Line 300, change from:
->setVendor($this->getConfigData(’vendor’))
to:
->setVendor($this->getConfigData(’vendor’, $order->getStore()->getId()))
————————–
Line 303, change from:
$request->setCurrency($this->getConfigData(’currency’))->setDescription($payment->getCcOwner());
to:
$request->setCurrency($this->getConfigData(’currency’))->setDescription($payment->getCcOwner(), $order->getStore()->getId());
—————————
Line 371, change from:
protected function _postRequest(Varien_Object $request, $callback3D = false)
to:
protected function _postRequest(Varien_Object $request, $payment, $callback3D = false)
—————————
Line 379, change from:
$uri = $this->getConfigData(’mode’);
to:
$uri = $this->getConfigData(’mode’, $order->getStore()->getId());
—————————
Line 412, change from:
if ($this->getConfigData(’debug’)) {
to:
if ($this->getConfigData(’debug’, $order->getStore()->getId())) {
Thanks for reporting this bug!
Regards,
Jorge
Hi,
I installed the form version of Protx using magento 1.1.6 and it knocked out my categories, they went wierd and i could not access the sub cats at all. I have also lost all links to images for my categories. I uninstalled the Protx module and my categories list returned to normal but my image links are still broken. Why would this module do this to the backend of my magento and the categories?
Justin
Hi Justin,
We developed the module for Protx Direct but not the Protx Form module. It was created by the Magento Team (it’s a core module).
I see you have already reported the bug in MagentoConnect. It’s a curious problem, I can’t figure out what is the relationship between this payment module and the categories module.
Regards,
Jorge Bejar
Hi Jorge
We are having a couple of issues getting your great Protx direct module to work.
1) When the card details are entered - it always throws an error stating invalid expiry date - then if you choose the expiry date again (same) it works fine.
2) On clicking continue after entering all of the payment information the page just goes back to the shipping part of the one page checkout and you cannot proceed any further.
Very strange issues and I am sure something simple to fix / or that we are doing wrong - could you help point us in the correct direction?
Thanks very much.
Hi Simon,
Let me ask you a few questions in order to investigate what it’s wrong in your installation.
What Magento version are you using?
Did you install the latest version of the Magento Direct module?
Maybe there is a conflict with other modules? Which modules have you installed?
Regards,
Jorge Bejar
Are you aware of a problem processing HSBC Maestro cards? There is some discussion on the magento forum as these cards have 18 digits rather than the normal 16.
First of all, thanks for your interest!
Yes, we are aware. Our plan is have fixed this issue shortly (we’re going to handle it this week).
What Magento version are you using? - we are using v1.1.6
Did you install the latest version of the Magento Direct module? - yes we did via connect
Maybe there is a conflict with other modules? Which modules have you installed? - only the standard save credit card - we tried disabling that though and still no luck.
we are also seeing the issues decribed here :
http://www.magentocommerce.com/boards/viewthread/16594/
when in admin viewing orders
thanks for the help
Hi
Was there any update on the Meastro issue? Also, how can you remove a payment methord - We don’t accept Amex and can’t work out how to remove it from the list.
Thanks for a great system!
Pete
Hi everybody, we’ve been very busy the last weeks delivering a few Magento stores, so, sorry for the delays and “silence”, a developer will address the outstanding issues sooner than later.
Thanks for using the Protx Module!
We’ve just uploaded a new version of the module removing some javascript checkings to allow all Maestro Cards. It’s not the most elegant solution but it allows 18-digit Maestro cards and other with were getting problems in the previous version. Also, we’ve fixed some javascript errors in IE7.
Please keep in mind we’re testing it and it’s still under development (we keep the module in Beta status for this reason). Please check if it’s working properly for your website in a test environment before move it to live.
Forgot to mention … You can select which credit cards are accepted by your store. We added this setting for the new version of the module.
Hey,
Not sure if you’ve noticed but at the moment there is an issue with the package on the website - it’s saying this…
magento-community/B4Before_ProtxDirect requires package “magento-core/”
magento-community/B4Before_ProtxDirect requires package “magento-core/”
Install Errors
No valid packages found
PEAR ERROR: upgrade failed
…when I try to update.
I can not seem to install this via Mag Connect.
I receive an error which I have posted in the magento forum regarding this module, which states:
magento-community/B4Before_ProtxDirect requires package “magento-core/”
magento-community/B4Before_ProtxDirect requires package “magento-core/”
Install Errors
No valid packages found
Am I missing something simple here?
Other extensions seem to install no problem, just not this one which we really need… typical huh?
You’re right, the module package had some errors related with the required packages. Please try now with the release 1.1.4 of the module.
Thanks for the advise!
Yeh perfect all working correctly now.
Thanks!
[...] You can download the extension here , for more information about this extension click here [...]
Hi! I need to set up Protx as payment method on a site. We will be using VSP SERVER plan with Magento 1.1.8, does your module works with that?
I really have no idea how to do this! =(
Thank you!!!!
Melina,
The module can be installed as any other Magento Module. I’m not sure what you mean by “VSP Server Plan”, if it is a hosting plan, I guess that you’d have to ask your hosting company.
BTW, Magento 1.1.8 is OK.
I hope this helps.
Hi there
We are using the module. Everything has gone fine with the testing, but we have switched to live mode and transactions are still being sent to the Protx test server. Since the only options in the config are for the vendor name and the mode, I am not sure how to troubleshoot this. I have spoken to Protx and they have confirmed that everything is OK with our live account.
Any advice would be much appreciated.
Nick
Nick,
Do you still have problems with Protx module?
Please, be sure you have the latest version of the module.
Also, try to fix the problem cleaning the Magento cache.
[...] The other great thing I found with Magento was the sheer number of features which I hadn’t found when researching the product; but which we later put to great use on the site. Some of these are third party developments, such as aheadWorks fantastic ajax autocomplete solution ‘Search Autocomplete and Suggest’ or ebizmart’s simple Protx Direct module [...]
I have problem with this module since I upgraded magento and this module to 1.3.2.1.
Reinstall the module can’t solve the problem.
The payment failed and the email shows:
Payment transaction failed.
Reason
No date part in ‘’ found.
However, however, the payment has been taken as I can see them in my Sagepay account and all payments have been taken correctly. No order generated in Magento. some customers submitted payment too many times so I have to refund them.
anybody has the same problem?
Xiang,
Please refer to this forum posthttp://www.magentocommerce.com/boards/viewthread/43980/#t143167
Keep in mind that it’s a good practice to test everything on a test environment before pushing live. Also, the module is not yet compatible with Magento 1.3.2.1 (which was released 2 days ago), stick to Magento v1.3.2 and you’ll be fine.
Thanks.
Hi there, I stupidly installed V1.3.2.1 so does this mean I have to uninstall Magento and re-install V1.3.2 ? Also I am really hoping someone can help with a link to a step-by-step guide to installing and testing this module end-to-end. I am not a developer but have had to do all this integration myself due to cost.
Thank you,
Adrian
Adrian, the module is compatible with Magento v1.3.2.1, you can get more information or post doubts here http://www.magentocommerce.com/boards/viewforum/10195/
HI Ignacio,
Thanks for the reply, I am struggling to install the extension though and am getting the error below:
I have had problems getting things working on my hosting provider and have had to change the file permissions to 644. I changed the tgz file permission to 644 and tried to run the installer again but still get the error below, hope you can help?
downloading B4Before_ProtxDirect-1.3.2.2.tgz …
Starting to download B4Before_ProtxDirect-1.3.2.2.tgz (24,975 bytes)
. . . . . . …done: 24,975 bytes
Could not get contents of package “/home/pandafac/public_html/magento/downloader/pearlib/download/B4Before_ProtxDirect-1.3.2.2.tgz”. Invalid tgz file.
Download of “magento-community/B4Before_ProtxDirect” succeeded, but it is not a valid package archive
Error: cannot download “magento-community/B4Before_ProtxDirect”
Install Errors
Download failed
PEAR ERROR: install failed
Adrian, Magento module installs are managed internally by Magento, they host the files and the install process is fully managed by their code. You might want to try again later or report the issue to Magento if the issue still occurs.
Finally found the info I needed thanks to your great blog, thanks! ^^
Hi Ignacio..
It was a known bug which I have now sorted out. I am looking to upgrade to Magento version 1.3.2.3, will this work with the current version of your extension?
Regards,
Adrian
Protx / Sagepay module has ceased to function after changing server. “Gateway Request Error: Unable to read response or response is empty”
Any ideas what I haven’t turned on/off that would be causing this error.
Nick, did you try contacting SagePay’s support? What Magento and module versions are you running?
Running 1.3.1 and the latest module. Never had a problem before until i changed server.
Figured it. Turns out CurlSSL had buggered. Had to restart httpd.
Adrian Says:
Hi Ignacio,
any update on whether I can upgrade?
July 27th, 2009 at 6:13 am
Hi Ignacio..
It was a known bug which I have now sorted out. I am looking to upgrade to Magento version 1.3.2.3, will this work with the current version of your extension?
Regards,
Adrian
Adrian, yes, upgrading to latest version (Magento and Module) will work.
i can try to connect sagepay in my magento site which version is magento 1.2.0 but it cant install and display some below error.
downloading B4Before_ProtxDirect-1.3.2.tgz …
Starting to download B4Before_ProtxDirect-1.3.2.tgz (24,685 bytes)
. . . . . . …done: 24,685 bytes
ERROR: failed to mkdir /var/www/vhosts/Mydomain/httpdocs/app/design/adminhtml/default/default/template/payment/form
but i already set 0777 permisssion to all the files.
any idea about this please help me.
developer, double check your permissions. Also, keep in mind that the version on MagentoConnect is not compatible with Magento v1.2, contact us by email and we’ll email you the last working version for Magento v1.2.
I am having a problem installing the latest version of this. I get the following error :-
magento-community/B4Before_ProtxDirect requires package “magento-core/”
Any idea as to why ?
Hi Bhavvy,
Can you please try again?
Try installing this package: magento-community/B4Before_ProtxDirect-1.3.2.4
Thanks