> For the complete documentation index, see [llms.txt](https://docs.payments.thalescloud.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.payments.thalescloud.io/dynamic-cvv/implement-dynamic-cvv2-control/handle-deferred-authorizations.md). # Handle deferred authorizations ### Overview Some merchants can submit **two authorizations** for a single purchase when they can’t confirm the final amount at checkout (for example, hotel reservations). A typical pattern is: * A **zero-amount authorization** to validate the card. * A second authorization for the **final amount**, submitted later (sometimes days or weeks after the first authorization). ### Why the second authorization can fail In these merchant flows, the merchant may reuse the same **Dynamic CVV2** for the second authorization. By default, D1 invalidates (discards) a **Dynamic CVV2** after the first verification (successfull or not). As a result, the second authorization is then declined if the merchant reuses the same **Dynamic CVV2** that D1 has already discarded. ### How D1 supports deferred authorizations To support deferred authorization scenarios, D1 can allow the same **Dynamic CVV2** to be reused for a limited number time, this will be allowed only for a specific category of merchant. D1 evaluates whether the **Dynamic CVV2** can be reused based on the **Merchant Category Group** configured during **D1 onboarding** for the issuer. ### Configuration options The following parameters are configurable: * **Maximum reuse count**: how many times the same **Dynamic CVV2** can be reused. * **Dynamic CVV2 validity window**: the overall period during which the **Dynamic CVV2** remains eligible for reuse. * **Merchant Category Group**: list of MCC granted for multiple reuse of Dynamic CVV2 ### Merchant binding D1 also tracks the merchant identifier (using `merchantId`) so a **Dynamic CVV2** can be reused **only** by the merchant that initiated the first authorization. --- # 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://docs.payments.thalescloud.io/dynamic-cvv/implement-dynamic-cvv2-control/handle-deferred-authorizations.md?ask=&goal= ``` `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.