FAQ

authority management

The permissions of this system are divided into roles and accounts. Menus and operations are configured to roles to achieve permissions management

Rights management objects: role types, roles, accounts

1. In the menu management, each menu can be set which "role types" can be assigned
2. In role management, you can specify the role type for the role and give specific permissions within the scope of the role type
3. In account management, assign roles to accounts.

Note: distinguish the difference between roles and role types. Role types can be understood as a general term for a certain type of role. A certain role type includes the scope of authority that this type of role should have. A role is a specific authority unit with specific assigned authority

About replenishment

The so-called replenishment order refers to the customer service staff assisting the user to create an order when the user fails to create an order, so as to avoid differences in order statistics and accounting checks.

When the user pays, but the amount does not match the order, the payer's information does not match the reservation, and the payer does not transfer the funds directly through the system, it will cause a situation that does not match the order.

There are two ways to fill an order

1. Make up the bill from the collection record

In the menu on the left side of the system, "Transaction Management" -> "Order Replenishment Record", the data here is the collection data that does not correspond to the order. There is a replenishment button in the first column of the list. Click this button to enter the replenishment interface. By replenishing the order here, the amount cannot be adjusted, and the order will be subject to the actual amount recorded by the system.

The replenishment data generated here is caused by the user's payment amount inconsistent with the order, the payer's information does not match the reservation, and the payer's failure to pass the system.

1. Create a blank order

Through the blue "replenish order" button at the top of order management, you can create a completely blank order, and you can fill in any content to create an order. When the user pays but fails to survive the payment information push and causes omissions, this type of order replenishment method can be used to replenish the order.

In the above two cases of replenishment, because they are all manual operations, the order can choose to call back or not. Whether to choose to call back or not, you need to negotiate and communicate with the merchant.

Order Status

Collection order status

• 0 = not paid
• 1 = paid
• 2 = overout
• 4 = cancelled

Payment order status

• 0 = unpaid
• 1 = Done
• 2 = Processing
• 3 = Processing(Manual)
• 4 = Cancelled

Data deletion

Most of the data deleted in the system through the background are logical deletions, but there is still a small part of the data that is actually deleted. Please handle these data carefully:

1. The relationship between the merchant and the agent
2. The relationship between merchants and collection devices
3. Merchant receiving bank data
4. The relationship between roles and menus
5. The relationship between the transferred bank information and the merchant
6. The relationship between login account and agent role
7. Login account and merchant relationship

Settlement order modification limit

The status of order 1 (completed) and 4 (cancelled) is final and cannot be modified.

Order status 0 (unprocessed), 2 (settlement), 3 (settlement failed) is a temporary state, and can be modified to other states in the background