satispay / magento2-plugin

satispay/magento2-plugin

Satispay Magento2 Plugin

magento2-module Compatibility: 2.4.7-2.4.8 Code Quality: Fail Tests: N/A Security: Pass MIT

Satispay Magento2 Plugin

Packagist Version
Packagist Downloads

Installation

Install with composer: composer require satispay/magento2-plugin

php bin/magento module:enable Satispay_Satispay
php bin/magento setup:upgrade
php bin/magento setup:di:compile

Change Log

All notable changes to this project will be documented in this file.

The format is based on Keep a Changelog
and this project adheres to Semantic Versioning.

2.2.5

Add success and failure return codes to CompleteUnhandledTransaction command

2.2.3

  • Made the plugin compatible with multishop configuration

2.2.2

  • Updated brand assets

2.2.1

  • Improved order management flow for 'PENDING' and 'CANCELLED' payments

2.2.0

  • Change flow for PENDING payments coming from Satispay API

2.1.2

  • Fixed bug regarding the <public_key> parameter. If the user didn't flush the cache after enabling the Plugin, the website threw an error.
  • Now the user has to: Enable the Plugin > Save the configuration > Set the token

2.1.1

  • Added Satispay logo on checkout

2.1.0

  • Added cron to finalize unhandled payments
  • Added support to web-app-web switch

2.0.5

  • Replace description with external_code in payment creation

2.0.3

  • Send new order email only when payment is accepted
  • Cancel order if payment is canceled

2.0.2

  • Performed refactoring to adhere to Magento 2 Coding Standards
  • Set SDK requirement to version ^1.2
  • Removed SDK directory
  • Set setup_version in module.xml
  • Added checkout-agreements-block to payment form
  • Added sort_order field in system.xml

2.0.1

bump version

2.0.0

Merge pull request #9 from satispay/new-version
New version with GBusiness APIs

1.2.4

fix capture notification

1.2.3

update sdk and bump version

1.2.2

bump version

1.2.1

bump version

1.2.0

working version

1.1.1

bump version

1.1.0

publish 1.1.0

1.0.0

1.0.0

Versions
Version Stability QA Status Compatibility Released
2.2.6 stable Fail Magento 2.4.7-2.4.8 Details 2026-03-05 13:13:59
2.2.5 stable Not tested Not yet tested Details 2025-02-14 10:46:54
2.2.3 stable Not tested Not yet tested Details 2025-02-11 14:30:17
2.2.2 stable Not tested Not yet tested Details 2024-06-11 07:38:57
2.2.1 stable Not tested Not yet tested Details 2024-03-25 14:46:12
2.2.0 stable Not tested Not yet tested Details 2024-02-09 11:39:58
2.1.2 stable Not tested Not yet tested Details 2023-11-13 10:06:40
2.1.1 stable Not tested Not yet tested Details 2022-09-20 17:24:45
2.1.0 stable Not tested Not yet tested Details 2022-05-05 16:38:29
2.0.5 stable Not tested Not yet tested Details 2020-08-07 13:06:19
2.0.3 stable Not tested Not yet tested Details 2020-06-26 09:18:31
2.0.2 stable Not tested Not yet tested Details 2020-04-20 10:00:25
2.0.1 stable Not tested Not yet tested Details 2019-10-21 13:46:20
2.0.0 stable Not tested Not yet tested Details 2019-10-14 08:30:41
1.2.4 stable Not tested Not yet tested Details 2018-12-05 08:57:48
1.2.3 stable Not tested Not yet tested Details 2018-02-28 16:58:13
1.2.2 stable Not tested Not yet tested Details 2018-02-26 15:13:43
1.2.1 stable Not tested Not yet tested Details 2018-02-26 15:11:23
1.2.0 stable Not tested Not yet tested Details 2018-02-26 14:36:10
1.1.1 stable Not tested Not yet tested Details 2018-02-22 17:44:47
1.1.0 stable Not tested Not yet tested Details 2018-02-15 17:01:58
1.0.0 stable Not tested Not yet tested Details 2017-09-07 13:53:17

Requires 5

Package Constraint
magento/framework >=100.0.0
magento/module-checkout >=100.0.0
magento/module-payment >=100.0.0
magento/module-sales >=100.0.0
satispay/gbusiness-api-php-sdk ^1.2

Compatibility

Each Magento release line is installed on its supported PHP versions, then the module is built (DI compilation + static-content deploy) and its unit and integration suites are run. The matrix shows the lines and PHP versions the module is confirmed to install and run on. Code-quality results further down (phpstan, phpcs, …) are reported separately and never affect compatibility.

Compatibility matrix (Magento × PHP)
Magento PHP 8.2 PHP 8.3 PHP 8.4 PHP 8.5
2.4.7 Pass Pass
2.4.8 Pass Pass
2.4.9 Fail di error Fail di error

Code Quality

Advisory checks against the module's source. Static analysis runs once across the whole module; PHPStan re-runs per Magento + PHP version because resolvable symbols differ between releases. These NEVER affect the Compatibility badge — a phpcs finding can't make a module incompatible.

Static analysis

Coding standards (phpcs), mess detection (phpmd), copy-pasted code (cpd), PHP cross-version compatibility, composer.json validity. Each runs once for the whole module.

Static analysis results
Tool Status Findings Summary
PHPCS Warning 45 45 warnings (ruleset: Magento2) — 28 auto-fixable with phpcbf
PHPMD Warning 13 13 rule violations (UnusedFormalParameter:8, MissingImport:4, ExcessiveParameterList:1)
Cpd Pass 0
Composer validate Info 5 valid; 5 advisory notes (composer validate --strict)

PHPStan

Type-checks the module's PHP against a real Magento install at the configured gate level. Re-runs per Magento and PHP version because resolvable symbols differ between releases. Cell → details modal.

PHPStan results by Magento and PHP version
Magento PHP 8.2 PHP 8.3 PHP 8.4 PHP 8.5
2.4.7 21 21
2.4.8 21 21
2.4.9 22 22

Tests

Unit and integration suites, run for each applicable Magento and PHP version. A test failure speaks to the module's behaviour, not its compatibility with a Magento line, so it is reported here separately and never reddens the compatibility matrix.

Unit tests

Unit tests results by Magento and PHP version
Magento PHP 8.2 PHP 8.3 PHP 8.4 PHP 8.5
2.4.7 N/A N/A
2.4.8 N/A N/A
2.4.9 N/A N/A

Integration tests

Integration tests results by Magento and PHP version
Magento PHP 8.2 PHP 8.3 PHP 8.4 PHP 8.5
2.4.7 N/A N/A
2.4.8 N/A N/A
2.4.9 N/A N/A

Security

Security checks run directly against the module: an audit of its declared dependencies for known vulnerabilities (composer audit) and a scan of its source for malware and web-shell signatures. Each runs once. A malware detection fails the version outright.

Security results
Tool Status Findings Summary
Composer audit Pass 0
Malware scan Pass 0
License
MIT
Authors
  • Satispay
Make it pay

Turn an existing module into recurring revenue.

If you already maintain a Magento 2 module on GitHub or GitLab, listing it on Packagento takes about five minutes. We mirror your tags, handle distribution signing, and route paid licenses through Stripe Connect, so you can keep shipping the way you already do.