Get the MageBase DPS – PaymentExpress Magento extension on MagentoConnect.
Features
- Use Payment Express either via PxPay or PxPost
- Adds new order statuses and configuration choices to fit your order workflow
- Displays transaction details in the back-end so you can be confident what you ship is what you have been paid for
Tested and approved by DPS.
PxPay Requirements
The extension uses the fail-proof notification by DPS to get notified of received payments – this requires internet connectivity (ie full testing on localhost will not work).
Some php / server configurations disallow access to the $_GET variable when it contains very long strings (2000+ characters) – if your server does this the extension will not work.
UPDATE: Please see the extension Trac pages for troubleshooting instructions: http://trac.fooman.co.nz/MB0002_DpsPaymentExpress/wiki
Screenshots
Originally published on magebase.com. Copyright © 2010 Magebase - All Rights Reserved.
Proud members of the 
Have installed the extension however on return to the website and the order success message is displayed no order confirmation is sent to customer.
Any ideas?
@Mitch See the link to the troubleshooting pages. We cannot help if we don’t know what your logs say.
Here is the log file contents;
2012-05-25T07:45:33+00:00 DEBUG (7): MageBaseDps successAction userid []
2012-05-25T07:45:33+00:00 DEBUG (7): MageBaseDps successAction result []
2012-05-25T07:45:33+00:00 DEBUG (7): 100000015 MageBaseDps User returned to Success Url
Only issue is customer does not automatically receive email notification of order, it has to be sent manually through order administration.
Cheers
Mitch
Seems like something is missing, you should see values for userid and result. Also, depending on whether you set DPS to Authorize or Purchase you should have a line saying: DPS Response: “Purchase OK – create Invoice” or similar. I assume you have configured the payment method with a valid DPS userid and pxpay key, and you installed the correct extension version for your Magento version.
Is your site access password protected or otherwise restricted?
What’s the status of the order in the backend?
Hi Robert,
The dps transaction response from the client’s browser is ignored and only the fail-proof notification from dps is processed by the extension, is that correct?
Cheers,
Tony
Yes that is correct.
Would it be possible for the extension to accept the first transaction response it gets? Whether it is via the client or from DPS?
I am asking this because DPS currently have a bug with their fail safe mechanism which sometimes causes a delay in the fail-safe transaction response being sent (Confirmed by them last week via a phone call).
I have found delays of up to 6hrs between the “via client browser response” and the “fail-safe response” in the DPS logs. This is causing a little bit of a headache for us as customers are complaining that they haven’t received their order confirmation email (thou they do eventually get this) and Mage is also holding stock until the fail-safe response is received regardless of the outcome of the payment.
Cheers,
Daniel
hi Daniel, I initially had the extension accept both customer return and DPS’s fail proof notifications. Unfortunately this lead to reports of the database locking up and/or multiple emails being sent. However this is about two years ago and if you want to give it a try you can do the following modification:
add
$this->_processSuccessResponse($this->getRequest()->getParam(‘result’));
just before
$this->_redirect(‘checkout/onepage/success’, array(‘_secure’=>true));
here
http://trac.fooman.co.nz/MB0002_DpsPaymentExpress/browser/app/code/community/MageBase/DpsPaymentExpress/controllers/PxpayController.php#L66
Let us know how it goes.
>Unfortunately this lead to reports of the database locking up and/or multiple emails being sent
Makes sense now that I think about it. Would be good if the first transaction response could some how acquire a lock for that order . Then then next response would be ignored if it was unable to get hold of the lock. Not sure if magneto has a lock mechanism but ill have a look around and let you know.
Thanks for your help. Much appreciated.
Cheers,
Daniel
We are currently getting two fail safe response notifications simultaneously (3 log entries per transaction). This is resulting in two invoices being created for an order. I have talked to dps and they assure me that there system is only sending out one. Anyone else having this issue ?
Any plans to support this?
http://www.paymentexpress.com/cvv2_mandate.html
Also, the trac link seems to be broken: http://trac.fooman.co.nz/MB0002_DpsPaymentExpress/wiki
Hi
Can this extension be used for a “one page checkout” setup?
Also do you offer services where I can get you to install this and get my payment gateway up and running correctly?
Thanks
Rainier
Hello Team,
I have installed this extension and it is working correctly on front-end, i have checked order details in back-end and found payment information not shown over there.
Can you please help to fix it?
@Sandeep
The extension works fine, both in the front and back end if installed and configured correctly. You have not provided enough detail for troubleshooting. We would need to see a screenshot of your order page to be able to check if your instance is working correctly or not.
Hey Robert,
Thanks for your reply
I am using extension on Magento EE v1.11, I am unable to attached screenshot here.
@all I have just uploaded a beta release of the DPS payment express extension to Magento Connect. It includes a couple of fixes, patches and support for the Cvv2 mandate stuff.
A detailed change log is here:
http://trac.fooman.co.nz/MB0002_DpsPaymentExpress/log/
If you run into any issues testing it please add them to the above issue tracker.
When a transaction fails on the DPS PxPay method, it sets the current order to Cancelled, and then the customer cannot checkout until their session expires. I am getting this exception:
Next exception ‘Zend_Db_Statement_Exception’ with message ‘SQLSTATE[23000]: Integrity constraint violation: 1062 Duplicate entry ‘XXXXXX’ for key ‘UNQ_SALES_FLAT_ORDER_INCREMENT_ID” in /XXX/lib/Zend/Db/Statement/Pdo.php:234
Could this be a compatibility issue with the Adjustware CustomNum module that is setting the Order ID’s?
Should I be trying to fix it by changing the DPS extension or the CustomNum extension?
Any advise would be appreciated!
Curious if PxFusion will be supported by this module in the near future?? It would be great to have customers enter their CC details on the shop site without the need for PCI certification (which seems to be the case here in NZ).