Skip to content

Connect a Magento Website

Prepare Saferpay through mame

Sign in to mame. Arrange the Saferpay connection and required Worldline/acquiring contracts through mame. Additional payment methods may need separate acceptance contracts. Complete merchant activation before expecting live payments.

Prepare an active Saferpay payment configuration, store and terminal in the same mame account as the module license. Follow the activation steps and review the current fees and terms shown there. A test terminal must be used for test payments. The mame staging environment and the terminal's provider test/live mode are separate settings.

Connect from Magento

  1. Open Stores > Configuration > Sales > Saferpay in Magento Admin.
  2. Select the intended Website in the scope selector. Store Views share the Website connection; configure each Website separately.
  3. Choose Connect with mame and allow the popup for the shop.
  4. Sign in to the owning mame account. Select the Saferpay for Magento 2 license, the correct Saferpay store and its payment configuration/terminal. Check the Website URL before approval. The wizard also offers supported store/configuration creation steps where needed.
  5. Approve the connection and wait until Magento confirms that the settings were transferred. Keep both windows open until the process completes.
  6. Save the configuration and enable the connection. Check its status and the synchronized payment methods.
  7. Enable your desired methods under Sales > Payment Methods, as described in checkout settings.

The setup transfers API-client credentials, the license, webhook key and the numeric mame Saferpay store ID. This store ID is different from a Worldline customer number or terminal ID. Do not substitute those numbers or copy a connection from another Website.

Single permits one activation and Multi up to five. If capacity is exhausted, review obsolete activations in license management or upgrade. Matching URLs in the wizard are suggestions; verify the actual store and terminal before approval.

Manual connection

Use the manual-settings disclosure if your browser cannot complete the popup. Open the Saferpay Magento setup assistant in mame, select the correct Website URL, license, store and payment configuration, and create the designated Magento API client. This is separate from Composer download access.

Transfer only the requested client ID, secret, license key, webhook key and mame store ID into the corresponding Website fields. Save, run the connection check/synchronization and review the listed methods. Keep credentials out of screenshots, email, browser URLs and Git. If the assistant is unavailable in your account, contact support rather than using another platform's setup assistant.

Test and production environments

Production mame access is the default. Connecting to stage.mamedev.ch is a developer option, allowed only after the server administrator adds this entry to the array returned by app/etc/env.php:

'mame_saferpay' => [
    'allow_staging' => true,
],

Merge it into the existing PHP array; preserve all other settings and the encryption key. Edit the file on the host or through your deployment tooling. Do not run the file as a shell command. Clean the configuration cache and select the intended mame environment in Saferpay's Website configuration. Use separate credentials and a provider test terminal.

Before going live, connect to production with the approved live terminal and recheck methods, currency and callbacks. Existing payment references keep their original environment. Do not change environments to retry an unresolved financial operation.

Webhooks and cron

The module's Website-specific endpoint is:

https://shop.example/saferpay/webhook/receive/website/WEBSITE_ID

Replace the host, base path and Website ID with the real shop values. Keep it reachable over HTTPS without login or maintenance interception. The connection uses the matching webhook key; never disable signature verification to solve a callback problem.

Keep Magento cron running. Notifications and scheduled recovery trigger authenticated status reads; a successful browser return alone cannot mark an order paid. Make an actual test payment and verify the resulting Magento status, invoice and callback before enabling customer payments.