DMA.md

DMA - Decentralized Mobile App

• DMA are apps that users download from the Google Play Store or Apple App Store that integrate with NewPay. (See all Dapp types)
• Android native Dapps use Newton's Android NewPay SDK
• iOS native Dapps use Newton's iOS NewPay SDK

User Authentication

Preconditions

• User has NewPay installed on their device and has set a NewID

sequenceDiagram;
    participant User;
    participant DMA;
	participant NewPay;
	participant HEP Node;
    User->>DMA: Click Login;
	DMA->>NewPay: Send login request;
	NewPay->>HEP Node: Send Dapp public key;
	HEP Node->>NewPay: Send Dapp info, request user access;
	NewPay->> User: Prompt to authorize login;
	User->>NewPay: Authorize login;
	NewPay->>DMA: NewID sent to Dapp;
	NewPay-->>DMA: Send user back;

Loading

Dapp requests user login

1. Dapp displays Login with NewID button
2. User taps button

• See [newpay.native.login.requestAccess]

User authorizes Dapp on NewPay

1. Dapp sends request for login to NewPay
2. NewPay gets public key of Dapp through [signature] and [message] parameters
3. NewPay sends public key to [HEP Node]
4. HEP Node uses public key to request app information that was registered in database and sends that information back to NewPay
5. NewPay opens and prompts user to authorize the Dapp login based on information gathered from HEP Node
6. User confirms login
7. User's NewID is sent to Dapp, with [message] and [signature]

Payments

sequenceDiagram;
    participant User;
    participant Native Dapp;
	participant NewPay;
	participant HEP Node;

    User->>Native Dapp: Click 'Pay with NewPay';
	Native Dapp->>NewPay: Send public key + order info;
	NewPay->>HEP Node: Send public key;
	HEP Node->>NewPay: Send Dapp info;
	NewPay->> User: Prompt: authorize payment;
	User->>NewPay: Type password + authorize;
	NewPay->>HEP Node: Request payment;
loop FundsTransfer;
        HEP Node->>HEP Node: Transfer payment;
	end;
	HEP Node->>NewPay: Send receipt;
	NewPay->>User: Send receipt;
	NewPay->>Native Dapp: Send receipt;
	NewPay-->>Native Dapp: Send user back;

Loading

Dapp requests user payment

1. Dapp displays Pay with NewID button
2. User taps button

• See [newpay.native.payment.requestPayment]

User authorizes payment on NewPay

1. NewPay gets public key of Dapp and order information through [signature] and [message] parameters
2. NewPay sends public key to [HEP Node]
3. HEP Node uses public key to request app information that was registered in database and sends that information back to NewPay
4. NewPay opens and prompts user to authorize the payment based on information gathered from HEP Node
5. User confirms payment
6. Payment receipt is sent to user and Dapp
7. User is redirected back to Dapp