Epic:
SM-232
-
Cards: Security Functions 1
Done
Priority: TBD
Effort estimate: TBD
Review status: APPROVED
Role: Client
Objective:
The client can block a specific virtual or physical card
Reason:
The client must be able to block the selected cards; this process will require some security verification process supported by a security SMS code. The Service Desk will get an automatic notification about this client activity/ticket will be created. The ticket will get a high priority. A copy of this ticket will be delivered to the client’s email address stored in the Contact information.
Functional requirements:
xxx
UI requirements:
xxx
Process flow:
n/a
Execution steps:
xxx
Internal dependencies:
BO Integration / Card Status
External dependencies:
CMS API Integration (Euronet)
SMS Service Provider
Alternative scenarios: n/a
Acceptance criteria:
The client can block his/her own virtual or physical card via a button in mode app/card settings
The client must be visually notified about successful or unsuccessful card blockage
The card blockage is approved by the client via the received SMS code
BO team must be notified via an auto-generated ticket that a specific card is blocked (card details must be provided in the ticket)
Links to wireframes/UI: