Testing, troubleshooting and updates¶
Start with the individual shop, its selected mame store and the latest payment state. Avoid changing several connection settings at once.
Test before going live¶
Use the test environment and payment details agreed with mame/your payment provider. A locally installed module is not automatically connected to a sandbox.
- Verify the shop URL, active license, payment configuration and terminal.
- Confirm that the intended methods are enabled, available and allowed by PrestaShop payment restrictions.
- Complete an agreed test payment and check the return to the shop, order amount/currency, Saferpay panel, order state and expected email.
- Check a customer cancellation and a failed payment; neither should be treated as a captured payment.
- If using authorization, test the later capture. Test partial refunds only where supported and agreed.
- Confirm that server notifications can reach the shop and that payment state remains correct if the customer closes the browser before returning.
- Repeat relevant checks for each shop, checkout theme, currency and enabled wallet/device combination.
Connection problems¶
| Symptom | What to check |
|---|---|
| Connect button disabled | Select one individual shop; check the employee's module-configure permission |
| Popup blocked or immediately closed | Allow popups, reload the module page and sign in again if needed; use the current module release |
| Setup expired / settings changed | Close stale settings tabs and start a fresh connection from the current page |
| No selectable stores | Check ownership, active payment configuration, store and terminal; incomplete stores cannot be selected |
| License cannot be activated | Correct PrestaShop product license, validity, activation allowance and the shop URL |
| Connected but old methods shown | Use the offered refresh action, or Synchronize stores under manual connection settings; save and reload the module |
| HTTP/API connection error | Outbound HTTPS, PHP cURL/OpenSSL, valid server certificates and matching mame connection details |
Payment method missing at checkout¶
Check these in order:
- The module is active and configured for the current shop.
- The option is enabled and marked available for the selected store.
- The store's methods were synchronized after the provider/configuration change.
- Payment → Preferences allows the customer's currency, country, group and carrier.
- The browser/device supports the selected wallet; the separate Apple Pay option is Safari-filtered.
- The checkout theme renders standard PrestaShop payment options and its cached assets are current.
A store having VISA does not imply support for every card brand or wallet. The grouped Credit card option shows the synchronized available card brands.
Order and payment disagree¶
Open the order's Saferpay panel and use Check status. Compare the payment with mame and, if needed, Saferpay. Check the module's paid/authorized state mapping and notification reachability.
An admin login wall, maintenance restriction or firewall must not block the payment-notification endpoint. Have your host or support check the actual request/result. Do not disable signature checks or mark an order paid just to hide an unresolved notification failure.
Logs and support¶
Enable Write logs in the module settings when troubleshooting. Review Advanced Parameters → Logs if available in your PrestaShop version. Send support the module/PrestaShop/PHP versions, affected shop, approximate time, order reference, payment status and the relevant transaction reference through the support channel.
Never include API client secrets, license keys, webhook keys, full card data or unredacted customer details. After resolving the issue, return logging to the level appropriate for your shop.
Update the module¶
Back up files and database, then apply the supplied module update using the Module Manager. Preserve the existing connection and transaction history; uninstalling is not an update procedure. Clear the relevant PrestaShop/theme cache after updating assets and repeat the checkout tests.
If the shop URL, mame account or store changes, review license entitlement and reconnect in the intended individual shop context.
Contact mame support if the result remains unclear.