Add privacy-safe, paginated analytics with demo/on-chain separation

[emrekayat]

Context

Public analytics returns recent payment and usage records directly, including query text/URLs and optional payer keys. Totals combine records without a clear distinction between demo and real settlement.

Scope

Define a privacy-safe analytics API and update the dashboard.

Acceptance criteria

• Separate demo-paid, verified, settled, and failed counts/volume.
• Only count authoritative settled evidence as on-chain paid volume.
• Redact or hash payer addresses by default and never expose secrets/payment payloads.
• Avoid returning raw query text or scrape URLs from public aggregate endpoints.
• Add cursor pagination and validated limits for detailed history.
• Add configurable retention for sensitive usage fields.
• Return stable typed analytics schemas from the shared package.
• Update the dashboard with explicit demo versus settled labels.
• Tests cover aggregation, redaction, pagination boundaries, retention, and unauthorized detail access.
• Document public/private analytics surfaces.

Out of scope

Claiming demo values as real Stellar volume.

Verification

Use mixed fixtures to prove public responses contain no raw sensitive query, URL, or full payer address.

[Samuel-21-eng]

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

Hi maintainer, I've read through the description and I'm confident that I can get this done

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Samuel-21-eng to this issue.

[drips-wave]

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

🧑‍💻 @Samuel-21-eng: 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 🌊