On Apr 6, 2009, at 4:10 PM, Michael Dunstan wrote: > On Mon, Apr 6, 2009 at 11:46 PM, Derek Richardson > <[email protected]> wrote: > >> Hmmmm. I was thinking a configlet that sees everything that is >> registered as a potential payment processor and allows choice. That >> seems even more end-user oriented to my naive judgment. Thoughts? > > Yup - allowing the user to pick their own payment processor would be > great. > > I don't currently have a good feel for what kind of changes that might > require to the core to support that. > > Minor technical note - I think the browser layer technique might still > be of value in that model too. In that case I guess you would interact > with the browser layer API at the request level. Different requests > would pick up different browser layers based on the users payment > processor selection. Obviously that only apply after the user has > actually selected a processor.
I think the GetPaid configlet already incorporates payment processor selection. It just doesn't work properly because of the use of view overrides in some processors. David --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "getpaid-dev" 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/getpaid-dev?hl=en -~----------~----~----~----~------~----~------~--~---
