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

# Installation

Install the SEB E-commerce Payment Gateway module for PrestaShop

## Before you start

* PrestaShop 9.0+ (PHP 8.1+ with the cURL extension — standard on virtually all hosting)
* Your SEB E-commerce Payment Gateway credentials at hand (see [prerequisites](/integration/web-plugins.md))
* Back-office administrator access
* Recommended: back up your shop before installing any module

## Install from the module package

1. Download the PrestaShop module ZIP.
2. In the back office, go to **Modules → Module Manager** and select **Upload a module**.
3. Drop the downloaded ZIP into the dialog. PrestaShop installs the module automatically.
4. Verify: the module *SEB E-commerce Payment Gateway* appears in Module Manager under **Payment**, and two new order states exist under **Shop Parameters → Order Settings → Statuses**: *Awaiting payment confirmation* and *Awaiting payment capture*.

![Modules → Module Manager → Upload a module dialog, with the drop zone ready for the module ZIP.](https://1157570179-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FuBDtfypkI85zidcVwaDj%2Fuploads%2F7i9hEhbXUQ1XPinan2sh%2Fps-upload-module.png?alt=media)

![Modules → Module Manager, with a list of uploaded modules, showing the SEB E-commerce Payment Gateway module.](https://1157570179-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FuBDtfypkI85zidcVwaDj%2Fuploads%2FNkOHCF4vP9Wsnb1LhFur%2Fps-upload-module-uploaded.png?alt=media)

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

![Payment → Payment Methods, showing the gateway module row installed and active with its Configure button.](https://1157570179-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FuBDtfypkI85zidcVwaDj%2Fuploads%2FcidbzUhpMS2eZrCC96xd%2Fps-module-installed.png?alt=media)

## Uninstall

1. **Modules → Module Manager** → find the module → **Disable** (stops offering it at checkout), or **Uninstall** to remove it.
2. Uninstalling removes the module's configuration (including credentials) and its internal payment-reference table. Orders, their states, and the two installed order states remain.
3. If you uninstall permanently, also delete the Callback URL registration in the Merchant Portal.

## Upgrade

Upload the new ZIP via **Module Manager → Upload a module**.


---

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