Cross-terminal payment processing method, system, device, equipment and medium

Abstract

The invention relates to a cross-terminal payment processing method, system and device, equipment and a medium. The first terminal responds to the operation instruction for the to-be-paid object, and the pull-up request of the payment page including the first account information is sent to the middle page server. In addition, the second terminal sends information of a second account logged in by the second terminal to the middle page server. The first account information and the second account information are subjected to consistency check through the middle page server, so that an account logged in by a first terminal serving as a payment page initiator and an account logged in by a second terminal serving as an actual payer are both first accounts; therefore, the money paid by the second terminal can be recharged into the first account, namely the member account, the user can smoothly enjoy the member rights and interests, and the user experience is improved.

Description

Technical Field

[0001] The present disclosure relates to the field of computers, and in particular to a cross-terminal payment processing method, system, device, equipment, and medium. Background Art

[0002] With the continuous development of technology, online payment has become a common payment method. For example, after a user selects a product or digital product on a computer, the computer displays a payment QR code. The user then uses their mobile phone to scan the payment QR code to make the payment.

[0003] However, some products or digital goods require membership registration, and users may have multiple accounts, including both member and non-member accounts. If a user logs in to a non-member account through their mobile phone, even after scanning the payment QR code to pay, they still cannot use the product or digital goods because their member account has not been topped up, resulting in a poor user experience. Summary of the Invention

[0004] In order to solve the above technical problems or at least partially solve the above technical problems, the present disclosure provides a cross-terminal payment processing method, system, device, equipment and medium, so that the account logged in by the first terminal as the initiator of the payment page and the account logged in by the second terminal as the actual payer are consistent, thereby ensuring that the amount paid by the second terminal is recharged into the same account, ensuring that users can smoothly enjoy membership rights and interests, and improving user experience.

[0005] In a first aspect, an embodiment of the present disclosure provides a cross-terminal payment processing method, the method being applicable to a cross-terminal payment system, the cross-terminal payment system including a first terminal, an intermediate page server, and a second terminal, the method comprising:

[0006] The first terminal sends a request for pulling up a payment page to the intermediate page server in response to an operation instruction for the object to be paid, wherein the request includes the first account information;

[0007] The second terminal sends the second account information logged in by the second terminal to the intermediate page server;

[0008] The intermediate page server compares the first account information and the second account information, and if the first account information and the second account information are consistent, the intermediate page server sends authorization information to the second terminal;

[0009] The second terminal sends a cross-terminal payment request to a server corresponding to the payment application in the second terminal according to the authorization information, where the cross-terminal payment request is used to complete the cross-terminal payment for the object to be paid.

[0010] In a second aspect, an embodiment of the present disclosure provides a cross-terminal payment processing method, the method comprising:

[0011] The intermediate page server receives a request for opening a payment page sent by the first terminal, the request including the first account information, the request being sent by the first terminal in response to an operation instruction for an object to be paid;

[0012] The intermediate page server receives the second account information sent by the second terminal for logging in by the second terminal;

[0013] The intermediate page server compares the first account information and the second account information. If the first account information and the second account information are consistent, the intermediate page server sends authorization information to the second terminal. The authorization information is used to authorize the second terminal to complete the cross-terminal payment for the object to be paid.

[0014] In a third aspect, an embodiment of the present disclosure provides a cross-terminal payment system, the cross-terminal payment system comprising a first terminal, an intermediate page server, and a second terminal;

[0015] The first terminal is configured to send a request to the intermediate page server to pull up a payment page in response to an operation instruction for the object to be paid, wherein the request includes first account information;

[0016] The second terminal is used to send the second account information logged in by the second terminal to the intermediate page server;

[0017] The intermediate page server is used to compare the first account information and the second account information. If the first account information and the second account information are consistent, the intermediate page server sends authorization information to the second terminal;

[0018] The second terminal is further configured to send a cross-end payment request to a server corresponding to a payment application in the second terminal according to the authorization information, wherein the cross-end payment request is configured to complete the cross-end payment for the object to be paid.

[0019] In a fourth aspect, an embodiment of the present disclosure provides a cross-terminal payment processing device, the device comprising:

[0020] a receiving module configured to receive a request from a first terminal to launch a payment page, the request including first account information, the request being sent by the first terminal in response to an operation instruction for an object to be paid; and receive second account information from a second terminal for login by the second terminal;

[0021] a comparison module, configured to compare the first account information with the second account information;

[0022] The sending module is used to send authorization information to the second terminal when the first account information and the second account information are consistent, and the authorization information is used to authorize the second terminal to complete the cross-terminal payment for the object to be paid.

[0023] In a fifth aspect, an embodiment of the present disclosure provides an electronic device, including:

[0024] Memory;

[0025] processor; and

[0026] computer programs;

[0027] The computer program is stored in the memory and is configured to be executed by the processor to implement the method as described in the first aspect or the second aspect.

[0028] In a sixth aspect, an embodiment of the present disclosure provides a computer-readable storage medium having a computer program stored thereon, wherein the computer program is executed by a processor to implement the method described in the first aspect or the second aspect.

[0029] In a seventh aspect, an embodiment of the present disclosure provides a computer program product, comprising a computer program, which implements the method described in the first aspect or the second aspect when executed by a processor.

[0030] The cross-terminal payment processing method, system, apparatus, device and medium provided by the embodiments of the present disclosure send a request to pull up a payment page including first account information to an intermediate page server in response to an operation instruction for the object to be paid by the first terminal. In addition, the second terminal sends the second account information logged in by the second terminal to the intermediate page server. The intermediate page server performs a consistency check on the first account information and the second account information, so that the account logged in by the first terminal as the initiator of the payment page and the account logged in by the second terminal as the actual payer are both the first account, thereby ensuring that the amount paid by the second terminal is recharged to the first account, i.e., the member account, ensuring that the user can smoothly enjoy the membership rights and interests, and improving the user experience. BRIEF DESCRIPTION OF THE DRAWINGS

[0031] The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present disclosure and, together with the description, serve to explain the principles of the present disclosure.

[0032] In order to more clearly illustrate the embodiments of the present disclosure or the technical solutions in the prior art, the following briefly introduces the drawings required for use in the embodiments or the description of the prior art. Obviously, for ordinary technicians in this field, other drawings can be obtained based on these drawings without any creative work.

[0033] Figure 1 A flow chart of the cross-terminal payment processing method provided in an embodiment of the present disclosure;

[0034] Figure 2 A schematic diagram of an application scenario provided by an embodiment of the present disclosure;

[0035] Figure 3 A flow chart of the cross-terminal payment processing method provided in an embodiment of the present disclosure;

[0036] Figure 4 A flow chart of the cross-terminal payment processing method provided in an embodiment of the present disclosure;

[0037] Figure 5 A flow chart of the cross-terminal payment processing method provided in an embodiment of the present disclosure;

[0038] Figure 6 A signaling diagram for a first terminal to periodically query the current login status of a member account provided in an embodiment of the present disclosure;

[0039] Figure 7 The figure shows the internal processing flow after the second terminal scans the QR code according to the embodiment of the present disclosure;

[0040] Figure 8 A flow chart of the cross-terminal payment processing method provided in an embodiment of the present disclosure;

[0041] Figure 9 A flow chart of the cross-terminal payment processing method provided in an embodiment of the present disclosure;

[0042] Figure 10 A schematic diagram of the structure of a cross-terminal payment processing device provided in an embodiment of the present disclosure;

[0043] Figure 11 A schematic diagram of the structure of an electronic device embodiment provided by the present disclosure. DETAILED DESCRIPTION

[0044] In order to more clearly understand the above-mentioned objectives, features and advantages of the present disclosure, the scheme of the present disclosure will be further described below. It should be noted that the embodiments of the present disclosure and the features therein can be combined with each other in the absence of conflict.

[0045] In the following description, many specific details are set forth to facilitate a full understanding of the present disclosure, but the present disclosure may also be implemented in other ways different from those described herein; it is obvious that the embodiments in the specification are only part of the embodiments of the present disclosure, rather than all of the embodiments.

[0046] Online payment has become a common payment method. For example, after a user selects a product or digital product on a computer, the computer displays a payment QR code. Furthermore, the user uses a mobile phone to scan the payment QR code to make the payment. However, the use of some products or digital products requires registered membership, and the user may have multiple accounts, including member accounts and non-member accounts. If the user logs in to a non-member account with a mobile phone, after the user uses the mobile phone to scan the payment QR code to make the payment, the user still cannot use the product or digital product because the member account has not been recharged, resulting in a poor user experience. To address this problem, the embodiments of the present disclosure provide a cross-end payment processing method, which is described below in conjunction with specific embodiments.

[0047] Figure 1 This is a flow chart of the cross-terminal payment processing method provided by the embodiment of the present disclosure. The method is applicable to a cross-terminal payment system, which includes a first terminal, an intermediate page server, and a second terminal. Figure 2 As shown, the first terminal 21 can be a desktop computer, a laptop computer, an all-in-one computer, a smart home device, etc. The second terminal 22 can be a mobile device such as a mobile phone or a tablet computer. The intermediate page server 23 can be a remote server or a server in a server cluster. A server cluster can be a collection of multiple servers that perform the same service together, and it looks like there is only one server to the client. The server cluster can use multiple computers for parallel computing to obtain a higher computing speed, and can also use multiple computers for backup, so that the entire system can still operate normally after any machine breaks down. Specifically, the first terminal 21 can interact with the intermediate page server 23, and the second terminal 22 can interact with the intermediate page server 23. The cross-end payment processing method provided by the embodiment of the present disclosure is introduced below with reference to the illustrations. Figure 1 As shown, the specific steps of this method are as follows:

[0048] S101. The first terminal sends a request to pull up a payment page to the intermediate page server in response to an operation instruction for an object to be paid, where the request includes first account information.

[0049] For example, the first terminal 21 is installed with video software, which is a client software for playing videos. Since some video resources are not free for users to watch, but require users to apply for membership and recharge to purchase before they can watch them. Therefore, the user will register a membership account in advance. For example, the first terminal 21 displays a registration page. After the user fills in the registration information on the registration page, the first terminal 21 sends a registration request to the intermediate page server 23. The registration request includes registration information, and the registration information includes member account information, such as a member account and password. After receiving the registration information, the intermediate page server 23 extracts the member account and password from the registration information, hashes the password using a hash algorithm, and generates a salt value (Salt) to increase security. The member account, the salt value, and the hash value are then stored in the database. When a user recharges to purchase a video resource, the user logs in to the member account. For example, the first terminal 21 displays a login page, and the user enters a member account and password on the login page. In addition, the login page also includes a "Confirm" or "Login" button. When the user clicks the button, the first terminal 21 sends an account login request to the intermediate page server 23. When the intermediate page server 23 feeds back confirmation information to the first terminal 21, the first terminal 21 successfully logs into the member account. The disclosed embodiment records the member account as the first account. After the first terminal 21 successfully logs into the member account, the first terminal 21 displays a product or service page, which may include multiple products or multiple services. The user can click on a product or service on the page, and the product or service is recorded as the object to be paid. Further, in response to the user's operation instruction for the object to be paid, such as a click operation, the first terminal 21 sends a request to the intermediate page server 23 to pull up the payment page. The pull-up request includes the first account information, and the first account information includes the member account and password. Here, the first account information is recorded as the member account information.

[0050] S102: The second terminal sends the second account information logged in by the second terminal to the intermediate page server.

[0051] In the disclosed embodiments, the same user can log in to the same account on different terminals. For example, the user may have multiple terminals. At time T1, the user logs in to a member account on the first terminal 21. At time T2, the user logs in to a member account on the second terminal 22. Furthermore, the same user may have multiple registered accounts. For example, the user may have both a member account and a non-member account. The user may log in to a non-member account on the first terminal 21 or a non-member account on the second terminal 22. In other words, the user's login to a member account or a non-member account on the first terminal 21 is random, and the user's login to a member account or a non-member account on the second terminal 22 is also random. When a user logs in to a member account on the first terminal 21 and clicks on a product or service on the product or service page, the first terminal 21 displays a payment page including a payment code. The user may choose to complete the payment by having the first terminal 21 recognize the payment code. Alternatively, the user may choose to complete the cross-terminal payment by having the second terminal 22 recognize the payment code. If the user chooses to identify the payment code through the second terminal 22, the second terminal 22 sends the second account information logged in by the second terminal 22 to the intermediate page server 23. The second account information is the historical account information stored by the second terminal 22. The second account information is member account information or non-member account information.

[0052] S103: The intermediate page server compares the first account information with the second account information. If the first account information and the second account information are consistent, the intermediate page server sends authorization information to the second terminal.

[0053] For example, after the intermediate page server 23 receives the first account information (UID1) and the second account information (UID2), it compares the first account information (UID1) and the second account information (UID2). If the first account information (UID1) and the second account information (UID2) are consistent, it means that the historical account information stored in the second terminal 22 is the first account information, that is, the account number requested by the second terminal 22 for cross-end login is consistent with the account number currently logged in by the first terminal 21. Therefore, the second terminal 22 can realize cross-end login for the first account and subsequent cross-end payment. Further, the intermediate page server 23 sends authorization information to the second terminal 22, and the authorization information is used to authorize the second terminal 22 to complete the cross-end payment under the first account, that is, to complete the cross-end payment of the payment object.

[0054] S104. The second terminal sends a cross-terminal payment request to a server corresponding to the payment application in the second terminal according to the authorization information. The cross-terminal payment request is used to complete the cross-terminal payment for the object to be paid.

[0055] For example, after the second terminal 22 receives the authorization information from the intermediate page server 23, it sends a cross-end payment request to the server corresponding to the payment application in the second terminal 22 according to the authorization information to complete the cross-end payment for the object to be paid.

[0056] In the disclosed embodiment, a first terminal responds to an operation instruction for the object to be paid by sending a request to the intermediate page server to launch a payment page including first account information. In addition, a second terminal sends the second account information logged in by the second terminal to the intermediate page server. The intermediate page server performs a consistency check on the first account information and the second account information, so that the account logged in by the first terminal as the initiator of the payment page and the account logged in by the second terminal as the actual payer are both the first account, thereby ensuring that the payment made by the second terminal is recharged into the first account, i.e., the member account, ensuring that the user can smoothly enjoy the membership benefits and improving the user experience.

[0057] Figure 3 A flow chart of a cross-terminal payment processing method provided by another embodiment of the present disclosure. After the first terminal sends a request to pull up a payment page to the intermediate page server in response to an operation instruction for the object to be paid, the method further includes: Figure 3 The following steps are shown:

[0058] S301. The intermediate page server generates a session identifier corresponding to the first account information according to the pull request, and sends the session identifier to the first terminal.

[0059] For example, after receiving the pull request, the intermediate page server 23 extracts the member account and password from the pull request. Furthermore, the intermediate page server 23 searches the database for the salt value and hash value associated with the member account. The intermediate page server 23 hashes the password in the pull request using the same hash algorithm and the salt value to generate a newly generated hash value. The intermediate page server 23 compares the newly generated hash value with the hash value found in the database. If the two match, the password is entered correctly, indicating that the intermediate page server 23 has successfully verified the first account information. Upon successful verification, the intermediate page server 23 creates a session and generates a session identifier, which is referred to as a token. The intermediate page server 23 may store the correspondence between the first account information and the session identifier in the database, or the correspondence between the first account and the session identifier in the database. Specifically, the intermediate page server 23 stores the generated session identifier corresponding to the first account information in the database, or stores the generated session identifier corresponding to the first account in the database. Furthermore, the intermediate page server 23 sends the session identifier to the first terminal 21. The first terminal 21 automatically sends the session identifier to the intermediate page server 23 in each subsequent request to maintain the logged-in state. After receiving the corresponding request, the intermediate page server 23 verifies the user identity through the session identifier and provides corresponding services or data.

[0060] S302: After obtaining the session identifier from the first terminal, the second terminal sends a cross-terminal login request for the first account to the intermediate page server, where the cross-terminal login request includes the session identifier.

[0061] For example, after the first terminal 21 receives the session identifier from the intermediate page server 23, the second terminal 22 obtains the session identifier from the first terminal 21 and, based on the session identifier, sends a cross-terminal login request for the first account, i.e., the member account, to the intermediate page server 23. The cross-terminal login request includes the session identifier. That is, after the first terminal 21 logs in to the first account, the second terminal 22 further sends a cross-terminal login request to the intermediate page server 23 to request login to the first account, causing the first account to be transferred from the first terminal 21 to the second terminal 22, thereby achieving cross-terminal login for the first account. Specifically, the cross-terminal login request includes the session identifier corresponding to the first account information. The session identifier can be the first account information or a unique identifier corresponding to the first account.

[0062] Optionally, the second terminal sends the second account information for logging in by the second terminal to the intermediate page server, including: if the second terminal fails to obtain the cross-terminal login status identifier generated by the intermediate page server locally, the second terminal determines that the cross-terminal login for the first account has failed; the second terminal obtains the second account information from the local payment application and sends the second account information to the intermediate page server.

[0063] For example, after receiving the cross-end login request, the intermediate page server 23 obtains the session identifier from the cross-end login request and performs user identity authentication based on the session identifier. The specific verification process can be that the intermediate page server 23 queries the database based on the session identifier in the cross-end login request to confirm whether the session identifier corresponding to the first account information stored in the database is consistent with the session identifier in the cross-end login request. If they are consistent, the verification is successful, and the intermediate page server 23 authorizes the second terminal 22 to log in to the first account. If they are inconsistent, the verification fails, and the intermediate page server 23 determines that the second terminal 22 cannot log in to the first account across ends, then the intermediate page server 23 does not send a cross-end login status identifier to the second terminal 22. At this time, the second terminal 22 cannot obtain the cross-end login status identifier generated by the intermediate page server 23 locally, and the cross-end login status identifier is P00001. In other words, if the cross-device login status indicator does not exist locally on second terminal 22, second terminal 22 determines that the cross-device login for the first account has failed. In this case, second terminal 22 obtains second account information from the local payment application. This second account information is historical account information stored by the payment application. Furthermore, second terminal 22 sends this second account information to intermediate page server 23.

[0064] For example, when the cross-terminal login of the second terminal 22 fails, the second terminal 22 obtains the second account information stored in its local payment application. Specifically, the second terminal 22 can call the interface provided by the payment application to obtain the second account information stored by the payment application. Assuming that the user has registered a non-member account on the intermediate page server 23, if the user has logged in to the non-member account through the payment application on the second terminal 22, the payment application will store the non-member account information. If the user has logged in to the member account through the payment application on the second terminal 22, the payment application will store the member account information. In other words, the payment application will store the account information of the account that the user last logged in through the payment application on the second terminal 22. Therefore, the account information stored by the payment application is also called historical account information. Further, the second terminal 22 sends the second account information to the intermediate page server 23.

[0065] Optionally, after the intermediate page server generates a session identifier corresponding to the first account information based on the pull-up request and sends the session identifier to the first terminal, the method also includes: the first terminal generates a QR code based on the session identifier, and the QR code includes the session identifier.

[0066] For example, after the first terminal 21 successfully logs in to the member account, the first terminal 21 displays the home page. After the user clicks the recharge button on the home page, the first terminal 21 jumps to the recharge page. On this recharge page, the user selects the recharge amount. The first terminal 21 generates a QR code for payment based on the session identifier. The QR code includes not only information such as the payment link, merchant ID, and payment amount, but also the session identifier. Furthermore, the first terminal 21 displays the QR code, which includes the session identifier.

[0067] Optionally, the second terminal obtains the session identifier from the first terminal, including: the second terminal obtains the session identifier by scanning the QR code displayed by the first terminal.

[0068] For example, there are multiple ways for the second terminal 22 to obtain the session identifier from the first terminal 21. One way is for the first terminal 21 to send the session identifier to the second terminal 22. Another way is for the second terminal 22 to scan a QR code displayed on the first terminal 21. The QR code generation process is as described above. When the second terminal 22 scans the QR code, it obtains the session identifier. For example, if a payment application is installed on the second terminal 22, when a user scans the QR code using the camera on the second terminal 22, the second terminal 22 enters a scanning intermediate page, which is invisible to the user. Simultaneously, the payment application in the second terminal 22 parses the information in the QR code to obtain information such as the payment link, merchant ID, payment amount, and the session identifier. Furthermore, based on the session identifier, the second terminal 22 sends a cross-terminal login request for the member account to the intermediate page server 23. The cross-terminal login request includes the session identifier.

[0069] Optionally, after the second terminal obtains the session identifier from the first terminal and sends a cross-terminal login request for the first account to the intermediate page server, the method further includes: Figure 4 The following steps are shown:

[0070] S401. If the intermediate page server determines that the session identifier included in the cross-end login request is consistent with the session identifier corresponding to the first account information generated by the intermediate page server, the intermediate page server stores the record information of the second terminal's cross-end login to the first account and generates a cross-end login status identifier.

[0071] For example, after the second terminal 22 sends a cross-terminal login request for the member account to the intermediate page server 23 based on the session identifier, the intermediate page server 23 obtains the session identifier from the cross-terminal login request. Furthermore, the intermediate page server 23 verifies the user's identity using the session identifier. Specifically, the intermediate page server 23 queries a database based on the session identifier in the cross-terminal login request to confirm whether the session identifier corresponding to the first account information stored in the database is consistent with the session identifier in the cross-terminal login request. If they are consistent, the intermediate page server 23 stores the record of the second terminal 22 logging into the member account in the database and generates a cross-terminal login status identifier.

[0072] S402: The intermediate page server writes the cross-terminal login status identifier into a preset file of the second terminal.

[0073] For example, after the intermediate page server 23 generates a cross-end login status identifier, it stores the cross-end login status identifier in a database and sends the cross-end login status identifier to the second terminal 22. Specifically, the intermediate page server 23 writes the cross-end login status identifier into a preset file of the second terminal 22, such as a cookie.

[0074] S403: After obtaining the cross-terminal login status identifier from the preset file, the second terminal determines that the cross-terminal login for the first account is successful, and displays the payment page.

[0075] For example, after the second terminal 22 obtains the cross-end login status identifier P00001 from the preset file, it determines that the cross-end login is successful. At this time, the second terminal 22 jumps from the code scanning intermediate page to the payment page and displays the payment page. The payment page is used to prompt the user to make payment. For example, the user enters the payment password on the payment page to complete the cross-end payment.

[0076] It is understood that the embodiments of this disclosure use video software as an example to describe the cross-device payment processing flow for users purchasing digital goods. Furthermore, the methods described in these embodiments can also be applied to shopping software to implement the cross-device payment processing flow for users purchasing goods. The specific process is similar to the above process and will not be repeated here.

[0077] In the embodiment of the present disclosure, a request to pull up a payment page is sent to the intermediate page server through the first terminal. The request includes member account information. After the intermediate page server successfully verifies the member account information, it sends a session identifier to the first terminal. When the first terminal generates a QR code, the session identifier is stored in the QR code, so that the second terminal obtains the session identifier when scanning the QR code, and sends a cross-end login request for the member account to the intermediate page server based on the session identifier. After the intermediate page server processes the cross-end login request, it sends a cross-end login status identifier to the second terminal to indicate that the cross-end login is successful, thereby ensuring the consistency of the account for cross-end login, that is, the second terminal successfully logs in to the member account. When the user makes a payment through the second terminal, the payment is recharged into the member account, ensuring that the user can smoothly enjoy the membership rights and interests, thereby improving the user experience.

[0078] In the above embodiment, the intermediate page server 23 compares the first account information with the second account information. In other embodiments, the second terminal 22 may also compare the first account information with the second account information. For example, after the second terminal 22 obtains the second account information from the payment application, the second account information is compared with the first account information obtained by the second terminal 22.

[0079] Specifically, the second terminal 22 obtains the first account information in the following ways:

[0080] In the embodiment of the present disclosure, the second terminal 22 obtains the member account information in the following ways:

[0081] In a feasible implementation, the QR code generated by the first terminal also includes the first account information; and the second terminal obtains the first account information when scanning the QR code.

[0082] For example, when the first terminal 21 generates a QR code, the first account information is stored in the QR code, so that the second terminal 22 obtains the first account information when scanning the QR code.

[0083] In another feasible implementation, the QR code generated by the first terminal also includes a payment link; the second terminal obtains the payment link when scanning the QR code; the second terminal accesses the intermediate page server according to the payment link, and obtains the first account information from the intermediate page server.

[0084] For example, the QR code generated by the first terminal 21 contains a payment link. The second terminal 22 obtains the payment link when scanning the QR code, and accesses the intermediate page server 23 according to the payment link. Since the intermediate page server 23 stores the first account information, the second terminal 22 can obtain the first account information from the intermediate page server 23.

[0085] Optionally, if the first account information and the second account information are consistent, after the intermediate page server sends authorization information to the second terminal, the method also includes: the second terminal displays an authorization page based on the authorization information, and the authorization page is used to prompt the authorization of the payment application in the second terminal to log in to the first account; the second terminal displays the payment page in response to the authorization operation for the payment application to log in to the first account.

[0086] If the second terminal 22 compares the second account information with the first account information and determines that the second account information is consistent with the first account information, it indicates that the account the user most recently logged in through the payment application on the second terminal 22 is a member account, ensuring account consistency across different devices. At this point, the second terminal 22 displays an authorization page prompting the user to authorize the payment application to log in to the member account. For example, after the user authorizes the payment application to log in to the member account on the authorization page, the second terminal 22 may respond by displaying a payment page, prompting the user to complete the cross-device payment.

[0087] Optionally, the method also includes: if the first account information and the second account information are inconsistent, the intermediate page server sends a prompt message to the second terminal, and the prompt message is used to prompt the second terminal that it cannot complete the cross-terminal payment for the object to be paid; the second terminal displays the prompt message.

[0088] For example, if the intermediate page server 23 compares the first account information with the second account information and determines that the first account information and the second account information are inconsistent, it means that the account the user last logged in through the payment application on the second terminal 22 is a non-member account, and the consistency of the account cannot be guaranteed across different terminals. Therefore, the intermediate page server 23 may send a prompt message to the second terminal 22, indicating that the second terminal 22 cannot complete the cross-terminal payment under the member account, that is, it cannot complete the cross-terminal payment for the object to be paid. When the second terminal 22 receives the prompt message, it displays the prompt message, thereby notifying the user that the purchase cannot be completed, thereby avoiding the incorrect recharge of a non-member account.

[0089] Optionally, after the first terminal sends a request to pull up a payment page to the intermediate page server in response to an operation instruction for the object to be paid, the method further includes: Figure 5 The following steps are shown:

[0090] S501: The first terminal periodically sends a login status query request for the first account to the intermediate page server.

[0091] For example, after the first terminal 21 sends a request to pull up the payment page to the intermediate page server 23, it can further periodically send a login status query request for the first account to the intermediate page server 23, that is, periodically query whether the member account is in a valid state.

[0092] S502: The intermediate page server sends the current login status of the first account to the first terminal according to the login status query request.

[0093] For example, each time the intermediate page server 23 receives a login status query request, it queries whether the member account is in a valid state, and sends the current login state of the member account, ie, valid state or invalid state, to the first terminal 21 .

[0094] S503: If the current login status indicates that the first account login is invalid, the first terminal prompts the user to log in to the first account again.

[0095] If the current login status indicates that the member account login is invalid, that is, in an invalid state, the first terminal 21 prompts the user to log in to the member account again.

[0096] The embodiment of the present disclosure periodically queries the current login status of the member account through the first terminal, and updates the page information in time according to the current login status. For example, when the current login status indicates that the login of the member account is invalid, a prompt message is displayed on the page to prompt the user to log in to the member account again, ensuring that the user's latest logged-in account is the member account, and preventing erroneous operations caused by changes in the account status.

[0097] Figure 6 The signaling diagram of the first terminal periodically querying the current login status of the member account provided in the embodiment of the present disclosure. Figure 6 As shown, the query process includes the following steps:

[0098] S601: The user enters the membership account and password at the first terminal.

[0099] S602: The first terminal sends a request to open a payment page to the intermediate page server.

[0100] S603: The intermediate page server sends a session identifier to the first terminal.

[0101] S604: The first terminal starts a timer.

[0102] S605. The first terminal sends a login status query request to the intermediate page server every one minute.

[0103] S606: The intermediate page server sends the current login status of the member account to the first terminal.

[0104] S607: The first terminal updates the page display content according to the current login status.

[0105] Specifically, the implementation process and specific principles of S601-S607 can refer to the contents described in the above embodiment and will not be repeated here.

[0106] Figure 7 The figure shows the internal processing flow after the second terminal scans the QR code provided by the embodiment of the present disclosure. Figure 7 As shown, the process includes the following steps:

[0107] S701, enter the middle page of scanning code.

[0108] S702: Read data from the cookie.

[0109] S703: Determine whether the cross-terminal login status identifier P00001 can be read from the cookie. If so, execute S704; otherwise, execute S705.

[0110] S704: Display the payment page.

[0111] S705: Obtain historical account information stored by the payment application.

[0112] S706: Determine whether the historical account information and the member account information are consistent. If so, execute S707 and S708; otherwise, execute S709.

[0113] S707: Display the authorization page.

[0114] S708: After the user authorizes, the payment page is displayed.

[0115] S709: Prompt the user that the purchase cannot be completed.

[0116] Specifically, the implementation process and specific principles of S701-S709 can refer to the contents described in the above embodiment and will not be repeated here.

[0117] In addition, in the disclosed embodiments, when transmitting member account information or historical account information, the member account information or historical account information can also be encrypted and decrypted at the receiving end to ensure data privacy and prevent interception or tampering during transmission, thereby ensuring the security and reliability of data transmission. In addition, in the event of anomalies, such as network failures or service unavailability, by providing users with clear error prompts or handling methods, the stability of the system and user experience can be enhanced. When historical account information and the member account information are inconsistent, by prompting the user that the purchase cannot be completed, the user can intuitively understand the current login status and make effective decisions. In addition, the login status of the member account is recorded by the intermediate page server, so that the first terminal or the second terminal can obtain the login status of the member account from the intermediate page server in a timely manner, ensuring accurate recording of the login status. Recording the user purchase process log in the database can realize the logging and monitoring of the user purchase process, collecting the entire process log of each scan code payment, facilitating problem tracking and analysis, and improving the quality of system maintenance.

[0118] Figure 8 Flowchart of a cross-terminal payment processing method provided in an embodiment of the present disclosure. This method is applicable to a cross-terminal payment system, which includes a first terminal such as a personal computer (PC), an intermediate page server, and a second terminal such as a mobile phone. The PC includes a patrol login status module. The intermediate page server includes a passport system and a database. The mobile phone includes a code scanning intermediate page, a user information interface, and a payment application. Specifically, the method includes the following steps:

[0119] 1. The user logs in on the PC user interface, such as entering a member account and password.

[0120] 2. PC starts patrol login status module.

[0121] 3. The patrol login status module periodically sends a login status query request to the passport system.

[0122] 4. The passport system returns the current login status of the member account to the patrol login status module.

[0123] 5. The user uses a mobile phone to scan the QR code on the PC, and the phone enters the middle page of the code scanning.

[0124] 6. The mobile phone sends a cross-terminal login request to the passport system.

[0125] 7. The passport system generates and stores identification information.

[0126] 8. The passport system returns identification information to the user information interface.

[0127] 9. When the mobile phone determines that the identification information is not P00001, it calls the user information interface.

[0128] 10. The mobile phone obtains user information from the payment application through the user information interface.

[0129] 11. The payment application returns the user information to the user information interface.

[0130] 12. The user information interface returns the historical account information in the user information to the QR code scanning intermediate page.

[0131] 13. The mobile phone obtains member account information from the database.

[0132] 14. The database returns the member account information to the mobile phone.

[0133] 15. The phone checks whether the historical account information and the member account information are consistent. If the historical account information and the member account information are consistent, it will prompt that the login is successful. If they are inconsistent, it will prompt that the purchase cannot be made.

[0134] Specifically, the implementation process and specific principles of the above steps 1-15 can refer to the contents described in the above embodiment and will not be repeated here.

[0135] Figure 9 A flow chart of a cross-terminal payment processing method provided in another embodiment of the present disclosure. The method includes the following steps:

[0136] S901. The intermediate page server receives a request for opening a payment page sent by a first terminal, where the request includes first account information. The request is sent by the first terminal in response to an operation instruction for an object to be paid.

[0137] For example, in response to a user's operation instruction, such as a click operation, on the object to be paid, first terminal 21 sends a request to the intermediate page server 23 to launch a payment page. The request includes first account information, which includes a member account number and password. Here, the first account information is referred to as member account information. Intermediate page server 23 receives the request to launch the payment page sent by first terminal 21 and obtains the first account information from the request.

[0138] S902: The intermediate page server receives the second account information sent by the second terminal for logging in.

[0139] When a user logs in to a member account on the first terminal 21 and clicks on a product or service on the product or service page, the first terminal 21 displays a payment page, which includes a payment code. The user can choose to identify the payment code through the first terminal 21 to complete the payment. Or the user can choose to identify the payment code through the second terminal 22 to complete the cross-terminal payment. If the user chooses to identify the payment code through the second terminal 22, the second terminal 22 sends the second account information logged in by the second terminal 22 to the intermediate page server 23. The second account information is the historical account information stored by the second terminal 22. The second account information is member account information or non-member account information. The intermediate page server 23 receives the second account information logged in by the second terminal 22.

[0140] S903. The intermediate page server compares the first account information and the second account information. If the first account information and the second account information are consistent, the intermediate page server sends authorization information to the second terminal. The authorization information is used to authorize the second terminal to complete the cross-terminal payment for the object to be paid.

[0141] For example, after the intermediate page server 23 receives the first account information (UID1) and the second account information (UID2), it compares the first account information (UID1) and the second account information (UID2). If the first account information (UID1) and the second account information (UID2) are consistent, it means that the historical account information stored in the second terminal 22 is the first account information, that is, the account number requested by the second terminal 22 for cross-end login is consistent with the account number currently logged in by the first terminal 21. Therefore, the second terminal 22 can realize cross-end login for the first account and subsequent cross-end payment. Further, the intermediate page server 23 sends authorization information to the second terminal 22, and the authorization information is used to authorize the second terminal 22 to complete the cross-end payment under the first account.

[0142] For example, after receiving the authorization information from the intermediate page server 23, the second terminal 22 sends a cross-end payment request to the server corresponding to the payment application in the second terminal 22 based on the authorization information. After receiving the cross-end payment request, the server corresponding to the payment application further interacts with the second terminal 22 to complete the cross-end payment for the object to be paid.

[0143] In the embodiment of the present disclosure, an intermediate page server is used to perform a consistency check on the first account information in the request to pull up the payment page sent by the first terminal and the second account information sent by the second terminal, so that the account logged in by the first terminal as the initiator of the payment page and the account logged in by the second terminal as the actual payer are consistent, for example, both are member accounts, thereby ensuring that the money paid by the second terminal is recharged into the member account, ensuring that the user can smoothly enjoy the membership rights and interests, and improving the user experience.

[0144] The disclosed embodiment also provides a cross-terminal payment processing system. The cross-terminal payment processing system can execute the processing flow provided in the cross-terminal payment processing method embodiment. Specifically, the cross-terminal payment system includes a first terminal, an intermediate page server, and a second terminal;

[0145] The first terminal is configured to send a request to the intermediate page server to pull up a payment page in response to an operation instruction for the object to be paid, wherein the request includes first account information;

[0146] The second terminal is used to send the second account information logged in by the second terminal to the intermediate page server;

[0147] The intermediate page server is used to compare the first account information and the second account information. If the first account information and the second account information are consistent, the intermediate page server sends authorization information to the second terminal;

[0148] The second terminal is further configured to send a cross-end payment request to a server corresponding to a payment application in the second terminal according to the authorization information, wherein the cross-end payment request is configured to complete the cross-end payment for the object to be paid.

[0149] Optionally, after the first terminal sends a request to pull up the payment page to the intermediate page server in response to an operation instruction for the object to be paid, the intermediate page server is also used to generate a session identifier corresponding to the first account information based on the pull-up request, and send the session identifier to the first terminal; the second terminal is also used to obtain the session identifier from the first terminal, and then send a cross-end login request for the first account to the intermediate page server, and the cross-end login request includes the session identifier.

[0150] Optionally, when the second terminal sends the second account information logged in by the second terminal to the intermediate page server, it is specifically used to:

[0151] If the second terminal fails to obtain the cross-terminal login status identifier generated by the intermediate page server locally, the second terminal determines that the cross-terminal login for the first account has failed;

[0152] The second terminal obtains the second account information from the local payment application and sends the second account information to the intermediate page server.

[0153] Optionally, after the intermediate page server generates a session identifier corresponding to the first account information based on the pull-up request and sends the session identifier to the first terminal, the first terminal is also used to generate a QR code based on the session identifier, and the QR code includes the session identifier; when the second terminal obtains the session identifier from the first terminal, it is specifically used: the second terminal obtains the session identifier by scanning the QR code displayed by the first terminal.

[0154] Optionally, after the second terminal obtains the session identifier from the first terminal and sends a cross-end login request for the first account to the intermediate page server, the intermediate page server is also used to: if the intermediate page server determines that the session identifier included in the cross-end login request is consistent with the session identifier corresponding to the first account information generated by the intermediate page server, then the intermediate page server stores the record information of the second terminal's cross-end login to the first account and generates a cross-end login status identifier; the intermediate page server writes the cross-end login status identifier into a preset file of the second terminal; the second terminal is also used to: after obtaining the cross-end login status identifier from the preset file, determine that the cross-end login for the first account is successful, and display the payment page.

[0155] Optionally, if the first account information and the second account information are consistent, after the intermediate page server sends authorization information to the second terminal, the second terminal is also used to display an authorization page based on the authorization information, and the authorization page is used to prompt the payment application in the second terminal to log in to the first account; the second terminal displays the payment page in response to the authorization operation for the payment application to log in to the first account.

[0156] Optionally, the intermediate page server is also used to: when the first account information and the second account information are inconsistent, send a prompt message to the second terminal, and the prompt message is used to prompt the second terminal that it cannot complete the cross-terminal payment for the object to be paid; the second terminal is also used to display the prompt message.

[0157] Optionally, after the first terminal sends a request to pull up the payment page to the intermediate page server in response to an operation instruction for the object to be paid, the first terminal is also used to periodically send a login status query request for the first account to the intermediate page server; the intermediate page server is also used to send the current login status of the first account to the first terminal based on the login status query request; if the current login status indicates that the login of the first account is invalid, the first terminal is also used to prompt the user to log in to the first account again.

[0158] Figure 10 This is a schematic diagram of the structure of a cross-end payment processing device provided by an embodiment of the present disclosure. The cross-end payment processing device can be configured in the intermediate page server as described above. Figure 10 As shown, the cross-terminal payment processing device 100 includes:

[0159] Receiving module 1001, configured to receive a request from a first terminal to launch a payment page, the request including first account information, the request being sent by the first terminal in response to an operation instruction for a payment object; and receive second account information from a second terminal for login by the second terminal;

[0160] Comparison module 1002, configured to compare the first account information with the second account information;

[0161] The sending module 1003 is configured to send authorization information to the second terminal when the first account information and the second account information are consistent, wherein the authorization information is used to authorize the second terminal to complete the cross-terminal payment for the object to be paid.

[0162] The cross-end payment processing system described above may be implemented as an electronic device. In addition, the cross-end payment processing apparatus 100 described above may also be implemented as an electronic device. Figure 11 This is a schematic diagram of the structure of an electronic device embodiment provided by the present disclosure. Figure 11 As shown, the electronic device includes a memory 111 and a processor 112 .

[0163] The memory 111 is used to store programs. In addition to the aforementioned programs, the memory 111 may also be configured to store various other data to support operations on the electronic device. Examples of such data include instructions for any application or method operating on the electronic device, contact data, phone book data, messages, images, videos, and the like.

[0164] The memory 111 can be implemented by any type of volatile or non-volatile memory device or a combination thereof, such as static random access memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic memory, flash memory, magnetic disk or optical disk.

[0165] The processor 112 is coupled to the memory 111 and executes the program stored in the memory 111 to implement the technical solution of the above method embodiment.

[0166] Further, if Figure 11As shown, the electronic device may further include: a communication component 113, a power component 114, an audio component 115, a display 116 and other components. Figure 11 Only some components are shown schematically, which does not mean that the electronic device only includes Figure 11 Components shown.

[0167] The communication component 113 is configured to facilitate wired or wireless communication between the electronic device and other devices. The electronic device can access a wireless network based on a communication standard, such as WiFi, 2G or 3G, or a combination thereof. In an exemplary embodiment, the communication component 113 receives a broadcast signal or broadcast-related information from an external broadcast management system via a broadcast channel. In an exemplary embodiment, the communication component 113 also includes a near field communication (NFC) module to facilitate short-range communication. For example, the NFC module can be implemented based on radio frequency identification (RFID) technology, infrared data association (IrDA) technology, ultra-wideband (UWB) technology, Bluetooth (BT) technology and other technologies.

[0168] The power supply assembly 114 provides power to various components of the electronic device. The power supply assembly 114 may include a power management system, one or more power supplies, and other components associated with generating, managing, and distributing power to the electronic device.

[0169] The audio component 115 is configured to output and / or input audio signals. For example, the audio component 115 includes a microphone (MIC), which is configured to receive external audio signals when the electronic device is in an operating mode, such as a call mode, a recording mode, and a voice recognition mode. The received audio signal can be further stored in the memory 111 or transmitted via the communication component 113. In some embodiments, the audio component 115 also includes a speaker for outputting audio signals.

[0170] The display 116 includes a screen, which may include a liquid crystal display (LCD) and a touch panel (TP). If the screen includes a touch panel, the screen may be implemented as a touch screen to receive input signals from the user. The touch panel includes one or more touch sensors to sense touches, slides, and gestures on the touch panel. The touch sensor may not only sense the boundaries of a touch or slide action, but also detect the duration and pressure associated with the touch or slide operation.

[0171] In addition, an embodiment of the present disclosure further provides a computer-readable storage medium on which a computer program is stored. The computer program is executed by a processor to implement the method described in the above embodiment.

[0172] Exemplary embodiments of the present disclosure further provide a computer program product, including a computer program, wherein when the computer program is executed by a processor of a computer, the computer is configured to enable the computer to implement the method described in the above embodiment.

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

[0174] The foregoing description is intended only to provide specific embodiments of the present disclosure, intended to enable those skilled in the art to understand and implement the present disclosure. Various modifications to these embodiments will be readily apparent to those skilled in the art, and the general principles defined herein may be implemented in other embodiments without departing from the spirit or scope of the present disclosure. Therefore, the present disclosure is not intended to be limited to the embodiments described herein, but rather to be construed in the broadest manner consistent with the principles and novel features disclosed herein.

Claims

1. A cross-terminal payment processing method, wherein: The method is applicable to a cross-terminal payment system, which includes a first terminal, an intermediate page server, and a second terminal. The method includes: The first terminal sends a request for pulling up a payment page to the intermediate page server in response to an operation instruction for the object to be paid, wherein the request includes the first account information; The second terminal sends the second account information logged in by the second terminal to the intermediate page server; The intermediate page server compares the first account information and the second account information, and if the first account information and the second account information are consistent, the intermediate page server sends authorization information to the second terminal; The second terminal sends a cross-terminal payment request to a server corresponding to the payment application in the second terminal according to the authorization information, where the cross-terminal payment request is used to complete the cross-terminal payment for the object to be paid.

2. The method according to claim 1, wherein After the first terminal sends a request to pull up a payment page to the intermediate page server in response to an operation instruction for the object to be paid, the method further includes: The intermediate page server generates a session identifier corresponding to the first account information according to the pull request, and sends the session identifier to the first terminal; After obtaining the session identifier from the first terminal, the second terminal sends a cross-terminal login request for the first account to the intermediate page server, where the cross-terminal login request includes the session identifier.

3. The method according to claim 2, wherein: The second terminal sends the second account information logged in by the second terminal to the intermediate page server, including: If the second terminal fails to obtain the cross-terminal login status identifier generated by the intermediate page server locally, the second terminal determines that the cross-terminal login for the first account has failed; The second terminal obtains the second account information from the local payment application and sends the second account information to the intermediate page server.

4. The method according to claim 2, wherein: After the intermediate page server generates a session identifier corresponding to the first account information according to the pull request and sends the session identifier to the first terminal, the method further includes: The first terminal generates a QR code according to the session identifier, where the QR code includes the session identifier; The second terminal obtaining the session identifier from the first terminal includes: The second terminal obtains the session identifier by scanning the QR code displayed by the first terminal.

5. The method according to claim 2, wherein: After the second terminal obtains the session identifier from the first terminal and sends a cross-terminal login request for the first account to the intermediate page server, the method further includes: If the intermediate page server determines that the session identifier included in the cross-terminal login request is consistent with the session identifier corresponding to the first account information generated by the intermediate page server, the intermediate page server stores the record information of the second terminal's cross-terminal login to the first account and generates a cross-terminal login status identifier; The intermediate page server writes the cross-terminal login status identifier into a preset file of the second terminal; After obtaining the cross-terminal login status identifier from the preset file, the second terminal determines that the cross-terminal login for the first account is successful, and displays the payment page.

6. The method according to claim 1, wherein If the first account information and the second account information are consistent, after the intermediate page server sends authorization information to the second terminal, the method further includes: The second terminal displays an authorization page according to the authorization information, wherein the authorization page is used to prompt the user to authorize the payment application in the second terminal to log in to the first account; The second terminal displays the payment page in response to the authorization operation for the payment application to log in to the first account.

7. The method according to claim 1, wherein The method further comprises: If the first account information and the second account information are inconsistent, the intermediate page server sends a prompt message to the second terminal, where the prompt message is used to prompt the second terminal that the cross-terminal payment for the object to be paid cannot be completed; The second terminal displays the prompt information.

8. The method according to claim 1, wherein After the first terminal sends a request to pull up a payment page to the intermediate page server in response to an operation instruction for the object to be paid, the method further includes: The first terminal periodically sends a login status query request for the first account to the intermediate page server; The intermediate page server sends the current login status of the first account to the first terminal according to the login status query request; If the current login status indicates that the first account login is invalid, the first terminal prompts the user to log in to the first account again.

9. A cross-terminal payment processing method, wherein: The method comprises: The intermediate page server receives a request for opening a payment page sent by the first terminal, the request including the first account information, the request being sent by the first terminal in response to an operation instruction for an object to be paid; The intermediate page server receives the second account information sent by the second terminal for logging in by the second terminal; The intermediate page server compares the first account information and the second account information. If the first account information and the second account information are consistent, the intermediate page server sends authorization information to the second terminal. The authorization information is used to authorize the second terminal to complete the cross-terminal payment for the object to be paid.

10. A cross-terminal payment system, wherein: The cross-terminal payment system includes a first terminal, an intermediate page server, and a second terminal; The first terminal is configured to send a request to the intermediate page server to pull up a payment page in response to an operation instruction for the object to be paid, wherein the request includes first account information; The second terminal is used to send the second account information logged in by the second terminal to the intermediate page server; The intermediate page server is used to compare the first account information and the second account information. If the first account information and the second account information are consistent, the intermediate page server sends authorization information to the second terminal; The second terminal is further configured to send a cross-end payment request to a server corresponding to a payment application in the second terminal according to the authorization information, wherein the cross-end payment request is configured to complete the cross-end payment for the object to be paid.

11. A cross-terminal payment processing device, wherein: The device comprises: a receiving module configured to receive a request from a first terminal to launch a payment page, the request including first account information, the request being sent by the first terminal in response to an operation instruction for an object to be paid; and receive second account information from a second terminal for login by the second terminal; a comparison module, configured to compare the first account information with the second account information; The sending module is used to send authorization information to the second terminal when the first account information and the second account information are consistent, and the authorization information is used to authorize the second terminal to complete the cross-terminal payment for the object to be paid.

12. An electronic device, wherein: include: Memory; processor; as well as computer programs; The computer program is stored in the memory and configured to be executed by the processor to implement the method according to any one of claims 1 to 9.

13. A computer-readable storage medium having a computer program stored thereon, wherein: When the computer program is executed by a processor, the method according to any one of claims 1 to 9 is implemented.

Images