> For the complete documentation index, see [llms.txt](https://docs.brokvix.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.brokvix.com/crm-admin/platform-configuration/configure-financial-approval-flows/overlimit-deposits/overlimit-deposits-authoritative.md). # Authoritative approval **For:** Finance and Risk operators handling a PSP-confirmed deposit hold when no applicable Overlimit Deposits workflow is live. ## When this route starts The PSP confirms a successful deposit, automatic credit is held by the PSP-account ceiling or a brand daily amount/count limit, and **no live applicable workflow** owns the hold. A no-match rule in a live workflow uses that workflow's fallback chain instead. ## Current decision model The transaction appears in **Deposit Approval — Authoritative**. Risk and Finance may see the same eligible transaction list, subject to their access. These are two views of **one transaction-level decision**; they are **not** a Risk-first, Finance-second chain. The deciding operator also needs transaction approval access. Approval credits the PSP-confirmed amount once. If policy requires two distinct human approvals for every overlimit deposit, this route does **not** satisfy that requirement. Configure and test an explicit two-level [Overlimit Deposits workflow](/crm-admin/platform-configuration/configure-financial-approval-flows/overlimit-deposits/overlimit-deposits-workflow.md) instead. Rejection does not establish that a confirmed PSP payment was refunded. Follow the refund/manual settlement instructions on the transaction and verify provider reconciliation. Return to the [overlimit deposit overview](/crm-admin/platform-configuration/configure-financial-approval-flows/overlimit-deposits.md) for route selection. --- # 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 following URL with the `ask` and `goal` query parameters: ``` GET https://docs.brokvix.com/crm-admin/platform-configuration/configure-financial-approval-flows/overlimit-deposits/overlimit-deposits-authoritative.md?ask=&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 `build a script that syncs our docs to a CMS` 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.