> For the complete documentation index, see [llms.txt](https://help.trybeans.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.trybeans.com/liana/redemption/pending-debits.md).

# Pending Debits

### What is a pending debit?

A pending debt occurs when the customer tries to redeem their points. Immediately after redeeming their point during a purchase, a debit is created with the status `pending` . This means that the debt is not yet fully recorded into the customer account's history. Once the customer completes the order the debit status is then moved from `pending` to `committed` and the transaction will appear in the history. \
\
The `pending` state exists to prevent customers from gambling with the system. For example, a customer could try to redeem multiple orders at the same time and get more discounts than they are allocated. \
\
The `pending` debits can be seen in the admin dashboard as explained in the screenshot below. 

![](/files/-M2ncg3r56vnMHYERJEA)

### How to cancel a pending debit

If the customer cancels their redemption, the `pending` debit is automatically canceled and then the customer gets access to their full balance. 

In case the customer exit without completing the order. the `pending` debit is automatically canceled within 48 hours. 


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://help.trybeans.com/liana/redemption/pending-debits.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.