> 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/opencart.md). # OpenCart SEB E-commerce Payment Gateway extension for OpenCart — overview This extension adds SEB E-commerce Payment Gateway as a payment method to your OpenCart 4 store. **How it works:** at checkout your customer selects the payment method (*Online Payment*) and confirms the order; the order is created and the customer is redirected to the gateway's secure hosted payment page. After paying, the customer returns to your store. The extension updates the order status 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 store's database. **Install effort:** installable by a store administrator from the admin panel — 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 extension | | Other payment method types on the hosted page | Bank account (Open Banking) alongside cards; depends on your shop's configured payment methods | | Checkout types | Default OpenCart 4 checkout ✓ | | Automatic order-status sync (callback) | ✓ | | Order totals passed to the gateway | Products, tax, shipping, handling/low-order fees, coupons, reward points, store credit | | Refunds | Issue the refund in the Merchant Portal; the extension reflects it on the order automatically. There's no refund action in the admin panel for this payment method | | Pre-authorization (capture later) | ✓ order stays *Pending* with an explanatory comment until captured | | 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 → Payment Methods*. You never see or store card details — see [Saved cards](/integration/web-plugins/opencart/configuration.md#saved-cards) | | Subscriptions / recurring payments | ✗ | | Express wallet buttons in your store | ✗ your own checkout shows only the single *Online Payment* radio option; Google Pay/Click to Pay appear only after redirect, on the gateway's hosted page | | 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 | Extension version | OpenCart | PHP | | ----------------- | -------- | ---- | | 1.0.0 | 4.1+ | 8.1+ | The extension targets the OpenCart 4 architecture and does not run on OpenCart 3.x. PHP 8.1 is the minimum OpenCart 4.1 itself requires. ## Next steps * [Installation](/integration/web-plugins/opencart/installation.md) * [Configuration](/integration/web-plugins/opencart/configuration.md) * [Order statuses & operations](/integration/web-plugins/opencart/order-lifecycle-and-operations.md) * [Testing & go-live](/integration/web-plugins/opencart/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/opencart.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.