SaFi Bank Space : 🟢 Option B: User clicks on 'Contact list' to select phone number of SaFi user

Key parent P fe story points be story points story points Status
SM-2101 Epic Transfer Money between SaFI Accounts (EPFS) Medium 3.0 3.0 5.0 Done

Role: User

Objective: I want to send money to another SaFi user and upload his/her name and phone number from my device contact list

Reason: so that I can send money from my SaFi account to another SaFi account without inputting it manually

Functional requirements:

  • the account number will not be displayed at all, nor pre-populated. This is to prevent users abuse of the functionality of checking which phone numbers have SaFi account

  • No verification on phone number

UI requirements: -

Process flow:

  1. Access to permission is asked

  2. Permission is granted by user

    1. Depending on user’s choice, if it’s only granted this time, the permission access will be asked again next time

  3. “Contacts” is populated with the imported contacts from the device

  4. Selecting a contact, the system imports the correct data into the “Receiver name” & “Phone number” fields

Execution steps:

  1. User is on “Send money to” screen

  2. User changes switch to “Phone number”

  3. User taps “Contacts” button on the “Phone number” numerical text box

  4. Permission to access contacts message appears

  5. User taps on “While using the app” or “Only this time”

    1. If user taps on “Only this time”, the permission access message will appear again next time

  6. “Contacts” panel is displayed

  7. User selects a contact

  8. “Send money to” screen is displayed with the “Receiver name” & “Phone number” fields filled with the selected contact’s details

Internal dependencies:

SM-1011 - FE: Transfer money between intrabank accounts - phone number Done

External dependencies:

Access to contacts on device

Alternative scenarios:

  1. User is on “Send money to” screen

  2. User changes switch to “Phone number”

  3. User taps “Contacts” button on the “Phone number” numerical text box

  4. Permission to access contacts message appears

  5. User taps on “Deny”

Acceptance criteria:

  • user is able to select “Phone number” option on the switcher

  • user Is able to select the icon for contact list

  • the device will ask him for permission to access his/her contact list

    • while using the app (user will allow this once and will be never asked again, the contact list will open automatically next time)

    • only this time (user will allow this only for this time, in the future he/she will be asked again, the contact list will not open automatically)

    • deny (user will not allow to open his/her contact list and will never be asked again)

  • the modal window with search bar and list of user’s contacts is displayed

  • user is able to simply select a contact from his list and the name and phone number will be pre-populated

  • name of the selected contact (beneficiary) must be extracted from the SENDER device    

    • no validation of real name attached to phone number must take place

  • both fields are editable:

    • input field for “Beneficiary name” is available to the user and can be changed (rewrited)

    • input field for “Phone number” is available and accepts only numeric characters

  • CTA button “Continue” is available to the user

Links to wireframes/UI:

https://www.figma.com/file/0LEEFZgkUnPkPTkY9PMREt/SaFi---WF-%26-UI-(Shared)?node-id=8198%3A87294

https://www.figma.com/file/dkDQHRa1zq7tU58MiL6hBR/SaFi---UI---MVP-(Shared)?node-id=9%3A3465