Payment processing method, apparatus, device, and computer-readable storage medium

Abstract

The application discloses a payment processing method, device, equipment and computer readable storage medium. The payment processing method comprises the following steps: in the case that it is determined that a user uses a target payment platform for a payment operation for the first time in a first application program, a second application program is started through a target payment control; the payment operation is performed by using the second application program; in the case that the payment operation is completed, to-be-bound payment account information is acquired and displayed through the target payment control; a first input of a user to at least one target payment account information in the to-be-bound payment account information is received; and in response to the first input, a binding request for the at least one target payment account information is sent to a platform server through the target payment control, and the binding request is used to instruct the platform server to perform a binding operation on user information and a payment account corresponding to the at least one target payment account information. According to the embodiment of the application, the payment process can be uninterrupted, and the payment experience of the user is improved.

Description

Technical Field

[0001] This application belongs to the field of payment technology, and in particular relates to a payment processing method, apparatus, device and computer-readable storage medium. Background Technology

[0002] With the increasing popularity of online payment methods, more and more applications are incorporating payment functions.

[0003] Typically, payment processing in applications follows a "link your card first, then pay" logic. That is, when a user uses a particular payment method within the application for the first time, they must first link their payment account to that method before the payment can be made. This can create interruptions in the payment process, negatively impacting the user's payment experience. Summary of the Invention

[0004] This application provides a payment processing method, apparatus, device, and computer-readable storage medium that enables a seamless payment process and enhances the user's payment experience.

[0005] In a first aspect, embodiments of this application provide a payment processing method applied to a terminal device, the method comprising:

[0006] If it is determined that the user is using the target payment platform for the first time in the first application, the second application is launched through the target payment control, which is the payment control set in the first application that corresponds to the target payment platform;

[0007] The payment operation is performed using the second application.

[0008] Upon completion of the payment operation, the payment account information to be bound is obtained and displayed through the target payment control. The payment account information to be bound is the payment account information queried by the platform server corresponding to the target payment platform based on the user information corresponding to the user.

[0009] Receive first input from the user regarding at least one target payment account among the payment account information to be bound;

[0010] In response to the first input, a binding request for the at least one target payment account information is sent to the platform server through the target payment control. The binding request is used to instruct the platform server to perform a binding operation on the user information and the payment account corresponding to the at least one target payment account information.

[0011] Secondly, embodiments of this application provide a payment processing method applied to a platform server, the method comprising:

[0012] Obtain user information corresponding to the user who completes the target payment operation. The target payment operation is when the user first uses the target payment platform to make a payment operation in the first application in the terminal device. The terminal device launches the second application through the target payment control and makes a payment operation using the second application. The target payment platform is the payment platform to which the platform server belongs. The target payment control is the payment control set in the first application that corresponds to the target payment platform.

[0013] Based on the user information, query the corresponding payment account information, which will be used as the payment account information to be bound.

[0014] Send the payment account information to be bound to the target payment control in the terminal device;

[0015] Receive a binding request from the terminal device via the target payment control for at least one target payment account among the payment account information to be bound;

[0016] In response to the binding request, a binding operation is performed on the payment account corresponding to the user information and the at least one target payment account information.

[0017] Thirdly, embodiments of this application provide a payment processing apparatus applied to a terminal device, the apparatus comprising:

[0018] The program initiation module is used to initiate the second application through the target payment control when it is determined that the user is using the target payment platform for the first time in the first application to perform a payment operation. The target payment control is the payment control set in the first application that corresponds to the target payment platform.

[0019] A payment operation module is used to perform the payment operation using the second application.

[0020] The first display module is used to obtain and display the payment account information to be bound through the target payment control when the payment operation is completed. The payment account information to be bound is the payment account information queried by the platform server corresponding to the target payment platform based on the user information corresponding to the user.

[0021] The first input module is used to receive the user's first input regarding at least one target payment account information among the payment account information to be bound;

[0022] The first request module is configured to respond to the first input by sending a binding request for the at least one target payment account information to the platform server through the target payment control. The binding request is used to instruct the platform server to perform a binding operation on the user information and the payment account corresponding to the at least one target payment account information.

[0023] Fourthly, embodiments of this application provide a payment processing apparatus applied to a platform server, the apparatus comprising:

[0024] The information acquisition module is used to acquire user information corresponding to the user who has completed the target payment operation. The target payment operation is when the user uses the target payment platform for the first time in the first application in the terminal device to perform a payment operation. The terminal device launches the second application through the target payment control and performs the payment operation using the second application. The target payment platform is the payment platform to which the platform server belongs. The target payment control is the payment control set in the first application that corresponds to the target payment platform.

[0025] The information query module is used to query the corresponding payment account information based on the user information, which will be used as the payment account information to be bound.

[0026] The information sending module is used to send the payment account information to be bound to the target payment control in the terminal device;

[0027] The request receiving module is used to receive a binding request sent by the terminal device through the target payment control for at least one target payment account among the payment account information to be bound.

[0028] The binding operation module is used to perform a binding operation on the user information and the payment account corresponding to the at least one target payment account information in response to the binding request.

[0029] Fifthly, embodiments of this application provide an electronic device, which includes: a processor and a memory storing computer program instructions;

[0030] When the processor executes the computer program instructions, it implements the steps of the payment processing method as described in any embodiment of the first or second aspect.

[0031] In a sixth aspect, embodiments of this application provide a computer-readable storage medium storing computer program instructions that, when executed by a processor, implement the steps of the payment processing method as described in any of the embodiments of the first or second aspect.

[0032] In a seventh aspect, embodiments of this application provide a computer program product in which instructions, when executed by a processor of an electronic device, cause the electronic device to perform the steps of the payment processing method as described in any embodiment of the first or second aspect.

[0033] The payment processing method, apparatus, device, and computer-readable storage medium in this application embodiment, upon determining that a user is performing a payment operation on a target payment platform for the first time in a first application, invokes a second application using a target payment control corresponding to the target payment platform set in the first application, and completes the payment operation using the second application. After the payment operation is completed, the user is then guided to bind their payment account. Thus, because this application embodiment processes payment by paying first and then binding the payment account, the payment process is uninterrupted, improving the user's payment experience. Attached Figure Description

[0034] To more clearly illustrate the technical solutions of the embodiments of this application, the accompanying drawings used in the embodiments of this application will be briefly introduced below. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0035] Figure 1 This is an architecture diagram applicable to the payment processing method provided in this application;

[0036] Figure 2 This is a schematic flowchart of the payment processing method provided in the first aspect of this application;

[0037] Figure 3 This is a schematic flowchart of the payment processing method provided in the second aspect embodiment of this application;

[0038] Figure 4 This is a flowchart illustrating the payment processing method for the first payment provided in this application;

[0039] Figure 5 This is a flowchart illustrating the payment processing method for non-first-time payments provided in this application.

[0040] Figure 6 This is a schematic diagram of the structure of the payment processing device provided in the first aspect embodiment of this application;

[0041] Figure 7 This is a schematic diagram of the structure of the payment processing device provided in the first aspect embodiment of this application;

[0042] Figure 8 This is a schematic diagram of the structure of an electronic device provided in one embodiment of this application. Detailed Implementation

[0043] The features and exemplary embodiments of various aspects of this application will be described in detail below. To make the objectives, technical solutions, and advantages of this application clearer, the application will be further described in detail below with reference to the accompanying drawings and specific embodiments. It should be understood that the specific embodiments described herein are only intended to explain this application and not to limit it. For those skilled in the art, this application can be implemented without some of these specific details. The following description of the embodiments is merely to provide a better understanding of this application by illustrating examples.

[0044] It should be noted that, in this document, relational terms such as "first" and "second" are used merely to distinguish one entity or operation from another, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Furthermore, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitations, an element defined by the phrase "comprising..." does not exclude the presence of additional identical elements in the process, method, article, or apparatus that includes said element.

[0045] To address the problems of the prior art, embodiments of this application provide a payment processing method, apparatus, device, and computer-readable storage medium. This payment processing method can be applied to online payment scenarios. The architecture applicable to the payment processing method in this application embodiment is described below.

[0046] Figure 1 This is an architecture diagram applicable to the payment processing method provided in this application.

[0047] like Figure 1 As shown, the architecture includes a terminal device 11, a platform server 12, and an institution server 13. The terminal device 11 has a merchant application 111 installed, which can include a target payment control 101 corresponding to the target payment platform. The terminal device 11 can also have a financial institution application 112 installed, corresponding to the target financial institution. Furthermore, the terminal device 11 can also have a payment platform application 113 installed, corresponding to the target payment platform.

[0048] Additionally, terminal device 11 can be a smart terminal device capable of installing applications, such as a mobile phone, computer, or tablet; platform server 12 can be a server used by the target payment platform; and institutional server 13 can be a server used by the target financial institution. Here, the server can be a distributed server or a centralized server; no limitation is made.

[0049] Terminal device 11 and platform server 12 can communicate through merchant application 111 or the target payment control 101 set therein; terminal device 11 and institution server 13 can communicate through financial institution application 112; and platform server 12 and institution server 13 can communicate through a network.

[0050] Based on the above architecture, the payment processing method provided in the embodiments of this application will be described below.

[0051] Figure 2 This is a schematic flowchart of a payment processing method provided in one embodiment of this application. The payment processing method can be performed by, for example... Figure 1 The terminal device 11 shown executes this.

[0052] like Figure 2 As shown, the payment processing method may specifically include the following steps:

[0053] S210. If it is determined that the user is using the target payment platform for the first time in the first application, the second application is launched through the target payment control, which is the payment control set in the first application that corresponds to the target payment platform.

[0054] S220. Perform payment operations using a second application;

[0055] S230. Upon completion of the payment operation, obtain and display the payment account information to be bound through the target payment control. The payment account information to be bound is the payment account information queried by the platform server corresponding to the target payment platform based on the user information corresponding to the user.

[0056] S240: Receive first input from the user regarding at least one target payment account information among the payment account information to be bound;

[0057] S250. In response to the first input, a binding request for at least one target payment account information is sent to the platform server through the target payment control. The binding request is used to instruct the platform server to bind the user information and the payment account corresponding to at least one target payment account information.

[0058] Therefore, by determining that the user is making a payment using the target payment platform for the first time in the first application, the second application is launched using the target payment control corresponding to the target payment platform set in the first application. The second application is then used to complete the payment operation. After the payment operation is completed, the user is then guided to bind their payment account. Thus, because this embodiment of the application processes payment by paying first and then binding the payment account, the payment process is seamless, improving the user's payment experience.

[0059] The specific implementation methods for each of the above steps are described below.

[0060] In some implementations, in S210, the first application may be as follows: Figure 1 The merchant application 111 shown corresponds to the merchant. This first application may include a payment control for the target payment platform, i.e., a target payment control, which can be used to assist the first application in implementing the payment services provided by the target payment platform.

[0061] The second application can be any application with payment functionality already installed on the terminal device, other than the first application, such as... Figure 1 The financial institution application 112 or payment platform application 113 shown.

[0062] For example, when a user selects to use a target payment platform for payment in a first application installed on a terminal device, the target payment control in the first application can send a query request to the platform server corresponding to the target payment platform to instruct the platform server to check whether this is the user's first payment on the target payment platform, that is, whether the payment service has been activated on the target payment platform. If the query result returned by the platform server is "not yet activated," then it can be determined that this payment operation is the first payment operation, that is, it can be determined that this payment operation is the user's first payment using the target payment platform in the first application.

[0063] Based on this, the target payment control in the first application can be invoked, and the second application installed on the terminal device that has a cooperative relationship with the target payment platform can be invoked through the target payment control, so as to complete the payment operation using the second application, and then execute the payment account binding process after the payment operation is completed, thereby ensuring that the payment operation process is uninterrupted.

[0064] Additionally, if the query result returned by the platform server is "activated", it can be determined that this payment operation is not the first payment operation, that is, it can be determined that this payment operation is the user's first payment operation using the target payment platform in the first application.

[0065] Based on this, in some implementations, the payment processing method provided in this application further includes:

[0066] If it is determined that the user is not using the target payment platform for payment operations for the first time in the first application, an information query request is sent to the platform server through the target payment control. The information query request is used to instruct the platform server to query the payment account information corresponding to the payment account bound to the user information, and obtain the bound payment account information.

[0067] The target payment control receives and displays the bound payment account information sent by the platform server.

[0068] Receives a fourth input from the user regarding the third payment account information in the linked payment account information;

[0069] In response to the fourth input, a payment request for the third payment account information is sent to the platform server through the target payment control. The payment request is used to instruct the platform server to perform a payment operation based on the payment account corresponding to the third payment account information.

[0070] Here, the fourth input can be the input where the user clicks to select the third payment account information from the already bound payment account information and confirms the payment.

[0071] For example, if it is determined that this payment operation is not the user's first payment using the target payment platform in the first application, the target payment control in the first application can be invoked. The target payment control then queries the platform server for the payment account information corresponding to the user's previously bound payment account. The bound payment account information retrieved by the platform server is displayed in the target payment control. After the user selects the payment account information corresponding to the payment account used for this payment operation (i.e., the third payment account information) and enters the platform payment password, the terminal device can again initiate a payment request to the platform server through the target payment control, instructing the platform server to complete the payment operation using the payment account corresponding to the third payment account information.

[0072] In some implementations, in S220, after the second application is launched, the user can be redirected to the payment page corresponding to the second application to perform the payment operation.

[0073] For example, a user can enter the payment password set in the second application on the payment page of the second application. The second application then sends a payment request to the corresponding server, instructing the server to complete the payment operation using the payment account bound to the user in the second application after the payment password is verified.

[0074] In some implementations, in S230, the payment account information to be bound can be payment account information retrieved by the platform server corresponding to the target payment platform based on the user information corresponding to the user. This payment account information can be, for example, information that uniquely identifies the payment account, such as a payment account number. The user information corresponding to the user can be sent to the platform server by the server corresponding to the second application after the payment operation is completed and authorized by the user. This user information can be, for example, information that identifies the user, such as the user's name and ID number.

[0075] In addition, the platform server can use the user information to find the payment accounts that the user has applied for or linked with one or more financial institutions or payment platforms, and then send the account information of these payment accounts as payment account information to be linked to the terminal device. Based on this, the terminal device can receive the payment account information to be linked returned by the platform server through the target payment control and display it on the payment interface of the target payment control.

[0076] In some implementations, in S240, the first input can be the user clicking to select a target payment account from the payment account information to be bound and confirming the binding, or the user selecting multiple target payment accounts from the payment account information to be bound and confirming the binding.

[0077] For example, a user can select one or more target payment accounts to be bound from the payment account information to be bound, and click to confirm the binding, thereby triggering the binding operation process for the one or more payment accounts represented by the one or more target payment account information.

[0078] In some implementations, in S250, after receiving the user's first input, the terminal device can send a binding request for the at least one target payment account information to the platform server through the target payment control. The binding request may carry the at least one target payment account information to instruct the platform server to complete the binding of the user with the payment account corresponding to the at least one target payment account information.

[0079] For example, after receiving a binding request from a terminal device, the platform server can obtain at least one target payment account information selected by the user from the binding request, and then bind the user's user information with the at least one target payment account information, so that when the user uses the payment service provided by the target payment platform next time, the user can query the payment account information corresponding to the payment account bound to the user, and then use the bound payment account to complete the payment operation.

[0080] In addition, after the binding operation is completed, the platform server can also prompt the user to set the payment password of the target payment platform through the target payment control in the terminal device. After the user completes the setting, the entire process can be ended.

[0081] Furthermore, the target payment platform can be a payment platform that cooperates with multiple financial institutions. Therefore, to fully leverage the advantage of the target payment platform's cooperation with multiple financial institutions, in some embodiments, before invoking the second application through the target payment control in S210 above, the payment processing method provided in this application embodiment may further include:

[0082] To query the financial institution applications that are installed on the terminal device and correspond to the financial institution;

[0083] If a financial institution application exists, display the application information corresponding to that financial institution application;

[0084] Receive a second input from the user regarding the target application information corresponding to the target financial institution within the application information;

[0085] In response to the second input, the financial institution application corresponding to the target financial institution is identified as the second application based on the target application information.

[0086] Here, the financial institution could be, for example, a bank. The second input could be the user selecting and confirming a target payment account from the application information. Additionally, the application information could include, for example, the application name, icon, or other identifying information.

[0087] For example, if it is determined that this payment operation is the first payment operation, the target payment control can poll the financial institution applications installed on the terminal device, such as bank APPs, and display the application information corresponding to the financial institution applications that can be selected for payment to the user. When the user selects the application information corresponding to the application of financial institution A, the application corresponding to financial institution A can be used as the second application, and then the second application can be invoked to complete the payment operation.

[0088] Furthermore, to reduce payment failures due to the absence of a financial institution application installed on the terminal device, embodiments of this application can also use the payment platform application corresponding to the target payment platform as a fallback to complete the payment operation. Based on this, in some embodiments, after querying the financial institution application corresponding to the financial institution already installed on the terminal device, the payment processing method provided in this application embodiment may further include:

[0089] In the absence of a financial institution application, query the payment platform application that is installed on the terminal device and corresponds to the payment platform.

[0090] If a payment platform application corresponding to the target payment platform exists, the payment platform application corresponding to the target payment platform shall be identified as the second application.

[0091] For example, if no financial institution application is installed on the terminal device, it can be queried whether a payment platform application corresponding to the target payment platform is installed on the terminal device. If it is determined that a payment platform application corresponding to the target payment platform exists on the terminal device, the payment platform application corresponding to the target payment platform is used as a second application, and then the second application is invoked to complete the payment operation.

[0092] It should be noted that when polling the terminal device to see if the financial institution's corresponding application is installed, the target payment control can also simultaneously query whether the target payment platform's corresponding payment platform application is installed. In the event that the financial institution's application is not installed, the payment operation can be performed directly using the payment platform application corresponding to the target payment platform.

[0093] In addition, to ensure users' right to know and information security, authorization prompts can be displayed to users, and user information can only be provided and synchronized to the platform server upon user authorization. Based on this, in some embodiments, before obtaining and displaying the payment account information to be bound through the target payment control in S230 above, the payment processing method provided in this application embodiment may further include:

[0094] The second application receives authorization prompts from the server of the target financial institution.

[0095] Display authorization prompts in the second application;

[0096] Receive third-party input from the user based on authorization prompts;

[0097] In response to the third input, an authorization instruction is sent to the agency server through the second application. The authorization instruction is used to instruct the agency server to send the user information to the platform server.

[0098] Here, the authorization prompt information may include information such as the payment service activation agreement of the target payment platform. Additionally, in some implementations, the authorization prompt information may also include user information, such as the user's name, ID number, or all or part of that information. In this way, the user can understand, through the authorization prompt information displayed in the second application and the user information contained therein, that the target financial institution will send the user information to the target payment platform after the user's authorization, thereby further ensuring the user's right to know.

[0099] Alternatively, the third input can be the input from when the user clicks to confirm authorization.

[0100] For example, after the payment operation is completed, the institution server can send the user information corresponding to the payment account used for this payment, as well as the payment service activation agreement and other information, as authorization prompt information to the second application on the terminal device. The terminal device receives and displays the authorization prompt information through the second application, prompting the user to authorize the activation of payment services on the target payment platform. When the user clicks to confirm authorization, the second application can send an authorization instruction to the institution server, which in turn instructs the institution server to send user information such as the user's name and ID number to the platform server. This allows the platform server to query the payment account information under the user's name based on the user information during the subsequent payment account binding process and generate the payment account information to be bound.

[0101] In addition, when a financial institution application exists in the terminal device, in some implementations, the payment account information to be bound that is subsequently queried by the platform server may include first payment account information, which may be the payment account information corresponding to the payment account bound to the user information in the financial institution application of the corresponding financial institution.

[0102] In addition, in some embodiments where a payment platform application corresponding to the target payment platform exists in the terminal device, the payment account information to be bound may also include second payment account information, which may be the payment account information corresponding to the payment account bound to the user information in the payment platform application corresponding to the target payment platform.

[0103] For example, the platform server can query the list of financial institution applications installed on the terminal device and the list of financial institutions supporting the target payment platform, and then determine whether there are any financial institution applications installed on the terminal device that support one or more financial institutions of the target payment platform. If there are financial institution applications that support one or more financial institutions, the platform server can query the payment account information of the payment account bound by the user in the financial institution applications that support one or more financial institutions through the one-click account binding interface, and send it to the terminal device as the payment account information to be bound, so that the user can choose to bind. If there are no financial institution applications that support one or more financial institutions, but the terminal device has a payment platform application that supports the target payment platform, or if the terminal device has both financial institution applications that support one or more financial institutions and a payment platform application that supports the target payment platform, the platform server can also query the payment account information of the payment account that the user has bound in the payment platform application that supports the target payment platform, and send it to the terminal device as the payment account information to be bound, so that the user can choose to bind.

[0104] Figure 3 This is a schematic flowchart of a payment processing method provided in one embodiment of this application. The payment processing method can be performed by, for example... Figure 1 The platform server 12 shown is executed.

[0105] like Figure 3 As shown, the payment processing method may specifically include the following steps S310 to S350, as detailed below.

[0106] S310. Obtain the user information corresponding to the user who completed the target payment operation.

[0107] Here, the target payment operation can be when a user first uses the target payment platform to make a payment operation in the first application within the terminal device, the terminal device calls up the second application through the target payment control, and the payment operation is performed by the second application. The target payment platform is the payment platform to which the platform server belongs, and the target payment control is the payment control set in the first application that corresponds to the target payment platform.

[0108] In addition, the platform server obtains user information in ways including but not limited to receiving it from the server corresponding to the second application.

[0109] For example, if the second application is a financial institution application, the user information may be the user information corresponding to the payment account used to complete the payment, which is sent by the corresponding institution's server to the platform server after the user's first payment operation on the target payment platform is completed.

[0110] For example, if the second application is a payment platform application, the user information can be obtained from the local data table corresponding to the payment platform application. This user information is the user information corresponding to the payment account used to complete the target payment operation.

[0111] Based on this, in some implementations, when the second application is a financial institution application corresponding to the target financial institution, S310 may specifically include:

[0112] Receive user information sent by the institutional server corresponding to the target financial institution. The user information is sent by the institutional server upon receiving an authorization instruction sent by the terminal device through the second application.

[0113] Here, explanations related to this implementation method can be found in the relevant parts of the above embodiments, and will not be repeated here.

[0114] S320. Query the corresponding payment account information based on the user information, and use it as the payment account information to be bound.

[0115] In some implementations, if a financial institution application corresponding to a financial institution exists in the terminal device, the above-mentioned S320 may specifically include:

[0116] Based on the user information, query the payment account information corresponding to the payment account bound in the financial institution's application to obtain the first payment account information; the payment account information to be bound includes the first payment account information.

[0117] In some implementations, if a payment platform application corresponding to the target payment platform exists in the terminal device, the above-mentioned S320 may specifically include:

[0118] The second payment account information is obtained by querying the payment account information corresponding to the payment account bound in the payment platform application based on the user information; the payment account information to be bound includes the second payment account information.

[0119] Here, explanations related to the above implementation methods can be found in the relevant parts of the above embodiments, and will not be repeated here.

[0120] S330: Send the payment account information to be bound to the target payment control in the terminal device.

[0121] S340: Receive a binding request from the terminal device via the target payment control for at least one target payment account among the payment account information to be bound.

[0122] S350. In response to the binding request, perform a binding operation on the user information and the payment account corresponding to at least one target payment account information.

[0123] Here, the explanations related to S330 to S350 can be found in the relevant parts of the above embodiments, and will not be repeated here.

[0124] Therefore, when a user first uses the target payment platform in the first application to make a payment, the terminal device launches the second application via a target payment control corresponding to the target payment platform set in the first application. The user then completes the payment using the second application. After the payment is completed, the platform server obtains the user information corresponding to the user who completed the target payment, retrieves the corresponding payment account information to be bound based on this user information, and guides the user to select at least one target payment account on the terminal device. The platform server then binds the user information and the payment account corresponding to at least one target payment account. Thus, because this embodiment processes payment by paying first and then binding the payment account, the payment process is seamless, improving the user's payment experience.

[0125] In addition, in some embodiments, the payment processing method provided in this application may further include:

[0126] Receive information query requests sent by the terminal device through the target payment control. The information query requests are sent by the user when making a payment operation using the target payment platform in the first application within the terminal device, and not for the first time.

[0127] In response to an information query request, query the payment account information corresponding to the payment account bound to the user information, and obtain the bound payment account information;

[0128] Send the linked payment account information to the terminal device;

[0129] The receiving terminal device sends a payment request for a third payment account in the bound payment account information through the target payment control;

[0130] In response to a payment request, a payment operation is performed based on the payment account corresponding to the third-party payment account information.

[0131] Here, explanations related to the above implementation methods can be found in the relevant parts of the above embodiments, and will not be repeated here.

[0132] To better describe the overall solution, some specific examples are given based on the above embodiments.

[0133] For example, such as Figure 4The flowchart shown is for the payment processing method of the first payment. This payment processing method may include S401-S415, which are explained in detail below.

[0134] S401. The merchant's app sends a query request to the platform server to check whether the platform's payment service has been activated, and uploads the list of app installations.

[0135] In some specific examples, when a user makes a payment using a target payment platform in a merchant app on their mobile phone, the merchant app can send a query request to the platform server corresponding to the target payment platform to check whether the platform's payment service has been activated, and upload a list of mobile app installations.

[0136] S402. The platform server returns a "Not yet activated" query result to the merchant's APP.

[0137] S403, Merchant APP invokes target payment control.

[0138] In some specific examples, the target payment control is the payment control corresponding to the target payment platform.

[0139] S404. The target payment control displays the financial institution's APP that can be invoked on the terminal device and receives the user's selection input.

[0140] S405, The target payment control invokes the financial institution's APP selected by the user.

[0141] S406. The financial institution's APP sends the institutional payment password entered by the user to the corresponding institutional server.

[0142] S407. After the institution's server completes the payment, it sends an authorization prompt message to the financial institution's APP.

[0143] In some specific examples, the authorization message includes user information and a payment service activation agreement.

[0144] S408. Financial institution apps display authorization prompts and receive user authorization input.

[0145] S409. The financial institution's APP sends an authorization instruction to the institution's server.

[0146] S410, The organization server synchronizes the user's information with the platform server.

[0147] S411. The platform server queries the list of apps corresponding to financial institutions that have been installed on the terminal device and support the target payment platform, and queries the payment account information of the financial institution that is bound to the user information.

[0148] S412, The platform server returns the queried payment account information to the target payment control.

[0149] S413. The target payment control receives the user's selection input and returns the target payment account information selected by the user to the platform server to complete the binding.

[0150] S414. The platform server prompts the user to set a platform payment password.

[0151] S415. The target payment control sends the platform payment password set by the user to complete the password setting.

[0152] Therefore, by updating the "bind card first, pay later" process for the first payment, and using the financial institution's APP to complete the payment first, and then bind the payment account, the smoothness of the payment process can be improved, making the payment process uninterrupted, thereby enhancing the user's payment experience.

[0153] In addition, by only synchronizing a user's information to the platform server with the user's authorization, the user's right to know can be guaranteed and the information security of the user's personal information can be improved.

[0154] Furthermore, user information is obtained through the initial payment, and the payment account information bound to the user in the financial institution APP installed on the terminal device is queried based on the user information. Based on this payment account information, the user is bound to the corresponding payment account on the target payment platform. Moreover, this application embodiment supports individual binding and batch binding, so it can realize one payment and multiple card binding, thereby further improving the user's payment experience.

[0155] Based on this, the payment processing procedure for non-first-time payments can be as follows: Figure 5 As shown. This payment processing method may include S501-S506, which will be explained in detail below.

[0156] S501, The merchant's APP sends a query request to the platform server to check whether the platform's payment service has been activated.

[0157] S502, The platform server returns the "activated" query result to the merchant's APP.

[0158] S503, Merchant APP invokes target payment control.

[0159] S504. The target payment control queries the platform server for information on the bound payment accounts.

[0160] S505, The platform server returns the information of the bound payment account.

[0161] S506. The target payment control sends the payment account information selected by the user to the platform server and enters the platform payment password to complete the payment.

[0162] It should be noted that the application scenarios described in the above embodiments of this application are for the purpose of more clearly illustrating the technical solutions of the embodiments of this application, and do not constitute a limitation on the technical solutions provided by the embodiments of this application. As those skilled in the art will know, with the emergence of new application scenarios, the technical solutions provided by the embodiments of this application are also applicable to similar technical problems.

[0163] Based on the same inventive concept, this application also provides a payment processing device. The following details its application. Figure 6 and Figure 7 Please provide a detailed explanation.

[0164] Figure 6 This is a schematic diagram of the structure of a payment processing device provided in one embodiment of this application. The payment processing device can be configured in, for example... Figure 1 In the terminal device 11 shown.

[0165] like Figure 6 As shown, the payment processing device 600 may include:

[0166] The program initiation module 601 is used to initiate the second application through the target payment control when it is determined that the user is using the target payment platform for the first time in the first application to perform a payment operation. The target payment control is the payment control set in the first application that corresponds to the target payment platform.

[0167] Payment operation module 602 is used to perform the payment operation using the second application;

[0168] The first display module 603 is used to obtain and display the payment account information to be bound through the target payment control when the payment operation is completed. The payment account information to be bound is the payment account information queried by the platform server corresponding to the target payment platform based on the user information corresponding to the user.

[0169] The first input module 604 is used to receive the user's first input regarding at least one target payment account information among the payment account information to be bound;

[0170] The first request module 605 is used to respond to the first input by sending a binding request for the at least one target payment account information to the platform server through the target payment control. The binding request is used to instruct the platform server to perform a binding operation on the user information and the payment account corresponding to the at least one target payment account information.

[0171] The payment processing device 600 described above will be explained in detail below:

[0172] In some embodiments, the payment processing device 600 further includes:

[0173] The first query module is used to query the financial institution application corresponding to the financial institution that is already installed on the terminal device before the second application is invoked through the target payment control.

[0174] The second display module is used to display application information corresponding to the financial institution application when the financial institution application exists.

[0175] The second input module is used to receive a second input from the user regarding the target application information corresponding to the target financial institution in the application information;

[0176] The first determining module is configured to, in response to the second input, determine the financial institution application corresponding to the target financial institution as the second application based on the target application information.

[0177] In some embodiments, the payment processing device 600 further includes:

[0178] The second query module is used to query the application corresponding to the financial institution that is already installed on the terminal device, and if the application corresponding to the financial institution does not exist, to query the payment platform application that is already installed on the terminal device.

[0179] The second determining module is used to determine the payment platform application corresponding to the target payment platform as the second application if a payment platform application corresponding to the target payment platform exists.

[0180] In some embodiments, the payment processing device 600 further includes:

[0181] The first receiving module is used to receive authorization prompt information sent by the institutional server corresponding to the target financial institution through the second application before obtaining and displaying the payment account information to be bound through the target payment control;

[0182] The third display module is used to display the authorization prompt information in the second application;

[0183] The third input module is used to receive third input from the user based on the authorization prompt information.

[0184] The first sending module is configured to, in response to the third input, send an authorization instruction to the institution server via the second application, wherein the authorization instruction instructs the institution server to send the user information to the platform server.

[0185] In some embodiments, the authorization prompt information includes the user information.

[0186] In some embodiments, the payment account information to be bound includes first payment account information, which is the payment account information corresponding to the payment account bound to the user information in the financial institution application corresponding to the financial institution.

[0187] In some embodiments, the payment account information to be bound includes second payment account information, which is the payment account information corresponding to the payment account bound to the user information in the payment platform application corresponding to the target payment platform.

[0188] In some embodiments, the payment processing device 600 further includes:

[0189] The second request module is used to send an information query request to the platform server through the target payment control when it is determined that the user is not using the target payment platform for payment operations for the first time in the first application. The information query request is used to instruct the platform server to query the payment account information corresponding to the payment account bound to the user information, so as to obtain the bound payment account information.

[0190] The fourth display module is used to receive and display the bound payment account information sent by the platform server through the target payment control;

[0191] The fourth input module is used to receive the user's fourth input regarding the third payment account information in the bound payment account information;

[0192] The third request module is used to respond to the fourth input by sending a payment request for the third payment account information to the platform server through the target payment control. The payment request is used to instruct the platform server to perform the payment operation based on the payment account corresponding to the third payment account information.

[0193] Therefore, by determining that the user is making a payment using the target payment platform for the first time in the first application, the second application is launched using the target payment control corresponding to the target payment platform set in the first application. The second application is then used to complete the payment operation. After the payment operation is completed, the user is then guided to bind their payment account. Thus, because this embodiment of the application processes payment by paying first and then binding the payment account, the payment process is seamless, improving the user's payment experience.

[0194] Figure 7 This is a schematic diagram of the structure of a payment processing device provided in one embodiment of this application. The payment processing device can be configured in, for example... Figure 1 The platform server 12 shown.

[0195] like Figure 7 As shown, the payment processing device 700 may include:

[0196] The information acquisition module 701 is used to acquire user information corresponding to the user who has completed the target payment operation. The target payment operation is when the user uses the target payment platform for the first time in the first application in the terminal device to perform a payment operation. The terminal device launches the second application through the target payment control and performs the payment operation using the second application. The target payment platform is the payment platform to which the platform server belongs. The target payment control is the payment control set in the first application that corresponds to the target payment platform.

[0197] Information query module 702 is used to query the corresponding payment account information based on the user information, as the payment account information to be bound;

[0198] Information sending module 703 is used to send the payment account information to be bound to the target payment control in the terminal device;

[0199] The request receiving module 704 is used to receive a binding request sent by the terminal device through the target payment control for at least one target payment account among the payment account information to be bound.

[0200] The binding operation module 705 is used to perform a binding operation on the user information and the payment account corresponding to the at least one target payment account information in response to the binding request.

[0201] The payment processing device 700 described above will be explained in detail below:

[0202] In some embodiments, when the second application is a financial institution application corresponding to the target financial institution, the information acquisition module 701 may specifically be used for:

[0203] The system receives user information sent by the institutional server corresponding to the target financial institution. This user information is sent by the institutional server upon receiving an authorization instruction sent by the terminal device through the second application.

[0204] In some embodiments, where a financial institution application corresponding to a financial institution exists in the terminal device, the information query module 702 can specifically be used for:

[0205] Based on the user information, query the payment account information corresponding to the payment account bound in the financial institution application to obtain the first payment account information; the payment account information to be bound includes the first payment account information.

[0206] In some embodiments, where a payment platform application corresponding to the target payment platform exists in the terminal device, the information query module 702 can specifically be used for:

[0207] Based on the user information, query the payment account information corresponding to the payment account bound in the payment platform application to obtain the second payment account information; the payment account information to be bound includes the second payment account information.

[0208] In some embodiments, the payment processing device 700 further includes:

[0209] The second receiving module is used to receive an information query request sent by the terminal device through the target payment control. The information query request is sent by the user when the user performs a payment operation on the target payment platform in the first application within the terminal device, which is not the first time.

[0210] The third query module is used to respond to the information query request, query the payment account information corresponding to the payment account bound to the user information, and obtain the bound payment account information;

[0211] The second sending module is used to send the bound payment account information to the terminal device;

[0212] The third receiving module is used to receive a payment request sent by the terminal device through the target payment control for the third payment account information in the bound payment account information;

[0213] The first payment module is used to respond to the payment request and perform the payment operation based on the payment account corresponding to the third payment account information.

[0214] Therefore, when a user first uses the target payment platform in the first application to make a payment, the terminal device launches the second application via a target payment control corresponding to the target payment platform set in the first application. The user then completes the payment using the second application. After the payment is completed, the platform server obtains the user information corresponding to the user who completed the target payment, retrieves the corresponding payment account information to be bound based on this user information, and guides the user to select at least one target payment account on the terminal device. The platform server then binds the user information and the payment account corresponding to at least one target payment account. Thus, because this embodiment processes payment by paying first and then binding the payment account, the payment process is seamless, improving the user's payment experience.

[0215] Figure 8 This is a schematic diagram of the structure of an electronic device provided in one embodiment of this application.

[0216] Electronic device 800 may include processor 801 and memory 802 storing computer program instructions.

[0217] Specifically, the processor 801 may include a central processing unit (CPU), an application-specific integrated circuit (ASIC), or one or more integrated circuits that can be configured to implement the embodiments of this application.

[0218] Memory 802 may include mass storage for data or instructions. For example, and not limitingly, memory 802 may include a hard disk drive (HDD), floppy disk drive, flash memory, optical disk, magneto-optical disk, magnetic tape, or Universal Serial Bus (USB) drive, or a combination of two or more of these. Where appropriate, memory 802 may include removable or non-removable (or fixed) media. Where appropriate, memory 802 may be internal or external to the integrated gateway disaster recovery device. In a particular embodiment, memory 802 is non-volatile solid-state memory.

[0219] In certain embodiments, the memory may include read-only memory (ROM), random access memory (RAM), disk storage media devices, optical storage media devices, flash memory devices, and electrical, optical, or other physical / tangible memory storage devices. Thus, typically, 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 method according to one aspect of this application.

[0220] The processor 801 implements any of the payment processing methods described in the above embodiments by reading and executing computer program instructions stored in the memory 802.

[0221] In some examples, the electronic device 800 may also include a communication interface 803 and a bus 810. For example, Figure 8 As shown, the processor 801, memory 802, and communication interface 803 are connected through bus 810 and complete communication with each other.

[0222] The communication interface 803 is mainly used to realize communication between various modules, devices, units and / or equipment in the embodiments of this application.

[0223] Bus 810 includes hardware, software, or both, that couples components of an online data traffic metering device together. For example, and not as a limitation, bus 810 may include an Accelerated Graphics Port (AGP) or other graphics bus, an Enhanced Industry Standard Architecture (EISA) bus, a Front Side Bus (FSB), HyperTransport (HT) interconnect, an Industry Standard Architecture (ISA) bus, an Infinite Bandwidth Interconnect, a Low Pin Count (LPC) bus, a memory bus, a Microchannel Architecture (MCA) bus, a Peripheral Component Interconnect (PCI) bus, a PCI-Express (PCI-X) bus, a Serial Advanced Technology Attachment (SATA) bus, a Video Electronics Standards Association Local (VLB) bus, or other suitable buses, or combinations of two or more of these. Where appropriate, bus 810 may include one or more buses. Although specific buses are described and illustrated in embodiments of this application, any suitable bus or interconnect is contemplated herein.

[0224] For example, the electronic device 800 can be a mobile phone, tablet computer, laptop computer, handheld computer, in-vehicle electronic device, ultra-mobile personal computer (UMPC), netbook, or personal digital assistant (PDA), etc.

[0225] The electronic device 800 can execute the payment processing method in the embodiments of this application, thereby achieving a combination Figures 1 to 7 The payment processing method and apparatus described.

[0226] Furthermore, in conjunction with the payment processing methods in the above embodiments, this application embodiment can provide a computer-readable storage medium for implementation. This computer-readable storage medium stores computer program instructions; when these computer program instructions are executed by a processor, they implement any of the payment processing methods in the above embodiments. Examples of computer-readable storage media include non-transitory computer-readable storage media, such as portable disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), portable compact disk read-only memory (CD-ROM), optical storage devices, magnetic storage devices, etc.

[0227] It should be clarified that this application is not limited to the specific configurations and processes described above and shown in the figures. For the sake of brevity, detailed descriptions of known methods are omitted here. In the above embodiments, several specific steps are described and shown as examples. However, the method process of this application is not limited to the specific steps described and shown. Those skilled in the art can make various changes, modifications, and additions, or change the order of steps, after understanding the spirit of this application.

[0228] The functional blocks shown in the above-described structural diagram can be implemented as hardware, software, firmware, or a combination thereof. When implemented in hardware, they can be, for example, electronic circuits, application-specific integrated circuits (ASICs), appropriate firmware, plug-ins, function cards, etc. When implemented in software, the elements of this application are programs or code segments used to perform the required tasks. Programs or code segments can be stored on a machine-readable medium or transmitted over a transmission medium or communication link via data signals carried on a carrier wave. "Machine-readable medium" can include any medium capable of storing or transmitting information. Examples of machine-readable media include electronic circuits, semiconductor memory devices, ROM, flash memory, erasable ROM (EROM), floppy disks, CD-ROMs, optical disks, hard disks, fiber optic media, radio frequency (RF) links, etc. Code segments can be downloaded via computer networks such as the Internet, intranets, etc.

[0229] It should also be noted that the exemplary embodiments mentioned in this application describe methods or systems based on a series of steps or apparatus. However, this application is not limited to the order of the above steps; that is, the steps can be performed in the order mentioned in the embodiments, or in a different order, or several steps can be performed simultaneously.

[0230] The aspects of this application have been described above with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of this application. It should be understood that each block in the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing apparatus to produce a machine such that these instructions, executable via the processor of the computer or other programmable data processing apparatus, enable the implementation of the functions / actions specified in one or more blocks of the flowchart illustrations and / or block diagrams. Such a 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 is also understood that each block in the block diagrams and / or flowcharts, and combinations of blocks in the block diagrams and / or flowcharts, can also be implemented by dedicated hardware performing the specified functions or actions, or can be implemented by a combination of dedicated hardware and computer instructions.

[0231] The above description is merely a specific implementation of this application. Those skilled in the art will clearly understand that, for the sake of convenience and brevity, the specific working processes of the systems, modules, and units described above can be referred to the corresponding processes in the foregoing method embodiments, and will not be repeated here. It should be understood that the protection scope of this application is not limited thereto. Any person skilled in the art can easily conceive of various equivalent modifications or substitutions within the technical scope disclosed in this application, and these modifications or substitutions should all be covered within the protection scope of this application.

Claims

1. A payment processing method, applied to a terminal device, characterized in that, The method includes: If it is determined that the user is using the target payment platform for the first time in the first application, the second application is launched through the target payment control, which is the payment control set in the first application that corresponds to the target payment platform; The payment operation is performed using the second application. Upon completion of the payment operation, the payment account information to be bound is obtained and displayed through the target payment control. The payment account information to be bound is the payment account information queried by the platform server corresponding to the target payment platform based on the user information corresponding to the user. Receive first input from the user regarding at least one target payment account among the payment account information to be bound; In response to the first input, a binding request for the at least one target payment account information is sent to the platform server through the target payment control. The binding request is used to instruct the platform server to perform a binding operation on the user information and the payment account corresponding to the at least one target payment account information.

2. The method according to claim 1, characterized in that, Before invoking the second application via the target payment control, the method further includes: Query the financial institution applications that are installed on the terminal device and correspond to the financial institution. If the financial institution application exists, display the application information corresponding to the financial institution application; Receive a second input from the user regarding the target application information corresponding to the target financial institution in the application information; In response to the second input, the financial institution application corresponding to the target financial institution is determined as the second application based on the target application information.

3. The method according to claim 2, characterized in that, After querying the applications corresponding to financial institutions that are already installed on the terminal device, the method further includes: If the financial institution application does not exist, query the payment platform application that is already installed on the terminal device and corresponds to the payment platform. If a payment platform application exists that corresponds to the target payment platform, the payment platform application that corresponds to the target payment platform is identified as the second application.

4. The method according to claim 2, characterized in that, Before obtaining and displaying the payment account information to be bound through the target payment control, the method further includes: The second application receives authorization prompt information sent by the institution server corresponding to the target financial institution; The authorization prompt information is displayed in the second application; Receive third input from the user authorizing based on the authorization prompt information; In response to the third input, the second application sends an authorization instruction to the institution server, which instructs the institution server to send the user information to the platform server.

5. The method according to claim 4, characterized in that, The authorization prompt message includes the user information.

6. The method according to claim 2, characterized in that, The payment account information to be bound includes first payment account information, which is the payment account information corresponding to the payment account bound to the user information in the financial institution application corresponding to the financial institution.

7. The method according to claim 6 or 3, characterized in that, The payment account information to be bound includes second payment account information, which is the payment account information corresponding to the payment account bound to the user information in the payment platform application corresponding to the target payment platform.

8. The method according to claim 1, characterized in that, The method further includes: If it is determined that the user is not using the target payment platform for payment operations for the first time in the first application, an information query request is sent to the platform server through the target payment control. The information query request is used to instruct the platform server to query the payment account information corresponding to the payment account bound to the user information, so as to obtain the bound payment account information. The target payment control receives and displays the bound payment account information sent by the platform server. Receive the user's fourth input regarding the third payment account information in the bound payment account information; In response to the fourth input, a payment request for the third payment account information is sent to the platform server through the target payment control. The payment request is used to instruct the platform server to perform the payment operation based on the payment account corresponding to the third payment account information.

9. A payment processing method applied to a platform server, characterized in that, The method includes: Obtain user information corresponding to the user who completes the target payment operation. The target payment operation is when the user uses the target payment platform for the first time in the first application in the terminal device to perform a payment operation. The terminal device launches the second application through the target payment control and performs the payment operation using the second application. The target payment platform is the payment platform to which the platform server belongs. The target payment control is the payment control set in the first application that corresponds to the target payment platform. Based on the user information, query the corresponding payment account information, which will be used as the payment account information to be bound. Send the payment account information to be bound to the target payment control in the terminal device; Receive a binding request from the terminal device via the target payment control for at least one target payment account among the payment account information to be bound; In response to the binding request, a binding operation is performed on the payment account corresponding to the user information and the at least one target payment account information.

10. The method according to claim 9, characterized in that, When the second application is a financial institution application corresponding to the target financial institution, obtaining the user information corresponding to the user who completed the target payment operation includes: The system receives user information sent by the institutional server corresponding to the target financial institution. This user information is sent by the institutional server upon receiving an authorization instruction sent by the terminal device through the second application.

11. The method according to claim 9, characterized in that, If a financial institution application corresponding to a financial institution exists in the terminal device, the step of querying the corresponding payment account information based on the user information as the payment account information to be bound includes: Based on the user information, query the payment account information corresponding to the payment account bound in the financial institution application to obtain the first payment account information; The payment account information to be bound includes the first payment account information.

12. The method according to claim 9, characterized in that, If a payment platform application corresponding to the target payment platform exists in the terminal device, the step of querying the corresponding payment account information based on the user information as the payment account information to be bound includes: Based on the user information, query the payment account information corresponding to the payment account bound in the payment platform application to obtain the second payment account information; The payment account information to be bound includes the second payment account information.

13. The method according to claim 9, characterized in that, The method further includes: Receive information query request sent by the terminal device through the target payment control, wherein the information query request is sent by the user when performing a payment operation on the target payment platform in the first application within the terminal device, and this is not the first time; In response to the information query request, query the payment account information corresponding to the payment account bound to the user information to obtain the bound payment account information; Send the bound payment account information to the terminal device; Receive a payment request sent by the terminal device through the target payment control for a third payment account in the bound payment account information; In response to the payment request, the payment operation is performed based on the payment account corresponding to the third payment account information.

14. A payment processing device, applied to a terminal device, characterized in that, The device includes: The program initiation module is used to initiate the second application through the target payment control when it is determined that the user is using the target payment platform for the first time in the first application to perform a payment operation. The target payment control is the payment control set in the first application that corresponds to the target payment platform. A payment operation module is used to perform the payment operation using the second application. The first display module is used to obtain and display the payment account information to be bound through the target payment control when the payment operation is completed. The payment account information to be bound is the payment account information queried by the platform server corresponding to the target payment platform based on the user information corresponding to the user. The first input module is used to receive the user's first input regarding at least one target payment account information among the payment account information to be bound; The first request module is configured to respond to the first input by sending a binding request for the at least one target payment account information to the platform server through the target payment control. The binding request is used to instruct the platform server to perform a binding operation on the user information and the payment account corresponding to the at least one target payment account information.

15. A payment processing device, applied to a platform server, characterized in that, The device includes: The information acquisition module is used to acquire user information corresponding to the user who has completed the target payment operation. The target payment operation is when the user uses the target payment platform for the first time in the first application in the terminal device to perform a payment operation. The terminal device launches the second application through the target payment control and performs the payment operation using the second application. The target payment platform is the payment platform to which the platform server belongs. The target payment control is the payment control set in the first application that corresponds to the target payment platform. The information query module is used to query the corresponding payment account information based on the user information, which will be used as the payment account information to be bound. The information sending module is used to send the payment account information to be bound to the target payment control in the terminal device; The request receiving module is used to receive a binding request sent by the terminal device through the target payment control for at least one target payment account among the payment account information to be bound. The binding operation module is used to perform a binding operation on the user information and the payment account corresponding to the at least one target payment account information in response to the binding request.

16. An electronic device, characterized in that, The device includes: a processor and a memory storing computer program instructions; When the processor executes the computer program instructions, it implements the steps of the payment processing method as described in any one of claims 1-8 or 9-13.

17. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores computer program instructions that, when executed by a processor, implement the steps of the payment processing method as described in any one of claims 1-8 or 9-13.

Images