> For the complete documentation index, see [llms.txt](https://wiki.delos.financial/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://wiki.delos.financial/additional-information/transaction-slas-and-statuses.md). # Transaction SLAs and statuses ### Timeframes \ **Application approval:** for corporations it’s 10 business days - this is the upper limit, however we try to fit within 5-7 business days; for Individuals it’s 2-3 business days. However, this depends on our and our partners' compliance, hence some cases may take longer. \ **Counterparty approval:** from several minutes up to several hours in case of additional compliance check \ **Exchanges Fiat <-> DLT** – from several minutes up to several hours \ **Exchanges Fiat <-> Fiat** – from an hour up to 24 hours. \ **DLT deposits and withdrawals** – from several minutes up to several hours \ **SWIFT** – 1-4 business days \ **Fedwire** – 1 business day \ **ACH** – 1 business day \ **SEPA** – 1-2 business days \ Note that in some exceptional cases it can take longer, but we will definitely inform you of the reasons and further procedures. ### Transaction statuses \ **Pending** - transaction has been ordered but not yet processed, usually in happens automatically within a short time period \ **In progress** - transaction is being processed by the correspondent bank, if the timeframes mentioned above passed, please contact Yazan. \ **Success** - transaction is credited to the destination account. \ **Cancelled** - transaction will not be processed, funds returned. If you did not initiate cancelling, please contact Yazan. --- # 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://wiki.delos.financial/additional-information/transaction-slas-and-statuses.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.