> For the complete documentation index, see [llms.txt](https://docs.zert.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.zert.com/integration-example/check-transaction-status.md).

# Check transaction status

After submitting a wallet-signed artifact, you can verify on-chain status using the transaction status endpoint. Supports EVM, Solana, and Bitcoin.

## When to use

* After `POST /swap/{swapId}/signing` leads to a broadcast transaction hash in your flow.
* To poll until the transaction is `confirmed` or `failed`.
* To show users real-time status (e.g. pending → confirmed).

## Request

**Endpoint:** `GET /status/transaction/{txHash}`\
**Required query:** `chainRef` — chain where the transaction was submitted.

```bash
curl -X GET 'https://api.gateway.zert.com/api/v1/status/transaction/0x123...abc?chainRef=eth-mainnet' \
  -H 'Authorization: Bearer YOUR_API_KEY'
```

Use the correct `chainRef` for the chain of the tx (e.g. `eth-mainnet`, `polygon-mainnet`, `solana-mainnet`, `bitcoin`).

## Response

```json
{
  "data": {
    "txHash": "0x123...abc",
    "chain": "eth-mainnet",
    "status": "confirmed",
    "confirmedAtMs": 1745400000000
  },
  "meta": { "requestId": "...", "timestamp": "..." }
}
```

## Status values

| Status      | Description                  |
| ----------- | ---------------------------- |
| `pending`   | Submitted, not yet confirmed |
| `confirmed` | Confirmed on chain           |
| `failed`    | Transaction failed           |

## Polling example

Poll every few seconds until `status` is `confirmed` or `failed`, or until a timeout:

1. Call `GET /status/transaction/{txHash}?chainRef=...`.
2. If `data.status` is `confirmed` or `failed`, stop.
3. If `pending`, wait (e.g. 3–5 seconds) and repeat.
4. Treat `404` as not indexed or not found yet, and retry only if that matches your expected flow.

See [Get Transaction Status](https://docs.zert.com/api-reference/status-and-tracking/get-transaction-status.md) for full parameters, response fields, and error codes.


---

# 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.zert.com/integration-example/check-transaction-status.md?ask=<question>&goal=<user_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.
