|
Rob Norman
|
December 9, 2013 at 10:06 pm
Hi,
I am using Event Espresso, Version 3.1.35.2.P on svc.org.au, hosted by Netregistry (Australia). I am trying to setup a payment gateway with eWay. Under “Payment Settings” there are two options for eWay –
1) “Eway Settings” which uses the eWay account ID and username (email address)
2) “Eway Rapid 3.0 Settings” which uses an API key, eWay Rapid API Username, eWay Rapid API Password
Using option 1) I can get payments working if card information is entered correctly; however, if I enter a wrong card number or incorrect CVN the following results occur:
The top of the return page –
Debugging / Sandbox output
Response code = CX Response = string(899) “HTTP/1.0 200 Connection established HTTP/1.1 200 OK Cache-Control: private Content-Type: text/html; charset=utf-8 Server: Microsoft-IIS/7.5 X-AspNet-Version: 4.0.30319 X-Powered-By: ASP.NET Content-Length: 465 Date: Tue, 10 Dec 2013 04:41:42 GMT Connection: keep-alive Set-Cookie: ASP.NET_SessionId=vxry5bfnvilxuyrgazzwvdpa; path=/; HttpOnly Set-Cookie: BIGipServerVirtServerPool-015-SSL=1929579274.47873.0000; path=/ CX10.00FalseCustomer Cancelled Transaction”
End of Debugging / Sandbox output (this will go away when you switch to live transactions)
Even though I have not turned on “Debugging” …?
Using option 2) simply returns –
An error has occured in the using of the Eway Rapid 3.0 payment gateway. Please try a different gateway
This is strange as I can authenticate my live api credentials when using https://api.ewaypayments.com/soap.asmx. Also I have tried applying the fix from here – https://eventespresso.com/topic/cant-get-eway-rapid-3-0-to-work/ without success.
Sorry for the long post but I wanted to provide as much info as possible.
Cheers,
Rob
|
|
Sidney Harrell
|
December 10, 2013 at 11:56 am
It does look like there is a logic bug in the original eway processing script. Try repairing it with this:
For the rapid 3.0 problem, try changing line 75 of gateways/eway_rapid3/eway_rapid3_vars.php to:
<p class='error'><?php _e("An error has occured in the using of the Eway Rapid 3.0 payment gateway. Please try a different gateway","event_espresso");var_dump($rapid3Response);?></p>
that should give you a better indication of what the root problem is.
|
|
Rob Norman
|
December 11, 2013 at 2:04 am
OK, using my numbering above –
1) Original eWay Gateway – I have applied the fix as suggested above. Output is now –
There was a problem processing your transaction
eWay reports that: Customer Cancelled Transaction
Payment Overview
Class/Event: Testing Event
Primary Registrant: Joe Bloggs
Payment Type: eWay
Payment Date: December 11, 2013
Amount Paid/Owed: A$10.00 Incomplete
Payment Status: Incomplete
Registration ID: 3-52a826356b8d4
Please choose a payment option
click to visit this payment gateway
Fatal error: Cannot redeclare fetch_data() (previously declared in /clientdata/zeus-dynamic-1/s/v/svc.org.au/www/wp-content/plugins/event-espresso/gateways/eway/ewaypaymentprocess.php:49) in /clientdata/zeus-dynamic-1/s/v/svc.org.au/www/wp-content/plugins/event-espresso/gateways/eway/Eway.php on line 62
Also, this output is not returning to the “Transaction” page (it didn’t originally either). The return URL in the browser is –
http://svc.org.au/?page_id=462&id=20&r_id=3-52a826356b8d4&event_id=3&attendee_action=post_payment&form_action=payment&type=eway
2) eWay Rapid 3.0 – After your modification, output is –
Payment Transactions by Eway Rapid 3.0 Payments Pro
An error has occured in the using of the Eway Rapid 3.0 payment gateway. Please try a different gatewayobject(stdClass)#39 (5) { [“AccessCode”]=> NULL [“Customer”]=> object(stdClass)#42 (27) { [“CardNumber”]=> NULL [“CardStartMonth”]=> NULL [“CardStartYear”]=> NULL [“CardIssueNumber”]=> NULL [“CardName”]=> NULL [“CardExpiryMonth”]=> NULL [“CardExpiryYear”]=> NULL [“IsActive”]=> bool(false) [“TokenCustomerID”]=> NULL [“Reference”]=> NULL [“Title”]=> NULL [“FirstName”]=> NULL [“LastName”]=> NULL [“CompanyName”]=> NULL [“JobDescription”]=> NULL [“Street1”]=> NULL [“Street2”]=> NULL [“City”]=> NULL [“State”]=> NULL [“PostalCode”]=> NULL [“Country”]=> NULL [“Email”]=> NULL [“Phone”]=> NULL [“Mobile”]=> NULL [“Comments”]=> NULL [“Fax”]=> NULL [“Url”]=> NULL } [“Payment”]=> object(stdClass)#38 (5) { [“TotalAmount”]=> int(1000) [“InvoiceNumber”]=> NULL [“InvoiceDescription”]=> string(13) “Testing Event” [“InvoiceReference”]=> NULL [“CurrencyCode”]=> string(3) “AUD” } [“FormActionURL”]=> NULL [“Errors”]=> string(5) “V6059” }
Choose a different payment option
The eWay Rapid 3.0 option apparently doesn’t connect to eWay at all? Which of these two eWay connect methods do you recommend ultimately? My simple thinking says “the one that work” which is neither at this stage but at least the original eWay gateway kind of works.
Thanks again,
Rob
|
|
Rob Norman
|
December 12, 2013 at 8:46 pm
Hi Guys,
Any solution for this? My preference if to get the eWay Rapid 3.0 solution working because it seems more elegant and I guess it means we’re not leaving our website and coming back with error messages that wreck our theme. This is quite an urgent problem as I have some paying events coming up shorty.
Cheers,
Rob
|
|
Sidney Harrell
|
December 13, 2013 at 11:38 am
For the rapid 3.0 issue, that error code indicates invalid redirectUrl. Try changing that var_dump to:
var_dump($redirectUrl);
For the eway classic problem, in that same file (ewaypaymentprocess.php) wrap that function in a function exists wrapper (for a quick fix)
if (!function_exists('fetch_data')) {
function fetch_data($string, $start_tag, $end_tag) {
$position = stripos($string, $start_tag);
$str = substr($string, $position);
$str_second = substr($str, strlen($start_tag));
$second_positon = stripos($str_second, $end_tag);
$str_third = substr($str_second, 0, $second_positon);
$fetch_data = trim($str_third);
return $fetch_data;
}
}
was lines 49-58 in my copy.
|
|
Rob Norman
|
December 15, 2013 at 9:33 pm
Thanks,
Upgraded to EE 3.1.36.1.P; now eway rapid 3.0 working well. Thanks for you fix to eway classic.
|
