ABOUT
django_payone implements the server and client API of Payone. It provides a thin layer to use the Payone payment gateway.
Server API
TODO
Client API
Implementation of the client API using jQuery. Payone uses JSONP to handle AJAX requests. Includes:
client.js to wrap up all required parameters
client.py for calculating the required secure hash
1 maintainer
Metadata
1 maintainer
Release files for django_payone 0.1.0-3
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 | |
|---|---|---|---|---|
| django_payone-0.1.0-3.tar.gz | 3.9 kB | Without provenance | Details |
Release files / django_payone-0.1.0-3.tar.gz
| Download URL | django_payone-0.1.0-3.tar.gz |
|---|---|
| Size | 3.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
d1a5e7c8ad0aa1acb5fbb60360b19951b1a84a66d142e6d1247e18c239aa2f44
|
|
BLAKE2b-256 checksum How to use checksums |
ef294883f95d446dd389d6021a16035bb3395456bf5278a23bca1234f9b429ab
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for django_payone 0.1.0-3
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.
