Releases
Releases are published on GitHub, with release notes describing what changed. The module is not distributed through PrestaShop's addons marketplace, so GitHub is the place to check.
Upgrading
Download the .zip of the newer release and upload it through Modules → Module Manager → Upload a module, exactly as for a new installation. PrestaShop replaces the module and keeps your settings, and the module applies any database changes the new version needs.
Test an upgrade on a staging copy first. Read the release notes before you start, since a release occasionally retires a payment method or changes a default, and it is easier to plan for that than to discover it afterwards.
Clear your PrestaShop cache after upgrading, then place a test payment to confirm the module is working before you rely on it.
Staying informed
Watch the repository on GitHub to be notified of new releases. The release notes are the authoritative record of what changed; this page does not repeat them, because a copy would fall behind.
Reporting a problem
Report bugs as issues on the repository, with your PrestaShop version, your module version and enough detail to reproduce the problem. The relevant part of the module log usually makes the difference between a quick fix and a long exchange.
For a problem affecting live payments, contact support rather than opening an issue. See Contact us.
Contributing
Contributions are welcome. Fork the repository, branch from develop, and open your pull request against develop. The contributing guidelines cover the branch naming convention and what is expected of a pull request.
Updated 11 days ago