How can I make duplicates of authorize.net module in magento?

Question

I've been stuck on this for a couple of days now. For some reason, duplicating the Magento Authorize.net (Mage_Paygate) module just doesn't work on the front-end. I've managed to duplicate the module and have it show up with its own configuration options in the back-end, but I can't get the payment method to show up on front-end during check out.

So far I've tried copying the module and changing every single instance of the model names to avoid conflict, I've done this multiple times from scratch so I'm confident that it's not an issue of an invalid class call...

There's some kind of magic button that I'm missing. I'm really hoping to hear from someone who's successfully duplicated a core payment module, specifically Authorize.net

I need to create duplicates for accounting purposes. There is no other solution than to duplicate the authorize.net modules.

Thanks

EDIT: Some insight into why I need multiple copies of the authorize.net module: My company processes high volume sales, more than most merchant services will allow. The idea is that we will have several authorize.net modules pre-loaded with multiple authorize.net API credentials that each correspond to a different merchant, so that when one of the merchants caps out we can disable that payment method and enable the next one.

The reason I can't just switch the information in a single authorize.net module is that we need the funds for each credit card to be deposited into separate bank accounts - ECC, the software we use to transfer data from magento to quickbooks, accepts the payment method based on the Title field. In order to differentiate which credit card processor we are transferring funds for, we append a (ACRONYM) to the title field. When this title field changes, ECC poops itself because it suddenly doesn't know where the funds came from for the transactions it's downloading.

We've tried various things and feel that making copies of an authorize.net module would be the best solution. Thanks.

start by describing your accounting issues/needs and you get the answer why you are doing it wrong. and read the FAQ of this site then you won't post off-topic questions here — Anton S
add more storefronts, switch the cart appropriately when the cap is reached — Anton S
The problem is that when I import the transactions into ECC, if the payment method doesn't currently exist in Magento, the transactions come through with a blank payment method. If I have 20 transactions with CC processor A, and 20 with CC processor B in the same day, 20 transactions are imported into quickbooks with blank payment methods. The switching store views is a great idea but gives me the same issue as just changing the API login info when the cap is hit. — dorkass

dorkass dorkass · Accepted Answer · 2013-01-06T08:07:55

I managed to figure it out, here's what I did in case anyone else runs into this, it's very handy to be able to duplicate payment and shipping modules that follow different rules without having to rely on store view changes:

Create new module Namespace_Modulename , I used Mage_Paygate1 until my concept was proven. Copy the etc folder from the module you'd like to duplicate Copy the main model file, in my case Mage/Paygate/Model/Authorizenet.php

Edit the system.xml: change group name so that a new block of configuration options will appear in the admin panel config, leave the module="" alone. We're going to refer to the original module files rather than copy them. I used authorizenet1.

Change the label node if you'd like, for clarity. In my case I named my copies Authorize.net (processor name)

Edit config.xml: Module name, change to Namespace_Modulename, I used Mage_Paygate1.

Make sure there is a blocks declaration if the original config.xml didn't have one. We want to refer to the blocks folder in the original module, ie:

<blocks>
<directpost><class>Mage_Paygate_Block</class></directpost>
</blocks>

change the node in the bottom under

<default><section> (<default><payment>) to the group name used in system.xml 
(authorizenet1)

Make sure the model node is correctly pointing to the new module, not the old. (paygate1/authorizenet)

Now edit the new model, (Authorizenet.php):

rename the Class to match the new Namespace_Modulename (Mage_Paygate1)

Make sure the $_code equals your group name from the config.xml file (authorize1)

That's what worked for me. The idea is to only copy the pieces that change the module's configuration and just recycle all of the original code.

There's probably an even cleaner way to do this but I'm no magento master by any means, so I very much welcome any advice on how to future-proof this sort of hack.

How can I make duplicates of authorize.net module in magento?

2 Answers