A member payment method, device, equipment and medium

Abstract

The embodiments of the present specification disclose a member payment method, device, equipment and medium. The scheme can include: a first device obtains the tag information of the NFC tag of a second device through near field communication; the tag information contains information for triggering a member login process and information for triggering a payment business processing process; at least part of the information in the tag information is sent to a server; the server executes a payment processing process according to a member payment link in the case of determining that the user of the first device is a member; payment result information fed back by the server is obtained, and a payment result page is displayed.

Description

[0001] This application is a divisional application of "A method, apparatus, device and medium for displaying a member login page (application date: August 5, 2024, application number: 202411069785.8)". Technical Field

[0002] This application relates to the field of computer technology, and in particular to a method, apparatus, device, and medium for displaying a member login page. Background Technology

[0003] To better serve users, more and more businesses are adopting membership mechanisms. For example, merchants offer members various benefits or promotional activities; and some service providers offer members richer reading, video, and audio information.

[0004] Providing a more convenient way for members to log in is a technical problem that urgently needs to be solved. Summary of the Invention

[0005] This specification provides a method, apparatus, device, and medium for displaying a member login page, to solve the problem of cumbersome operation in existing member login methods.

[0006] To solve the above-mentioned technical problems, the embodiments in this specification are implemented as follows:

[0007] This specification provides an embodiment of a method for displaying a member login page, comprising:

[0008] The first device acquires the tag information of the NFC tag of the second device via near-field communication; the tag information includes first information for activating the target application and second information for executing the member login process;

[0009] Based on the first information, the target application in the first device is invoked;

[0010] Based on the second information, the target application sends a page information retrieval request to the server.

[0011] Obtain the member login page information returned by the server and display the member login page.

[0012] This specification provides an embodiment of a method for displaying a member login page, comprising:

[0013] The system obtains a page information retrieval request sent by a first device; the page information retrieval request is generated by the first device obtaining tag information of the NFC tag of a second device through near-field communication; the tag information includes first information for waking up the target application and second information for executing the member login process;

[0014] Based on the page information retrieval request, member login page information is sent to the first device so that the first device can display the member login page.

[0015] This specification provides an embodiment of a device for displaying a member login page, comprising:

[0016] The information acquisition module is used to acquire tag information of the NFC tag of the second device through near-field communication; the tag information includes first information for waking up the target application and second information for triggering the member login process;

[0017] An application invocation module is used to invoke the target application in the first device based on the first information;

[0018] The request sending module is used to send a page information retrieval request to the server using the target application based on the second information.

[0019] The page display module is used to obtain the member login page information returned by the server and display the member login page.

[0020] This specification provides an embodiment of a device for displaying a member login page, comprising:

[0021] The request acquisition module is used to acquire a page information acquisition request sent by the first device; the page information acquisition request is generated by the first device acquiring the tag information of the NFC tag of the second device through near field communication; the tag information includes first information for waking up the target application and second information for executing the member login process;

[0022] The page information sending module is used to send member login page information to the first device based on the page information acquisition request, so that the first device can display the member login page.

[0023] This specification provides an embodiment of a device for displaying a member login page, comprising:

[0024] At least one processor; and,

[0025] A memory communicatively connected to the at least one processor; wherein,

[0026] The memory stores instructions that can be executed by the at least one processor to enable the at least one processor to perform a method for displaying a member login page.

[0027] This specification provides an embodiment of a computer-readable medium storing computer-readable instructions that can be executed by a processor to implement a method for displaying a member login page.

[0028] One embodiment of this specification achieves the following beneficial effects: the first device obtains the tag information of the NFC tag of the second device through near field communication, and displays the member login page using the first information and the second information in the tag information. In this way, the user can display the member login page by bringing the first device close to the second device, making it more convenient for the user to log in as a member. Attached Figure Description

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

[0030] Figure 1 This is a schematic diagram illustrating an application scenario of a method for displaying a member login page as described in the embodiments of this specification.

[0031] Figure 2 A flowchart illustrating a method for displaying a member login page, provided as an embodiment of this specification;

[0032] Figure 3 This is a swimlane diagram of a method for displaying a member login page provided in the embodiments of this specification;

[0033] Figure 4 This is a schematic diagram of a member authorization login page provided in the embodiments of this specification;

[0034] Figure 5 This is a schematic diagram of a member login results page provided in the embodiments of this specification;

[0035] Figure 6 This is a schematic diagram of another member login result page provided in the embodiments of this specification;

[0036] Figure 7 This is a schematic diagram of another member authorization login page provided in the embodiments of this specification;

[0037] Figure 8 This is a schematic diagram of a payment result page provided in an embodiment of this specification;

[0038] Figure 9 This is a schematic diagram of a payment confirmation page provided in the embodiments of this specification;

[0039] Figure 10 This is a schematic diagram of a login response page provided in the embodiments of this specification;

[0040] Figure 11 This is a schematic diagram of a member notification page provided in the embodiments of this specification;

[0041] Figure 12 This is a schematic diagram of a payment response page provided in the embodiments of this specification;

[0042] Figure 13 A flowchart illustrating a method for displaying a member login page, provided as an embodiment of this specification;

[0043] Figure 14 The embodiments provided in this specification correspond to Figure 2 A schematic diagram of the structure of a device for displaying a member login page;

[0044] Figure 15 The embodiments provided in this specification correspond to Figure 13 A schematic diagram of the structure of a device for displaying a member login page;

[0045] Figure 16 This is a schematic diagram of the structure of a device for displaying a member login page, provided as an embodiment of this specification. Detailed Implementation

[0046] To make the objectives, technical solutions, and advantages of one or more embodiments of this specification clearer, the technical solutions of one or more embodiments of this specification will be clearly and completely described below in conjunction with specific embodiments and corresponding drawings. Obviously, the described embodiments are only a part of the embodiments of this specification, and not all of them. Based on the embodiments in this specification, all other embodiments obtained by those skilled in the art without creative effort are within the protection scope of one or more embodiments of this specification.

[0047] The technical solutions provided in the various embodiments of this specification are described in detail below with reference to the accompanying drawings.

[0048] In related technologies, if a user wants to log in or activate a membership, one method requires the user to first find the corresponding webpage, client, or mini-program, then locate the membership entry point, and enter verification information such as account and password before logging in. Another method involves the user scanning a membership code provided by the merchant using the scanning capability of certain mobile clients. Both methods require the user to first find the webpage, client, or mini-program, or open the corresponding client to scan the code to access the membership login page, making the process rather cumbersome.

[0049] To address the shortcomings of existing technologies, this solution provides the following embodiments:

[0050] Figure 1 This is a schematic diagram illustrating an application scenario of a method for displaying a member login page, as described in an embodiment of this specification. Figure 1 As shown, this solution may include a first device 1, a second device 2, and a server 3. The first device 1 can acquire NFC tag information by bringing the NFC tag of the second device 2 close together, such as by sticking it together or tapping it against the device. The first device 1 can then use this tag information to activate a target application within the first device and display the member login page information obtained from the server 3 within the target application.

[0051] Next, a method for displaying a member login page provided in the embodiments of the specification will be described in detail with reference to the accompanying drawings:

[0052] Figure 2 This is a flowchart illustrating a method for displaying a member login page, provided in an embodiment of this specification. From a program perspective, the entity executing the process can be a program or application client mounted on a first device. From a hardware perspective, the entity executing the process can be a first device with near-field communication (NFC) functionality. The first device can be a mobile phone, smartwatch, smart bracelet, portable computer, wearable smart device, etc., or other mobile terminals; the specific type of device is not limited here.

[0053] like Figure 2 As shown, the process may include the following steps:

[0054] Step 202: The first device obtains the tag information of the NFC tag of the second device through near field communication.

[0055] The tag information includes first information for activating the target application and second information for triggering the member login process. The second device can be a device associated with the NFC tag; for example, the NFC tag can be located on the second device or connected separately via wired or wireless means. The first device has NFC near-field communication capabilities and can act as an NFC reader to obtain the tag information of the NFC tag on the second device. An NFC tag, also known as an NFC card, includes components such as an NFC chip and a coil.

[0056] In this manual, the first device can function as a card reader. When the NFC switch is turned on, it sends signals in LPCD (Low Power Card Detection) mode, or a combination of LPCD mode and normal card detection. When the first device is brought close to the NFC tag, such as by tapping or sticking it against the second device, the tag coil in the NFC tag will affect the LPCD signal of the first device, either in amplitude or phase. The first device can determine the presence of a tag based on this effect and then initiate an inquiry, entering the interaction process. This can be either command interaction or data interaction; for example, the first device can retrieve information from the NFC tag. For details on the specific NFC interaction process, please refer to relevant technologies; they will not be elaborated here.

[0057] The first and second information can be characters or strings in a preset format, such as link information, like URLs starting with http or https (Universal Resource Locator), or other forms of characters or strings that can be recognized by the first device. The first and second information can be information from the same string, or they can be separate characters or strings, without specific limitations.

[0058] Step 204: Based on the first information, activate the target application in the first device.

[0059] The first piece of information is used to launch the target application. Specifically, it can be an identifier representing the target application, such as the application's package name, package signature, etc., or other information agreed upon with the first device. The first device can launch the target application based on this identifier. The target application can be an application client (APP), a mini-program, a system application, etc. In practical applications, the first device's OS (Opening System) can launch the corresponding target application based on the application package name.

[0060] Step 206: Based on the second information, use the target application to send a page information retrieval request to the server.

[0061] The second information is used to trigger the member login process. The operating system of the first device can provide the second information to the target application, which can then trigger the member login process based on this information. This can be understood as the target application's client application executing a process related to member login based on the second information. As one implementation, the second information may include page redirection information, such as URL information. After the first device launches the target application, the target application can send a page information retrieval request to the server based on this second information, and can also receive feedback information from the server.

[0062] Step 208: Obtain the member login page information returned by the server and display the member login page.

[0063] The server is a server that can provide services to the target application. The server can determine the corresponding member login page information based on the page information retrieval request sent by the target application and then send it back to the target application.

[0064] In practical applications, different merchants or members can provide service providers with member login pages that meet their business needs. Optionally, the second information can include the identification information of the member's service provider, such as the identification information of the merchant served by the second device. The server can use this identification information to set the corresponding member login page information, and the corresponding member login page can be displayed on the first device.

[0065] It should be understood that the order of some steps in the methods described in one or more embodiments of this specification may be interchanged according to actual needs, or some steps may be omitted or deleted. For example, if the operating system of the first device can recognize and respond to the member login process represented by the second information, the target application in the first device may not need to be invoked.

[0066] Figure 2 The method described above involves the first device acquiring the tag information of the second device's NFC tag via near-field communication. Using the first and second information from the tag information, a member login page can be displayed. This allows users to display the member login page simply by bringing the first device close to the second device, making it more convenient for users to log in as members.

[0067] In the embodiments described in this specification, the member login page can be a single page or multiple related pages. As one implementation, if the user of the first device is already a member of the member service provider, the first device can display a login result page after obtaining the NFC tag information. If the user is not yet a member of the member service provider, a member authorization login page can be displayed to prompt the user to authorize membership. This allows the user to be confirmed as a member after authorization is obtained. Based on the user's authorization and the first device or server storing the relevant member information, if the user logs in again by tapping the first device against the second device, the first device may not display the member authorization login page and can directly display the member login result page.

[0068] To more clearly illustrate the method for displaying member login page information provided in the embodiments of this specification, Figure 3 This is a swimlane diagram of a method for displaying a member login page provided in the embodiments of this specification, such as... Figure 3 As shown, the method may include the following steps.

[0069] Step 302: The second device has an NFC tag containing tag information.

[0070] In practical applications, the second device can be a device used by the member service provider, or a device connected to the member service provider's management system. The member service provider can program tag information into the NFC tag of the second device according to actual business needs. For example, tag information can be programmed into the NFC tag through the second device. The member service provider can be an entity providing membership services, such as merchants offering membership services like supermarkets, shopping malls, bookstores, restaurants, hospitals, social service organizations, etc., or non-profit or non-profit organizations, such as book clubs, sports meets, etc.

[0071] Step 304: The first device obtains the tag information of the NFC tag of the second device through near field communication.

[0072] The tag information may include first information for activating the target application and second information for triggering the member login process.

[0073] Step 306: Based on the first information, activate the target application in the first device.

[0074] Step 308: Based on the second information, use the target application to send a page information retrieval request to the server.

[0075] In practical applications, different service providers can correspond to different member login pages. Optionally, as one implementation method, the above-mentioned method, based on the second information, uses the target application to send a page information retrieval request to the server, which may specifically include:

[0076] Obtain the scene parameter information from the second information;

[0077] Based on the scene parameter information, a page information retrieval request is generated;

[0078] Send the request to obtain the page information to the server.

[0079] The scenario parameter information can represent parameter information related to the member login scenario. Specifically, it can include at least one of the following: the identifier information of the target object providing the member service, the identifier information of the second device, and the business identifier information representing the member login business being processed. The scenario parameter information can also include token information generated using a token mechanism, etc. The page information retrieval request can include the scenario parameter information, or it can include the identifier information corresponding to the scenario parameter information, so that the server can execute the corresponding member login process based on the parameter information contained in the page information retrieval request.

[0080] Step 310: The server obtains the page information retrieval request sent by the first device.

[0081] The page information retrieval request is a request for the server to provide relevant information about member login.

[0082] Step 312: Based on the page information acquisition request, send member login page information to the first device.

[0083] Step 314: The first device obtains the member login page information fed back by the server and displays the member login page.

[0084] In practical applications, the server can also provide different page information for users with different statuses. For example, if a user has not registered or authorized registration as a member of the target object corresponding to the second device via NFC communication, the server can provide a page prompting the user to register or authorize membership. If the user is already a member of the target object or has previously authorized membership via NFC communication, meaning the server has a record of the user as a member, there is no need to provide a page prompting the user to register or authorize membership again. Instead, the login result page can be sent to the first device so that the user knows whether they have logged in as a member.

[0085] As one implementation, the page information retrieval request may include user identification information of the first device, such as device identification information of the first device, or user identification information of the user on the first device or in the target application, such as UID (User Identification), mobile phone number, email address, application account, social media account, etc. Before sending the member login page information to the first device, the server may also perform step 3122: based on the user identification information, determine whether the user of the first device is a member of the target object, and obtain a determination result.

[0086] Optionally, if the determination result indicates that the user is not a member of the target object, the server may also execute step 3124: send member authorization login page information to the first device.

[0087] Correspondingly, step 314 of the first device described above, which involves obtaining the member login page information fed back by the server and displaying the member login page, may further include step 3142: obtaining the member authorization login page information fed back by the server and displaying the member authorization login page.

[0088] The member authorization login page information is the page information returned by the server after determining that the user of the first device is not a member of the target object.

[0089] The member login page may include at least one of the following: the identification information of the target object corresponding to the member login page, the information indicating the content that the user needs to authorize, the control indicating confirmation of member login, the control indicating exit from member login, the control indicating payment via member method, and the control indicating payment via non-member method.

[0090] Figure 4 This is a schematic diagram of a member authorization login page provided in an embodiment of this specification. Figure 4 As shown, the member authorization login page may include information 402 indicating the content that the user needs to authorize, and the user can also view the specific authorization agreement content. It may also include a control 404 indicating confirmation of member login. If the user clicks this control, the target application can use the user's mobile phone number and other information to register the user as a member of the target object. For example, the target application can send a member registration request containing user information to a server or system used to manage member information. This server or system can record the user's information and the member benefits enjoyed by the user. The server used to manage member information may be the same server as the server in the embodiments of this specification, or it may be a different server.

[0091] like Figure 4 As shown, the member authorization login page may also include a control 406 indicating that the user does not agree to log in or register as a member. If the user clicks this control, it indicates that the user does not agree to log in or register as a member, and the first device can terminate the member login process and exit the member authorization login page. The member authorization login page may also include the identification information of the target object 408, etc.

[0092] Optionally, the method in the embodiments of this specification may further include step 3146: the first device obtains the user's first operation on the member authorization login page and sends a member login request to the server.

[0093] The first operation is an operation that indicates the user's consent to become a member of the target object. Specifically, it can be the first operation of the first control on the member authorization login page, or it can be an operation executed according to a preset operation instruction. It can be a substantive operation or a non-substantive operation of the inaction type. For example, if the user does not perform an operation indicating the cancellation of authorization login or registration while displaying a countdown prompt, it can indicate that the user agrees to authorize login or registration as a member.

[0094] Correspondingly, the server can execute step 3126: obtain the member login request sent by the first device.

[0095] The member login request is generated by the first device based on the user's first operation on the first control of the member authorization login page. The server can execute a member registration or login process based on the member login request sent by the first device, recording the user as a member of the target object or a member in a logged-in state.

[0096] Step 3128: Send member login result information to the first device.

[0097] The server can generate member login result information based on the user's login result and send it back to the first device. In practical applications, the server can interact with the member service provider's device or system to complete user login or registration. For example, the obtained user information can be provided to the member service provider's device or system so that the member service provider can mark the user as a member. Alternatively, the server can complete member registration or login independently. The specific member registration or login process is not detailed here; please refer to the relevant implementation methods.

[0098] Correspondingly, the first device can also perform step 3148: obtain the member login result information fed back by the server and display the member login result page.

[0099] As one implementation, if the judgment result indicates that the user is a member of the target object, that is, after determining that the user is already a member user, the server can send member login result information to the first device. The sending of member login page information to the first device in step 312 above can specifically include step 3128 above: sending member login result information to the first device.

[0100] Correspondingly, step 314, performed by the first device, which involves obtaining the member login page information returned by the server and displaying the member login page, can specifically include step 3148: obtaining the member login result information returned by the server and displaying the member login result page. The member login result information is the page information returned by the server after determining that the user of the first device is a member of the target object.

[0101] Figure 5 This is a schematic diagram of a member login results page provided in an embodiment of this specification. Figure 5 As shown, this page can include information 502 indicating the member's login result. In practical applications, if the login is successful, the login result page can display information indicating successful login, such as "Login successful"; if the login fails, it can display information indicating login failure, such as "Login failed," or information indicating the reason for the login failure, such as "Login timeout"; if the login fails, it can also display information prompting the user to log in again, etc.

[0102] like Figure 5 As shown, this page can also include information about the service provider (e.g., the merchant's name, logo, etc.), as well as identification information for the target application. It can also include identification information for near-field communication (NFC), such as the "NFC" designation.

[0103] In practical applications, users can exit the login results page automatically, such as... Figure 5 The countdown message "2 seconds" shown can automatically exit the login results page after the countdown ends. Alternatively, it can exit based on user interaction; for example, the login results page can include controls that allow the user to exit the page or navigate to another page.

[0104] Figure 6 This is a schematic diagram of another member login result page provided in the embodiments of this specification. Figure 6 As shown, the page may include information 602 indicating the member login result. It may also include a control 604 for accessing the member service page and a control 606 for exiting the current page. If the user clicks control 604, the first device can be redirected from this page to the member service page, which may contain member service information such as coupons, user points, and user membership level. If the user clicks control 606, they can exit the member login result page.

[0105] In practical applications, some merchants offering membership services can also use membership payment for transactions. Users who use membership payment can enjoy certain membership benefits, such as discounted member prices, coupons, and member points. The membership login method provided in the embodiments of this specification can also be applied to payment application scenarios.

[0106] Figure 7 This is a schematic diagram of another member authorization login page provided in the embodiments of this specification. Figure 7 As shown, the member authorization login page may include a control 702 indicating agreement to register as a member and pay using the member payment method. If a user interacts with this control, it indicates that the user agrees to register as a member and agrees to make payments, allowing the user to enjoy the benefits of member payments. A single interaction with control 702 can trigger both the member registration and login process and the payment processing flow.

[0107] like Figure 7As shown, the member authorization login page can also include a control 704 indicating payment via a non-member method. If the user interacts with this control, it indicates that the user has not authorized membership registration but agrees to make the payment, which can trigger the payment processing flow. In practical applications, the member authorization login page can also include a control indicating exiting the member login results page, or a control indicating that the user cancels or disagrees with member login.

[0108] It is understood that the above is just a page example, and the specific page content can be set according to actual needs. No specific restrictions are made here.

[0109] Optional, such as Figure 3 As shown, the method in the embodiments of this specification may further include step 316: sending a payment trigger request to the server.

[0110] The payment trigger request can be generated by the first device based on a user's preset action on the member login results page. This preset action can represent the user making a payment, agreeing to pay using a non-member method, or agreeing to pay using a member method. (As mentioned above...) Figure 7 In the member authorization login page shown, regardless of whether the user operates on control 702, which indicates agreement to register as a member and pay using the member method, or on control 704, which indicates payment using the non-member method, the first device can send a payment processing request to the server.

[0111] Optionally, the server can also perform step 318: obtain a payment trigger request and execute the payment processing flow.

[0112] Step 320 can also be performed: send payment result information to the first device.

[0113] The server contains a program that processes user payment requests. Upon receiving a payment trigger request from the first device, it can execute the corresponding payment processing flow. For example, the payment trigger request may contain information about both parties to the transaction and the quantity of resources to be traded. Based on this request, the server can transfer the payer's resources to the payee's account. Alternatively, the server can send the first device's user information to the counterparty's system or device so that the counterparty can generate order information and send it to the server. The server can then process the payment transaction between the first device and the counterparty based on the order information provided by the counterparty.

[0114] The transaction result information can be the result obtained by the server processing the payment transaction, and can indicate either a successful transaction or a failed transaction. The specific process of the server processing the payment transaction can be found in relevant technical documents, and will not be elaborated upon here.

[0115] Correspondingly, the first device can also perform step 322: display the payment result page.

[0116] The first device can obtain the payment result information fed back by the server; based on the payment result information, it displays a payment result page. The payment result page may contain the payment result information fed back by the server.

[0117] Figure 8 This is a schematic diagram of a payment result page provided as an embodiment of this specification. Figure 8 As shown, Figure 8 As shown, the transaction results page can include payment result information 802, such as payment success or payment failure, and payment information 804, such as payment amount, payment method, transacting party, and promotional information; it can also include controls 806 for closing the transaction results page, such as a "Complete" control. In practical applications, the specific content and format of the transaction results page can be set according to actual needs, and no specific limitations are made here.

[0118] The second information in the tag information of the embodiments of this specification may include information for triggering the member login process, or information for triggering the payment business processing process. For example, it may contain some preset characters. The first device may send at least part of the information in the tag information to the server. The server may trigger the payment business processing process based on some preset characters when determining whether the user is a member or not.

[0119] As one implementation, the first operation of the user on the member authorization login page obtained by the first device can also represent the user making a payment through a member payment method. Optionally, the first device can also perform the following steps:

[0120] A first payment trigger request is sent to the server so that the server can execute the corresponding payment processing procedure.

[0121] The first payment trigger request can represent a payment trigger request for making payment using the member payment method, and the server can process the request according to the member payment link.

[0122] In practical applications, to simplify user operations, the first payment trigger request can also be generated based on the user's first action on the member authorization login page. That is, a user performing a first action can trigger member registration and login, or it can trigger the payment process. The first device can send a member login request to the server based on the first action, or it can send a first payment trigger request to the server. These two requests can also be sent to the server as a single request, or they can be sent to the server separately.

[0123] Correspondingly, the server can also perform processing steps for the first payment trigger request. Optionally, the first device can also perform the following steps:

[0124] Obtain the first payment trigger request sent by the first device;

[0125] Based on the first payment trigger request, the user's first transaction information is sent to the payment system of the counterparty to the first device; so that the payment system can process the payment transaction for the user based on the first transaction information; the first transaction information includes transaction identification information representing the user's transaction account information and the user's membership information.

[0126] In this context, the payment system can refer to the system used by the other party in a transaction with the first device to manage payment operations. It can also be understood as the counterparty's payment system, also known as a POS system, such as a merchant's cash register. Alternatively, it can be a payment device connected to the merchant's POS system, such as a second device. The payment system can send a payment request to the server based on the acquired transaction information. The server processes the payment and can also send the transaction result back to both parties. Examples of POS systems in supermarkets and shopping malls include cash registers, POS machines, and self-service payment devices. The POS system can determine the user's payment account based on transaction identification information. If the POS system is used for receiving payments, the user's payment account can represent the payment account; if it is used for making payments, the user's payment account can represent the receiving account. The POS system can also correspond to a transaction account. Based on the acquired user's payment account and the corresponding transaction account, the POS system can generate a transaction request and send it to the server. The server can process the transaction request, for example, deducting resources from the user's payment account and adding them to the corresponding transaction account. After processing, the server can send the payment result information back to the first device. For specific transaction processing procedures, please refer to the relevant technical documentation. The POS system can also process transactions according to the existing processing procedures, which will not be elaborated here.

[0127] In practical applications, the server can directly send the first transaction information to the payment system of the counterparty to the first device, or it can send the first transaction information to the payment system through a second device. The second device can send the first transaction information to the payment system via wired or wireless means. If the payment system can also read NFC information, the second device can also burn the acquired first transaction information into an NFC tag, which can then be read by the payment system using the NFC reading function.

[0128] Transaction identification information can be used to identify the user's transaction account in the first device. If the tag information contained in the NFC tag indicates a payment process, the account can be a payment account; if the tag information contained in the NFC tag indicates a payment process for receiving payment, the account can be a receiving account. No specific limitations are made here. In practical applications, the target application can be a terminal application with payment functionality, and the user's transaction account can be the user account logged into that terminal application.

[0129] In practical applications, transaction identification information can be generated by the server based on the payment trigger request sent by the first device. The first device can request the server to generate transaction identification information according to actual transaction needs. The transaction identification information can be different in different payment processes.

[0130] In one implementation, the first device can send a payment trigger request containing user identification information of the first device to the server; the server can generate transaction identification information for the user of the first device based on the obtained user identification information.

[0131] The user identification information can be a user ID, or it can be a device identifier for the mobile terminal, a user application identifier in the terminal application, or other identification information that can be used to determine the user's transaction account. The server can determine the user's transaction account based on the user identification information and generate transaction identification information that corresponds to that user's transaction account, so that payment transactions can be processed using that user's transaction account in the future based on the transaction identification information.

[0132] In practical applications, transaction identification information can also include strings representing payment codes, transaction order numbers, etc. The server can process transactions between the two parties based on this transaction identification information. Specifically, the transaction identification information can be a string that the server processing the payment transaction can recognize, and it must conform to the payment application's payment rules. For example, it can be a string starting with 28, or a string starting with 25, 30, etc. The string length can be 16 to 24 characters, or other lengths as required. The specific form of the string is not specifically limited here. The relevant content of the transaction identification information can also be found in the descriptions in the foregoing embodiments.

[0133] A user's membership information may include user information used during registration, such as mobile phone number and name, or membership identification information generated by the server for the member, such as membership card number and member user ID. For details, please refer to relevant technologies, which will not be specifically limited or elaborated here.

[0134] In this embodiment of the specification, after determining that the user is using the membership payment method, the server sends the transaction identifier information and membership information of the first device user to the payment system. The transaction identifier information and membership information can be sent to the payment system in one message, or they can be sent to the payment system separately.

[0135] The member authorization login page in this embodiment may include a control indicating payment via a non-member method. Optionally, the first device in this embodiment may also perform the following steps:

[0136] The system obtains a second operation performed by the user on the second control of the member authorization login page; the second operation is an operation indicating that the user agrees to use a non-member payment method for payment.

[0137] A second payment trigger request is sent to the server so that the server can execute the corresponding payment processing procedure.

[0138] The second payment trigger request can represent a payment trigger request for making a payment using a non-member payment method. The server can process this request according to the non-member payment link.

[0139] Correspondingly, the server can also perform the following steps:

[0140] The first device receives a second payment trigger request; the second payment trigger request is generated by the first device based on a second operation performed by the user on a second control of the member authorization login page; the second operation is an operation indicating that the user agrees to make payment using a non-member payment method.

[0141] Based on the second payment trigger request, the user's second transaction information is sent to the payment system associated with the second device; so that the payment system can process the payment transaction for the user based on the second transaction information; the second transaction information includes transaction identifier information for representing the user's transaction account information.

[0142] The transaction identification information and payment system can be found in the previous embodiments. The specific process of sending the second transaction information to the payment system in this embodiment can be found in the previous embodiments of sending the first transaction information to the payment system, and will not be repeated here.

[0143] If a user does not agree to register as a member or chooses a non-member payment method, the server does not need to send the user's membership information to the payment system. Instead, it can send the transaction identifier information, which represents the user's transaction account information, to the payment system.

[0144] The server can process payment transactions based on requests from the payment system and provide payment result information. Optionally, in the embodiments of this specification, the server may perform the following steps:

[0145] Obtain the payment processing request generated by the payment system based on the transaction identifier information;

[0146] The payment process is executed based on the payment processing request to obtain payment result information;

[0147] The payment result information is sent to the first device.

[0148] The payment result information can indicate either payment failure or payment success. For details on the payment process, please refer to relevant technical documentation; it will not be elaborated upon here. The server can also send the payment result information back to the payment system, such as a POS machine or a merchant's cash register, which have display capabilities.

[0149] In practical applications, if the tag information obtained by the first device includes information about the counterparty or the transaction amount, the first device can send a payment request containing information about both parties to the transaction to the server. The server can then process the transaction based on the payment request sent by the first device. The information about both parties can include their account information or identification information, the transaction amount, the type of product, or the specific product name. In this way, the server can execute the transaction processing flow based on the necessary information required for the transaction, obtain the payment result, and then send the result back to both parties. This eliminates the need for the server to send the user transaction identification information from the first device to the business system or to generate transaction identification information, simplifying the payment processing flow and improving payment efficiency.

[0150] In practical applications, to improve payment security, before executing the resource transfer steps between the transacting parties, the server can send transaction information to the first device. This allows the server to execute the resource transfer steps after the first device automatically confirms the transaction based on user authorization or after manual confirmation by the user. Optionally, in the embodiments of this specification, the server can also perform the following steps:

[0151] Send payment link information to the first device; the payment link information includes identification information indicating payment information to be confirmed;

[0152] The server obtains payment confirmation information provided by the first device so that it can execute the corresponding payment processing procedure after receiving the payment confirmation information.

[0153] Optionally, the corresponding first device may perform the following steps:

[0154] Obtain payment link information provided by the server; the payment link information includes identification information indicating payment information to be confirmed;

[0155] Based on the payment link information, a payment confirmation message is sent to the server so that the server can execute the corresponding payment processing procedure after receiving the payment confirmation message.

[0156] The payment information to be confirmed may include the amount to be paid, information about the counterparty, etc. The payment link information may contain a string representing the payment information to be confirmed or a string obtained by processing the payment information to be confirmed according to preset rules. As one implementation method, the payment link information may be in URL format or other string formats recognizable by the first device. In practical applications, the target application in the first device can send payment confirmation information to the server based on the payment link information. If, with user authorization, the user does not need to confirm, the server may not need to send the payment link information to the first device.

[0157] As one implementation, after obtaining the payment link information, the first device can also display a payment confirmation page so that the user can manually confirm the information to be paid. Optionally, in the embodiments of this specification, the first device can also perform the following steps:

[0158] Based on the payment link information, a payment confirmation page is displayed; the payment confirmation page contains payment information to be confirmed.

[0159] Based on the user's fourth action on the payment confirmation page, payment confirmation information is sent to the server.

[0160] The payment confirmation information is sent by the first device based on the user's fourth action on the payment confirmation page displayed based on the payment link information.

[0161] Figure 9 This is a schematic diagram of a payment confirmation page provided in the embodiments of this specification, such as... Figure 9 As shown, the payment confirmation page may include an area 902 for displaying payment information, specifically the payment amount, payment method, transacting party, transaction time, etc. The payment page may also include an operation control 904. If the user clicks this control, it indicates that the user agrees to the payment, and the mobile terminal can generate a confirmation message. In practical applications, the operation control can be used for payment confirmation or for canceling payment. If the user does not click the control to cancel payment within a preset time period, it also indicates that the user agrees to the payment, and the mobile terminal can generate a confirmation message for subsequent processes. Figure 9As shown, the payment confirmation page may also include descriptive information 906 for NFC payments, which helps users understand the advantages or usage of NFC payments.

[0162] In practical applications, the payment amount information contained on the payment confirmation page can be the transaction amount determined by the merchant using the second device based on the actual transaction, or it can be the amount entered by the user of the first device. For example, it can be entered on the payment confirmation page, or it can be entered on the page where the user enters the amount that was displayed before the payment confirmation page.

[0163] The fourth step can represent the user confirming the payment. This can be a substantive action or a non-substantive action, such as the user confirming payment. Figure 9 The confirmation control shown, or the control indicating cancellation of payment if not clicked within a preset time, can both indicate that the user has confirmed the payment operation.

[0164] The operations described in the embodiments of this specification can refer to operations performed by the user's limbs, or operations performed based on voice, eye movements, etc. No specific limitations are made here regarding the specific type of operation.

[0165] In practical applications, to improve payment efficiency, the first device may not display a payment confirmation page if certain preset conditions are met, such as a secure payment environment or user authorization for the first device or server to confirm payment information. Optionally, in the embodiments of this specification, the first device may also perform the following steps:

[0166] Determine whether the user of the first device meets the preset payment conditions; the preset payment conditions refer to the conditions under which fast payment can be made.

[0167] If the user meets the preset payment conditions, the first device may not display the payment confirmation page; if the user does not meet the preset payment conditions, the first device will display the payment confirmation page.

[0168] The aforementioned payment confirmation page may specifically include: displaying the payment confirmation page if the user does not meet the preset payment conditions.

[0169] The aforementioned payment result page may specifically include: displaying the payment result page if the user meets the preset payment conditions. That is, the payment confirmation page may not be displayed before the payment result page.

[0170] As one implementation method, the preset payment conditions may include at least one of the following: authorized use of the express payment function, the user being a highly active user of the target application, and authorized use of the password-free payment function.

[0171] The "Instant Payment" function refers to a payment method that eliminates the need for confirmation. For example, it avoids displaying the payment confirmation page or other pages requiring user confirmation before the transaction results page, thus minimizing or eliminating the need for user confirmation and providing an extremely fast payment method. In practice, users can enable the Instant Payment function in the relevant settings page of the target application. If the user has already authorized the use of the Instant Payment function and meets the preset payment conditions, the payment confirmation page will not be displayed when the user makes a payment via NFC.

[0172] Highly active users can be defined as users whose activity level in using payment applications is greater than or equal to a preset threshold. In practical applications, user activity can be calculated based on factors such as the duration and frequency of a user's login to the payment application. Alternatively, user activity can be determined based on the frequency with which a user uses the payment application to scan a QR code or enter a payment code. For highly active users, a fast payment processing flow can be provided, such as not displaying the payment page.

[0173] In practical applications, for highly active users, the express payment function in their payment application can be enabled by default, or the corresponding payment process can be provided to the user based on the status of the express payment function.

[0174] Password-free payment means that payment can be made without entering a password. Payment can be made using biometric features such as fingerprints, faces, voiceprints, and irises as verification information. Alternatively, the server can be authorized to automatically execute the payment when processing transactions for users, without requiring users to enter a password or biometric information for verification.

[0175] Considering practical applications, after obtaining the NFC tag information, the first device needs to parse the tag information before activating the target application and displaying the member login page. Before displaying the member login page, the first device needs to perform some processes. To improve user experience, the first device can also display a transition page after obtaining the NFC tag information. Optionally, in the embodiments of this specification, before displaying the member login result page, the first device can also perform the following steps:

[0176] The login response page is displayed; the login response page contains a prompt message indicating that the login process is in progress.

[0177] Figure 10 This is a schematic diagram of a login response page provided in an embodiment of this specification. Figure 10 As shown, the login response page can include a login message (1002). In practical applications, the login response page can also include information such as the target application identifier and merchant identifier. The login response page can be generated locally on the first device or based on information returned by the server.

[0178] In one implementation, the server may also send login response page information to the first device so that the first device displays the login response page.

[0179] After the server receives the member login request sent by the first device, it can first send the login response page information to the first device. After the login process is completed, the login result information will be sent to the first device.

[0180] To ensure the security of user information, the first device may also perform the following steps before activating the target application on the first device:

[0181] A member notification page is displayed; the member notification page contains information prompting the user to log in as a member or information prompting the user to make payments through the member;

[0182] The aforementioned invocation of the target application in the first device may specifically include:

[0183] The system obtains a second action performed by the user on the member notification page; the second action indicates agreement to use the target application.

[0184] Based on the second operation, the target application in the first device is invoked.

[0185] Figure 11 This is a schematic diagram of a member notification page provided in an embodiment of this specification. Figure 11 As shown, this page may include information prompting the user to log in as a member (1102), such as "Click to Log In as a Member". The prompts on this page may also include information prompting the user to make payments through their membership, such as "Click to Pay as a Member".

[0186] like Figure 11 As shown, the member prompt page may also include an operation control 1104. If the user agrees to log in as a member using the target application by interacting with this control, the first device can launch the target application. The operation on the member prompt page can be either a substantive operation or a non-substantive operation; no specific limitation is made here. The member prompt page may also contain identification information of the target application, such as its name and logo.

[0187] If the target application is not installed on the mobile terminal, or if it is installed but the user has not yet registered to use it, the user can be redirected to the download page for the client used to download the target application or the registration page for using the target application after operating the operation control 1102, so that the user can log in as a member using the target application or make a payment after logging in as a member.

[0188] In practical applications, the member prompt page can also include a download control for downloading the target application client. If the user clicks the control, the first device can be redirected to the download page for downloading the target application client, or the first device can download the target application from the app store. It can also display prompts indicating the download progress, whether it starts as a background download or installation, and display a prompt message indicating that the download or installation is complete after the download or installation is finished.

[0189] In one implementation, if the first device is an iOS system, after the first device approaches the NFC tag and obtains the tag information, it can display a membership prompt page. The membership prompt page can be displayed as a Clips card or in the notification bar. If the user performs an action indicating agreement to launch the target application on the membership prompt page, the first device can launch the target application. The first device can then execute a membership login process or a membership payment process based on the launched target application, such as displaying the membership login page. In practical applications, during the user's operation on the membership prompt page, the first device can collect the user's biometric information as payment verification information. If the user submits information indicating confirmation of membership login and payment based on the membership prompt page, it can indicate that the user has confirmed the payment information, or the payment confirmation page may not be displayed. Of course, the payment confirmation page can also be displayed according to actual needs. If the user has not enabled the express payment function or does not meet the above-mentioned preset payment conditions, the first device can also display the payment confirmation page.

[0190] In one implementation, if the first device is an Android system, after the first device is brought close to the NFC tag and the tag information is obtained, if the target application is already installed on the first device, the target application can be launched and the member login page can be displayed.

[0191] In practical applications, the server needs some time to process the transaction business corresponding to the first device, such as 0.5m seconds, 1 second, 2 seconds, etc. In order to improve the user experience, the first device can also display a payment response page before displaying the payment result page, which can be used to prompt the user that the payment is in progress.

[0192] Figure 12 This is a schematic diagram of a payment response page provided in an embodiment of this specification. Figure 12 As shown, the payment response page may include a prompt message 1202 indicating that a payment is in progress, and a prompt message 1204 indicating that a near-field communication (NFC) payment method is being used, such as the word "NFC"; it may also include relevant descriptive information about NFC payment, etc. Figure 12 The text indicates "Pay with a tap".

[0193] The payment response page can be generated locally on the first device or based on response information from the server. The payment response page can also include progress information about the payment process, such as percentage-based progress information, progress bar-based information, etc.

[0194] It is understood that the various display pages in the embodiments of this specification may be pop-up pages, H5 pages, application pages in the target application, web pages, or other forms of pages, and no specific limitations are made here. For example, the aforementioned member authorization login page may be displayed as a pop-up in the member response page; the aforementioned member prompt page may be displayed as a mini-application page, or as a notification page, etc.

[0195] In practical applications, to improve user experience and ensure user information security, the tag information in an NFC tag can be read only once. After the NFC tag information is read, it can be deleted from the NFC tag, or new tag information can be entered into the NFC tag. Of course, the tag information can also be set to be reusable, depending on actual business needs; no specific limitations are made here.

[0196] In the embodiments of this specification, the target application can be an application with payment functionality or other types of applications. In at least one embodiment of this specification, when a user needs to make a payment using a membership, the user can bring the first device close to the NFC tag of the second device to obtain tag information, and then use the target application to complete membership login and payment. The user can complete membership login and payment simply by touching or tapping the first device against the second device; the entire process requires minimal operation. If the user has not yet registered as a member, the first device can display a membership login authorization page. After the user authorizes and agrees to membership registration, the first device and the server can register the user as a member and perform payment based on the user's authorization. The user can operate solely on the membership login authorization page, requiring minimal additional steps and simplifying the user's operation process.

[0197] In practical applications, to ensure users can make payments seamlessly, payment confirmation pages and other similar displays may be shown. It is understood that the various display pages provided in this manual can be customized according to actual needs, as long as they conform to the business processing logic.

[0198] In the embodiments described in this specification, if the second device has a display screen, the server can also send login result information, payment result information, etc., to the second device, and the second device can also display information indicating the login result, payment result, etc. Before displaying the login result information and payment result information, the second device can also display information indicating that the user is logging in as a member, or information indicating that a payment is in progress, etc. The second device can also display information about various business processing stages through voice broadcasts, prompts, etc. The information displayed on the second device can be set according to actual needs; no specific limitations are made here.

[0199] In practical applications, the first device can display the aforementioned display pages in an unlocked state. For example, the user can unlock the first device first and then bring the first device close to the second device; or the user can bring the first device close to the second device first and then unlock the first device during the bringing process or when processing the bringing state.

[0200] If the system program of the first device can accurately parse the content in the tag information, such as when the tag information is an HTTPS link, the system program can access the link information and display the corresponding display page. The first device can also display the above display pages in the unlocked state to complete operations such as member login or payment.

[0201] Based on the same idea, this specification also provides a method with a server corresponding to the first device described above as the execution subject. Figure 13 This is a flowchart illustrating a method for displaying a member login page, provided as an embodiment of this specification. Figure 13 As shown, the method may include the following steps:

[0202] Step 1302: Obtain the page information retrieval request sent by the first device.

[0203] The page information acquisition request is generated by the first device acquiring the tag information of the second device's NFC tag through near-field communication; the tag information includes first information for activating the target application and second information for executing the member login process.

[0204] Step 1304: Based on the page information acquisition request, send member login page information to the first device.

[0205] The first device can display the member login page.

[0206] In practical applications, the tag information in the second device can be generated by the server according to actual needs. Specifically, it can include: receiving a tag information acquisition request sent by the second device; generating tag information for burning into the NFC tag of the second device based on the tag information acquisition request; the tag information includes first information for activating the target application and second information for executing the member login process; sending the tag information to the second device, which can then burn the tag information into the NFC tag so that the first device can acquire the tag information and execute the member login process via near-field communication.

[0207] The tag information retrieval request can be sent by the merchant or user themselves after determining that the user needs to log in as a member. For example, the second device can be an operable POS system or connected device containing operable controls, such as a cashier clicking a control on the POS terminal to indicate member payment, or a user clicking a control on a self-service payment device to indicate member login or payment. The second device or POS system can then send a tag information retrieval request to the server. The second device can be part of the POS system or self-service payment device, or it can be a device connected to it.

[0208] The server can also send tag information to the second device or the POS system, which in turn sends it to the second device. The second device has the ability to burn NFC tag information into the NFC tag. In this way, the user of the first device can log in as a member via NFC.

[0209] The specific steps the server takes to perform member login or payment can be found in the aforementioned embodiments, and will not be repeated here.

[0210] Based on the same idea, embodiments of this specification also provide apparatus corresponding to the above methods. Figure 14 The embodiments provided in this specification correspond to Figure 2 A schematic diagram of the structure of a device for displaying a member login page. (See diagram below.) Figure 14 As shown, the device may include:

[0211] The information acquisition module 1402 is used to acquire tag information of the NFC tag of the second device through near-field communication; the tag information includes first information for waking up the target application and second information for triggering the member login process;

[0212] Application invocation module 1404 is used to invoke the target application in the first device based on the first information;

[0213] Request sending module 1406 is used to send a page information acquisition request to the server based on the second information using the target application;

[0214] The page display module 1408 is used to obtain the member login page information fed back by the server and display the member login page.

[0215] based on Figure 14 The embodiments of this specification also provide some specific implementations of the device, which will be described below.

[0216] Optionally, the page display module can be specifically used for:

[0217] Obtain the member login result information returned by the server and display the member login result page; the member login result information is the page information returned by the server after determining that the user of the first device is a member of the target object.

[0218] Optionally, the page display module can be specifically used for:

[0219] Obtain the member authorization login page information returned by the server and display the member authorization login page; the member authorization login page information is the page information returned by the server after determining that the user of the first device is not a member of the target object.

[0220] Optionally, the page display module may include a first page display unit, which can be used for:

[0221] The user performs a first operation on the first control of the member authorization login page; the first operation is an operation indicating that the user agrees to become a member of the target object.

[0222] Based on the first operation, a member login request is sent to the server;

[0223] Obtain the member login result information returned by the server and display the member login result page.

[0224] Optionally, the first operation can also represent the user making a payment through a membership payment method. The request sending module can also be used for:

[0225] A first payment trigger request is sent to the server so that the server can execute the corresponding payment processing procedure.

[0226] Optionally, the page display module may include a second page display unit, which can be used for:

[0227] The system obtains a second operation performed by the user on the second control of the member authorization login page; the second operation is an operation indicating that the user agrees to use a non-member payment method for payment.

[0228] A second payment trigger request is sent to the server so that the server can execute the corresponding payment processing procedure.

[0229] Optionally, the page display module may include a third page display unit, which can be used for:

[0230] Obtain the payment result information returned by the server;

[0231] Based on the payment result information, the payment result page is displayed.

[0232] Optionally, the device may also include a payment processing module, which may include:

[0233] The link acquisition unit is used to acquire payment link information provided by the server; the payment link information includes identification information indicating payment information to be confirmed;

[0234] The payment confirmation unit is used to send payment confirmation information to the server based on the payment link information, so that the server can execute the corresponding payment processing flow after obtaining the payment confirmation information.

[0235] Optionally, the payment processing module may also include:

[0236] A page display unit is used to display a payment confirmation page based on the payment link information; the payment confirmation page contains payment information to be confirmed.

[0237] Specifically, the aforementioned payment confirmation unit can be used to send payment confirmation information to the server based on the user's fourth operation on the payment confirmation page.

[0238] Optionally, the payment processing module may also include:

[0239] The condition judgment unit is used to determine whether the user of the first device meets the preset payment conditions; the preset payment conditions represent the conditions under which fast payment can be made.

[0240] The aforementioned page display unit can be specifically used to display the payment confirmation page if the user does not meet the preset payment conditions;

[0241] The aforementioned payment result page may specifically include: if the user meets the preset payment conditions, then the payment result page is displayed.

[0242] Optionally, the page display module also includes a fourth page display unit, which can be used for:

[0243] The login response page is displayed; the login response page contains a prompt message indicating that the login process is in progress.

[0244] Optionally, the page display module also includes a fifth page display unit, which can be used for:

[0245] A member notification page is displayed; the member notification page contains information prompting the user to log in as a member or information prompting the user to make payments through the member;

[0246] The aforementioned application initiation module can specifically be used for:

[0247] The system obtains a second action taken by the user on the member notification page; the second action indicates agreement to log in as a member using the target application.

[0248] Based on the second operation, the target application in the first device is invoked.

[0249] Optionally, the request sending module can be used specifically for:

[0250] Obtain the scene parameter information from the second information;

[0251] Based on the scene parameter information, a page information retrieval request is generated;

[0252] Send the request to obtain the page information to the server.

[0253] Based on the same line of thought Figure 15 The embodiments provided in this specification correspond to Figure 13 A schematic diagram of the structure of a device for displaying a member login page. (See diagram below.) Figure 15 As shown, the device may include:

[0254] The request acquisition module 1502 is used to acquire a page information acquisition request sent by the first device; the page information acquisition request is generated by the first device acquiring the tag information of the NFC tag of the second device through near field communication; the tag information includes first information for waking up the target application and second information for executing the member login process;

[0255] The page information sending module 1504 is used to send member login page information to the first device based on the page information acquisition request, so that the first device can display the member login page.

[0256] based on Figure 15 The embodiments of this specification also provide some specific implementations of the device, which will be described below.

[0257] Optionally, the page information acquisition request includes the user identification information of the first device; the device may also include a judgment module, used to determine whether the user of the first device is a member of the target object based on the user identification information, and obtain a judgment result.

[0258] The aforementioned page information sending module may include a first page information sending unit, which is used to send member login result information to the first device if the judgment result indicates that the user is a member of the target object, so that the first device can display the member login result page.

[0259] Optionally, the above-mentioned page information sending module may include a second page information sending unit, which is used to send member authorization login page information to the first device if the judgment result indicates that the user is not a member of the target object, so that the first device can display the member authorization login page.

[0260] Optionally, the above-mentioned page information sending module may include a third page information sending unit, used for:

[0261] Obtain a member login request sent by the first device; the member login request is generated by the first device based on a first operation by the user on a first control of the member authorization login page; the first operation is an operation indicating that the user agrees to become a member of the target object;

[0262] Send member login result information to the first device so that the first device can display the member login result page.

[0263] Optionally, the request acquisition module may include a first payment request acquisition unit, and the first operation further represents the user's payment operation using a membership payment method. The first payment request acquisition unit may be used to: acquire the first payment trigger request sent by the first device;

[0264] Based on the first payment trigger request, the user's first transaction information is sent to the payment system of the counterparty to the first device; so that the payment system can process the payment transaction for the user based on the first transaction information; the first transaction information includes transaction identification information representing the user's transaction account information and the user's membership information.

[0265] Optionally, the request acquisition module may include a second payment request acquisition unit, which can be used to: acquire a second payment trigger request sent by the first device; the second payment trigger request is generated by the first device based on a second operation by the user on a second control of the member authorization login page; the second operation is an operation indicating that the user agrees to make payment using a non-member payment method;

[0266] Based on the second payment trigger request, the user's second transaction information is sent to the payment system associated with the second device; so that the payment system can process the payment transaction for the user based on the second transaction information; the second transaction information includes transaction identifier information for representing the user's transaction account information.

[0267] Optionally, the device may include a transaction processing module. If the determination result indicates that the user is a member of the target object, the transaction information sending module in the transaction processing module is used to: send the user's first transaction information to the payment system associated with the second device, so that the payment system can process the payment business for the user based on the first transaction information; the first transaction information includes transaction identification information for representing the user's transaction account information and the user's membership information.

[0268] Optionally, the transaction processing module can also be used to: obtain a payment processing request generated by the payment system based on the transaction identifier information;

[0269] The payment process is executed based on the payment processing request to obtain payment result information;

[0270] The payment result information is sent to the first device.

[0271] Optionally, the transaction processing module can also be used to: send payment link information to the first device; the payment link information includes identification information indicating payment information to be confirmed;

[0272] The server obtains payment confirmation information provided by the first device so that it can execute the corresponding payment processing procedure after receiving the payment confirmation information.

[0273] Optionally, the payment confirmation information is sent by the first device based on the user's fourth operation on the payment confirmation page displayed based on the payment link information.

[0274] Based on the same idea, this specification also provides devices corresponding to the above methods in its embodiments.

[0275] Figure 16 This is a schematic diagram of the structure of a device for displaying a member login page, provided as an embodiment of this specification. Figure 16 As shown, device 1600 may include:

[0276] At least one processor 1610; and,

[0277] Memory 1630 communicatively connected to the at least one processor; wherein,

[0278] The memory 1630 stores instructions 1620 that can be executed by the at least one processor 1610 to enable the at least one processor 1610 to perform the above-described method for displaying the member login page.

[0279] Based on the same approach, embodiments of this specification also provide a computer-readable medium corresponding to the above-described method. The computer-readable medium stores computer-readable instructions that can be executed by a processor to implement the above-described method for displaying a member login page.

[0280] The various embodiments in this specification are described in a progressive manner. Similar or identical parts between embodiments can be referred to mutually. Each embodiment focuses on describing the differences from other embodiments. In particular, the above-described apparatus and device are basically similar to the method embodiments, so the description is relatively simple; relevant parts can be referred to the description of the method embodiments.

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

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

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

[0284] For ease of description, the above devices are described separately by function as various units. Of course, in implementing this application, the functions of each unit can be implemented in one or more software and / or hardware.

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

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

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

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

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

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

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

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

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

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

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

Claims

1. A method for member payment, comprising: The first device obtains the tag information of the NFC tag of the second device through near field communication; The tag information includes information for triggering the member login process and information for triggering the payment transaction processing process. Send at least a portion of the tag information to the server; If the server determines that the user of the first device is a member, it executes the payment processing flow according to the member payment link. Obtain the payment result information returned by the server and display the payment result page; The method further includes: If the user of the first device is not a member of the target object, obtain the member authorization login page information fed back by the server and display the member authorization login page; the member authorization login page information is the page information fed back by the server after determining that the user of the first device is not a member of the target object; A member login request is generated based on the user's first operation on the member authorization login page; the member login request is sent to the server; the first operation indicates that the user agrees to become a member of the target object.

2. The method according to claim 1, wherein the tag information includes information for invoking the target application; and before displaying the payment result page, it further includes: Based on the information used to invoke the target application, the target application in the first device is invoked.

3. The method according to claim 2, further comprising: The target application sends a page information retrieval request to the server.

4. The method according to claim 1, further comprising, before displaying the payment result page: Obtain the member login result information returned by the server and display the member login result page; The member login result information is the page information returned by the server after determining that the user of the first device is a member of the target object.

5. The method according to claim 1, further comprising: Obtain the user's first operation on the first control of the member authorization login page; The first operation is an operation that indicates the user's consent to become a member of the target object; Based on the first operation, a member login request is sent to the server; Obtain the member login result information returned by the server and display the member login result page.

6. The method according to claim 5, wherein the first operation further represents the user making a payment through a membership payment method, and the method further includes: A first payment trigger request is sent to the server so that the server can execute the corresponding payment processing procedure.

7. The method according to claim 1, further comprising: Obtain the user's second operation on the second control of the member authorization login page; The second operation is to indicate to the user that they agree to use a non-member payment method for payment; A second payment trigger request is sent to the server so that the server can execute the corresponding payment processing procedure.

8. The method according to claim 1, further comprising, before displaying the payment result page: The payment response page is displayed; the payment response page is used to notify the user that a payment is in progress.

9. The method according to claim 1, further comprising, before obtaining the payment result information returned by the server: Obtain payment link information provided by the server; the payment link information includes identification information indicating payment information to be confirmed; Based on the payment link information, a payment confirmation message is sent to the server so that the server can execute the corresponding payment processing procedure after receiving the payment confirmation message.

10. The method according to claim 9, wherein sending payment confirmation information to the server based on the payment link information specifically includes: Based on the payment link information, a payment confirmation page is displayed; the payment confirmation page contains payment information to be confirmed. Based on the user's fourth action on the payment confirmation page, payment confirmation information is sent to the server.

11. The method according to claim 10, wherein displaying the payment confirmation page based on the payment link information specifically includes: Determine whether the user of the first device meets the preset payment conditions; The preset payment conditions represent the conditions under which fast payments can be made; The payment confirmation page specifically includes: If the user does not meet the preset payment conditions, the payment confirmation page will be displayed; The payment result display page specifically includes: If the user meets the preset payment conditions, the payment result page will be displayed.

12. The method according to claim 1, further comprising: Display the login response page; The login response page includes a message indicating that a member is logging in.

13. The method according to claim 1, further comprising: Display the member notification page; The member notification page contains information prompting the user to log in as a member or prompting the user to make a payment through the member; The system obtains a second action taken by the user on the member notification page; the second action indicates agreement to log in as a member using the target application. Based on the second operation, the target application in the first device is invoked.

14. The method according to claim 3, wherein sending a page information retrieval request to the server using the target application specifically includes: Obtain the scenario parameter information from the information used to trigger the member login process and the information used to trigger the payment business processing process; Based on the scene parameter information, a page information retrieval request is generated; Send the request to obtain the page information to the server.

15. A method for member payment, comprising: Obtain at least a portion of the tag information sent by the first device; The tag information is obtained by the first device from the NFC tag of the second device via near-field communication; the tag information includes information for triggering the member login process and information for triggering the payment transaction processing process. Based on at least some of the information in the tag information, the payment process is performed according to the member payment link to generate payment result information; Send payment result information to the first device; The method further includes: Determine whether the user of the first device is a member of the target object, and obtain the determination result; If the determination result indicates that the user is not a member of the target object, then send the member authorization login page information to the first device so that the first device can display the member authorization login page; The system obtains a member login request sent by the first device, which is generated based on the user's first operation on the member authorization login page; the first operation indicates that the user agrees to become a member of the target object.

16. The method according to claim 15, further comprising, before sending the payment result information: Obtain the page information retrieval request sent by the first device; The page information retrieval request is generated by the first device based on the tag information.

17. The method according to claim 15, further comprising, before sending the payment result information: Send member login page information to the first device so that the first device can display the member login page.

18. The method according to claim 17, wherein sending the member login page information to the first device specifically includes: If the determination result indicates that the user is a member of the target object, then the member login result information is sent to the first device so that the first device can display the member login result page.

19. The method according to claim 15, further comprising: Obtain the member login request sent by the first device; The member login request is generated by the first device based on a first operation by the user on a first control of the member authorization login page; the first operation is an operation indicating that the user agrees to become a member of the target object. Send member login result information to the first device so that the first device can display the member login result page.

20. The method according to claim 19, wherein the first operation further represents an operation in which the user makes a payment using a membership payment method, and the method further includes: Obtain the first payment trigger request sent by the first device; Based on the first payment trigger request, the user's first transaction information is sent to the payment system of the counterparty to the first device; so that the payment system can process the payment transaction for the user based on the first transaction information; the first transaction information includes transaction identification information representing the user's transaction account information and the user's membership information.

21. The method according to claim 15, further comprising: Obtain the second payment trigger request sent by the first device; The second payment trigger request is generated by the first device based on the user's second operation on the second control of the member authorization login page; the second operation is an operation indicating that the user agrees to make payment using a non-member payment method; Based on the second payment trigger request, the user's second transaction information is sent to the payment system associated with the second device; so that the payment system can process the payment transaction for the user based on the second transaction information; the second transaction information includes transaction identifier information for representing the user's transaction account information.

22. The method according to claim 15, further comprising: The first transaction information of the user of the first device is sent to the payment system associated with the second device, so that the payment system can process the payment business for the user based on the first transaction information; the first transaction information includes transaction identification information for representing the user's transaction account information and the user's membership information.

23. The method according to claim 22, further comprising: Obtain the user identification information sent by the first device; The user's transaction account is determined based on the user identification information; Generate the transaction identifier information that corresponds to the user's transaction account.

24. The method according to claim 15, further comprising: The system obtains a payment processing request generated by the payment system based on transaction identifier information, so that the server executes the payment process based on the payment processing request and obtains payment result information. The transaction identifier information is used to represent the transaction account information of the user of the first device.

25. The method according to claim 15, further comprising: Send payment link information to the first device; The payment link information includes identification information indicating payment information to be confirmed; The payment confirmation information provided by the first device is obtained so that the server can execute the corresponding payment processing flow after obtaining the payment confirmation information.

26. The method according to claim 25, wherein the payment confirmation information is sent by the first device based on a fourth operation by the user on the payment confirmation page displayed based on the payment link information.

27. A device for member payment, comprising: The information acquisition module is used by the first device to acquire the tag information of the NFC tag of the second device through near-field communication; The tag information includes information for triggering the member login process and information for triggering the payment transaction processing process. A sending module is used to send at least a portion of the tag information to a server; If the server determines that the user of the first device is a member, it executes the payment processing flow according to the member payment link. The page display module is used to obtain the payment result information returned by the server and display the payment result page; The device is also used for: If the user of the first device is not a member of the target object, obtain the member authorization login page information fed back by the server and display the member authorization login page; the member authorization login page information is the page information fed back by the server after determining that the user of the first device is not a member of the target object; A member login request is generated based on the user's first operation on the member authorization login page; Send the member login request to the server; The first operation represents the user's agreement to become a member of the target object.

28. A device for member payment, comprising: The information acquisition module is used to acquire at least a portion of the tag information sent by the first device; The tag information is obtained by the first device from the NFC tag of the second device via near-field communication; the tag information includes information for triggering the member login process and information for triggering the payment transaction processing process. The payment processing module is used to process at least some of the information in the tag information according to the member payment link and generate payment result information; The information sending module is used to send payment result information to the first device; The device is also used for: Determine whether the user of the first device is a member of the target object, and obtain the determination result; If the determination result indicates that the user is not a member of the target object, then send the member authorization login page information to the first device so that the first device can display the member authorization login page; The system obtains a member login request sent by the first device, which is generated based on the user's first operation on the member authorization login page; the first operation indicates that the user agrees to become a member of the target object.

29. A device for member payment, comprising: At least one processor; as well as, A memory communicatively connected to the at least one processor; wherein, The memory stores instructions executable by the at least one processor, which, when executed by the at least one processor, enables the at least one processor to perform the member payment method according to any one of claims 1 to 26.

30. A computer-readable medium having stored thereon computer-readable instructions that can be executed by a processor to implement the member payment method according to any one of claims 1 to 26.

Images