> 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/woocommerce/installation.md).

# Installation

Install the SEB E-commerce Payment Gateway plugin for WooCommerce

## Before you start

* WordPress 6.7+ with WooCommerce 10.1+ active, PHP 8.3+
* Your SEB E-commerce Payment Gateway credentials at hand (see [prerequisites](/integration/web-plugins.md))
* Administrator access to WordPress admin
* Recommended: back up your site before installing any plugin

## Install from the plugin package

1. Download the WooCommerce plugin ZIP.
2. In WordPress admin, go to **Plugins → Add New Plugin → Upload Plugin**.
3. Choose the downloaded ZIP and select **Install Now**.
4. Select **Activate Plugin** (or later via **Plugins**: find *SEB E-commerce Payment Gateway* and select **Activate**).

![WordPress admin → Plugins → Add New Plugin → Upload Plugin, with the plugin ZIP chosen and the Install Now button visible.](https://1157570179-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FuBDtfypkI85zidcVwaDj%2Fuploads%2FKXEzACSabTnfqK7OjNYf%2Fwc-upload-plugin.png?alt=media)

![WordPress admin → Plugins → Installed Plugins, with the SEB E-commerce Payment Gateway activated.](https://1157570179-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FuBDtfypkI85zidcVwaDj%2Fuploads%2FisKF7cVRzGS5XWQO8vZC%2Fwc-upload-plugin-activated.png?alt=media)

The plugin needs nothing else to work: there are no files to edit and no environment values to obtain beyond your credentials. The payment method now appears under **WooCommerce → Settings → Payments**. Continue with [Configuration](/integration/web-plugins/woocommerce/configuration.md).

![WooCommerce → Settings → Payments list, showing the gateway method row with its Active status and the Manage button.](https://1157570179-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FuBDtfypkI85zidcVwaDj%2Fuploads%2FXBAC5x0lSPuUGnJhxVFM%2Fwc-payments-list.png?alt=media)

## Uninstall

1. **WooCommerce → Settings → Payments** → toggle the method off (stops offering it at checkout).
2. **Plugins** → *deactivate*, then *delete* the plugin.

What remains after deletion: the plugin's settings row in the WordPress options table (including credentials) and any order data or order notes it created. Orders and their statuses are never removed. If you uninstall permanently, also delete the Callback URL registration in the Merchant Portal.

## Upgrade

Upload the new ZIP via **Plugins → Add New Plugin → Upload Plugin** and confirm **Replace current with uploaded**.


---

# 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/woocommerce/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.