> 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.md). # PrestaShop SEB E-commerce Payment Gateway module for PrestaShop — overview This module adds SEB E-commerce Payment Gateway as a payment option to your PrestaShop checkout. **How it works:** at checkout your customer selects the payment option (*Online Payment*), an order is created in the state *Awaiting payment confirmation*, and the customer is redirected to the gateway's secure hosted payment page. After paying, the customer returns to your shop. The module updates the order state twice: when the customer returns, and authoritatively when the gateway sends a server-to-server callback notification. 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. **Install effort:** installable by a shop administrator from the back office — no developer needed. ## Features | Feature | Supported | | --------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Card payments on the hosted page | ✓ — the card schemes enabled for your shop, configured in the Merchant Portal rather than in the module | | Other payment method types on the hosted page | Bank account (Open Banking) and wallet options (Google Pay, Click to Pay) appear alongside cards, if enabled for your shop | | Checkout types | Standard PrestaShop checkout ✓ | | Automatic order-state sync (callback) | ✓ (two dedicated order states installed: *Awaiting payment confirmation*, *Awaiting payment capture*) | | Refunds | Issue the refund in the Merchant Portal; the module reflects it on the order automatically. There's no refund action in the back office for this payment method | | Pre-authorization (capture later) | ✓ order waits in *Awaiting payment capture* | | Saved cards (one-click payments) | ✓ — optional, off by default. Logged-in customers can save the card they pay with and pay with it later in one click (3-D Secure still applies); saved cards are listed under *My Account → Saved cards*. You never see or store card details — see [Saved cards](/integration/web-plugins/prestashop/configuration.md#saved-cards) | | Subscriptions / recurring payments | ✗ | | Express wallet buttons in your shop | ✗ — not shown in your shop's own checkout; Google Pay and Click to Pay appear as options after redirect, on the gateway's hosted page | | Multi-store / multi-language | Standard PrestaShop mechanisms; not yet certified. Module strings translatable via International → Translations | | Performance | Optional: gateway access tokens use PrestaShop's cache (e.g. Memcached) when enabled | Gateway features beyond this list are available via the [Merchant API](/integration/merchant-api.md) or via the [API Client SDK](/integration/api-client-sdk.md). ## Compatibility | Module version | PrestaShop | PHP | | -------------- | ---------- | ---- | | 1.0.0 | 9.0+ | 8.1+ | The module installs only on PrestaShop 9.0.0 or newer. PHP 8.1 is the minimum PrestaShop 9.0 itself requires. ## Next steps * [Installation](/integration/web-plugins/prestashop/installation.md) * [Configuration](/integration/web-plugins/prestashop/configuration.md) * [Order states & operations](/integration/web-plugins/prestashop/order-lifecycle-and-operations.md) * [Testing & go-live](/integration/web-plugins/prestashop/testing-and-go-live.md) --- # 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.md?ask=&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.