Skip to content

feat(v2): implement transaction limits engine and configurable fee tiers - #267

Open
Gpraiz01 wants to merge 1 commit into
Feyisara2108:mainfrom
Gpraiz01:antigravity/v2-limits-fees
Open

feat(v2): implement transaction limits engine and configurable fee tiers#267
Gpraiz01 wants to merge 1 commit into
Feyisara2108:mainfrom
Gpraiz01:antigravity/v2-limits-fees

Conversation

@Gpraiz01

Copy link
Copy Markdown
Contributor

Summary

Implement a database-driven transaction limits and fee engine with KYC-tier enforcement, USD-based limit validation, configurable fee rules, admin management APIs, and user-facing allowance visibility.

Related Issues

Closes #384

Type of Change
New feature

Bug fix
Breaking change
Refactor
Documentation

Changes Made
Added TransactionLimit and FeeConfig entities.
Seeded default limits and fee configurations.
Implemented LimitsService for tier validation and fee calculation.
Integrated limit enforcement into transaction creation flow.
Added admin APIs for managing limits and fees.
Added /limits/me endpoint.
Added comprehensive tests covering limits, fees, and KYC tiers.

Testing Done
Verified KYC tier enforcement.
Verified limit validation and allowance calculations.
Verified fee calculations and deductions.
Verified admin updates take effect immediately.
Verified UTC daily reset behavior.
Ran build and full test suite successfully.

@github-actions

Copy link
Copy Markdown

Auto-review failed (API error). Leaving PR for human review.

@github-actions

Copy link
Copy Markdown

This pull request has been automatically marked as stale because it has not had activity in the last 30 days. It will be closed in 14 days if no further activity occurs. If you are still working on this, please leave a comment or remove the stale label.

@github-actions github-actions Bot added the stale label Jul 27, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Make /create route functional or redirect it

2 participants