RealEX Payment Gateway

[niall08]

Hi - Bit of an AbleCommerce noob here - trying to create a new Payment Gateway, but i'm having no joy - even after re-naming and compiling the Authorize.NET sample. The dll isn't being picked up when I return to the admin GUI.

Has anyone done much work with the creation of new Payment Gateways?

Has anyone used RealEx before?

Thanks in advance,
Niall

[mazhar]

Please read the following topic
http://wiki.ablecommerce.com/index.php/ ... nt_Gateway

[niall08]

I've already had a look at the wiki documentation - the problem is that I have no idea where to start merging the RealEx example code with that of the Authorize.NET example.

Moreover, renaming and compiling the Authorize.NET example and dropping the dll into the "bin" folder doesn't generate a new Payment Gateway in the admin GUI. Even getting this step to produce some results would be an encouraging step forward.

Would it be useful if I attached the RealEX documentation?

[niall08]

OK - in the hope of getting some movement on this issue..

First things first - I'm simply trying to get a new payment gateway to be recognised. As such, I've edited the Authorize.NET example provided elsewhere in these forums (I've simply changed the assembly name etc.), and placed the dll (CommerceBuilder.RealEx.dll) in the bin folder for the AbleCommerce installation..

However, the Merchant Admin doesn't pick up the new Gateway - am I doing something that is fundamentally wrong?

The code for RealExProvider.cs is attached.

Any ideas?

[niall08]

Right - for anyone else with the same problems..

I created a new solution, copied the code across and recompiled - then FTP'd the dll across to the solution's /bin folder.

Instead of popping the application pool, I restarted the website and.. hey presto, the new gateway appears in the Payment Gateway list.

Now all that remains is editing the Authorize.NET functionality to match RealEx.

[mazhar]

I have created the solution and deployed the dll to the bin folder. It worked for me. You can download the sample solution I have created. Please read the RealEx integration help about the implementation guide lines.

[niall08]

Thanks Mazhar - I recently got that working - but I do appreciate your effort there

The current problem is that RealEx expects an XML message containing the details of the transaction, not a parameterised querystring (looking at the log, this is what the Authorize.NET example uses, isn't it?).

Offhand, do you know if converting the Authorize.NET example to use this xml structure is difficult/possible? Or should I forgo the integration element and build a wholly customised Payment Gateway that doesn't extend the CommerceBuilder.Payments.Providers.PaymentProviderBase class, but rather uses the RealAuth dll?

[niall08]

Hi,
I've some questions regarding the editing of the Authorize.NET payment gateway:

I take it "DoAuthorize" is the method used when "Authorize" is selected in the payment gateway options?
Does the "DoAuthorize" method use a parameterised querystring when connecting to the gateway?
In the demo, are these extended methods ignored (I've tried to edit the querystring, but the logs show no change)?
Is there any technical barrier to using the "SendXmlRequestToGateway" instead of "SendRequestToGateway" for DoAuthorize" (as RealEx expects an XML message, not a parameterised querystring)?

[mazhar]

No I don't think so. You can provide some method in the gateway that would send the XML messages.

[mazhar]

I think you should also take a look at the RealAuth samples for RealEx remote payments, I think those will be very helpful for you.

[mazhar]

You have to use the CommerceBuilder. You can use a mixed approach. When communicating with RealEX payments then you can take the information from CommerceBuider and pass it to RealEX using their API code and when you got response from RealEX payments then you can convert and make the information Commercebuilder compatible.