Proxt VPS Direct Payment Module for Magento
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.
Tags: contribution, Magento, module, payment, protx, vsp direct, vsp form
August 12th, 2008 at 12:12 am
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.
August 12th, 2008 at 8:45 am
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
September 25th, 2008 at 10:45 am
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
September 26th, 2008 at 10:54 am
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
September 29th, 2008 at 9:31 am
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.
September 29th, 2008 at 10:16 am
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
September 30th, 2008 at 10:07 am
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
October 1st, 2008 at 7:13 am
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
October 1st, 2008 at 11:12 am
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
October 31st, 2008 at 9:58 am
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.
November 6th, 2008 at 2:09 pm
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
November 9th, 2008 at 1:56 pm
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.
November 10th, 2008 at 9:01 am
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).
November 11th, 2008 at 8:24 am
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.
November 11th, 2008 at 8:27 am
we are also seeing the issues decribed here :
http://www.magentocommerce.com/boards/viewthread/16594/
when in admin viewing orders
thanks for the help