> 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/payment-methods/pay-by-bank/refunds.md).

# Refunds

The SEB Ecommerce Payment Gateway supports automated refunds for eligible **Pay by Bank** transactions.

Refunds can be initiated through either the **Merchant Portal** or the **Merchant API**. Both channels use the same refund service and follow the same business rules, validation, and eligibility requirements.

***

### Supported Refund Features

| Feature                       | Availability |
| ----------------------------- | ------------ |
| Full Refund                   | Supported    |
| Partial Refund                | Supported    |
| Multiple Partial Refunds      | Supported    |
| Merchant Portal Initiation    | Supported    |
| Merchant API Initiation       | Supported    |
| Customer Authentication (SCA) | Not Required |

***

### Refund Eligibility

A Pay by Bank transaction is eligible for an automated refund when all of the following conditions are met:

* The original payment was settled to your **SEB settlement account**.
* The refund is initiated within the supported refund period (180 days from the original payment).
* The refund is returned to the **original payer**.
* The total refunded amount does not exceed the remaining refundable amount of the original payment.

{% hint style="warning" %}
For SEPA payments where instant processing fails, verify that the original payment has been credited to your SEB settlement account before initiating a refund. Initiate the refund only after the funds are available. Otherwise, the refund transaction may fail.
{% endhint %}

{% hint style="warning" %}
If settlement is made to an account held with another bank, automated refunds are not available through the SEB Ecommerce Payment Gateway. In this case, refunds must be processed outside the Pay by Bank service.
{% endhint %}

### Refund Processing

Every refund request is validated before processing. The gateway verifies that the original payment exists and is eligible for refund, that the refund period has not been exceeded, that the requested amount does not exceed the remaining refundable balance, and that no conflicting refund request is currently being processed. If any validation fails, the refund request is not accepted.

If the refund request is accepted, the amount is returned to the original payer’s bank account, and the refund status is reflected in the Merchant Portal and via the API. Each transaction carries a unique reference identifier to ensure traceability and reconciliation.

### Merchant Recommendations

Before initiating a refund, verify that:

* The original payment is eligible for refund.
* The requested refund amount does not exceed the remaining refundable balance.
* The refund is initiated within the supported refund period.
* The original payment was settled to your SEB settlement account.
* Refund functionality has been enabled for your merchant account.

For automated integrations, we recommend validating refund eligibility before submitting the refund request.

### Common Reasons Why a Refund Cannot Be Processed

A refund request may not be accepted if:

* The original payment cannot be identified.
* The payment is no longer eligible for refund.
* The refund period of **180 days** has expired.
* The requested refund amount exceeds the remaining refundable balance.
* Another refund request is currently being processed.
* The payment was not settled to the merchant's SEB settlement account.


---

# 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/payment-methods/pay-by-bank/refunds.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.