feat: compliance improvements (limit request, stop transaction, chargeback)#1048
Merged
feat: compliance improvements (limit request, stop transaction, chargeback)#1048
Conversation
The modal was positioned absolute inside the scroll container, causing it to appear at the top of the scroll area rather than the visible viewport. Switch to fixed + overflow-y-auto so the modal always stays in the viewport regardless of scroll position.
Move the Limit Request form fields (Name, Limit, Investment Date, Fund Origin, Message, File) into a dedicated component so the same UI can be reused in the compliance flow without duplication.
Compliance users can now create a Limit Request on behalf of a user directly from the onboarding review (depositLimit row) and from the user data panel. The modal reuses the shared LimitRequestFields component so any future changes to the form apply to both the user and compliance flows.
Introduce a chargeback modal in the compliance transactions tab that calls the new PUT /support/transaction/:id/chargeback endpoint to release a refund. Extract reusable refund components (creditor fields and data table) and refactor the bank-tx-return screen to use them. Add STOPPED to the payment state labels and a getSupportUserInfo hook.
![github-code-quality[bot]](https://avatars.githubusercontent.com/u/9919?s=60&v=4){kind=small}
- Remove getSupportUserInfo and BankRefundData (no longer needed) - Update chargeback URL from /chargeback to /refund - Migrate bank-tx-return screen to use chargebackTransaction with nested creditorData
davidleomay
approved these changes
Apr 16, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
9080619,06e78f1): remove the "Login Kundenkonto" row from the onboarding header and use fixed positioning for the modal overlay.5b6c089,19244f6,9a8f301): addcreateLimitRequestto the compliance hook, extractLimitRequestFieldsfor reuse, and add a "Limit Request" button in compliance onboarding.a4d112d): add a stop-transaction button with confirm dialog in the compliance transactions tab, calling the newPOST /transaction/admin/:id/stopendpoint.88950a0): add a chargeback modal in the compliance transactions tab that callsPUT /support/transaction/:id/chargebackto release a refund. Extract reusable refund components (creditor fields, data table) and refactorcompliance-bank-tx-returnto use them. Add the newSTOPPEDpayment state label and agetSupportUserInfohook.4d8a711): bump@dfx.swiss/reactand@dfx.swiss/react-componentsto1.3.0-beta.268(includes the newTransactionState.STOPPED).Companion PRs
Test plan
npm run lint✅npm test✅ (26 suites, 276 tests passing)