Security: payment tokens in links/deeplinks may leak via referrers or logs

[Cedarich]

Problem
Deep links or URL-based payment tokens in mobile and web may expose tokens via referrers or logs if not properly scoped/expired.

Evidence

• Payments by link/QR are core to the product; token lifecycle policies are unclear.

How to reproduce

1. Generate a payment link and inspect whether the token appears in referrer headers or unmasked logs when used.

Suggested fix

• Use one-time tokens or short-lived tokens for payments; avoid embedding secrets in query params when possible.
• Ensure server-side rotation and token revocation and sanitize logs from tokens.

Files to check

• mobile/src/deeplink or frontend link handlers
• backend token creation code

[Mhidesav]

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

Hi
I would like to work on this issue please

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

[omosvico]

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

Hi maintainer, can this task be assigned to me?

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

[obafemimathew01-hue]

@obafemimathew01-hue has applied to work on this issue as part of the Stellar Wave Program's 7th wave.

Hi Maintainer,

I'd like to work on this issue.

I reviewed the report and agree that payment tokens embedded in links or deep links can create security risks if they are exposed through referrer headers, analytics systems, application logs, screenshots, or shared URLs. I'll audit the token generation, storage, transmission, and redemption flow to determine whether sensitive tokens are unnecessarily exposed and assess the current expiration and revocation mechanisms.

I'll implement appropriate mitigations such as short-lived or one-time-use tokens where applicable, improve token revocation and rotation handling, ensure logs and telemetry do not capture sensitive token values, and add tests validating secure token lifecycle behavior. I'll also document the security assumptions and any changes to token handling to help prevent future regressions.

Thank you.

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

[sublime247]

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

would love to do this

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

[drips-wave]

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

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

[drips-wave]

This issue has been marked as completed by a Drips Wave moderator for @omosvico as part of the Stellar Wave Program's 7th Wave 🥳

Moderator's reason: [Auto-assessed] No maintainer response across any of the four channels. The PR is a high-quality, comprehensive contribution that implements the requested short-lived payment tokens, security headers, and log sanitization to resolve the identified security risk.

😎 @omosvico: You earned 200 Points for completing this issue! After the current Wave ends, you'll be eligible for a percentage of the Wave's reward pool based on the percentage of total points you've earned. Learn more here.

🧑‍💻 Repo maintainers: How'd the contributor do? Leave a review to share your experience working with them.

ℹ️ Note: This issue was marked complete via moderation. Points were issued even though the GitHub issue remains open.