ayushcodes27 commented on code in PR #204: URL: https://github.com/apache/fineract-consumer-facing/pull/204#discussion_r4294579204
########## docs/consumer/features/transfers.adoc: ########## @@ -144,5 +144,5 @@ The query side owns transfer history because it is a cross-account view: per-acc * *Transfers execute immediately.* They use the server's current date; there is no scheduling, no future-dated transfer, and no recurring transfer. * *The transfer description is a fixed constant.* The customer cannot attach a note. -* *No amount ceiling on own-account transfers.* Transfers to the customer's own accounts are bounded only by the optional per-beneficiary `transferLimit`. A global or per-tier transaction limit would need new policy data. +* *No amount ceiling on own-savings transfers.* Transfers between the customer's own savings accounts are bounded only by the optional per-beneficiary `transferLimit` (loan repayments are capped at the loan's outstanding balance). A global or per-tier transaction limit would need new policy data. Review Comment: Resolved: Added the overpayment rejection Cucumber scenario in transfers.feature asserting HTTP 422 and error.msg.consumer.transfers.command.loan.overpayment. Also documented the best-effort/non-locking concurrency limitation and retry behavior in transfers.adoc. (The exact-payoff E2E scenario requires dynamic seeding changes in FineractSeeder and will follow in a separate PR to keep this PR clean) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
