how it works

UPASS Transaction Flow

• UPASS Module is downloaded onto the handset
• User is allocated unique Identity and Password
• User Logs in keying his details
• User details are checked and upon authentication User access request is routed to relevant Server
• User then Proceeds to Key in Customer Number of Searches for the Customer Number using UPASS Directory for Collections and Billing functions or Product/service Options in case of Sales functions
• The relevant Data is fetched from the Backend and displayed on the User's Mobile screen
• User then keys in transaction details such as Payment made and mode of payment, product/service Options in case of Sales
• This Data gets registered on the Back-end server and the server issues acknowledgement/authorization command which flows back via UPASS Server Farm on to the User's handset, if Customer documentation is needed, the Systems sends out in-built print command to the Blue Tooth printer paired with the User Handset