digital wallet solution using blockchain

Digital Wallet Solution

DHANRAJ DADHICHD FROZEN SOFT PRIVATE LIMITED

Solution OverviewThe digital wallet solution which presents diverse commerce-related applications extending well beyond payments. Few key features:

Open Source, Secure, Encrypted, High-Speed, Feasibility, etc.

Extensible, Symmetric, Non-web-centric, Client-driven.

Cost Effective: Due to open source API the development cost is less even for enterprise solution.

Integrated & Scalable: the systems must be inter-operable with all the other existing systems.

Server side digital wallet also called thin wallet which add multiple utilities to the end-user.

Multiple content repository, templates, User driven workflow & approval using Liferay 7. _

Consumers increasingly expect to shop in a seamless flow across all channels and form factors such as physical stores, smartphones, tablets and desktops.

© – 2016 D FROZENSOFT PRIVATE LIMITED. ALL RIGHTS RESERVED.

https://web.liferay.com/products/liferay-portal/features/enterprise-cms

Key Guidelines Considered In Solution

The cloud-based digital wallet must support online and in-store purchases, remaining synced across channels.

Digital wallets should integrate importing, sorting and prioritizing coupons. At the point of purchase, digital wallets should assist consumers by prompting methods of payment that maximize their discounts and rewards.

Digital wallet technology implementation should be in the cloud and its on-device representation must be tested and certified as secure against known threats.

Some consumers are reluctant to lock into a digital wallet for fear of relinquishing control over their purchasing behaviour and history and even losing information when switching providers.

To encourage adoption and allay consumers’ fears, digital wallet implementations and integrations should be agnostic of the wallet provider, and transfers should not be difficult.

Host card emulation enabled (HCE) technology is a viable option for in-store payments, and both MasterCard and Visa have announced support for HCE, although it is currently feasible only on Android devices.

At a high level, this means incorporating anti-malware measures against vulnerabilities related to opening links, attachments and scanning QR codes and implementing anti-theft measures such as two factor authentication and remote wiping of the on-device wallet.

Consumer privacy concerns must be addressed continuously.


Digital Wallet Strategies When developing a digital wallet strategy, it’s important that to keep in mind that not all mobile wallet functions will have value for them. The digital wallet includes a variety of functionalities, like storage of personal information, loyalty program and mobile transactions.

Device Native Features: Harnessing the power of a handset’s native features, including camera, contacts, social networking and location-based services, all enable a more engaging experience for consumers and will increase application adoption.

Consumer Friendly: Single store for all consumer information, and should be able to fetch all the information like Payment, Coupons, Loyalty, Receipts, … case is around customer data access.

Marketplace Focused: The objective is to deliver a fantastic customer experience in purchasing within a focused marketplace.

Easy to use: Offering Wallet on-device applications, not just mobile web, is important to meet consumers’ expectations of the sophisticated functionality and ease-of-use.


Blockchain Powered Wallets


Blockchain In A Nutshell

Shared ContractConsensus

Business terms embedded in transaction database & executed with transactions

All parties agree to network verified transaction

CryptographyShared LedgerEnsuring secure, authenticated & verifiable transactions

Append-only system of record shared across

business network


High Level Architecture


Data

& U

ser P

rivac

yProtocol and Flow

s Information

Data Format &

API

Wallet & Payment Management Layer

Protocol Negotiation Layer

Transport Layer

Token Based Payment

Push PaymentCC-Info

PaymentsCoupons /

LoyaltyCrypto

Currencies

Access / Credential Management

Authentication Management

Receipt and Log Management

Service Access Layer

&

Secure access

NFC HTTPS P2P … …

Ledger ManagementCentralized LedgerDistributed Ledger


Wallet Platform Abstraction Layer


Wallet ArchitectureUser Wallet Vendor Wallet

Communication Manager Communication Manager

User Wallet Manager Frontend / UI

Wallet Controller

Instrument Manager

Protocol Manager

Ledger Manager

Vendor Wallet Manager Frontend / UI

Vendor Controller

Instrument Manager

Protocol Manager

Ledger Manager


Transaction Execution

subscribe(EXECUTE_TRANSACTION)

VendorApplication

checkPrivileges (inv, Mastercard, PAY)

OK

Vendor Wallet

executeTransaction(inv, , Mastercard,PAY)

UserApplication

WalletController

User ProfileManager

SETProtocol

doOperation(PAY, Mastercard,PAY)

EXECUTE TRANSACTION SETProtocol2KP PAY

doOperation(PAY,Mastercard,PAY)

OK

notify (EXECUTE_TRANSACTION)

End-User Wallet

SETProtocol

WalletController


Applying Security Mechanism (Sender)

The security mechanism at sender node:

Apply hash function to the message

Encrypt the result of hash function with private key of sender.

Concatenate the result of step 2 with original data.

Encrypt result of step 3 with secret key.

Encrypt secret key by public key of receiver.

Concatenate step 4 and 5.


Protocol Data

Money-----------Personal

Information-----------

Control Data

Apply Hash Encrypt Encrypt

Concatenate Encrypt Concate

nate

Secrete Key

Publ

ic K

ey

Priv

ate

Key

Applying Security Mechanism (Receiver)

The generic services supported by the wallet could include:

Extract secret key and decrypt it by receiver's private key.

Decrypt message: result - step 1 secret key.

Decrypt hash by sender's public key.

Apply hash to the remained data.

Compare the result of step 3 and step 4.

If the result is equal, it means that data was send in secure manner and there is no threat in this respect. Else, the message is not valid.


Protocol Data

Money-----------Personal

Information-----------

Control Data

Apply Hash

Decrypt

DecryptDecrypt

Priv

ate

Key

Publ

ic K

ey

Hash

Security Key

Protocol Data

Hash

Transaction Management The flow of transaction management:

Transaction will be a block in system.

Block will be hashed and available to all the devices of user.

Once transaction validated .

Encrypt result of step 3 with secret key.

Encrypt secret key by public key of receiver.

Concatenate step 4 and 5.


Permissioned Access and Security User get registered and assigned with

enrolment certificate Ecert.

Unique Ecert will be used to validate the user for authorized transaction.

Every validating peer will have one Smart Contract.

One user can have multiple Tcert which is unique for each transaction and stored in wallet.

Each transaction will have a unique Tkey on initiation of transaction by user.

Tkey will be validated to access the ledger within consensus network.

Once transaction validated system will share Tcert with a public key which will be sent to benefiters.


Wallet Services Overview The generic services supported by the wallet are:

QR code based C2B payment system.

Payment functions, such as making a contactless.

Payment or reviewing the balance on a specific wallet account.

Account-to-account transfers in real time for P2P payments.

Coupon management, like receiving, displaying, managing and redeeming coupons.

Web Content, Theme and Site Management along with Allow UI and WYSIWYG editors.

Page level management for admin and microsites management along with individual theme.

Customer, Merchant and Product management.


High Level Approach


Application Test Strategy


Testing Process Action and Deliverables


Phases & DeliverablesPhase IndGlobal Deliverables Customer Deliverables

Discovery & Envision Application Backlog (Epics & Stories) SRS / SDD Architecture document & HLD Mockups / Wireframes Test strategy Overall project plan, Release plan, Test plan

• Detailed User Stories• Review feedback for architecture & HLD• Review feedback on acceptance criteria of elaborated

stories• Review feedback on screen mockups• Review feedback on test strategy

Build • Every Sprint– Sprint plan (for each sprint)– Elaborated user stories with acceptance criteria– LLD’s– Executable checked in code for the user stories – Automated Test Scripts & QA test cases– Conduct demo of developed features

• At end of the phase – Performance test scripts & results– Code quality compliance report

• UAT Defects’ report• Updated Deployable executable code

– User Help documentation

• Every Sprint– Review feedback on acceptance criteria of

elaborated stories– Review feedback on LLDs– Review feedback on QA test cases– Review feedback on features demonstrated

• Before end of Build Phase– UAT test scenarios

• Conduct UAT and log defects – Review feedback on help documentation

Sustain & Evolve • Defect reports• Updated Deployable executable code


Technology StackArea Name of API / Stack

Frontend Liferay 7.0 OR AngularJS & HTML5, AloyUI, D3, etc.

Core API Java, JEE, Web Services, Blockchain (Ethereum).

Security OAuth, Triple DES.

Server Apache Server, Apache Tomcat, Cloud (Amazon).

Database MySQL / Neo4j. (Based on discussion)

Mobile SDK Android, iOS.

OS Windows / Linux.

PM JIRA

Others GitHub, Jenkins, JUnit, JMeter.


Questions & AnswersPlease feel free to write us email for any of your queries & suggestions.

Looking forward for business opportunities.

Our email is: [email protected] | [email protected]

Thank You!!!© – 2016 D FROZENSOFT PRIVATE LIMITED. ALL RIGHTS RESERVED.

mailto:[email protected]



digital wallet solution using blockchain

Software