Add helper for masking webhook callback URLs in logs and error responses

[Chucks1093]

Summary

Webhook callback URLs registered by creators may contain API keys or tokens in the query string. A shared masking helper should strip query params and keep only the scheme and host before any URL appears in a log or error response.

Scope

• Add a maskWebhookUrl(url: string): string helper that returns scheme://host with path and query string removed
• Use this helper in all log statements and error responses that reference a callback URL
• Add unit tests for: URL with query params, URL with path only, URL with no path

Acceptance Criteria

• Query string is stripped from all logged URLs
• Path is stripped, only scheme and host remain
• Unit tests cover all URL shapes

ETA: 12 hours

---

Coordinate on Telegram

[umohjosephemmanuel-cyber]

Enhanced webhook security and privacy by developing a URL masking utility that removes sensitive paths and query parameters from callback URLs, integrating it across logs and error responses, and validating behavior through comprehensive unit testing.

[bamiebot-maker]

kindly assign this to me i am ready to work on it

[spiffamani]

I'm a full-stack Software Engineer with 3 years of experience
I'd love to take this on — thanks for considering me

[DeePrincipal-dev-lang]

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

I would love to work on this task
And I'm confident I'll be able to deliver the result in a short amount of time

ℹ️ Repo Maintainers: To accept this application, review their application or assign @DeePrincipal-dev-lang to this issue.

[Abioladory123]

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

Interested in taking this on. I’ve worked across smart contracts, APIs, and frontend integrations, and I can start immediately.

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

[Demilade01]

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

Hey Sebastian, I will like to work on this issue!

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

[Yasir-TechGuy]

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

Hi please assign this issue to me

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

[InemesitMatthew]

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

Hi, I would like to work on this. You'd get a PR in 2-4 hrs of assignment
Thanks

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

[AJ0070]

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

Please, I would like to work on this issue.

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

[chinelo002]

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

Hi, my name is chinelo002, and I am a fullstack and smart contract developer skilled in React, Next.js, JavaScript, TypeScript, Tailwind CSS, and Soroban. For this task, I will:

1. Implement a reusable maskWebhookUrl(url: string): string helper that safely reduces callback URLs to their scheme://host representation while removing paths, query parameters, and sensitive tokens.
2. Integrate the masking helper across all log statements and error responses that reference webhook callback URLs to ensure no sensitive URL details are exposed.
3. Validate URL handling for multiple formats, including URLs with query strings, path-only URLs, and root-host URLs, ensuring consistent masking behavior throughout the application.
4. Add comprehensive unit tests covering all required URL shapes and verify that logged and returned URL values always exclude paths and query parameters.

ETA: 10 hours

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

[drips-wave]

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

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