Electronic red envelope sending and receiving method, server, management device, system and medium

Abstract

The application discloses an electronic red envelope sending and receiving method, a server, a management device, a system and a medium, and belongs to the field of data processing. The method comprises the following steps: receiving a red envelope payment message sent by a sender user terminal; sending the red envelope payment message to a management device, so that the management device sends the red envelope payment message to a card management system corresponding to a payment card identifier, and transfers resources with a resource amount of a red envelope sending resource amount from a payment card corresponding to the payment card identifier to a public transfer account; in the case that it is determined that a receiver user terminal has a user account and is bound with a receiving card, a red envelope receiving message is sent to the management device, so that the management device sends the red envelope receiving message to a card management system corresponding to the receiving card identifier, and transfers resources with a resource amount of a red envelope receiving resource amount from the public transfer account to a receiving card corresponding to the receiving card identifier. According to the embodiment of the application, the process of receiving an electronic red envelope to a transaction required card can be simplified.

Description

TECHNICAL FIELD

[0001] The application belongs to the field of data processing, and particularly relates to an electronic red envelope sending and receiving method, a server, a management device, a system and a medium. BACKGROUND

[0002] With the development of mobile payment technology, the mobile payment technology is applied more and more widely in people's life. For example, a user can send an electronic red envelope to relatives and friends through an application program, or receive an electronic red envelope sent by other users in the application program.

[0003] The resources of the electronic red envelope received by the user will enter an account created by the user in the application program, and the user needs to perform a cash-out operation to extract the resources of the electronic red envelope to a transaction-required card. The user can use the resources of the electronic red envelope extracted through the transaction-required card to make online or offline payment. The cash-out operation is relatively cumbersome, and the process of extracting the electronic red envelope to the transaction-required card by the user is also relatively cumbersome. SUMMARY

[0004] The embodiments of the application provide an electronic red envelope sending and receiving method, a server, a management device, a system and a medium, which can simplify the process of extracting the electronic red envelope to the transaction-required card by the user.

[0005] In a first aspect, the embodiments of the application provide an electronic red envelope sending and receiving method applied to a background server, and the method comprises the following steps: receiving a red envelope payment message sent by a sender user terminal, wherein the red envelope payment message comprises a red envelope sending resource amount and a payment card identifier; sending the red envelope payment message to a management device, so that the management device sends the red envelope payment message to a card management system corresponding to the payment card identifier, and transfers resources with the resource amount of the red envelope sending resource amount from a payment card corresponding to the payment card identifier to a public transfer account; in the case that it is determined that a receiver user terminal has a user account and is bound with a receiving card, sending a red envelope receiving message to the management device, so that the management device sends the red envelope receiving message to a card management system corresponding to the receiving card identifier, and transfers resources with the resource amount of the red envelope receiving resource amount from the public transfer account to a receiving card corresponding to the receiving card identifier, wherein the red envelope receiving message comprises the red envelope receiving resource amount and the receiving card identifier.

[0006] In a second aspect, the embodiments of the present application provide an electronic red envelope sending and receiving method applied to a management device, the method comprising: receiving a red envelope payment message sent by a background server, the red envelope payment message comprising a red envelope sending resource amount and a payment card identifier, the red envelope payment message being sent by a sender user terminal to the background server; sending the red envelope payment message to a card management system corresponding to the payment card identifier, and transferring resources with the resource amount being the red envelope sending resource amount from a payment card corresponding to the payment card identifier to a public transfer account; in a case where it is determined that a recipient user terminal has a user account and is bound with a receiving card, receiving a red envelope receiving message sent by the background server, the red envelope receiving message comprising a red envelope receiving resource amount and a receiving card identifier; sending the red envelope receiving message to a card management system corresponding to the receiving card identifier, and transferring resources with the resource amount being the red envelope receiving resource amount from the public transfer account to a receiving card corresponding to the receiving card identifier.

[0007] In a third aspect, the embodiments of the present application provide a background server, comprising: a receiving module configured to receive a red envelope payment message sent by a sender user terminal, the red envelope payment message comprising a red envelope sending resource amount and a payment card identifier; and a sending module configured to send the red envelope payment message to a management device, so that the management device sends the red envelope payment message to a card management system corresponding to the payment card identifier, and transfers resources with the resource amount being the red envelope sending resource amount from a payment card corresponding to the payment card identifier to a public transfer account; the sending module is further configured to, in a case where it is determined that a recipient user terminal has a user account and is bound with a receiving card, send a red envelope receiving message to the management device, so that the management device sends the red envelope receiving message to a card management system corresponding to the receiving card identifier, and transfers resources with the resource amount being the red envelope receiving resource amount from the public transfer account to a receiving card corresponding to the receiving card identifier, the red envelope receiving message comprising a red envelope receiving resource amount and a receiving card identifier.

[0008] In a fourth aspect, the embodiments of the present application provide a management device, comprising: a receiving module configured to receive a red envelope payment message sent by a background server, the red envelope payment message comprising a red envelope sending resource amount and a payment card identifier, the red envelope payment message being sent by a sender user terminal to the background server; a sending module configured to send the red envelope payment message to a card management system corresponding to the payment card identifier; and a resource transfer module configured to transfer resources with the resource amount being the red envelope sending resource amount from a payment card corresponding to the payment card identifier to a public transfer account; the receiving module is further configured to, in a case where it is determined that a recipient user terminal has a user account and is bound with a receiving card, receive a red envelope receiving message sent by the background server, the red envelope receiving message comprising a red envelope receiving resource amount and a receiving card identifier; the sending module is further configured to send the red envelope receiving message to a card management system corresponding to the receiving card identifier; and the resource transfer module is further configured to transfer resources with the resource amount being the red envelope receiving resource amount from the public transfer account to a receiving card corresponding to the receiving card identifier.

[0009] In a fifth aspect, an embodiment of the present application provides a background server, comprising a processor and a memory storing computer program instructions; the processor implements the electronic red envelope sending and receiving method of the first aspect when executing the computer program instructions.

[0010] In a sixth aspect, an embodiment of the present application provides a management device, comprising a processor and a memory storing computer program instructions; the processor implements the electronic red envelope sending and receiving method of the second aspect when executing the computer program instructions.

[0011] In a seventh aspect, an embodiment of the present application provides an electronic red envelope sending and receiving system, comprising the server of the fifth aspect and the management device of the sixth aspect.

[0012] In an eighth aspect, an embodiment of the present application provides a computer readable storage medium, the computer readable storage medium storing computer program instructions, the computer program instructions being executed by a processor to implement the electronic red envelope sending and receiving method of the first aspect or the electronic red envelope sending and receiving method of the second aspect.

[0013] The electronic red envelope sending and receiving method, the server, the management device, the system and the medium provided by the embodiments of the present application can receive the red envelope payment message sent by the sender user terminal, and send the red envelope payment message to the management device. The red envelope payment message comprises a red envelope sending resource amount and a payment card identifier. The management device can send the red envelope payment message to the card management system corresponding to the payment card identifier, so that the resource amount of the resource corresponding to the red envelope sending resource amount can be transferred from the payment card corresponding to the payment card identifier to the public transfer account. The background server can send the red envelope receiving message to the management device. The red envelope receiving message comprises a red envelope receiving resource amount and a receiving card identifier. The management device can send the red envelope receiving message to the card management system corresponding to the receiving card identifier, so that the resource amount of the resource corresponding to the red envelope receiving resource amount can be transferred from the public transfer account to the receiving card corresponding to the receiving card identifier, that is, the resource in the electronic red envelope can be directly transferred to the card required for the user transaction, and the user's cash-out operation is saved, and the process of the user receiving the electronic red envelope to the card required for the transaction is simplified. BRIEF DESCRIPTION OF DRAWINGS

[0014] In order to more clearly illustrate the technical solutions of the embodiments of the present application, the following will briefly introduce the drawings needed to be used in the embodiments of the present application. Those skilled in the art can obtain other drawings according to these drawings without creating any creative labor.

[0015] Figure 1 A schematic diagram of an example of an application scenario of the electronic red envelope sending and receiving method provided by the embodiments of the present application;

[0016] Figure 2 A flowchart of an embodiment of the electronic red envelope sending and receiving method provided by the first aspect of the present application;

[0017] Figure 3 Flow chart of another embodiment of the electronic red envelope sending and receiving method provided by the first aspect of the present application;

[0018] Figure 4 Flow chart of still another embodiment of the electronic red envelope sending and receiving method provided by the first aspect of the present application;

[0019] Figure 5 Flow chart of an embodiment of the electronic red envelope sending and receiving method provided by the second aspect of the present application;

[0020] Figure 6 Flow chart of another embodiment of the electronic red envelope sending and receiving method provided by the second aspect of the present application;

[0021] Figure 7 Flow chart of an example of the red envelope sending process provided by the embodiments of the present application;

[0022] Figure 8 Flow chart of an example of the red envelope receiving process provided by the embodiments of the present application;

[0023] Figure 9 Structural schematic diagram of an embodiment of the background server provided by the third aspect of the present application;

[0024] Figure 10 Structural schematic diagram of another embodiment of the background server provided by the third aspect of the present application;

[0025] Figure 11 Structural schematic diagram of still another embodiment of the background server provided by the third aspect of the present application;

[0026] Figure 12 Structural schematic diagram of an embodiment of the management device provided by the fourth aspect of the present application;

[0027] Figure 13 Structural schematic diagram of an embodiment of the background server provided by the fifth aspect of the present application;

[0028] Figure 14 Structural schematic diagram of an embodiment of the management device provided by the sixth aspect of the present application. DETAILED DESCRIPTION

[0029] The features and exemplary embodiments of various aspects of the present application will be described below in detail, in order to make the purposes, technical solutions and advantages of the present application more clear and apparent, the present application will be further described in detail below in combination with the drawings and specific embodiments. It should be understood that the specific embodiments described herein are only intended to explain the present application, but not to limit the present application. The present application can be implemented without some of these specific details for those skilled in the art. The following description of the embodiments is only to provide a better understanding of the present application by showing examples of the present application.

[0030] With the development of mobile payment technology, mobile payment technology is more and more widely used in people's life. For example, a user can distribute electronic red packets to friends and relatives through an application program, or receive electronic red packets distributed by other users in the application program. The resources of the electronic red packets received by the user will enter the account created by the user in the application program, and the user needs to perform a cash-out operation to extract the resources of the electronic red packets to a transaction card, so as to make online or offline payment by using the resources of the electronic red packets extracted from the transaction card. The cash-out operation needs to be manually operated by the user through the guidance of the application program, which is relatively cumbersome, resulting in a relatively cumbersome process of extracting the electronic red packets to the transaction card by the user.

[0031] The electronic red packet sending and receiving method, server, management device, system and medium provided by the embodiments of the present application can interact through the user terminal, the background server of the application program, the management device and the card management system, so that the red packets distributed by the red packet distribution user can directly enter the card of the red packet receiving user after being received by the red packet receiving user, saving the cash-out operation, simplifying the process of extracting the electronic red packets to the transaction card by the user, and improving the user experience.

[0032] Figure 1 An example of the application scenario of the electronic red packet sending and receiving method provided by the embodiments of the present application is shown in the schematic diagram. Figure 1 As shown in the figure, the electronic red packet sending and receiving method provided by the embodiments of the present application can involve a user terminal 11, a background server 12 of an application program, a management device 13 and a card management system 14.

[0033] The user terminal 11 can include a sender user terminal 111 for distributing red packets and a receiver user terminal 112 for receiving red packets. For a user terminal 11, the user terminal 11 can be a sender user terminal 111 or a receiver user terminal 112, and the identity of the user terminal 11 can be determined according to the task to be performed by the user. In the embodiments of the present application, in order to facilitate the description of the two processes of sending and receiving electronic red packets, the user terminal 11 is divided into the sender user terminal 111 and the receiver user terminal 112 for description.

[0034] The user terminal 11 can be installed with an application program. The user can realize the sending and receiving of the electronic red packet by operating the application program in the user terminal 11. The user terminal 11 can interact with the background server of the application program to realize the interaction between the user and the background server. The user terminal can include a mobile phone, a tablet computer, a smart wearable device, and the like, which are not limited herein.

[0035] The background server 12 is a background server of the application program installed in the user terminal 11, which can provide data, functions, and the like for the application program, which are not limited herein. The background server 12 can communicate with the management device 13 to complete the interaction of information, data, instructions, and the like.

[0036] The management device 13 can be a general term of devices constituting a management system, and the types and quantities of the management device 13 are not limited herein. The management device 13 can communicate with the background server 12, and can also communicate with the card management system. The different management devices 13 can also communicate with each other, which are not limited herein. For example, part of the management devices 13 can constitute a channel management system for channel transactions, and part of the management devices 13 can constitute an information processing center system for forwarding transaction information and performing clearing related businesses, which are not limited herein. The channel management system and the information processing center system can be respectively arranged, or can be integrated, which are not limited herein. The background server 12 can specifically interact with the management device 13 of the channel management system, the management device 13 of the channel management system can interact with the management device 13 in the information processing center system, and the management device 13 in the information processing center system can interact with the card management system.

[0037] The card management system 14 is used for managing cards and resources in the cards. The card management system 14 can include one or more servers, which are not limited herein. In order to distinguish the cards for deducting resources in the red packet and the cards for receiving resources in the red packet, the card for deducting resources in the red packet will be referred to as a payment card, and the card for receiving resources in the red packet will be referred to as a receiving card. The card in the embodiment of the application can specifically include a bank card, which can refer to a bank card account or a virtual bank card, which are not limited herein.

[0038] In the embodiment of the application, the resources in the electronic red packet can include funds, electronic money, and the like, which are not limited herein.

[0039] The electronic red packet sending and receiving method, the server, the management device, the system, and the medium provided by the application will be described one by one as follows.

[0040] The first aspect of the application provides an electronic red packet sending and receiving method, which can be applied to a background server, that is, the electronic red packet sending and receiving method can be executed by the background server. Figure 2 The flowchart of an embodiment of the electronic red packet sending and receiving method provided by the first aspect of the application is shown in FIG. 1. As shown in FIG. 1, the electronic red packet sending and receiving method provided by the first aspect of the application can include the following steps. Figure 2As shown, the electronic red envelope sending and receiving method can include steps S201 to S203.

[0041] In step S201, a red envelope payment message sent by a sender user terminal is received.

[0042] The sender user terminal is a user terminal of a red envelope sender. In the process of sending a red envelope by a user, the sender user terminal can display a red envelope sending function interface, and the sender user terminal receives input of the user on the red envelope sending function interface and can send a red envelope payment message to a background server. The red envelope payment message includes a red envelope sending resource amount and a payment card identifier.

[0043] The red envelope sending resource amount is the resource amount in the sent electronic red envelope. For example, if the resource in the electronic red envelope is fund, the red envelope sending resource amount represents the amount of fund in the electronic red envelope. The red envelope payment message can represent sending one red envelope this time, or can represent sending multiple red envelopes this time. In some examples, the red envelope payment message can further include an electronic red envelope quantity. In the case that the electronic red envelope quantity is greater than or equal to 2, the red envelope sending resource amount can include a total resource amount and a single electronic red envelope resource amount. The single electronic red envelope resource amount of different electronic red envelopes can be the same or different, which is not limited herein. The electronic red envelope resource amount can be set by the user or can be a randomly generated resource amount, which is not limited herein. In some examples, a limit condition can be set in advance for the red envelope sending resource amount, which is not limited herein. For example, if the resource is fund, the minimum value of the red envelope sending resource amount can be set to 0.01 yuan, and the maximum value of the red envelope sending resource amount can be set to 2000 yuan.

[0044] The payment card identifier is used to identify a payment card. According to the payment card identifier, the payment card and the card management system to which the payment card belongs can be determined. The payment card identifier can include a card number, a payment Token, etc., which is not limited herein.

[0045] In some examples, the sender user terminal can select an electronic red envelope cover pattern, add a red envelope note, etc. in response to user input, which is not limited herein.

[0046] In some examples, the background server can also provide a candidate recipient list to the sender user terminal, so that the user of the red envelope sender can select the user of the red envelope recipient, which is not limited herein.

[0047] In step S202, the red envelope payment message is sent to a management device, so that the management device sends the red envelope payment message to the card management system corresponding to the payment card identifier, and transfers the resource with the resource amount of the red envelope sending resource amount from the payment card corresponding to the payment card identifier to a public transfer account.

[0048] The background server sends the red packet payment message to the management device. In some examples, the background server can first send the red packet payment message to the channel management system, and the channel management system sends the red packet payment message to the information processing center system. The payment card identifier corresponds to the card management system to which the payment card belongs. The management device sends the red packet payment message to the card management system to which the payment card belongs, and the card management system can verify in response to the red packet payment message, and in the case of successful verification, deduct resources, i.e., transfer resources in the payment card with an amount equal to the red packet sending resource amount to the public transfer account.

[0049] The public transfer account is a shared account, and the number of public transfer accounts is not limited herein and can be one or multiple. The public transfer account can be managed by the management device or the card management system. In some examples, the public transfer account can be a transfer account shared by multiple red packet senders and multiple red packet recipients. In other examples, the public transfer account can be a transfer account shared by multiple red packet senders. In yet other examples, the public transfer account can be a transfer account shared by multiple red packet recipients, which is not limited herein.

[0050] In some examples, the red packet payment message can further include an electronic red packet identifier. The electronic red packet identifier is used to identify the electronic red packet, and the electronic red packet identifier can ensure that the resources transferred out of the payment card of the red packet sender can be received by the red packet recipient and directly transferred to the receiving card of the red packet recipient.

[0051] After the resources of the electronic red packet are transferred from the payment card to the public transfer account, the management device can send a resource deduction success message to the background server, and the background server can send the resource deduction success message to the sender user terminal to notify the red packet sender that the red packet sending is successful.

[0052] In step S203, in the case where it is determined that the recipient user terminal has a user account and is bound to a receiving card, a red packet receiving message is sent to the management device to enable the management device to send the red packet receiving message to the card management system corresponding to the receiving card identifier, and transfer resources with an amount equal to the red packet receiving resource amount from the public transfer account to the receiving card corresponding to the receiving card identifier.

[0053] The recipient user terminal is a red packet recipient user terminal. In the process of receiving the red packet by the user, the recipient user terminal can display a red packet receiving function interface, and the recipient user terminal can interact with the user through the red packet receiving function interface. The red packet receiving message includes a red packet receiving resource amount and a receiving card identifier.

[0054] The red envelope receiving resource amount is the resource amount in the received electronic red envelope. For example, if the resource in the electronic red envelope is money, the red envelope receiving resource amount represents the amount of money in the received electronic red envelope.

[0055] The receiving card identifier is used to identify the receiving card. According to the receiving card identifier, the receiving card and the card management system to which the receiving card belongs can be determined. The card management system corresponding to the receiving card identifier is the card management system to which the receiving card belongs. The receiving card identifier can include a card number, a payment token, etc., which are not limited herein.

[0056] In some examples, the sender user terminal can specify that the resource does not need to be actively received and is transferred to the receiving card of the receiving user. After the sender user terminal sends the electronic red envelope and the resource amount of the red envelope sending resource is transferred to the public transfer account, the background server can send a red envelope receiving message to the management device without receiving the message sent by the receiving user terminal, so that the management device sends the red envelope receiving message to the card management system to which the receiving card belongs. The card management system can verify in response to the red envelope receiving message, and allow the resource amount of the red envelope receiving resource in the public transfer account to be transferred to the receiving card if the verification is successful. In this process, the receiving user terminal does not need to send a red envelope receiving message to the background server.

[0057] In other examples, the sender user terminal can specify that the resource needs to be actively received before being transferred to the receiving card of the receiving user. After the sender user terminal sends the electronic red envelope and the resource amount of the red envelope sending resource is transferred to the public transfer account, the background server needs to wait for the red envelope receiving message sent by the receiving user terminal. After the background server receives the red envelope receiving message sent by the receiving user terminal, the background server sends the red envelope receiving message to the management device, so that the management device sends the red envelope receiving message to the card management system to which the receiving card belongs. The card management system can verify in response to the red envelope receiving message, and allow the resource amount of the red envelope receiving resource in the public transfer account to be transferred to the receiving card if the verification is successful. In this process, the receiving user terminal needs to send a red envelope receiving message to the background server.

[0058] For example, the red envelope payment message can also include receiving mode information. The receiving mode information is used to indicate the receiving mode of the electronic red envelope. The receiving mode information can include a first identifier or a second identifier. The first identifier indicates that the background server sends the red envelope receiving message to the management device in the case of receiving the red envelope receiving message sent by the receiving user terminal, i.e., the receiving user terminal needs to actively initiate the red envelope receiving process. The second identifier indicates that the red envelope receiving message is sent to the management device without receiving the red envelope receiving message sent by the receiving user terminal, i.e., the receiving user terminal does not need to actively initiate the red envelope receiving process, and the resource of the electronic red envelope can be directly transferred to the corresponding receiving card.

[0059] In some examples, the red packet receiving message further comprises an electronic red packet identifier. The electronic red packet identifier in the matched red packet payment message and the red packet receiving message is the same, and the management device and the card management device can transfer the resource in the electronic red packet corresponding to the electronic red packet identifier in the public transfer account to the receiving card corresponding to the receiving card identifier in the red packet receiving message according to the electronic red packet identifier in the red packet receiving message.

[0060] In some examples, the management device and / or the background server can prompt the user to receive the electronic red packet by sending a red packet path link, a red packet password, a red packet two-dimensional code, etc. to the receiving party user terminal. Similarly, the receiving party user terminal can also trigger the red packet receiving process by using the red packet path link, the red packet password, the red packet two-dimensional code, etc.

[0061] In some embodiments, in the case that the resource of the electronic red packet is transferred to the receiving card, the background server and the management device can update data according to the payment card identifier, the receiving card identifier, the resource amount of the red packet sent, the resource amount of the red packet received, the user information of the account logged in by the sender user terminal, the user information of the account logged in by the receiving party user terminal, etc.

[0062] In the case that the resource of the electronic red packet is transferred from the public transfer account to the receiving card, the management device can send a red packet receiving success message to the background server, and the background server can send the red packet receiving success message to the sender user terminal and the receiving party user terminal to notify the user of the red packet sender and the user of the red packet receiving party that the red packet receiving is successful.

[0063] In some embodiments, the background server and / or the management device can set a red packet receiving duration. If the duration of the resource of the electronic red packet transferred to the public transfer account reaches the red packet receiving duration but has not been transferred to the receiving card, i.e., the electronic red packet has not been received within the red packet receiving duration after being sent, the management server can interact with the card management system corresponding to the payment card identifier to transfer the resource of the electronic red packet in the public transfer account that has not been received back to the payment card. For example, if the electronic red packet sent by the user of the red packet sender through the sender user terminal is not received by the user of the red packet receiving party through the receiving party user terminal within 24 hours, the resource of the electronic red packet transferred from the payment card of the user of the red packet sender to the public transfer account is transferred back to the payment card of the user of the red packet sender.

[0064] In the embodiment of the present application, the background server can receive the red envelope payment message sent by the sender user terminal, and send the red envelope payment message to the management device. The red envelope payment message includes the red envelope sending resource amount and the payment card identifier. The management device can send the red envelope payment message to the card management system corresponding to the payment card identifier, so as to transfer the resource with the resource amount of the red envelope sending resource amount from the payment card corresponding to the payment card identifier to the public transfer account. The background server can send the red envelope receiving message to the management device. The red envelope receiving message includes the red envelope receiving resource amount and the receiving card identifier. The management device can send the red envelope receiving message to the card management system corresponding to the receiving card identifier, so as to transfer the resource with the resource amount of the red envelope receiving resource amount from the public transfer account to the receiving card corresponding to the receiving card identifier, that is, the resource in the electronic red envelope can be directly transferred to the card required for user transaction, saving the user's cashing operation, simplifying the process of the user receiving the electronic red envelope to the card required for transaction, and improving the user experience.

[0065] In some embodiments, the user of the red envelope sender can specify the user of the red envelope receiver through the sender user terminal. Figure 3 The flowchart of another embodiment of the electronic red envelope transceiving method provided for the first aspect of the present application. Figure 3 Different from Figure 2 The difference is that Figure 3 The electronic red envelope transceiving method shown in FIG. 4 can further include steps S204 to S210.

[0066] In step S204, the red envelope payment request message sent by the sender user terminal is received.

[0067] The sender user terminal can send the red envelope payment request message to the background server before sending the red envelope payment request message to the background server. The red envelope payment request message is used to request sending a red envelope, and can specify the user of the red envelope receiver. The red envelope payment request message includes the specified receiver communication information. The user of the red envelope receiver can be determined by the specified receiver communication information. The specified receiver communication information is used to indicate the communication contact information of the user of the red envelope receiver. The specified receiver communication information can be obtained from the address book list of the sender user terminal, which is not limited herein. For example, the specified receiver communication information can include a mobile phone number, an email address, a communication tool account, etc., which is not limited herein.

[0068] In step S205, the target user account matching the specified receiver communication information is found.

[0069] The background server can first find whether there is a user account matching the specified receiver communication information. When a user registers a user account in the background server, some user information will be uploaded correspondingly, and the user information can include a mobile phone number, an email address, a communication tool account, etc.

[0070] The target user account matching the specified receiver communication information can be found in the background server, indicating that the user corresponding to the specified receiver communication information has registered in the application corresponding to the background server. The target user account matching the specified receiver communication information is not found in the background server, indicating that the user corresponding to the specified receiver communication information has not registered in the application corresponding to the background server.

[0071] In step S206, in the case of finding the target user account, a verification request message is sent to the sender user terminal.

[0072] The verification request message is used to request the user's identity information for identity verification from the sender user terminal. The sender user terminal can respond to the verification request message and send a verification reply message to the background server.

[0073] In step S207, the verification reply message sent by the sender user terminal is received.

[0074] The verification reply message includes user identity information. The user identity information can include a mobile phone number, name, and other information that can represent the identity of the user of the red packet receiver, which is not limited here.

[0075] In step S208, it is verified whether the user identity information in the verification reply message is consistent with the user identity information associated with the target user account.

[0076] The user identity information in the verification reply message is consistent with the user identity information associated with the target user account, indicating that the user indicated by the target user account and the user indicated by the user identity information provided by the sender user terminal are the same person, and the subsequent process of the electronic red packet sending and receiving method can continue.

[0077] The user identity information in the verification reply message is not consistent with the user identity information associated with the target user account, indicating that the user indicated by the target user account and the user indicated by the user identity information provided by the sender user terminal are not the same person, and the subsequent process of the electronic red packet sending and receiving method should be interrupted to ensure transaction security.

[0078] In step S209, in the case where the user identity information in the verification reply message is consistent with the user identity information associated with the target user account, a first red packet receiving message is sent to the receiver user terminal corresponding to the target user account.

[0079] The first red packet receiving message is used to prompt the user corresponding to the target user account to receive the electronic red packet. The receiver user terminal can receive the first red packet receiving message in the case of logging in the target user account.

[0080] In some examples, the first red packet receiving message can include, but is not limited to, any one of a red packet path link, a red packet password, a red packet two-dimensional code, etc. The receiving user terminal directly views details of resource transfer of the electronic red packet to the receiving card by accessing the red packet path link, copying or inputting the red packet password, scanning the red packet two-dimensional code, etc., or triggers sending of the red packet receiving message to the background server, which is not limited herein.

[0081] In some examples, in the case that the target user account is found, the background server can also not send a verification request message to the sending user terminal, i.e., does not perform verification of the user identity information, and directly sends the first red packet receiving message to the receiving user terminal corresponding to the target user account, which is not limited herein.

[0082] In step S210, in the case that the target user account is not found, a second red packet receiving message is sent to the receiving user terminal specified by the specified receiving communication information through the communication channel indicated by the specified receiving communication information.

[0083] The second red packet receiving message can be used to prompt the specified red packet receiving user to receive the electronic red packet. Sending the second red packet receiving message to the receiving user terminal through the specified receiving communication information can expand the range of the red packet receiving user, i.e., even if the red packet receiving user indicated by the specified receiving communication information is not a friend of the red packet sending user in the application program, or the red packet receiving user indicated by the specified receiving communication information is not registered in the application program, the second red packet receiving message can still be received, which improves the openness and flexibility of red packet sending and receiving, and also accumulates relationship data between the red packet sending user and the red packet receiving user, perfects the user relationship portrait, and further improves the user experience.

[0084] For example, the specified receiving communication information includes a mobile phone number, the background server can send a short message to the receiving user terminal corresponding to the mobile phone number through the short message service, the short message can be regarded as the second red packet receiving message, or the short message can include the second red packet receiving message.

[0085] For another example, the specified receiving communication information includes an email address, the background server can send an email to the email of the red packet receiving user corresponding to the mobile phone number through the email service, the email can be regarded as the second red packet receiving message, or the email includes the second red packet receiving message.

[0086] The second red envelope receiving message can include, but is not limited to, any one of the following: a red envelope path link, a red envelope password, and a red envelope two-dimensional code. The receiving party user terminal can perform operations such as application registration, receiving card binding, triggering the sending of a red envelope receiving message to the background server, and viewing details of the transfer of resources of the electronic red envelope to the receiving card by accessing the red envelope path link, copying or inputting the red envelope password, and scanning the red envelope two-dimensional code, and the like, without being limited herein.

[0087] In some embodiments, the background server can send the red envelope receiving request message to the management device after receiving the red envelope receiving request message sent by the receiving party user terminal. Figure 4 A flowchart of another embodiment of the electronic red envelope transceiving method provided by the first aspect of the present application is shown in FIG. 3. Figure 4 Different from Figure 2 , the electronic red envelope transceiving method shown in FIG. 3 can further include steps S211 to S213. Figure 4 The electronic red envelope transceiving method shown in FIG. 3 can further include steps S211 to S213.

[0088] In step S211, the red envelope receiving request message sent by the receiving party user terminal is received.

[0089] The red envelope receiving request message can be used to trigger the red envelope receiving process and can include user information.

[0090] In step S212, it is determined whether the receiving party user terminal has registered a user account and bound a receiving card according to the red envelope receiving request message.

[0091] The background server can match the user information in the red envelope receiving request message with the user information associated with the registered user account to determine whether the receiving party user terminal has registered a user account and bound a receiving card.

[0092] In step S213, prompt information is sent to the receiving party user terminal in a case where it is determined that the receiving party user terminal has not registered a user account and / or has not bound a receiving card.

[0093] The prompt information is used to instruct the receiving party user terminal to register a user account and / or bind a receiving card. After the receiving party user terminal registers a user account and binds a receiving card, the background server can obtain information such as the receiving card identifier of the receiving card and the amount of red envelope receiving resources, thereby interacting with the management device to complete the receiving of the resources of the electronic red envelope to the receiving card.

[0094] The second aspect of the present application provides an electronic red envelope transceiving method, which can be applied to a management device, i.e., the electronic red envelope transceiving method can be executed by the management device. Figure 5 A flowchart of an embodiment of the electronic red envelope transceiving method provided by the second aspect of the present application is shown in FIG. 4. Figure 5 As shown in FIG. 4, the electronic red envelope transceiving method can include steps S301 to S304.

[0095] In step S301, the red envelope payment message sent by the background server is received.

[0096] The red envelope payment message includes a red envelope sending resource amount and a payment card identifier. The red envelope payment message is sent by the sender user terminal to the background server.

[0097] In some examples, the red envelope payment message can further include an electronic red envelope quantity, and the red envelope sending resource amount can include a total resource amount and a single electronic red envelope resource amount. Details can be referred to the related description in the above embodiments, which will not be repeated here.

[0098] In some examples, the red envelope payment message can further include pickup method information. The pickup method information includes a first identifier or a second identifier. The first identifier indicates that the red envelope pickup message is sent by the background server in the case that the red envelope pickup message sent by the pickup user terminal is received. The second identifier indicates that the red envelope pickup message is sent by the background server in the case that the red envelope request message sent by the pickup user terminal is not received. Details of the pickup method information, the first identifier, the second identifier, etc. can be referred to the related description in the above embodiments, which will not be repeated here.

[0099] In step S302, the red envelope payment message is sent to the card management system corresponding to the payment card identifier, and the resource amount of the resource amount of the red envelope sending resource amount is transferred from the payment card corresponding to the payment card identifier to the public transfer account.

[0100] In step S303, the red envelope pickup message sent by the background server is received in the case that the pickup user terminal has a user account and is bound with a receiving card.

[0101] The red envelope pickup message includes a red envelope pickup resource amount and a receiving card identifier.

[0102] The red envelope pickup message received by the management device can be triggered by the background server in response to the operation of the pickup user terminal actively picking up. The red envelope pickup message received by the management device can also be actively sent by the background server in the case that the pickup user terminal does not actively pick up in the case that the sender user terminal specifies in the red envelope payment message that the pickup user terminal does not need to actively pick up.

[0103] In some examples, the management device and / or the background server can prompt the pickup user terminal to pick up the electronic red envelope by sending a red envelope path link, a red envelope password, a red envelope two-dimensional code, etc. Similarly, the pickup user terminal can also trigger the red envelope pickup process by using the red envelope path link, the red envelope password, the red envelope two-dimensional code, etc.

[0104] In step S304, the red envelope receiving message is sent to the card management system corresponding to the receiving card identifier, and the resource amount of the red envelope is transferred from the public transfer account to the receiving card corresponding to the receiving card identifier.

[0105] The specific content of steps S301 to S304 can be referred to the related description in the above embodiments, which will not be repeated here.

[0106] In some examples, the management device and / or the background server can prompt the user to receive the electronic red envelope by sending the red envelope path link, the red envelope password, the red envelope two-dimensional code, etc. to the receiving user terminal. Similarly, the receiving user terminal can also trigger the red envelope receiving process by using the red envelope path link, the red envelope password, the red envelope two-dimensional code, etc.

[0107] In some embodiments, in the case that the resource of the electronic red envelope is transferred to the receiving card, the background server and the management device can update the data according to the payment card identifier, the receiving card identifier, the red envelope sending resource amount, the red envelope receiving resource amount, the user information of the account logged in by the sending user terminal, the user information of the account logged in by the receiving user terminal, etc.

[0108] In the case that the resource of the electronic red envelope is transferred from the public transfer account to the receiving card, the management device can send the red envelope receiving success message to the background server, and the background server can send the red envelope receiving success message to the sending user terminal and the receiving user terminal to notify the user of the red envelope sender and the user of the red envelope receiver that the red envelope receiving is successful.

[0109] In some embodiments, the background server and / or the management device can set the red envelope receiving duration. If the duration of the resource of the electronic red envelope in the public transfer account reaches the red envelope receiving duration but has not been transferred to the receiving card, i.e., the electronic red envelope is not received within the red envelope receiving duration after being sent, the management server can interact with the card management system corresponding to the payment card identifier to transfer the resource of the electronic red envelope that has not been received in the public transfer account back to the payment card. For example, if the electronic red envelope sent by the user of the red envelope sender through the sending user terminal is not received by the user of the red envelope receiver through the receiving user terminal within 24 hours, the resource of the electronic red envelope transferred from the payment card of the user of the red envelope sender to the public transfer account is transferred back to the payment card of the user of the red envelope sender.

[0110] In the embodiments of the present application, the background server can receive the red envelope payment message sent by the sender user terminal. The management device receives the red envelope payment message sent by the background server. The red envelope payment message includes the red envelope sending resource amount and the payment card identifier. The management device can send the red envelope payment message to the card management system corresponding to the payment card identifier, so as to transfer the resource with the resource amount of the red envelope sending resource amount from the payment card corresponding to the payment card identifier to the public transfer account. The management device can receive the red envelope receiving message sent by the background server. The red envelope receiving message includes the red envelope receiving resource amount and the receiving card identifier. The management device can send the red envelope receiving message to the card management system corresponding to the receiving card identifier, so as to transfer the resource with the resource amount of the red envelope receiving resource amount from the public transfer account to the receiving card corresponding to the receiving card identifier, that is, the resource in the electronic red envelope can be directly transferred to the card required for the user transaction, which saves the user's cashing operation and simplifies the process of the user receiving the electronic red envelope to the card required for the transaction.

[0111] In some embodiments, the user of the red envelope sender can specify the user of the red envelope receiver through the sender user terminal, and the red envelope payment message can further include the specified receiver communication information.

[0112] In some examples, in the case that the background server finds the target user account matching the specified receiver communication information, the specified receiver communication information is used to instruct the background server to send the first red envelope receiving message to the receiver user terminal. For example, the first red envelope receiving message can include, but is not limited to, any one of the red envelope path link, the red envelope password, the red envelope two-dimensional code, etc.

[0113] In some examples, in the case that the background server does not find the target user account matching the specified receiver communication information, the specified receiver communication information is used to instruct the background server to send the second red envelope receiving message to the receiver user terminal specified by the specified receiver communication information through the communication channel indicated by the specified receiver communication information. For example, the second red envelope receiving message can include, but is not limited to, any one of the red envelope path link, the red envelope password, the red envelope two-dimensional code.

[0114] The specific content of the specified receiver communication message, the first red envelope receiving message and the second red envelope receiving message can be referred to the related description in the above embodiments, which will not be described here.

[0115] In some embodiments, the red envelope payment message can further include the electronic red envelope identifier, and correspondingly, the red envelope receiving message can further include the electronic red envelope identifier. The management device and the card management device can transfer the resource in the electronic red envelope corresponding to the electronic red envelope identifier in the public transfer account to the receiving card according to the electronic red envelope identifier in the red envelope receiving message. Figure 6 The flowchart of another embodiment of the electronic red envelope transceiving method provided by the second aspect of the present application. Figure 6 WithFigure 5 The difference is that, Figure 5 Step S302 can be further refined as follows: Figure 6 Step S3021 in the process, Figure 5 Step S304 can be further refined as follows: Figure 6 Step S3041 in the process.

[0116] In step S3021, a red packet payment message is sent to the card management system corresponding to the payment card identifier, and the resource amount equal to the red packet sending resource amount is transferred from the payment card corresponding to the payment card identifier to the resource pool corresponding to the electronic red packet identifier in the public transfer account.

[0117] In step S3041, a red packet claim message is sent to the card management system corresponding to the receiving card identifier, and the resources with the red packet claim resource amount are transferred from the resource pool corresponding to the electronic red packet identifier in the public transfer account to the receiving card corresponding to the receiving card identifier.

[0118] When a user sends an electronic red envelope through their user terminal, the payment message includes an electronic red envelope identifier. The management device can then establish a resource pool corresponding to that identifier in the public transfer account, and the resources associated with the electronic red envelope are transferred to that resource pool. When the electronic red envelope is received by a user through their user terminal, the receipt message includes an electronic red envelope identifier, and this identifier matches the one in the payment message. Resources in the resource pool corresponding to the electronic red envelope identifier in the receipt message can then be transferred to the corresponding receiving card.

[0119] When a user sending multiple electronic red envelopes at once via their sending terminal, each electronic red envelope can have its own unique electronic red envelope identifier, and these identifiers are different for different electronic red envelopes. Alternatively, when a user sending multiple electronic red envelopes at once via their sending terminal, the electronic red envelopes have the same electronic red envelope identifier. The management device can establish a resource pool corresponding to the electronic red envelope identifier in the public transfer account, and the resources of the electronic red envelopes corresponding to that identifier are transferred to the resource pool. When the electronic red envelope is received by a user receiving it via their receiving terminal, the red envelope receipt message includes the electronic red envelope identifier, and the resources in the resource pool corresponding to the electronic red envelope identifier in the red envelope receipt message can be transferred to the corresponding receiving card.

[0120] For ease of explanation, the following will use the one-to-one red envelope sending and receiving process as examples.

[0121] Figure 7 A flowchart of an example of the red envelope sending process provided by an embodiment of the present application. As shown in the figure, the red envelope sending process can include steps S401 to S417. Figure 7

[0122] In step S401, the sender user terminal initiates a red envelope sending request to the background server.

[0123] In step S402, the background server feeds back the user list to the sender user terminal.

[0124] In step S403, the sender user terminal displays the user list and the user verification form.

[0125] In step S404, the sender user terminal receives the user input, and obtains the user indicated by the user input, the mobile phone number of the user, and the name of the user.

[0126] In step S405, the user, the mobile phone number of the user, and the name of the user are sent to the background server.

[0127] In step S406, the background server verifies the user according to the user, the mobile phone number of the user, and the name of the user, and obtains a verification result.

[0128] In step S407, the verification result is fed back to the sender user terminal.

[0129] In step S408, in the case where the user has a user account and is bound to a receiving card, the sender user terminal displays a receiving method selection interface. The receiving method selection page can select the red envelope receiving method, i.e., whether the red envelope needs to be actively received.

[0130] In step S409, the sender user terminal displays a red envelope sending function interface, and provides selectable red envelope covers, red envelope resource amount input boxes, etc.

[0131] In step S410, in response to the user input to the red envelope sending function interface, the sender user terminal sends a red envelope payment message to the background server.

[0132] In step S411, the background server sends the red envelope payment message to the management device.

[0133] In step S412, the management device sends the red envelope payment message to the card management system of the payment card.

[0134] In step S413, the card management system performs verification and deduction by using the red envelope payment message. ​

[0135] In step S414, in case of verifying the withholding pass, the card management system transfers the resource amount of the red packet sending resource amount in the red packet payment information from the payment card to the public transfer account of the management device.

[0136] In step S415, the card management system sends a payment response message to the management device, the payment response message including result information of transferring the resource from the payment card to the public transfer account of the management device.

[0137] In step S416, the management device sends the payment response message to the background server.

[0138] In step S417, the background server sends the payment response message to the sender user terminal.

[0139] The specific content of steps S401 to S417 can be referred to the related description in the above embodiments, which will not be repeated here.

[0140] Figure 8 A flowchart of an example of the red packet receiving process provided by the embodiments of the present application is shown in FIG. 5. Figure 8 As shown in FIG. 5, the red packet receiving process can include steps S501 to S513.

[0141] In step S501, the receiver user terminal receives the user's trigger operation such as copying password, clicking link or scanning two-dimensional code, and triggers sending of a red packet receiving request message to the background server.

[0142] In step S502, the background server verifies the receiver user terminal according to the red packet receiving request message, and determines whether the receiver user terminal is registered with a user account and binds a receiving card. If the receiver user terminal is not registered with a user account and / or does not bind a receiving card, jump to step S503; if the receiver user terminal is registered with a user account and binds a receiving card, jump to step S504.

[0143] In step S503, the background server receives the registration and binding card message sent by the receiver user terminal, and registers the user account and binds the receiving card, and jump to step S504.

[0144] In step S504, the receiver user terminal receives the user input, and the user input triggers the receiver user terminal to send a red packet receiving message.

[0145] In step S505, the receiver user terminal sends the red packet receiving message to the background server.

[0146] In step S506, the background server sends the red packet receiving message to the management device.

[0147] In step S507, the management device sends a verification credit request to the card management system of the receiving card.

[0148] In step S508, the card management system verifies the user information and obtains a verification result.

[0149] In step S509, the card management system sends the verification result to the management device.

[0150] In step S510, in a case where the verification result indicates that the verification is passed, the management device transfers the resource amount of the red envelope taking resource amount in the red envelope taking message from the public transfer account to the receiving card.

[0151] In step S511, the card management system sends a taking response message to the management device, the taking response message including result information of the resource transfer from the public transfer account of the management device to the receiving card.

[0152] In step S512, the management device sends the taking response message to the background server.

[0153] In step S513, the background server sends the taking response message to the taking party user terminal.

[0154] In some cases, the background server also sends the taking response message to the sending party user terminal.

[0155] The specific content of steps S501 to S513 can be referred to the related description in the above embodiments, which will not be repeated here.

[0156] The third aspect of the present application provides a background server. Figure 9 An embodiment of the background server provided by the third aspect of the present application is shown in a structural schematic diagram. As shown in the figure, the background server 600 can include a receiving module 601 and a sending module 602. Figure 9

[0157] The receiving module 601 can be used to receive the red envelope payment message sent by the sending party user terminal.

[0158] The red envelope payment message includes a red envelope sending resource amount and a payment card identifier.

[0159] In some examples, the red envelope payment message further includes taking mode information, and the taking mode information includes a first identifier or a second identifier. The first identifier indicates that the red envelope taking message is sent to the management device in a case where the red envelope taking message sent by the taking party user terminal is received. The second identifier indicates that the red envelope taking message is sent to the management device in a case where the red envelope taking message sent by the taking party user terminal is not received.

[0160] In some examples, the red envelope payment message further includes an electronic red envelope identifier. ​

[0161] In some examples, the red packet payment message also includes the number of electronic red packets, and the red packet sending resource includes the total resource and the resource of a single electronic red packet.

[0162] The sending module 602 can be used to send a red envelope payment message to the management device, so that the management device sends a red envelope payment message to the card management system corresponding to the payment card identifier, and transfers the resource amount equal to the red envelope sending resource amount from the payment card corresponding to the payment card identifier to the public transfer account.

[0163] The sending module 602 can also be used to send a red envelope receiving message to the management device when it is determined that the receiving user terminal has a user account and is bound to a receiving card, so that the management device sends a red envelope receiving message to the card management system corresponding to the receiving card identifier, and transfers the resource amount equal to the red envelope receiving resource amount from the public transfer account to the receiving card corresponding to the receiving card identifier.

[0164] The message for receiving a red envelope includes the amount of red envelope resources received and the identifier of the receiving card.

[0165] In some examples, the message for claiming the red envelope also includes an electronic red envelope identifier.

[0166] In this embodiment, the backend server can receive a red envelope payment message sent by the sending user terminal and send the message to the management device. The red envelope payment message includes the red envelope sending resource amount and the payment card identifier. The management device can send the red envelope payment message to the card management system corresponding to the payment card identifier, thereby transferring resources equal to the red envelope sending resource amount from the payment card corresponding to the payment card identifier to the public transfer account. The backend server can send a red envelope receiving message to the management device. The red envelope receiving message includes the red envelope receiving resource amount and the receiving card identifier. The management device can send the red envelope receiving message to the card management system corresponding to the receiving card identifier, thereby transferring resources equal to the red envelope receiving resource amount from the public transfer account to the receiving card corresponding to the receiving card identifier. That is, the resources in the electronic red envelope can be directly transferred to the card required for the user's transaction, eliminating the user's withdrawal operation, simplifying the process of the user receiving the electronic red envelope and transferring it to the card required for the transaction, and improving the user experience.

[0167] In some embodiments, the red packet payment message may also include communication information specifying the recipient. Figure 10 A schematic diagram of another embodiment of the backend server provided in the third aspect of this application. Figure 10 and Figure 9 The difference is that, Figure 10 The backend server 600 shown may also include a lookup module 603 and a verification module 604.

[0168] The receiving module 601 can also be configured to receive a red envelope payment request message sent by the sender user terminal, the red envelope payment request message comprising specified receiver communication information.

[0169] The searching module 603 can also be configured to search for a target user account matching the specified receiver communication information.

[0170] The sending module 602 can also be configured to send, in the case where the target user account is found, a first red envelope receiving message to a receiver user terminal corresponding to the target user account.

[0171] The sending module 602 can also be configured to send, in the case where the target user account is not found, a second red envelope receiving message to a receiver user terminal specified by the specified receiver communication information through a communication channel indicated by the specified receiver communication information.

[0172] In some examples, the second red envelope receiving message comprises any of the following: a red envelope path link, a red envelope password, and a red envelope two-dimensional code.

[0173] In some examples, the sending module 602 can also be configured to send, in the case where the target user account is found, a verification request message to the sender user terminal.

[0174] The receiving module 601 can also be configured to receive a verification reply message sent by the sender user terminal, the verification reply message comprising user identity information.

[0175] The verification module 604 can be configured to verify whether the user identity information in the verification reply message is consistent with user identity information associated with the target user account.

[0176] The sending module 602 can be configured to send, in the case where the user identity information in the verification reply message is consistent with the user identity information associated with the target user account, the first red envelope receiving message to the receiver user terminal corresponding to the target user account.

[0177] Figure 11 A structural schematic diagram of still another embodiment of the background server provided in the third aspect of the present application. Figure 11 Different from Figure 9 , the background server 600 shown in FIG. 6 further comprises a processing module 605. Figure 11 The receiving module 601 can also be configured to receive a red envelope receiving request message sent by the receiver user terminal.

[0178] The receiving module 601 can also be configured to receive a red envelope receiving request message sent by the receiver user terminal.

[0179] The red envelope receiving request message comprises user information.

[0180] The processing module 605 can be configured to determine, according to the red envelope receiving request message, whether the receiver user terminal has registered a user account and bound a receiving card.

[0181] The sending module 602 can also be configured to send prompt information to the user terminal of the recipient in a case where it is determined that the user terminal of the recipient is not registered with a user account and / or is not bound with a receiving card.

[0182] The prompt information is used to instruct the user terminal of the recipient to register a user account and / or bind a receiving card.

[0183] The fourth aspect of the present application provides a management device. Figure 12 An embodiment of the management device provided by the fourth aspect of the present application is shown in a structural schematic diagram. As shown in the diagram, the management device 700 can include a receiving module 701, a sending module 702, and a resource transfer module 703. Figure 12

[0184] The receiving module 701 can be configured to receive a red envelope payment message sent by a background server.

[0185] The red envelope payment message includes a red envelope sending resource amount and a payment card identifier. The red envelope payment message is sent by a sender user terminal to the background server.

[0186] In some examples, the red envelope payment message further includes pickup method information, which includes a first identifier or a second identifier. The first identifier indicates that the red envelope pickup message is sent by the background server in a case where the red envelope pickup message sent by the user terminal of the recipient is received. The second identifier indicates that the red envelope pickup message is sent by the background server in a case where the red envelope pickup message sent by the user terminal of the recipient is not received.

[0187] In some examples, the red envelope payment message further includes an electronic red envelope quantity. The red envelope sending resource amount includes a total resource amount and a single electronic red envelope resource amount.

[0188] The sending module 702 can be configured to send the red envelope payment message to a card management system corresponding to the payment card identifier.

[0189] The resource transfer module 703 can be configured to transfer resources with the red envelope sending resource amount from a payment card corresponding to the payment card identifier to a public transfer account.

[0190] The receiving module 701 can also be configured to receive a red envelope pickup message sent by the background server in a case where it is determined that the user terminal of the recipient has a user account and is bound with a receiving card.

[0191] The red envelope pickup message includes a red envelope pickup resource amount and a receiving card identifier.

[0192] The sending module 702 can also be configured to send the red envelope pickup message to a card management system corresponding to the receiving card identifier.

[0193] ​The resource transfer module 703 can also be configured to transfer the resource with the resource amount of the red envelope receiving resource amount from the public transfer account to the receiving card corresponding to the receiving card identifier.

[0194] In the embodiments of the present application, the background server can receive the red envelope payment message sent by the sender user terminal. The management device receives the red envelope payment message sent by the background server. The red envelope payment message includes the red envelope sending resource amount and the payment card identifier. The management device can send the red envelope payment message to the card management system corresponding to the payment card identifier, so as to transfer the resource with the resource amount of the red envelope sending resource amount from the payment card corresponding to the payment card identifier to the public transfer account. The management device can receive the red envelope receiving message sent by the background server. The red envelope receiving message includes the red envelope receiving resource amount and the receiving card identifier. The management device can send the red envelope receiving message to the card management system corresponding to the receiving card identifier, so as to transfer the resource with the resource amount of the red envelope receiving resource amount from the public transfer account to the receiving card corresponding to the receiving card identifier. That is, the resource in the electronic red envelope can be directly transferred to the card required for transaction, which saves the user's cashing operation and simplifies the process of the user receiving the electronic red envelope to the card required for transaction.

[0195] In some embodiments, the red envelope payment message further includes the specified receiving party communication information.

[0196] In the case that the background server finds the target user account matching the specified receiving party communication information, the specified receiving party communication information is used to instruct the background server to send the first red envelope receiving message to the receiving party user terminal.

[0197] In the case that the background server does not find the target user account matching the specified receiving party communication information, the specified receiving party communication information is used to instruct the background server to send the second red envelope receiving message to the receiving party user terminal specified by the specified receiving party communication information through the communication channel indicated by the specified receiving party communication information.

[0198] In some examples, the second red envelope receiving message includes any one of the following: a red envelope path link, a red envelope password, and a red envelope two-dimensional code.

[0199] In some embodiments, the red envelope payment message further includes the electronic red envelope identifier, and the red envelope receiving message further includes the electronic red envelope identifier.

[0200] The resource transfer module 703 can be configured to transfer the resource with the resource amount of the red envelope sending resource amount from the payment card corresponding to the payment card identifier to the resource pool corresponding to the electronic red envelope identifier in the public transfer account.

[0201] The resource transfer module 703 can be configured to transfer the resource with the resource amount of the red envelope receiving resource amount from the resource pool corresponding to the electronic red envelope identifier in the public transfer account to the receiving card corresponding to the receiving card identifier.

[0202] The fifth aspect of the present application further provides a background server. Figure 13 An embodiment of the background server provided by the fifth aspect of the present application is shown in a structural schematic diagram. As shown in the figure, Figure 13 The background server 800 includes a memory 801, a processor 802 and a computer program stored in the memory 801 and executable on the processor 802.

[0203] In one example, the processor 802 can include a central processing unit (CPU), or an application specific integrated circuit (ASIC), or one or more integrated circuits configured to implement one or more embodiments of the present application.

[0204] The memory 801 can include a read-only memory (ROM), a random access memory (RAM), a magnetic disk storage medium device, an optical storage medium device, a flash memory device, an electrical, optical or other physical / tangible memory storage device. Therefore, generally, the memory includes one or more tangible (non-transitory) computer-readable storage media (e.g., memory devices) encoded with software including computer-executable instructions and when the software is executed (e.g., by one or more processors), it is operable to perform the operations described with reference to the electronic red packet transceiving method according to the first aspect of the embodiments of the present application.

[0205] The processor 802 runs the computer program corresponding to the executable program code stored in the memory 801 by reading the executable program code, for implementing the electronic red packet transceiving method of the first aspect of the above-described embodiments.

[0206] In one example, the background server 800 can further include a communication interface 803 and a bus 804. As shown in the figure, Figure 13 The memory 801, the processor 802 and the communication interface 803 are connected through the bus 804 and complete communication among each other.

[0207] The communication interface 803 is mainly used to realize the communication among various modules, devices, units and / or equipment in the embodiments of the present application. The input device and / or the output device can also be accessed through the communication interface 803.

[0208] Bus 804 includes hardware, software, or both, to couple components of background server 800 to each other and to couple them both to other components, including a user within a particular environment, not shown for the sake of clarity. By way of example, and not limitation, bus 804 can be an Accelerated Graphics Port (AGP) or other graphics bus, an Enhanced Industry Standard Architecture (EISA) bus, a Front Side Bus (FSB), a Hyper Transport (HT) interconnect, an Industry Standard Architecture (ISA) bus, an InfiniBand interconnect, a Low Pin Count (LPC) bus, a memory bus, a Micro Channel Architecture (MCA) bus, a Peripheral Component Interconnect (PCI) bus, a PCI-Express (PCI-E) bus, a Serial Advanced Technology Attachment (SATA) bus, a Video Electronics Standards Association Local (VLB) bus, or some other suitable bus or a combination of two or more of these. Where appropriate, bus 804 can include one or more buses. Although this application describes and shows a particular bus, this application contemplates any suitable bus or interconnect.

[0209] The sixth aspect of the application further provides a management device. Figure 14 An embodiment of the management device provided by the sixth aspect of the application is shown in a structural schematic diagram. As shown in the figure, the management device 900 includes a memory 901, a processor 902, and a computer program stored in the memory 901 and executable on the processor 902. Figure 14

[0210] In one example, the processor 902 described above can include a central processing unit (CPU), or an application specific integrated circuit (ASIC), or can be configured to implement one or more integrated circuits of the embodiments of the application.

[0211] ​The memory 901 can include a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk storage medium device, an optical storage medium device, a flash memory device, an electrical, optical, or other physical / tangible memory storage device. Therefore, generally, the memory includes one or more tangible (non-transitory) computer-readable storage media (e.g., memory devices) encoded with software including computer-executable instructions, and when the software is executed (e.g., by one or more processors), it is operable to perform the operations described with reference to the electronic red envelope transceiving method according to the second aspect in the embodiments of the present application.

[0212] The processor 902 runs a computer program corresponding to the executable program code stored in the memory 901 by reading the executable program code, for implementing the electronic red envelope transceiving method of the second aspect in the above-described embodiments.

[0213] In one example, the management device 900 can further include a communication interface 903 and a bus 904. As shown, the memory 901, the processor 902, and the communication interface 903 are connected through the bus 904 and complete communication among each other. Figure 14

[0214] The communication interface 903 is mainly used to implement the communication among various modules, devices, units, and / or equipment in the embodiments of the present application. The input device and / or the output device can also be accessed through the communication interface 903.

[0215] ​Bus 904 includes a hardware, software, or both that couples components of management device 900 to each other. As an example and not by way of limitation, bus 904 can include an accelerated graphics port (AGP) or other graphics bus, an enhanced industry standard architecture (EISA) bus, a front side bus (FSB), a Hyper Transport (HT) interconnect, an industry standard architecture (ISA) bus, an infinitiband interconnect, a low pin count (LPC) bus, a memory bus, a Micro Channel Architecture (MCA) bus, a peripheral component interconnect (PCI) bus, a PCI-Express (PCI-E) bus, a serial advanced technology attachment (SATA) bus, a video electronics standards association local (VLB) bus, or another suitable bus or a combination of two or more of these. Where appropriate, bus 904 can include one or more buses. Although this application describes and shows a particular bus, this application contemplates any suitable bus or interconnect.

[0216] A seventh aspect of the present application provides an electronic red envelope sending and receiving system. The electronic red envelope sending and receiving system can include the background server and the management device in the above embodiments, and the specific content can be referred to the related description in the above embodiments, which will not be described here.

[0217] In some embodiments, the electronic red envelope sending and receiving system can further include the user terminal and / or the card management system in the above embodiments. The user terminal can include the sender user terminal and the recipient user terminal in the above embodiments.

[0218] The eighth aspect of the present application also provides a computer readable storage medium, which stores computer program instructions. The computer program instructions are executed by a processor to implement the electronic red packet sending and receiving method in the above embodiments, and achieve the same technical effects. To avoid repetition, details are not described herein. The computer readable storage medium can include a non-transitory computer readable storage medium, such as a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk, and the like, which is not limited herein.

[0219] It should be noted that each of the embodiments in the present specification is described in a progressive manner, and the same or similar parts between each embodiment can be referred to each other. Each embodiment mainly describes the difference from other embodiments. For the device embodiment, the background server embodiment, the management device embodiment, the system embodiment, and the computer readable storage medium embodiment, the relevant parts can be referred to the description of the method embodiment. The present application is not limited to the specific steps and structures described above and shown in the drawings. Those skilled in the art can make various changes, modifications and additions, or change the order of the steps, after understanding the spirit of the present application. Moreover, for the sake of simplicity, the detailed description of the known method technology is omitted herein.

[0220] The aspects of the present application are described above with reference to flowcharts and / or block diagrams of the method, device (system) and computer program product according to the embodiments of the present application. It should be understood that each block in the flowcharts and / or block diagrams, and the combination of the blocks in the flowcharts 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, a special-purpose computer, or other programmable data processing apparatus, to produce a machine, so that the instructions executed by the processor of the computer or other programmable data processing apparatus enable the implementation of the functions / acts specified in one or more blocks of the flowcharts and / or block diagrams. The processor can be, but is not limited to, a general-purpose processor, a special-purpose processor, a special application processor, or a field programmable logic circuit. It should also be understood that each block in the block diagrams and / or flowcharts, and the combination of the blocks in the block diagrams and / or flowcharts, can also be implemented by special hardware to perform the specified functions or acts, or can be implemented by a combination of special hardware and computer instructions.

[0221] It should be understood by those skilled in the art that the above embodiments are exemplary but not limiting. Different technical features appearing in different embodiments can be combined to achieve beneficial effects. Other changed embodiments of the disclosed embodiments can be understood and implemented by those skilled in the art based on the drawings, the specification and the claims. In the claims, the term "comprising" does not exclude other devices or steps; the numerical term "one" does not exclude a plurality; the terms "first", "second" are used to designate names and not to indicate any particular order. Any reference signs in the claims should not be understood as limiting the scope of protection. The functions of multiple parts appearing in the claims can be implemented by a single hardware or software module. The fact that certain technical features appear in different dependent claims does not mean that these technical features cannot be combined to achieve beneficial effects.

Claims

1. An electronic red envelope transceiving method, characterized in that, The method is applied to a background server and comprises the following steps: receiving a red envelope payment message sent by a sender user terminal, wherein the red envelope payment message comprises specified receiver communication information, a red envelope sending resource amount and a payment card identifier, and the receiver communication information is used to determine a user of a red envelope receiver; sending the red envelope payment message to a management device, so that the management device sends the red envelope payment message to a card management system corresponding to the payment card identifier, and transfers a resource with the resource amount of the red envelope sending resource amount from a payment card corresponding to the payment card identifier to a public transfer account; in a case where it is determined that a receiver user terminal has a user account and is bound to a receiving card, sending a red envelope receiving message to the management device, so that the management device sends the red envelope receiving message to a card management system corresponding to the receiving card identifier, and transfers a resource with the resource amount of the red envelope receiving resource amount from the public transfer account to the receiving card corresponding to the receiving card identifier, wherein the red envelope receiving message comprises the red envelope receiving resource amount and the receiving card identifier, and the user account matches the specified receiver communication information.

2. The method of claim 1, wherein, before receiving the red envelope payment message sent by the sender user terminal, the method further comprises: receiving a red envelope payment request message sent by the sender user terminal, wherein the red envelope payment request message comprises specified receiver communication information; finding a target user account matching the specified receiver communication information; in a case where the target user account is found, sending a first red envelope receiving message to the receiver user terminal corresponding to the target user account; in a case where the target user account is not found, sending a second red envelope receiving message to the receiver user terminal specified by the specified receiver communication information through a communication channel indicated by the specified receiver communication information. before sending the first red envelope receiving message to the receiver user terminal corresponding to the target user account, the method further comprises:

3. The method of claim 2, wherein, in a case where the target user account is found, sending a verification request message to the sender user terminal; receiving a verification reply message sent by the sender user terminal, wherein the verification reply message comprises user identity information; verifying whether the user identity information in the verification reply message is consistent with user identity information associated with the target user account; the step of sending the first red envelope receiving message to the receiver user terminal corresponding to the target user account comprises: in a case where the user identity information in the verification reply message is consistent with the user identity information associated with the target user account, sending the first red envelope receiving message to the receiver user terminal corresponding to the target user account. The second red envelope receiving message comprises any one of the following:

4. The method of claim 2, wherein, a red envelope path link, a red envelope password, and a red envelope two-dimensional code. before sending the red envelope receiving message to the management device in a case where it is determined that a receiver user terminal has a user account and is bound to a receiving card, the method further comprises:

5. The method of claim 1, wherein, receiving a red envelope receiving request message sent by the receiver user terminal, wherein the red envelope receiving request message comprises user information; ​ According to the red envelope receiving request message, it is determined whether the receiving party user terminal has registered a user account and bound the receiving card; In the case where it is determined that the receiving party user terminal has not registered a user account and / or has not bound the receiving card, prompt information is sent to the receiving party user terminal, and the prompt information is used to instruct the receiving party user terminal to register a user account and / or bind the receiving card.

6. The method of claim 1, wherein, The red envelope payment message further includes receiving mode information, and the receiving mode information includes a first identifier or a second identifier, The first identifier indicates that the red envelope receiving message is sent to the management device in the case where the red envelope receiving message sent by the receiving party user terminal is received, The second identifier indicates that the red envelope receiving message is sent to the management device in the case where the red envelope receiving message sent by the receiving party user terminal is not received.

7. The method of claim 1, wherein, The red envelope payment message further includes an electronic red envelope identifier, and the red envelope receiving message further includes the electronic red envelope identifier.

8. The method of claim 1, wherein, The red envelope payment message further includes an electronic red envelope quantity, and the red envelope sending resource quantity includes a total resource quantity and a single electronic red envelope resource quantity.

9. An electronic red envelope transceiving method, characterized in that, The method applied to a management device comprises: receiving a red envelope payment message sent by a background server, the red envelope payment message including specified receiving party communication information, a red envelope sending resource quantity, and a payment card identifier, the red envelope payment message being sent by a sender user terminal to the background server, the specified receiving party communication information being used to determine a red envelope receiving party user; sending the red envelope payment message to a card management system corresponding to the payment card identifier, and transferring resources with the red envelope sending resource quantity from a payment card corresponding to the payment card identifier to a public transfer account; in the case where it is determined that the receiving party user terminal has a user account and is bound with a receiving card, receiving a red envelope receiving message sent by the background server, the red envelope receiving message including the red envelope receiving resource quantity and the receiving card identifier, the user account matching the specified receiving party communication information; sending the red envelope receiving message to a card management system corresponding to the receiving card identifier, and transferring resources with the red envelope receiving resource quantity from the public transfer account to a receiving card corresponding to the receiving card identifier.

10. The method of claim 9, wherein in the case where the background server finds a target user account matching the specified receiving party communication information, the specified receiving party communication information is used to instruct the background server to send a first red envelope receiving message to a receiving party user terminal, in the case where the background server does not find a target user account matching the specified receiving party communication information, the specified receiving party communication information is used to instruct the background server to send a second red envelope receiving message to the receiving party user terminal indicated by the specified receiving party communication information through a communication path indicated by the specified receiving party communication information.

11. The method of claim 10, wherein, The second red envelope receiving message includes any one of the following: a red envelope path link, a red envelope password, and a red envelope two-dimensional code.

12. The method of claim 9, wherein, The red envelope payment message further includes receiving mode information, and the receiving mode information includes a first identifier or a second identifier, The first identifier indicates that the red envelope taking message is sent by the background server in a case where the background server receives the red envelope taking message sent by the taking party user terminal, The second identifier indicates that the red envelope taking message is sent by the background server in a case where the background server does not receive the red envelope taking message sent by the taking party user terminal.

13. The method of claim 9, wherein, The red envelope payment message further comprises an electronic red envelope identifier, and the red envelope taking message further comprises an electronic red envelope identifier; The resource amount is the resource amount of the red envelope sending resource, and the resource is transferred from the payment card corresponding to the payment card identifier to the public transfer account. The resource amount is the resource amount of the red envelope taking resource, and the resource is transferred from the resource pool corresponding to the electronic red envelope identifier in the public transfer account to the receiving card corresponding to the receiving card identifier. The red envelope payment message further comprises an electronic red envelope quantity, and the red envelope sending resource amount comprises a total resource amount and a single electronic red envelope resource amount. Comprise:

14. The method of claim 1, wherein, The receiving module is used for receiving the red envelope payment message sent by the sender user terminal, and the red envelope payment message comprises specified taking party communication information, red envelope sending resource amount and payment card identifier, and the taking party communication information is used for determining the user of the red envelope taking party; 15. A back-end server, characterized by The sending module is used for sending the red envelope payment message to the management device, so that the management device sends the red envelope payment message to the card management system corresponding to the payment card identifier, and transfers the resource amount of the red envelope sending resource from the payment card corresponding to the payment card identifier to the public transfer account; The sending module is further used for sending the red envelope taking message to the management device in a case where the taking party user terminal has a user account and is bound with a receiving card, so that the management device sends the red envelope taking message to the card management system corresponding to the receiving card identifier, and transfers the resource amount of the red envelope taking resource from the public transfer account to the receiving card corresponding to the receiving card identifier, the red envelope taking message comprises the red envelope taking resource amount and the receiving card identifier, and the user account matches the specified taking party communication information. Comprise: The receiving module is used for receiving the red envelope payment message sent by the background server, and the red envelope payment message comprises specified taking party communication information, red envelope sending resource amount and payment card identifier, and the red envelope payment message is sent by the sender user terminal to the background server, and the taking party communication information is used for determining the user of the red envelope taking party; 16. A management device, characterized by comprising: The sending module is used for sending the red envelope payment message to the card management system corresponding to the payment card identifier; The resource transfer module is used for transferring the resource amount of the red envelope sending resource from the payment card corresponding to the payment card identifier to the public transfer account; ​ ​ The receiving module is further configured to receive the red envelope receiving message sent by the background server, the red envelope receiving message comprising the red envelope receiving resource amount and the receiving card identifier, in a case where it is determined that the receiving party user terminal has a user account and is bound with a receiving card, and the user account matches the specified receiving party communication information; The sending module is further configured to send the red envelope receiving message to a card management system corresponding to the receiving card identifier; The resource transferring module is further configured to transfer a resource with a resource amount of the red envelope receiving resource amount from the public transfer account to a receiving card corresponding to the receiving card identifier.

17. A back-end server, comprising: Comprising: a processor and a memory storing computer program instructions; The processor executes the computer program instructions to implement the electronic red envelope receiving and sending method of any one of claims 1 to 8.

18. A management device, comprising: Comprising: a processor and a memory storing computer program instructions; The processor executes the computer program instructions to implement the electronic red envelope receiving and sending method of any one of claims 9 to 14.

19. An electronic red envelope transceiving system, characterized in that, The server of claim 17 and the management device of claim 18 are comprised.

20. A computer-readable storage medium, characterized in that, The computer readable storage medium stores computer program instructions, and the computer program instructions are executed by the processor to implement the electronic red envelope receiving and sending method of any one of claims 1 to 14.

Images