> For the complete documentation index, see [llms.txt](https://docs.ecommerce.seb.ee/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ecommerce.seb.ee/integration/web-plugins/magento-2/installation.md).

# Installation

Install the SEB E-commerce Payment Gateway module for Magento 2

**This page is for developers.** Merchants: forward it to whoever maintains your Magento installation.

## Prerequisites

* Magento Open Source on PHP 8.3+
* SSH/CLI access with permissions to deploy code and run `bin/magento`
* SEB E-commerce Payment Gateway credentials at hand (see [prerequisites](/integration/web-plugins.md))
* Back up code and database before installing

## Install

1. Download and extract the Magento 2 module package.
2. Copy the module into your Magento installation:

   ```bash
   mkdir -p app/code/EGW/Checkout
   cp -R <extracted>/EGW/Checkout/* app/code/EGW/Checkout/
   ```
3. Enable the module and upgrade the setup:

   ```bash
   bin/magento module:enable EGW_Checkout
   bin/magento setup:upgrade
   bin/magento setup:di:compile
   bin/magento cache:flush
   ```
4. In production mode, also redeploy static content:

   ```bash
   bin/magento setup:static-content:deploy
   ```
5. Verify: `bin/magento module:status EGW_Checkout` reports the module enabled, and **Stores → Configuration → Sales → Payment Methods** shows *SEB E-commerce Payment Gateway*.

The module needs no file edits and no environment-specific values beyond the credentials you enter in the admin. Continue with [Configuration](/integration/web-plugins/magento-2/configuration.md).

![Stores → Configuration → Sales → Payment Methods → Other Payment Methods, expanded to show the SEB E-commerce Payment Gateway section immediately after installation, before any values are entered.](https://1157570179-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FuBDtfypkI85zidcVwaDj%2Fuploads%2FUjFLfo5FGxzpsNqLH18T%2Fm2-payment-methods-panel.png?alt=media)

## Uninstall

```bash
bin/magento module:disable EGW_Checkout
bin/magento setup:upgrade
rm -rf app/code/EGW/Checkout
bin/magento setup:di:compile && bin/magento cache:flush
```

What remains: module configuration values (including credentials) in `core_config_data`, and all orders/invoices/credit memos it created. Remove the config rows manually if required, and delete the Callback URL registration in the Merchant Portal.

## Upgrade

Replace `app/code/EGW/Checkout` with the new version and re-run the enable sequence (`setup:upgrade`, `di:compile`, `cache:flush`, static deploy in production).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.ecommerce.seb.ee/integration/web-plugins/magento-2/installation.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.