Hello Sergio, Here is a pr https://github.com/apache/fineract/pull/515 <https://github.com/apache/fineract/pull/515> which aimed to address this problem by relying on the client to optionally supply a unique id with each request. Maybe you can build on the same (it was missing test cases and api doc updates) and get it merged ?
Regards, Vishwas > On Mar 24, 2020, at 7:39 PM, Sergio Junior <[email protected]> wrote: > > Hello everyone, > > Im integrating a system with Fineract, and doing some tests with the Savings > API (Deposit/Withdrawal functions), nothing is considered “Unique”, so if for > any reason my system interpret a call as failed (maybe a reverse proxy fault, > tcp issues etc) and perform a retry, Fineract will Credit (or Debit) a > transaction multiple times, no field is considered an Identifier and i > couldnt find any resource to notify the API that a transaction is a retry or > a new one. > > Whats the idea for such scenario, to maintain consistency and avoid > duplicates? > > Thanks!
