Stripe payment processor for bda.plone.shop.
Installation
This package is part of the bda.plone.shop stack. Please refer to https://github.com/bluedynamics/bda.plone.shop for installation instructions.
Include this package to your setup dependencies and install this package via Plone control panel add on installation page or add bda.plone.stripe to install dependencies in your integration package generic setup dependencies.
Configuration
In order to make this payment processor work properly you need to define the Stripe Secret key and Publishable key. You can obtain these keys from https://stripe.com.
You either need to configure these keys in Shop Control Panel under Stripe of via your integration package generic setup registry.xml
Create translations
$ cd src/bda/plone/stripe/ $ ./i18n.sh
Contributors
Robert Niederreiter (Author)
Peter Holzer (Development)
Changes
1.0 (2024-04-30)
Initial work.
License
Copyright (c) 2012-2024, BlueDynamics Alliance, Austria All rights reserved.
Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:
Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.
Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution.
Neither the name of the BlueDynamics Alliance nor the names of its contributors may be used to endorse or promote products derived from this software without specific prior written permission.
THIS SOFTWARE IS PROVIDED BY BlueDynamics Alliance AS IS AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL BlueDynamics Alliance BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
Release files for bda.plone.stripe 1.0
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 |
|---|---|---|---|---|
| bda.plone.stripe-1.0.tar.gz | 19.8 kB | Without provenance | Details for bda.plone.stripe-1.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| bda.plone.stripe-1.0-py3-none-any.whl | Python 3 | none | any | Details for bda.plone.stripe-1.0-py3-none-any.whl |
Total release size: 47.0 kB
Release files / bda.plone.stripe-1.0.tar.gz
| Download URL | bda.plone.stripe-1.0.tar.gz |
|---|---|
| Size | 19.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
fcfaf93345162b0f6b2a58dc6c21246a5cc66a01abf9010a2190aec8c3fd91a3
|
|
BLAKE2b-256 checksum How to use checksums |
f659d90d61130a0b5d205b119210b9a93fb31206b7433659fd60fad43a924b8e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.0.0 CPython/3.9.2
|
Release files / bda.plone.stripe-1.0-py3-none-any.whl
| Download URL | bda.plone.stripe-1.0-py3-none-any.whl |
|---|---|
| Size | 27.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
0334d08ee7f723cae068d66051fbe95b7d040634f061e4e0ebb5db0d0daf57df
|
|
BLAKE2b-256 checksum How to use checksums |
fa78397eafd506381add07a07e73fd1360d9191ce8b68cedb5cad1be4d3e47f8
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.0.0 CPython/3.9.2
|
Security for bda.plone.stripe 1.0
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.
