π Problem Statement
The fraud prevention log table does not include a risk score for flagged transactions. Admins can see that a transaction was flagged but have no quantitative measure to prioritise review β treating all flags equally regardless of severity.
π‘ User Story
As a Pelcro admin, I want a risk score displayed in the fraud prevention log table, so that I can prioritise reviews by severity rather than treating all flagged transactions equally.
π― Definition of Done (DoD)
A feature is done when:
βοΈ Given a flagged transaction in the fraud prevention log, when an admin views the table, then a risk score (e.g. 0β100) is displayed for each entry β and the table can be sorted by risk score.
Please authenticate to join the conversation.
Backlog
Pelcro Product
4 months ago

Mike Gilbert
Get notified by email when there are changes.
Backlog
Pelcro Product
4 months ago

Mike Gilbert
Get notified by email when there are changes.