Digital Asset Platform Application Design Challenge

Welcome to "Digital Asset Platform Application Design Challenge". We are looking for your help to create a simple, clean, and intuitive application designs that will provide a bank's customers, their operation users and treasury managers with new and innovative banking features to help them with their daily operations in a more seamless and interactive way as well as improve a banking customer's experience.

Customers will require access to basic banking self-service features (e.g. account summary, account statement, initiate a payment, manage personal information etc), but we would also like you to be creative and identify new and different capabilities that a customer may desire. Similarly an operations user and treasury manager will require access to an easy to navigate and an interactive application. 

Read the challenge specification carefully and watch the forums for any questions or feedback concerning this challenge. Let us know if you have any questions in the challenge forum!

Round 1

Submit your initial design for a Checkpoint Feedback

• As part of your checkpoint submission, you must upload your submission to MarvelApp so we can provide direct feedback on your designs. Please include the MarvelApp URL in your notes.txt. 
• Make sure all pages have the correct flow. Use the proper file numbers, (1, 2, 3, etc.)

Round 2

Submit your Final Design plus Checkpoint Updates

• As part of your Final submission, you must replace your checkpoint submission with the final submission into MarvelApp so we can provide direct feedback on your designs. Please include the MarvelApp URL in your notes.txt.
• Make sure all pages have the correct flow. Use the proper file numbers, (1, 2, 3, etc.)

BACKGROUND OVERVIEW

• Blockchain or Distributed Ledger Technology (DLT) is one of the most talked-about topics in the financial services industry today. 
• Blockchain is a combination of technologies that allow digital assets to be created and passed from party to party with guarantees that the assets are authentic and have not been copied or counterfeited, without needing a trusted third party to open and maintain accounts for customers.
• If fully adopted, it will enable banks to process payments more quickly and more accurately while reducing transaction processing costs and the requirement for exceptions.
• In order to help central banks, banks and non-banking financial corporations leverage this technology, we aim to build a digital banking product on a distributed ledger. 
• Our product will enable customers and operation users of a bank to perform activities using the UX/UI screens developed by you. 
• Hence, these screens ought to be simple, user-friendly and intuitive
• Some of the key features of our digital asset platform are:
  • Payments on DLT
  • Cash tokenization/De-tokenization
  • Bond tokenization/De-tokenization
  • Management Information Report

DESIGN  CONSIDERATION

• Simple, clean, and intuitive application designs - Provide a Bank's customers, their operation users and treasury managers with new and innovative banking features to help them with their daily operations in a more seamless and interactive way as well as improve a banking customer's experience
• Access to basic banking self-service features (e.g. account summary, account statement, initiate a payment, manage personal information, etc) 
• Access to an easy to navigate and an interactive application
• Creativity to identify new and different capabilities that a customer may desire beyond the original request
• Focus on the UI/UX interactions on how this application should work (specifically around non-financial transactions). What should the user see and experience when using the application? 

CHALLENGE GOAL

• The goal of this challenge is to develop the best visual design and explore how banking experience can be improved using blockchain/DLT

CHALLENGE FORUM

• If you have any doubts or questions regarding challenge requirements, please ask in our challenge forum: https://apps.topcoder.com/forums/?module=ThreadList&forumID=712617

SCREEN REQUIREMENTS

• For this challenge, we are looking for the below pages to be designed/considered in your concepts. 
• The screen functionality details listed below are suggested functionality for consideration.
• Do not allow the suggestions below to impact the creativity of design. 
• If there is a better way to accomplish the same goal, then feel free to take creative liberties.
• In this challenge, we will focus only on "Retail and Corporate Customer" and "Bank Operations User" roles

All User Roles
01) Landing Page

• Show initial screen with some simple placeholder for the logo
• Show the purpose of this application - Treat this as marketing page to inform a potential user or non-logged in user about the app capability
• Link to login page 

02) Login Page

• All users need to login in order to access the application
• Provide a login form where the user can enter their account credentials (username, password, submit)
• Provide Two Factor Authentication (OTP Screen) to email or phone
• Provide a series of security system features if the user enters the wrong credential for several times:
  • Retail and Corporate Customer: Error message -> Warnings confirmation to check their credential with the bank -> Block account and inform the user to contact Bank to re-open the account
  • Bank Operations User: Error message -> Warnings confirmation to check their credential -> Block account and inform the user to contact Admin to re-open the account

Retail and Corporate Customer
03) Retail and Corporate Customer User Dashboard 

• Once a customer logs in, this will be his landing page with the details of the activities that a user can perform. 
• Provide user account features like Welcome user, user profile, account summary, account statement, password change, transaction history, account balance, new payment request, etc
• User activity options (account summary, account statement download, account settings, account name, available balance, transaction history, timestamp, etc)
• Please add other information that can be put into this screen. Show us your creativity

04) New Payment Request (Retail and Corporate Users)

• Allow for a customer to initiate a payment request to a beneficiary
• Provide user to initiate a transfer request by keying in some of the important fields like – funds transfer between accounts of the same bank, funds transfer between two different banks, etc
• Sender details - type of account, account details, display account balance
• Beneficiary details – name, account number, amount, mobile number (optional field), the purpose of transfer, date and time for standing instruction, etc
• Provide user a feature to check all these transactions carried out on a particular account, i.e. a transaction log. 

05) Add beneficiary

• Ability to add a list of a beneficiary that will be used frequently by the user in the app 
• Beneficiary details fields: name, account number, amount, mobile number (optional field), the purpose of transfer, date and time for standing instruction, etc
• View list of an existing beneficiary and ability to search and filter the list easily by the beneficiary available information
• Edit and Delete beneficiary 

Bank Operations User
06) Bank Operations User Dashboard 

• Dashboard screen – Once the Bank Operation Dashboard user successfully logs in, this will be his landing page with the details of the activities that a user can perform. 
• Provide user account features like Welcome user, user profile, account summary, account statement, password change, transaction history, new payment request, role-based functionality, payments queue, etc
• Please add other information that can be put into this screen. Show us your creativity. 

07) New Payment Request (Bank Operations)

• Allow for an operation user to initiate a payment request to a beneficiary on behalf of its customers - There will some situations where customers cannot able to maintain the payment requests due to the high volume of transactions. So they will call their personal relationship manager in the bank and request to do the payment request. Relationship Manager will assign to Bank Operation Users so that they can transfer on behalf of their customers.
• Provide user to initiate a transfer request by keying in some of the important fields like – funds transfer between accounts of the same bank, funds transfer between two different banks, 
• Sender details - type of account, account details, display account balance
• Beneficiary details – name, account number, amount, mobile number (optional field), the purpose of transfer, date and time for standing instruction, etc
• Ability to add total balance that needs to be transferred into the beneficiary 

08) Search and Manage Payment

• Provide the user with a feature to search for a particular payment request and add/update fields in that payment request. In effect, an operation user should be able to repair or cancel a payment.
• Repair functionality is required when a transaction failed. Bank Operation users can cross-check the details of that particular transaction like IFSC (Bank Code), Swift Code, or some similar details, correct them and reinitiate the transfer. But please note crucial details like Transaction ID, Account Number cannot be changed or no editable
• Please note that we don’t have a fixed payment form here, so please feel free to come up with a more required field for a transaction (as you experience in your local banking)  
• Provide user a feature to check all these transactions carried out on a particular account, i.e. a transaction log

9) Payment Queue Monitoring Incoming and Outgoing

• Allow banks operations users to monitor incoming payments queue, outgoing payments queue, display fields (transaction id, creation timestamp, sender, receiver, amount, priority, status and last updated), the total number of payments, the total value of payments, etc
• This is a situation where the payment is stuck in the queue due to insufficient liquidity in the system and is waiting to be confirmed. In such cases, bank operation users monitor queue on a regular basis and based on the priority and other factors – re-order transactions. This happens for cross border payments and for RTGS systems. End customers will never get to know about these processes happening. 
• Payment queue monitoring will come before "search and manage payment" in the sequence of event
• Provide users a feature to perform actions on them like cancel and reprioritize, the reason for user action, re-ordering functionality (high priority transactions). 

IMPORTANT

• Keep things consistent. This means all graphics styles should work together.
• All of the graphics should have a similar feel and general aesthetic appearance
• Please provide design notes in marvel app or design explanation
• Create marvel app hotspots (Specific requested)

 
MARVEL PROTOTYPE

• We need you to upload your screens to Marvel App.
• Please send your marvel app request to fajar.mln@gmail.com (Challenge Copilot) 
• You MUST include your Marvel app URL (in your marvel app prototype, click on share and then copy the link & share it with your notes/comment on this link while you upload)

 
BRANDING GUIDELINES

• Follow our branding guidelines doc

DOCUMENTATION

• branding.pdf (attached in forum)

TARGET DEVICES

• Web-Based Application
• Desktop: minimum 1366px Width with Height adjusted accordingly

TARGET AUDIENCES

• Retail and Corporate Customer
• Bank Operations User

JUDGING CRITERIA

• Your submission will be judged on the following criteria:
  • Simple, user-friendly and intuitive design
  • Overall idea and execution of concepts
  • How well does your design align with the objectives of the challenge
  • Execution and thoughtfulness put into solving the problem
  • The overall design and user experience

 
SUBMISSION AND SOURCE FILES
Preview Image

• Please create your preview image as one (1) 1024x1024px JPG or PNG file in RGB color mode at 72dpi and place a screenshot of your submission within it.

 
Submission File

• Submit JPG/PNG image files based on Challenge submission requirements stated above
• MarvelApp link for review and to provide feedback

 
Source Files

• All source files of all graphics created in either Adobe Photoshop, Illustrator (Might need to convert it to PSD later), XD, or Sketch and saved as an editable layer

 
FINAL FIXES

• As part of the final fixes phase, you may be asked to modify your graphics (sizes or colours) or modify overall colours.