My company use Barclay's for our banking facilities and therefore our software has to integrate with the Barclays EPDQ interface for online transactions. We will shortly be building a Distillery tour booking system and i would like to use the Events module but it will require us to integrate an EPDQ payment provider into the module rather than use paypal. Is there a standard approach to creating a payment provider so that it can be 'plugged' into the events module without making code changes to the source code coming out from the events team. I wish to ensure we can continue to install future releases of the events module without either our code or the events code breaking.

Best Regards
Bryn

Hello Ernst Peter,

Thanks for the prompt reply.

The events team have done an amazing job to get the module to its current level. With limited manpower, time and acting on a voluntary basis there have to be clear, reachable targets, otherwise the development could easily swamp all members, so i fully understand why there is no current payment plugin option. Your reply has helped me clarify the position and therefore i can now formulate a way forward. In the new year i will study the events code and try to come up with a technique that will cause minimal disruption as and when event module upgrades appear.
I agree a central payment plugin would be useful especially in my case where the Barclays EDPQ stores are allowed to be linked to only 1 web address. Therefore If you have two dotnetnuke modules that take payments on two different pages its means paying Barclays for two stores currently at £25.00 a month plus a % percentage of your sales. The costs increase with each module, whereas if all modules could use a central payment 'router' there would only be only one web address and hence once EPDQ store required.

Good luck with work on the events module ans thanks for everyones efforts to date..

Best Regards
Bryn