Hello! I'm Oludele, an independent researcher working on payment system integrity. I wanted to introduce myself and share something I built that references your project, in case it's useful or interesting to anyone here, and because I'd genuinely value technical pushback on it.
I've been developing a framework called CIF (Chronological Input Failure), focused on a specific pattern in async payment systems: a transaction getting recorded as complete before the validation step behind it actually finishes, silently, without triggering an error. To check whether this pattern shows up in real, independently built systems, I went through Fineract's public JIRA history and mapped several tickets against it. FINERACT-1744 (System idempotency) was the strongest match I found, not a bug report, but a case where the pattern was significant enough that the team built dedicated infrastructure against it. I also found FINERACT-2304, FINERACT-2188, and FINERACT-2457 relevant in different ways, and explicitly ruled out one ticket I initially thought fit (FINERACT-1876) once I read it properly and realized it didn't match the pattern I was actually describing. The full writeup, including where I think the mapping is solid and where it's more of a stretch, is here: https://github.com/oludeleoluwapelumi/cif-simulation/blob/main/validation/FINERACT_TAXONOMY_MAPPING.md I'm not looking for endorsement, I'm looking for people who actually know this codebase to tell me where I've gotten something wrong or oversimplified. If anyone worked on FINERACT-1744 or the related tickets, or just has views on whether this framing holds up, I'd really value hearing it, positive or critical. Thanks for reading, and for the work you've put into Fineract, it's a genuinely useful thing to have public and well-documented for people like me trying to learn from real systems. Oludele
