## PAPAYA PAY (Payment Gateway) - Beta documentation*
### Initial software requirements and use case flow

##### There are many other features not included here but will be added here ASAP, things like creating transection, (QR 30) code, and getting callback and customer data. (after number 15).

#
1. User/Merchant registration

    - email (unique)
    - password

2. User Roles/Account types
- 2.1 Super Admin (Default Admin - Registration is not available)
- 2.2 Merchants (Registration available and will take place with KYC confirmation)
- Corporate
- Personal
- 2.3 Normal User / Sub-ordinate user (can be created by Merchants/Super Admin and will be maintained by merchants employees)

3. After initial registration submission
- 3.1 users/merchants have to confirm their registration with **OTP** sent to their phone/email.
- 3.2 If users fails to confirm their **OTP**
- 3.2.1 They still will be able to login with their email/userid and password.
- 3.2.2 After login the window will stuck for **OTP** confirmation as previous, and user will be able to request for new **OTP** on phone/email.
- 3.2.3 In any resgistration related user will have to contact with customer support.

4. After registration and **OTP** confirmation done (**KYC** step)
- 4.1 Merchant/user will be asked to submit **KYC** form for their type of account.
- 4.2 For personal merchant **KYC** form might include
- 4.2.1 Userid (unique), Real name, email, phone
- 4.2.2 ID Card No, ID Card Pic, Retail Info/docs, Selfie etc
- 4.3 For corporate merchant **KYC** form might include
- 4.3.1 Userid (unique), Company name, email, phone
- 4.3.2 Address, Corporate documents, clear pic or scanned copy

5. After the submission of all **KYC** info through the API, Users/Merchant will wait for their Profile Review & Approval. and Merchant will get email notification about profile approval. Mean time users will be shown their profile approval status on home page only.

6. Super Admin will see list of awaiting Registration & KYC submission and will approve or disapprove the KYC & the whole account.

7. After the KYC info reviewed approved from Super Admin, a New **API** key will be generated for that merchant account (API Key integration to merchants own service is their self service). And if KYC doesn't get approved user will be notified about the cause and will have to resubmit the KYC docs.

8. Each user login must have to authenticated with email OTP. If there is any sudden change of last login IP address within 24hrs or so. Then OTP varification required for re-login.

9. System other main functionalities are daily summary, Pay in, Pay out, Settlement, Profile management, Roles, Add users. (will be in detail after a while)

10. Each merchant depositor required to submit additional data of **UID** for every specific customer, **UID** must be unique to each customer. (How UID data will be collected?)

11. Each **UID** will sync with the customer details for first time payment. (UID will sync form gatway? any other way?)

12. Before making a second time payment, customer able to select the bank account they using to pay to prevent frauds. (Customer/Which customer* will select bank and where they will select)

13. second payment from the same UID will be synced with UID previous transaction history data and if the data mismatch the transaction will go pending.

14. QR will expired after 15mins, required bot to cancel the QR (This requires study of SCB bank api documentation).

15. download excel for transaction history.