UNIFY / SUPPORT
Transaction help & recovery
Find transaction steps, support references and safe recovery instructions for a pending swap or bridge.
Find the precise step
- Open History and expand Transaction steps.
- Check whether the record is approval-only, submitted source execution, or verified destination completion.
- Use the explorer links for the recorded chains. A source success alone does not prove delivery.
- Copy the support reference and keep the full transaction hash.
Recover without repeating a transfer
Use Recover moves for an existing bridge. A recovery check reads existing state; it does not send another source transfer. If a source swap finished but its bridge did not, inspect its checkpoint and current wallet balances before proceeding.
Unknown receipt status is not a safe reason to retry. Failed, cancelled and pending moves have different next steps. Recovery availability depends on browser records, authenticated journal access and provider/network availability.
Report a problem privately
Use the form below to send a report directly to the Unify operator. Reports are not published on GitHub or shown to other visitors. Include the networks, tokens, approximate amount, time and exact error. An email is optional; no response deadline or recovery guarantee is made. Do not include seed phrases, private keys, API keys, passwords or session tokens.
Match the next step to the actual status
| What you see | What it proves | What to do next |
|---|---|---|
| No wallet prompt | A route may have failed checks before authorization. | Refresh the quote and check the displayed cause. There may be no transaction hash. |
| Approval only | Spending permission was granted; the asset was not swapped by that approval. | Review balances and get a fresh quote before sending the swap. |
| Source submitted / Check wallet | Submission or confirmation remains uncertain. | Check the exact source hash. Do not repeat an uncertain source transfer. |
| Source confirmed, bridge pending | Source activity is confirmed but delivery is not yet verified. | Use Recover moves and check the destination evidence. |
| Complete / verified destination | The recorded delivery check has confirmed the destination step. | Check the receiving wallet on the correct network and exact token contract. |
Read older history without losing context
Latest 3 moves starts with recent saved routes and approvals. Load older activity expands the feed and reveals the Grid / List switch beside Refresh. Both views display the same loaded records; switching the layout does not submit transactions or change their status.
Ordinary explorer records are labeled Wallet activity. They prove a transaction on their recorded network, not an ultimate bridge destination. Saved routes have Transaction steps and a support reference where available. The eye button can hide the connected address in the interface; it does not erase public transaction history.
Prepare a useful report
- The support reference and source transaction hash, if one exists.
- Source and destination networks; exact token contracts are more useful than tickers.
- The approximate amount, selected provider and route preference.
- Whether a wallet prompt appeared and whether you approved, signed, cancelled or submitted.
- The exact error and its time, with sensitive information removed.
- For bridges, the destination hash or order reference if shown.
Submit through the private form on this page, not a GitHub issue. Keep the returned support reference. There is no published support-response deadline or reimbursement promise. Do not send passwords, seed phrases, API credentials or another person’s private data. File attachments are not accepted.
Common questions
Why is a balance missing after completion?
Check the receiving address, destination network and exact token contract first. Portfolio indexing can lag. A reference valuation or an explorer delay is not by itself evidence that delivery failed.
Can support reverse my transfer?
Do not assume a transfer can be reversed or that support controls your funds. Recovery depends on the specific route state and provider capabilities, not a promise to undo a completed transfer.
What happens if one asset fails in a portfolio move?
Completed legs remain on-chain. Eligible failures before an uncertain submission can allow later assets to continue. An in-flight or uncertain wallet submission requires review instead of an automatic resend.