Business processing method, device, terminal and medium
By setting up the application portal of the target sub-app in the enterprise office application, the interaction with the collection application is achieved, and resource graphic code is obtained, the management complexity caused by the differences in the organizational structure of the enterprise office application and collection application is solved, and the development is reduced. Cost realizes the collection business function of corporate office applications.
Patent Information
- Application Number
- CN201910965866.9
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2019-10-09
- Publication Date
- 2024-12-17
- Estimated Expiration
- 2039-12-13
AI Technical Summary
In the prior art, due to the different organizational structure and account system, enterprise office applications and other collection applications are difficult for enterprises to manage and maintain uniformly, increasing development costs and complexity to realize collection business functions.
By setting up the application portal of the target sub-app in the enterprise office application, it realizes interaction with the payment application, obtains resource graphic codes and generates notification data, allowing payment users to scan through the payment terminal to achieve the transfer of electronic resources, reducing the number of business operations to be carried out Application development requirements.
There is no need to develop software for corporate office applications, which realizes the collection business function, reduces development costs, and simplifies the collection business operations of enterprises in different applications.
Smart Images

Figure CN112633871B_ABST
Abstract
Description
Technical Field
[0001] The present invention relates to the field of Internet technology, specifically to the field of communication technology, and in particular to a service processing method, a service processing device, a terminal and a computer storage medium. Background Art
[0002] With the development of Internet technology, electronic payment methods based on the Internet have emerged; and this electronic payment method has gradually been used by more and more users, enterprises and merchants due to its advantages of simplicity, speed, safety and reliability. At present, when users, enterprises or merchants want to perform payment collection business through a certain application, they must require that the application can support the payment collection business function, otherwise the application cannot respond to the payment collection needs of users or merchants; for example, when a salesperson uses an enterprise office application to work, if he wants to charge a certain business fee to a target customer through the enterprise office application, the enterprise office application must have a payment collection function, otherwise the salesperson cannot collect the corresponding electronic resources from the target customer through the enterprise office application. In this case, in order to meet the payment collection business needs of users in different applications, it is usually necessary for the developers of each application to develop functions for their respective applications separately to add corresponding payment collection functions in their respective applications, which will undoubtedly increase the development cost. Summary of the invention
[0003] The embodiments of the present invention provide a business processing method, device, terminal and computer storage medium, which can meet the user's payment collection business needs in different applications and reduce development costs.
[0004] On the one hand, an embodiment of the present invention provides a service processing method, the service processing method comprising:
[0005] In response to a trigger operation detected in a first application for an application entry of a target sub-application in a second application, switching from the first application to a target sub-application in the second application;
[0006] Displaying a resource service interface of the target sub-application, wherein the resource service interface includes a resource service item for collecting electronic resources;
[0007] According to the resource business operation for the resource service item, obtaining the resource graphic code corresponding to the resource service item;
[0008] In response to a resource business instruction issued by a resource collecting user to a resource paying user detected in the first application, notification data of the resource graphic code is generated, and the notification data is used to notify the resource paying user to scan the resource graphic code through a payment terminal to transfer electronic resources to the resource collecting user.
[0009] On the other hand, an embodiment of the present invention provides a service processing device, the service processing device comprising:
[0010] a processing unit, configured to switch from the first application to the target sub-application in the second application in response to a triggering operation of an application entry for a target sub-application in the second application detected in the first application;
[0011] A display unit, used to display a resource service interface of the target sub-application, wherein the resource service interface includes a resource service item for collecting electronic resources;
[0012] The processing unit is used to obtain the resource graphic code corresponding to the resource service item according to the resource business operation for the resource service item;
[0013] The processing unit is used to generate notification data about the resource graphic code in response to a resource business instruction issued by a resource collecting user to a resource paying user detected in the first application, and the notification data is used to notify the resource paying user to scan the resource graphic code through a payment terminal to transfer electronic resources to the resource collecting user.
[0014] In another aspect, an embodiment of the present invention provides a terminal, the terminal including an input device and an output device, the terminal further including:
[0015] a processor adapted to implement one or more instructions; and,
[0016] A computer storage medium storing one or more instructions, wherein the one or more instructions are suitable for being loaded by the processor and executing the following steps:
[0017] In response to a trigger operation detected in a first application for an application entry of a target sub-application in a second application, switching from the first application to a target sub-application in the second application;
[0018] Displaying a resource service interface of the target sub-application, wherein the resource service interface includes a resource service item for collecting electronic resources;
[0019] According to the resource business operation for the resource service item, obtaining the resource graphic code corresponding to the resource service item;
[0020] In response to a resource business instruction issued by a resource collecting user to a resource paying user detected in the first application, notification data of the resource graphic code is generated, and the notification data is used to notify the resource paying user to scan the resource graphic code through a payment terminal to transfer electronic resources to the resource collecting user.
[0021] In another aspect, an embodiment of the present invention provides a computer storage medium, wherein the computer storage medium stores one or more instructions, wherein the one or more instructions are suitable for being loaded by a processor and executing the following steps:
[0022] In response to a trigger operation detected in a first application for an application entry of a target sub-application in a second application, switching from the first application to a target sub-application in the second application;
[0023] Displaying a resource service interface of the target sub-application, wherein the resource service interface includes a resource service item for collecting electronic resources;
[0024] According to the resource business operation for the resource service item, obtaining the resource graphic code corresponding to the resource service item;
[0025] In response to a resource business instruction issued by a resource collecting user to a resource paying user detected in the first application, notification data about the resource graphic code is generated, and the notification data is used to notify the resource paying user to scan the resource graphic code through a payment terminal to transfer electronic resources to the resource collecting user.
[0026] The embodiment of the present invention can respond to the trigger operation of the application entry of the target sub-application in the second application detected in the first application, first switch from the first application to the target sub-application; secondly, display the resource service interface including the resource service item for collecting electronic resources, and obtain the resource graphic code corresponding to the resource service item according to the resource business operation for the resource service item; then, in response to the resource business instruction issued by the resource collecting user to the resource paying user detected in the first application, generate notification data about the resource graphic code, the notification data is used to notify the resource paying user to scan the resource graphic code through the payment terminal to transfer the electronic resource to the resource collecting user. In the above business processing process, by setting the application entry of the target sub-application in the second application in the first application, the interaction between the first application and the target sub-application in the second application can be realized, and through this interaction, the first application can realize the collection business function with the help of the target sub-application, without performing software development work on the first application, which can effectively reduce the development cost of the first application. BRIEF DESCRIPTION OF THE DRAWINGS
[0027] In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the accompanying drawings required for use in the description of the embodiments will be briefly introduced below. Obviously, the accompanying drawings described below are some embodiments of the present invention. For ordinary technicians in this field, other accompanying drawings can be obtained based on these accompanying drawings without paying any creative work.
[0028] Figure 1 is a schematic diagram of the architecture of a communication system provided by an embodiment of the present invention;
[0029] Figure 2 It is a flowchart of a service processing method provided by an embodiment of the present invention;
[0030] Figure 3 is a schematic diagram of a resource graphic code provided by an embodiment of the present invention;
[0031] Figure 4 is a flowchart of a business processing method provided by another embodiment of the present invention;
[0032] Figure 5a This is an application scenario diagram of a business processing method provided by an embodiment of the present invention;
[0033] Figure 5b is another application scenario diagram of a business processing method provided by an embodiment of the present invention;
[0034] Figure 5c is another application scenario diagram of a business processing method provided by an embodiment of the present invention;
[0035] Figure 5d is another application scenario diagram of a business processing method provided by an embodiment of the present invention;
[0036] Figure 5e is another application scenario diagram of a business processing method provided by an embodiment of the present invention;
[0037] Figure 5f is another application scenario diagram of a business processing method provided by an embodiment of the present invention;
[0038] Figure 5g is another application scenario diagram of a business processing method provided by an embodiment of the present invention;
[0039] Figure 5h is another application scenario diagram of a business processing method provided by an embodiment of the present invention;
[0040] Figure 5i is another application scenario diagram of a business processing method provided by an embodiment of the present invention;
[0041] Figure 5j is another application scenario diagram of a business processing method provided by an embodiment of the present invention;
[0042] Figure 5k is another application scenario diagram of a business processing method provided by an embodiment of the present invention;
[0043] Figure 5lis another application scenario diagram of a business processing method provided by an embodiment of the present invention;
[0044] Figure 5m is another application scenario diagram of a business processing method provided by an embodiment of the present invention;
[0045] Figure 5n is another application scenario diagram of a business processing method provided by an embodiment of the present invention;
[0046] Figure 5o is another application scenario diagram of a business processing method provided by an embodiment of the present invention;
[0047] Figure 5p is another application scenario diagram of a business processing method provided by an embodiment of the present invention;
[0048] Figure 5q is another application scenario diagram of a business processing method provided by an embodiment of the present invention;
[0049] Figure 5r is another application scenario diagram of a business processing method provided by an embodiment of the present invention;
[0050] Figure 5s is another application scenario diagram of a business processing method provided by an embodiment of the present invention;
[0051] Figure 5t is another application scenario diagram of a business processing method provided by an embodiment of the present invention;
[0052] Figure 5u is another application scenario diagram of a business processing method provided by an embodiment of the present invention;
[0053] Figure 6 is a flowchart of a business processing method provided by another embodiment of the present invention;
[0054] Figure 7 is a structural diagram of a service processing device provided by an embodiment of the present invention;
[0055] Figure 8 It is a schematic diagram of the structure of a terminal provided by an embodiment of the present invention. DETAILED DESCRIPTION
[0056] The technical solutions in the embodiments of the present invention will be described clearly and completely below in conjunction with the accompanying drawings in the embodiments of the present invention.
[0057] The embodiment of the present invention proposes a communication system, which may include at least: a receiving terminal, a payment terminal and at least one application server; the specific architecture diagram can be found in Figure 1As shown. Among them, the receiving terminal refers to the terminal used by the resource receiving user, that is, the terminal used to collect electronic resources; the payment terminal refers to the terminal used by the resource paying user, that is, the terminal used to transfer (or pay) electronic resources. The terminal here (such as the receiving terminal, the payment terminal, etc.) can be any of the following: portable devices such as smart phones, tablet computers, laptops, and desktop computers, etc.; electronic resources refer to: currencies equivalent to legal tender (such as RMB) and stored in electronic wallets (such as WeChat wallets and QQ wallets) in electronic form. Various applications (Applications) can be installed and run in the terminal, such as the first application and the second application. Among them, the first application refers to an application that does not provide related services about electronic resources, such as: an enterprise office application that provides office management services for the target enterprise (such as an enterprise WeChat application), a video application that provides video playback services, etc. The second application refers to an application that can provide related services about electronic resources, such as: a social application with a wide range of functions (such as WeChat applications, Tencent QQ applications), a third-party payment application, etc. In a specific implementation, the second application can directly provide users with relevant services regarding electronic resources by means of software function upgrades, or can indirectly provide users with embedded target sub-applications by means of embedded target sub-applications; the target sub-application here refers to a sub-application that can provide asset managers with relevant services regarding electronic resources. The so-called asset manager refers to an individual or organization that produces and operates related items, such as a merchant or individual; the so-called sub-application refers to an application that can be used without downloading and installing, such as a WeChat applet. Correspondingly, an application server refers to a server that provides corresponding services for various applications installed and running in a terminal; any application server can be an independent service device or a cluster device composed of multiple service devices. It should be noted that Figure 1 The architecture of the communication system involved in the embodiment of the present invention is merely exemplified and does not limit the specific architecture of the communication system.
[0058] Based on the above communication system, an embodiment of the present invention proposes a business processing scheme; the business processing scheme can be executed by the collection terminal in the above communication system, specifically as follows: the collection terminal can pre-add the application entry of the target sub-application in the second application in the first application, so that when the resource collection user in the first application has a collection demand, the application entry can trigger the collection terminal to switch from the first application to the target sub-application in the second application, and obtain a resource graphic code through the target sub-application; the resource graphic code here can also be called a collection graphic code, which refers to a graphic code used to collect electronic resources. Then, in response to the resource business instruction issued by the resource collection user to the resource payment user detected in the first application, notification data about the resource graphic code can be generated; the notification data is used to notify the resource payment user to scan the resource graphic code through the payment terminal to transfer the corresponding electronic resources to the resource collection user. It can be seen that the business processing scheme proposed in the embodiment of the present invention can realize the interaction between the first application and the target sub-application in the second application by setting the application entry of the target sub-application in the second application in the first application, and through this interaction, the first application can realize the collection business function with the help of the target sub-application, without performing software development work on the first application, which can effectively reduce the development cost of the first application.
[0059] Based on the above description, an embodiment of the present invention proposes a service processing method, which can be executed by a receiving terminal in the above communication system. Figure 2 The business processing method may include the following steps S201-S204:
[0060] S201 , in response to a trigger operation detected in a first application for an application entry of a target sub-application in a second application, switching from the first application to a target sub-application in the second application.
[0061] As can be seen from the foregoing, the receiving terminal can pre-add an application entry in the first application for entering the target sub-application in the second application. When the resource receiving user in the first application wants to receive electronic resources from the resource paying user, the application entry can be triggered in the first application to trigger the receiving terminal to switch applications; the resource receiving user here can be any user who has registered the first application (i.e., has a user account that logs in to the first application), and the triggering operation performed by the resource receiving user may include but is not limited to: a click operation of clicking on the application entry, a press operation of pressing the application entry, a voice operation of voice controlling the application entry to be in a triggered state, and so on. Accordingly, the receiving terminal can detect in real time in the first application whether the triggering operation exists; if the triggering operation is detected, the triggering operation can be responded to and switched from the first application to the target sub-application in the second application.
[0062] S202, displaying the resource service interface of the target sub-application.
[0063] S203: According to the resource business operation for the resource service item, a resource graphic code corresponding to the resource service item is obtained.
[0064] In steps S202-S203, after successfully switching from the first application to the target sub-application in the second application, the receiving terminal can display the resource service interface of the target sub-application, and provide one or more service items about electronic resources through the resource service interface of the target sub-application; for example, it can be used to collect resource service items of electronic resources by allowing other users to scan graphic codes, it can be used to add user service items for target asset operators, and so on; wherein, service users refer to users who provide labor services to the target asset operators (such as clerks who provide labor services to merchants). Then, the receiving terminal can detect in real time whether there is a resource business operation for the resource service item. If a resource business operation for the resource service item is detected, it can respond to this resource business operation and obtain the resource graphic code corresponding to the resource service item. The resource graphic code here can be a barcode, a QR code, etc. Among them, the barcode (such as Figure 3 A QR code is a graphic identifier that uses a certain geometric shape distributed in black and white on a two-dimensional plane according to a certain rule to record data symbol information.
[0065] In a specific implementation, after obtaining the resource graphic code, the receiving terminal can save the resource graphic code to the local space of the receiving terminal. In one embodiment, since the resource collecting user has a payment demand in the first application, the collecting terminal can also directly switch from the current interface of the target sub-application to the application interface of the first application after obtaining the resource graphic code, so that when the resource collecting user issues a resource service instruction to the resource paying user in the application interface of the first application, the first application can read the resource graphic code from the local space. Among them, the current interface of the target sub-application refers to the interface that displays the resource graphic code, and the current interface can be the same as the resource service interface or different from the resource service interface; the application interface of the first application can include any of the following: a session interface including a session window, a main interface, a message list interface, etc. In another embodiment, after obtaining the resource graphic code, the collecting terminal can detect whether there is an opening instruction of the first application opened by the resource collecting user within the validity period of the resource graphic code; if the opening instruction is detected, the opening instruction can be responded to and the application interface of the first application can be output.
[0066] In another specific implementation, after obtaining the resource graphic code, the receiving terminal can also switch from the target sub-application to the first application, and pass the resource graphic code from the target sub-application to the first application, so that when the subsequent resource collecting user issues a resource business instruction to the resource paying user through the first application, the first application can directly generate notification data about the resource graphic code.
[0067] S204, in response to a resource service instruction sent by the resource collecting user to the resource paying user detected in the first application, generating notification data about the resource graphic code.
[0068] The resource business instruction here may include an operation instruction for the resource collecting user to send the resource graphic code to the resource paying user. In one embodiment, the resource business instruction may be detected in a session window created in the first application based on the user account of the resource collecting user and the user account of the resource paying user. Specifically, the collecting terminal may create a session window in the first application based on the user account of the resource collecting user and the user account of the resource paying user; when an operation instruction for the resource collecting user to send the resource graphic code to the resource paying user is detected in the session window, the operation instruction may be used as a resource business instruction. Among them, the user account of the resource collecting user may be the account used by the resource collecting user to log in to the first application, and the user account of the resource paying user may also be the account used by the resource paying user to log in to the first application; for example, if the first application is an enterprise office application, the user account of the resource collecting user may be the enterprise account used by the resource collecting user to log in to the enterprise office application, and the user account of the resource paying user may also be the enterprise account used by the resource paying user to log in to the enterprise office application. Alternatively, the user account of the resource collection user may be the account used by the resource collection user to log in to the first application, and the user account of the resource payment user may be the account used by the resource payment user to log in to the second application; for example, if the first application is an enterprise office application and the second application is a social application, the user account of the resource collection user is the enterprise account used by the resource collection user to log in to the enterprise office application, and the user account of the resource payment user is the social account used by the resource payment user to log in to the social application. In another embodiment, the resource business instruction may also be detected in any interface (such as the main interface, the message list interface, etc.) in the first application. Specifically, the resource collection user may enter a voice-type operation instruction in the message list interface of the first application, such as "Please send the resource graphic code to the resource payment user"; at this time, the collection terminal may detect the operation instruction in the message list interface and use the operation instruction as a resource business instruction. For ease of explanation, the following description will be based on the detection of the resource business instruction in the conversation window of the first application as an example.
[0069] After detecting the resource service instruction, the receiving terminal may also generate notification data about the resource graphic code in response to the resource service instruction; the notification data here may include any of the following: image data containing the resource graphic code, identification data corresponding to the resource graphic code, and audio data generated according to the resource graphic code. After generating the notification data, the receiving terminal may also send the notification data to the payment terminal used by the resource payment user, so that the payment terminal outputs the resource graphic code according to the notification data, thereby notifying the resource payment user to scan the resource graphic code through the payment terminal to transfer the electronic resource to the resource receiving user. In one embodiment, if the user account of the resource receiving user is the account used by the resource receiving user to log in to the first application, and the user account of the resource payment user is the account used by the resource payment user to log in to the first application; then in this embodiment, the receiving terminal may send the notification data to the first server corresponding to the first application, so that the first server sends the notification data to the first application in the payment terminal used by the resource payment user. In another embodiment, if the user account of the resource collecting user is the account used by the resource collecting user to log in to the first application, and the user account of the resource paying user is the account used by the resource paying user to log in to the second application; then under this embodiment, the collecting terminal can generate a data forwarding request carrying notification data; and send the data forwarding request to the first server corresponding to the first application to request the first server to forward the notification data to the second server corresponding to the second application, so that the second server sends the notification data to the second application in the payment terminal used by the resource paying user; it can be seen from this that the embodiment of the present invention can also enable the resource collecting user to send notification data about the resource graphic code to the resource paying user across applications, without the resource collecting user manually switching from the first application to the second application, and the business operation is simple and efficient, which can effectively improve the business processing efficiency.
[0070] It should be noted that when the notification data includes image data, the receiving terminal may not send the notification data to the payment terminal, but directly display the resource graphic code in the image data in the user interface of the receiving terminal; in this case, the resource receiving user may show the resource graphic code displayed in the receiving terminal to the resource paying user, so that the resource paying user scans the resource graphic code displayed in the receiving terminal through the payment terminal to transfer the electronic resource to the resource receiving user. When the notification data includes audio data, the receiving terminal may not send the notification data (i.e., audio data) to the payment terminal through the server, but directly play the audio data through the speaker of the receiving terminal; in this case, the payment terminal may receive the audio data through its own microphone, obtain the resource graphic code based on the audio data, and then display the resource graphic code in the user interface of the payment terminal, so that the resource paying user scans the resource graphic code through the payment terminal to transfer the electronic resource to the resource receiving user.
[0071] The embodiment of the present invention can respond to the trigger operation of the application entry of the target sub-application in the second application detected in the first application, first switch from the first application to the target sub-application; secondly, display the resource service interface including the resource service item for collecting electronic resources, and obtain the resource graphic code corresponding to the resource service item according to the resource business operation for the resource service item; then, in response to the resource business instruction issued by the resource collecting user to the resource paying user detected in the first application, generate notification data about the resource graphic code, the notification data is used to notify the resource paying user to scan the resource graphic code through the payment terminal to transfer the electronic resource to the resource collecting user. In the above business processing process, by setting the application entry of the target sub-application in the second application in the first application, the interaction between the first application and the target sub-application in the second application can be realized, and through this interaction, the first application can realize the collection business function with the help of the target sub-application, without performing software development work on the first application, which can effectively reduce the development cost of the first application.
[0072] As more and more companies use enterprise office applications for office management, there will also be a large number of business needs for electronic resources (such as collection needs); for example, sales personnel in the company (i.e., enterprise users) need to collect electronic resources corresponding to a certain product sold from customers; for example, financial personnel in the company (i.e., enterprise users) need to collect electronic resources corresponding to cooperation fees from cooperative companies, and so on. In this case, the company can use the enterprise office application for office management while using a collection application with a collection function to perform collection business as an asset operator (such as a merchant). However, studies have shown that for companies that use enterprise office applications and other collection applications at the same time, since the organizational structure of the enterprise office application and the organizational structure of the other collection application are different, the two applications have different account systems, which is not convenient for the company to uniformly manage and maintain. Based on this, the embodiment of the present invention, based on the description of the above method embodiment, also proposes another method such as Figure 4 The business processing method shown; the business processing method can be executed by the collection terminal in the above-mentioned communication system. Through the business processing method, the organizational structure management of the enterprise office application and the organizational structure management of other collection applications can be combined, so that employees in the enterprise can use other collection applications in the enterprise office application to perform collection business.
[0073] It should be noted that the first application mentioned in the embodiments of the present invention refers to an enterprise office application that provides office management services for the target enterprise, and the resource collection user is the management user in the target enterprise who is responsible for managing the office management services; the second application includes a social application, and the target sub-application in the second application refers to a sub-application that can provide asset managers with related services related to electronic resources, that is, the target sub-application can be equivalent to a collection application. Figure 4 The business processing method may include the following steps S401-S414:
[0074] S401 : In response to a binding triggering event detected in a binding management page of a second application, output a binding entry page.
[0075] Since the organizational structures corresponding to the target sub-applications in the first application and the second application are different, the two have different account systems; for example, the account system of the first application includes the enterprise accounts of each enterprise user in the target enterprise used to log in to the first application, while the account system of the target sub-application includes the asset accounts registered and used by the target asset operator (such as a merchant) in the target sub-application, where the asset account refers to an account used to uniquely identify the target asset operator, such as a merchant number. Therefore, in order to facilitate the unified management and maintenance of the target enterprise and to enable the use of the target sub-application to perform payment collection business in the enterprise office application, the embodiment of the present invention can bind the enterprise information of the target enterprise using the first application and the asset account of the target asset operator corresponding to the target enterprise in the target sub-application in the second application, and set an application entry to the target sub-application in the first application.
[0076] In the specific implementation process, the management user can first log in to the application management end system (or application management end platform) of the first application, and query the enterprise identification (such as enterprise ID) of the target enterprise in the application management end system of the first application; then, log in to the application management end system of the second application, and open the binding management page of the application management end system of the second application, which may include a binding entry button; the management user can trigger the receiving terminal to switch from the binding management page to the binding entry page by clicking or pressing the binding entry button, such as Figure 5a Accordingly, the receiving terminal may output a binding entry page in response to a binding trigger event detected in the binding management page of the second application; the binding trigger event here may include: an event of detecting a trigger operation for a binding entry button.
[0077] S402, obtaining binding application information in the binding entry page.
[0078] S403: Send a binding application request carrying binding application information to the second server.
[0079] In steps S402-S403, after the receiving terminal outputs the binding entry interface, the management user can fill in the binding application information in the binding entry interface; accordingly, the receiving terminal can obtain the binding application information in the binding entry page. The binding application information here at least includes: the corporate information of the target enterprise and the asset account of the target asset operator to be bound; wherein the corporate information may include the corporate logo, corporate logo certification subject, corporate name, etc. After the receiving terminal obtains the binding application information, it can send a binding application request carrying the binding application information to the second server to request the second server to generate an authorization application form based on the binding application information, add the authorization application form to the authorization binding list of the target enterprise, and review the authorization qualification of the authorization application form.
[0080] Accordingly, after receiving the binding application request, the second server may verify the legitimacy of the binding application request based on the binding application information. If the verification is successful, the binding application information may be entered into the authorized binding database; wherein, the specific implementation method of entering the binding application information into the authorized binding database may be: generating an authorization application form based on the binding application information, and adding the authorization application form to the authorization binding list of the target enterprise, wherein the authorization application form at least includes the corporate information of the target enterprise and the asset account number of the target asset operator. If the verification fails, the binding application request may be rejected and a corresponding error code may be returned. It should be noted that, in one implementation, after the second server adds the authorization application form to the authorization binding list of the target enterprise, it may also send a successful application notification to the receiving terminal; accordingly, if the receiving terminal receives the successful application notification returned by the second server, it may output the successful application notification in the application management end system of the second application, such as Figure 5b In this case, when the management user switches to the binding entry interface again, the authorization application form will be presented in the binding entry interface, as shown in Figure 5c In another embodiment, the second server may also send an application acceptance notification to the receiving terminal; accordingly, if the receiving terminal receives the application acceptance notification returned by the second server, the application acceptance notification may be output in the second application, such as Figure 5d As shown in the left figure; the application acceptance notice is issued by the second server after the authorization application form is added to the authorization binding list of the target enterprise. The application acceptance notice may include at least one of the following contents: acceptance prompt information (such as "The application you submitted has been accepted, please wait for review, the review time is 1-3 working days"), asset account number, operator name (such as merchant name), enterprise name, enterprise logo, enterprise logo certification entity, etc.
[0081] After the second server adds the authorization application form to the authorization binding list of the target enterprise, it can review the authorization qualifications of the authorization application form. Specifically, the second server obtains the authentication information of the target enterprise based on the enterprise identification in the enterprise information, and obtains the input information entered by the target asset operator when registering and applying for the asset account based on the asset account. By comparing whether the authentication information and the input information are the same, the authorization qualification of the authorization application form is reviewed. If they are the same, the review is passed; at this time, the second server can update the authorization status corresponding to the authorization application form to the pending authorization status. If they are not the same, the review fails; at this time, the second server can update the authorization status of the authorization application form to the failed review status. After the review is completed, the second server can also send the review results to the receiving terminal; accordingly, if the receiving terminal receives the review results sent by the second server, it can output the review results in the application management end system of the second application, such as Figure 5d As shown in the right figure; the audit result is issued by the second server after reviewing the authorization qualifications of the authorization application form. The audit result is used to guide the management user to the application management end system of the first application to continue the next operation (such as authorization operation).
[0082] S404, obtaining the authorization application form to be authorized of the target enterprise, and displaying the authorization application form in the authorization management page.
[0083] After receiving the audit result, the management user can log in to the application management end system of the first application and enter the application management page in the application management end system of the first application; accordingly, the receiving terminal can obtain the authorization binding list of the target enterprise from the second server through the first server, and display the authorization binding list in the application management page; the authorization binding list includes the authorization application forms to be authorized and the processed historical application forms. The management user can select the authorization application form to be authorized from the authorization binding list. At this time, the receiving terminal can respond to the management user's selection operation, obtain the authorization application form to be authorized from the authorization binding list, switch from the application management page to the authorization management page, and display the authorization application form on the authorization management page, such as Figure 5e shown.
[0084] S405: In response to the confirmation operation on the authorization application form, sending an authorization request to the second server corresponding to the second application.
[0085] After the receiving terminal displays the authorization application form on the authorization management page, the management user can check whether the information in the authorization application form is correct; if it is correct, the management user can click the authorization button in the authorization management page to perform a confirmation operation on the authorization application form. Accordingly, if the receiving terminal detects a confirmation operation for the authorization application form, it can generate an authorization request and send the authorization request to the second server corresponding to the second application to request the second server to update the authorization status of the authorization application form from the pending authorization status to the authorized status to complete the binding between the target enterprise and the target asset operator. It can be seen from step S404 that the authorization application form is displayed on the authorization management page of the first application; accordingly, the specific implementation method of step S405 can be: sending the authorization request to the first server corresponding to the first application so that the first server performs a legality check on the authorization request, and after the legality check passes, forwarding the authorization request to the second server corresponding to the second application. Among them, the authorization request can carry the following content: enterprise identification, user identification of the management user, application form number (such as application form ID), asset account, authorization status (authorized status), operation timestamp and other information.
[0086] Accordingly, after receiving the authorization request, the second server can verify the legitimacy of the authorization request; if the verification is successful, the authorization application form corresponding to the application form identifier can be read from the authorization binding database, and the authorization status of the authorization application form can be updated from the pending authorization status to the authorized status to complete the binding between the target enterprise and the target asset operator. Then, the second server can also return an authorization success notification to the first server, so that the first server sends the authorization success notification to the receiving terminal. Accordingly, if the receiving terminal receives the authorization success notification returned by the first server, it can output the authorization success notification in the form of a pop-up window on the authorization management page, such as Figure 5f shown.
[0087] S406, after successfully completing the binding between the target enterprise and the target asset operator, add an application entry of the target sub-application in the first application.
[0088] If the receiving terminal receives the authorization success notification returned by the first server, it can be determined that the binding between the target enterprise and the target asset operator is successfully completed. The authorization success notification is sent by the second server to the first server. At this time, the receiving terminal can add the application entry of the target sub-application in the first application, such as Figure 5g In one embodiment, after the receiving terminal adds the application entry of the target sub-application in the first application, it generates a new entry notification about the application entry of the target sub-application; and outputs the new entry notification in the first application to notify the management user that the application entry of the target sub-application has been added in the first application.
[0089] It should be noted that the pages mentioned in the above steps S401-S406 (such as binding management page, binding entry page, authorization management page, etc.) all refer to pages presented in the form of web pages, such as traditional browser web pages, H5 pages, etc.; the H5 page here refers to the web page of the mobile terminal. After the management user receives the notification of the newly added entry, he can perform a trigger operation on the application entry in the first application to enter the target sub-application, so as to perform subsequent operations.
[0090] S407 , in response to a triggering operation on an application entry of a target sub-application in the second application detected in the first application, switching from the first application to the target sub-application in the second application.
[0091] S408, displaying the resource service interface of the target sub-application.
[0092] In steps S407-S408, when the management user has business needs related to electronic resources, the application portal can be triggered to trigger the receiving terminal to switch from the first application to the target sub-application in the second application and display the resource service interface of the target sub-application. In one embodiment, after switching from the first application to the target sub-application in the second application, the receiving terminal can directly display the resource service interface, such as Figure 5h As shown. In another embodiment, after the collection terminal switches from the first application to the target sub-application in the second application, the collection terminal may first display the home service interface of the target sub-application, and provide one or more service items in the home interface to meet the needs of resource collection users; for example: store service items to meet the needs of resource collection users to view asset stores, code scanning service items to meet the needs of resource collection users to collect payments by scanning codes, material purchase service items to meet the needs of resource collection users to purchase goods and materials, query service items to meet the needs of users to query collection records, and so on. Then, in response to the trigger operation for the store service item, switch from the home service interface to the resource service interface, such as Figure 5i As shown; or, in response to a trigger operation for a store service item, switching from the home service interface to the store service interface, the store service interface may include a store logo of at least one store; then according to a selection operation for at least one store logo detected in the store service interface, switching from the store service interface to the resource service interface of the store corresponding to the selected store logo, such as Figure 5j It should be noted that, in other embodiments, the resource service items may also be directly displayed in the home service interface of the target sub-application, such as Figure 5k As shown; in this case, the home page service interface can be used as the resource service interface.
[0093] The resource service interface of the target sub-application may include one or more service items, for example: a resource service item that can be used to collect electronic resources by allowing other users to scan graphic codes, a user service item that can be used to add service users for the target asset operator, and so on. When the management user wants to use the enterprise user (other users except the management user) in the target enterprise as a new service user of the target asset operator, and add an application entry for the enterprise user to enter the target sub-application in the first application used by the enterprise user, the corresponding user addition operation can be performed on the user service item; accordingly, the collection terminal can respond to the user addition operation and execute the subsequent steps S409-S412. When the management user wants to collect electronic resources from the resource payment user, the corresponding resource business operation can be performed on the resource service item; accordingly, the collection terminal can respond to the resource business operation and execute the subsequent steps S413-S414.
[0094] S409: Output a user adding interface according to the user adding operation for the user service item.
[0095] In a specific application, the management user may first perform a trigger operation on the user service item to trigger the receiving terminal to switch from the resource service interface to the user details interface, such as Figure 5l As shown; the user details interface may include a user add button; optionally, the user details interface may also include the user identifier of the added service user, such as the service user's work number, the service user's name, the social account used by the service user in the second application, or the enterprise account used by the service user in the first application. The management user may perform a trigger operation on the user add button to trigger the receiving terminal to switch from the user details interface to the user add interface; accordingly, the receiving terminal may respond to the trigger operation on the user add button and call the selection component of the first application to output the user add interface, such as Figure 5m In this implementation, the user adding operation in the embodiment of the present invention may include: triggering operation on user service items, and triggering operation on user adding button. It should be noted that the user adding interface is output through the first application, and the user adding interface may include the enterprise account of at least one enterprise user under the target enterprise in the first application.
[0096] S410, determining the target enterprise account of the selected target enterprise user, and generating a user adding request carrying the target enterprise account and the asset account of the target asset operator.
[0097] S411, sending the user adding request to the second server.
[0098] S412, receiving a notification of successful addition of the service user returned by the second server, and outputting the notification of successful addition of the service user.
[0099] In steps S410-S412, the management user can select one or more enterprise accounts in the user adding interface, and the receiving terminal can determine the target enterprise account of the selected target enterprise user according to the selection operation of the management user on the one or more enterprise accounts, such as Figure 5n As shown; and after detecting the management user's confirmation operation on the target enterprise account (such as the triggering operation of the "Confirm" button in the user adding interface), a user adding request carrying the target enterprise account and the asset account of the target asset operator is generated. Then, the receiving terminal can send the user adding request to the second server to request the second server to associate and store the target enterprise account with the asset account, so as to use the target enterprise user as a new service user of the target asset operator. Accordingly, after receiving the user adding request, the second server can detect whether the target enterprise user is a legitimate user by calling the first server; if it is a legitimate user, the target enterprise account and the asset account of the target enterprise user can be associated and stored. Optionally, if the target enterprise user is a legitimate user, the second server registers the target enterprise account of the target enterprise user in the second application, so that the subsequent target enterprise user can use the target enterprise account to log in to the second application, and use the target enterprise account in the second application and other users in the second application for conversational communication.
[0100] After the second server associates and stores the target enterprise account and the asset account of the target enterprise user, it can also send a notification of successfully adding the service user to the receiving terminal; accordingly, the receiving terminal can receive the notification of successfully adding the service user returned by the second server and output the notification of successfully adding the service user. In one embodiment, after receiving the notification of successfully adding the service user, the receiving terminal can directly output the notification of successfully adding the service user in the user adding interface of the first application, such as Figure 5o In another embodiment, the receiving terminal may output the notification of successfully adding the service user in the user details interface of the target sub-application; specifically, the receiving terminal may first switch from the user adding interface of the first application to the user details interface of the target sub-application, and output the notification of successfully adding the service user in the user details interface of the target sub-application, such as Figure 5p shown.
[0101] Optionally, after associating and storing the target enterprise account and asset account of the target enterprise user, the second server may also send a user notification request to the first server; after receiving the user notification request, the first server may verify the legitimacy of the user notification request. If the verification is successful, the first server may send a user notification prompt to the first application used by the target enterprise user, so that the first application used by the target enterprise user adds the application entry of the target sub-application and outputs the user notification prompt, such as Figure 5q As shown; the user notification prompt may include at least one of the following content: prompt information (such as "Congratulations on becoming a service user for external payment"), store name, content summary, remarks information, etc. Among them, the content summary can be used to explain the functional information of the target sub-application to the target enterprise users, which may specifically include information such as "After the customer scans the resource graphic code to pay, you will receive a payment notification sent by the first application, and you can also enter the "Workbench-External Payment" in the first application to view the payment record and other functions" and similar information; the remarks information can be used to explain the use of the target sub-application to the target enterprise users, which may specifically include information such as "Use it directly in the "Workbench-External Payment" in the first application" and similar information.
[0102] S413, according to the resource business operation for the resource service item, obtaining the resource graphic code corresponding to the resource service item.
[0103] In an embodiment of the present invention, the resource graphic code corresponding to the resource service item may be pre-set, or may be generated and updated in real time or periodically. In the specific implementation process, the receiving terminal may send a graphic code request to the second server according to the resource business operation for the resource service item. Accordingly, the second server may respond to the graphic code request, obtain a pre-set resource graphic code associated with the asset account, or generate a resource graphic code associated with the asset account in real time; and send the resource graphic code to the receiving terminal; and the receiving terminal may receive the resource graphic code sent by the second server. After obtaining the resource graphic code according to the resource business operation for the resource service item, the receiving terminal may also display the resource graphic code in the user interface, such as Figure 5r After the receiving terminal displays the resource graphic code, the management user can also save the resource graphic code to the local space of the receiving terminal.
[0104] It should be noted that in other embodiments, if the resource graphic code corresponding to the resource service item is stored in the local space of the receiving terminal, the resource graphic code corresponding to the resource service item can also be directly obtained from the local storage space; or, a resource graphic code can be generated in real time by the receiving terminal.
[0105] S414, in response to a resource service instruction sent by the resource collecting user to the resource paying user detected in the first application, generating notification data about the resource graphic code.
[0106] The management user can open a session window created based on the user account of the management user (i.e., the enterprise account) and the user account of the resource payment user in the first application running on the receiving terminal, and send the resource graphic code to the resource payment user through the session window, such as Figure 5sAs shown in the left figure of . At this time, the receiving terminal can use the operation instruction of the resource receiving user (here, the management user) in the first application to send the resource graphic code to the resource paying user as a resource business instruction; and in response to the resource business instruction, generate notification data about the resource graphic code, and send the notification data to the payment terminal used by the resource paying user; the notification data is used to notify the resource paying user to transfer the electronic resource to the resource collecting user by scanning the resource graphic code through the payment terminal. Accordingly, after receiving the notification data, the payment terminal used by the resource paying user can output the resource graphic code according to the notification data in the corresponding session window in the first application or the second application in the payment terminal. Specifically, when the user account of the resource payment user is the corporate account used by the resource payment user to log in to the first application, the payment terminal can output the resource graphic code according to the notification data in the first session window between the resource payment user and the resource collecting user in the first application, and the first session window is a session window created by the payment terminal in the first application based on the corporate account of the resource payment user and the corporate account of the resource collecting user; when the user account of the resource payment user is the social account used by the resource payment user to log in to the second application (i.e., the account for logging in to the second application), the payment terminal can output the resource graphic code according to the notification data in the second session window between the resource payment user and the resource collecting user in the second application, and the second session window is a session window created in the second application of the payment terminal based on the social account of the resource payment user and the corporate account of the resource collecting user, such as Figure 5s As shown in the right figure.
[0107] For the sake of convenience, the payment process on the payment terminal side is described by taking the output of the resource graphic code according to the notification data in the second session window as an example: after receiving the resource graphic code, the resource payment user can scan the resource graphic code through the second application in the payment terminal to trigger the payment terminal to output the payment interface; then, the resource payment user can pay for the corresponding electronic resources in the payment interface, such as Figure 5t As shown. Accordingly, the payment terminal may send a payment request to the second server in response to the payment operation of the resource payment user; the payment request carries the target number of electronic resources, and the payment request is used to request the second server to transfer the target number of electronic resources from the account of the resource payment user to the account of the target asset operator. After receiving the payment request, the second server may transfer the target number of electronic resources from the account of the resource payment user to the account of the target asset operator; and send a payment notification request to the first server to notify the first server to send the collection notification to the first application in the collection terminal used by the resource collection user, so that the first application in the collection terminal can output the collection notification to prompt the resource collection user that the electronic resources paid by the resource payment user have been successfully received, such as Figure 5u shown.
[0108] The embodiment of the present invention can respond to the trigger operation of the application entry of the target sub-application in the second application detected in the first application, first switch from the first application to the target sub-application; secondly, display the resource service interface including the resource service item for collecting electronic resources, and obtain the resource graphic code corresponding to the resource service item according to the resource business operation for the resource service item; then, in response to the resource business instruction issued by the resource collecting user to the resource paying user detected in the first application, generate notification data about the resource graphic code, the notification data is used to notify the resource paying user to scan the resource graphic code through the payment terminal to transfer the electronic resource to the resource collecting user. In the above business processing process, by setting the application entry of the target sub-application in the second application in the first application, the interaction between the first application and the target sub-application in the second application can be realized, and through this interaction, the first application can realize the collection business function with the help of the target sub-application, without performing software development work on the first application, which can effectively reduce the development cost of the first application.
[0109] To better understand the above Figure 4 The method embodiment shown below is combined with Figure 6 The flowchart shown in the figure further illustrates the business processing method mentioned in the above embodiment; in this process, the target asset operator is a merchant and the asset account is a merchant number as an example for illustration; it can be roughly divided into the following four sub-processes:
[0110] [1]. The process of applying for the first application to bind with the merchant number and the first application to pull the authorization binding list:
[0111] The management user of the target enterprise (i.e., the enterprise administrator) first logs in to the application management end system of the first application, and queries the enterprise identity of his own enterprise (such as the enterprise's APPID) in the application management end system of the first application; then logs in to the application management end system of the second application to apply for binding the enterprise identity. Specifically, you can first enter the product center-APPID binding management page; secondly, you can click the "+ Add Authorization Application Form" button (i.e., the binding entry button) to enter the binding entry page; then, you can fill in and submit the binding application information according to the page prompts. Correspondingly, the receiving terminal can form the binding application information into a binding application request through the binding entry page; the binding application request can be a data packet, and the package body can contain fields such as merchant number, merchant credential, APPID, APPID authentication subject, account type, application reason, operation timestamp, etc.; then, the binding application request is encrypted and sent to the second server corresponding to the second application.
[0112] After receiving the binding application request, the second server can conduct a qualification review: first, according to the content included in the package body of the binding application request, make a judgment on whether the binding application request is legal: for illegal operations, refuse to execute and return the corresponding error code in the reply package; for legal requests, enter the binding application materials into the authorization binding database, that is, enter the authorization application form corresponding to the binding application materials into the authorization binding list. Secondly, the second server can send a review notice to the relevant reviewer, and the reviewer goes to the public platform of the second application according to the enterprise logo to obtain the authentication information corresponding to the enterprise logo, and compares the authentication information with the input information entered when applying for the merchant number; if the authentication information and the input information are the same, the review is passed; otherwise, the review is not passed. If the review is passed, the second server can update the status of the authorization application form corresponding to the binding application materials in the authorization binding database to the status of the authorization application form corresponding to the binding application materials in the authorization binding database to the status of the authorization application form corresponding to the binding application materials in the authorization binding database to the status of the authorization application form corresponding to the authorization application form; if the review is not passed, the status of the authorization application form is updated to the status of the authorization application form. Then, the second server can send the review result to the second application to inform the management user of the review result, and guide the management user to the application management end system of the first application to continue the next authorization operation.
[0113] The management user logs in to the application management end system of the first application to authorize, and the receiving terminal pulls the authorization binding list through the application management end system of the first application. Specifically, the management user can click to enter the application management page in the application management end system of the first application; at this time, the receiving terminal can generate a list request package for pulling the authorization binding list through the application management page, and the package body of the list request package can contain fields such as enterprise identification, operator ID, operation timestamp, etc. The list request package is encrypted and sent to the first server corresponding to the first application. After receiving the list request package, the first server determines whether the list request package is legal based on the content of the list request package: for illegal operations, it refuses to execute and returns the corresponding error code in the return packet; for legal requests, it groups a list pull package, and the package body of the list pull package can contain the enterprise identification, encrypt the list pull package and send it to the second server. Correspondingly, after receiving the list pull package, the second server determines whether the list pull package is legal based on the content of the list pull package: for illegal operations, it refuses to execute and returns the corresponding error code in the reply package; for legal requests, it reads the authorization binding list corresponding to the enterprise identity from the authorization binding database (including application forms in various states such as authorized, pending authorization, and unapproved), and returns the package to the first server. After receiving the reply package from the second server, the first server can send the authorization binding list to the application management end system of the first application in the receiving terminal.
[0114] [2]. Agree to the authorization binding process:
[0115] The management user logs in to the application management system of the first application and clicks to enter the application management page; at this time, the application management page can display the authorization binding list. The management user can select an authorization application form to be authorized from the authorization application list to enter the authorization management page; and click the "Authorize" button on the authorization management page. At this time, the receiving terminal can initiate an authorization request through the authorization management page. The authorization request can be a data packet, the package body contains fields such as enterprise identification, operator ID, application form ID, merchant number, authorization status, operation timestamp, etc.; encrypt the authorization request and send it to the first server.
[0116] After the first server receives the authorization request, it determines whether the authorization request is legal based on the content of the authorization request: if it is an illegal operation, it refuses to execute and returns the corresponding error code in the reply package; for a legal request, it forms an application authorization request package, the package body of which contains the enterprise ID, application form ID, merchant number, and authorization status; then, the first server encrypts the application authorization request package and sends it to the second server. After the second server receives the application authorization request package, it determines whether the application authorization request package is legal based on the content of the application authorization request package: if it is an illegal operation, it refuses to execute and returns the corresponding error code in the reply package; for a legal request, it reads the authorization application form corresponding to the application form ID from the authorization binding database, and updates the authorization status of the authorization application form to the authorized status, thereby completing the binding of the enterprise ID and the merchant number (only after binding can the enterprise use the relevant functions of the merchant number in the target sub-application of the second application); and can form a successful authorization notification and return it to the first server. After the first server receives the authorization success notification returned by the second server, it can store the binding relationship between the enterprise identification and the merchant number; and can also send the authorization success notification to the receiving terminal, so that the receiving terminal outputs the authorization success notification in the form of a pop-up window in the authorization management page, thereby prompting the management user that the authorization has been successful.
[0117] In addition, after receiving the authorization success notification returned by the second server, the first server also queries the service users of the merchant number from the second server; specifically, the user list request packet of the service user can be queried, and the package body of the user list request packet includes the enterprise logo and the merchant number, and the user list request packet is encrypted and sent to the second server. After receiving the user list request packet, the second server judges whether the user list request packet is legal according to the content of the user list request packet: for illegal operations, it refuses to execute and returns the corresponding error code in the reply packet; for legal requests, it reads the user list from the service user database under the merchant number, and the user list includes at least one user logo of the service user (such as a social application account); and then returns the user list to the first server. After receiving the user list, the first server can store the user list in the database and record the identity of each service user; then notify the first application corresponding to each service user in the user list of the newly added target sub-application application entry (such as the "external collection" entry), and output the newly added entry notification to notify each service user that the application entry of the target sub-application has been added. It should be noted that if it is used for the first time, that is, when the management user has not added a service user, the user list can only include the user logo of the management user.
[0118] [3]. The process of managing users to add new service users:
[0119] In the workbench of the first application, the management user clicks the application entrance (i.e., the "external collection" entrance) to enter and log in to the target sub-application; and clicks "asset store" to enter the store service interface (if there is no store, a new store can be created), and then selects and clicks a store logo to enter the resource service page, and clicks "add user" (i.e., user service item). At this time, the target sub-application in the receiving terminal can call up the selection component of the first application and output the user addition interface; the management user selects an enterprise user's corporate account and performs a confirmation operation, and at this time the selection component can return the selected enterprise user's corporate account to the target sub-application. Then, the receiving terminal can form a user addition request through the target sub-application. The user addition request can be a data packet, and the package body of the user addition request contains fields such as corporate identification, management user's corporate account, merchant number, store id, target corporate account of the target corporate user (i.e., the newly added service user), and operation timestamp; encrypt the user addition request and send it to the second server. After receiving the user addition request, the second server requests the first server to confirm whether the selected target corporate user is legal; after the first server verifies the legality of the target corporate user, it can return the verification result to the second server.
[0120] After the second server receives the verification result: for the target enterprise user that does not meet the legality check, the target enterprise user can be rejected as a new service user, and the corresponding error code is returned in the reply package; for the target enterprise user that meets the legality check, the target enterprise account of the target enterprise user can be stored under the merchant number store id, so as to associate the target enterprise account of the target enterprise account with the merchant number. Then, a notification of successful addition of the service user can be returned to the receiving terminal used by the management user to notify the management user that the target sub-application has successfully added a new service user; and a group user notification request is sent to the first server, and the package body of the user notification request contains fields such as enterprise identification, administrator ID, merchant number, store name, enterprise member id (newly added service user), operation timestamp, etc. After the first server receives the user notification request, it determines whether the user notification request is legal according to the content of the user notification request: for illegal operations, it refuses to execute and returns the corresponding error code in the reply package; for legal requests, it sends a group user notification prompt, and sends the user notification prompt to the first application corresponding to the target enterprise user (i.e., the new service user); after the first application of the target enterprise user receives the user notification prompt, it can open the application entrance of the target sub-application in the workbench of the first application.
[0121] [4] The process of a new service user (i.e., target enterprise user) using the target sub-application in the first application to collect payment from the paying customer in the second application:
[0122] After the new service user has connected with the paying customer in the first application to complete the payment matters, such as negotiating the number of electronic resources to be paid, he can perform the following click operations in the workbench of the first application: click the application entrance to enter the target sub-application, click "My Store" to enter the store service interface, select and click a store to enter the resource service interface, click "Store Payment Code" to obtain the resource graphic code, save the resource graphic code, and send the resource graphic code to the paying customer through the first application. After the paying customer receives the resource graphic code in the second application of the target terminal he uses, he can scan the code to pay; specifically, he can scan the resource graphic code through the second application to enter the payment interface, enter the consumption amount and pay. After confirming that the payment has been received, the second server can assemble an arrival notification request and send the arrival notification request to the first server. The arrival notification request can contain fields such as enterprise identification, merchant number, store name, enterprise member id (service user), payment amount, customer nickname, remarks, operation timestamp, etc. After the first server receives the payment notification request, it determines whether the payment notification request is legal based on the content of the payment notification request: if it is an illegal operation, it refuses to execute and returns the corresponding error code in the response packet; if it is a legal request, it assembles a payment notification and sends it to the first application corresponding to the enterprise user; at this point, the transaction between the new service user and the paying customer is completed.
[0123] Based on the description of the above service processing method embodiment, the embodiment of the present invention further discloses a service processing device, which may be a computer program (including program code) running in a terminal. The service processing device may execute Figure 2 or Figure 4 See the method shown in Figure 7 , the service processing device may run the following units:
[0124] The processing unit 101 is configured to switch from the first application to the target sub-application in the second application in response to a trigger operation of an application entry for a target sub-application in the second application detected in the first application;
[0125] A display unit 102, used to display the resource service interface of the target sub-application, wherein the resource service interface includes resource service items for collecting electronic resources;
[0126] The processing unit 101 is used to obtain the resource graphic code corresponding to the resource service item according to the resource business operation for the resource service item;
[0127] The processing unit 101 is used to generate notification data about the resource graphic code in response to a resource business instruction issued by the resource collecting user to the resource paying user detected in the first application, and the notification data is used to notify the resource paying user to scan the resource graphic code through the payment terminal to transfer the electronic resources to the resource collecting user.
[0128] In one embodiment, the resource service instruction is detected in a session window created in the first application according to the user account of the resource collection user and the user account of the resource payment user; the user account of the resource collection user is the account used by the resource collection user to log in to the first application, and the user account of the resource payment user is the account used by the resource payment user to log in to the second application;
[0129] The notification data includes any one of the following: image data including the resource graphic code, identification data corresponding to the resource graphic code, or audio data generated according to the resource graphic code.
[0130] In another embodiment, the first application includes an enterprise office application that provides office management services for the target enterprise, and the resource collection user is a management user in the target enterprise who is responsible for managing the office management services;
[0131] The second application includes a social application, and the target sub-application in the second application refers to a sub-application that provides asset managers with services related to electronic resources.
[0132] In another implementation manner, the processing unit 101 may also be used for:
[0133] Obtaining an authorization application form to be authorized for the target enterprise, and displaying the authorization application form on an authorization management page, wherein the authorization application form at least includes the enterprise information of the target enterprise and the asset account number of the target asset operator;
[0134] In response to the confirmation operation on the authorization application form, sending an authorization request to the second server corresponding to the second application to request the second server to update the authorization status of the authorization application form from a pending authorization status to an authorized status, so as to complete the binding between the target enterprise and the target asset operator;
[0135] After successfully completing the binding between the target enterprise and the target asset operator, an application entry of the target sub-application is added to the first application.
[0136] In another embodiment, the authorization application form is displayed on the authorization management page of the first application; accordingly, when the processing unit 101 is used to send the authorization consent request to the second server corresponding to the second application, it can be specifically used to: send the authorization consent request to the first server corresponding to the first application, so that the first server performs a legitimacy check on the authorization consent request, and after the legitimacy check passes, forward the authorization consent request to the second server corresponding to the second application;
[0137] The processing unit 101 may also be used to: if an authorization success notification returned by the first server is received, determine that the binding between the target enterprise and the target asset operator is successfully completed; the authorization success notification is sent by the second server to the first server.
[0138] In another implementation manner, the processing unit 101 may also be used for:
[0139] After adding the application entry of the target sub-application in the first application, generating a new entry notification about the application entry of the target sub-application;
[0140] A new entry notification is output in the first application to notify the management user that an application entry of the target sub-application has been added in the first application.
[0141] In another embodiment, before obtaining the authorization application form to be authorized for the target enterprise, the processing unit 101 may also be used to:
[0142] In response to a binding trigger event detected in the binding management page of the second application, outputting a binding entry page;
[0143] Obtaining binding application materials on the binding entry page, the binding application materials at least including: the enterprise information of the target enterprise and the asset account number of the target asset operator to be bound;
[0144] Send a binding application request carrying the binding application information to the second server to request the second server to generate an authorization application form based on the binding application information, add the authorization application form to the authorization binding list of the target enterprise, and review the authorization qualification of the authorization application form.
[0145] In another implementation manner, the processing unit 101 may also be used for:
[0146] If an application acceptance notice returned by the second server is received, the application acceptance notice is output in the second application; the application acceptance notice is issued by the second server after adding the authorization application form to the authorization binding list of the target enterprise;
[0147] If the audit result sent by the second server is received, the audit result is output in the application management end system of the second application; the audit result is sent by the second server after auditing the authorization qualification of the authorization application form.
[0148] In another embodiment, the resource service interface further includes a user service item for adding a service user for the target asset operator; accordingly, after displaying the resource service interface of the target sub-application, the processing unit 101 may also be used to:
[0149] Outputting a user adding interface according to the user adding operation for the user service item, the user adding interface including an enterprise account of at least one enterprise user under the target enterprise in the first application;
[0150] Determine the target enterprise account of the selected target enterprise user, and generate a user adding request carrying the target enterprise account and the asset account of the target asset operator;
[0151] Sending the user adding request to the second server to request the second server to associate and store the target enterprise account with the asset account, so as to use the target enterprise user as a new service user of the target asset operator;
[0152] A notification of successfully adding a service user is received from the second server, and the notification of successfully adding a service user is output.
[0153] According to one embodiment of the present invention, Figure 2 or Figure 4 Each step involved in the method shown can be performed by Figure 7 The business processing device shown in FIG. 1 is executed by each unit in the business processing device shown in FIG. Figure 2 The steps S201, S203-S204 shown in FIG. 1 can be performed by Figure 7 The processing unit 101 shown in FIG. 1 is executed, and step S202 can be performed by Figure 7 , the display unit 102 shown in is executed; for example, Figure 4 Steps S401-S407 and steps S409-S414 shown in Figure 7 The processing unit 101 shown in FIG. 1 is executed, and step S408 can be performed by Figure 7 According to another embodiment of the present invention, Figure 7 The various units in the business processing device shown can be combined into one or several other units separately or in whole, or one (some) of the units can be further divided into multiple functionally smaller units to form the same operation, which can achieve the same operation without affecting the realization of the technical effects of the embodiments of the present invention. The above-mentioned units are divided based on logical functions. In practical applications, the function of one unit can also be implemented by multiple units, or the functions of multiple units can be implemented by one unit. In other embodiments of the present invention, other units can also be included based on the business processing device. In practical applications, these functions can also be implemented with the assistance of other units, and can be implemented by the collaboration of multiple units.
[0154] According to another embodiment of the present invention, the program can be executed by running a program on a general computing device such as a computer including a central processing unit (CPU), a random access memory medium (RAM), a read-only memory medium (ROM), and other processing elements and storage elements. Figure 2 or Figure 4 A computer program (including program code) for each step involved in the corresponding method shown in Figure 7 The business processing device shown in the embodiment of the present invention is used to implement the business processing method of the embodiment of the present invention. The computer program can be recorded on a computer-readable recording medium, for example, and loaded into the above-mentioned computing device through the computer-readable recording medium and run therein.
[0155] The embodiment of the present invention can respond to the trigger operation of the application entry of the target sub-application in the second application detected in the first application, first switch from the first application to the target sub-application; secondly, display the resource service interface including the resource service item for collecting electronic resources, and obtain the resource graphic code corresponding to the resource service item according to the resource business operation for the resource service item; then, in response to the resource business instruction issued by the resource collecting user to the resource paying user detected in the first application, generate notification data about the resource graphic code, the notification data is used to notify the resource paying user to scan the resource graphic code through the payment terminal to transfer the electronic resource to the resource collecting user. In the above business processing process, by setting the application entry of the target sub-application in the second application in the first application, the interaction between the first application and the target sub-application in the second application can be realized, and through this interaction, the first application can realize the collection business function with the help of the target sub-application, without performing software development work on the first application, which can effectively reduce the development cost of the first application.
[0156] Based on the description of the above method embodiment and device embodiment, the embodiment of the present invention further provides a terminal. Figure 8 The terminal at least includes a processor 201, an input device 202, an output device 203, and a computer storage medium 204. The processor 201, the input device 202, the output device 203, and the computer storage medium 204 in the terminal can be connected via a bus or other means. The first application and the second application can also be used in the terminal, and the first application includes an application entry for entering a target sub-application in the second application.
[0157] The computer storage medium 204 may be stored in a memory of the terminal. The computer storage medium 204 is used to store a computer program. The computer program includes program instructions. The processor 201 is used to execute the program instructions stored in the computer storage medium 204 . The processor 201 (or CPU (Central Processing Unit)) is the computing core and control core of the terminal, which is suitable for implementing one or more instructions, and is specifically suitable for loading and executing one or more instructions to implement corresponding method processes or corresponding functions. In one embodiment, the processor 201 described in the embodiment of the present invention can be used to perform a series of business processing, including: in response to a trigger operation of an application entry for a target sub-application in a second application detected in a first application, switching from the first application to the target sub-application in the second application; displaying a resource service interface of the target sub-application, the resource service interface including a resource service item for collecting electronic resources; obtaining a resource graphic code corresponding to the resource service item according to a resource business operation for the resource service item; in response to a resource business instruction issued by a resource collecting user to a resource paying user detected in the first application, generating notification data about the resource graphic code, the notification data being used to notify the resource paying user to scan the resource graphic code through a payment terminal to transfer electronic resources to the resource collecting user, and the like.
[0158] The embodiment of the present invention also provides a computer storage medium (Memory), which is a memory device in the terminal for storing programs and data. It is understandable that the computer storage medium here can include both the built-in storage medium in the terminal and the extended storage medium supported by the terminal. The computer storage medium provides a storage space, which stores the operating system of the terminal. In addition, one or more instructions suitable for being loaded and executed by the processor 201 are also stored in the storage space, and these instructions can be one or more computer programs (including program codes). It should be noted that the computer storage medium here can be a high-speed RAM memory, or a non-volatile memory (non-volatile memory), such as at least one disk storage; optionally, it can also be at least one computer storage medium located away from the aforementioned processor.
[0159] In one embodiment, the processor 201 may load and execute one or more instructions stored in a computer storage medium to implement the corresponding steps of the method in the above-mentioned business processing embodiment; in a specific implementation, the processor 201 loads one or more instructions in the computer storage medium and executes the following steps:
[0160] In response to a trigger operation detected in a first application for an application entry of a target sub-application in a second application, switching from the first application to a target sub-application in the second application;
[0161] Displaying a resource service interface of the target sub-application, wherein the resource service interface includes a resource service item for collecting electronic resources;
[0162] According to the resource business operation for the resource service item, obtaining the resource graphic code corresponding to the resource service item;
[0163] In response to a resource business instruction issued by a resource collecting user to a resource paying user detected in the first application, notification data about the resource graphic code is generated, and the notification data is used to notify the resource paying user to scan the resource graphic code through a payment terminal to transfer electronic resources to the resource collecting user.
[0164] In one embodiment, the resource service instruction is detected in a session window created in the first application according to the user account of the resource collection user and the user account of the resource payment user; the user account of the resource collection user is the account used by the resource collection user to log in to the first application, and the user account of the resource payment user is the account used by the resource payment user to log in to the second application;
[0165] The notification data includes any one of the following: image data including the resource graphic code, identification data corresponding to the resource graphic code, or audio data generated according to the resource graphic code.
[0166] In another embodiment, the first application includes an enterprise office application that provides office management services for the target enterprise, and the resource collection user is a management user in the target enterprise who is responsible for managing the office management services;
[0167] The second application includes a social application, and the target sub-application in the second application refers to a sub-application that provides asset managers with services related to electronic resources.
[0168] In another embodiment, the one or more instructions may also be loaded and executed by the processor 201:
[0169] Obtaining an authorization application form to be authorized for the target enterprise, and displaying the authorization application form on an authorization management page, wherein the authorization application form at least includes the enterprise information of the target enterprise and the asset account number of the target asset operator;
[0170] In response to the confirmation operation on the authorization application form, sending an authorization request to the second server corresponding to the second application to request the second server to update the authorization status of the authorization application form from a pending authorization status to an authorized status, so as to complete the binding between the target enterprise and the target asset operator;
[0171] After successfully completing the binding between the target enterprise and the target asset operator, an application entry of the target sub-application is added to the first application.
[0172] In another embodiment, the authorization application form is displayed on the authorization management page of the first application; accordingly, when sending the authorization consent request to the second server corresponding to the second application, the one or more instructions are loaded and specifically executed by the processor 201: sending the authorization consent request to the first server corresponding to the first application, so that the first server performs a legitimacy check on the authorization consent request, and after the legitimacy check passes, forwarding the authorization consent request to the second server corresponding to the second application;
[0173] The one or more instructions may also be loaded and executed by the processor 201: if a successful authorization notification is received from the first server, it is determined that the binding between the target enterprise and the target asset operator is successfully completed; the successful authorization notification is sent from the second server to the first server.
[0174] In another embodiment, the one or more instructions may also be loaded and executed by the processor 201:
[0175] After adding the application entry of the target sub-application in the first application, generating a new entry notification about the application entry of the target sub-application;
[0176] A new entry notification is output in the first application to notify the management user that an application entry of the target sub-application has been added in the first application.
[0177] In another embodiment, before obtaining the authorization application form to be authorized for the target enterprise, the one or more instructions may also be loaded and executed by the processor 201:
[0178] In response to a binding trigger event detected in the binding management page of the second application, outputting a binding entry page;
[0179] Obtaining binding application materials on the binding entry page, the binding application materials at least including: the enterprise information of the target enterprise and the asset account number of the target asset operator to be bound;
[0180] Send a binding application request carrying the binding application information to the second server to request the second server to generate an authorization application form based on the binding application information, add the authorization application form to the authorization binding list of the target enterprise, and review the authorization qualification of the authorization application form.
[0181] In another embodiment, the one or more instructions may also be loaded and executed by the processor 201:
[0182] If an application acceptance notice returned by the second server is received, the application acceptance notice is output in the second application; the application acceptance notice is issued by the second server after adding the authorization application form to the authorization binding list of the target enterprise;
[0183] If the audit result sent by the second server is received, the audit result is output in the application management end system of the second application; the audit result is sent by the second server after auditing the authorization qualification of the authorization application form.
[0184] In another embodiment, the resource service interface further includes a user service item for adding a service user for the target asset operator; accordingly, after displaying the resource service interface of the target sub-application, the one or more instructions may also be loaded and executed by the processor 201:
[0185] Outputting a user adding interface according to the user adding operation for the user service item, the user adding interface including an enterprise account of at least one enterprise user under the target enterprise in the first application;
[0186] Determine the target enterprise account of the selected target enterprise user, and generate a user adding request carrying the target enterprise account and the asset account of the target asset operator;
[0187] Sending the user adding request to the second server to request the second server to associate and store the target enterprise account with the asset account, so as to use the target enterprise user as a new service user of the target asset operator;
[0188] A notification of successfully adding a service user is received from the second server, and the notification of successfully adding a service user is output.
[0189] The embodiment of the present invention can respond to the trigger operation of the application entry of the target sub-application in the second application detected in the first application, first switch from the first application to the target sub-application; secondly, display the resource service interface including the resource service item for collecting electronic resources, and obtain the resource graphic code corresponding to the resource service item according to the resource business operation for the resource service item; then, in response to the resource business instruction issued by the resource collecting user to the resource paying user detected in the first application, generate notification data about the resource graphic code, the notification data is used to notify the resource paying user to scan the resource graphic code through the payment terminal to transfer the electronic resource to the resource collecting user. In the above business processing process, by setting the application entry of the target sub-application in the second application in the first application, the interaction between the first application and the target sub-application in the second application can be realized, and through this interaction, the first application can realize the collection business function with the help of the target sub-application, without performing software development work on the first application, which can effectively reduce the development cost of the first application.
[0190] The above disclosure is only the preferred embodiment of the present invention, which certainly cannot be used to limit the scope of the present invention. Therefore, equivalent changes made according to the claims of the present invention are still within the scope of the present invention.
Claims
1. A business processing method, characterized in that: include: In response to a trigger operation detected in a first application for an application entry of a target sub-application in a second application, switching from the first application to a target sub-application in the second application; the first application includes an enterprise office application that provides office management services for a target enterprise, and the target sub-application in the second application refers to a sub-application that provides services related to electronic resources for asset managers; the application entry of the target sub-application is added to the first application after the binding between the target enterprise and the target asset manager is completed; Displaying a resource service interface of the target sub-application, wherein the resource service interface includes a resource service item for collecting electronic resources and a user service item for adding a service user for the target asset operator; According to the resource business operation for the resource service item, obtaining the resource graphic code corresponding to the resource service item; In response to a resource service instruction issued by a resource receiving user to a resource paying user detected in the first application, generating notification data about the resource graphic code, the notification data being used to notify the resource paying user to scan the resource graphic code through a payment terminal to transfer the electronic resource to the resource receiving user; Outputting a user adding interface according to the user adding operation for the user service item, the user adding interface including an enterprise account of at least one enterprise user under the target enterprise in the first application; Determine the target enterprise account of the selected target enterprise user, and generate a user adding request carrying the target enterprise account and the asset account of the target asset operator; Sending the user adding request to the second server corresponding to the second application, so as to request the second server to associate and store the target enterprise account with the asset account, so as to use the target enterprise user as a new service user of the target asset operator; A notification of successfully adding a service user is received from the second server, and the notification of successfully adding a service user is output.
2. The method according to claim 1, characterized in that The resource service instruction is detected in a session window created in the first application according to the user account of the resource collection user and the user account of the resource payment user; the user account of the resource collection user is the account used by the resource collection user to log in to the first application, and the user account of the resource payment user is the account used by the resource payment user to log in to the second application; The notification data includes any one of the following: image data including the resource graphic code, identification data corresponding to the resource graphic code, or audio data generated according to the resource graphic code.
3. The method according to claim 1, characterized in that The resource collection user is a management user in the target enterprise who is responsible for managing the office management business; The second application includes a social application.
4. The method according to claim 3, characterized in that The method further comprises: Obtaining an authorization application form to be authorized for the target enterprise, and displaying the authorization application form on an authorization management page, wherein the authorization application form includes the enterprise information of the target enterprise and the asset account number of the target asset operator; In response to the confirmation operation on the authorization application form, sending an authorization request to the second server corresponding to the second application to request the second server to update the authorization status of the authorization application form from a pending authorization status to an authorized status, so as to complete the binding between the target enterprise and the target asset operator; After successfully completing the binding between the target enterprise and the target asset operator, an application entry of the target sub-application is added to the first application.
5. The method according to claim 4, characterized in that The authorization application form is displayed on the authorization management page of the first application; The sending of the authorization request to the second server corresponding to the second application includes: sending the authorization request to the first server corresponding to the first application, so that the first server performs a legality check on the authorization request, and after the legality check passes, forwarding the authorization request to the second server corresponding to the second application; The method further includes: if a notification of successful authorization returned by the first server is received, determining that the binding between the target enterprise and the target asset operator is successfully completed; the notification of successful authorization is sent from the second server to the first server.
6. The method according to claim 5, characterized in that The method further comprises: After adding the application entry of the target sub-application in the first application, generating a new entry notification about the application entry of the target sub-application; A new entry notification is output in the first application to notify the management user that an application entry of the target sub-application has been added in the first application.
7. The method according to claim 4, characterized in that Before obtaining the authorization application form to be authorized for the target enterprise, the method further includes: In response to a binding trigger event detected in the binding management page of the second application, outputting a binding entry page; Obtaining binding application materials on the binding entry page, the binding application materials including: the enterprise information of the target enterprise and the asset account number of the target asset operator to be bound; Send a binding application request carrying the binding application information to the second server to request the second server to generate an authorization application form based on the binding application information, add the authorization application form to the authorization binding list of the target enterprise, and review the authorization qualification of the authorization application form.
8. The method according to claim 7, characterized in that The method further comprises: If an application acceptance notice returned by the second server is received, the application acceptance notice is output in the second application; the application acceptance notice is issued by the second server after the authorization application form is added to the authorization binding list of the target enterprise; If the audit result sent by the second server is received, the audit result is output in the application management end system of the second application; the audit result is sent by the second server after auditing the authorization qualification of the authorization application form.
9. A service processing device, characterized in that: include: A processing unit, configured to switch from the first application to a target sub-application in the second application in response to a trigger operation detected in the first application for an application entry of a target sub-application in the second application; the first application includes an enterprise office application that provides office management services for a target enterprise, and the target sub-application in the second application refers to a sub-application that provides services related to electronic resources for asset managers; the application entry of the target sub-application is added to the first application after the binding between the target enterprise and the target asset manager is completed; A display unit, used to display a resource service interface of the target sub-application, wherein the resource service interface includes a resource service item for collecting electronic resources and a user service item for adding a service user for the target asset operator; The processing unit is used to obtain the resource graphic code corresponding to the resource service item according to the resource business operation for the resource service item; The processing unit is used to generate notification data about the resource graphic code in response to a resource service instruction issued by the resource collecting user to the resource paying user detected in the first application, wherein the notification data is used to notify the resource paying user to scan the resource graphic code through a payment terminal to transfer the electronic resource to the resource collecting user; The processing unit is configured to output a user adding interface according to a user adding operation for the user service item, wherein the user adding interface includes an enterprise account of at least one enterprise user under the target enterprise in the first application; Determine the target enterprise account of the selected target enterprise user, and generate a user adding request carrying the target enterprise account and the asset account of the target asset operator; The user adding request is sent to the second server corresponding to the second application to request the second server to associate and store the target enterprise account with the asset account so as to use the target enterprise user as a new service user of the target asset operator; a notification of successful adding of the service user is received from the second server, and the notification of successful adding of the service user is output.
10. A terminal comprising an input device and an output device, characterized in that: Also includes: a processor adapted to implement one or more instructions; as well as, A computer storage medium storing one or more instructions, wherein the one or more instructions are suitable for being loaded by the processor and executing the business processing method according to any one of claims 1 to 8.
11. A computer storage medium, characterized in that: The computer storage medium stores one or more instructions, and the one or more instructions are suitable for being loaded by a processor and executing the business processing method according to any one of claims 1-8.
Citation Information
Patent Citations
A data transfer method and related equipment
CN109034759A
Service processing method and device, terminal and storage medium
CN109840146A
