> For the complete documentation index, see [llms.txt](https://docs.nymcard.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.nymcard.com/get-started/transactions/transaction-lifecycle.md). # Transaction lifecycle nCore platform creates and keeps electronic messages received from the payment card network as an object called transaction. Transaction state changes during their lifecycle depends on whether they are in a temporary state or final state. Temporary and final transactions states are closely related to single-message and dual-message transactions. In dual-message transaction system there are two or more transaction messages requires to complete, for example: * The merchant submits an electronic message containing the information required for an authorization decision at the time or purchase. * Later point in time, the merchant submits another electronic message containing additional data which is required for clearing and settlement. In this scenario, the first message is a **temporary** transaction, which means it can be reversed. The last message is a **final** transaction. Temporary transaction messages, such as authorizations flows in real time from the merchant to the issuer processor and these are handled synchronously. However, the **final** transaction messages are handled asynchronously because these requests can be submitted later. Some transactions, for example a PIN based transactions contain all the information required for authorization and clearing in a single electronic message. These transactions are typically considered as **final** transactions that are handled synchronously. --- # 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.nymcard.com/get-started/transactions/transaction-lifecycle.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.