Payment Acquirers’ configuration with server_environment
This module allows to configure payment acquirers using server_environment files.
Table of contents
Installation
To install this module, you need to have the server_environment module installed and properly configured.
After installed, the environment configurable fields will be read from the environment files.
Configuration
With this module installed, the payment acquirers are configured in the server_environment_files module (which is a module you should provide, see the documentation of server_environment for more information).
In the configuration file of each environment, for each payment acquirer you may use the section [payment_acquirer.technical_name] to configure the acquirer values, where “technical_name” is the acquirer’s tech_name.
This module alone only lets you configure the state field, which allows to set the acquirer’s environment. Most payment acquirers will define specific fields to store their credentials, so glue modules are required to include them in _server_env_fields if that’s what you want.
Example of config file
[payment_acquirer.paypal] state = test
Usage
Once configured, Odoo will read the payment acquirer values from the configuration file related to each environment defined in the main Odoo file.
Known issues / Roadmap
Due to the special nature of this addon, you cannot test it on the OCA runbot.
Bug Tracker
Bugs are tracked on GitHub Issues. In case of trouble, please check there if your issue has already been reported. If you spotted it first, help us smashing it by providing a detailed and welcomed feedback.
Do not contact contributors directly about support or help with technical issues.
Credits
Contributors
-
Iván Todorovich <ivan.todorovich@gmail.com>
Maintainers
This module is maintained by the OCA.
OCA, or the Odoo Community Association, is a nonprofit organization whose mission is to support the collaborative development of Odoo features and promote its widespread use.
Current maintainer:
This module is part of the OCA/server-env project on GitHub.
You are welcome to contribute. To learn how please visit https://odoo-community.org/page/Contribute.
Metadata
Release files for odoo13-addon-payment-environment 13.0.1.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| odoo13_addon_payment_environment-13.0.1.1.0-py3-none-any.whl | Python 3 | none | any | Details for odoo13_addon_payment_environment-13.0.1.1.0-py3-none-any.whl |
Release files / odoo13_addon_payment_environment-13.0.1.1.0-py3-none-any.whl
| Download URL | odoo13_addon_payment_environment-13.0.1.1.0-py3-none-any.whl |
|---|---|
| Size | 24.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
1a4df396a63ffa22939a7c5a25aa71b1b4a90733c69ed6033c7ab2e92704d9ab
|
|
BLAKE2b-256 checksum How to use checksums |
411a6d107e30d9cb124f2ee50b4b58a918a60d9f7f50151a04f4703bdbd0c8e0
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.0 CPython/3.8.5
|
Security for odoo13-addon-payment-environment 13.0.1.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.