Skip to content

Magento 2 Loki Checkout

Use ICEPAY payment methods with Loki Checkout in Magento 2.


The ICEPAY integration for Loki Checkout adds support for ICEPAY payment methods to Magento stores using Loki Checkout.

It works alongside the standard ICEPAY Magento 2 module and provides the compatibility required to use ICEPAY payment methods within Loki Checkout.

Make sure your Magento installation already has:

Loki Checkout

Loki Checkout must be installed and working in your Magento store before adding the ICEPAY compatibility module.

Loki Checkout documentation →

The current Loki Checkout ICEPAY package requires PHP 8.2 or later within the supported PHP 8 releases. Loki lists Magento 2.4.7 and 2.4.8 for the integration.

Install the ICEPAY integration for Loki Checkout using Composer:

Terminal window
composer require loki-checkout/magento2-icepay

Enable the Loki Checkout ICEPAY integration and the standard ICEPAY Magento module:

Terminal window
php bin/magento module:enable LokiCheckout_Icepay Icepay_Payment

Then run the Magento upgrade and clear the cache:

Terminal window
php bin/magento setup:upgrade
php bin/magento cache:clean

You can verify that the modules are enabled with:

Terminal window
php bin/magento module:status LokiCheckout_Icepay
php bin/magento module:status Icepay_Payment

There is no separate ICEPAY merchant configuration for the Loki Checkout module.

Configure your ICEPAY Account and payment methods through the standard ICEPAY Magento 2 integration.

See the Magento 2 integration guide for the regular ICEPAY configuration.

Once the standard ICEPAY module, Loki Checkout, and the Loki Checkout ICEPAY integration are installed, enabled ICEPAY payment methods can be used within Loki Checkout.

The Loki Checkout ICEPAY module connects the standard ICEPAY Magento integration with Loki Checkout.

The integration adds the Loki-specific functionality required for the ICEPAY payment flow, including:

  • Payment redirects.
  • Payment method icons.
  • Compatibility between ICEPAY payment methods and the Loki Checkout payment step.

Payment creation, merchant configuration, payment status handling, and the connection with ICEPAY remain part of the standard ICEPAY Magento 2 module.

After installing the module, place a test order through Loki Checkout.

Check that:

  1. The expected ICEPAY payment methods are displayed.
  2. A payment method can be selected.
  3. The order can be placed successfully.
  4. The customer is redirected to the appropriate ICEPAY payment flow.
  5. Returning from the payment flow redirects the customer back to your store.
  6. The Magento order receives the expected payment status.

Update the Loki Checkout ICEPAY integration using Composer:

Terminal window
composer update loki-checkout/magento2-icepay
php bin/magento setup:upgrade
php bin/magento cache:clean

After updating, test the checkout again before deploying the changes to production.

The Loki Checkout ICEPAY integration is maintained as part of the Loki Checkout ecosystem.

For questions about your ICEPAY merchant configuration or payment processing, contact the ICEPAY team.

Contact the ICEPAY team

Get help with your ICEPAY Magento integration.

For issues specifically related to the Loki Checkout compatibility module, use the Loki Checkout project on GitHub.

Loki Checkout issues

Report an issue with the Loki Checkout ICEPAY integration.

ICEPAY payment methods are not visible in Loki Checkout

Check that:

  • The standard ICEPAY Magento 2 module is installed and enabled.
  • The Loki Checkout ICEPAY module is installed and enabled.
  • Loki Checkout itself is installed and enabled.
  • The payment method is enabled in Stores → Configuration → Sales → Payment Methods → ICEPAY.
  • The correct ICEPAY merchant is configured.
  • The payment method is enabled for your ICEPAY merchant.
  • Your Magento and PHP versions meet the extension requirements.

Verify that the relevant modules are enabled:

Terminal window
php bin/magento module:status Icepay_Payment
php bin/magento module:status LokiCheckout_Core
php bin/magento module:status LokiCheckout_Icepay

Clear the Magento cache after changing the payment configuration:

Terminal window
php bin/magento cache:flush

If the payment methods are available in the standard Magento checkout but not in Loki Checkout, check the Magento logs for errors related to LokiCheckout_Icepay.

The standard Magento checkout works, but Loki Checkout does not

Confirm that the Loki Checkout ICEPAY module is enabled:

Terminal window
php bin/magento module:status LokiCheckout_Icepay

If the module is disabled, enable it:

Terminal window
php bin/magento module:enable LokiCheckout_Icepay

Then run the Magento upgrade and clear the cache:

Terminal window
php bin/magento setup:upgrade
php bin/magento cache:flush

Also confirm that Loki Checkout itself is enabled in Stores → Configuration → Loki → Loki Checkout.

Test the checkout again after these changes.

If the problem continues, check the Magento logs for errors related to Loki Checkout or the ICEPAY integration.

The customer is not redirected to the payment

Confirm that:

  • The standard ICEPAY Magento module is enabled.
  • The Loki Checkout ICEPAY module is enabled.
  • The selected payment method is enabled for your ICEPAY merchant.
  • The Magento order is created successfully.

Check the Magento logs for errors that occur when the order is placed.

If ICEPAY works through the standard Magento checkout but the redirect does not occur through Loki Checkout, the issue may be related to the Loki Checkout compatibility layer.

In that case, include the Magento version, PHP version, Loki Checkout version, ICEPAY extension version, and any relevant error message when reporting the issue.

The payment remains pending

Open the corresponding order in Sales → Orders and review its status history.

Then check the payment in the ICEPAY Portal and compare its status with the Magento order.

The Loki Checkout module provides compatibility with the checkout. Payment processing and order status handling are provided by the standard ICEPAY Magento 2 integration.

If the payment has been completed in ICEPAY but the Magento order has not been updated, contact the ICEPAY team with the order number, payment reference, Merchant ID, and approximate time of the payment.

Do not include your Merchant Secret in a support request.

The customer cannot complete the payment

Confirm that:

  • The correct Merchant ID and Merchant Secret are configured.
  • The ICEPAY merchant is enabled.
  • The selected payment method is available for the merchant.
  • The standard ICEPAY and Loki Checkout ICEPAY modules are enabled.
  • Your Magento store can communicate with ICEPAY.

Check the Magento logs for errors related to the payment request or checkout.

If an error is shown during checkout, include the error message when contacting the ICEPAY team.

The extension does not work after an update

Confirm that your Magento, PHP, Loki Checkout, and ICEPAY extension versions are compatible.

Check whether the relevant modules are enabled:

Terminal window
php bin/magento module:status Icepay_Payment
php bin/magento module:status LokiCheckout_Core
php bin/magento module:status LokiCheckout_Icepay

Then run the Magento upgrade and clear the cache:

Terminal window
php bin/magento setup:upgrade
php bin/magento cache:flush

If your deployment process requires it, regenerate compiled code and static content before testing the checkout again.

If the issue continues, check the Magento logs and include the ICEPAY module version, Loki Checkout version, Magento version, PHP version, and any relevant error message when contacting the ICEPAY team.

The ICEPAY configuration is not taking effect in Loki Checkout

ICEPAY settings are managed by the standard Magento 2 module. There is no separate merchant configuration for the Loki Checkout compatibility module.

Make sure the ICEPAY settings were saved for the correct website or store view.

Then clear the Magento configuration cache:

Terminal window
php bin/magento cache:clean config

Reload the configuration and test Loki Checkout again.

If the problem continues, confirm that no website-level or store-level configuration is overriding the value you expect.