Barclaycard ePDQ for 1.3.7

I have installed the installation files and setup the Payment module in ZenCart. However, I am having no luck setting up the EPDQ CPI parameters as I keep getting "INVALID URL ALLOWED" from the Barclays website.

I think the problem may be the Allowed URL and/or the POST URL. What should these be?

I noticed a very old post that stated HTTPS on the POST URL was not allowed, is this still the case?

Any advice greatly appreciated.

It's most likely the allowed URL as the POST URL that you set in your CPI admin is over-ridden (for good reason) by the mod.

I don't know whether https addresses are not supported and would recommend talking to ePDQ support directly on this point. They're open until midnight.

Oops. Previous response was sloppy. Confused POST and return URLs. But the main part remains the same - a problem with the allowed URL.

After further testing it seems that the POST URL is a bit limiting. Basically Barclays require an absolute URL and does not allow session ids.

Originally the post URL was in the following format:

http://www.domain.com/checkout_confirmation.htm?zenid=123456789

This needed to be changed to:

http://www.domain.com/checkout_confirmation.htm

We have had to amend the previous page (Checkout Payment) so that the post URL from this page excluded the zenid parameter. This meant when the page redirected to barclays the referrer was correct.

How did you get around the issue if the customer completes the transaction, but doesn't press continue on the final ePDQ page, leaving you with cash, but no return to Zen Cart to complete the order?

How are you recognizing and handling a declined transaction in Zen Cart?

abrown21:

Basically Barclays require an absolute URL and does not allow session ids.It's possible that you're mixing up the POST and return URLs here. Though your comment would apply to both but at a more fundamental level.

It seems to me that Baraclays are stripping away all URL parameters (which does have some security benefits) and replacing them with the order ID for the return URL and the transaction status data for the POST URL. Dynamic URL parameters such as used by Zen Cart by default and session IDs are just two examples of what gets stripped.

I haven't go this far yet... we are waiting on Barclays to put the account live as the sand box area does not support a full transaction test apparently! :censored:

I'll keep you informed... no doubt back for more advice!

They told me they didn't have a Sandbox only a live environment, but that we could have a test account against that. Haven't been able to make that happen though, and we've ended up testing in the live environment against a live site :censored:

Stand by for a PM.

Every Time i Install this mod it removes all my payment Module

With

With Out

Even without the problem, you seem to be missing some payment modules, i.e. authorize.net.

I doubt that the modules are being removed, but rather that there's a php error occuring. I've just downloaded the mod from the downloads area to check that it hadn't been corrupted. It installed with no problem, so this looks like something local to your system.

I would recommend installing the Zen Cart Debug Logger to find out what the error is and where its occurring.

I removed the authorize.net to see if was a space thing and the de buger shows no bugs but dont no why they all dont go?

I doubt that they have all gone, just that the page stops rendering after it hits a PHP error. What does the debug utility tell you about the error?

it report no bugs:blink:

in the epdq.php file should there be ?> and the end

[26-Nov-2008 14:07:44] PHP Parse error: syntax error, unexpected T_STRING, expecting T_OLD_FUNCTION or T_FUNCTION or T_VAR or '}' in /hermes/bosweb/web275/b2757/ipw.tuneyourcar/public_html/includes/modules/payment/epdq.php on line 13

tuneyour:

in the epdq.php file should there be ?> and the end
No there shouldn't.

In times past closing PHP tags at the end of files was generally considered to be good practise. However, that approach could be problematic as FTP programs sometimes deposited hidden characters after the fuinal closing tag (e.g. end of line markers) leading to almost header errors that were almost impossible to track down.

So nowadays we usually leave off the last closing tag since the PHP parser automatically treats the end of file marker as a closing tag, and we avoid the aforementioned risk.

tuneyour:

[26-Nov-2008 14:07:44] PHP Parse error: syntax error, unexpected T_STRING, expecting T_OLD_FUNCTION or T_FUNCTION or T_VAR or '}' in /hermes/bosweb/web275/b2757/ipw.tuneyourcar/public_html/includes/modules/payment/epdq.php on line 13Good news is that that as an error would explain the behaviours you're seeing. Bad news is that the copy of the mod that I downloaded earlier today doesn't cause that error or have anything that could cause it. Maybe your copy is corrupted.

what is the best FTP to use and just to make sure could you e-mail me the file to [email protected] and if this dose not work how much would it cost for someone to set it up for me as im running out of time:(

and remember its for v 1.3.8

sorry to keep posting can i use Version: 1.0 as im getting this one to work in my payment Module just not filled the rest of the info out yet as i wanna make sure im not wasting my time

[02-Dec-2008 13:43:02] PHP Parse error:  syntax error, unexpected T_STRING, expecting T_OLD_FUNCTION or T_FUNCTION or T_VAR or '}' in /hermes/bosweb/web275/b2757/ipw.tuneyourcar/public_html/includes/modules/payment/epdq.php on line 13

Here is a new one that comes up