Web: Refund panel does not notice a wallet connected after the modal is opened

[mallison031]

Repo context. accensa-app is the off-chain half of Accensa — the merchant back-office for x402 sellers on Stellar. Three workspace packages matter: apps/web (Next.js dashboard and the indexer at src/app/api/sync), packages/sdk (@accensa/sdk), and apps/demo-merchant. The Soroban contracts live in accensa-contracts.

🟢 Unblocked. Small, self-contained fix in one component.

Problem

components/refund-panel.tsx reads wallet status exactly once, in an effect with an empty dependency array:

useEffect(() => {
  let live = true;
  void readStatus().then((status) => {
    if (live) setMerchant(status.kind === 'connected' ? status.address : null);
  });
  return () => { live = false; };
}, []);

If no wallet is connected at that moment, merchant stays null and the panel renders "Connect a Stellar wallet to issue refunds" permanently. A merchant who reads that message, connects Freighter, and comes back finds the same message — the panel never re-checks.

The only way out is to close the modal and reopen it, which is not signposted anywhere. The message tells the user exactly what to do and then ignores them doing it.

What to build

Re-read wallet status when it can have changed.

1. Re-check on a trigger the user controls at minimum — a "Check again" affordance next to the connect prompt is the smallest honest fix.
2. Prefer reacting to the wallet itself if practical. Look at what lib/freighter.ts exposes; if connection state can be observed rather than polled, that is the better answer. Do not add a polling loop against the extension without saying why in the PR.
3. Keep the existing live guard. The unmount-safety pattern is correct and should survive the change.

Out of scope: initiating the wallet connection from inside the refund panel. Connecting is the login flow's job.

Acceptance criteria

• A merchant who connects a wallet while the payment modal is open can reach the refund flow without reopening it.
• No state is written after unmount.
• The connect prompt tells the user what to do after connecting.
• pnpm lint passes in apps/web.
• pnpm test passes, including new tests covering this change.
• pnpm build succeeds for apps/web.
• PR description includes Closes #<this issue>.

Contact & Support

• Telegram
• Discord
• SUPPORT.md — contribution help, Wave process, and the full list of channels

[Datanyra]

@Datanyra has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

Hi Maintainer, I would love to work on this issue.... please assign

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Datanyra to this issue.

[Uchechukwu-Ekezie]

@Uchechukwu-Ekezie has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

Please can i get assigned to this issue

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Uchechukwu-Ekezie to this issue.

[drips-wave]

Congratulations, @Uchechukwu-Ekezie! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on August 31, 2026.

🧑‍💻 @Uchechukwu-Ekezie: Please resolve the issue such that the repo's maintainers have enough time to review your contribution before the due date. You'll earn Points for completing the issue on-time, which will make you eligible for a share of the Stellar Wave Program's reward pool.

Warning

When opening a PR, please link it to this issue to ensure it gets tracked accurately. Points are awarded when this issue is marked as completed by the maintainer.

🤠 Repo maintainers: Please keep an eye on the contributor's progress and review their work before the due date. You can manage this issue, including adjusting its complexity and points, here.

🌊 Happy Wave 🌊

[DeFex-lab]

@DeFex-lab has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

Hi Maintainer! I’m interested in contributing to this task and can work toward delivering a clean solution on time.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @DeFex-lab to this issue.

[Oluwasuyi-Oluwatimilehin-Daniel]

@Oluwasuyi-Oluwatimilehin-Daniel has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

Hello @maintainer, I’d like to work on this issue. I have experience handling similar tasks and can start immediately. And I will deliver at the shortest possible time.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Oluwasuyi-Oluwatimilehin-Daniel to this issue.

[Joyee730]

@Joyee730 has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

Maintainer please kindly assign me ,

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Joyee730 to this issue.

[drips-wave]

Congratulations, @Joyee730! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on August 31, 2026.

🧑‍💻 @Joyee730: Please resolve the issue such that the repo's maintainers have enough time to review your contribution before the due date. You'll earn Points for completing the issue on-time, which will make you eligible for a share of the Stellar Wave Program's reward pool.

Warning

When opening a PR, please link it to this issue to ensure it gets tracked accurately. Points are awarded when this issue is marked as completed by the maintainer.

🤠 Repo maintainers: Please keep an eye on the contributor's progress and review their work before the due date. You can manage this issue, including adjusting its complexity and points, here.

🌊 Happy Wave 🌊