> 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/testing-and-go-live.md).

# Testing & go-live

End-to-end test flow and go-live checklist for the SEB E-commerce Payment Gateway module for PrestaShop

## Test in Sandbox

Prerequisites: module [installed](/integration/web-plugins/prestashop/installation.md) and [configured](/integration/web-plugins/prestashop/configuration.md) with Environment = *Sandbox*, sandbox credentials, callback URL registered in the Merchant Portal at <https://merchantportal.ecommerce.sebgroup.com>.

For test cards and magic values, see [Sandbox test data](/guides/sandbox.md).

The end-to-end test script:

1. **Place an order** in the storefront and pick *Online Payment*; you are redirected to the SEB E-commerce Payment Gateway payment page. The order appears in the back office as *Awaiting payment confirmation*.
2. **Pay with a test card:** use the test card number for successful authorization, any cardholder name, any valid future expiry date (e.g. 12/28) and any 3-digit CVV (e.g. 123). You return to the shop and reach the order confirmation page.
3. **Verify the order**: state is *Awaiting payment capture* — the sandbox only authorizes, it does not capture automatically, so this is the normal resting state after step 2 (or *Payment accepted*, if your shop settings capture immediately); the transaction ID matches the payment in the Merchant Portal.
4. **Verify the callback**: repeat, but close the browser right after paying. The order must still update within a few minutes — otherwise the callback URL isn't reachable.
5. **Capture** (pre-authorization shops): capture in the Merchant Portal; the order must move to *Payment accepted*.
6. **Fail one on purpose:** either cancel on the payment page, or pay with the test card for declined authorization, which always fails authorization. The order must be *Canceled* and your cart restored at checkout.

![The storefront checkout payment step with Online Payment selected, and beside it the back-office order list after step 5 showing the order in Payment accepted.](https://1157570179-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FuBDtfypkI85zidcVwaDj%2Fuploads%2Fp60Kgga9Mz6hT7ysZuRJ%2Fps-checkout-and-orders.png?alt=media)

## Go-live checklist

* [ ] Sandbox script fully passed
* [ ] Live OAuth2 credentials obtained from the Merchant Portal → **Settings → Shop Settings → Technical Information**
* [ ] **Environment** switched to *Live*, credentials saved
* [ ] Callback URL registered for the live shop; `/module/egwcheckout/callback` reachable from outside (no cache/WAF block)
* [ ] Title/Description reviewed in all shop languages (International → Translations for module strings)
* [ ] One real low-value order: paid → verified

For support: module version, PrestaShop version, order reference, transaction ID, and relevant entries from **Advanced Parameters → Logs** → SEB support.


---

# 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/testing-and-go-live.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.