Implement Merchant-defined Accepted Token List

[DanielEmmanuel1]

Description 📝

Allow merchants to specify a subset of the global token whitelist that they wish to accept for their specific invoices.

Proposed Steps 📝

• Update storage: Store a whitelist per merchant.
• Validation: When creating an invoice, check if the token is in the merchant's personal list.

Acceptance Criteria ✅

• Merchants can control their own preferred payment tokens.

[drips-wave]

This issue has been added to the Stellar Wave Program and is worth 200 Points.

🧑‍💻 Interested in contributing? Apply to work on this issue on Drips Wave, earn points, and receive rewards.

Warning

Only applications submitted via the apply link above will be considered. Please do not apply by commenting on the issue or opening a PR directly.

🤠 Repo maintainers: You can manage this issue's Points and Complexity on your Maintainer Dashboard here. Please keep an eye on applications and respond quickly 💙

ℹ️ Learn more about Drips Wave

[edehvictor]

@edehvictor has applied to work on this issue as part of the Stellar Wave Program's 2nd wave.

Can I fix this as soon as possible

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

[Lakes41]

@Lakes41 has applied to work on this issue as part of the Stellar Wave Program's 2nd wave.

Hello maintainer,

I am interested in implementing the merchant-specific token whitelist to provide granular control over accepted payment methods. I will start by updating the storage layer to map a personalized subset of the global token whitelist to each merchant's identity, ensuring these selections remain compliant with protocol-wide standards. My approach involves integrating a validation guard within the invoice creation process that cross-references the selected token against the merchant's specific list, alongside developing secure management functions for adding or removing tokens. By establishing this hierarchical validation flow, merchants can tailor their payment experience without compromising the security or integrity of the underlying contract state.

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

[Tybravo]

@Tybravo has applied to work on this issue as part of the Stellar Wave Program's 2nd wave.

Hello, I am a full-stack Software Engineer with 7+ years of experience and a Blockchain Developer. New to open-source contributions and adapting very quickly, and I do like to work on the Issue.

I have strong hands-on experience building advanced, user-friendly and visually engaging frontend interfaces using React, TypeScript, and Next.js, with a focus on reusable component architecture, modern UI patterns, responsive design, state management, and performance optimization. I work across both frontend and backend systems, including backend logic, API design, database architecture, and schema modeling.

I have experience building modern, scalable web applications using React, Typescript, Next.js, Node.js, Java, Rust, and related technologies. Some relevant projects (personal and OPEN SOURCE) I have worked on include:

--> https://www.verilens.xyz/
--> https://repeasy.wal.app/
--> https://docwalrus.vercel.app/
--> https://grainlify.0xo.in/

I am comfortable working within an existing codebase or independently , following project conventions, and delivering clean, maintainable, and well-structured solutions. My GitHub repositories can speak for themselves in demonstrating my experience and consistency across different types of projects.

I am confident I can contribute effectively and deliver high-quality results.

Thank you for your time and considering my application.

Regards,
Bravo

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