Hello, GetPaid folks. Several of us in Seattle are planning to hold a mini-sprint at the end of this week to work on adding support for recurring payments to GetPaid. I wanted to say a bit about our goals and planned tasks, in case anyone has feedback or concerns you'd like to raise before we dive in.
My main overall goal is to make it possible to set up recurring payments via the GetPaid infrastructure, using either Paypal or Authorize.net as the payment processor. So it should be possible to either mark a piece of content as a recurring payment with some price, frequency, and number of occurences; or to programmatically add a recurring line item to a cart. And then check out and have that get set up with the payment processor. Additional "nice-to-haves" if we have time: - Make a "Donation Form" product that makes it really easy to create a basic PloneFormGen-based donation form that allows specifying either a one-time or a recurring donation. (I have a prototype of this without the recurrence piece.) - Make sure that we can be notified and record when subsequent payments actually occur. As a starting point, we will be using several branches of GetPaid that were done by Juan Gímenez for ifPeople in mid-2008. This branch is a bit buggy, but provides a solid start with the following: - Adds support for Authorize.net's Automated Recurring Billing (ARB) API to the authorize.net payment processor. - Adds the ability to mark content items as something that can be purchased via recurring payment (or programmatically add recurring items to the cart). Recurrence is specified with a frequency and total # of occurences. - Exposes recurrence in a few places in the UI (e.g. in cart listing, records of old orders) Here are some of the additional tasks that we hope to take on during the sprint: - Refactor the ARB support in the zc.authorizedotnet branch into a separate package (I checked with Zvezdan from Zope Corp. who is one of the maintainers of zc.authorizedotnet, and this is his preference). - Fix a number of minor issues in the ifPeople branches: - fix spelling of 'frecuency' - display the recurrence of items in the cart in a nicer fashion - fix broken Payable tab; update portlet to work in Plone 3+ - modify ARB processor to verify via the standard AIM processor first (otherwise bad CC info is not rejected immediately; subscription payment processing doesn't happen until ~2 a.m.) - do better checking to ensure that recurring items can't end up in a cart with non-recurring items - don't allow marking items as recurring if the selected processor doesn't support it - make sure subscription id is recorded on the order - document the changes - Merge the branches to trunk and make new releases - Add recurring payment support to the Paypal processor - Add authorize.net "Silent Post" listener to update order info when transactions are actually processed - Create a custom widget that can be used in PloneFormGen and getpaid.formgen, which lets you select either a one-time or recurring payment. peace, David -- GetPaid for Plone: http://www.plonegetpaid.com (overview info) | http://code.google.com/p/getpaid (code and issue tracker) You received this message because you are subscribed to the Google Groups "getpaid-dev" group. To post to this group, send email to getpaid-dev@googlegroups.com To unsubscribe from this group, send email to getpaid-dev+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/getpaid-dev?hl=en?hl=en
