> 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/payment-statuses.md).

# Payment Statuses

The gateway returns the current status of every Pay by Bank payment throughout its lifecycle. Always use the payment status received from the gateway – via callback notifications or the API – to determine the next action in your order fulfilment process.

Pay by Bank payments are account-to-account payments and use a simpler status model than card payments: the Authorized and Captured statuses do not apply. A Pay by Bank payment is considered paid when it reaches the Settled status.

#### Statuses

<table><thead><tr><th width="135" valign="top">Status</th><th valign="top">Description</th><th valign="top">Recommended Merchant Action</th></tr></thead><tbody><tr><td valign="top">Initialized</td><td valign="top">The payment has been created and the customer is selecting a bank or completing authentication and payment authorization.</td><td valign="top">Wait for the final payment notification. Do not fulfil the order.</td></tr><tr><td valign="top">Settled</td><td valign="top">The payment has been completed and the funds have been transferred. This is the “paid” status for Pay by Bank.</td><td valign="top">Proceed with order fulfilment. Store the payment reference for reconciliation.</td></tr><tr><td valign="top">Failed</td><td valign="top">The payment could not be completed – for example, due to a technical issue or the bank declining the payment.</td><td valign="top">Inform the customer with a clear message and allow another payment attempt or payment method.</td></tr><tr><td valign="top">Cancelled</td><td valign="top">The payment was cancelled before completion – by the customer or by the merchant.</td><td valign="top">Return the customer to checkout and allow another payment method.</td></tr><tr><td valign="top">Abandoned</td><td valign="top">A final status: the payment was initiated but never completed – the customer left the flow or the allowed time window passed.</td><td valign="top">Create a new payment if the customer wishes to continue. Do not reuse the payment.</td></tr><tr><td valign="top">Refunded</td><td valign="top">The payment has been refunded in full or in part after successful completion.</td><td valign="top">Update the order and refund status accordingly.</td></tr></tbody></table>

{% hint style="info" %}
Refund processing follows its own lifecycle (e.g., Processing, Completed, Reverted). When a refund reaches Completed, the payment status changes to Refunded. If a refund is reverted, the payment status may return to Settled, provided no other completed refunds remain.
{% endhint %}


---

# 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/payment-statuses.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.
