I'd like to build a generic payment interface in cake with the ability to easily plug-in several different gateway implementations.
The stubs would be things like: Authorize.Net, LinkPoint, Verisign, paypal, GoogleCO, 2CO, etc. I'm not sure which of several architectural approaches to choose within cake. Possibilities: 1. single generic Payment model, different behavior per gateway. 2. single generic Payment model, different datasource per gateway. 3. different model per gateway 4. different component per gateway 5. other ... Any tips ? Check out the new CakePHP Questions site http://cakeqs.org and help others with their CakePHP related questions. You received this message because you are subscribed to the Google Groups "CakePHP" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/cake-php?hl=en
