#88: Integration test — merchant payout address change mid-settlement

[misrasamuelisiguzor-oss]

Description

Combine treasury-local #32 with a real cross-contract scenario: merchant calls update_merchant_payout_address between propose_settlement and execute_settlement, confirm funds go to the address current at execution time, and that this is the deliberately intended behavior (not a bug).

Requirements and context

If funds should instead be locked to the payout address at proposal time, that's a different (larger) issue — first confirm current behavior and document/test whichever is correct.

Suggested execution

git checkout -b test/e2e-payout-address-change-mid-settlement

• Files: tests/invoice_treasury/mod.rs

Test and commit

• Test: payout address change between proposal and execution behaves per confirmed/documented design
• cargo test --all passes

Example commit message

test: cover merchant payout address change during settlement lifecycle

Closes #88

Guidelines

Timeframe: 48 hours. Depends on #32.

[OmniZlatoon]

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

Hi maintainer sir, I'm called Junior Brown , a full-stack and smart contract engineer building on Stellar. I specialize in designing and shipping scalable, secure systems end-to-end, from Soroban smart contracts to production-ready backend infrastructure and user-facing applications.

I’ve worked on complex architectures involving automated agents, cross-chain logic, and data indexing, focusing on reliability, performance, and clean standards. My approach is very product-driven: I don’t just build contracts, I build complete systems that solve real user problems and can scale in production.

I’m especially interested in infrastructure, security, and automation creating tools and frameworks that make it easier for other developers to build safely and efficiently on Stellar.

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

[akindoyinabraham0-collab]

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

I will like to work on this issue

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

[drips-wave]

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

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