> 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/cards/card-payment-lifecycle/understanding-initial-and-standing-amounts.md).

# Understanding Initial and Standing Amounts

How the original payment amount can differ from the amount that remains on the transaction later

The **initial amount** is the amount that was first placed on the transaction. The **standing amount** is the amount that is still active when you check the payment later.

#### When the payment was pre-authorised

With a pre-authorisation, the payment can later be completed for less than the original amount, or it can be cancelled before it is completed. In both cases, the standing amount may be lower than the initial amount.

* Example: a hotel authorises €100 at check-in, but only €80 is needed at check-out. The initial amount is €100, and the standing amount becomes €80.

So, in this flow, the standing amount reflects what is left after the final amount has been confirmed or the authorisation has been released.

#### When the payment was final-authorised

With a final-authorisation, the original amount is usually the amount you expect to collect. The standing amount changes only after the payment is reduced by a refund.

* A full refund leaves a standing amount of €0.
* A partial refund leaves a standing amount equal to the remaining balance.

The initial amount always stays the same: it is the amount of the original payment request, not the amount that is left after refunds.


---

# 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/cards/card-payment-lifecycle/understanding-initial-and-standing-amounts.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.