The basic usage is to connect you order model class with django-getpaid. Because the AbstractMixin is used, Payment model class uses a real ForeignKey to your order class model, so it avoids messy django content_type relations.
This app was written because there still is not a single reliable or simple to use payment processor. There are many payments related projects out there like Satchmo, python-payflowpro, django-authorizenet, mamona, django-paypal, django-payme, but none of them are satisfying. Mamona project was the most interesting payment app out there (because of general conception), but still has got some serious architectural pitfalls. Therefore django-getpaid in the basic stage was aimed to be a next version of mamona. django-getpaid took many architectural decisions different than mamona and therefore has been started as a separate project, while still borrowing a lot of great ideas from mamona, like e.g. using AbstractMixin, dynamic model and urls loading, etc. Thanks mamona!
Semantic Version guidelines will be followed in this project versioning.
Releases will be numbered with the following format:
And constructed with the following guidelines:
For more information on SemVer, please visit http://semver.org/.
You are welcome to contribute to this project via github fork & pull request.
If you create your standalone backend (even if you don’t want to incorporate it into this app) please write to me, you can still be mentioned as third party payment backend provider.