GetPaid for Plone

GetPaid is a flexible framework for payment processing and commerce in Plone. It is made using the Zope 3 technologies and is meant to be extensible and flexible for your needs - yet useful out of the box for basic use cases. GetPaid also has many available add-on packages for additional functionality and for payment processing around the world.

Project Description

PloneGetPaid is designed to make it easy to accept payments on your site. The framework provides a simple way to get started with that, and a rich structure for extending usage for specific needs.

GetPaid has been used in production since December 2007. Since then several improvements have occurred to keep the product improving and evolving. You can find a list of 15+ Sites Using GetPaid, for examples of how it is used.. Read on for more on installing.For more about the project, including features, updates, and ways to contribute, please see our public web site, www.plonegetpaid.com 

How to GetPaid

 You can get the GetPaid product in two ways:

• Adding GetPaid to Existing Site - There is a buildout recipe that can be used to install GetPaid in your existing buildout: getpaid.recipe.release.  More information on how to use this recipe can be found at the Python Package Index. 
  
• Testing/Developing: There is also a development buildout for GetPaid.  This makes it easy for developers to get set up with everything needed for the product with just a few commands. See DevGettingStarted .  

Documentation

• You can find manuals, tutorials and howto's on this site by following this link to documentation. 
• For more on how the internals of GetPaid work, please see the notes on the getpaid.core listing on pypi. 
• For documentation on integrating payment processors with GetPaid is available in the product.
  

How to Get Involved

We welcome participation in the project! You can:

• Join our development mailing list to contact others, discuss features, and learn more
• Make a financial contribution or become a sponsor of the project (especially if you have a feature you want in the system!) Contact us to express your interest.
  
• Tackle issues (for developers and non-developers!), make an extension or additional functionality,  

Credits

Project leaders: Kapil Thangavelu provided the role of chief architect of the base product. Christopher Johnson organized the project, collaborative process, and funding. Jon Stahl served as the project's NGO Liason for the first release. Lucie Lejard played the role of release manager through 0.7.x. Brandon Rhodes provided review and refactoring of the payment processor interfaces.

Special thanks to our sponsors that helped us "social source" this project!

ObjectRealms     ifPeople     Groundwire (formerly ONE/Northwest)     Contextual Corporation     Trees for Life     Totsie.com

>>Read more about our sponsors 

Self-Certification

[X] Internationalized

[X] Unit tests

[X] End-user documentation

[ ] Internal documentation (documentation, interfaces, etc.)

[X] Existed and maintained for at least 6 months

[X] Installs and uninstalls cleanly

[ ] Code structure follows best practice

Independent Review