Skip to content

Testing, troubleshooting and updates

Before accepting customer payments

Use a test copy of the shop, a valid activation and an explicitly assigned Saferpay test terminal. A mame staging URL alone does not make a live terminal safe for testing. Do not reuse production callback credentials without an agreed test arrangement.

Check these cases with the actual checkout, currencies and shipping rules you will use:

  • Successful payment, cancelled payment, declined payment and a delayed/pending result.
  • Return to the shop, authenticated reconciliation and signed webhook delivery, including a customer closing the payment window.
  • Authorization only, full/partial capture, cancellation and full/partial refund for the methods contracted to support them.
  • Correct Magento order, transaction, invoice, credit memo and cumulative amounts; no duplicate charge after a repeated return or notification.
  • Guest and signed-in checkout, explicit saved-method consent, use and removal of a saved method.
  • Every enabled payment option/group, discount, shipping and tax case. Repeat with Luma and/or Hyvä as actually deployed, on mobile and desktop.
  • Website scope, language, German address form and license capacity, particularly in installations with multiple Websites.

Only claim acceptance for the versions and payment methods actually tested. An Adobe Commerce installation needs its own qualification, including enabled Commerce modules and the actual deployment configuration.

Troubleshooting

Symptom Check
Composer authentication fails Valid module license, dedicated Downloads credentials, repository host and stored authentication. Payment API credentials do not authenticate Composer.
An adapter cannot be installed Your own Hyvä dependencies/licenses and compatible core/Theme/Checkout constraints. Install the matching packages together.
No Saferpay method appears Correct Website, enabled connection, active store/terminal, synchronization, enabled payment options, billing country, currency and order limits.
A method vanished after configuration changes Recheck/synchronize the new connection. Old terminal capabilities are intentionally not reused with changed credentials.
The popup cannot finish Popup permission, same account, correct Website URL, license capacity and current settings. Restart setup if it expired or the Website changed.
Payment remains pending Magento cron, callback reachability, signature key and authenticated status. Inspect recovery before retrying payment.
A capture/refund is uncertain Reconcile the existing operation and confirmed amounts. Preserve the journal; avoid a second speculative operation.
Hyvä styling or old text remains Rebuild the active child theme, deploy the actual locales and refresh Magento/browser caches.

Use Sales > Saferpay payment recovery and the redacted module log var/log/mame_saferpay.log. A server administrator can reconcile one known attempt or the bounded pending set:

php bin/magento mame:saferpay:reconcile ATTEMPT_UUID
php bin/magento mame:saferpay:reconcile

Share only redacted error text, module/Magento versions, order/attempt references and the time of the issue with support. Never send API secrets, license keys, webhook keys or full payment payloads.

Composer updates

Back up the database, files, composer.json/composer.lock and the protected Magento encryption key. Test the approved release in staging first. Composer updates run through your deployment workflow; the module does not update itself when a new release is uploaded to mame.

For the standard checkout:

composer update mamedev/module-saferpay --with-all-dependencies

For Hyvä Theme and Hyvä Checkout, include all installed companions:

composer update mamedev/module-saferpay mamedev/module-saferpay-hyva mamedev/module-saferpay-hyva-checkout --with-all-dependencies

Use constraints that permit the approved release. Review the lock-file changes and dependency compatibility before deployment. Then run:

php bin/magento setup:upgrade
php bin/magento setup:di:compile
php bin/magento setup:static-content:deploy -f de_CH en_US
php bin/magento cache:flush

With Hyvä, regenerate its configuration and rebuild the active child theme before static-content deployment, as in the installation guide. Use your actual storefront locales and normal maintenance/worker procedures. Verify the installed versions, connection, checkout and pending-payment recovery after deployment.

ZIP updates and rollback

Download the approved core and matching installed companion archives from Downloads. Replace each module's files at its existing app/code/Mame/… path, removing obsolete source files through a controlled deployment. Keep environment configuration, credentials, encryption keys and all payment tables. Run the same Magento/Hyvä deployment steps and acceptance checks. Do not leave duplicate Composer and app/code copies.

Restore only a compatible, tested code/database backup if rollback is necessary. A database restore cannot undo a provider charge or refund; reconcile operations performed since the backup. Disabling or removing source files is not permission to delete financial history or issue compensating refunds automatically.