On Fri, Jul 24, 2009 at 3:00 AM, danimal<[email protected]> wrote: > > Hi Michael & Chris, > thanks for the continued input, it's great! > > I'm using encryptec.net as my client's webhost. > > I managed to complete my first test order for a Shippable item on the > Test Payment Processor. > I had to: > - continue past the error message at the Shipping methods stage > - enter a real credit card number (actually I've realised that I > could have calculated a Psuedo-real credit card number ... it only has > to pass the "luhn mod-10 checksum" in getpaid.core/getpaid/core/ > fields.py) > > So that's alright, I'm getting more confident about this working now. > But more qus: > 1) The site is selling DVDs - so I guess I need to make them Shippable > to get P&P calculation. But FlatRateShipping doesn't appear to work > out the box yet. Am I right? Is there a plan to fix this?
I'm not familiar with the state of the art of shipping and getpaid. > 2) Chris you said that something (GetPaid or GoogleCheckout, can you > confirm which?) meant I didn't need to take customers Credit card > details over the web, and therefore I guess I wouldn't need to get an > SSL certificate. > a) is that correct? > b) for these purposes does it matter whether I use Paypal or > Googlecheckout? Correct. There are several payment processors for getpaid that redirect the user to a third party site to complete the credit card component. So that you don't have to take customers card details over the web using your own server. The googlecheckout and paypall processors (among others such as pxpay) follow that model. Within getpaid these are called asynchronous processors. > My webhost would be open to requests to upgrade/add known Packages, > but not so open to me putting my own code/fixes up outside of that, so > using overrides.zcml might be out :-/ They have lots of plone > instances running on 1 or 2 zope services as I understand it. Ah... here is the problem... the core of getpaid does not really support asynchronous processors. All the asynchronous processors for getpaid rely on using overrides to patch getpaid. There is a chance that this may be resolved by the recent work to support multiple payment processors. See http://code.google.com/p/getpaid/issues/detail?id=167 Oh yeah - there is a small usability feature of googlecheckout that relies on your site having a valid SSL cert. (Not self signed.) That's not critical to using googlecheckout and does not affect the security of the customers credit card details. -- 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 -~----------~----~----~----~------~----~------~--~---
