CiviCRM Community Forums (archive)

Hey Dan - nice approach, and one that I was going to put up for discussion anyway. I think the issue for small players to contribute back is that to make the contribution seem meaningful pushes the development cost too high.
We also have a need to look at pulling data from NZ banks in order to be able to keep record of APs, when they cease, change etc. Would be interested to compare notes, and if what you are suggesting covers what we have on our list, then yes we could be in for a share.

Good move - what's your business name?

G'Day - I've just written a CiviCRM eWAY Payment Processor - a week ago I looked for eWAY / CiviCRM and the only ref I could find was a Nabble conversation between Donald Lobo & Brant Winter (date Nov 22/24) - I contacted Brant last Thursday - he'd had no luck - so I wrote the module.
TWO CAUTIONs:
(1) I have only implemented a single payment process - ie I did not need nor have time to do the 'recur' process section.
(2) eWAY is multi-currency challenged - it will not integrate with CiviCRM for multi-currency as it uses different accounts ('user_name')for each currency and CiviCRM enables one per allocated payment processor, expecting (very reasonably) that the 'currencyID' parameter will be fed to the payment processor's gateway. This is not the case with eWAY - it does not have a field for 'currencyID' in its XML request. So you can have a different currency for a range of allocated (ie different named) payment processors for different (say) events - but you can't (without some interesting coding) have multiple currencies for the same event.

The package is fairly complete - has simple installation notes showing where all the files go, so as well as the main eWAY.php, there are the Contribute and Event class extenders files, and the eWAY (package) support files, and simple text for an SQL INSERT that will add the eWAY entry into 'civicrm_payment_processor_type ' table, plus entries for the 'Processor.Hlp' file for the eWAY config form's pop-up help 'boxes'.

Code was based initially on the recent PayJunction, borrowed heavily from AuthoriseNet, took a bit of input from Drupal 5.7's 'ecommerce' eWAY module (stable and dev versions), and of course referenced the 3 eWAY standard developer's sample files.

Code is pretty good on differentiating eWAY errors and system errors and formats error messages appropriately.
Stole some good duplicate checking from AuthoriseNet, so if the user submits twice if catches the second one before it can send a duplicate to eWAY.

There are two versions of the 'eWAY.php' - standard code and 'eWAY_Debug.php' full of debug 'alert' statements if you need to display request and response packages, etc. Might be useful for someone adding the 'recur' section'.

Was coded for CiviCRM V1.9 - but shouldn't be too much of an issue to use it for V2.0 - probably be doing that myself shortly.

All in all it's on a par with the coding standards of the existing payment processor modules - been reasonably well tested (haven't had a whole lot of time), and except for the missing 'recur' function, and eWAY's inherent multi-currency limitations its complete.

I've blitzed this since last Thursday (13 March 08) - it took me a very hard 5 days +, with many long hours straight through last weekend - if there is a possible form of compensation - I'd be v interested to hear about it - equally if there's a desperate impoverished NGO then what the hell.

Regards

Peter Barwell
PB at DolphinSoftware dot com dot au

Donald (lobo)

Looks like we are upgrading to CiviCRM 2.0 today (as support for Events looks a lot better) - I'll update the eWAY code for 2.0 if it needs any changes (clues ?) and post again accordingly.

You want this for your Melbourne gig ?

BTW eWAY says they are interested in listing it on their PlugIns page - if you add it into standard CiviCRM - then they'll link to you guys as a user of eWAY (every link helps).

Cheers

PB

Donald,

OK - eWAY Payment Processor now operating in V2.0.1.

And to answer your question - Yes eWAY is one of the main processors in AU.

BTW - The single currency restriction may not be such a big deal for Aussie users of CiviCRM if the majority of the 'constituents' are Australian. Also it doesn't stop international users from paying - it only restricts them from paying in any currency other than the (eWAY account) designated currency (AUD by default).
So if for example you are being forced to pay in AUD for an Australian event - would you be that bent out of shape ? Happens all the time when you are actually (physically) travelling that you pay in the local currency with your credit card.

AND LASTLY - I wasn't suggesting that you add my stuff to core just yet - by having a package ready I meant that I've made a ZIP file with the modules, the help file update, the SQL syntax, and some reasonably clear install instructions. So I thought it might be useful for you to be able to indciate at your Melbourne gig that an eWAY solution (currently without recur) exists.

Cheers

pb

Woodsy,

Hi, I wrote to Dan90 directly to see what was happening - ie to see if there was some $$$ around but have had no reply.
I've been in contact with PeterD re possible use in NZ and Lobo re having it available for his Melbourne gig and that's about it.

I'm getting a lot of benefit from being able to use CiviCRM, so I'm happy to contribute - if you'd like to get hold of this package let me know - PB at DolphinSoftware dot com dot au

regards

PB

Lobo,

I am in Melbourne, I would have loved to come to the training, but I heard it was full? I play football on saturday's so I didn't think I could have come anyway.

I am still interested in the eway payment processor, and woud love to have it in the 'core', or try and squeeze my group for some cash for it.

I have been ever increasing my interest in development with Joomla/Civicrm and a few other components.

I haven't done any coding since university (java), but have picked it up as I go, just like riding a bike (Just need to start riding some more)

Anyways, I'll keep reading and coding.

Cheers Woodsy

Hey Vince,

Don't feel too bad about replying to an old thread.  If it wasn't for you I wouldn't have found it either.

I've found the eWay Payment Processor listed in the current CiviCRM ... so it's looking good.  Feeling even better about implementing CiviCRM than ever before!

Andrew