Skip to content

Testing, troubleshooting and updates

Before production

Use a separate staging shop and an appropriate TWINT test/live store. A local simulation is useful for Magento behavior but does not prove hosted TWINT acceptance. Never replay a customer's payment or webhook as a test.

Verify:

  1. A new installation, download entitlement and Website connection work with the intended account.
  2. Guest and signed-in ordinary purchases complete with the correct amount, address, currency and one Magento order/invoice.
  3. Each enabled Express location works for physical/virtual products, quantity and required options. Product Express preserves the ordinary cart.
  4. Shipping options, coupons, tax, free shipping and any required canton completion produce the expected final total.
  5. Cancelling ordinary checkout returns to checkout; cancelling Express returns to its originating page. Neither creates a paid order.
  6. Pending/late results, browser reloads and duplicate notifications do not create another payment, order, capture or invoice.
  7. Saved-method consent, a later saved-method purchase and revocation work with the intended TWINT environment.
  8. Immediate/deferred capture and online partial/full refunds work for the enabled payment setup.
  9. Production HTTPS webhooks reach the correct Website and are authenticated. Check successful asynchronous updates independently of the browser return.
  10. If using Hyvä, repeat relevant flows on desktop/mobile with the deployed child theme and installed Checkout version.

Use synthetic customer details. Check the resulting native orders and provider/mame transaction states; a success-page screenshot alone is insufficient.

When TWINT or Express is missing

  • Verify Enable TWINT, current connection status, owned unexpired license and the selected active store/payment configuration in the correct Website scope.
  • Check CHF and the cart total. Express also requires its master switch and the relevant location switch.
  • For Hyvä, verify the required Theme/Checkout companion modules and dependencies. Regenerate Hyvä configuration, rebuild the actual child theme's CSS and deploy the correct locales.
  • Clear the relevant Magento caches and load a fresh page. With CSP/SRI asset errors, correct the deployed files and integrity metadata rather than disabling the protection.
  • If changing payment providers, disable the unwanted provider's payment methods in each relevant configuration scope. This does not configure the TWINT connection automatically.

Cancellation, failed QR scan or pending payment

A QR scan or cancellation button does not by itself establish the provider outcome. Check the authenticated payment status and the matching order/mame transaction. A provider rejection, wallet/test-environment mismatch or abandoned authorization may require a fresh customer decision after the previous outcome is resolved. Do not assume every QR cancellation is a Magento or Hyvä defect.

For a pending payment, use the provided refresh/manual status action. Do not create a second order while the first payment is uncertain. If the outcome requires review, contact support with the order number, time, module versions and the nonsecret error code. Never include API credentials, a webhook key, active QR payloads or customer payment data.

Webhooks and scheduled recovery

The module supplies a Website-specific endpoint of the form /twint/webhook/receive/website/WEBSITE_ID. Keep public HTTPS access working and review proxy/firewall rules. A password-protected or localhost-only shop cannot prove production webhook delivery.

Maintain Magento cron and your host's worker/deployment practices. For a test database copied from another shop, do not start broad reconciliation over retained historical payment bindings. A separately installed empty shop is safer for installation tests.

Update with Composer

Back up database/files/lock file and test the update in staging. Use your normal maintenance and worker process, then update the installed packages:

composer update mamedev/module-twint --with-dependencies
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

For Hyvä, include the installed TWINT Theme/Checkout companions in the Composer update, regenerate Hyvä configuration and rebuild the active child theme before Magento static deployment. The Downloads dialog provides commands for the selected frontend. Keep maintenance active if a deployment fails and use the shop's verified recovery plan.

The module's update-check action reports licensed available releases; it does not run Composer or change shop code from a web request. Pin/review the target version in your deployment workflow.

Update from ZIP

Use the reviewed package for each installed module, replace that module's files in its existing app/code/Mame/... location and run Magento upgrade/DI/assets/cache steps. Retain credentials, configuration and payment history. Do not mix an app/code copy with a Composer copy of the same module.

For rollback, restore a consistent tested application/database backup through your hosting process. Removing the extension or dropping its tables is not a payment recovery procedure.