> 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.md).

# Web-Plugins

SEB E-commerce Payment Gateway e-shop plugins — supported platforms

Accept payments through SEB E-commerce Payment Gateway in your online shop without writing code. A plugin adds the gateway as a payment method to your shop platform: at checkout your customer is redirected to a secure hosted payment page, pays, and returns to your shop — the plugin keeps your order statuses in sync automatically. Card details are entered only on the hosted payment page; they are never sent to, processed by, or stored on your server or in your shop's database.

## Supported platforms

| Platform    | Platform versions                             |
| ----------- | --------------------------------------------- |
| WooCommerce | WordPress 6.7+ · WooCommerce 10.1+ · PHP 8.3+ |
| Magento 2   | Magento Open Source 2.4.8+ · PHP 8.3+         |
| PrestaShop  | 9.0+ · PHP 8.1+                               |
| OpenCart    | 4.1+ · PHP 8.1+                               |

All four plugins are published by SEB and available for download at the [Distribution](/integration/web-plugins/distribution.md) page.

Not on one of these platforms? Integrate directly with the SEB E-commerce Payment Gateway API — see the [Merchant API](/integration/merchant-api.md) documentation — or use the [API Client SDK](/integration/api-client-sdk.md).

## Plugin, SDK, or API — which path?

* **Plugin** — you run one of the shops above and want payments working today with configuration, not code. Choose this unless you have a custom-built shop.
* **Server-side SDK** — you have a custom shop or backend and a development team; you want typed API access without writing HTTP plumbing.
* **Direct API** — full control, any language, or platforms without an SDK.

## Before you install any plugin

You need three things, all from the same places regardless of platform:

1. **A merchant agreement with SEB**, and access to the Merchant Portal at <https://merchantportal.ecommerce.sebgroup.com>.
2. **Your shop credentials** — OAuth2 Client ID and Client Secret from the Merchant Portal → **Settings → Shop Settings → Technical Information**. Sandbox and Live have separate credential pairs.
3. **Administrator access** to your shop platform's admin panel (and for Magento 2, a developer with server access).

Every plugin has a **Sandbox environment** — test with it first. Switching to Live is one setting plus your live credentials: there is nothing to edit in files, and no environment-specific values to obtain beyond the credential pair. Each platform guide ends with a go-live checklist.


---

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