Skip to main content
Welcome to the preview portal — This is an early release of the new Doc Hub experience, with more content coming soon.
Technology Partner

Configure the PrestaShop Plugin


Go to Modules > Module Manager, scroll down to , and click Configure to access the PrestaShop plugin configuration settings.

Click Save after working on each configuration tab.

Minimum Configuration

As a minimum to accept payments with , configure these settings.

General Settings Tab:

  • Checkout Label: this text is displayed on your checkout page to your customers.
  • Sandbox Mode:
    • Yes: choose for testing your test account.
    • No: choose for production transactions.
  • Merchant ID: the transacting merchant ID (MID) that assigned to you.
  • Merchant Key ID: the key from your REST API Shared Secret Key.
  • Merchant Secret Key: the shared secret from your REST API Shared Secret Key.
  • Key File Path: enter the path and filename for the Response MLE certificate created in .
  • Key Password: enter the password for the Response MLE certificate.
  • Checkout Version: optional field to force a version of Unified Checkout. Format 1.x. It is recommended to leave this blank to always take the latest version.
  • Display Mode:
    • Embedded: the payment widget loads within the browser page.
    • Sidebar: the payment widget appears to the side of the browser.
  • Tokenization: set to Yes to enable your customers to save their cards for future purposes.
  • Fraud Management: set to Yes to inform the module that your account is configured for fraud screening and needs to subscribe to the REVIEW webhook notification.

Message-Level Encryption

Message-Level Encryption (MLE) uses certificates that ensure each message is securely encrypted and tied to the sender's verified identity, without needing to share secret keys in advance. MLE provides stronger authentication, easier key management, and better protection against fraud or tampering.

A shared secret uses the same key for both sending and receiving messages, meaning both parties must securely exchange and protect that key in advance. Although MLE can be simpler, it offers less identity verification and can be more vulnerable if the key is compromised.

Prerequisite: Message-Level Encryption requires a P12 certificate.

Tokenization

  • Network Tokens: if your account is enabled for Network Tokens, set to Yes to inform the module it needs to manage token lifecycle updates.

Report Settings

Report Settings Tab:

  • Transaction Request Report: when enabled, the extension downloads a report from containing details for transactions processed each day. Set to Yes to enable.
  • Payment Batch Detail Report: when enabled, the extension downloads a report from containing details of all captures and refunds that were submitted to your payment processor. Set to Yes to enable.

For all reports, it is strongly recommended that your PrestaShop store and the Portal user profile operate in the same time zone.

Report download locations:

  • In test mode: {PrestaShopModuleInstallationDirectory}//Reports/Sandbox
  • In production mode: {PrestaShopModuleInstallationDirectory}//Reports/Production

Registered Webhooks

Registered Webhooks Tab:

View information about subscribed webhooks. You can delete a webhook, but doing so can affect transaction response handling. Webhooks are automatically subscribed to based on your configuration settings.

Additional Options

General Settings Tab:

  • Enhanced Logs: to generate logs that can be accessed from Configure > Advanced Parameters > Logs, set to Yes. This feature is not recommended for production mode.

Last published: November 18, 2026