This release is a pre-release and may not be stable for production use.
pcommerce.payment.ogone
pcommerce.payment.ogone is a plone plugin, which provides payment over ogone for PCommerce
By: Huub Bouma (http://www.goldmund-wyldebeast-wunderliebe.com)
The Ogone specific hashing, status, and exception code was taken from the django-ogone project (Thierry Schellenbach). django-ogone is licenced under the GPLV3 licence, which is included
This package was mainly designed after the pcommerce.payment.saferpay plugin, and works almost identically, except ofcourse this uses a different payment platform.
Installation instructions
Step 1 - installing
Install via the plone quickinstaller
Step 2 - configure plone
Look at the ogone settings in the site configuration
You should set the ogone specific settings and these should obviously match the settings as you have configured them with Ogone.
Ogone Server URL
pspid
SHA In Passphrase
SHA Out Passphrase
step 3 - Ogone settings
In Ogone there are a couple of settings which you should set:
- Hash algorithm:
SHA-512
- SHA-IN Pass phrase:
your secret password for hashing the request
- SHA-OUT Pass phrase:
your secret password for hashing the response
- I want to receive transaction feedback parameters on the redirection URLs:
checked
On the subsection Direct HTTP server-to-server request you can set the Timing of the request to: Always deferred (not immediately after the payment). This will make sure that if something goes wrong and the customer has already payed, it will still be processed by plone because Ogone will send the request (again)
Make sure that you fill in the complete URL of the processOgone URL, which will be the URL of your homepage, followed by ‘/processOgone’, e.g.:
http://my.website.com/processOgone
Ogone should be able to access this URL in order for it to work.
LICENCE
This code is open source. It’s licenced under the GPLV3 licence. See LICENCE.txt
Changelog
0.1a2 (unreleased)
0.1a1 (2011-11-21)
First release on GW20e’s private egg repository
Metadata
Release files for pcommerce.payment.ogone 1.0a2
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 |
|---|---|---|---|---|
| pcommerce.payment.ogone-1.0a2.zip | 43.6 kB | Without provenance | Details for pcommerce.payment.ogone-1.0a2.zip |
Release files / pcommerce.payment.ogone-1.0a2.zip
| Download URL | pcommerce.payment.ogone-1.0a2.zip |
|---|---|
| Size | 43.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
ab56267967f1ef58714eacf527d757b02052334f4b02a236a1794520c679e35b
|
|
BLAKE2b-256 checksum How to use checksums |
6ba811b2fb411ad3652d6b83aa6eb5af4edc7bc7e09cee5a9930bb4fcf28e092
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for pcommerce.payment.ogone 1.0a2
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.