Problem:  A few developers new to the e-Commerce Framework run into a problem when developing a custom gateway:  their input fields on the front-end are not displaying and/or their configuration section on the back-end is not visible.  

Solution:  The solution to this issue is actually quite simple.  When creating a payment gateway on the back-end you are asked to enter a System Name.   This system name must match the folders on both the front-end and the back-end where your controls reside.  

This is because the e-Commerce Framework looks for folders on the front-end as well as the back-end that match this system name in order to render the controls on the page.    For the front-end the path is:  eCommerce Framework 4.0\PublicStore\Plugins\PaymentGateways\{your system name}

And for the back-end:                                                                                             \eCFCommerceManager\Plugins\PaymentGateways\{your system name}

The fact that the front-end has to match the system name specified on the back-end ensures that the public interface will match up with the back-end custom configuration.  

Try it:   You can see this demonstrated if you take a payment gateway and change the folder name on the front-end to be different from the system name specified in the commerce manager.   Be sure that caching is set to off in your public store web.config file to see the immediate effect.   

If you have went through the RPS tutorial guide as a new developer you will notice in the section about creating your custom gateway on pages 69-70, the instruction that the system name must always match your folder name.  Also you will get instruction on how to begin to build your own custom gateway.  You can get our RPS Tutorial guide along with many of our other kits and guides at:    http://www.mediachase.com/ecf/documentation.aspx