Cashaa Technology Updates: Sprint Demo “Apple”

The Cashaa Team had its first sprint (named “Apple”) demo last Friday, where various team members demonstrated what they had completed, for the team and leadership to review.

The Team

Participants

Kumar Gaurav, Shareholder & CEO

Celestine Vettical, Shareholder

Felice Covelli, Shareholder

Amjad Raza Khan, Shareholder and Director — Technology

Janina Lowisz, Shareholder and VP — Marketing

Saurabh Jain, VP — Product Management

Priyakant Charokar, VP — Engineering

Dhanasekaran Sukumaran, Director — Project Management

Shibu Thomas, General Manager

Nilesh Kangane, Blockchain Developer

Vibhor Agrawal, UX/UI Lead

Mukesh Kumar, Mobile App Developer

Ajay Singh, Blockchain Developer

Jitendra Patwa, Blockchain Developer

Nisha Yadav, Blockchain Developer

Hrishikesh Devhare, iOS Developer

Anurag Kumar, Creative Head

Shruti Saha, Design Strategist

Supriya Patil, Java Developer

Abhinay Jiwankar, Blockchain Developer

Akash Jadav, Java Developer

Vaibhav Deshpande, Associate Developer

Time

1.54pm — 3.08pm BST

Agenda

1. UX Demo — Shruti
2. JHipster Framework for Cashaa core — Nisha
3. KYC (mobile) — Hrishikesh
4. KYC (web) —  Akash/Jitendra
5. CashaaPay (BTC) — Abhinay/Ajay
6. CashaaPay (ERC20) — Nilesh/Ajay

Summary:

UX Demo — Shruti

• Onboarding process (Selecting account, submitting Tier 1 KYC information) and dashboard

Celestine:

• Dashboard needs to include a full view of all connected accounts
• Include the ability to change the photo and to connect accounts in next development cycle (sprint)

JHipster Framework for Cashaa core — Nisha

• Demo of Shruti’s flow of customer onboarding integrated in JHipster

KYC (mobile) — Hrishikesh

• Demo how KYC is verified on the mobile app
• Demo of invalid ID, resulting in the message “no document found”

KYC (web) — Akash

• Demo how 3 kinds of reports are generated: Watchlist, documents upload and facial similarity reports

CashaaPay (BTC) — Abhinay

• Demo of list of users with access to the Bitcoin network and the APIs
• When a customer does a Bitcoin transaction, the CashaaPay module is the interface receiving the confirmation from the blockchain and posting into the Cashaa platform (now the user is Cashaa, later it can also be external users)

Amjad:

• We can create BTC addresses and make BTC payments from this panel

Kumar:

• CashaaPay will be used by companies, one of them will be Cashaa

Priyakant:

• Saurabh to write requirements for security, scalability, efficiency

CashaaPay (ERC20) — Nilesh

• Demo of CashaaPay, enabling to accept and forward Ether, CAS and other ERC20 tokens
• Demo of same UI as for CashaaPay (BTC), same way to add users and apps
• Demo of transaction page, checking status of individual transaction

Kumar:

• Have one login for both: Run separate nodes for both, but have a view of both together, if one is down it will not affect the view

Appendix: Conversation:

UX Demo — Shruti

• Presented onboarding process (Customer selecting account, collection of Tier 1 KYC information (mobile number and email)) and dashboard

Celestine:

• Onboarding process should be as simple as possible
• In dashboard, users should have a full view of all their connected accounts
• Include changing photo, connecting accounts in the next sprint

JHipster Framework for Cashaa core — Nisha

• Presented Shruti’s flow of customer onboarding integrated in JHipster

Celestine:

• How long is the daily standup meeting, is there a daily collaboration between Shruti & Nisha?

Nisha:

• 20 min

Shruti:

• Everyone is working together, there is one scrum team, everyone knows what the others are doing

Priyakant:

• We’ll have several smaller scrum teams in the future

Onfido (mobile) — Hrishikesh

• Demo how KYC is verified on the mobile app:

User provides first and last name, unique applicant ID is created, identity document and customer selfie are captured and uploaded on our KYC Partner’s portal. A unique application is stored for further evaluation of the user.

Celestine:

• After signup, the name information should not need to be entered again before KYC verification
• Include a message for the user

Saurabh:

• We have limited access to the Sandbox due to ongoing negotiations with the KYC services provider, therefore the details needed to be entered first.

Celestine:

• Don’t say KYC service provider’s name, but Cashaa

Kumar:

• Users will see it as “Cashaa Compliance API”

Hrishikesh:

• Demo of invalid ID, resulting in the message “no document found”

KYC (web) — Akash

• 3 kinds of reports are generated: Watchlist, documents upload, facial similarity reports (resulting of document + selfie comparison)
• Watchlist demo: details input, applicant ID created, watchlist verification done directly, report generated in admin dashboard

CashaaPay (BTC) — Abhinay

• List of users with access to the Bitcoin network and the APIs
• When a customer does a Bitcoin transaction, the CashaaPay module is the interface receiving the confirmation from the blockchain and posting into the Cashaa platform (now the user is Cashaa, later it can also be external users)

Amjad:

• We can create BTC addresses and make BTC payments from this panel
• Migration result from Auxpay to the framework, independent component interacting with the blockchain

Felice:

• Is it similar to the Btc2bid admin panel?

Kumar:

• The Btc2bid panel listed users of Btc2bid, the list in CashaaPay lists users with access to the Bitcoin network and the APIs
• We copied the Auxpay code so we have an internal module like we had Blockcypher before, a reader and writer for the Bitcoin blockchain, the team is also creating one for the Ethereum network

Celestine:

• Will all customers have an ID, or will there be aggregated accounts?

Kumar:

• From outside, users will never see CashaaPay
• If we have 1 Million users, we will have 1 Million addresses generated, you will see all addresses in CashaaPay to track all individually
• Testing is crucial to prevent past negative experiences like with BlockCypher
• CashaaPay will be used by companies, one of them will be Cashaa

Felice:

• What is the status concerning security, scalability, efficiency?

Priyakant:

• Saurabh will write requirements for that

Kumar:

• Vigorous testing is needed to see how many addresses are possible to create per second, how many we will be able to read — in BlockCypher it took up to 1–2 days to read information → write an automated script and run on a testnet
  Celestine:

• Need to stress test and find out the maximum possible

Shibu:

• Currently, performance testing is in process

Kumar:

• Later make the design look more Bitcoin-related

CashaaPay (ERC20) — Nilesh

• Demo of CashaaPay: Accept and forward Ether, CAS and other ERC20 tokens
  Kumar:

• Why not one login for both, Bitcoin and ERC20?

Priyakant:

• Logins are separate to prevent having a single point of failure

Kumar:

• Still possible to have one login: Run separate nodes for both, but have a view of both together, if one is down it will not affect the view

Amjad:

• It is difficult to manage user data when both together

Kumar:

• As a bank it needs to be together, users want access to all in one, like in BlockCypher, where BTC, LTC, ETH are together

Shibu:

• In the future, we’ll have it together

Nilesh:

• Showing same UI as for CashaaPay (BTC), same way to add users and apps

Kumar:

• When the App key is generated, is a password added to that?

Amjad:

• It will be done when we have multiple users

Nilesh:

• Showing transaction page, checking status of individual transaction

Questions:

Celestine:

• Can the admin user see everything?

Amjad:

• The user can see only data related to their apps

Celestine:

• Priyakant to share code view for him to check copyright and headers

`Team working on the Sprint

Regards

Team Cashaa
The Next Generation Banking Platform for The Next Billion

---

Handy links:

Website | Exchanges | Whitepaper | Telegram | Twitter | Facebook | Linkedin | Youtube