{
"info": {
"author": "Getpaid Community",
"author_email": "getpaid-dev@googlegroups.com",
"bugtrack_url": null,
"classifiers": [
"Programming Language :: Python",
"Topic :: Software Development :: Libraries :: Python Modules"
],
"description": "Purpose\n-------\n\nThis package provides generic payment processor registration methods. Though the code itself is free from Plone dependencies,\nthis documentation covers Plone too.\n\nPreface\n-------\n\nGetPaid provides support for two different kind of payment processors:\n\n- *Synchronous*: Your web server does the payment authorization by doing a remote procedure call to the payment processor server\n You need to override payment processor checkout-review-pay wizard step to have your own custom form fields\n needed for the payment submission. The default Products.PloneGetPaid.browser.checkout.CheckoutReviewAndPay\n provides fields for simple credit card payment.\n\n- *Asynchronous*: The buyer will leave your site for the payment to the payment web server (PayPal) and come back to your site after\n the payment is completed\n\nInstallation\n------------\n\nInstall GetPaid from trunk. \n\nUse branch following development branches. Note that PayPal changes are in trunk::\n\n\tcd src\n\trm -rf Products.PloneGetPaid\n\trm -rf getpaid.nullpayment\n\trm -rf getpaid.paypal\n\tsvn co https://getpaid.googlecode.com/svn/Products.PloneGetPaid/branches/multiplepaymentprocessors Products.PloneGetPaid\n\tsvn co https://getpaid.googlecode.com/svn/getpaid.nullpayment/branches/multiplepaymentprocessors getpaid.nullpayment\n\tsvn co https://getpaid.googlecode.com/svn/getpaid.paypal/trunk getpaid.paypal\n\t\nAdd *getpaid.paymentprocessers* to your *316.cfg* eggs and develop-eggs sections.\n\nAdministration\n--------------\n\nActive payment processors must be enabled in *Site setup* -> *GetPaid* -> *Payment processor settings*.\n\nYou can manage individual payment processor settings from the same screen.\n\nCheckout wizard steps\n---------------------\n\nA checkout wizard contains a step \"checkout-payment-method\" which allows the user to select \nthe wanted payment method. This step is only available if the site has more than \none active payment processors.\n\nCreating your own payment processor\n-----------------------------------\n\nPayment processor directive\n===========================\n\nPayment processors are registered using a ZCML directive::\n\n \n\n \t\n\n \n\n \n\n\nIt is recommended best practice to put paymentprocessor directive into a separate ZCML file in your getpaid extension module\nto maintain backwards compatibility. You can do it using zcml condition::\n\n \n \nYou can also maintain backward compatiblity overrides with not-installed directive::\n\n \n\n\npaymentprocessors:registerProcessor attributes\n++++++++++++++++++++++++++++++++++++++++++++++\n\nBelow is explanation for **registerProcessor** attributes.\n\n**name**: This must match getpaid.core.interfaces.IPaymentProcessor adapter name\n\n**i18_name**: This is the user visible name of the payment processor. It might appear in the summaries and listing.\n Term \"payment method\" is recommended here for more end user friendly language.\n\n**selection_view**: This is a registration name which renders the payment method selection button on payment\nmethod selection checkout wizard step. The browser view class should be subclasses from Products.GetPaid.browser.checkout.BasePaymentMethodButton.\n\nselection_view template should render a
element which is rendered on the checkout payment method selection page. It contains three columns:\n\n\t-