> 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.md). # WooCommerce SEB E-commerce Payment Gateway plugin for WooCommerce — overview This plugin adds SEB E-commerce Payment Gateway as a payment method to your WooCommerce store. It works with both the classic checkout and the WooCommerce Blocks checkout. **How it works:** at checkout your customer selects the payment method (default label: *Online Payment*) and is redirected to the gateway's secure hosted payment page. After paying, the customer returns to your store. The plugin updates the order status twice: immediately when the customer returns, and authoritatively when the gateway sends a server-to-server callback notification to your store. 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 WordPress database. **Install effort:** installable by a store administrator from the WordPress admin — 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 plugin | | 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 | Classic checkout ✓ · Blocks checkout ✓ | | Automatic order-status sync (callback) | ✓ | | Refunds | Issue the refund in the Merchant Portal; the plugin reflects it on the order automatically. There's no Refund button in WooCommerce itself | | Pre-authorization (capture later) | ✓ order goes *On hold* until captured | | Saved cards (one-click payments) | ✓ — optional, off by default; classic and Blocks checkout. 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 → Payment methods*. You never see or store card details — see [Saved cards](/integration/web-plugins/woocommerce/configuration.md#saved-cards) | | Subscriptions / recurring payments | ✗ | | Express wallet buttons in your store (Apple Pay / Google Pay) | ✗ — not shown in your store's own checkout; Google Pay and Click to Pay appear as options after redirect, on the gateway's hosted page | | Multi-currency | Order currency is passed to the gateway; currencies must be enabled in your SEB agreement | | Translations shipped | English, Latvian | 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 | Plugin version | WordPress | WooCommerce | PHP | | -------------- | --------- | ----------- | ---- | | 1.0.0 | 6.7+ | 10.1+ | 8.3+ | These are the minimum versions the plugin enforces at activation. PHP 8.3 is required. ## Next steps * [Installation](/integration/web-plugins/woocommerce/installation.md) * [Configuration](/integration/web-plugins/woocommerce/configuration.md) * [Order statuses & operations](/integration/web-plugins/woocommerce/order-lifecycle-and-operations.md) * [Testing & go-live](/integration/web-plugins/woocommerce/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/woocommerce.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.