> For the complete documentation index, see [llms.txt](https://docs.finpay.id/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.finpay.id/appendix/enumeration/status-list.md). # Status List

No	Name	Description
1	PAID	The process of transferring funds from the payer's account to the merchant's account
2	AUTHENTICATED	3DS authentication success
3	AUTHORIZED	A message sent via an acquirer to a card issuer, asking that funds be reserved in the payer's account for later capture. If the authorization is successful, an authorization ID or code is returned as a receipt. The hold on the funds is generally only valid for a limited period, for example 7 days.
4	PARTIALLY_CAPTURED	The process of transferring funds from the payer's account to the merchant's account partially. The capture must always be preceded by an authorize, and the authorization ID sent with the capture.
5	CAPTURED	The process of transferring funds from the payer's account to the merchant's account. The capture must always be preceded by an authorize, and the authorization ID sent with the capture.
6	PARTIALLY_REFUNDED	A return of funds to the payer from the merchant partially
7	REFUNDED	A return of funds to the payer from the merchant
8	CANCELLED	A cancellation of the payment portion of the transaction, so that no funds are transferred between the payer and the merchant. The transaction is cancelled and is not recorded on the payer's statement.
9	INITIATED	3DS initiation success
10	AUTHENTICATION_INITIATED	3DS payer authentication success
11	REQUEST_INITIATED	Merchant request initiation success
12	FAILURE	The operation was declined or rejected
13	PENDING	The operation is currently in progress or pending processing
14	EXPIRED	The operation is no longer valid

--- # 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.finpay.id/appendix/enumeration/status-list.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.