Implement account spending limits and multi-approver transaction controls

[Just-Bamford]

Description

Problem

Applications cannot enforce high-level spending policies before transactions are submitted. There is no unified mechanism for configuring per-transaction, daily, or monthly limits or requiring additional approval when a transaction exceeds a configured threshold.

Solution

Implement a spending policy engine that evaluates transactions before submission.

Policies should support:

• Per-transaction limits.
• Daily limits.
• Monthly limits.
• Asset-specific limits.
• Destination restrictions.
• Approval thresholds.
• Multiple required approvers.

The policy engine must calculate already-authorized spending and prevent concurrent transactions from bypassing configured limits.

Acceptance Criteria

• setSpendingLimit(asset, amount, period) is implemented.
• Per-transaction limits are enforced.
• Daily and monthly cumulative limits are supported.
• Limits can be configured per asset.
• Transactions exceeding limits enter an approval state.
• Multiple approvers can be required.
• Approval status is tracked.
• Concurrent transactions cannot bypass cumulative limits.
• Policy violations return structured errors.
• Tests cover limits, resets, concurrent requests, approvals, rejection, and multi-approver workflows.
• Exported through src/transaction/index.ts and src/index.ts.

Note for Contributors

The policy engine should evaluate the transaction before signing/submission. Be explicit about how pending, failed, and completed transactions affect spending calculations.

[bolajigate-cell]

@bolajigate-cell has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

Kindly assign this issue to me.

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

[Mayor-Isaac]

@Mayor-Isaac has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

Hi Maintainer! I’m interested in contributing to this task and can work toward delivering a clean solution on time.

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

[obedojukwu16-jpg]

@obedojukwu16-jpg has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

I will like to work on this project, I know exactly what to do and I will deliver efficiently.

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

[Johnalex-hub]

@Johnalex-hub has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

Good day team. My name is John and i am a fullstack web3 developer. I have gone through the scope of the issue and i can guarantee my ability in getting this done. Can i please get assigned

ETA :48 hrs

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

[drips-wave]

Congratulations, @Johnalex-hub! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on August 31, 2026.

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