Third-party payment framework requirements Document: Login module

Back to home directory

Login Module 1. Login Verification Code

You must submit a verification code at login to log in.
Example:

2. Limit number of simultaneous login users

Login limit: Only one person is allowed to log in at the same time, and if anyone logs in from another location, the original logged-in user is kicked out of the login state.
Depending on the account user, here are some tentative types:
1. Administrator account

Permissions: The administrator account has all the available rights, in addition to: query all user login record, set blacklist, kick out users and other functions
Operation background: Have all data query, modification and other rights (except for sensitive information such as order, withdrawal record, etc.)

2. Sales Account

Cash Clerk:

Permission: To withdraw work order query, withdraw work order progress modification (once modified cannot change)
Operating background: corresponding permissions

Financial Reconciliation Clerk:

Permissions: Order pipelining report Query
Operating background: corresponding permissions

3. Merchant Account

Permissions: API interface settings, order inquiries, application withdrawals
Operating background: corresponding permissions

4. Department Administrator account

Rights: Sales account increase, deletion, specific business inquiries
Operating background: corresponding permissions

3. Account Risk Control

When the account password leakage and other issues, the user can use the SMS notification function one click to freeze the account and change the secret.
Note: The premise of this operation is that the user has been bound to the mobile phone number, mobile phone number once bound only the original phone SMS confirmation can be modified.

Third-party payment framework requirements Document: Login module