eWay recurring payment processor

[ChrisChinchilla]

I can't make the code sprints but anyone at CiviCon want to help me improve my beta eWay recurring payment processor next week? We have it working for a client, but it needs improvement and I'm not really that good a developer…

I'll be in Town from Monday to Saturday, but am also attending NTEN

[frogburger]

Hi Chris, how did you progress with you eway payment gateway. Great to hear if you have something worked out. I also have a client who requires eway with recurring payments. Is it complete and if so can you share it? Or, please say if you need some help with the remainder.
Thanks,
Clinton

[henare]

I'm just starting to work on this too and I hope to have something running soon.

If you're able to share what you've done so far or have any suggestions about the approach that'd be a great help.

[scrubba]

Thanks Eileen for the heads up on this thread - and big *waves* to Henare and Chris C.

Wanted to add that my people have also been eager to get this set up.

And we were talking to another developer who was looking at helping us - so great to see chatter already 

I have just discussed this with Henare and where he is going.
Chris C -  it would be great to find out what you are up to code wise- possible to share where you are at?

The big issues in summary for us were how best set up the procedure based solidly from civicrm side,
then how best to alert eway the recurr payment needs to happen - most probably using the eway Token payments system

Then managing the result - transaction success - but also importantly -  fail so that info passes back to civicrm - and can be dealt with from there, by groups or reports etc..

What was everyone else thinking for direction?

Chris D (scrubba)





 

[ChrisChinchilla]

Sorry guys, I didn't get any notifications about replies :-(

We're having code sprint-ette on Monday night, if that's not convenient we'll be posting the code onto github as part of it, so people can jump in and help us finish things off at a later date to…

http://www.meetup.com/MelbourneCiviCRM/events/55767992/

Watch the link above and I'll post links to the code and tasks etc…

[henare]

Here's the code released on Monday - thanks @ChrisChinchilla!

github.com/ChrisChinchilla/CiviCRM-eWay-recurring-payment-processor (Sorry that's not a link, I'm not allowed to post them. Yay forums!)

I've taken a quick look and it takes a different approach to the one described by @scrubba. A recurring payment is created on the eWay side, then the email notifications that eWay provides are parsed to log a payment in CiviCRM each time it's automatically processed.

I was thinking that the way @scrubba described would be a nicer approach but I assume it's not possible in CiviCRM, is that about right @ChrisChinchilla?

[henare]

I've had a bit more of a look at this now.

I noticed that CiviCRM is trying to push payment processors into extensions and @ChrisChinchilla had already started to do that in his code. I've finished that work off in a branch:

https://github.com/henare/CiviCRM-eWay-recurring-payment-processor/tree/extension

It seems to do what it says on the tin but I'm still pretty wary about parsing receipt emails. Aren't these supposed to go to the customer: https://github.com/ChrisChinchilla/CiviCRM-eWay-recurring-payment-processor/blob/master/civicrm/CRM/Core/Payment/eWAYRecurring.php#L233

@ChrisChinchilla, can you think of anything that would stop us using the Token Payments API? (http://www.eway.com.au/developers/api/token.html) If we did that we'd need to hook into Civi's cron (which looks quite easy these days) to process payments.

[ChrisChinchilla]

This was created with a very specific purpose for a client and they didn't want the emails going to the customer and had a custom receipt instead.

Been a bit busy the past weeks and I need dedicated time n things like this really. Could we all arrange a time to lock heads and talk? Thursday would be good…

Then I can also talk through the process and justification…

[henare]

Been a bit busy the past weeks and I need dedicated time n things like this really. Could we all arrange a time to lock heads and talk? Thursday would be good…

Then I can also talk through the process and justification…

Perfect. I'll arrange with you off-forum to catch up.

Cheers, Henare

[SarahG (FountainTribe)]

I would like to test this new code for eWay,  How can I download it? Both links mentioned below produce a 404.

[henare]

I would like to test this new code for eWay,  How can I download it? Both links mentioned below produce a 404.

Hey Sarah - here's the link to my repository: https://github.com/henare/CiviCRM-eWay-recurring-payment-processor

Cheers,

Henare

[SarahG (FountainTribe)]

Thanks for the updated link. I have downloaded and installed the extension in my environment.  Two new questions:  1) What do I need to setup/configure in order to get the transaction confirmation messages from eWay back in CiviCRM?  2) Do you consider the code stable, ie production ready?

[henare]

1) What do I need to setup/configure in order to get the transaction confirmation messages from eWay back in CiviCRM?  2) Do you consider the code stable, ie production ready?

You need to set up some kind of mailbox. I've not set this up myself yet so it's not documented.

@ChrisChinchilla would be able to advise, given he wrote it If you work it out, please document it and send me a pull request.

2) Do you consider the code stable, ie production ready?

AFAIK it's being used in production but that said Chris and I have spoken about significantly changing the way it works, i.e. change it to use a different eWay API method which would remove the need to set up a mailbox, etc.

[ChrisChinchilla]

Hey Sarah, it's not quite ready for production yet, the code needs a little more work to make it work straight away on anyones set up and we also need to add in some attribution stuffs… So watch this space for when it really is ready… Or jump in and help out!

PS. We'll also get the official new location for GitHub up soon to.

[Martin Fuggle]

I am currently using PayPal Website Payments Standard which provides a facility to Auto Renew a membership. We are moving to eWay and have only just realised that whilst eWay provides the 'auto renew' capability it is not implemented in the CiviCRM eWay Payment processor. It seems that this post indicates it is in the process of being developed. Is it possible to get an update on the progress of this facility.

Cheers
Martin Fuggle