---
title: Overview
description: Choose the right wallet docs page for embedded wallet integration,
  approval flow behavior, and troubleshooting.
source_url:
  html: https://thru.org/docs/wallet/overview/
  md: https://thru.org/docs/wallet/overview.md
---

# Overview

Use this section when you are integrating a Thru web app with the hosted embedded wallet at `wallet.thru.org`.

## Start Here

- [Embedded Wallet Integration](https://thru.org/docs/wallet/embedded-wallet-integration.md): Set up the wallet in a web app, choose the right package layer, and wire \`connect()\` plus \`signTransaction()\` correctly.
- [Approval and Signing](https://thru.org/docs/wallet/approval-and-signing.md): Understand the request lifecycle for connect and transaction signing, including cached reconnects, approval modals, and dApp UX expectations.
- [Troubleshooting](https://thru.org/docs/wallet/troubleshooting.md): Debug wallet integration failures such as origin issues, stalled approval flows, malformed transaction payloads, and transactions that never reach explorer.

## Choose The Right Page

| If your task is… | Open this page | Then open… |
| - | - | - |
| Add wallet connect to a React dApp | [Embedded Wallet Integration](https://thru.org/docs/wallet/embedded-wallet-integration.md) | [`@thru/wallet`](https://thru.org/docs/sdks/web-packages/wallet.md) with `@thru/wallet/react` |
| Add wallet connect to a non-React dApp | [Embedded Wallet Integration](https://thru.org/docs/wallet/embedded-wallet-integration.md) | [`@thru/wallet`](https://thru.org/docs/sdks/web-packages/wallet.md) |
| Explain what the user sees during approval | [Approval and Signing](https://thru.org/docs/wallet/approval-and-signing.md) | [`@thru/wallet`](https://thru.org/docs/sdks/web-packages/wallet.md) protocol exports |
| Debug why a request or transaction flow failed | [Troubleshooting](https://thru.org/docs/wallet/troubleshooting.md) | [Explorer MCP](https://thru.org/docs/api-ref/explorer-mcp/overview.md) |

## What This Section Assumes

- you are integrating the hosted wallet iframe rather than building a custom wallet
- your web app can reach `https://wallet.thru.org/embedded`
- you will use the wallet to approve connection and sign serialized transactions
- you will use [`@thru/sdk`](https://thru.org/docs/sdks/web-packages/sdk.md) or another client to actually submit signed transactions

## Open Next

- [Embedded Wallet Integration](https://thru.org/docs/wallet/embedded-wallet-integration.md) for the recommended integration path
- [Approval and Signing](https://thru.org/docs/wallet/approval-and-signing.md) before you design wallet status UI
- [Troubleshooting](https://thru.org/docs/wallet/troubleshooting.md) when the wallet flow is present but not behaving as expected