Building a BluePay payment module

[mbrando]

Hi,

Does anyone know how to go about building a payment module? I need one for BluePay v2.0 merchant account. I have processor API examples but the forum attach will not attach them, all of 20kb.

Any help or direction would be great.

Thanks,
Mike

[Kelly]

did you ever get this accomplished?  If so, please let me know how.  I am working on the same thing right now. 

[mbrando]

Hi,

No one ever responded. It was never built. I've been looking at modifying an authorize.net module but have not hound the time to do it.

Mike

[Nick Sumner]

Hi Kelly

I have several payment modules on my site at http://www.e-commerce-solution.co.uk/ -
We haven't got a BluePay one yet, but we can develop a custom API payment module for you if you wish, for around £200

Nick

[mbrando]

Hi Nick,

Would this be a one time fee to develop and I would be able to use for any web site I'm developing or would you create the module and charge around 80 pound per web site to license?

I do not have project need today, but would like to call you for my next e-commerce project.

Mike

[ecom integration]

Hi Mike

Whoever we develop the modules for get the module licensed for there own sites/clients sites they can reuse the module, we then resell 1 domain licensed versions .

[newbyr]

I have a Virtuemart bluepay payment module.
I have the rights to the module and will sell to you for $39.95.
Send me a PM with your information

[uche40]

I need the  Virtuemart bluepay payment module for $39.95 , Please contact me i would like to purchase it. uche40@mypancho.com

[inkewbus]

OK You can modify your existing authorize.net script to easily work with your BluePay merchant account by following the instructions below. Since BluePay now has an authorize.net emulator, you can use the current authorize.net module for BluePay. I've successfully implemented this change in my site which is currently using BluePay. I've been able to test this in the test mode and it did show up correctly in the BluePay transactions. I figured everyone could use some nice free information for how to convert over an existing module to their merchant account. If you have any questions regarding this, please send me an email to pekulior@gmail.com




In /administrator/components/com_virtuemart/classes/payment/ps_authorize.php

Change line 381 from

Code Select Expand

$host = 'secure.authorize.net';
TO

Code Select Expand

$host = 'secure.bluepay.com';



Change line 383 from

Code Select Expand

$result = vmConnector::handleCommunication( "https://$host:443/gateway/transact.dll", $poststring );
TO

Code Select Expand

$result = vmConnector::handleCommunication( "https://$host:443/interfaces/a.net", $poststring );


Also change line 588 from

Code Select Expand

$host = 'secure.authorize.net';
TO

Code Select Expand

$host = 'secure.bluepay.com';


And line 590 from

Code Select Expand

$result = vmConnector::handleCommunication( "https://$host:443/gateway/transact.dll", $poststring );
TO

Code Select Expand

$result = vmConnector::handleCommunication( "https://$host:443/interfaces/a.net", $poststring );



Save the settings then you're done editing files. Below are the rest of the instructions if needed.

It is important to note that it only handles A.net AIM mode. IT DOES NOT HANDLE A.NET SIM MODE.

Authorize.NET expects a parameter called "x_Login" - sometimes this will be in the shopping cart as "Login" or "user name." Whatever it is labeled, this must be set to the 12-digit Bluepay ACCOUNT ID.

Authorize.NET expects a parameter called "x_trans_key" or "x_password" - this will usually be listed as "Transaction Key" or "Password" in the shopping cart. This must be set to the 32-character Bluepay SECRET KEY. The real Authorize.NET only requires 16 character transaction keys, so if the shopping cart will only allow 16 characters, you are allowed to use just the FIRST 16 letters of the SECRET KEY.

[theengel]

Thanks a bunch for that Inkewbus!

[theengel]

Just popping back in to say I followed the directions above and this worked perfectly.  I don't know the difference between a.net AIM and a.net SIM, so I have no idea if there was something people would have to change there.  But I followed everything else and it worked.  Thanx so much Inkewbus for pointing this out.