Implement "Withdraw to Another Account" Functionality

[codebestia]

Description 📝

Implement functionality to allow the merchant to withdraw funds from their account contract directly to an arbitrary external address (another account). This provides flexibility for the merchant to transfer funds without first sending them to their primary registered wallet.

Proposed Steps 📝

• Update Events:
  • Define WithdrawalTo event in contracts/account/src/events.rs (fields: token address, amount, merchant address, recipient address, timestamp).
• Implement Functions:
  • withdraw_to(env: Env, token: Address, amount: i128, to: Address):
    • Retrieves the stored Merchant address.
    • Requires authentication from the merchant (merchant.require_auth()).
    • Checks if the account has enough balance of the specified token.
    • Performs a transfer of the amount from the current contract to the to (recipient) address using the token client.
    • Emits the WithdrawalTo event.
• Interface: Update MerchantAccountTrait in contracts/account/src/interface.rs to expose the withdraw_to function.
• Main Contract: Implement the method in contracts/account/src/contract.rs.

Acceptance Criteria ✅

• withdraw_to successfully transfers tokens to the specified recipient.
• Only the assigned merchant can call withdraw_to. Unauthorized calls must panic.
• The function correctly checks for sufficient balance.
• WithdrawalTo event is emitted upon success with correct data.

[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

[ikemHood]

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

Hi, I would like to implement the withdraw_to functionality.

I can define the WithdrawalTo event in the events module and implement the function in the core contract using the token client for external transfers. I will ensure strict merchant.require_auth() checks and balance validation as specified in the requirements to prevent unauthorized access. I will also update the interface trait to expose the new method.

ETA: 3 hours. Please assign this to me.

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

[Idrhas]

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

Hi Chief, I'd like to work on this issue, I have experience with the relevant technologies and ecosystem and have previously contributed to similar issues. I’m comfortable working with the codebase and familiar with standard practices.

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

[Tijesunimi004]

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

Hi Maintainer,I'd like to work on this issue

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

[Themancalledpg]

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

Hi, my name is Preciousgift, 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:
Define the WithdrawalTo event in contracts/account/src/events.rs with token, amount, merchant, recipient, and timestamp fields using Soroban event publishing.
Extend MerchantAccountTrait in contracts/account/src/interface.rs and implement withdraw_to in contracts/account/src/contract.rs with merchant.require_auth(), balance checks, and token client transfer to the recipient address.
Add secure logic to retrieve the stored merchant address, validate sufficient token balance using checked operations, and prevent unauthorized calls from non-merchant accounts.
Write and run unit tests verifying successful transfers, unauthorized access panics, insufficient balance handling, and correct WithdrawalTo event emission.
ETA: 10 hours

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

[Ogstevyn]

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

Hi, I'd like to pick up issue #69 — implementing the withdraw_to functionality for the ShadeProtocol account contract.

I'm familiar with the shade-stellar-contract codebase and have experience with the full implementation scope: defining contractevents in events.rs, merchant auth patterns with require_auth(), balance checks using the token client, token transfers from contract to arbitrary recipients, and exposing new functions through the MerchantAccountTrait interface.

I'll implement the WithdrawalTo event, the withdraw_to function with proper auth and balance validation, update the trait in interface.rs, and wire it up in contract.rs — with tests covering the success path, unauthorized access, and insufficient balance cases.

Could you assign this to me? Happy to get started right away.

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

[drips-wave]

Congratulations, @Ogstevyn! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on February 26, 2026.

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