CN115314880B

CN115314880B - Payment object binding method, device, system and medium based on 5G message application

Info

Publication number: CN115314880B
Application number: CN202210848150.2A
Authority: CN
Inventors: 傅珏; 赵海; 回春野; 谭颖; 孙权; 杨阳; 侯腾; 杨波; 张彦超; 佟冬; 胡明涛; 吴裕; 高峰; 陈硌琼
Original assignee: China Unionpay Co Ltd
Current assignee: China Unionpay Co Ltd
Priority date: 2022-07-19
Filing date: 2022-07-19
Publication date: 2024-08-20
Anticipated expiration: 2042-07-19
Also published as: CN115314880A

Abstract

The application discloses a payment object binding method, device, system and medium based on 5G message application, and belongs to the field of data processing. The method comprises the following steps: in response to a first input of the user to the 5G message application, sending, by the 5G message application, a payment object binding request to the 5G message payment platform through the 5G message application background system; receiving a binding trigger link fed back by the 5G message payment platform through a 5G message application background system by the 5G message application; triggering the 5G message application to call the payment application based on a second input of the binding trigger link by the user; the user identification and the payment object identification are transmitted to the payment system by the payment application, so that the payment system binds the payment object indicated by the user identification and the payment object identification, and the user identification is used for representing the mobile phone number of the user. According to the embodiment of the application, the binding of the user and the payment object in the 5G message application can be realized.

Description

Payment object binding method, device, system and medium based on 5G message application

Technical Field

The application belongs to the field of data processing, and particularly relates to a payment object binding method, device, system and medium based on 5G message application.

Background

The fifth generation mobile communication technology (5th Generation Mobile Communication Technology,5G) message is a conventional short message upgrading technology, and can provide a message service with multimedia and interactive capabilities. A 5G message application is an application that implements 5G messages.

At present, electronic payment is very popular, and in order to meet the requirement of users on electronic payment, it is desirable to bind a 5G message application with a payment object, so as to realize payment based on the 5G message application. There is therefore a need for a payment object binding method based on 5G messaging applications.

Disclosure of Invention

The embodiment of the application provides a payment object binding method, device, system and medium based on a 5G message application, which can realize the binding of a user and a payment object in the 5G message application.

In a first aspect, an embodiment of the present application provides a payment object binding method based on a 5G message application, applied to a terminal device, where the terminal device has a 5G message application and a payment application, and the method includes: in response to a first input of the user to the 5G message application, sending, by the 5G message application, a payment object binding request to the 5G message payment platform through the 5G message application background system; receiving a binding trigger link fed back by the 5G message payment platform through a 5G message application background system by the 5G message application; triggering the 5G message application to call the payment application based on a second input of the binding trigger link by the user; the user identification and the payment object identification are transmitted to the payment system by the payment application, so that the payment system binds the payment object indicated by the user identification and the payment object identification, and the user identification is used for representing the mobile phone number of the user.

In a second aspect, a payment object binding method based on a 5G message application is applied to a 5G message payment platform, and the method includes: receiving a payment object binding request sent by a 5G message application of terminal equipment through a 5G message application background system, wherein the terminal equipment is provided with the 5G message application and a payment application; and feeding back a binding triggering link to the 5G message application through the 5G message application background system, so that the 5G message application is triggered to call the payment application to transmit a user identifier and a payment object identifier to the payment system based on the binding triggering link, and the payment system binds the payment object indicated by the user identifier and the payment object identifier, wherein the user identifier is used for representing the mobile phone number of the user.

In a third aspect, an embodiment of the present application provides a terminal device having a 5G message application and a payment application, the terminal device including: the sending module is used for responding to the first input of the user to the 5G message application, and is called by the 5G message application to send a payment object binding request to the 5G message payment platform through the 5G message application background system; the receiving module is used for being called by the 5G message application to receive binding triggering links fed back by the 5G message payment platform through a 5G message application background system; the processing module is used for triggering the 5G message application to call the payment application based on the second input of the binding triggering link by the user; the sending module is also used for being called by the payment application to transmit the user identification and the payment object identification to the payment system so that the payment system binds the payment object indicated by the user identification and the payment object identification, and the user identification is used for representing the mobile phone number of the user.

In a fourth aspect, an embodiment of the present application provides a payment object binding apparatus based on a 5G message application, applied to a 5G message payment platform, where the apparatus includes: the receiving module is used for receiving a payment object binding request sent by a 5G message application of the terminal equipment through a 5G message application background system, wherein the terminal equipment is provided with the 5G message application and the payment application; the sending module is used for feeding back the binding triggering link to the 5G message application through the 5G message application background system, so that the 5G message application is triggered to call the payment application to transmit the user identification and the payment object identification to the payment system based on the binding triggering link, the payment object indicated by the user identification and the payment object identification is bound by the payment system, and the user identification is used for representing the mobile phone number of the user.

In a fifth aspect, an embodiment of the present application provides a terminal device, including: a processor and a memory storing computer program instructions; the processor, when executing the computer program instructions, implements the payment object binding method of the first aspect based on the 5G message application.

In a sixth aspect, an embodiment of the present application provides an electronic device, including: a processor and a memory storing computer program instructions; the processor, when executing the computer program instructions, implements the payment object binding method of the second aspect based on the 5G message application.

In a seventh aspect, an embodiment of the present application provides a payment system based on a 5G message application, including: a terminal device for executing the 5G message application-based payment object binding method of the first aspect; a 5G message payment platform for performing the 5G message application based payment object binding method of the second aspect.

In an eighth aspect, an embodiment of the present application provides a computer readable storage medium, on which computer program instructions are stored, which when executed by a processor implement the 5G message application-based payment object binding method of the first aspect or the 5G message application-based payment object binding method of the second aspect.

The embodiment of the application provides a payment object binding method, device, system and medium based on a 5G message application, wherein in response to first input of the 5G message application in terminal equipment by a user, the 5G message application and a 5G message payment platform interact through a 5G message application background system, and a binding trigger link fed back by the 5G message payment platform is acquired. Based on the second input to the binding trigger link, the 5G message application can be automatically triggered to invoke the payment application, which transmits the user identification and the payment object identification to the payment system. The payment system can bind the user identification with the payment object indicated by the payment object identification according to the received user identification and the payment object identification, so that the binding of the user and the payment object in the 5G message application is realized, the blank of the binding of the user and the payment object in the 5G message application is made up, and the subsequent realization of the payment based on the 5G message application is facilitated.

Drawings

In order to more clearly illustrate the technical solution of the embodiments of the present application, the drawings that are needed to be used in the embodiments of the present application will be briefly described, and it is possible for a person skilled in the art to obtain other drawings according to these drawings without inventive effort.

Fig. 1 is a schematic diagram of an application scenario of a payment object binding method based on a 5G message application according to an embodiment of the present application;

FIG. 2 is a flowchart of a method for binding payment objects based on a 5G messaging application according to an embodiment of the first aspect of the present application;

FIG. 3 is a flow chart of a method for binding payment objects based on a 5G messaging application according to another embodiment of the first aspect of the present application;

FIG. 4 is a flow chart of a method for binding payment objects based on a 5G messaging application according to a further embodiment of the first aspect of the present application;

FIG. 5 is a flow chart of a method for binding payment objects based on a 5G messaging application according to yet another embodiment of the first aspect of the present application;

FIG. 6 is a flow chart of a method for binding payment objects based on a 5G messaging application according to an embodiment of the second aspect of the present application;

FIG. 7 is a flow chart of a payment object binding method based on a 5G messaging application according to another embodiment of the second aspect of the present application;

FIG. 8 is a flow chart of a payment object binding method based on a 5G messaging application provided in accordance with a further embodiment of the second aspect of the present application;

FIG. 9 is a flowchart of an example of a payment card binding process based on a 5G messaging application provided by an embodiment of the present application;

FIG. 10 is a flowchart of an example of a 5G messaging application based payment application account binding process provided by an embodiment of the present application;

fig. 11 is a schematic structural diagram of a terminal device according to an embodiment of a third aspect of the present application;

fig. 12 is a schematic structural diagram of a payment device based on a 5G message application according to an embodiment of the fourth aspect of the present application;

fig. 13 is a schematic structural diagram of a terminal device according to an embodiment of the fifth aspect of the present application;

fig. 14 is a schematic structural diagram of an electronic device according to an embodiment of the sixth aspect of the present application.

Detailed Description

Features and exemplary embodiments of various aspects of the present application will be described in detail below, and in order to make the objects, technical solutions and advantages of the present application more apparent, the present application will be described in further detail below with reference to the accompanying drawings and the detailed embodiments. It should be understood that the particular embodiments described herein are meant to be illustrative of the application only and not limiting. It will be apparent to one skilled in the art that the present application may be practiced without some of these specific details. The following description of the embodiments is merely intended to provide a better understanding of the application by showing examples of the application.

The fifth generation mobile communication technology (5th Generation Mobile Communication Technology,5G) message is a conventional short message upgrading technology, and can provide a message service with multimedia and interactive capabilities. A 5G message application is an application that implements 5G messages. With the development of payment technology, the application of electronic payment has become very popular. With popularization and application of 5G message applications, in order to meet the requirement of users for electronic payment by using the 5G message application, it is desirable to bind users in the 5G message application with payment objects, so as to realize payment based on the 5G message application.

The application provides a 5G message application-based payment object binding method, a device, a system and a medium, wherein a user terminal is provided with a 5G message application and a payment reference, and the binding of a user and a payment object in the 5G message application is realized through interaction among terminal equipment, a 5G message application background system, a 5G message payment platform and a payment system, so that the payment of the 5G message application is realized based on the binding of the user and the payment object in the 5G message application.

The embodiment of the application provides a payment object binding method, device, system and medium based on a 5G message application, which are applied to a payment object binding scene of the 5G message application and can relate to terminal equipment, a 5G message application background system, a 5G message payment platform, a payment system and the like. Fig. 1 is a schematic diagram of an application scenario of a payment object binding method based on a 5G message application according to an embodiment of the present application. As shown in fig. 1, terminal device 11 may communicatively interact with 5G message application background system 12, 5G message paymate 13, and payment system 14, respectively, 5G message application background system 12 may communicatively interact with 5G message paymate 13, and 5G message paymate 13 may communicatively interact with payment system 14.

The terminal device 11 has a 5G messaging application 111 and a payment application 112. The 5G application message 111 may provide a 5G message service (i.e., 5G messaging service), which is a message service that may support rich media formats and has the characteristics of standardization, multimedia, and light weight. The mapping relationship between the 5G message application 111 in the terminal device 11 and the subscriber identity module (Subscriber Identity Module, SIM) card in the terminal device may be specifically implemented as a correspondence relationship between the 5G message application 111 and a SIM card number, or as a correspondence relationship between the 5G message application 111 and a mobile phone number corresponding to the SIM card, which is not limited herein. The 5G message application 111 may have an in-application payment function. The 5G message application 111 may invoke the payment application 112 in the terminal device 11, binding with a payment application account of the payment application 112 or binding with a payment card under a payment application account of the payment application 112, but is not limited thereto. The payment application account can be an account which is opened by a user in the payment application, the payment application account can have a binding relation with the payment card, and resources can be transferred in or out of the payment application account. The 5G message application 111 of the terminal device 11 may communicatively interact with the 5G message application backend system 12 and the payment application 112 of the terminal device 11 may communicatively interact with the payment system 14. The terminal device 11 may specifically include a mobile phone, a tablet computer, an electronic computer, a smart wearable device, etc., which is not limited herein.

The 5G messaging application background system 12 is a background system of the 5G messaging application 111 and may include more than one electronic device. The electronic devices may include servers, gateways, routers, etc., and are not limited in this regard as to the type and number of electronic devices in the 5G messaging application background system 12. In some examples, the 5G messaging application background system 12 may provide messaging service functionality to a user of the terminal device 11 by way of a messaging conversation in the manner of a chat bot and/or human customer service. In the payment object binding process, the 5G message application may interact with the 5G message paymate 13 through the 5G message application backend system 12, or may access the 5G message paymate 13 through a link.

The 5G message payment platform 13 is a platform system for managing and processing payments initiated by 5G message applications, and may aggregate multiple payment application accounts and/or payment cards for managing users, providing a unified payment interface for 5G message applications. The 5G message payment platform 13 may include more than one electronic device, which may include servers, gateways, routers, etc., and is not limited in terms of the type and number of electronic devices in the 5G message payment platform 13. In the payment object binding process, the 5G message payment platform 13 may interact with the 5G message application in the terminal device 11 through the 5G message application backend system 12.

The payment system 14 is a system that manages the resources of the user's payment application account and/or the resources of the payment card, and can complete the resource transfer-out and resource transfer-in required for payment. The payment system 14 may include more than one electronic device, which may include servers, gateways, routers, etc., and is not limited in terms of the type and number of electronic devices in the payment system 14. In the payment object binding process, the payment system 14 may interact with the payment application 112 in the terminal device 11 to implement binding of the payment object.

The method, the device, the equipment, the system and the medium for binding the payment object based on the 5G message application are sequentially described below.

The first aspect of the present application provides a payment object binding method based on a 5G message application, where the payment object binding method based on a 5G message application may be applied to a terminal device, i.e. the payment object binding method based on a 5G message application may be executed by the terminal device. The terminal device has a 5G message application and a payment application, and specific contents of the 5G message application and the payment application may be referred to the related description in the above embodiments, which are not described herein. Fig. 2 is a flowchart of a payment object binding method based on a 5G message application according to an embodiment of the first aspect of the present application. As shown in fig. 2, the payment object binding method based on the 5G message application may include steps S201 to S204.

In step S201, a payment object binding request is sent by the 5G message application to the 5G message paymate through the 5G message application backend system in response to a first input by the user to the 5G message application.

The first input is used to trigger binding of the payment object. The first input may be a single click input, a long press input, a double click input, or other gesture input, etc., to a control in the 5G message application that initiates binding of the payment object, without limitation. In some examples, the interface of the 5G message application may include a payment object binding control, and the first input may be an input to the payment object binding control. In response to the first input, the 5G message application sends a payment object binding request to the 5G message application background system, which in turn sends a payment object binding request to the 5G message paymate. The payment object binding request is used for triggering the 5G message payment platform to feed back a binding triggering link.

In step S202, the binding trigger link fed back by the 5G message paymate through the 5G message application backend system is received by the 5G message application.

The 5G message payment platform responds to the payment object binding request and sends a binding trigger link to the 5G message application background system, and the 5G message application background system sends the binding trigger link to the terminal equipment so that the 5G message application can acquire the binding link.

In step S203, the 5G messaging application is triggered to invoke the payment application based on a second input by the user to the binding trigger link.

The second input is for causing the binding to trigger a linking action. The second input may be a single click input, a long press input, a double click input, or other gesture input to the binding trigger link, etc., without limitation.

In some examples, the binding trigger link may include information indicating that the payment application is triggered to be invoked and information to access the payment system, and in response to the second input, the information in the binding trigger link indicating that the payment application is triggered to be invoked may be operative to invoke the payment application.

In some examples, the binding trigger link may include information indicating access to the 5G message paymate and information indicating access to the payment system, and in response to the second input, the information in the binding trigger link indicating access to the 5G message paymate may be operative to access the 5G message paymate, determine a invoked payment application based on interactions of the 5G message application with the 5G message paymate, and thereby invoke the payment application to interact with the payment system.

In step S204, the user identification and the payment object identification are transmitted by the payment application to the payment system, so that the payment system binds the payment object indicated by the user identification and the payment object identification.

The user identification is used for characterizing the mobile phone number of the user, and the user of the 5G message application can be determined through the mobile phone number. The user identifier may include one or more of the SIM card number, the mobile phone number, the desensitized SIM card number, the desensitized mobile phone number, and the like, which are not limited herein.

The invoked payment application may transmit the user identification and payment object identification to the payment system through one or more interactions with the payment system. The payment system may bind the received user identification with the payment object indicated by the payment object identification. The payment object is an object that makes a resource deduction from what the user may use to pay, and in some examples, the payment object may include a payment card and/or a payment application account. The payment card may be a bank card, and the payment application account may be an account opened by the user at the payment application.

In the embodiment of the application, in response to the first input of the 5G message application in the terminal equipment by the user, the 5G message application and the 5G message payment platform interact through a 5G message application background system to acquire a binding trigger link fed back by the 5G message payment platform. Based on the second input to the binding trigger link, the 5G message application can be automatically triggered to invoke the payment application, which transmits the user identification and the payment object identification to the payment system. The payment system can bind the user identification with the payment object indicated by the payment object identification according to the received user identification and the payment object identification, so that the binding of the user and the payment object in the 5G message application is realized, the blank of the binding of the user and the payment object in the 5G message application is made up, and the subsequent realization of the payment based on the 5G message application is facilitated.

In some embodiments, the payment object includes a payment card, and the payment system may bind the user identification and the payment card. Fig. 3 is a flowchart of a payment object binding method based on a 5G message application according to another embodiment of the first aspect of the present application. Fig. 3 is different from fig. 2 in that step S204 in fig. 2 may be specifically subdivided into steps S2041 to S2044 in fig. 3.

In step S2041, a binding trigger link transmitted by the 5G message application is received by the payment application.

In the case of triggering the 5G message application to invoke the payment application, the 5G message application transmits a binding trigger link to the payment application. The binding trigger link may include information to access the payment system, such as an access address of the payment system, and the like. The payment application may access the payment system based on the information in the binding trigger link to access the payment system and send a payment card list request message to the payment system.

In step S2042, a payment card list request message is sent by the payment application to the payment system based on the binding trigger link.

The payment card list request message includes a payment application account of the user in the payment application. The payment application account of the user in the payment application is the account logged in by the user in the invoked payment application.

In some examples, the payment system may feed back the list of payment cards to the terminal device after the user authorizes use of the payment application account. Specifically, a payment system indicated by a binding trigger link may be accessed by a payment application; receiving, by the payment application, an authorization request message for the payment system; in response to the user's authorization input, authorization confirmation information corresponding to the authorization input is sent by the payment application to the payment system, the authorization confirmation information being used to authorize use of the payment application account. For example, the terminal device may display an authorization request interface, the authorization input of the user may be input to the authorization request interface, the authorization input may be a single click input, a long press input, a double click input, or other gesture input to a control having an authorization function in the authorization request interface, and the like, which is not limited herein. The authorization input may generate authorization confirmation information. And after receiving the authorization confirmation information, the payment system feeds back a payment card list to the payment application.

In step S2043, a payment card list fed back by the payment system is received by the payment application.

The payment system stores a payment application account of the payment application and a payment card identification bound to the payment application account. In the embodiment of the application, the fast binding flow can be carried out by using the payment card of the payment application, which is bound by the payment application account of the payment application. The payment system may feed back a payment card list to the payment application of the terminal device, the payment card list comprising payment card identifications bound to payment application accounts.

For example, a payment application account of the payment application is A1, and payment cards B1, B2 and B3 are bound to the payment application account, and for convenience of explanation, the payment card identifications of the payment cards B1, B2 and B3 are also denoted as B1, B2 and B3, respectively, and the payment system forms a payment card list according to the payment card identifications B1, B2 and B3 of the payment cards bound to the payment application account in response to the list request message, and transmits the payment card list to the terminal device so that the payment application can acquire the payment card list.

In step S2044, a first binding request message is sent by the payment application to the payment system in response to a first selection input by the user to the payment card list, to cause the payment system to bind the user identification and the payment card identification indicated by the first selection input.

The first selection input is operable to select a payment card identification of a payment card for payment in the payment card list and to trigger transmission of a first binding request message to the payment system. The first selection input may be a single click input, a long press input, a double click input, or other gesture input to a list of payment cards, etc., without limitation.

The first binding request message includes a user identifier and a payment card identifier indicated by a first selection input, where the payment card identifier corresponding to the first selection input is the payment card identifier of the selected payment card for payment. The number of the payment card identifiers corresponding to the first selection input is not limited herein, and the user may select to bind one payment card at a time or bind more than two payment cards at a time, which is not limited herein. And the payment system responds to the first binding request message and binds the payment card corresponding to the user identifier in the first binding request message and the payment card identifier indicated by the first selection input.

By calling the payment application, the binding of the 5G message application and the payment card under the payment application account of the payment application is realized, the operation of binding the payment card by the 5G message application can be simplified, the operation of binding the payment card by the 5G message application is simpler, and the efficiency of binding the payment card by the 5G message application is further improved.

In some embodiments, the payment object includes a payment application account, and the payment system may bind the user identification and the payment application account. The payment application account may be associated with a user's payment at the payment application

Fig. 4 is a flowchart of a payment object binding method based on a 5G message application according to a further embodiment of the first aspect of the present application. Fig. 4 is different from fig. 2 in that step S203 in fig. 2 may be specifically thinned into steps S2031 to S2033 in fig. 4, and step S204 in fig. 2 may be specifically thinned into steps S2045 to S2047 in fig. 4.

In step S2031, a 5G message paymate is accessed by a 5G message application requesting a list of payment applications in response to a second input.

The payment application list includes application identifications of payment applications supported by the 5G message paymate. The payment application supported by the 5G message payment platform is the payment application with the function accessed to the 5G message payment platform. The binding trigger link may include information indicating access to the 5G message paymate, and in response to the second input, the 5G message paymate accesses the 5G message paymate to request the payment application list in accordance with the information indicating access to the 5G message paymate.

In step S2032, a list of payment applications sent by the 5G message paymate is received by the 5G message application.

The 5G message payment platform sends a payment application list to the 5G message application in response to the access by the 5G message application.

In step S2033, in response to a second selection input by the user to the payment application list, the 5G messaging application is triggered to invoke the payment application indicated by the second selection input.

The second selection input may be used to select a payment application identification of the invoked payment application in the payment application list to invoke the second selection input to select the invoked payment application. The second selection input may be a single click input, a long press input, a double click input, or other gesture input to a list of payment applications, and the like, without limitation.

In some examples, the binding trigger link may include information to access the payment system, and the 5G message application may transmit the binding trigger link to the payment application selected by the second selection input to cause the payment application to interact with the payment system.

In step S2045, a second binding request message is sent by the payment application to the payment system.

The second binding request message includes a user identification and a payment application account identification of the user in the payment application. The payment application account identification in the second binding request message characterizes an account of the invoked payment application in which the user is logged in. The second binding request message is for requesting binding of the user identification and the second selection input to the payment application account of the selected payment application.

In step S2046, an authorization request message sent by the payment system is received by the payment application.

The payment system sends an authorization request message to the payment application, the authorization request message being for requesting a second selection in the second binding request message to enter authorization for use of the payment application account of the selected payment application.

In step S2047, an authorization confirmation message is sent by the payment application to the payment system in response to the user' S authorization input, to cause the payment system to bind the user identification and the payment application account indicated by the payment application account identification.

The authorization input may generate authorization confirmation information. For example, the terminal device may display an authorization request interface, the authorization input of the user may be input to the authorization request interface, the authorization input may be a single click input, a long press input, a double click input, or other gesture input to a control having an authorization function in the authorization request interface, and the like, which is not limited herein. The authorization confirmation information is used to authorize use of the payment application account. The payment system binds the user identification with the payment application account indicated by the payment application account identification in response to the authorization confirmation message. In some examples, resources may be stored in the payment application account, and after the user identification is bound to the payment application account indicated by the payment application account identification, in the case of making a payment based on the 5G message application, resources corresponding to the payment amount may be transferred from the payment application account bound to the user identification. In some examples, the payment application account is bound with a payment card, and after the user identification is bound with the payment application account indicated by the payment application account identification, in the case of making a payment based on the 5G message application, resources corresponding to the payment amount may be transferred from a default card in the payment card bound to the payment application account.

In some embodiments, after the payment system binds the user identification and the payment object indicated by the payment object identification, the payment system may also notify the payment application of the outcome of the 5G message application binding. Fig. 5 is a flowchart of a payment object binding method based on a 5G message application according to still another embodiment of the first aspect of the present application. Fig. 5 is different from fig. 2 in that the payment object binding method based on the 5G message application shown in fig. 5 further includes step S205 and step S206.

In step S205, a first binding result sent by the payment system is received by the payment application.

The first binding result characterizes successful binding of the user identifier and the payment object indicated by the payment object identifier.

In some examples, if the user identification fails to bind with the payment object indicated by the payment object identification, the payment system may generate a binding result indicative of the binding failure and send the binding result to the payment application of the terminal device, so that the payment application may obtain the binding result indicative of the binding failure.

In step S206, the second binding result sent by the 5G message paymate through the 5G message application background system is received by the 5G message application.

The second binding result characterizes successful binding of the user identifier and the payment object indicated by the payment object identifier. The payment system may send the second binding result to the 5G message payment platform, which in turn sends the second binding result to the 5G message application of the terminal device. After the 5G message application receives the second binding result, prompt information indicating successful binding of the payment object indicated by the user identifier and the payment object identifier can be sent out, so that the user can know the binding result in time.

In some examples, if the user identifier fails to bind with the payment object indicated by the payment object identifier, the payment system may generate a binding result that characterizes the binding failure, send the binding result that characterizes the binding failure to the 5G message payment platform, and then send the binding result that characterizes the binding failure to the 5G message application of the terminal device.

And under the condition that the payment object comprises a payment card, the first binding result represents that the user identification and the payment card corresponding to the payment card identification indicated by the first selection input are successfully bound, and the second binding result represents that the user identification and the payment card corresponding to the payment card identification indicated by the first selection input are successfully bound.

In the case that the payment object comprises a payment application account, the first binding result characterizes that the user identification is successfully bound with the payment application account indicated by the payment application account identification, and the second binding result characterizes that the user identification is successfully bound with the payment application account indicated by the payment application account identification.

The second aspect of the present application provides a 5G message application-based payment object binding method, which is applicable to a 5G message paymate, i.e., the 5G message application-based payment object binding method is executable by the 5G message paymate. Fig. 6 is a flowchart of a payment object binding method based on a 5G message application according to an embodiment of the second aspect of the present application. As shown in fig. 6, the payment object binding method based on the 5G message application may include step S301 and step S302.

In step S301, a payment object binding request sent by a 5G message application of the terminal device through a 5G message application background system is received.

The terminal device has a 5G messaging application and a payment application.

In step S302, a feedback binding trigger link is applied to the 5G message by the 5G message application background system.

The binding trigger link may enable the 5G message application to trigger the 5G message application to invoke the payment application to transmit the user identification and the payment object identification to the payment system based on the binding trigger link, the payment system binding the payment object indicated by the user identification and the payment object identification. The user identification is used to characterize the mobile phone number of the user.

The details of step S301 and step S302 may be referred to the description of the above embodiments, and will not be repeated here.

In some embodiments, the payment object comprises a payment card.

In some embodiments, the payment object includes a payment application account. Fig. 7 is a flowchart of a payment object binding method based on a 5G message application according to another embodiment of the second aspect of the present application. Fig. 7 is different from fig. 6 in that the payment object binding method based on the 5G message application shown in fig. 7 may further include steps S303 to S304.

In step S303, the 5G message application is accepted in response to user access to a second input of the binding trigger link.

In step S304, the payment application list is fed back to the 5G message application.

The payment application list includes application identifications of payment applications supported by the 5G message paymate.

The details of step S303 to step S304 can be referred to the related descriptions in the above embodiments, and are not repeated here.

Fig. 8 is a flowchart of a payment object binding method based on a 5G message application according to a further embodiment of the second aspect of the present application. Fig. 8 is different from fig. 6 in that the payment object binding method based on the 5G message application shown in fig. 8 may further include steps S305 to S307.

In step S305, the second binding result sent by the payment system and the binding relationship between the user identifier and the payment object indicated by the payment object identifier are received.

The second binding result characterizes successful binding of the user identifier and the payment object indicated by the payment object identifier.

In step S306, the binding relationship is stored.

In step S307, the second binding result is sent to the 5G message application by the 5G message application background system.

The details of step S305 to step S307 can be referred to the related descriptions in the above embodiments, and are not repeated here.

For easy understanding, the following description will take two scenarios of terminal device, 5G message application background system, 5G message payment platform, and payment card binding between payment systems, and payment application account binding as examples. Wherein the terminal device has a 5G messaging application and a payment application.

Fig. 9 is a flowchart of an example of a payment card binding procedure based on a 5G message application according to an embodiment of the present application. As shown in fig. 9, the payment card binding procedure of the 5G message-based application may include steps S401 to S416.

In step S401, in response to the first input, the 5G message application transmits a payment object binding request to the 5G message application background system.

In step S402, the 5G message application background system sends a payment object binding request to the 5G message payment platform.

In step S403, the 5G message payment platform feeds back the binding trigger link to the 5G message application backend system.

In step S404, the 5G message application background system feeds back the binding trigger link to the 5G message application.

In step S405, in response to the second input of the binding trigger link by the user, the 5G message application invokes the payment application and transmits the binding trigger link to the payment application.

In step S406, the payment application accesses the payment system based on the binding trigger link.

In step S407, the payment system transmits an authorization request message to the payment application.

In step S408, the payment application receives an authorization input of the user, and transmits a payment card list request message to the payment system.

In step S409, the payment system feeds back the payment card list to the payment application in response to the payment card list request message.

In step S410, the payment application sends a first binding request message to the payment system in response to a first selection input by the user to the payment card list.

In step S411, in response to the first binding request message, the payment system binds the payment card corresponding to the user identification and the payment card identification indicated by the first selection input.

In step S412, the payment system sends the first binding result to the payment application.

In step S413, the payment system sends the second binding result and the binding relationship between the user identifier and the payment card corresponding to the payment card identifier indicated by the first selection input to the 5G message payment platform.

In step S414, the 5G message payment platform stores the binding relationship.

In step S415, the 5G message payment platform sends the second binding result to the 5G message application background system.

In step S416, the 5G message application background system sends the second binding result to the 5G message application.

The specific content of the above steps S401 to S416 may be referred to the relevant content in the above embodiments, and will not be described herein.

Fig. 10 is a flowchart of an example of a payment application account binding procedure based on a 5G message application according to an embodiment of the present application. As shown in fig. 10, the payment card binding procedure of the 5G message-based application may include steps S501 to S516.

In step S501, in response to a first input, the 5G message application sends a payment object binding request to the 5G message application background system.

In step S502, the 5G message application background system sends a payment object binding request to the 5G message payment platform.

In step S503, the 5G message payment platform feeds back the binding trigger link to the 5G message application backend system.

In step S504, the 5G message application background system feeds back the binding trigger link to the 5G message application.

In step S505, in response to a second input by the user of the binding trigger link, the 5G message application accesses the 5G message paymate, requesting a list of payment applications.

In step S506, the 5G message payment platform feeds back the payment application list to the 5G message application.

In step S507, in response to a second selection input by the user to the payment application list, the 5G message application invokes the payment application indicated by the second selection input.

In step S508, the payment application sends a second binding request message to the payment system. The second binding request message includes a user identification and a payment application account identification of the user in the payment application.

In step S509, in response to the second binding request message, the payment system transmits an authorization request message to the payment application.

In step S510, the payment application sends an authorization confirmation message to the payment system in response to the user' S authorization input.

In response to the authorization confirmation message, the payment system binds the user identification and the payment application account indicated by the payment application account identification in step S511.

In step S512, the payment system sends the first binding result to the payment application.

In step S513, the payment system sends the second binding result and the binding relationship between the user identifier and the payment application account indicated by the payment application account identifier to the 5G message payment platform.

In step S514, the 5G message payment platform stores the binding relationship.

In step S515, the 5G message payment platform sends the second binding result to the 5G message application background system.

In step S516, the 5G message application background system sends a second binding result to the 5G message application.

The specific content of the steps S501 to S516 may be referred to the relevant content in the above embodiment, and will not be described herein.

It should be noted that, in the embodiment of the present application, the information, the data acquisition, the data storage, the data use, the data processing, etc. are all authorized by the user or the related institutions, which accords with the related regulations of the national laws and regulations.

A third aspect of the application provides a terminal device having a 5G messaging application and a payment application. Fig. 11 is a schematic structural diagram of a terminal device according to an embodiment of a third aspect of the present application. As shown in fig. 11, the terminal device 600 may include a transmitting module 601, a receiving module 602, and a processing module 603.

The sending module 601 may be configured to send, by the 5G message application call, a payment object binding request to the 5G message paymate through the 5G message application backend system in response to a first input by a user to the 5G message application.

The receiving module 602 may be configured to be invoked by a 5G message application to receive a binding trigger link fed back by the 5G message paymate through a 5G message application backend system.

The processing module 603 may be configured to trigger the 5G message application to invoke the payment application based on a second input by the user of the binding trigger link.

The sending module 601 may be further configured to be invoked by the payment application to transmit a user identifier and a payment object identifier to the payment system, so that the payment system binds the user identifier and the payment object indicated by the payment object identifier, where the user identifier is used to characterize the mobile phone number of the user.

In some embodiments, the payment object includes a payment card.

The receiving module 602 may be configured to be invoked by a payment application to receive a binding trigger link transmitted by a 5G messaging application.

The sending module 601 may be configured to be invoked by the payment application to send a payment card list request message to the payment system based on the binding triggering link, the payment card list request message including a payment application account of the user in the payment application.

The receiving module 602 may be configured to be invoked by a payment application to receive a payment card list fed back by the payment system, the payment card list including payment card identifications bound to payment application accounts.

The sending module 601 may be configured to, in response to a first selection input from a user to the payment card list, be invoked by the payment application to send a first binding request message to the payment system to cause the payment system to bind the user identification and the payment card identification indicated by the first selection input, the first binding request message including the user identification and the payment card identification indicated by the first selection input.

In some embodiments, the payment object includes a payment application account.

The sending module 601 may be configured to access the 5G message paymate by the 5G message application invocation in response to the second input, requesting a payment application list, the payment application list including application identifications of payment applications supported by the 5G message paymate.

The receiving module 602 may be configured to be invoked by a 5G message application to receive a list of payment applications sent by a 5G message paymate.

The processing module 603 may be configured to trigger the 5G message application to invoke the payment application indicated by the second selection input in response to a second selection input by the user to the payment application list.

In some embodiments, the payment object includes a payment application account.

The sending module 601 may be configured to be invoked by the payment application to send a second binding request message to the payment system, where the second binding request message includes a user identification and a payment application account identification of the user in the payment application.

The receiving module 602 may be configured to be invoked by a payment application to receive an authorization request message sent by a payment system.

The sending module 601 may be configured to be invoked by the payment application to send an authorization confirmation message to the payment system in response to an authorization input by the user to cause the payment system to bind the user identification and the payment application account indicated by the payment application account identification.

In some embodiments, the receiving module 602 may be further configured to be invoked by the payment application to receive a first binding result sent by the payment system, where the first binding result characterizes that the user identification binds successfully with the payment object indicated by the payment object identification.

The receiving module 602 may be further configured to be invoked by the 5G message application to receive a second binding result sent by the 5G message payment platform through the 5G message application background system, where the second binding result characterizes that the user identifier and the payment object indicated by the payment object identifier are successfully bound.

The fourth aspect of the present application provides a payment object binding apparatus based on a 5G message application, which is applicable to a 5G message payment platform. Fig. 12 is a schematic structural diagram of a payment object binding apparatus based on a 5G message application according to an embodiment of the fourth aspect of the present application. As shown in fig. 12, the payment object binding apparatus 700 based on the 5G message application may include a receiving module 701 and a transmitting module 702.

The receiving module 701 may be configured to receive a payment object binding request sent by a 5G message application of the terminal device through a 5G message application background system.

The terminal device has a 5G messaging application and a payment application.

The sending module 702 may be configured to feed back a binding trigger link to the 5G message application through the 5G message application background system, so that the 5G message application triggers the 5G message application to invoke the payment application to transmit the user identifier and the payment object identifier to the payment system based on the binding trigger link, and the payment system binds the payment object indicated by the user identifier and the payment object identifier.

The user identification is used to characterize the mobile phone number of the user.

In some embodiments, the payment object includes a payment card.

In some embodiments, the payment object includes a payment application account.

The receiving module 701 may also be configured to accept access by the 5G message application in response to a second input by the user to the binding trigger link.

The sending module 702 may also be configured to feed back a payment application list to the 5G message application, the payment application list including application identifications of payment applications supported by the 5G message paymate.

In some embodiments, the 5G message application-based payment object binding apparatus 700 may further include a storage module.

The receiving module 701 may be further configured to receive a second binding result sent by the payment system, and a binding relationship between the user identifier and the payment object indicated by the payment object identifier, where the second binding result indicates that the user identifier and the payment object indicated by the payment object identifier are successfully bound.

The storage module may be used to store the binding relationship.

The sending module 702 may be further configured to send the second binding result to the 5G message application through the 5G message application background system.

The fifth aspect of the present application also provides a terminal device. Fig. 13 is a schematic structural diagram of a terminal device according to an embodiment of the fifth aspect of the present application. As shown in fig. 13, the terminal device 800 includes a memory 801, a processor 802, and a computer program stored on the memory 801 and executable on the processor 802.

In one example, the processor 802 may include a Central Processing Unit (CPU), or an Application SPECIFIC INTEGRATED Circuit (ASIC), or may be configured as one or more integrated circuits that implement embodiments of the present application.

The Memory 801 may include Read-Only Memory (ROM), random-access Memory (Random Access Memory, RAM), magnetic disk storage media devices, optical storage media devices, flash Memory devices, electrical, optical, or other physical/tangible Memory storage devices. Thus, in general, the memory comprises one or more tangible (non-transitory) computer-readable storage media (e.g., memory devices) encoded with software comprising 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 payment object binding method applied based on 5G messages in embodiments in accordance with the first aspect of the application.

The processor 802 runs a computer program corresponding to the executable program code by reading the executable program code stored in the memory 801 for implementing the payment object binding method based on the 5G message application in the embodiment of the first aspect described above.

In one example, terminal device 800 can also include a communication interface 803 and a bus 804. As shown in fig. 13, the memory 801, the processor 802, and the communication interface 803 are connected to each other via a bus 804 and perform communication with each other.

Communication interface 803 is primarily used to implement communication between modules, devices, units, and/or apparatuses in an embodiment of the present application. Input devices and/or output devices may also be accessed through communication interface 803.

Bus 804 includes hardware, software, or both, coupling the components of terminal device 800 to one another. By way of example, and not limitation, bus 804 may include an accelerated graphics Port (ACCELERATED GRAPHICS Port, AGP) or other graphics Bus, an enhanced industry Standard architecture (Enhanced Industry Standard Architecture, EISA) Bus, a Front Side Bus (FSB), a HyperTransport (HT) interconnect, an industry Standard architecture (Industry Standard Architecture, ISA) Bus, an Infiniband interconnect, a Low Pin Count (LPC) Bus, a memory Bus, a micro channel architecture (Micro Channel Architecture, MCA) Bus, a peripheral component interconnect (PERIPHERAL COMPONENT INTERCONNECT, PCI) Bus, a PCI-Express (PCI-E) Bus, a serial advanced technology attachment (SERIAL ADVANCED Technology Attachment, SATA) Bus, a video electronics standards Association local (Video Electronics Standards Association Local Bus, VLB) Bus, or other suitable Bus, or a combination of two or more of the above. Bus 804 may include one or more buses, where appropriate. Although embodiments of the application have been described and illustrated with respect to a particular bus, the application contemplates any suitable bus or interconnect.

The sixth aspect of the present application also provides an electronic device, where the electronic device is used for a 5G message payment platform. Fig. 14 is a schematic structural diagram of an electronic device according to an embodiment of the sixth aspect of the present application. As shown in fig. 14, the electronic device 900 includes a memory 901, a processor 902, and a computer program stored on the memory 901 and executable on the processor 902.

In one example, the processor 902 may include a Central Processing Unit (CPU), or an Application SPECIFIC INTEGRATED Circuit (ASIC), or may be configured as one or more integrated circuits that implement embodiments of the present application.

Memory 901 may include Read-Only Memory (ROM), random-access Memory (Random Access Memory, RAM), magnetic disk storage media devices, optical storage media devices, flash Memory devices, electrical, optical, or other physical/tangible Memory storage devices. Thus, in general, the memory comprises one or more tangible (non-transitory) computer-readable storage media (e.g., memory devices) encoded with software comprising 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 payment object binding method applied based on 5G messages in embodiments in accordance with the second aspect of the application.

The processor 902 runs a computer program corresponding to the executable program code by reading the executable program code stored in the memory 901 for implementing the payment object binding method based on the 5G message application in the embodiment of the above second aspect.

In one example, the electronic device 900 may also include a communication interface 903 and a bus 904. As shown in fig. 14, the memory 901, the processor 902, and the communication interface 903 are connected to each other via a bus 904, and communicate with each other.

The communication interface 903 is mainly used to implement communication between each module, device, unit, and/or apparatus in the embodiment of the present application. Input devices and/or output devices may also be accessed through communication interface 903.

Bus 904 includes hardware, software, or both, coupling components of electronic device 900 to one another. By way of example, and not limitation, bus 904 may include an AGP or other graphics bus, an EISA bus, an FSB, an HT interconnect, an ISA bus, an InfiniBand interconnect, an LPC bus, a memory bus, an MCA bus, a PCI-E bus, a SATA bus, a VLB bus, or other suitable bus, or a combination of two or more of the foregoing. Bus 904 may include one or more buses, where appropriate. Although embodiments of the application have been described and illustrated with respect to a particular bus, the application contemplates any suitable bus or interconnect.

A seventh aspect of the present application provides a 5G message application based payment system, which may comprise the terminal device and the 5G message paymate in the above embodiments. The terminal device may perform the payment object binding method based on the 5G message application of the above first aspect. The 5G message payment platform may perform the payment object binding method based on the 5G message application of the above second aspect. The specific content of the terminal device, the 5G message payment platform, and the respective executed payment object binding method based on the 5G message application may be referred to the related description in the foregoing embodiments, and will not be described herein again.

In some embodiments, the payment system based on the 5G message application may further include the 5G message application background system and/or the payment system in the above embodiments, and details may be referred to in the above embodiments and will not be described herein.

An eighth aspect of the present application further provides a computer readable storage medium, where computer program instructions are stored, where the computer program instructions, when executed by a processor, may implement the payment object binding method based on a 5G message application in the embodiment of the first aspect or the payment object binding method based on a 5G message application in the embodiment of the second aspect, and achieve the same technical effects, and are not repeated herein. The computer readable storage medium may include a non-transitory computer readable storage medium, such as Read-Only Memory (ROM), random access Memory (Random Access Memory RAM), magnetic disk or optical disk, and the like, which are not limited herein.

The present application may also provide a computer program product, where the instructions in the computer program product, when executed by a processor of an electronic device and/or a terminal device, cause the electronic device and/or the terminal device to execute the payment object binding method based on a 5G message application in the embodiment of the first aspect or the payment object binding method based on a 5G message application in the embodiment of the second aspect, and achieve the same technical effects, so that repetition is avoided and no further description is given here.

It should be understood that, in the present specification, each embodiment is described in an incremental manner, and the same or similar parts between the embodiments are all referred to each other, and each embodiment is mainly described in a different point from other embodiments. For terminal device embodiments, apparatus embodiments, electronic device embodiments, system embodiments, computer-readable storage medium embodiments, computer program product embodiments, the relevant points may be found in the description of method embodiments. The application is not limited to the specific steps and structures described above and shown in the drawings. Those skilled in the art will appreciate that various alterations, modifications, and additions may be made, or the order of steps may be altered, after appreciating the spirit of the present application. Also, a detailed description of known method techniques is omitted here for the sake of brevity.

Aspects of the present application are described above with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems) and computer program products according to embodiments of the application. It will be understood that each block of the flowchart illustrations and/or block diagrams, and combinations of blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, enable the implementation of the functions/acts specified in the flowchart and/or block diagram block or blocks. Such a processor may be, but is not limited to being, a general purpose processor, a special purpose processor, an application specific processor, or a field programmable logic circuit. It will also be understood that each block of the block diagrams and/or flowchart illustration, and combinations of blocks in the block diagrams and/or flowchart illustration, can be implemented by special purpose hardware which performs the specified functions or acts, or combinations of special purpose hardware and computer instructions.

Those skilled in the art will appreciate that the above-described embodiments are exemplary and not limiting. The different technical features presented in the different embodiments may be combined to advantage. Other variations to the disclosed embodiments can be understood and effected by those skilled in the art in view of the drawings, the description, and the claims. In the claims, the term "comprising" does not exclude other means or steps; the word "a" does not exclude a plurality; the terms "first," "second," and the like, are used for designating a name and not for indicating any particular order. Any reference signs in the claims shall not be construed as limiting the scope. The functions of the various elements presented in the claims may be implemented by means of a single hardware or software module. The presence of certain features in different dependent claims does not imply that these features cannot be combined to advantage.

Claims

1. A payment object binding method based on a 5G message application, characterized in that it is applied to a terminal device having a 5G message application and a payment application, the method comprising:

Responsive to a first input by a user to the 5G message application, sending, by the 5G message application, a payment object binding request to the 5G message payment platform through the 5G message application background system;

receiving a binding trigger link fed back by the 5G message payment platform through the 5G message application background system by the 5G message application;

triggering the 5G message application to call the payment application based on a second input of the binding triggering link by a user;

transmitting, by the payment application, a user identification and a payment object identification to a payment system, so that the payment system binds the user identification and a payment object indicated by the payment object identification, where the user identification is used to characterize a mobile phone number of a user.

2. The method of claim 1, wherein the payment object comprises a payment card,

The transmitting, by the payment application, a user identification and a payment object identification to a payment system to enable the payment system to bind the user identification and a payment object indicated by the payment object identification, comprising:

receiving, by the payment application, the binding trigger link transmitted by the 5G message application;

Based on the binding trigger link, sending, by the payment application, a payment card list request message to the payment system, the payment card list request message including a payment application account of a user in the payment application;

receiving, by the payment application, a payment card list fed back by the payment system, the payment card list including a payment card identification bound to the payment application account;

And responding to the first selection input of the user to the payment card list, sending a first binding request message to the payment system by the payment application so as to enable the payment system to bind the user identification and the payment card identification indicated by the first selection input, wherein the first binding request message comprises the user identification and the payment card identification indicated by the first selection input.

3. The method of claim 1, wherein the payment object comprises a payment application account,

The triggering the 5G message application to invoke the payment application based on a second input of the binding trigger link by a user includes:

Responsive to the second input, accessing, by a 5G message application, the 5G message paymate, requesting a payment application list, the payment application list including application identifications of payment applications supported by the 5G message paymate;

receiving, by the 5G message application, the payment application list sent by the 5G message payment platform;

And responding to a second selection input of the user to the payment application list, triggering the 5G message application to call the payment application indicated by the second selection input.

4. A method according to claim 3, wherein the transmitting, by the payment application, the user identification and the payment object identification to the payment system to cause the payment system to bind the user identification and the payment object indicated by the payment object identification comprises:

Transmitting, by the payment application, a second binding request message to the payment system, the second binding request message including the user identification and a payment application account identification of the user in the payment application;

Receiving, by the payment application, an authorization request message sent by the payment system;

in response to an authorization input by a user, an authorization confirmation message is sent by the payment application to the payment system to cause the payment system to bind the user identification and the payment application account indicated by the payment application account identification.

5. The method of claim 1, further comprising, after the transmitting, by the payment application, a user identification and a payment object identification to a payment system to cause the payment system to bind the user identification and the payment object indicated by the payment object identification:

receiving a first binding result sent by the payment system by the payment application, wherein the first binding result represents that the user identification and the payment object indicated by the payment object identification are successfully bound;

and receiving a second binding result sent by the 5G message payment platform through the 5G message application background system by the 5G message application, wherein the second binding result characterizes successful binding of the user identifier and the payment object indicated by the payment object identifier.

6. A payment object binding method based on a 5G message application, characterized in that the method is applied to a 5G message paymate, the method comprising:

receiving a payment object binding request sent by a 5G message application of terminal equipment through a 5G message application background system, wherein the terminal equipment is provided with the 5G message application and a payment application;

And feeding back a binding triggering link to the 5G message application through the 5G message application background system, so that the 5G message application triggers the 5G message application to call a payment application to transmit a user identifier and a payment object identifier to a payment system based on the binding triggering link, the payment system binds the user identifier and the payment object indicated by the payment object identifier, and the user identifier is used for representing a mobile phone number of a user.

7. The method of claim 6, wherein the payment object comprises a payment card.

8. The method of claim 6, wherein the payment object comprises a payment application account,

After the feedback binding trigger link is applied to the 5G message through the 5G message application background system, the method further comprises the following steps:

Accepting access by the 5G message application in response to a second input by the user to the binding trigger link;

And feeding back a payment application list to the 5G message application, wherein the payment application list comprises application identifiers of payment applications supported by the 5G message payment platform.

9. The method of claim 6, further comprising, after said feedback binding trigger link is applied to said 5G message by said 5G message application background system:

Receiving a second binding result sent by the payment system and a binding relation between the user identifier and a payment object indicated by the payment object identifier, wherein the second binding result represents that the user identifier and the payment object indicated by the payment object identifier are successfully bound;

Storing the binding relation;

And sending the second binding result to the 5G message application through the 5G message application background system.

10. A terminal device having a 5G messaging application and a payment application, the terminal device comprising:

The sending module is used for responding to the first input of the user to the 5G message application, and is called by the 5G message application to send a payment object binding request to the 5G message payment platform through the 5G message application background system;

The receiving module is used for being called by the 5G message application to receive a binding trigger link fed back by the 5G message payment platform through the 5G message application background system;

The processing module is used for triggering the 5G message application to call the payment application based on the second input of the binding triggering link by the user;

The sending module is further used for being called by the payment application to transmit a user identifier and a payment object identifier to a payment system so that the payment system binds the user identifier and the payment object indicated by the payment object identifier, and the user identifier is used for representing the mobile phone number of the user.

11. A payment object binding apparatus based on a 5G message application, the apparatus being applied to a 5G message paymate, the apparatus comprising:

The terminal equipment comprises a receiving module and a payment object binding module, wherein the receiving module is used for receiving a payment object binding request sent by a 5G message application of the terminal equipment through a 5G message application background system, and the terminal equipment is provided with the 5G message application and the payment application;

and the sending module is used for feeding back a binding trigger link to the 5G message application through the 5G message application background system, so that the 5G message application is triggered to call a payment application to transmit a user identifier and a payment object identifier to a payment system based on the binding trigger link, the payment system binds the user identifier and the payment object indicated by the payment object identifier, and the user identifier is used for representing the mobile phone number of the user.

12. A terminal device, comprising: a processor and a memory storing computer program instructions;

the processor, when executing the computer program instructions, implements a 5G message application based payment object binding method as claimed in any one of claims 1 to 5.

13. An electronic device, comprising: a processor and a memory storing computer program instructions;

The processor, when executing the computer program instructions, implements a 5G message application based payment object binding method as claimed in any one of claims 6 to 9.

14. A 5G message application-based payment system, comprising:

terminal device for performing a payment object binding method based on a 5G message application according to any of claims 1 to 5;

A 5G message paymate for performing the payment object binding method based on a 5G message application as claimed in any one of claims 6 to 9.

15. A computer readable storage medium, having stored thereon computer program instructions which, when executed by a processor, implement a 5G message application based payment object binding method according to any of claims 1 to 9.