I've not written a payment Gateway from scratch yet but I have modified the Authorize.net one for my own requirements. I think the best place to get started is to look at the source for one of the existing providers:

https://github.com/Merchello/Merchello.Plugin.Payment.AuthorizeNet https://github.com/Merchello/Merchello/tree/merchello-dev/src/Merchello.Providers/Payment

I'm learning the code base by example and picking through existing providers to understand it all. If you get stuck post on here and someone should hopefully try and help you.

Cheers, Simon

Thank you Simon,

This was what i was looking for. Let me look into this and if i have any question i'll post it here :)

Cheers

Shinsuke

I have now used eWay on two systems, one I made my own functions and used the eWay SOAP interface.

The one I just tested to see if it compiles (got to test the payment page yet) I used the eWay nuget package. But as it uses AutoMapper there were difficulties getting it to play with Umbraco.

So I have recompiled a more modern version of Automapper and used different namespaces, I then recompiled the source of the eWay sdk (on github) to use the new namespaces.

It seems to be working fine at the moment.

Thanks Damien. Can you share the Github link. Sounds like it could be perfect if my project goes ahead

Seriously, shouldn't umbraco be doing their own namespaces for these libraries if they are going to have a long time between full version updates and expect people to be able to use more modern stuff with it?

I removed the newtonsoft.json whinge because you can simply update in your Umbraco solution and it seems to work.

So far the new compile seems to be working well, a bit more testing and I can make the dlls available.

Maybe a better Idea would be to fork the Umbraco build and rename the namespaces in that, but it is a much bigger task, maybe after I get married.

Ok, I have verified the libraries and eWay is now fully functional using the .net sdk on Umbraco!

This is just the .Net version of the eWay SDK.

All you need to do is use these dlls instead of the eway ones and update your Umbraco project to version 9 of newtonsoft.JSON.

I will do a fork of Umbraco in the near future where I will hopefully use this technique to make the automapper used by umbraco namespace safe. This way we can use whatever plugins and add-ons we want.

Here are the DLL's, I didn't use a proper github fork for either of these projects. find them zipped up here

Thanks Damien, thats great. I'll give them a try.

hmm, just discovered that the update has allowed the usage of version 331 of automapper, which is the min version for eway.

So the method now would be simply update to latest umbraco version then update automapper to 331 then install nuget eway package and you should be right, at least until they update it again.

Hi Shinsuke and David

I am New Zealand based and stumbled across eWay last year.

I am now looking to implement Merchello + eWay for my partners website and intend hooking into the transparent redirect process (not redirect off website).

Assuming I get something working, I'd be more than happy to provide the source, but initially wondered if either of you have made any progress in wiring up a Payment Provider for eWay.

Cheers

Nigel

Yeah eWay is now fully functional. MUCH easier than PayPal's ridiculous system.

Actually the nuget for eWay is better than most payment systems I have had to incorporate so far. Support from eWay, whilst being annoying at times is still better too.

I have never incorporated eWay into Merchello however as I never needed it, made my own shopfront as records are kept externally to website.

But you should be able to hit Merchello's code and alter the calls to paypal and alter it to the eway code.

UPDATE: eWay's new nuget package is further forward from Umbraco again, however you can get a beta version of the next package that allows a greater variablity in the Automapper versions.

Get it at: https://github.com/eWAYPayment/eway-rapid-net/issues/23?_pjax=%23js-repo-pjax-container

Using this package and matching my automapper area of web.config to the below settings worked perfectly.

<dependentAssembly>
    <assemblyIdentity name="AutoMapper" publicKeyToken="be96cd2c38ef1005" culture="neutral" />
    <bindingRedirect oldVersion="0.0.0.0-4.1.1.0" newVersion="3.3.1.0" />
</dependentAssembly>

Hi Damien

I know this thread is a bit old but the latest eWay SDK is up to: AutoMapper (>= 6.2.2) Newtonsoft.Json (>= 10.0.3)

So this just won't work to use to build and eWay payment provider for Merchello right?

is working on a reply...