Add wallet-safe pay-to address display and validation copy

[emrekayat]

Why this matters

Before an agent or reviewer pays for a query, the UI should make the configured pay-to address visible in a safe, inspectable way without exposing secrets or implying custody.

Scope

Add a compact pay-to address display near paid-query evidence or provider pricing:

• shortened Stellar address with copy button;
• clear testnet label when configured for Stellar testnet;
• warning state when pay-to address is missing;
• no private key or payment header display.

Suggested files:

• apps/web/src/App.tsx
• apps/api/src/routes/public.ts if a safe config field needs to be exposed;
• packages/shared/src/schemas.ts if typing is needed.

Acceptance criteria

• UI shows a shortened pay-to public address only, never a secret key.
• Missing pay-to address renders a warning, not a blank state.
• Copy button copies the full public address.
• Test covers configured and missing address states.
• Existing payment flow remains unchanged.

Wave complexity

High - improves payment transparency and reviewer trust before paid-query execution.

[TheWeirdDee]

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

I'd like to work on this issue because payment transparency is important for both user trust and reviewer confidence. Displaying the pay-to address in a clear, wallet-safe manner helps users verify where payments are directed while ensuring sensitive information is never exposed.

I have experience building React/TypeScript interfaces, implementing secure data-display patterns, and creating user-friendly payment and wallet-related UI components. I'm comfortable adding address formatting and copy-to-clipboard functionality, handling missing-configuration states gracefully, integrating safe configuration data from backend APIs, and writing tests that verify both configured and warning scenarios. I can implement the feature while ensuring no private keys, payment headers, or other sensitive information are ever displayed and that the existing payment flow remains unchanged.

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

[Menjay7]

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

Hi! I’m a full-stack developer with a strong blockchain background. I’d love to handle this issue and can deliver a clean, reliable solution. Kindly assign it to me.

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

[Silver36-ship-it]

@Silver36-ship-it has applied to work on this issue as part of the Stellar Wave Program's 6th wave.

I would love to work on this professionally, please assign it to me

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Silver36-ship-it to this issue.

[drips-wave]

Congratulations, @TheWeirdDee! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on June 30, 2026.

🧑‍💻 @TheWeirdDee: 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 🌊