Connect a Magento Website¶
1. Prepare the TWINT store¶
Sign in to the TWINT merchant portal. Add the settlement bank account if needed, then create an online store. In the standard integration flow, choose the PSP connection and mame as the PSP. Enter the shop details and retain the generated Store UUID.
The portal store, mame store and Magento Website are different objects. A TWINT Store UUID is not the numeric mame store ID. Use the correct merchant and settlement account for each intended Website.
Existing portal illustrations are available in the TWINT store setup guide. Portal wording can change; follow the corresponding current online-store/PSP flow.
2. Open the Magento connection¶
- Sign in to Magento Admin and open Stores > Configuration > Sales > Payment Methods > TWINT by mame.
- Select the intended Website in the configuration scope selector. Connection credentials are Website-scoped; connecting a Store View or Default Config is not a substitute.
- Enable TWINT and choose Connect with mame in the Easy setup area. Allow the popup for the shop.
- Sign in to the owning mame account in the popup and select a valid TWINT for Magento 2 license.
Single allows one active Website; Multi allows up to five. When a license is already fully assigned, disconnect an obsolete Website or upgrade the license. Do not reuse a connection ID copied from another shop.
3. Select or create the mame store¶
Follow the setup wizard to select an existing TWINT store or add one using the portal's Store UUID. Set the internal name and public store name. Check that the store is active and belongs to your mame account.
Select or create the mame payment configuration used to bill transaction fees and assign the store. Add the required billing payment method and activate the configuration. This configuration pays the mame fees; the TWINT settlement account controls where customer receipts are settled.
Review and accept the current TWINT service terms and displayed tariff in the account's activation flow. A module license alone does not activate a merchant store or payment configuration.
4. Finish the connection¶
Approve the intended Website, license and store in the wizard. API-client credentials, the module license, webhook key and store assignment are transferred to Magento. Wait for the successful handoff and connection status. Save the Magento configuration if the screen requests it, then use the available connection-check action.
The onboarding proof is exchanged by Magento's server. A local shop does not need an inbound callback to finish this popup handoff. Payment webhooks are a separate requirement: configure public HTTPS access for asynchronous payment notifications in a production shop.
For several Magento Websites, repeat the process in each Website scope. Store Views within the same Website inherit that Website's connection. If changing the TWINT store, use the module's store-selection action; it retains historical payment bindings.
Manual connection¶
Use Show manual connection settings only when configuring an existing integration manually or with support:
- Create an API client in mame with TWINT scope. An API token or Composer password is not the same credential.
- Copy the Client ID, one-time Client Secret, mame webhook key and valid module license into the corresponding Website settings.
- Select the correct mame TWINT store and complete the activation/connection check.
Use the exact secret values from the owning account. Magento stores secret fields encrypted. Do not send secret values, decrypted configuration or live payment payloads in support screenshots.
Test and live environments¶
The mame API host/environment and the TWINT store's test/live provider setup are separate choices. A test provider store may require a corresponding TWINT test app. Use the wallet and merchant setup intended for that environment.
Production is the ordinary merchant setup. Access to mame staging is deliberately restricted by server configuration and should only be enabled for an agreed test setup. Selecting a mode does not create a production merchant agreement. Complete the test checklist before taking customer payments.