1 file was added to this release more than 14 days after its initial publication. Inspect the release files before installing.
Why do I want to use this package?
In our shop shipping to different countries is possible but shipping costs vary for different items and destination countries. (the ups plugin is bound to ups service which is not that common and quite expensive in our region)
Writing a custom shipment plugin that handles all these cases seemed to be too much work for the start.
We have a small website with shop functionality (no dedicated webshop) and expect few orders (about 0-10 per week).
That’s why we decided to let our staff calculate shipping costs and handle the payment (via credit card, bank transfer, cash on delivery, etc) and fulfillment part of the shopping process offline.
What this package does
getpaid.emailcheckout customize the CheckoutReviewAndPay step so users need not supply credit card information.
currently orders stay in CHARGING state. getpaid’s order interface does not offer the possibility to set the state to charged atm.
Requirements
This package has been developed for and tested with
Plone 4.0.X (older plone versions should work though)
Products.PloneGetPaid >= 0.10.1
Questions - Feedback
Just drop me an email: harald (at) webmeisterei dot com
CHANGES
0.1 (2011-02-14)
initial release (used >6 months in production)
Metadata
Release files for getpaid.emailcheckout 0.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
File added late
1 file was uploaded more than 14 days after the first file in this release.
While project maintainers occasionally add legitimate files to an existing release, late additions can also indicate a security compromise.
We recommend inspecting the release files before installing.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| getpaid.emailcheckout-0.1.zip | 13.6 kB | Without provenance | Details for getpaid.emailcheckout-0.1.zip |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| getpaid.emailcheckout-0.1-py2.6.egg | Legacy Egg format | - | - | Details for getpaid.emailcheckout-0.1-py2.6.egg |
Total release size: 23.2 kB
Release files / getpaid.emailcheckout-0.1.zip
File added late
This file was uploaded more than 14 days after the first file in this release.
While project maintainers occasionally add legitimate files to an existing release, late additions can also indicate a security compromise.
We recommend inspecting the release file before installing.
| Download URL | getpaid.emailcheckout-0.1.zip |
|---|---|
| Size | 13.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
bc249573c0dcbd3a6dc189cbef48592e512fa1ada729465e9fe4a9246422a0d7
|
|
BLAKE2b-256 checksum How to use checksums |
7f680ba190629cfdb89466fe1513ef2d7fa6d2179a137777bb3c957b7949a1cf
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Release files / getpaid.emailcheckout-0.1-py2.6.egg
| Download URL | getpaid.emailcheckout-0.1-py2.6.egg |
|---|---|
| Size | 9.6 kB |
| Tags | Egg |
|
SHA-256 checksum How to use checksums |
98a8b5cf4c63d1067221d62f0ce9674f20cc97de0ff79d27c286ca2d5879f4a4
|
|
BLAKE2b-256 checksum How to use checksums |
50de033a880301694f7b9dd99e43fb27124267993669061b31df6a94913c75f3
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for getpaid.emailcheckout 0.1
Upload timing
Release file added late
1 file was uploaded more than 14 days after the first file in this release.
While project maintainers occasionally add legitimate files to an existing release, late additions can also indicate a security compromise.
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.