Jump to content

eWay Payment Gateway - UK


Recommended Posts

Hi there,

has anyone used eWay as their payment gateway?

If so did you use their downloadable module from their site?
Did it integrate ok without issues?

Any other advise or feedback would be great!

EWay are offering us the best deal as the module is FREE! Sagepay is our other option but the module costs 300 Euros!!!

Thanks in advance
Gary

Link to comment
Share on other sites

Hi Gary,

I'm a Senior Support Engineer at eWAY and I was involved in building the PrestaShop module. It works great! Just make sure that you have cURL compiled on your server (very standard feature) and you'll be up and running within minutes.

If you want, download and install the module and set it to Test Mode so you can get a feel for our customisable shared page.

Feel free to contact us on [email protected] if you have any issues but I'm confident you can get it working easily enough, all you have to do is upload the eway folder to the modules sub directory and your off!

Let me know if you have any questions/issues.

Kind Regards,

Maclean
Senior Support Engineer
eWAY

Link to comment
Share on other sites

FYI: I just noticed a mistake in the version available on our site.

ewaysharedpage.php
Line 493

$posturl="https://www.ewaygateway.com/Gateway/UK/Results.aspx?".$querystring;

SHOULD BE

$posturl="https://payment.ewaygateway.com/Result/?".$querystring;

I'll have the latest version uploaded to our site but just check that line when you download it.

Maclean

Link to comment
Share on other sites

FYI: I just noticed a mistake in the version available on our site.

ewaysharedpage.php
Line 493

$posturl="https://www.ewaygateway.com/Gateway/UK/Results.aspx?".$querystring;

SHOULD BE

$posturl="https://payment.ewaygateway.com/Result/?".$querystring;

I'll have the latest version uploaded to our site but just check that line when you download it.

Maclean


I changed the line and it came up as an error in Back Office of Prestashop. (Parse or something it said). So I reverted back to the original and it seemed to work.

I'm running test mode now to see what it is like and I thought it would be an iframe on my page but it actually redirects to eWay, is this correct?

Gary
Link to comment
Share on other sites

Hi Gary,

That is correct, it diverts to a page on our servers.

Containing an SSL encrypted page within a non-SSL encrypted page has the potential to raise security issues with your customers and the most recent updates to UK/Europe banking requirements means that merchants must divert to their gateways servers when taking credit card details.

I'll look in to that error but that line shouldn't create any issues in the PrestaShop BackOffice.

Thanks,

Maclean
eWAY

Link to comment
Share on other sites

  • 1 month later...

Maclean, I've been in contact with eWay NZ because I can't get a proper response code from the eWay Prestashop module on the www.eway.co.nz website.

Link to module page

Support has told me that the listed module is not compatable with v1.3.3 of Prestashop. Yet from your comments here it seems that it should be.

So, here's the problem. The module installs and configures fine. It accesses the eWay transaction page and verification page just fine. (I'm using the standard test account and test CC number. I use a transaction amount of 10.00 which should return success). But when the result returns to my site, the parameters in the url string don't have any values:

/modules/ewaysharedpage/ewayfaild.php?trxnnumber=&trxnstatus;=&trxnresponsemessage;=&response;=



And the transaction fails.

One point, when I hit the verification button on the eWay page, I get a security warning popup, but I'm thinking that's simply because the script is about to return to a non-SSL page.

Any thoughts?

Link to comment
Share on other sites

Maclean, I've been in contact with eWay NZ because I can't get a proper response code from the eWay Prestashop module on the www.eway.co.nz website.

Link to module page

Support has told me that the listed module is not compatable with v1.3.3 of Prestashop. Yet from your comments here it seems that it should be.

So, here's the problem. The module installs and configures fine. It accesses the eWay transaction page and verification page just fine. (I'm using the standard test account and test CC number. I use a transaction amount of 10.00 which should return success). But when the result returns to my site, the parameters in the url string don't have any values:

/modules/ewaysharedpage/ewayfaild.php?trxnnumber=&trxnstatus;=&trxnresponsemessage;=&response;=



And the transaction fails.

One point, when I hit the verification button on the eWay page, I get a security warning popup, but I'm thinking that's simply because the script is about to return to a non-SSL page.

Any thoughts?



Hi nuwanda,

I'm testing this for you now and will let you know what I find.

Kind Regards,

Maclean
Link to comment
Share on other sites

Hi nuwanda,

Quick and simple fix for this one. The Result URL is missing the trailing slash. Open ewaysharedpage.php and go to line 493

Please update it

FROM: $posturl="https://nz.ewaygateway.com/Result?".$querystring;

TO: $posturl="https://nz.ewaygateway.com/Result/?".$querystring;

Let me know if you have any other issues.

Maclean

Link to comment
Share on other sites

Thanks, Maclean.

Now, for clarification: I've tested response codes such as 05 and 08 which eWay indicates should return positive responses. The eway transaction page fails but when I'm returned to the site, I get a successful transaction and indeed the order record shows that the payment has been accepted.

This is a little disconcerting. I assume that eway has not in fact accepted the transaction, yet my client will process the order assuming payment has been made.

A note about the 05 and 08 codes. It's good that eway failed those codes (even though your site says they are approved responses, that is, they are ticked green) because they seem to be conditional approvals (partial for 05 and with identification for 08). So, is it the case that only 00 is considered a truly valid transaction?

If so, then why is the module, as explained above, telling my client that they have been approved.

Link to comment
Share on other sites

Hi nuwanda,

Only the following transaction codes are approved:

00, 08, 10, 11, 16

05 will result in a failed transaction with the text 'Do Not Honour'

Although there are five successful transaction response codes you will only ever see the first two (00 and 08) and please rest assured that you do not need to obtain a signature for a 08 response code, it's just an older code left over from EFTPOS days that some banks continue to use.

If you look in the ewaysharedpage.php file on lines 514-523 you will see the code that is looking for the successful response codes and updating the transaction.

Kind Regards,

Maclean

Link to comment
Share on other sites

Maclean, thanks.

But the problem is that an 05, while failing on the eway transaction page, is sending an approval to the site and it is being included in the orders record as "payment received".

Further, 08 is showing to the customer that the transaction has failed, but on returning to the site they are informed that it is approved.

Link to comment
Share on other sites

Hi nuwanda,

You should leave the accepted response codes as they were. At the moment, if a transaction is processed and receives the 08 approved code the transaction will be approved but your system will interpret the transaction as failed and ask the customer to pay again.

Line should be: if($responsecode=="00" || $responsecode=="08" || $responsecode=="10" || $responsecode=="11" || $responsecode=="16")

I have not been able to replicate your issue on my test server, can you please provide a link where I can test your site?

Maclean

Link to comment
Share on other sites

Ok, I've reinstalled the module but made your original edit for the trailing slash. No other code has been altered.

If you go to:

http://ps.oleo.co.nz/

When you create your account make New Zealand your country.

You'll see only one category, Oils. In that category is Basil Oil. Select view. There are two size options, 100ml and 200ml.

100ml is priced at 6.00 and 200ml is priced at 6.08 (both will add 4.00 shipping). The final prices will be 10.00 and 10.08 to simulate 00 and 08 codes.

00 will approve on eway and also approve when returned to the site. Correctly.

08 will fail on eway but then approve on the site. This is not as expected.

Thanks for your efforts.

Link to comment
Share on other sites

Hi nuwanda,

I've been able to replicate that for you.

I'm just double checking with our development team whether the 08 response code is indeed supposed to be a failed transaction or not however I have fixed the code so that it now reads the trxnstatus field instead. This is the way we recommend doing it, I'm not sure how the PrestaShop code got through with the current method.

To fix it open your ewaysharedpage.php file again and go to line 515.

Replace: if($responsecode=="00" || $responsecode=="08" || $responsecode=="10" || $responsecode=="11" || $responsecode=="16")

With: if($trxnstatus=="true")

Maclean

Link to comment
Share on other sites

Maclean

I've edited the code as you suggested.

The 08 transaction fails on eWay and on the site. This is correct.

But now the 00 transaction approves on eWay but fails on the site.

We now have a reversal of the original problem.

Fail capture attached. My site is available for testing with the edited code.

34843_T6NH4hyOVZybbQWjxQoV_t

Link to comment
Share on other sites

My apologies, Maclean.

I've just noticed that when I copied the new code from this forum, my IDE used non-standard double quotes in the pasted text.

00 now returns a successful transaction.

Thanks for all of your efforts. Best customer service I've had for quite some time.

I'll continue testing and let you know if I have further problems.

I assume the module has been updated on the eWay site?

Link to comment
Share on other sites

×
×
  • Create New...