I am developing a new payment module. I have several points I am a little unsure about; if anybody is able to help, I would appreciate it.
1 - Is it possible to create a customized back-end configuration page for my payment module that can be found in the ‘Payment Methods’ menu?
2 - The interface I am developing for requires credit card information to be entered on-site. I see that I can create '‘fields’ through the back-end but I would much rather have a template loaded upon module selection. Is there any way to do this? The payment.tpl conditional beginning on line 80 seems to assign ‘payment_other.tpl’ to any custom payment methods. Is there any way to circumvent this conditional? (Without overriding any core file, if possible). I assume that editing payment_other.tpl is not the ideal solution.
I did see them but they didn’t seem to answer my questions - unless I missed something?
The Authorize.net tutorial itself seems to suggest that there is no proper admin configuration area, since the configuration values required by Authorize.net are there found in class properties that are then used by the executePayment() method. Am I correct in thinking that is the only way payment modules can be passed such values and that we cannot add a HTML form in the administration area to have these values set?
Of course you can add an own page in backend to give some information to the user and ask for some values like perhaps account-id, password for the payment-provider login and so on. I have some modules integrated in my shop, which have added own menu-links and own pages in backend.
Maybe this tutorial can help you out? I´m not a coder, so I can just guess…
