> 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/getting-started/release-notes.md).

# Release notes

Learn about the latest updates to our APIs, web plug-ins, API SDKs, and iOS and Android SDKs.

{% hint style="info" %}

#### New Service – Implementation and Migration Phase

The E-commerce Payment Gateway is currently in the implementation and merchant migration phase.

During this phase, functionality is being progressively introduced and made available for integration and testing in the Sandbox environment. Release Notes will focus on new functionality, improvements and changes relevant to onboarding, integration, testing and migration.

Once the Service transitions to regular operation, Release Notes will follow the standard process described in the Release Policy.
{% endhint %}

<details>

<summary>[Month YYYY] Release</summary>

> Status: Release Candidate\
> Planned release: \[DD Month YYYY]\
> Action required: \[Yes / No]

### What’s new

#### \[Feature name]

**Area:** \[Merchant Portal / Hosted Checkout / Payments / API / SDK / Plug-in]\
**Impact:** No Action Required\
**Sandbox:** \[Available / Not applicable]

\[Short description of what is new and why it is useful.]

\[Link to documentation]

#### \[Feature name]

**Area:** \[Component]\
**Impact:** Awareness Required\
**Sandbox:** \[Available / Not applicable]

\[Short description of the change.]

### Improvements & fixes

* \[Component] — \[Short description of improvement or fix.]
* \[Component] — \[Short description.]
* \[Component] — \[Short description.]

### Action required

{% hint style="warning" %}

{% endhint %}

#### \[Change name]

**Area:** \[API / SDK / Plug-in / Configuration]\
**Deadline:** \[DD Month YYYY]\
**Sandbox:** \[Available from DD Month YYYY]

\[Short explanation of what is changing and what you need to do.]

### API, SDK & plug-in updates

| Component  | Version           | Update                               |
| ---------- | ----------------- | ------------------------------------ |
| API        | `vX.X.X`          | \[No action / Action required]       |
| Mobile SDK | `vX.X.X`          | \[Optional / Recommended / Required] |
| Plug-ins   | `Name and vX.X.X` | \[Optional / Recommended / Required] |

{% hint style="info" %}
Release Candidate scope and planned dates may change. This page will be updated if the release plan changes.
{% endhint %}

</details>


---

# 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/getting-started/release-notes.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.