On Wed, Aug 26, 2009 at 1:04 PM, Brandon Craig Rhodes<[email protected]> wrote: > > As Michael suggested last week, I have studied how all of the payment > processors besides Google Checkout integrate with GetPaid; Michael, it > was a great suggestion! And, thanks to guidance which Christopher > Johnson provided when we talked on Friday, I have also read through the > various branches in GetPaid labeled "multiplepaymentprocessors". > > (USABILITY PEOPLE: You can skip down to the "Big Questions That I > Need Feedback On" section farther down if you want > to skip the technical discussion.) > > As a result, I now have a more complete picture of how the various > GetPaid payment processors are designed. To keep things straight, I > sketched out this rough diagram in Inkscape this afternoon: > > http://rhodesmill.org/brandon/static/2009/getpaid-overrides.png > > Red text in the diagram indicates the presence of a ZCML override of > some sort. Note that I have left out extra steps that might be present > in the wizard, like shipping options; when present, such steps would sit > between the "Address Info" and the "Review & Pay" pages in the diagram. > > Payment Processors, and How They Work > ------------------------------------- > > Taking the diagram from top to bottom: > > * Google Checkout: > > The payment processor provides its own copies of the shopping cart > view and shopping cart portlet, so that it can draw a pretty "Google > Checkout" button on each of them. The buttons point at a view named > "/google-checkout" on the Plone site, which has no associated > template but instead redirects directly to Google itself. > > OPEN QUESTION: It is not clear to me why the checkout buttons do not > point at Google directly instead of going through the extra view, but > I see Google Analytics parameters being constructed on the way that > might have something to do with it.
The strongest reason is that the site itself needs to communicate with Google Checkout before redirecting the shopper to Google Checkout. It could be arranged that is communication is done when rendering the checkout button and the result somehow used in that rendering. But that would mean having to communicate with googlecheckout each time the checkout button was rendered for the shopper. > * ClickandBuy / PagSeguro: > > These both provide their own @@getpaid-checkout-wizard view that > removes all of the normal functionality, and shows a big button that, > when pushed, sends the user to an off-site checkout process. > > OPEN QUESTION: This approach competes directly with the Google > Checkout approach. Which is better: providing a special checkout > button for "Checkout"? Or, letting them visit our normal checkout > URL then asking them to click off-site? The former requires one less > click from the user; the latter gives them a bit more warning that > they are leaving. Should we rewrite all three payment processors to > use a common approach, and then provide an admin config option for > whether a store owner wants the extra "Click here to checkout" step > added or not? I think less clicking is for the shopper is good. And I think that these off site processors try to provide strongly branded checkout buttons which gives the shopper just enough warning. So you don't need the intermediate page. > * PayPal: > > This also provides its own @@getpaid-checkout-wizard, but the view > simply does an immediate redirect to PayPal. > > OPEN QUESTION: Like with Google Checkout, the question is, why? > Because it was easier than overriding the "Checkout" buttons? Or > because the extra step lets a few last variables and parameters be > put into place before the customer arrives at PayPal? I don't know. Might be the same reasoning as the Google Checkout. -- 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 -~----------~----~----~----~------~----~------~--~---
