Stellar payment-link / invoicing guide

[truthixify]

Tier: M (2-4 days) Type: writing

Context

Demo wave shipped payment-link generation. Real apps want this primitive. Document the URL schema, signing patterns (to prevent tampering), and integration recipes.

Scope

Write docs/guides/stellar-payment-links.mdx:

• URL schema for Wraith payment links (https://your-domain/pay?to=alice.wraith&amount=...&memo=...&exp=...)
• Optional signature for tamper protection
• Deep-linking into your own app
• QR code generation patterns
• Expiry handling
• Demo's reference implementation walkthrough (link to demo repo)
• Webhook receiver for confirmed payments

Acceptance criteria

• Page committed
• Working example URL
• Reference implementation code excerpts
• Linked from demo + SDK Stellar

Files to start with

• New: docs/guides/stellar-payment-links.mdx
• demo/src/components/StellarPaymentLink.tsx

[baedboibidex-cmyk]

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

I would love to handle this issue and author the definitive architectural guide for Wraith payment-links and invoicing primitives. Standardizing secure URL schemas and web3 checkout patterns is essential for converting decentralized payment states into friction-free user applications. I have deep experience working with cryptographic URI design, deep-linking protocols, and implementing secure transaction listeners.

To deliver an exceptional, highly secure integration reference, I will structure docs/guides/stellar-payment-links.mdx around:

1. The Core Schema Specification: Clearly documenting the structural query parameters (to, amount, memo, exp) along with a valid, live-running URL example.
2. Cryptographic Tamper-Proofing: Detailing the explicit signing patterns (e.g., HMAC or asymmetric key pairs) required to attach an optional signature block, preventing malicious users from altering amounts or recipient addresses in-transit.
3. App Integration & Handshakes:
   • Mapping deep-linking schemes to gracefully hand off parameters to native or web application shells.
   • Outlining clean front-end QR code generation patterns and handling expiration lookups gracefully during the payment session lifecycle.
4. Post-Payment Webhooks: Documenting a production-style webhook receiver architecture to listen for on-chain ledger confirmations, matching the transaction hash back to the original link payload.
5. Reference Implementation Walkthrough: Incorporating explicit code excerpts directly from demo/src/components/StellarPaymentLink.tsx to provide a practical, developer-ready blueprint.

I am ready to dive into the codebase and deliver a pristine guide for the Wraith Protocol ecosystem!

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

[truthixify]

@baedboibidex-cmyk Assigned. Welcome to wave 6.

Quick expectations to make this smooth for both sides:

1. Branch from develop (not main). PRs target develop.
2. Open a draft PR within ~3 days of pickup so we can see direction early.
3. Update at least every 5 days. Silence is the only thing that costs you the assignment; if you get stuck or context changes, just say so on the PR.
4. Read the issue body's acceptance criteria carefully. Hitting those is the merge bar.

If anything is ambiguous, ask before building.

[drips-wave]

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

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