django-payments-mollie
Django Payments Mollie is a Django app that adds support for the Mollie payment provider to Django Payments.
Table of Contents
Installation
pip install django-payments-mollie
Configuration
You should follow the configration guide in the Django Payments documentation. To setup this package as a payment variant, use the following PAYMENT_VARIANTS in the Django settings file:
PAYMENT_VARIANTS = {
"mollie": (
"django_payments_mollie.provider.MollieProvider",
{
# For api key authentication
"api_key": "test_example-api-key",
# For access token authentication
"access_token": "access_example-token",
"testmode": True,
# For OAuth2 authentication
"client_id": "example-client-id",
"client_secret": "example-client-secret",
"testmode": True,
}
)
}
Available configuration options
api_key: A Mollie API key, this is the simplest way to configure access to the Mollie API. Use the test key for development or testing. This also allows you to use payment methods that aren't enabled for live payments yet.
Configuration helpers
Payment model
Django Payments docs will instruct you to create a Payment model that subclasses BasePayment. This package also provides a base model that you can use (optionally). The abstract model class BaseMolliePayment is a subclass of BasePayment, and it configures some of the fields as required=True, since Mollie requires them to be filled. Use it just like you would use Django payments' BasePayment:
from django_mollie_payments.models import BaseMolliePayment
class Payment(BaseMolliePayment):
...
# Add custom fields and methods
Sandbox
The project contains a sandbox that shows a very simple implementation of Django Payments with the Mollie payment variant. You can use it to see how implementation could be done, or to actually run an application against your own Mollie account. See the Sandbox README for details.
License
django-payments-mollie is distributed under the terms of the MIT license.
Metadata
Release files for django-payments-mollie 0.0.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| django_payments_mollie-0.0.1.tar.gz | 17.4 kB | Without provenance | Details for django_payments_mollie-0.0.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| django_payments_mollie-0.0.1-py3-none-any.whl | Python 3 | none | any | Details for django_payments_mollie-0.0.1-py3-none-any.whl |
Total release size: 25.8 kB
Release files / django_payments_mollie-0.0.1.tar.gz
| Download URL | django_payments_mollie-0.0.1.tar.gz |
|---|---|
| Size | 17.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
53cb5fd67029f3a570a8ef34a220419d8ca2313db5008b34ab23035287c7d371
|
|
BLAKE2b-256 checksum How to use checksums |
6aa0bb3bf8bd7569e40ef6b1cf1949b97995c52639fd45867bb6a173ee949eb4
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
python-requests/2.28.2
|
Release files / django_payments_mollie-0.0.1-py3-none-any.whl
| Download URL | django_payments_mollie-0.0.1-py3-none-any.whl |
|---|---|
| Size | 8.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
59b074bdd2b1245e6abbefe1ee37f0f8a4f594e7ff2c192a25e441eb6a03679a
|
|
BLAKE2b-256 checksum How to use checksums |
d8dcca5772108e8ee2f6e1d24cd60a91b0d13ad87760c665dea58ec95606a5e5
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
python-requests/2.28.2
|
Security for django-payments-mollie 0.0.1
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.