> For the complete documentation index, see [llms.txt](https://docs.verifone.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.verifone.com/functional-specification/confirm_surcharge_incl_description.md). # confirm\_surcharge\_incl\_description Description\ Customer is prompted to confirm the surcharge amount incurred by the transaction. If no surcharge is to be applied to the transaction, the surcharge confirmation screen shall not be presented. When `Merchant.SurchargeApplicationBehavior` is set to *Card product-based surcharging with Merchant-override capability*, the surcharge alert is displayed at the beginning of the transaction. If the merchant decides that the transaction is not subject to surcharge, no surcharge will be added and the surcharge confirmation screen shall not be presented. When `Merchant.PreauthCompletionSurchargeType` is set to apply surcharge during completion, a disclaimer will be prompted indicating that this transaction may be subject to surcharge at completion during the pre-authorisation flow. Customer Action\ Selecting Accept will continue the transaction. Selecting Cancel will abort the transaction. Per configuration, the surcharge confirmation prompt will automatically time out after a set time. In normal (non-accessible) mode, the surcharge may be automatically accepted, allowing the transaction flow to proceed, *or* be automatically declined, resulting in cancellation of the transaction. In accessible mode, and when configured to beep and re-prompt, the terminal will beep periodically while awaiting customer decision to proceed. --- # 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.verifone.com/functional-specification/confirm_surcharge_incl_description.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 `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.