Payment interaction processing method and apparatus

Abstract

Embodiments of the present specification provide a payment interaction processing method and device, wherein a payment interaction processing method comprises: receiving a payment request submitted by a member terminal of a target member in a member group of an institution; the payment request is generated after triggering a payment interface configured by the member group; performing payment processing on payment information carried by the payment request to obtain a payment bill; generating a payment interaction message for each institution member in the member group according to the member authority of each institution member, the payment interaction message carries an interaction tag of the corresponding institution member; if a payment interaction request submitted by any institution member based on the interaction tag is received, performing payment interaction processing on the payment interaction request.

Description

[0001] This application is a divisional application of Chinese invention patent application filed on February 10, 2022, with application number CN202210125930.4 and title "Payment Interaction Processing Method and Apparatus". Technical Field

[0002] This document relates to the field of data processing technology, and in particular to a payment interaction processing method and apparatus. Background Technology

[0003] With the continuous development of the Internet and information technology, small and micro enterprises (generally defined as small enterprises with bank loans of less than 5 million yuan and micro enterprises with bank loans of less than 1 million yuan) account for more than 99% of the total number of enterprises. They play a huge role in stimulating the market, increasing tax revenue, creating jobs, and maintaining social stability, and are an important force for economic development and healthy social development. Summary of the Invention

[0004] This specification provides one or more embodiments of a payment interaction processing method. The payment interaction processing method includes: receiving a payment request submitted by a member terminal of a target member in a member group of an institution; the payment request is generated after triggering a payment interface configured in the member group. Payment information carried in the payment request is processed to obtain a payment bill. Based on the member permissions of each institutional member in the member group, payment interaction messages for each institutional member regarding the payment bill are generated; the payment interaction messages carry interaction tags corresponding to the institutional members. If a payment interaction request submitted by any institutional member based on an interaction tag is received, payment interaction processing for the payment interaction request is performed.

[0005] This specification provides one or more embodiments of another payment interaction processing method, including: receiving a payment instruction submitted by a target member in a member group of an institution by triggering the payment interface of the member group; acquiring payment information collected in response to the payment instruction and generating a payment request to submit to a server; receiving a payment interaction message carrying the interaction tag of the target member issued by the server and displaying the payment interaction information in the interaction list of the member group; and if the interaction tag is detected to be triggered, submitting a payment interaction request corresponding to the interaction tag to the server.

[0006] This specification provides one or more embodiments of a payment interaction processing apparatus, comprising: a request receiving module configured to receive payment requests submitted by member terminals of target members in a member group of an organization; the payment request is generated after triggering a payment interface configured in the member group. A payment processing module configured to process the payment information carried in the payment request to obtain a payment bill. A message generation module configured to generate payment interaction messages for each member of the organization in relation to the payment bill, based on the member permissions of each member in the member group; the payment interaction messages carry interaction tags corresponding to the member of the organization. If a payment interaction request submitted by any member of the organization based on the interaction tag is received, the interaction processing module is run, and the interaction processing module is configured to perform payment interaction processing on the payment interaction request.

[0007] This specification provides one or more embodiments of another payment interaction processing device, including: an instruction receiving module configured to receive a payment instruction submitted by a target member in a member group of an institution by triggering the payment interface of the member group; a request submission module configured to acquire payment information collected in response to the payment instruction and generate a payment request to submit to a server; and a message display module configured to receive a payment interaction message carrying an interaction tag of the target member issued by the server and display the payment interaction information in the interaction list of the member group. If the interaction tag is detected to be triggered, the interaction request submission module is run, which is configured to submit the payment interaction request corresponding to the interaction tag to the server.

[0008] This specification provides one or more embodiments of a payment interaction processing device, including: a processor; and a memory configured to store computer-executable instructions, which, when executed, cause the processor to: receive a payment request submitted by a member terminal of a target member in a member group of an organization; the payment request is generated after triggering a payment interface configured in the member group; process the payment information carried in the payment request to obtain a payment bill; generate payment interaction messages for each member of the organization regarding the payment bill based on the member permissions of each member in the member group; the payment interaction messages carry interaction tags corresponding to the member of the organization; if a payment interaction request submitted by any member of the organization based on the interaction tag is received, perform payment interaction processing on the payment interaction request.

[0009] This specification provides one or more embodiments of another payment interaction processing device, including: a processor; and a memory configured to store computer-executable instructions, which, when executed, cause the processor to: receive a payment instruction submitted by a target member in a member group of an institution by triggering a payment interface of the member group; acquire payment information collected in response to the payment instruction and generate a payment request to submit to a server; receive a payment interaction message carrying an interaction tag of the target member issued by the server and display the payment interaction information in the interaction list of the member group; and if the interaction tag is detected to be triggered, submit a payment interaction request corresponding to the interaction tag to the server.

[0010] This specification provides one or more embodiments of a storage medium for storing computer-executable instructions that, when executed by a processor, implement the following process: receiving a payment request submitted by a member terminal of a target member in a member group of an organization; the payment request is generated after triggering a payment interface configured in the member group. Payment information carried in the payment request is processed to obtain a payment invoice. Based on the member permissions of each organization member in the member group, payment interaction messages for the payment invoice are generated for each organization member; the payment interaction messages carry interaction tags corresponding to the organization member. If a payment interaction request submitted by any organization member based on the interaction tag is received, payment interaction processing for the payment interaction request is performed.

[0011] This specification provides one or more embodiments of another storage medium for storing computer-executable instructions that, when executed by a processor, implement the following process: A target member in a member group of a receiving organization submits a payment instruction by triggering the payment interface of the member group. Payment information collected in response to the payment instruction is acquired, and a payment request is generated and submitted to a server. A payment interaction message carrying the target member's interaction tag is received from the server, and the payment interaction information is displayed in the interaction list of the member group. If the interaction tag is detected to be triggered, a payment interaction request corresponding to the interaction tag is submitted to the server. Attached Figure Description

[0012] To more clearly illustrate the technical solutions in one or more embodiments of this specification or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments recorded in this specification. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0013] Figure 1A flowchart illustrating a payment interaction processing method provided in one or more embodiments of this specification;

[0014] Figure 2 A schematic diagram of an access page provided for one or more embodiments of this specification;

[0015] Figure 3 A schematic diagram of a single standby resource configuration page provided for one or more embodiments of this specification;

[0016] Figure 4 A schematic diagram of a cyclic standby resource configuration page provided for one or more embodiments of this specification;

[0017] Figure 5 A schematic diagram of a periodic standby resource configuration page provided for one or more embodiments of this specification;

[0018] Figure 6 A schematic diagram of a first resource display page provided for one or more embodiments of this specification;

[0019] Figure 7 A schematic diagram of a second resource display page provided for one or more embodiments of this specification;

[0020] Figure 8 A schematic diagram of a third resource display page provided for one or more embodiments of this specification;

[0021] Figure 9 A schematic diagram of an interactive list page provided for one or more embodiments of this specification;

[0022] Figure 10 Another interactive list page diagram provided for one or more embodiments of this specification;

[0023] Figure 11 A schematic diagram of a log recording page provided for one or more embodiments of this specification;

[0024] Figure 12 A flowchart illustrating a payment interaction processing method applied to a verification interaction scenario, provided for one or more embodiments of this specification;

[0025] Figure 13 A flowchart illustrating another payment interaction processing method provided in one or more embodiments of this specification;

[0026] Figure 14 A schematic diagram of a payment interaction processing device provided for one or more embodiments of this specification;

[0027] Figure 15A schematic diagram of another payment interaction processing device provided in one or more embodiments of this specification;

[0028] Figure 16 A schematic diagram of the structure of a payment interaction processing device provided for one or more embodiments of this specification;

[0029] Figure 17 This is a schematic diagram of the structure of another payment interaction processing device provided in one or more embodiments of this specification. Detailed Implementation

[0030] To enable those skilled in the art to better understand the technical solutions in one or more embodiments of this specification, the technical solutions in one or more embodiments of this specification will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only a part of the embodiments of this specification, and not all of the embodiments. Based on one or more embodiments of this specification, all other embodiments obtained by those skilled in the art without creative effort should fall within the protection scope of this document.

[0031] This specification provides an example of a payment interaction processing method:

[0032] Reference Figure 1 It shows a flowchart of a payment interaction processing method provided in this embodiment, with reference to... Figure 2 It shows a schematic diagram of an access page provided in this embodiment, with reference to... Figure 3 This illustration shows a schematic diagram of a single-use backup resource configuration page provided in this embodiment. (Refer to...) Figure 4 This illustration shows a schematic diagram of a cyclic standby resource configuration page provided in this embodiment. (Refer to...) Figure 5 This illustration shows a schematic diagram of a periodic standby resource configuration page provided in this embodiment. (Refer to...) Figure 6 It shows a schematic diagram of a first resource display page provided in this embodiment, with reference to... Figure 7 This illustration shows a schematic diagram of a second resource display page provided in this embodiment. Figure 8 This illustration shows a schematic diagram of a third resource display page provided in this embodiment. Figure 9 This illustration shows a schematic diagram of an interactive list page provided in this embodiment. Figure 10 This illustrates another interactive list page diagram provided in this embodiment, see reference. Figure 11 This illustration shows a log recording page provided in this embodiment. Figure 12 The diagram illustrates a payment interaction processing method for a verification interaction scenario provided in this embodiment.

[0033] Reference Figure 1 The payment interaction processing method provided in this embodiment specifically includes steps S102 to S108.

[0034] Step S102: The receiving institution receives a payment request submitted by a member terminal of the target member in its member group.

[0035] The payment interaction processing method provided in this embodiment is applied to a server. After processing the payment request submitted by the member terminal of the target member in the member group, a payment bill is obtained. By sending the payment interaction information of the payment bill to each institutional member in the member group, any institutional member can submit a payment interaction request for the payment bill. In this way, the institutional members in the member group can jointly supervise the payment bill and improve the awareness of each institutional member in the member group regarding the payment bill of any institutional member in the member group.

[0036] The member groups described in this embodiment include user groups that bind at least two users together; payment groups that jointly supervise the payment process; and bill groups that jointly manage bills within a group. A member group is a group jointly participated in by members of an enterprise or a (temporary) organization. Specifically, this embodiment does not limit the nature of the member group. The payment request is generated after triggering the payment interface configured in the member group. The payment request includes payment requests of the red envelope type and / or payment requests of the transfer type.

[0037] In practice, the target member submits a payment instruction to the server through the member terminal. Specifically, the member terminal receives the payment instruction submitted by the target member in the member group by triggering the payment interface of the member group, and then obtains the payment information collected in response to the payment instruction based on the payment instruction and generates a payment request to submit to the server.

[0038] In this embodiment, during the process of submitting a payment instruction, the member terminal obtains the target member's access request to the member group and displays an access page based on the access request; it also receives the payment instruction submitted by the target member through an identifier code collection component configured on the access page. After receiving the payment instruction, the terminal calls the configured collection component to collect and parse the payment identifier code; based on the parsing result, it interacts with the target member to obtain the payment information and generates a payment request containing the payment information, which is then submitted to the server.

[0039] like Figure 2 As shown, when a target member accesses a member group through a member terminal, the member terminal displays the following: Figure 2The access page shown includes a payment identification code, an identification code collection component ("Scan"), a red envelope component, a transfer component, a spare resource (advance payment) component, a voucher verification component, and a resource application (request for funds) component. After the target member triggers the identification code collection component, the member's terminal calls the configured camera component to collect the merchant's payment identification code. After obtaining the payment resource amount entered by the target member, the member submits a payment request to the server carrying the payment account identifier and the payment resource amount.

[0040] In addition, the payment request submitted by the member terminal of the target member in the member group of the receiving institution can be replaced by the payment request submitted by the receiving merchant terminal after scanning the payment code identifier of the target member in the member group of the institution.

[0041] Step S104: Process the payment information carried in the payment request to obtain a payment bill.

[0042] The payment information includes a set of information required during the payment process.

[0043] In practice, after receiving a payment request submitted by a member terminal, the payment information carried in the payment request is processed to obtain a payment bill.

[0044] To enhance the awareness of services offered by member institutions within a member group, any member can allocate reserve resources to the group, enabling payment processing based on the account providing the reserve resources. To avoid freezing reserve resources by transferring them to a designated account, thus avoiding resource occupation by the resource provider, this embodiment only marks the amount of reserve resources allocated by any member when allocating them; it does not transfer or freeze the resources in that member's account. In one optional implementation, the resource allocation information for the member group is determined as follows:

[0045] Obtain any backup resource allocation request from any member of the target organization in the member group;

[0046] Based on the backup resource allocation request, the backup update type configured for the target organization's members is collected;

[0047] Collect the backup resource parameters uploaded by the members of the target organization under the backup update type;

[0048] The backup resource information to be allocated to the member group is determined based on the backup update type and the backup resource parameters.

[0049] Specifically, in order to improve the effectiveness of managing backup resource information, when a backup resource allocation request from any member of a target organization to a member group is obtained, the backup update type configured by the member of the target organization is first obtained; then the backup resource parameters uploaded by the member of the target organization under the configured backup update type are obtained; finally, backup resource information containing the backup update type and backup resource parameters is generated.

[0050] The backup update types include: a first update type with a single disbursement, where the funder provides the user with a backup resource limit that can be used if the backup payment conditions are met; the limit decreases in real time after use and does not recover. It also includes a second update type with a periodic update, where the funder provides the user with a backup resource limit that can be used if the backup payment conditions are met; the limit decreases in real time after use and recovers in real time upon receiving a reconciliation instruction for the payment bill. Finally, it includes a third update type with a cyclical update, where the funder provides the user with a backup resource limit that can be used if the backup payment conditions are met; the limit decreases in real time after use and recovers on the first day of the next cycle after receiving a reconciliation instruction for the payment bill.

[0051] Optionally, the amount of available resources in the backup resource information is configured based on the backup update type included in the backup resource information;

[0052] If the backup update type is the first update type, then the amount of available resources in the backup resource information remains unchanged.

[0053] In one optional implementation of this embodiment, if the backup update type is the second update type, the following operation is performed:

[0054] Take the update cycle conditions contained in the backup resource information;

[0055] Calculate the update time for the amount of available resources based on the payment time recorded in the payment bill and the update cycle conditions;

[0056] If the update time is detected, the available resource amount in the backup resource information will be updated to the backup resource amount.

[0057] like Figure 3 As shown, member A configures backup resource information for the member group through the single backup resource configuration page; for example... Figure 4 As shown, member A configures reserve resource information for the member group through the reserve fund configuration page of the revolving reserve resource configuration page; for example... Figure 5As shown, member A configures backup resource information for the member group through the periodic backup resource configuration page. After the member configures the backup resources, the backup resource information is displayed through the member group's interactive list, such as... Figure 6 As described above, after member A configures a single-use backup resource, the first resource display page is displayed. For example... Figure 7 As shown, after member A configures a periodic reserve resource of 3000, member B uses 300 yuan. After member C verifies member B's payment of 300 yuan, the second resource display page is displayed; Figure 8 As shown, after member A configures the cyclical backup resources, member B uses 300 yuan. After member C verifies member B's payment bill of 300 yuan, the third resource display page is displayed.

[0058] In specific implementation, if the member group has backup resource information configured, payment processing is performed based on the backup resource information. If no backup resource information is configured, payment processing is performed based on the target member's resource account. To improve the target member's awareness of the payment process, in an optional implementation of this embodiment, the following operations are performed during the payment processing of the payment information carried in the payment request to obtain the payment invoice:

[0059] Check whether to allocate spare resources for the aforementioned member group;

[0060] If not, then the payment information is processed based on the target member's resource account to obtain a payment bill;

[0061] If so, if the payment information meets the backup payment conditions corresponding to the backup resource information, the payment information is processed based on the resource account corresponding to the backup resource information to obtain the payment bill;

[0062] Based on the amount of payment resources contained in the payment information, the amount of reserve resources in the reserve resource information is updated to the amount of available resources.

[0063] Optionally, the alternative payment terms include at least one of the following:

[0064] The amount of payment resources contained in the payment information is less than or equal to the amount of backup resources, the member identifier of the target member is recorded in the available member list of the backup payment information device, and the payment time recorded in the payment information is within the available time range of the backup resource information.

[0065] Specifically, the system checks whether backup resources have been allocated to the member group. If not, it processes the payment information based on the resource account corresponding to the payment identifier code and obtains a payment invoice. If resources have been allocated, it first verifies whether the payment information meets the backup payment conditions corresponding to the backup resource information. If not, the payment fails. If it does, it determines the resource account corresponding to the backup resource information (i.e., the resource account of the backup resource provider) and processes the payment information based on that resource account to obtain a payment invoice.

[0066] Step S106: Based on the member permissions of each member in the member group, generate payment interaction messages for each member regarding the payment bill.

[0067] The payment interaction message carries an interaction tag corresponding to the member of the organization; in the member group, the target member has access to the payment bill; other members of the organization in the member group have shared access to the payment bill.

[0068] To ensure equal access to payment bills among users with shared permissions, all users share the same interaction tag. This interaction tag represents the member's access rights to the payment bill and is the interaction tag of the payment bill obtained after the target member, as determined by the server, processes the payment information. Optionally, the target member's interaction tag may be empty or a voucher submission tag. The interaction tags of other institutional members in the member group, besides the target member, include bill confirmation, bill return, and / or voucher request tags.

[0069] In one optional implementation of this embodiment, during the process of generating payment interaction messages for the payment bill based on the member permissions of each member in the member group, the following operations are performed:

[0070] Based on the payment type corresponding to the payment request, determine the members of the organization who have shared authority over the payment bill;

[0071] Based on the shared permissions, an audit tag for the payment bill is generated by the shared members, and payment interaction information containing the audit tag is generated.

[0072] Furthermore, for the target member, based on their access permissions to the payment bill, a resource tag is generated for the payment bill, and payment interaction information containing the resource tag is generated. The target member's terminal receives the payment interaction message carrying the target member's interaction tag sent by the server, and displays the payment interaction information in the interaction list of the member group.

[0073] It should be noted that the description of the interactive labels in this embodiment is merely illustrative. In actual scenarios, the interactive labels can be determined according to the requirements, and this embodiment does not impose any limitations on them.

[0074] For example, after member B uses their own resource account to process payments and generate a payment invoice, member B can do so through methods such as... Figure 9 The interactive list page shown perceives payment interaction information for the payment bill. Among them, the configured real-time location, communication box, and entry point for uploading photos / videos / invoices are the interaction tags of organization member B for the payment bill.

[0075] Organization member A can use, for example Figure 10 The interactive list page shown displays payment interaction information for payment bills. The configured real-time location, communication box, entry point for uploading photos / videos / invoices, verification control, and rejection control represent the interaction tags of organization member A regarding the payment bill. The payment interaction information of other organization members within the member group is also displayed. Figure 10 Similarly, in order to improve group members' awareness of the reconciliation status of payment bills, the reconciliation status is also displayed.

[0076] Step S108: If a payment interaction request is received from any member of an organization based on an interaction tag, perform payment interaction processing on the payment interaction request.

[0077] In practice, the payment interaction process differs depending on whether the payment is made using backup resources or using the target member's resource account.

[0078] (1) Process payment based on the target member's resource account.

[0079] In one optional implementation of this embodiment, after payment processing is performed based on the target member's resource account, payment interaction is processed in the following manner:

[0080] If a reconciliation request for the payment bill is received from any target organization member other than the target member in the member group, then the resource account of the target organization member is determined.

[0081] Transfer the resources corresponding to the payment resource amount recorded in the payment information in the resource account to the target member's payment account;

[0082] Based on the resource transfer results and the member identifier of any of the target organization members, a reconciliation log for the payment bill is generated, and the reconciliation log is pushed to be displayed in the interaction list of the member group.

[0083] Specifically, if the target member's resource account is used for payment processing, then other group members in the member group need to perform the reconciliation. After any institutional member in the member group other than the target member submits a reconciliation request for the payment bill, the resources corresponding to the payment bill are transferred from the institutional member's resource account to the target member's resource account to achieve the reconciliation of the payment bill.

[0084] To improve the awareness of the reconciliation status of payment bills among members of the group, a reconciliation log of the payment bill is generated and displayed after reconciliation.

[0085] like Figure 11 As shown, after member A reconciles member B's payment bill, a log page is displayed stating "xx-xx, xx o'clock xx minute, member A reconciled the payment bill" and the reconciliation status is updated to reconciled.

[0086] (2) Payment processing based on backup resources

[0087] In one optional implementation of this embodiment, after payment processing based on backup resource information, payment interaction processing is performed in the following manner:

[0088] When the backup update type is a cyclic update type, if a confirmation request for the payment bill is received from an institutional member other than the target member in the member group, the available resource amount in the backup resource information is updated to the backup resource amount based on the confirmation request.

[0089] In addition, when the backup update type is a periodic update type, if a confirmation request for the payment bill is received from an institutional member other than the target member in the member group, the update cycle condition contained in the backup resource information is read; the update time for the available resource amount is calculated based on the payment time recorded in the payment bill and the update cycle condition; and when the update time is detected to have arrived, the available resource amount in the backup resource information is updated to the backup resource amount.

[0090] To ensure the authenticity of payment invoices, institutional members can request supporting documentation to verify the authenticity and reasonableness of the invoices. Target members can upload invoices, videos, or other supporting documents. Based on this, in one optional implementation of this embodiment, payment interaction is processed in the following manner:

[0091] If a billing voucher request for the payment bill is received from any member of the target organization other than the target member in the member group, a voucher is generated based on the voucher type carried in the billing voucher request, a reminder message is added, and the message is pushed out.

[0092] After obtaining the billing voucher uploaded by the target member based on the added reminder information of the voucher, the billing voucher is associated with the payment bill;

[0093] The billing voucher is pushed to the interaction list of the member group to display the billing voucher.

[0094] Specifically, to improve the convenience for organizational members to view invoices and vouchers, if the invoice or voucher is a video, the video will be played automatically, allowing for one-screen review and completion of the review.

[0095] The following description uses the application of a payment interaction processing method provided in this embodiment in a verification interaction scenario as an example to further illustrate the payment interaction processing method provided in this embodiment. (See also...) Figure 12 The payment interaction processing method applied to the verification interaction scenario includes the following steps.

[0096] In step S1208, after receiving the payment request, the server queries the backup resources allocated to the member group.

[0097] Prior to this, the target member's terminal receives the payment instruction submitted by the target member through triggering the payment identification code collection control of the member group, collects the payment identification code and determines the payment information, and generates a payment request based on the payment information and sends it to the server.

[0098] In step S1210, if the spare resources are empty, payment processing is performed based on the target member's resource account and a payment bill is obtained.

[0099] Step S1212: Generate access interaction tags for the target member's access to the payment bill based on the target member's access rights to the payment bill, and generate shared access interaction tags for the shared accounts' access to the payment bill based on the shared access rights of institutional members other than the target member in the member group to the payment bill.

[0100] Step S1214: Generate the target member's payment interaction information for the payment bill based on the access interaction tag and send it to the target member's terminal.

[0101] Step S1216: Generate payment interaction information of the co-rights member on the payment bill based on the co-rights interaction tag and send it to the co-rights member's terminal.

[0102] The execution order of steps S1214 and S1216 is not limited during the execution process.

[0103] Step S1218: Obtain the billing credential request submitted by the co-rights member terminal based on the credential request tag in the co-rights interaction tag.

[0104] Step S1220: Generate voucher based on bill voucher request, add reminder information and send it to the target member terminal.

[0105] Step S1222: Obtain the billing voucher collected and uploaded by the target member's terminal.

[0106] Step S1224: Establish the association between billing vouchers and payment bills.

[0107] Step S1226: Generate voucher interaction information for the target member's statement voucher based on the access interaction tag and send it to the target member's terminal.

[0108] Step S1228: Generate voucher interaction information for the shared rights member's statement voucher based on the shared rights interaction tag and send it to the shared rights member's terminal.

[0109] Step S1230: Obtain the reconciliation request for payment bills submitted by the co-owner's terminal.

[0110] Step S1232: Transfer the resources corresponding to the payment information in the resource account of the co-owner to the resource account of the target member.

[0111] Step S1234: Generate a reversal log based on the resource transfer, and push the reversal log to the target member terminal and the co-owner member terminal.

[0112] Another embodiment of the payment interaction processing method provided in this specification:

[0113] Reference Figure 13 It shows a flowchart of a payment interaction processing method provided in this embodiment, with reference to... Figure 2 It shows a schematic diagram of an access page provided in this embodiment, with reference to... Figure 3 This illustration shows a schematic diagram of a single-use backup resource configuration page provided in this embodiment. (Refer to...) Figure 4 This illustration shows a schematic diagram of a cyclic standby resource configuration page provided in this embodiment. (Refer to...) Figure 5 This illustration shows a schematic diagram of a periodic standby resource configuration page provided in this embodiment. (Refer to...) Figure 6 It shows a schematic diagram of a first resource display page provided in this embodiment, with reference to... Figure 7 This illustration shows a schematic diagram of a second resource display page provided in this embodiment. Figure 8 This illustration shows a schematic diagram of a third resource display page provided in this embodiment. Figure 9 This illustration shows a schematic diagram of an interactive list page provided in this embodiment. Figure 10 This illustrates another interactive list page diagram provided in this embodiment, see reference. Figure 11 This illustration shows a log recording page provided in this embodiment. Figure 12 The diagram illustrates a payment interaction processing method for a verification interaction scenario provided in this embodiment.

[0114] The payment interaction processing method provided in this embodiment is applied to the member terminal of the target member. The payment interaction processing method provided in this embodiment cooperates with the payment interaction processing method applied to the server provided in the above embodiments during runtime. Therefore, please refer to the relevant content of the above embodiments when reading this embodiment.

[0115] Reference Figure 13 The payment interaction processing method provided in this embodiment specifically includes steps S1302 to S1308.

[0116] Step S1302: The target member in the member group of the receiving institution submits a payment instruction by triggering the payment interface of the member group.

[0117] The payment interaction processing method provided in this embodiment is applied to the user terminal of the target member. By uploading a payment request to the server, the server generates and sends payment interaction information carrying an interaction tag. When the payment interaction information is obtained, it is displayed in the interaction list of the member group. When the interaction tag is detected to be triggered, the payment interaction request corresponding to the interaction tag is submitted to the server. In this way, the payment interaction information is displayed in the form of member groups and interaction lists, which improves the perception of payment interaction information. The setting of interaction tags also improves the convenience of payment interaction for the target member.

[0118] The member groups described in this embodiment include user groups that bind at least two users together; payment groups that jointly supervise the payment process; and bill groups that jointly manage bills within a group. A member group is a group jointly participated in by members of an enterprise or a (temporary) organization. Specifically, this embodiment does not limit the nature of the member group. The payment request is generated after triggering the payment interface configured in the member group. The payment request includes payment requests of the red envelope type and / or payment requests of the transfer type.

[0119] In practice, the target member submits a payment instruction to the server through the member terminal. Specifically, the member terminal receives the payment instruction submitted by the target member in the member group by triggering the payment interface of the member group, and then obtains the payment information collected in response to the payment instruction based on the payment instruction and generates a payment request to submit to the server.

[0120] In one optional implementation provided in this embodiment, the member terminal performs the following operations during the process of submitting a payment instruction:

[0121] Obtain the target member's access request to the member group, and display the access page based on the access request;

[0122] Receive payment instructions submitted by the target member by triggering the identification code collection component configured on the access page.

[0123] Step S1304: Obtain the payment information collected in response to the payment instruction and generate a payment request to submit to the server.

[0124] In one optional implementation of this embodiment, after receiving the payment instruction, payment information is obtained and a payment request is generated and submitted to the server in the following manner:

[0125] The configured data collection component is invoked to collect and parse the payment identification code;

[0126] Based on the parsing results, the payment information is obtained by interacting with the target member, and a payment request containing the payment information is generated and submitted to the server.

[0127] like Figure 2 As shown, when a target member accesses a member group through a member terminal, the member terminal displays the following: Figure 2 The access page shown includes a payment identification code, an identification code collection component 201, a red envelope component 202, a transfer component 203, a spare resource distribution component 204, a voucher verification component 205, and a resource application component 206. After the target member triggers the identification code collection component 201, the member's terminal calls the configured camera component to collect the merchant's payment identification code. After obtaining the payment resource amount entered by the target member, the member submits a payment request to the server, carrying the payment account identifier and the payment resource amount.

[0128] In one optional implementation of this embodiment, the server performs the following operations after receiving the payment request:

[0129] The payment information carried in the payment request is processed to generate a payment invoice;

[0130] Based on the target member's membership permissions for the payment bill, determine the target member's interaction tags for the payment bill;

[0131] Based on the interaction tag, the target member's access information for the payment bill is generated, and the payment interaction information containing the access information is generated and sent to the target member's member terminal.

[0132] Specifically, the process of the server generating payment invoices and payment interaction messages is explained in detail below.

[0133] The payment information includes a set of information required during the payment process.

[0134] In practice, after receiving a payment request submitted by a member terminal, the payment information carried in the payment request is processed to obtain a payment bill.

[0135] To enhance the awareness of services offered by member institutions within a member group, any member can allocate reserve resources to the group, enabling payment processing based on the account providing the reserve resources. To avoid freezing reserve resources by transferring them to a designated account, thus avoiding resource occupation by the resource provider, this embodiment only marks the amount of reserve resources allocated by any member when allocating them; it does not transfer or freeze the resources in that member's account. In one optional implementation, the resource allocation information for the member group is determined as follows:

[0136] Obtain any backup resource allocation request from any member of the target organization in the member group;

[0137] Based on the backup resource allocation request, the backup update type configured for the target organization's members is collected;

[0138] Collect the backup resource parameters uploaded by the members of the target organization under the backup update type;

[0139] The backup resource information to be allocated to the member group is determined based on the backup update type and the backup resource parameters.

[0140] Specifically, in order to improve the effectiveness of managing backup resource information, when a backup resource allocation request from any member of a target organization to a member group is obtained, the backup update type configured by the member of the target organization is first obtained; then the backup resource parameters uploaded by the member of the target organization under the configured backup update type are obtained; finally, backup resource information containing the backup update type and backup resource parameters is generated.

[0141] The backup update types include: a first update type with a single disbursement, where the funder provides the user with a backup resource limit that can be used if the backup payment conditions are met; the limit decreases in real time after use and does not recover. It also includes a second update type with a periodic update, where the funder provides the user with a backup resource limit that can be used if the backup payment conditions are met; the limit decreases in real time after use and recovers in real time upon receiving a reconciliation instruction for the payment bill. Finally, it includes a third update type with a cyclical update, where the funder provides the user with a backup resource limit that can be used if the backup payment conditions are met; the limit decreases in real time after use and recovers on the first day of the next cycle after receiving a reconciliation instruction for the payment bill.

[0142] Optionally, the amount of available resources in the backup resource information is configured based on the backup update type included in the backup resource information;

[0143] If the backup update type is the first update type, then the amount of available resources in the backup resource information remains unchanged.

[0144] In one optional implementation of this embodiment, if the backup update type is the second update type, the following operation is performed:

[0145] Take the update cycle conditions contained in the backup resource information;

[0146] Calculate the update time for the amount of available resources based on the payment time recorded in the payment bill and the update cycle conditions;

[0147] If the update time is detected, the available resource amount in the backup resource information will be updated to the backup resource amount.

[0148] like Figure 3 As shown, member A configures backup resource information for the member group through the single backup resource configuration page; for example... Figure 4 As shown, member A configures reserve resource information for the member group through the reserve fund configuration page of the revolving reserve resource configuration page; for example... Figure 5 As shown, member A configures backup resource information for the member group through the periodic backup resource configuration page. After the member configures the backup resources, the backup resource information is displayed through the member group's interactive list, such as... Figure 6 As described above, after member A configures a single-use backup resource, the first resource display page is displayed. For example... Figure 7As shown, after member A configures the periodic reserve resources, member B uses 300 yuan. After member C verifies member B's 300 yuan payment, the second resource display page is displayed; Figure 8 As shown, after member A configures the cyclical backup resources, member B uses 300 yuan. After member C verifies member B's payment bill of 300 yuan, the third resource display page is displayed.

[0149] In specific implementation, if the member group has backup resource information configured, payment processing is performed based on the backup resource information. If no backup resource information is configured, payment processing is performed based on the target member's resource account. To improve the target member's awareness of the payment process, in an optional implementation of this embodiment, the following operations are performed during the payment processing of the payment information carried in the payment request to obtain the payment invoice:

[0150] Check whether to allocate spare resources for the aforementioned member group;

[0151] If not, then the payment information is processed based on the target member's resource account to obtain a payment bill;

[0152] If so, if the payment information meets the backup payment conditions corresponding to the backup resource information, the payment information is processed based on the resource account corresponding to the backup resource information to obtain the payment bill;

[0153] Based on the amount of payment resources contained in the payment information, the amount of reserve resources in the reserve resource information is updated to the amount of available resources.

[0154] Optionally, the alternative payment terms include at least one of the following:

[0155] The amount of payment resources contained in the payment information is less than or equal to the amount of backup resources, the member identifier of the target member is recorded in the available member list of the backup payment information device, and the payment time recorded in the payment information is within the available time range of the backup resource information.

[0156] Specifically, the system checks whether backup resources have been allocated to the member group. If not, it processes the payment information based on the resource account corresponding to the payment identifier code and obtains a payment invoice. If resources have been allocated, it first verifies whether the payment information meets the backup payment conditions corresponding to the backup resource information. If not, the payment fails. If it does, it determines the resource account corresponding to the backup resource information (i.e., the resource account of the backup resource provider) and processes the payment information based on that resource account to obtain a payment invoice.

[0157] Based on the membership permissions of each member in the member group, payment interaction messages for the payment bill are generated for each member.

[0158] The payment interaction message carries an interaction tag corresponding to the member of the organization; in the member group, the target member has access to the payment bill; other members of the organization in the member group have shared access to the payment bill.

[0159] To ensure equal access to payment bills among users with shared permissions, all users share the same interaction tag. This interaction tag represents the member's access rights to the payment bill and is the interaction tag of the payment bill obtained after the target member, as determined by the server, processes the payment information. Optionally, the target member's interaction tag may be empty or a voucher submission tag. The interaction tags of other institutional members in the member group, besides the target member, include bill confirmation, bill return, and / or voucher request tags.

[0160] In one optional implementation of this embodiment, during the process of generating payment interaction messages for the payment bill based on the member permissions of each member in the member group, the following operations are performed:

[0161] Based on the payment type corresponding to the payment request, determine the members of the organization who have shared authority over the payment bill;

[0162] Based on the shared permissions, an audit tag for the payment bill is generated by the shared members, and payment interaction information containing the audit tag is generated.

[0163] It should be noted that the description of the interactive labels in this embodiment is merely illustrative. In actual scenarios, the interactive labels can be determined according to the requirements, and this embodiment does not impose any limitations on them.

[0164] For example, after member B uses their own resource account to process payments and generate a payment invoice, member B can do so through methods such as... Figure 9 The interactive list page shown perceives payment interaction information for the payment bill. Among them, the configured real-time location, communication box, and entry point for uploading photos / videos / invoices are the interaction tags of organization member B for the payment bill.

[0165] Organization member A can use, for example Figure 10The interactive list page shown displays payment interaction information for payment bills. The configured real-time location, communication box, entry point for uploading photos / videos / invoices, verification control, and rejection control represent the interaction tags of organization member A regarding the payment bill. The payment interaction information of other organization members within the member group is also displayed. Figure 10 Similarly, in order to improve group members' awareness of the reconciliation status of payment bills, the reconciliation status is also displayed.

[0166] Step S1306: Receive a payment interaction message from the server carrying the interaction tag of the target member, and display the payment interaction information in the interaction list of the member group.

[0167] For the target member, based on access permissions to the payment bill, a resource tag is generated for the payment bill, and payment interaction information containing the resource tag is generated. The target member's terminal receives the payment interaction message carrying the target member's interaction tag sent by the server, and displays the payment interaction information in the interaction list of the member group.

[0168] It should be noted that the description of the interactive labels in this embodiment is merely illustrative. In actual scenarios, the interactive labels can be determined according to the requirements, and this embodiment does not impose any limitations on them.

[0169] For example, after member B uses their own resource account to process payments and generate a payment invoice, member B can do so through methods such as... Figure 9 The interactive list page shown perceives payment interaction information for the payment bill. Among them, the configured real-time location, communication box, and entry point for uploading photos / videos / invoices are the interaction tags of organization member B for the payment bill.

[0170] Step S1308: If the interaction tag is detected to be triggered, submit the payment interaction request corresponding to the interaction tag to the server.

[0171] In one optional implementation of this embodiment, if the interaction tag is detected to be triggered, a billing voucher for the payment bill is collected based on the tag type of the interaction tag.

[0172] The billing voucher is submitted to the server so that the server associates the billing voucher with the payment bill.

[0173] Obtain the billing voucher issued by the server after associating the billing voucher with the payment bill;

[0174] If the billing voucher is a video, it is played when the member group is detected to have been accessed.

[0175] Specifically, target members can upload billing vouchers based on interaction tags. Upon detecting a triggered interaction tag, the server collects the billing voucher and uploads it to the server, allowing the server to associate the billing voucher with the payment bill. After associating the billing voucher with the payment bill, the server generates an interaction tag for the billing voucher based on the target member's access permissions to the payment bill, and sends voucher interaction information carrying the interaction tag to the member's terminal. The member's terminal displays the voucher in the interaction list upon receiving the voucher interaction information. Furthermore, after associating the billing voucher with the payment bill, the server generates an interaction tag for the shared access members' access to the billing voucher based on the shared access permissions of the shared users to the payment bill, and sends voucher interaction information carrying the interaction tag to the shared access members' member terminals.

[0176] The following description uses the application of a payment interaction processing method provided in this embodiment in a verification interaction scenario as an example to further illustrate the payment interaction processing method provided in this embodiment. (See also...) Figure 12 The payment interaction processing method applied to the verification interaction scenario includes the following steps.

[0177] In step S1202, the target member's terminal receives the payment instruction submitted by the target member through the payment identification code collection control of the member group.

[0178] Step S1204: Collect the payment identification code and obtain payment information.

[0179] Step S1206: Generate a payment request based on the payment information and send it to the server.

[0180] Subsequently, upon receiving a payment request, the server queries the backup resources allocated to the member group. If the backup resources are empty, it processes the payment based on the target member's resource account and obtains a payment invoice. Based on the target member's access permissions to the payment invoice, it generates an access interaction tag for the target member's payment invoice. Based on the shared permissions of other institutional members in the member group (excluding the target member) to the payment invoice, it generates a shared interaction tag for the shared accounts' payment invoice. Based on the access interaction tags, it generates payment interaction information for the target member's payment invoice and sends it to the target member's terminal. Based on the shared interaction tags, it generates payment interaction information for the shared members' payment invoice and sends it to the shared members' terminals, thus obtaining... The shared-rights member terminal submits a billing voucher request based on the voucher request tag in the shared-rights interaction tag. Based on the billing voucher request, it generates voucher addition reminder information and sends it to the target member terminal. It obtains the billing voucher collected and uploaded by the target member terminal, establishes the association between the billing voucher and the payment bill, generates the target member's voucher interaction information on the billing voucher based on the access interaction tag and sends it to the target member terminal. It also generates the shared-rights member's voucher interaction information on the billing voucher based on the shared-rights interaction tag and sends it to the shared-rights member terminal. It obtains the reconciliation request for the payment bill submitted by the shared-rights member terminal and transfers the resources corresponding to the payment information in the shared-rights member's resource account to the target member's resource account.

[0181] This specification provides an embodiment of a payment interaction processing device as follows:

[0182] In the above embodiments, a payment interaction processing method is provided, and correspondingly, a payment interaction processing device is also provided, which will be described below with reference to the accompanying drawings.

[0183] Reference Figure 14 The diagram shows a payment interaction processing device provided in this embodiment.

[0184] Since the apparatus embodiments correspond to the method embodiments, the descriptions are relatively simple. For relevant parts, please refer to the corresponding descriptions of the method embodiments provided above. The apparatus embodiments described below are merely illustrative.

[0185] This embodiment provides a payment interaction processing device, including:

[0186] The request receiving module 1402 is configured to receive payment requests submitted by member terminals of target members in the member group of the institution; the payment request is generated after triggering the payment interface configured in the member group.

[0187] The payment processing module 1404 is configured to process the payment information carried in the payment request and obtain a payment bill.

[0188] The message generation module 1406 is configured to generate payment interaction messages for each member of the organization in the member group for the payment bill based on the member permissions of each member of the organization; the payment interaction messages carry the interaction tags of the corresponding member of the organization.

[0189] If a payment interaction request is received from any member of an organization based on an interaction tag, the interaction processing module 1408 is run. The interaction processing module 1408 is configured to perform payment interaction processing on the payment interaction request.

[0190] Another embodiment of the payment interaction processing device provided in this specification is as follows:

[0191] In the above embodiments, another payment interaction processing method is provided, and correspondingly, another payment interaction processing device is also provided, which will be described below with reference to the accompanying drawings.

[0192] Reference Figure 15 The diagram shows a payment interaction processing device provided in this embodiment.

[0193] Since the apparatus embodiments correspond to the method embodiments, the descriptions are relatively simple. For relevant parts, please refer to the corresponding descriptions of the method embodiments provided above. The apparatus embodiments described below are merely illustrative.

[0194] This embodiment provides a payment interaction processing device, including:

[0195] The instruction receiving module 1502 is configured to receive payment instructions submitted by a target member in a member group of an institution by triggering the payment interface of the member group;

[0196] The request submission module 1504 is configured to obtain payment information collected in response to the payment instruction and generate a payment request to submit to the server;

[0197] The message display module 1506 is configured to receive a payment interaction message sent by the server carrying the interaction tag of the target member, and display the payment interaction information in the interaction list of the member group;

[0198] If the interaction tag is detected to be triggered, the interaction request submission module 1508 is run. The interaction request submission module 1508 is configured to submit the payment interaction request corresponding to the interaction tag to the server.

[0199] This specification provides the following embodiment of a payment interaction processing device:

[0200] Corresponding to the payment interaction processing method described above, based on the same technical concept, one or more embodiments of this specification also provide a payment interaction processing device, which is used to execute the payment interaction processing method provided above. Figure 16 This is a schematic diagram of the structure of a payment interaction processing device provided for one or more embodiments of this specification.

[0201] This embodiment provides a payment interaction processing device, including:

[0202] like Figure 16 As shown, payment interaction processing devices can vary significantly due to differences in configuration or performance. They may include one or more processors 1601 and memory 1602, with memory 1602 storing one or more application programs or data. Memory 1602 can be temporary or persistent storage. The application programs stored in memory 1602 may include one or more modules (not shown), each module including a series of computer-executable instructions from the payment interaction processing device. Furthermore, processor 1601 may be configured to communicate with memory 1602, executing the series of computer-executable instructions in memory 1602 on the payment interaction processing device. The payment interaction processing device may also include one or more power supplies 1603, one or more wired or wireless network interfaces 1604, one or more input / output interfaces 1605, one or more keyboards 1606, etc.

[0203] In one specific embodiment, the payment interaction processing device includes a memory and one or more programs, wherein the one or more programs are stored in the memory, and the one or more programs may include one or more modules, and each module may include a series of computer-executable instructions for the payment interaction processing device, and is configured to be executed by one or more processors. The one or more programs include computer-executable instructions for performing the following:

[0204] The payment request is submitted by a member terminal of the target member in the member group of the receiving institution; the payment request is generated after triggering the payment interface configured in the member group.

[0205] The payment information carried in the payment request is processed to obtain a payment invoice;

[0206] Based on the member permissions of each organization member in the member group, a payment interaction message is generated for each organization member in response to the payment bill; the payment interaction message carries the interaction tag of the corresponding organization member;

[0207] If a payment interaction request is received from any member of an organization based on an interaction tag, the payment interaction processing of the payment interaction request shall be performed.

[0208] Another embodiment of the payment interaction processing device provided in this specification is as follows:

[0209] Corresponding to the other payment interaction processing method described above, based on the same technical concept, one or more embodiments of this specification also provide another payment interaction processing device, which is used to execute the payment interaction processing method provided above. Figure 17 This is a schematic diagram of the structure of a payment interaction processing device provided for one or more embodiments of this specification.

[0210] This embodiment provides a payment interaction processing device, including:

[0211] like Figure 17 As shown, payment interaction processing devices can vary significantly due to differences in configuration or performance. They may include one or more processors 1701 and memories 1702. The memories 1702 may store one or more application programs or data. The memories 1702 may be temporary or persistent storage. The application programs stored in the memories 1702 may include one or more modules (not shown), each module including a series of computer-executable instructions from the payment interaction processing device. Furthermore, the processor 1701 may be configured to communicate with the memories 1702, executing the series of computer-executable instructions stored in the memories 1702 on the payment interaction processing device. The payment interaction processing device may also include one or more power supplies 1703, one or more wired or wireless network interfaces 1704, one or more input / output interfaces 1705, one or more keyboards 1706, etc.

[0212] In one specific embodiment, the payment interaction processing device includes a memory and one or more programs, wherein the one or more programs are stored in the memory, and the one or more programs may include one or more modules, and each module may include a series of computer-executable instructions for the payment interaction processing device, and is configured to be executed by one or more processors. The one or more programs include computer-executable instructions for performing the following:

[0213] The target member in the receiving institution's member group submits a payment instruction by triggering the payment interface of the member group;

[0214] Obtain payment information collected in response to the payment instruction and generate a payment request to submit to the server;

[0215] Receive the payment interaction message sent by the server carrying the interaction tag of the target member, and display the payment interaction information in the interaction list of the member group;

[0216] If the interaction tag is detected to be triggered, a payment interaction request corresponding to the interaction tag is submitted to the server.

[0217] This specification provides an example of a storage medium as follows:

[0218] Corresponding to the payment interaction processing method described above, based on the same technical concept, one or more embodiments of this specification also provide a storage medium.

[0219] The storage medium provided in this embodiment is used to store computer-executable instructions, which, when executed by a processor, implement the following process:

[0220] The payment request is submitted by a member terminal of the target member in the member group of the receiving institution; the payment request is generated after triggering the payment interface configured in the member group.

[0221] The payment information carried in the payment request is processed to obtain a payment invoice;

[0222] Based on the member permissions of each organization member in the member group, a payment interaction message is generated for each organization member in response to the payment bill; the payment interaction message carries the interaction tag of the corresponding organization member;

[0223] If a payment interaction request is received from any member of an organization based on an interaction tag, the payment interaction processing of the payment interaction request shall be performed.

[0224] It should be noted that the embodiments concerning the storage medium in this specification and the embodiments concerning the payment interaction processing method in this specification are based on the same inventive concept. Therefore, the specific implementation of this embodiment can be referred to the implementation of the corresponding method described above, and the repeated parts will not be described again.

[0225] Another embodiment of the storage medium provided in this specification is as follows:

[0226] In response to the other payment interaction processing method described above, based on the same technical concept, one or more embodiments of this specification also provide another storage medium.

[0227] The storage medium provided in this embodiment is used to store computer-executable instructions, which, when executed by a processor, implement the following process:

[0228] The target member in the receiving institution's member group submits a payment instruction by triggering the payment interface of the member group;

[0229] Obtain payment information collected in response to the payment instruction and generate a payment request to submit to the server;

[0230] Receive the payment interaction message sent by the server carrying the interaction tag of the target member, and display the payment interaction information in the interaction list of the member group;

[0231] If the interaction tag is detected to be triggered, a payment interaction request corresponding to the interaction tag is submitted to the server.

[0232] It should be noted that the embodiments concerning the storage medium in this specification and the embodiments concerning the payment interaction processing method in this specification are based on the same inventive concept. Therefore, the specific implementation of this embodiment can be referred to the implementation of the corresponding method described above, and the repeated parts will not be described again.

[0233] The foregoing has described specific embodiments of this specification. Other embodiments are within the scope of the appended claims. In some cases, the actions or steps recited in the claims may be performed in a different order than that shown in the embodiments and may still achieve the desired result. Furthermore, the processes depicted in the drawings do not necessarily require the specific or sequential order shown to achieve the desired result. In some embodiments, multitasking and parallel processing are possible or may be advantageous.

[0234] In the 1930s, improvements to a technology could be clearly distinguished as either hardware improvements (e.g., improvements to the circuit structure of diodes, transistors, switches, etc.) or software improvements (improvements to the methodology). However, with technological advancements, many improvements to the methodology today can be considered direct improvements to the hardware circuit structure. Designers almost always obtain the corresponding hardware circuit structure by programming the improved methodology into the hardware circuit. Therefore, it cannot be said that an improvement to the methodology cannot be implemented using a hardware physical module. For example, a Programmable Logic Device (PLD) (e.g., a Field Programmable Gate Array (FPGA)) is such an integrated circuit whose logic function is determined by the user programming the device. Designers can program a digital system themselves to "integrate" it onto a PLD, without needing chip manufacturers to design and manufacture dedicated integrated circuit chips. Furthermore, nowadays, instead of manually manufacturing integrated circuit chips, this programming is mostly implemented using "logic compiler" software. Similar to the software compiler used in program development, the original code before compilation must be written in a specific programming language, called a Hardware Description Language (HDL). There are many HDLs, such as ABEL (Advanced Boolean Expression Language), AHDL (Altera Hardware Description Language), Confluence, CUPL (Cornell University Programming Language), HDCal, JHDL (Java Hardware Description Language), Lava, Lola, MyHDL, PALASM, and RHDL (Ruby Hardware Description Language). Currently, the most commonly used are VHDL (Very-High-Speed ​​Integrated Circuit Hardware Description Language) and Verilog. Those skilled in the art should understand that by simply performing some logic programming on the method flow using one of these hardware description languages ​​and programming it into an integrated circuit, the hardware circuit implementing the logical method flow can be easily obtained.

[0235] The controller can be implemented in any suitable manner. For example, it can take the form of a microprocessor or processor and a computer-readable medium storing computer-readable program code (e.g., software or firmware) executable by the (micro)processor, logic gates, switches, application-specific integrated circuits (ASICs), programmable logic controllers, and embedded microcontrollers. Examples of controllers include, but are not limited to, the following microcontrollers: ARC625D, Atmel AT91SAM, Microchip PIC18F26K20, and Silicon Labs C8051F320. A memory controller can also be implemented as part of the control logic of the memory. Those skilled in the art will also recognize that, in addition to implementing the controller in purely computer-readable program code form, the same functionality can be achieved by logically programming the method steps to make the controller take the form of logic gates, switches, ASICs, programmable logic controllers, and embedded microcontrollers. Therefore, such a controller can be considered a hardware component, and the means included therein for implementing various functions can also be considered as structures within the hardware component. Alternatively, the means for implementing various functions can be considered as both software modules implementing the method and structures within the hardware component.

[0236] The systems, devices, modules, or units described in the above embodiments can be implemented by computer chips or entities, or by products with certain functions. A typical implementation device is a computer. Specifically, a computer can be, for example, a personal computer, laptop computer, cellular phone, camera phone, smartphone, personal digital assistant, media player, navigation device, email device, game console, tablet computer, wearable device, or any combination of these devices.

[0237] For ease of description, the above apparatus is described by dividing it into various functional units. Of course, when implementing the embodiments of this specification, the functions of each unit can be implemented in one or more software and / or hardware.

[0238] Those skilled in the art will understand that one or more embodiments of this specification can be provided as a method, system, or computer program product. Therefore, one or more embodiments of this specification may take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, this specification may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0239] This specification is described with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of this specification. It will be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create a machine for implementing the flowchart illustrations and / or block diagrams. Figure 1 One or more processes and / or boxes Figure 1 A device that provides the functions specified in one or more boxes.

[0240] These computer program instructions may also be stored in a computer-readable storage medium that can direct a computer or other programmable data processing device to function in a particular manner, such that the instructions stored in the computer-readable storage medium produce an article of manufacture including instruction means, which are implemented in a process Figure 1 One or more processes and / or boxes Figure 1 The function specified in one or more boxes.

[0241] These computer program instructions may also be loaded onto a computer or other programmable data processing equipment to cause a series of operational steps to be performed on the computer or other programmable equipment to produce a computer-implemented process, thereby providing instructions that execute on the computer or other programmable equipment for implementing the process. Figure 1 One or more processes and / or boxes Figure 1 The steps of the function specified in one or more boxes.

[0242] In a typical configuration, a computing device includes one or more processors (CPU), input / output interfaces, network interfaces, and memory.

[0243] Memory may include non-persistent storage in computer-readable media, such as random access memory (RAM) and / or non-volatile memory, such as read-only memory (ROM) or flash RAM. Memory is an example of computer-readable media.

[0244] Computer-readable media includes both permanent and non-permanent, removable and non-removable media that can store information using any method or technology. Information can be computer-readable instructions, data structures, modules of programs, or other data. Examples of computer storage media include, but are not limited to, phase-change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technologies, CD-ROM, digital versatile optical disc (DVD) or other optical storage, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other non-transferable medium that can be used to store information accessible by a computing device. As defined herein, computer-readable media does not include transient computer-readable media, such as modulated data signals and carrier waves.

[0245] It should also be noted that the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes said element.

[0246] One or more embodiments of this specification can be described in the general context of computer-executable instructions, such as program modules, that are executed by a computer. Generally, program modules include routines, programs, objects, components, data structures, etc., that perform a particular task or implement a particular abstract data type. One or more embodiments of this specification can also be practiced in distributed computing environments where tasks are performed by remote processing devices connected via a communication network. In distributed computing environments, program modules can reside in local and remote computer storage media, including storage devices.

[0247] The various embodiments in this specification are described in a progressive manner. Similar or identical parts between embodiments can be referred to interchangeably. Each embodiment focuses on describing the differences from other embodiments. In particular, the system embodiments are basically similar to the method embodiments, so the description is relatively simple; relevant parts can be referred to the descriptions in the method embodiments.

[0248] The above description is merely an embodiment of this document and is not intended to limit the scope of this document. Various modifications and variations can be made to this document by those skilled in the art. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of this document should be included within the scope of the claims of this document.

Claims

1. A payment interaction processing method, comprising: receiving a payment request submitted by a target member of a member group after a payment identifier code of the target member is scanned by a merchant terminal; processing payment information carried by the payment request based on a resource account of a backup resource provider corresponding to backup resource information configured for the member group to obtain a payment bill; the backup resource provider includes an institutional member in the member group; generating a payment interaction message of each institutional member in the member group for the payment bill according to the member authority of each institutional member in the member group; if a verification request submitted by any target institutional member in the member group is received, determining a resource account of the any target institutional member and transferring resources corresponding to the payment information from the resource account to a payment account of the target member, generating and pushing a verification log of the payment bill according to a resource transfer result and a member identifier of the any target institutional member. 2.The payment interaction processing method of claim 1, after the receiving a payment request submitted by a target member of a member group after a payment identifier code of the target member is scanned by a merchant terminal step is executed, and before the processing payment information carried by the payment request based on a resource account of a backup resource provider corresponding to backup resource information configured for the member group to obtain a payment bill step is executed, further comprising: inquiring whether backup resources are allocated for the member group; if not, processing payment of the payment information based on a resource account of the target member to obtain a payment bill. 3.The payment interaction processing method of claim 2, if an execution result of the inquiring whether backup resources are allocated for the member group operation is yes, the processing payment information carried by the payment request based on a resource account of a backup resource provider corresponding to backup resource information configured for the member group to obtain a payment bill step is executed; wherein the processing payment information carried by the payment request based on a resource account of a backup resource provider corresponding to backup resource information configured for the member group to obtain a payment bill, comprises: in a case where the payment information meets backup payment conditions corresponding to the backup resource information, processing payment of the payment information based on a resource account corresponding to the backup resource information to obtain the payment bill; updating a backup resource amount in the backup resource information to an available resource amount based on a payment resource amount included in the payment information. 4.The payment interaction processing method of claim 3, the backup payment conditions include at least one of: a payment resource amount included in the payment information is less than or equal to the backup resource amount, a member identifier of the target member is recorded in an available member list configured by the backup resource information, and a payment time recorded by the payment information is within an available time range of the backup resource information. 5.The payment interaction processing method of claim 3, the updating a backup resource amount in the backup resource information to an available resource amount based on a payment resource amount included in the payment information, comprises: If a confirmation request of an institution member other than the target member in the member group is received for the payment bill, the available resource amount in the standby resource information is updated to the standby resource amount based on the confirmation request. 6.The payment interaction processing method of claim 3, wherein the standby resource information is configured in the following manner: obtaining a standby resource allocation request of a target institution member in the member group for the member group; acquiring a standby update type configured by the target institution member based on the standby resource allocation request; acquiring a standby resource parameter uploaded by the target institution member under the standby update type; determining the standby resource information allocated to the member group according to the standby update type and the standby resource parameter. 7.The payment interaction processing method of claim 6, wherein the available resource amount in the standby resource information is configured based on the standby update type contained in the standby resource information; if the standby update type is a first update type, the available resource amount in the standby resource information remains unchanged. 8.The payment interaction processing method of claim 7, further comprising: if the standby update type is a second update type, reading an update period condition contained in the standby resource information; calculating an update time for the available resource amount according to a payment time recorded in the payment bill and the update period condition; updating the available resource amount in the standby resource information to the standby resource amount if it is detected that the update time has arrived. 9.The payment interaction processing method of claim 1, wherein the payment interaction message for the payment bill of each institution member in the member group is generated according to a member authority of each institution member in the member group, comprising: determining a co-authority member having a co-authority for the payment bill among the institution members according to a payment type corresponding to the payment request; generating an audit label of the co-authority member for the payment bill and a payment interaction message containing the audit label based on the co-authority. 10.The payment interaction processing method of claim 1, wherein the interaction label of the target member is empty or a voucher submission label; the interaction label of an institution member other than the target member in the member group comprises a bill confirmation label, a bill return label and / or a voucher request label. 11.A payment interaction processing method, comprising: receiving a payment instruction submitted by a target member in a member group of an institution through triggering a payment interface of the member group; obtaining payment information collected for the payment instruction and generating a payment request to be submitted to a server; the server performs payment processing on the payment information carried by the payment request based on a resource account of a standby resource provider corresponding to standby resource information configured for the member group; the standby resource provider comprises an institution member in the member group; receiving a payment interaction message carrying an interaction label of the target member issued by the server and displaying the payment interaction message in an interaction list of the member group; if the interaction tag is detected to be triggered, a payment interaction request corresponding to the interaction tag is submitted to the server; a verification log of a payment bill pushed by the server is received; the verification log determines a resource account of any target institution member in the member group after receiving a verification request submitted by the target institution member, and transfers resources corresponding to the payment information from the resource account to a payment account of the target member according to a resource transfer result and a member identifier of the target institution member.

12. The payment interaction processing method of claim 11, wherein the payment instruction submitted by a target member in the member group of the receiving institution through triggering a payment interface of the member group comprises: an access request of the target member to the member group is obtained, and an access page is displayed based on the access request; a payment instruction submitted by the target member through triggering an identifier code collection component configured in the access page is received.

13. The payment interaction processing method of claim 12, wherein the payment information collected for the payment instruction is obtained and a payment request is generated and submitted to the server, comprising: the configured collection component is called to collect a payment identifier code and perform analysis; the payment information is obtained by interacting with the target member based on the analysis result, and a payment request containing the payment information is generated and submitted to the server.

14. The payment interaction processing method of claim 11, wherein the server performs the following operations after receiving the payment request: the payment information carried in the payment request is processed for payment, and a payment bill is generated; an interaction tag of the target member for the payment bill is determined according to a member right of the target member to the payment bill; access information of the target member for the payment bill is generated based on the interaction tag, and the payment interaction message containing the access information is generated and pushed to a member terminal of the target member.

15. The payment interaction processing method of claim 14, wherein if the interaction tag is detected to be triggered, a bill voucher for the payment bill is collected based on a tag type of the interaction tag, and the bill voucher is submitted to the server so that the server associates the bill voucher to the payment bill.

16. The payment interaction processing method of claim 15, further comprising: the bill voucher pushed by the server after associating the bill voucher to the payment bill is obtained; if the bill voucher is of a video type, the bill voucher is played when the member group is detected to be accessed.

17. The payment interaction processing method of claim 11, wherein the interaction tag is an interaction tag of a payment bill obtained by the server after the target member performs payment processing on the payment information.

18. A payment interaction processing device, comprising: ​ ​ The request receiving module is configured to receive a payment request submitted by a target member in a member group of an institution terminal scanning mechanism after scanning a payment identifier code of the target member; The payment processing module is configured to perform payment processing on payment information carried by the payment request based on a resource account of a backup resource provider corresponding to backup resource information configured for the member group, and obtain a payment bill; the backup resource provider includes an institutional member in the member group; The message generating module is configured to generate a payment interaction message of each institutional member in the member group for the payment bill according to a member authority of the each institutional member; If a verification request submitted by any target institutional member in the member group is received, a resource account of the any target institutional member is determined, and resources corresponding to the payment information are transferred from the resource account to a payment account of the target member, a verification log of the payment bill is generated and pushed according to a resource transfer result and a member identifier of the any target institutional member.

19. A payment interaction processing apparatus, comprising: The instruction receiving module is configured to receive a payment instruction submitted by a target member in a member group of an institution through triggering a payment interface of the member group; The request submitting module is configured to obtain payment information collected for the payment instruction and generate a payment request to submit to a server; the server performs payment processing on payment information carried by the payment request based on a resource account of a backup resource provider corresponding to backup resource information configured for the member group; the backup resource provider includes an institutional member in the member group; The message display module is configured to receive a payment interaction message carrying an interaction tag of the target member pushed by the server, and display the payment interaction message in an interaction list of the member group; If the interaction tag is detected to be triggered, an interaction request submitting module is run, the interaction request submitting module is configured to submit a payment interaction request corresponding to the interaction tag to the server; The verification log of the payment bill pushed by the server is received; the verification log is generated after receiving a verification request submitted by any target institutional member in the member group, a resource account of the any target institutional member is determined, and resources corresponding to the payment information are transferred from the resource account to a payment account of the target member, and the verification log is generated according to a resource transfer result and a member identifier of the any target institutional member.

20. A payment interaction processing device, comprising: A processor; And A memory configured to store computer executable instructions, the computer executable instructions, when executed, cause the processor to: Receive a payment request submitted by a target member in a member group of an institution terminal scanning mechanism after scanning a payment identifier code of the target member; Perform payment processing on payment information carried by the payment request based on a resource account of a backup resource provider corresponding to backup resource information configured for the member group, and obtain a payment bill; the backup resource provider includes an institutional member in the member group; generate a payment interaction message for each of the institution members in the member group according to a member right of each of the institution members in the member group; if a verification request submitted by any target institution member in the member group is received, determine a resource account of the target institution member and transfer resources corresponding to the payment information from the resource account to a payment account of the target member, and generate a verification log of the payment bill according to a resource transfer result and a member identifier of the target institution member and push the verification log.

21. A payment interaction processing device, comprising: a processor; and a memory configured to store computer executable instructions which, when executed, cause the processor to: receive a payment instruction submitted by a target member in a member group of an institution by triggering a payment interface of the member group; acquire payment information collected for the payment instruction and generate a payment request to submit to a server; the server performs payment processing on the payment information carried by the payment request based on a resource account of a backup resource provider corresponding to backup resource information configured for the member group; the backup resource provider includes an institution member in the member group; receive a payment interaction message carrying an interaction tag of the target member pushed by the server and display the payment interaction message in an interaction list of the member group; if it is detected that the interaction tag is triggered, submit a payment interaction request corresponding to the interaction tag to the server; receive a verification log of a payment bill pushed by the server; the verification log determines a resource account of any target institution member in the member group after receiving a verification request submitted by the target institution member, and transfers resources corresponding to the payment information from the resource account to a payment account of the target member, and generates according to a resource transfer result and a member identifier of the target institution member.

22. A storage medium for storing computer executable instructions which, when executed by a processor, implement the following processes: receive a payment request submitted by a merchant terminal after scanning a payment identifier code of a target member in a member group of an institution; perform payment processing on the payment information carried by the payment request based on a resource account of a backup resource provider corresponding to backup resource information configured for the member group, and obtain a payment bill; the backup resource provider includes an institution member in the member group; generate a payment interaction message for each of the institution members in the member group according to a member right of each of the institution members in the member group; if a payment interaction request submitted by any institution member based on an interaction tag is received, perform payment interaction processing on the payment interaction request.

23. A storage medium for storing computer executable instructions which, when executed by a processor, implement the following processes: receive a payment instruction submitted by a target member in a member group of an institution by triggering a payment interface of the member group; Obtaining payment information collected for the payment instruction and generating a payment request to submit to a server; the server performs payment processing on the payment information carried by the payment request based on the resource account of the backup resource provider corresponding to the backup resource information configured for the member group; the backup resource provider includes an institutional member in the member group; Receiving a payment interaction message carrying an interaction tag of the target member issued by the server, and displaying the payment interaction message in an interaction list of the member group; If it is detected that the interaction tag is triggered, a payment interaction request corresponding to the interaction tag is submitted to the server; a payment bill verification log pushed by the server is received; the verification log determines a resource account of any target institutional member in the member group after receiving a verification request submitted by the target institutional member, and transfers resources corresponding to the payment information from the resource account to a payment account of the target member, and generates a resource transfer result and a member identifier of the target institutional member according to the resource transfer result.

Images