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. >> Yeah - having some explicit support for a several different payment >> processor types of integration would be useful. Might be worth getting >> a good idea of what the different processors types all look like. For >> starters: >> >> (a) Synchronous. Where GetPaid collects all the user details and >> payment details and clears the payment details on the spot. >> >> (b) GetPaid collects the user details but does not collect the payment >> details. Instead the user is redirected to a different service to >> collect the payment details. I think the paypal and pxpay processors >> are examples of this. >> >> (c) GetPaid does not collect anything. Instead the user is redirected >> to a different service to collect user details and payment details. I >> think googlecheckout is an example processor like this. >> >> (d) GetPaid collects user details and provides payment instructions >> but but payment is not processed in real time. Instead an invoice is >> issued. I dunno if there are existing processors like this. > > Thanks for the explanation of the basic varieties! Oh yeah - another component for input on this is finding all the various overrides that are used by the various payment processors. A list of those has been started here: http://code.google.com/p/getpaid/issues/detail?id=167 Though since that list was started a few more payment processors have been added to the getpaid ecosystem. -- Michael Dunstan --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
