Michael - good point on the currency situation! Thanks for bringing that into the scenarios also.
-c On Mon, Aug 31, 2009 at 5:16 AM, Michael Dunstan <[email protected]>wrote: > > On Sun, Aug 30, 2009 at 4:21 AM, Brandon Craig > Rhodes<[email protected]> wrote: > > > > We have established that a store owner might want to allow the user to > > choose between different off-site checkout processes, because the user > > might have an account already on one but not on another. One user might > > have a Google Checkout account already; another, a PayPal account. And, > > so, a certain shop owner might want the user confronted during the > > checkout process with a screen (which the "multiplepaymentprocessor" > > guys already have an early working version of!) like: > > > > How would you like to check out? > > > > * Use Google Checkout > > * Use PayPal > > * Enter my credit card information right here on-site > > > > So, we need to support user choice between different off-site payment > > processors, and also let them choose to remain on-site if that is an > > option the store owner wants to offer. > > > > But what about the various on-site mechanisms? Take, for example, > > AuthorizeDotNet and PayFlowPro: both of them let Plone accept the credit > > card information, and then, hidden back behind Plone where the user > > never even knows they're there, they authorize and charge the payment on > > behalf of the site. > > > > Because they're hidden, and the user cannot interact with them directly > > - they never get to talk to the user's browser or anything - it's not > > clear to me that it would ever be useful to let the user choose among > > these credit card processors. That is, I'm not sure there's a use case > > for the user being presented with the following dialog: > > > > How would you like your credit card charged? > > > > * Use AuthorizeDotNet to check my credit card number > > * Use PaymentTech to check my credit card number > > > > So, what do *you* guys think? > > There *may* be a case for dynamically selecting from several different > on-site payment processors. Where the code picks one that matches the > currency of the shopper. If buying in USD then use ProcessorA or if > buying in GBP then use ProcessorB. (Though that'd be a bit more > elaborate than usual I suspect.) > > -- > Michael Dunstan > > > > -- Cofounder and CEO ifPeople - Innovation for People www.ifpeople.net t: 678-608-3408 130 Boulevard NE, #6 Atlanta, GA 30312 --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
