Â
Key | parent | P | fe story points | be story points | story points | Status |
---|---|---|---|---|---|---|
SM-6341 | PUBLIC LAUNCH: Transaction Identification with Business Unique Number (complex solution) | 3.0 | 13.0 | To Do |
Role: SaFi bank
Objective:
want to create a concise/not-too-long reference number for every transaction
Reason:
so that the user can easily identify any transaction and provide details when contacting customer support.
Functional requirements:
Owner of the new sequence numbering on customer level will be THM, also mapping for card transactions will be done here (MasterCard ID ~ SaFi ID).
UI requirements:
Process flow:
Execution steps (Happy path):
Internal dependencies:
Transaction History Manager
External dependencies:-
Alternative scenarios:-
Acceptance criteria:
Every parent transaction has its unique reference number, 8+ digits long
for TX containing also fees, only one ID should be issued, i.e. no separate ID for fee entry
for a split transaction, only one ID should be issued for the parent TX and not the child transactions
This customer-facing ID is a simplified version of the existing UUID (very long, not readable)
Links to wireframes/UI:
n/a