Your Loop wallet works with a range of applications built on the network. This page is for when something goes wrong between your wallet and one of them.

Discover, in your wallet, lists the applications that have integrated Loop as the wallet. You use the wallet you already have, with the assets already in it, rather than creating a separate wallet for each one.

Applications do not appear there on their own. Each one is a partner we have worked with to integrate Loop.

That is a partnership, not a guarantee. Each application is still run by its own organisation, sets its own fees, and answers for what happens inside it. We cannot reverse something you approved there, and we cannot decide on their behalf.

Open an app from Discover or from an address you type yourself, never from a link somebody sent you. Do not install extensions, scripts or "connection tools" that claim to link your wallet to an app.

Before anything else: a connection problem does not mean your assets are gone. Almost every case here turns out to be a connection, a wrong account, or a balance that has not settled yet.

Signing in, connecting the two, approving a connection, depositing, withdrawing, seeing your balance, placing or settling an order, signing something, or reconnecting after signing out.

These have different causes, so knowing which one it is saves you most of the work. Note the exact error message while you are there.

Refresh both sites. Use an up-to-date browser. Sign out and back in through the official Loop site. Check you are on the account and wallet address you expect.

Try a fresh browser session. A privacy setting or content blocker can quietly break the connection flow, and this is a common cause. Turn one off temporarily to test if you need to, then turn it back on.

Never disable your security protections permanently, and never import your wallet credentials into another app to "fix" a connection.

This message does not necessarily mean the two products are incompatible. Refresh both pages and retry on an updated browser first.

If it keeps appearing, send us the full error text, which site showed it, and your browser, device and operating system. Do not go looking for a download or an installer, there isn't one.

Compare the public wallet address shown in Loop with the one shown in the app. If they differ, that is your answer.

The usual cause is signing in a different way than before, with a different email, Google account or passkey, which can put you in a different wallet rather than the one you meant. It can also happen if a new wallet was created instead of restoring the existing one.

If the addresses do not match and you cannot explain why, send us both and we will look. Separate wallets cannot be merged, so it is worth getting this right before moving anything.

Some apps ask for delegation. Temple is one example: when you deposit into it, you grant it limited permission to act for trading and settlement. It does not get control of your wallet, and it cannot move your funds elsewhere.

Delegation problems can show up as failed deposits, stuck orders, unavailable balance or blocked withdrawals. Check in the app whether delegation shows as active, expired or revoked.

Revoking delegation or using an emergency withdrawal can cancel open orders and affect unsettled trades. It is a way out, not a free undo. If you are unsure what it will do in your situation, ask us before you press it.

And never sign a delegation request you did not initiate and cannot explain.

Do not try again while the first attempt is uncertain. Each attempt can be its own transaction with its own fee, and that is how one problem becomes two.

Check the status shown in both Loop and the app, look for a transaction hash, and send us what you find.

Common reasons: a transaction still pending, a trade that has not settled, open orders or delegated holdings, holdings split into pieces that need merging, a display that has not refreshed, or simply a different wallet address connected than you thought.

Refresh both sites and compare the wallet addresses first. That single check resolves most of these.

Read every request before you approve it. A signature can grant permissions even when it shows no transfer.

Do not approve requests from apps you do not recognise, requests opened through a link someone sent you, requests whose details differ from what you intended, or anything presented to you by "support". If you cannot explain what it does, do not sign it.

If the problem is inside the app, its own team is the right place to start, because the record of what happened sits with them.

If the problem is the wallet itself, signing in, your address, your balance, a transfer that did not arrive, that is us.

If you are not sure which it is, write to us anyway and we will tell you.

The public wallet address shown in each app. The transaction hash. The asset and roughly how much. Roughly when. The status each app shows. The exact error message. Your browser, device and operating system. A screenshot with anything sensitive hidden.