Member payment method and device, equipment and medium

Abstract

The embodiment of the invention discloses a member payment method and device, equipment and a medium. According to the scheme, the method comprises the steps that a first device obtains label information of an NFC label of a second device in a near field communication mode; the label information comprises information used for triggering a member login process and information used for triggering a payment business processing process; at least part of information in the label information is sent to a server; the server executes a payment processing flow according to a member payment link under the condition that the server determines that the user of the first equipment is a member; and obtaining payment result information fed back by the server, and displaying a payment result page.

Description

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

[0002] The present application relates to the field of computer technology, and in particular to a method, device, equipment and medium for displaying a member login page. Background Art

[0003] In order to provide better services to users, more and more businesses have adopted a membership mechanism. For example, merchants provide members with various rights or preferential activities; for example, some service providers provide member users with richer reading information, videos, audio information, etc.

[0004] How to provide a more convenient member login method is a technical problem that needs to be solved urgently. Summary of the invention

[0005] The embodiments of this specification provide a method, device, equipment and medium for displaying a member login page to solve the problem of complicated operation in the existing member login method.

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

[0007] A method for displaying a member login page provided in an embodiment of this specification includes:

[0008] The first device obtains tag information of the NFC tag of the second device by means of near field communication; the tag information includes first information for invoking the target application and second information for executing the member login process;

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

[0010] Based on the second information, using the target application to send a page information acquisition request to a server;

[0011] Obtain the member login page information fed back by the server, and display the member login page.

[0012] A method for displaying a member login page provided in an embodiment of this specification includes:

[0013] Obtaining a page information acquisition request sent by a first device; the page information acquisition request is generated by the first device acquiring tag information of an NFC tag of a second device through near field communication; the tag information includes first information for invoking a target application and second information for executing a member login process;

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

[0015] An apparatus for displaying a member login page provided by an embodiment of this specification includes:

[0016] An information acquisition module, configured to acquire the tag information of the NFC tag of the second device by means of near field communication; the tag information includes first information for invoking a target application and second information for triggering a member login process;

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

[0018] A request sending module, configured to send a page information acquisition request to the server by using the target application based on the second information;

[0019] A page display module, configured to acquire the member login page information fed back by the server and display the member login page.

[0020] An apparatus for displaying a member login page provided by an embodiment of this specification includes:

[0021] A request acquisition module, configured 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 by means of near field communication; the tag information includes first information for invoking a target application and second information for executing a member login process;

[0022] A page information sending module, configured to send the 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] An apparatus for displaying a member login page provided by an embodiment of this specification includes:

[0024] At least one processor; and,

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

[0026] The memory stores instructions executable by the at least one processor, and when the instructions are executed by the at least one processor, the at least one processor is enabled to execute a method for displaying a member login page.

[0027] A computer-readable medium provided by an embodiment of this specification, on which computer-readable instructions are stored, and the computer-readable instructions can be executed by a processor to implement a method for displaying a membership login page.

[0028] An 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 uses the first information and the second information in the tag information to display the membership login page. In this way, the user can bring the first device close to the second device to display the membership login page, making it more convenient for the user to log in to the membership. BRIEF DESCRIPTION OF THE DRAWINGS

[0029] To more clearly illustrate the technical solutions in the embodiments of this specification or the prior art, the following will briefly introduce the drawings required for use in the description of the embodiments or the prior art. Obviously, the drawings in the following description are only some embodiments recorded in this application. For those of ordinary skill in the art, without creative efforts, other drawings can also be obtained based on these drawings.

[0030] Figure 1 It is a schematic diagram of an application scenario of a method for displaying a membership login page in an embodiment of this specification;

[0031] Figure 2 It is a schematic flowchart of a method for displaying a membership login page provided by an embodiment of this specification;

[0032] Figure 3 It is a swimlane diagram of a method for displaying a membership login page provided in an embodiment of this specification;

[0033] Figure 4 It is a schematic diagram of a membership authorization login page provided in an embodiment of this specification;

[0034] Figure 5 It is a schematic diagram of a membership login result page provided in an embodiment of this specification;

[0035] Figure 6 It is a schematic diagram of another membership login result page provided in an embodiment of this specification;

[0036] Figure 7 It is a schematic diagram of another membership authorization login page provided in an embodiment of this specification;

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

[0038] Figure 9 It is a schematic diagram of a payment confirmation page provided in an embodiment of this specification;

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

[0040] Figure 11 It is a schematic diagram of a membership prompt page provided in the embodiments of this specification;

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

[0042] Figure 13 It is a schematic flow diagram of a method for displaying a membership login page provided in the embodiments of this specification;

[0043] Figure 14 corresponding to the embodiments of this specification Figure 2 It is a schematic structural diagram of a device for displaying a membership login page;

[0044] Figure 15 corresponding to the embodiments of this specification Figure 13 It is a schematic structural diagram of a device for displaying a membership login page;

[0045] Figure 16 It is a schematic structural diagram of a device for displaying a membership login page provided in the embodiments of this specification. Detailed implementation manners

[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 the specific embodiments of this specification and the corresponding drawings. Obviously, the described embodiments are only a part of the embodiments of this specification, rather than all of the embodiments. Based on the embodiments in this specification, all other embodiments obtained by those of ordinary skill in the art without creative efforts fall within the scope protected by one or more embodiments of this specification.

[0047] The following will detail the technical solutions provided in each embodiment of this specification in conjunction with the drawings.

[0048] In the related art, if a user wants to log in to a membership or activate a membership, one way is that the user needs to first find the corresponding web page, client, or mini-program, then find the membership entrance, and then enter some verification information, such as account number, password, etc., before being able to log in to the membership. Another way is that the user uses the QR code scanning function of certain clients in the mobile phone to scan the membership code provided by the merchant to log in to the membership. These methods all require the user to first find the web page, client, or mini-program, or open the corresponding client to scan the code to display the membership login page, and the operations are relatively cumbersome.

[0049] To solve the defects in the prior art, the following embodiments are provided in this solution:

[0050] Figure 1 This is a schematic diagram of the application scenario of a method for displaying a member login page in the embodiments of this specification. As Figure 1 shown, this solution may include a first device 1, a second device 2, and a server 3. Among them, the first device 1 can obtain the tag information of the NFC tag of the second device by approaching the NFC tag of the second device, such as by sticking or touching, and utilize the near-field communication function to obtain the tag information of the NFC tag. The first device 1 can use this tag information to evoke the target application in the first device and display the member login page information obtained from the server 3 in the target application.

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

[0052] Figure 2 This is a schematic flowchart of a method for displaying a member login page provided in the embodiments of this specification. From a program perspective, the execution subject of the process can be a program or application client installed on the first device. From a hardware perspective, the execution subject of this process can be the first device with near-field communication function. The first device can be a mobile phone, smart watch, smart bracelet, portable computer, wearable smart device, etc., or other mobile terminals, and the specific type of the device is not limited here.

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

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

[0055] Among them, the tag information contains the first information for evoking the target application and the 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 can be separately set from the second device and connected by wire or wirelessly. The first device has NFC near-field communication function and can be used as an NFC card reader to obtain the tag information of the NFC tag of the second device. The NFC tag can also be called an NFC card and has components such as an NFC chip and a coil.

[0056] In this specification, the first device can be used as a card reader. When the NFC switch is turned on, it will send signals in the LPCD (Low Power Card Detection) mode, or a combination of the LPCD mode and normal card searching. When the first device is close to the NFC tag, for example, by touching or sticking to 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 that there is a tag nearby based on this influence and then initiate an inquiry to enter the interaction process, which can specifically be command interaction and data interaction. For example, the first device can obtain the information in the NFC tag. The specific NFC interaction process can be referred to in the related technology and will not be elaborated here.

[0057] The first information and the second information can be characters or strings in a preset format. For example, they can be link information, such as a URL (Universal Resource Locator) starting with http or https, or other forms of characters or strings that can be recognized by the first device. The first information and the second information can be information within the same string, or they can be independent characters or strings respectively, and no specific limitation is required.

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

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

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

[0061] The second information is the information used to trigger the membership login process. The operating system of the first device can provide the second information to the target application, and the target application can trigger the membership login process based on the second information. It can be understood that the client application program of the target application can execute the process related to membership login according to the second information. As an implementation manner, the second information can include information for jumping to a page, such as information in the form of a URL. After the first device starts the target application, the target application can send a page information acquisition request to the server according to the second information and can also receive the information feedback from the server.

[0062] Step 208: Obtain the membership login page information fed back by the server and display the membership login page.

[0063] The server is a server that can provide services for the target application. The server can determine the corresponding membership login page information according to the page information acquisition request sent by the target application and feed it back to the target application.

[0064] In practical applications, different merchants or membership service providers can set a membership login page that meets the business requirements according to actual needs. Optionally, the second information may include the identification information of the membership service provider. For example, the identification information of the merchant served by the second device. The server can, according to this identification information, send the corresponding membership login page information, and the corresponding membership login page can be displayed on the first device.

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

[0066] Figure 2 In the method, the first device obtains the tag information of the NFC tag of the second device through near-field communication. By using the first information and the second information in the tag information, the membership login page can be displayed. In this way, the user can bring the first device close to the second device to display the membership login page, making it more convenient for the user to log in to the membership.

[0067] In the embodiments of this specification, the above-mentioned membership login page can be a single page or multiple associated pages. As an implementation manner, if the user of the first device is already a member of the membership service provider, after the first device obtains the NFC tag information, the login result page can be displayed. If the user is not yet a member of the membership service provider, the membership authorization login page for prompting the user to authorize to become a member can be displayed. After obtaining the user's authorization, the user can be determined as a member. On the basis that the user authorizes the first device or the server to save the relevant membership information, if the user logs in to the membership again next time, after the user uses the first device to stick to the second device, the membership authorization login page may not be displayed on the first device, and the membership login result page can be directly displayed.

[0068] To more clearly illustrate the method for displaying the information of the membership login page provided in the embodiments of this specification, Figure 3 The following is a swimlane diagram of a method for displaying a membership login page provided in the embodiments of this specification. As Figure 3 shown, this 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 a membership service provider or a device connected to the management system of the membership service provider. The membership service provider can burn tag information into the NFC tag of the second device according to actual business needs. For example, the tag information can be burned into the NFC tag through the second device. The membership service provider can be an object providing membership services, such as some merchants with membership services, such as supermarkets, shopping malls, bookstores, restaurants, hospitals, social service institutions, etc., or some public welfare or non-public welfare organization groups, such as reading clubs, sports meetings, etc.

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

[0072] Among them, the tag information can include a first piece of information for invoking a target application and a second piece of information for triggering a membership login process.

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

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

[0075] In practical applications, different membership service providers can correspond to different membership login pages. Optionally, as an implementation manner, the above-mentioned using the target application to send a page information acquisition request to the server based on the second piece of information can specifically include:

[0076] Obtain the scenario parameter information in the second piece of information;

[0077] Generate a page information acquisition request based on the scenario parameter information;

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

[0079] Among them, the scenario parameter information can represent parameter information related to the membership login scenario, and specifically can include at least one of the identification information of the target object providing membership services, the identification information of the second device, and the service identification information representing the processed membership login service. The scenario parameter information can also include token information generated using the Token mechanism, etc. The page information acquisition request can include the scenario parameter information or the identification information corresponding to the scenario parameter information, so that the server can execute the corresponding membership login process according to the parameter information included in the page information acquisition request.

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

[0081] The page information acquisition request is a request for the server to feedback 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 feedback by the server and displays the member login page.

[0084] In practical applications, for users in different states, the server can also feedback different page information. For example, if the user has not registered before or has not authorized the registration of the member of the target object corresponding to the second device through NFC communication, the server can feedback a page that prompts the user to register or authorize to become a member; if the user is already a member of the target object or has been authorized as a member through NFC communication before, that is, there is record information of the user as a member in the server, there is no need to feedback a page that prompts the user to register or authorize to become a member, and the login result page can be feedback to the first device so that the user can know whether they have logged in as a member.

[0085] As an implementation manner, the page information acquisition request may include the user identification information of the first device. For example, it may be the device identification information of the first device, or the user identification information of the user in the first device or the target application, such as UID (User Identification), mobile phone number, email account, application account, social account, etc. Before sending the member login page information to the first device, the server may also execute step 3122: Based on the user identification information, determine whether the user of the first device is a member of the target object to obtain a judgment result.

[0086] Optionally, if the judgment 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 to obtain the member login page information feedback by the server and display the member login page may specifically further include step 3142: Obtain the member authorization login page information feedback by the server and display the member authorization login page.

[0088] Among them, the member authorization login page information is the page information feedback 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 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 the confirmation of member login, the control indicating the logout of member login, the control indicating payment in the member mode, and the control indicating payment in the non-member mode.

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

[0091] As Figure 4 shown, the member authorization login page may further include the control 406 indicating the logout of member login. If the user clicks this control, it can indicate 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 408 of the target object, etc.

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

[0093] Wherein, the first operation is an operation indicating that the user agrees to become a member of the target object. Specifically, it may be the first operation on the first control of the member authorization login page, or an operation executed according to a preset operation instruction. It may also be a substantial operation or a non-substantial operation of the non-action type. For example, during the process of displaying a prompt message for canceling authorization in a countdown manner, if the user does not perform an operation indicating the cancellation of member login or registration for authorization, it can indicate that the user agrees to authorize login or registration as a member.

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

[0095] Among them, 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 the member registration or login process according to the member login request sent by the first device, and record the user as a member of the target object or a member in the logged-in state.

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

[0097] The server can generate member login result information based on the result of the member login for the user and feedback it to the first device. In practical applications, the server can interact with the devices or systems of the member service provider to complete the login or registration of the user's membership. For example, the obtained user information can be provided to the devices or systems of the member service provider so that the member service provider can mark the user as a member user. It is also possible for the server to independently complete member registration or login. The specific member registration or login process is not specifically limited or elaborated here, and relevant implementation methods can be referred to.

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

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

[0100] Correspondingly, the obtaining of the member login page information fed back by the server and the display of the member login page in Step 314 executed by the above first device can specifically include the above Step 3148: Obtaining the member login result information fed back by the server and displaying the member login result page. Among them, the member login result information is the page information fed back after the server determines 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 result page provided in the embodiments of this specification. As Figure 5 shown, the page may include information 502 indicating the member login result. In practical applications, if the login is successful, information indicating successful login, such as "Login successful", can be displayed on the login result page; if the login fails, information indicating failed login, such as "Login failed", can be displayed, or information on the reason for the failed login, such as "Login timeout", can also be displayed; if the login fails, information prompting the user to log in again can also be displayed, and so on.

[0102] like Figure 5 As shown, the page may also include information 504 of the member-provided service provider, such as the name of the merchant, logo information, etc., and may also include identification information of the target application, etc. It may also include identification information of near field communication, such as information with the word NFC, etc.

[0103] In actual applications, the login result page can be logged out automatically, such as Figure 5 The countdown information of "2 seconds" is shown in the figure. After the countdown ends, the login result page can exit automatically. It can also be exited based on user operations. For example, the login result page can include an operation control, and the user can exit the page or jump to another page by clicking the control.

[0104] Figure 6 FIG. 1 is a schematic diagram of another member login result page provided in an embodiment 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 entering the member service page, and may also include a control 606 for exiting the current page. If the user clicks the control 604, the first device may jump from the page to the member service page containing member service information, and the page may contain member rights information that the user can enjoy, such as coupons, user member points, user member level, etc. If the user clicks the control 606, the member login result page may be exited.

[0105] In actual applications, in some merchants that provide membership services, transactions can also be made using the membership payment method, and users who use the membership payment method can enjoy some membership benefits, such as preferential member prices, coupons, member points, etc. The member login method provided in the embodiments of this specification can also be applied to payment application scenarios.

[0106] Figure 7 FIG. 1 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 that the user agrees to register as a member and pay in a member manner. If the user operates the control, it means that the user agrees to register as a member and agrees to make the payment, and the user can enjoy the benefits of member payment. The user's operation on the control 702 can trigger the member registration and login process, and can also trigger the payment processing business process.

[0107] like Figure 7As shown, the member authorization login page may further include a control 704 indicating payment in a non-member manner. If the user operates on this control, it indicates that the user has not authorized to register as a member but agrees to make a payment, and can trigger the payment processing business process. In practical applications, the member authorization login page may further include a control indicating the logout member login result page, or a control indicating that the user cancels or does not agree to member login.

[0108] It can be understood that the above is only a page example, and the specific page content can be set according to actual needs, and no specific limitation is made here.

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

[0110] Among them, the payment trigger request may be generated by the first device based on a preset operation of the user on the member login result page. The preset operation may represent an operation for the user to make a payment, which may be an operation indicating that the user agrees to pay in a non-member manner, or an operation indicating that the user agrees to pay in a member manner. As in the above Figure 7 shown member authorization login page, whether the user operates on the control 702 indicating agreeing to register as a member and pay in a member manner, or on the control 704 indicating payment in a non-member manner, the first device can send a payment processing request to the server.

[0111] Optionally, the server may further execute step 318: obtain the payment trigger request and execute the payment processing process.

[0112] It may also execute step 320: send payment result information to the first device.

[0113] Among them, the server contains a program for the user to process payment requests. After obtaining the payment trigger request sent by the first device, it can execute the corresponding payment processing process. For example, the payment trigger request contains information about both parties to the transaction and the quantity of resources to be traded. The server can transfer the resources of the payer to the corresponding account of the payee according to this request. Another example is that the server can also send the user information of the first device to the system or device of the other party to the transaction, so that the other party to the transaction can generate order information and send it to the server. The server can also process the payment transaction between the first device and the other party to the transaction according to the order information provided by the other party to the transaction.

[0114] Among them, the transaction result information may be the result information obtained by the server processing the payment business 1, which may be information indicating successful transaction or information indicating failed transaction. The specific process of the server processing the payment business can refer to related technologies and will not be elaborated here in detail.

[0115] Correspondingly, the first device may further execute step 322: display a payment result page.

[0116] Wherein, the first device may obtain the payment result information fed back by the server; based on the payment result information, display a payment result page. The payment result page may include the payment result information fed back by the server.

[0117] Figure 8 It is a schematic diagram of a payment result page provided by an embodiment of this specification. As Figure 8 shown, as Figure 8 shown, the transaction result page may include information 802 on the payment result, such as payment success, payment failure, etc., and may also include payment information 804 such as the payment amount, payment method, trading party, preferential information, etc.; it may also include a control 806 for closing the transaction result page, such as a "complete" control. In practical applications, the specific content and format of the transaction result page may be set according to actual needs, and no specific limitation is made here.

[0118] The second information in the label information of the embodiment of this specification may include information for triggering a membership login process, or may include information for triggering a payment service processing process. For example, it may include some preset characters. The first device may send at least part of the information in the label information to the server, and the server may trigger the payment service processing process whether it determines that the user is a member or not according to some preset characters.

[0119] As an implementation manner, the first operation of the user on the membership authorization login page obtained by the first device may also indicate an operation for the user to make a payment by using the membership payment method. Optionally, the first device may further execute the following steps:

[0120] Send a first payment trigger request to the server so that the server executes a corresponding payment processing process.

[0121] Wherein, the first payment trigger request may indicate a payment trigger request for making a payment by using the membership payment method, and the server may process the request according to the membership payment link.

[0122] In practical applications, to simplify the user operation, the first payment trigger request may also be generated based on the above-mentioned first operation of the user on the membership authorization login page, that is, when the user performs a first operation, it may trigger membership registration and login, or may trigger the payment process. The first device may send a membership login request to the server based on the first operation, or may send a first payment trigger request to the server. These two requests may also be sent to the server as one request, or may be sent to the server separately.

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

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

[0125] Based on the first payment trigger request, send the first transaction information of the user to the payment system of the trading party opposite to the first device; so that the payment system processes the payment service for the user based on the first transaction information; the first transaction information includes transaction identification information for representing the transaction account information of the user and the membership information of the user.

[0126] Among them, the payment system can represent the system for managing payment services of the other party trading with the first device, and can also be understood as the payment system of the trading counterparty, which can also be called the cash register system, such as a merchant cash register, a merchant cash register, etc., or can also be a payment device connected to the merchant cash register system, such as the second device. The payment system can send a payment request to the server based on the obtained transaction information, and the server conducts payment processing and can also feedback the transaction result to both trading parties. For example, cash registers, cash register devices, self-service payment devices, etc. set up in places such as supermarkets and shopping malls, the cash register system can determine the user payment account for conducting transactions based on the transaction identification information. If the cash register system is used for receiving payments, the user payment account can represent the payment account. If the cash register system is used for making payments, the user payment account can represent the receiving account. The cash register system can also correspond to the transaction account. The cash register system can generate a transaction request based on the obtained user payment account and the transaction account corresponding to the cash register system and send it to the server. The server can process this transaction request. For example, it can deduct the corresponding resources from the user payment account and add them to the transaction account corresponding to the cash register system. After the processing is completed, the server can feedback the payment result information to the server. The specific transaction processing flow can refer to the related technology, and the cash register system can also process transactions according to the existing processing flow, which will not be specifically elaborated here.

[0127] In practical applications, the server can directly send the first transaction information to the payment system of the trading party opposite to the first device, or can send the first transaction information to the payment system through the second device. Among them, the second device can send the first transaction information to the payment system in a wired or wireless manner. If the payment system can also read NFC information, the second device can also burn the obtained first transaction information into the NFC tag, and then the payment system reads this information using the NFC reading function.

[0128] The transaction identification information can be used to determine the user transaction account in the first device. If the tag information contained in the NFC tag represents a payment process for making a payment, this account can be the payment account. If the tag information contained in the NFC tag represents a payment process for receiving payment, this account can be the receiving account, which is not specifically limited here. In practical applications, the target application can be a terminal application with payment functions, and the user transaction account can also be the user account logged in to this terminal application.

[0129] In practical applications, the transaction identification information can be generated by the server according to 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, and the transaction identification information can be different in different payment processes.

[0130] As an implementation manner, the first device can send a payment trigger request containing the user identification information in 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] Among them, the user identification information can be the user ID, and can also be the device identification of the mobile terminal, the user application identification of the user in the terminal application, etc., which are identification information that can be used to determine the user transaction account. The server can determine the user transaction account according to the user identification information, and generate transaction identification information having a corresponding relationship with this user transaction account, so that subsequent payment transactions can be processed using this user transaction account according to this transaction identification information.

[0132] In practical applications, the transaction identification information can also include a string representing the payment code, a string representing the transaction order number, etc. The server can process the transactions between the trading parties according to this transaction identification information. The specific transaction identification information can be a string of characters, which can be a string that can be recognized by the server for processing payment services and is a string that conforms to the payment rules of the payment application. For example, it can be a string starting with 28, or a string starting with 25, 30, etc. The length of the string can be 16 to 24 characters, or other lengths that meet the requirements. The specific form of the string is not specifically limited here. For the relevant content of the transaction identification information, reference can also be made to the relevant descriptions in the foregoing embodiments.

[0133] The user's membership information can include the user information used when registering as a member, such as mobile phone number, name and other information, and can also include the membership identification information generated by the server for member users, such as the card number of the membership card, the member user number, etc. For details, reference can be made to the relevant technologies, which are not specifically limited and elaborated here.

[0134] In the embodiments of this specification, after determining that the user uses the membership payment method, the server sends the transaction identification information and membership information of the first device user to the payment system. Among them, the transaction identification information and membership information can be sent to the payment system in one piece of information, or can be sent to the payment system separately.

[0135] In the embodiments of this specification, the membership authorization login page may include a control indicating payment by non-membership method. Optionally, in the embodiments of this specification, the first device may further perform the following steps:

[0136] Obtain a second operation of the user on the second control of the membership authorization login page; the second operation is an operation indicating that the user agrees to pay by non-membership payment method;

[0137] Send a second payment trigger request to the server so that the server executes the corresponding payment processing flow.

[0138] Among them, the second payment trigger request may indicate a payment trigger request for paying by non-membership payment method, and the server may process this request according to the non-membership payment link.

[0139] Correspondingly, the server may further perform the following steps:

[0140] 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 second operation of the user on the second control of the membership authorization login page; the second operation is an operation indicating that the user agrees to pay by non-membership payment method;

[0141] Based on the second payment trigger request, send the second transaction information of the user to the payment system associated with the second device; so that the payment system processes the payment service for the user based on the second transaction information; the second transaction information includes transaction identification information for representing the transaction account information of the user.

[0142] Among them, the transaction identification information and the payment system can refer to the content in the foregoing embodiments. The specific process of sending the second transaction information to the payment system in this embodiment can refer to the content of sending the first transaction information to the payment system in the foregoing embodiments, which will not be elaborated here.

[0143] If the user does not agree to register as a member or choose to pay by non-membership payment method, the server does not need to send the user's membership information to the payment system, and can send the transaction identification information representing the user's transaction account information to the payment system.

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

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

[0146] Execute a payment process based on the payment processing request to obtain payment result information;

[0147] Send the payment result information to the first device.

[0148] Among them, the payment result information can be result information indicating payment failure or result information indicating payment success. The specific process of the payment process can refer to related technologies and will not be elaborated here. The server can also feedback the payment result information to the payment system, such as devices with display functions such as POS machines and merchant cash registers.

[0149] In practical applications, if the tag information obtained by the first device contains information about the trading partner, or also includes information such as the transaction amount, the first device can send a payment request containing information about both trading parties to the server, and the server can also process the transaction based on the payment request sent by the first device. The information about both trading parties can include the account information or identification information of both trading parties, can also include the transaction amount information, can also include the type information of the traded product or the specific product name information, etc. In this way, the server can execute the transaction processing process based on the necessary information required for the transaction business, obtain the payment result information, and can also feedback the result information to both trading parties. In this way, the server does not need to send the user transaction identification information of the first device to the business system, nor does it need to generate transaction identification information, which can simplify the payment processing process and improve the payment efficiency.

[0150] In practical applications, to improve the security of payments, before the server executes the relevant steps for resource transfer between the two trading parties, it can also send information about the pending transaction to the first device, so that after the first device automatically confirms based on user authorization or the user manually confirms, the server executes the relevant steps for resource transfer between the two trading parties. 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 contains identification information representing the payment information to be confirmed;

[0152] Obtain the payment confirmation information provided by the first device, so that the server executes the corresponding payment processing process after receiving the payment confirmation information.

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

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

[0155] Based on the payment link information, send a payment confirmation message to the server so that the server can execute the corresponding payment processing process after obtaining the payment confirmation message.

[0156] Among them, the payment information to be confirmed may include the amount information to be paid, the information of the trading partner, 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 a preset rule. As an implementation manner, the payment link information may be a URL format information or a string in other formats that can be recognized by the first device. In practical applications, the target application in the first device may send a payment confirmation message to the server based on the payment link information. If, on the basis of 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 an implementation manner, after the first device obtains the payment link information, it may also display a payment confirmation page for the user to manually confirm the information to be paid. Optionally, in the embodiments of this specification, the first device may also perform the following steps:

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

[0159] Based on the fourth operation of the user on the payment confirmation page, send a payment confirmation message to the server.

[0160] Among them, the payment confirmation message is sent by the first device based on the fourth operation of the user 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. As Figure 9 shown, the payment confirmation page may include an area 902 for displaying payment information, which can specifically display the payment amount information, and can also display information such as the payment method, the trading party, and the trading time. The payment page may also include an operation control 904. If the user clicks on this control, it may indicate that the user agrees to make a payment, and the mobile terminal may generate a confirmation message. In practical applications, the operation control may be a control for payment confirmation or a control for canceling payment. If the user does not click on the control indicating canceling payment within a preset time period, it may also indicate that the user agrees to make a payment, and the mobile terminal may also generate a confirmation message for subsequent processes. As Figure 9As shown, the payment confirmation page may further include description information 906 for NFC payment, which is helpful for users to understand the advantages or usage methods of NFC payment.

[0162] In practical applications, the payment amount information included in the payment confirmation page may be the transaction amount determined by the merchant using the second device based on the actual transaction, or may be input by the user of the first device. For example, it may be input on this payment confirmation page, or may be input on a page for user input of the amount displayed before this payment confirmation page is displayed.

[0163] The fourth operation may represent the user's confirmation of the payment operation, which may be a substantial operation or a non-substantial operation. For example, the user Figure 9 The confirmation control shown or the control indicating cancellation of payment that is not clicked within a preset time period can both represent the user's confirmation of the payment operation.

[0164] The operations in the embodiments of this specification may refer to operations performed by the user's body, or may be operations performed according to voice, eye movement, etc. No specific limitation is made on the specific operation type here.

[0165] In practical applications, in order to improve the payment efficiency, when the user meets some preset conditions, such as the payment environment is safe, the user has authorized the first device or the server to confirm the payment information, etc., the first device may not display the payment confirmation page. Optionally, the first device in the embodiments of this specification may further perform the following steps:

[0166] Determine whether the user of the first device meets the preset payment conditions; the preset payment conditions represent the conditions for enabling fast payment.

[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 above display of the payment confirmation page may specifically include: if the user does not meet the preset payment conditions, then display the payment confirmation page.

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

[0170] As an implementation manner, the preset payment conditions may include at least one of having authorized the use of the express payment function, the user being a highly active user using the target application, and having authorized the use of the passwordless payment function.

[0171] Among them, the instant payment function can represent a payment function that does not require confirmation. For example, it can not display the payment confirmation page and other pages that require users to confirm information before the transaction result page, without or reducing the relevant operations for users to confirm payment, which is an extremely fast payment method. In practical applications, users can enable the instant payment function in the relevant settings page of the target application. If the user has authorized the use of the instant payment function, it can be determined that the user meets the preset payment conditions. When the user makes a payment through NFC, the payment confirmation page can not be displayed.

[0172] Highly active users can represent users whose activity level of using the payment application is greater than or equal to a preset threshold. In practical applications, the activity level of users can be calculated based on factors such as the duration and frequency of the user logging in to the payment application. It can also be determined based on the frequency of the user using the payment application to scan the payment code or output the payment code. For highly active users, a fast payment processing flow can be provided for the user, such as not displaying the payment page.

[0173] In practical applications, for highly active users, the instant payment function in the user's payment application can also be in the default enabled state, or a corresponding payment process can be provided for the user based on the state of the instant payment function.

[0174] The passwordless payment function can represent a function that does not require entering a password for payment. It can use biometric features such as fingerprints, faces, voiceprints, and irises as verification information for payment, or authorize the server to automatically execute when processing transactions for the user, without the user entering a password or biometric information for verification.

[0175] Considering that in practical applications, after the first device obtains the NFC tag information, it needs to parse the tag information before invoking the target application and then displaying the membership login page. The first device needs to execute some processes before displaying the membership login page. To improve the user experience, the first device can also display a transition page after obtaining the NFC tag information. Optionally, before the first device displays the membership login result page in the embodiments of this specification, the following steps can also be executed:

[0176] Display a login response page; the login response page contains a prompt message indicating that the user is logging in.

[0177] Figure 10 This is a schematic diagram of a login response page provided in the embodiments of this specification. As Figure 10 shown, the login response page can contain a prompt message 1002 indicating that the user is logging in. In practical applications, the login response page can also contain information such as the target application identifier and the merchant identifier. The login response page can be generated locally by the first device or generated based on the information fed back by the server.

[0178] As an implementation, the server may also send login response page information to the first device so that the first device can display the login response page.

[0179] After the server receives the member login request sent by the first device, it may first send the login response page information to the first device, and then send the login result information to the first device after the login process is completed.

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

[0181] Display a member prompt page; the member prompt page contains information prompting the user to log in as a member or information prompting the user to make a payment through the member.

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

[0183] Obtain a second operation of the user on the member prompt page; the second operation represents an operation of agreeing to use the target application.

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

[0185] Figure 11 This is a schematic diagram of a member prompt page provided in the embodiments of this specification. As Figure 11 shown, this page may include information 1102 prompting the user to log in as a member, such as the words "Click to log in as a member". The prompt information included in this page may be information prompting the user to make a payment through the member, such as information with the words "Click member payment".

[0186] As Figure 11 shown, the member prompt page may also include an operation control 1104. If the user performs an operation of agreeing to use the target application to log in as a member on this control, the first device may invoke the target application. The operation on the member prompt page may be a substantial operation or a non-substantial operation, which is not specifically limited here. The member prompt page may also contain identification information of the target application, such as name, logo, and other information.

[0187] If the target application is not installed in the mobile terminal or has been installed but the user has not yet registered and used it, after the user operates on the operation control 1102, it may also jump to the download page for the client of the target application or the page for registering and using the target application, 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 membership prompt page may also include a download control for downloading the control of the target application client. If the user clicks on this control, the first device can jump to display a download page for downloading the target application client, or the first device can download the target application from the application market. It can also display a prompt message indicating the download progress, and the download or installation can start in the background. After the download or installation is completed, a prompt message indicating the completion of the download or installation will be displayed.

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

[0190] As an implementation, if the first device is an Android system and the first device approaches the NFC tag and obtains the tag information, if the target application has been installed in the first device, the target application can be launched and the membership login page can be displayed.

[0191] In practical applications, it takes some time for the server to process the transaction business corresponding to the first device, such as 0.5 milliseconds, 1 second, 2 seconds, etc. 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 the embodiments of this specification. As Figure 12 shown, the payment response page may include a prompt message 1202 indicating that the payment is in progress, and may also include a prompt message 1204 for the payment method using near field communication, such as the words "NFC"; it may also include relevant description information about near field communication payment, etc., such as Figure 12 the words "tap to pay" as shown.

[0193] Among them, the payment response page can be generated locally on the first device or generated based on the response information fed back by the server. The payment response page can also include the progress information of the payment process, such as progress information in the form of a percentage, information in the form of a progress bar, and so on.

[0194] It can be understood that each display page in the embodiments of this specification can be a page displayed in a pop-up window, an H5 page, an application page in the target application, a network page, or a page in other forms, which is not specifically limited here. For example, the above-mentioned membership authorization login page can be displayed in the membership response page in the form of a pop-up window; the above-mentioned membership prompt page can be displayed in the form of a light application page or in the form of a notification page, and so on.

[0195] In practical applications, in order to improve the user experience and ensure user information security, the tag information in the NFC tag can be set to be readable only once. After the NFC tag information in the NFC tag is read, the tag information 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, which can be set according to actual business needs and is not specifically limited here.

[0196] In the embodiments of this specification, the target application can be an application with payment functions or other types of applications. In at least one embodiment of this specification, when the user needs to use membership payment, the user can bring the first device close to the NFC tag of the second device to obtain the tag information, and then use the target application to complete membership login and payment. Among them, after the user touches or brings the first device and the second device close to each other, the membership login and payment can be completed, and the whole process does not require too many operations. If the user has not registered as a member, the first device can display a membership login authorization page. After the user authorizes and agrees to register as a member, the first device and the server can register a member for the user and make a payment based on the user's authorization. The user can operate only on the membership login authorization page throughout the process and does not require too many operations, which can simplify the user operation steps.

[0197] In practical applications, in order to enable the user to perceive the payment, a payment confirmation page and other pages can also be displayed. It can be understood that the various display pages provided in this specification can be set according to actual needs as long as they conform to the business processing logic.

[0198] In the embodiments of 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, information indicating the 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 in the process of member login, information indicating that payment is in progress, etc. The second device can also reflect the information of various service processing stages in the form of voice broadcast, prompt sound, etc. The information displayed in the second device can be set according to actual needs, and no specific limitation is made here.

[0199] In practical applications, the first device can display the above-mentioned display pages in the unlocked state. For example, the user can first unlock the first device and then bring the first device close to the second device; the user can also first bring the first device close to the second device and then unlock the first device during the approach process or when in the approaching state.

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

[0201] Based on the same idea, the embodiments of this specification also provide a method with the server corresponding to the above-mentioned first device as the execution subject. Figure 13 It is a schematic flowchart of a method for displaying a member login page provided by the embodiments of this specification. As Figure 13 shown, the method may include the following steps:

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

[0203] Among them, the page information acquisition request is generated by the first device obtaining the tag information of the NFC tag of the second device through near-field communication; the tag information contains first information for invoking 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 label information in the second device can be generated by the server according to actual requirements. Specifically, it can include: obtaining a label information acquisition request sent by the second device; generating, based on the label information acquisition request, label information to be burned into the NFC label of the second device; the label information includes first information for invoking a target application and second information for executing a membership login process; sending the label information to the second device, and the second device can burn the label information into the NFC label so that the first device can obtain the label information through near-field communication and execute the membership login process.

[0207] Among them, the label information acquisition request can be sent by a merchant or the user himself after determining that the user needs to log in to the membership. For example, the second device can be operably connected to a cashier system or a device. The second device includes operable controls. For example, a cashier clicks a control representing membership payment on a cashier terminal. Another example is that in a self-service payment device, a user clicks a control representing membership login or payment. The second device or the cashier system can send a label information acquisition request to the server. The second device can be a part of the cashier system or a self-service payment device, or a device connected thereto.

[0208] The server can also feedback the label information to the second device, or feedback it to the cashier system, and then the cashier system sends it to the second device. The second device has the ability to burn NFC label information and can burn the obtained label information into the NFC label. In this way, the user of the first device can log in to the membership through the NFC method.

[0209] For the specific steps of the server to execute membership login or payment, reference can be made to the content in the foregoing embodiments, which will not be elaborated here.

[0210] Based on the same idea, the embodiments of this specification also provide a device corresponding to the above method. Figure 14 For the embodiments of this specification to provide corresponding to Figure 2 A schematic structural diagram of a device for displaying a membership login page. As Figure 14 shown, the device may include:

[0211] An information acquisition module 1402, configured to obtain label information of an NFC label of a second device through near-field communication; the label information includes first information for invoking a target application and second information for triggering a membership login process;

[0212] An application invocation module 1404, configured to invoke the target application in the first device based on the first information;

[0213] A request sending module 1406, configured to send a page information acquisition request to a server by using the target application based on the second information;

[0214] A page display module 1408, configured to acquire member login page information fed back by the server and display a member login page.

[0215] Based on Figure 14 For the device, some specific implementation solutions of the device are further provided in the embodiments of the present specification, and are described below.

[0216] Optionally, the page display module may specifically be configured to:

[0217] Acquire member login result information fed back by the server and display a member login result page; the member login result information is page information fed back 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 may specifically be configured to:

[0219] Acquire member authorization login page information fed back by the server and display a member authorization login page; the member authorization login page information is page information fed back 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, and may be configured to:

[0221] Acquire a first operation of a 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;

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

[0223] Acquire member login result information fed back by the server and display a member login result page.

[0224] Optionally, the first operation may further be an operation indicating that the user makes a payment by adopting a member payment method, and the request sending module may further be configured to:

[0225] Send a first payment trigger request to the server so that the server executes a corresponding payment processing flow.

[0226] Optionally, the page display module may include a second page display unit, and may be configured to:

[0227] Acquire a second operation of a user on a second control of the member authorization login page; the second operation is an operation indicating that the user agrees to make a payment by adopting a non-member payment method;

[0228] Send a second payment trigger request to the server so that the server executes the corresponding payment processing flow.

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

[0230] Obtain the payment result information fed back by the server;

[0231] Based on the payment result information, display a payment result page.

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

[0233] A link acquisition unit, configured to obtain payment link information provided by the server; the payment link information contains identification information representing the payment information to be confirmed;

[0234] A payment confirmation unit, configured to send a payment confirmation message to the server based on the payment link information, so that the server executes the corresponding payment processing flow after obtaining the payment confirmation message.

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

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

[0237] The above-mentioned payment confirmation unit may specifically be configured to send a payment confirmation message to the server based on a fourth operation of the user on the payment confirmation page.

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

[0239] A condition judgment unit, configured to judge whether the user of the first device meets a preset payment condition; the preset payment condition represents a condition that enables fast payment;

[0240] The above-mentioned page display unit may specifically be configured to display the payment confirmation page if the user does not meet the preset payment condition;

[0241] The above-mentioned display of the payment result page may specifically include: if the user meets the preset payment condition, display the payment result page.

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

[0243] Display a login response page; the login response page contains a prompt message indicating that the user is logging in.

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

[0245] Display a membership prompt page; the membership prompt page contains information prompting the user to log in as a member or information prompting the user to make a payment through the membership.

[0246] The above application invocation module can specifically be used for including:

[0247] Obtain a second operation of the user on the membership prompt page; the second operation represents an operation of agreeing to log in as a member using the target application.

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

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

[0250] Obtain the scenario parameter information in the second information;

[0251] Based on the scenario parameter information, generate a page information acquisition request;

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

[0253] Based on the same idea, Figure 15 For the embodiment of the present specification, it provides a structural schematic diagram of a device corresponding to Figure 13 for displaying a membership login page. As Figure 15 shown, the device may include:

[0254] A request acquisition module 1502, configured to acquire a page information acquisition request sent by a first device; the page information acquisition request is generated by the first device acquiring the tag information of the NFC tag of a second device through near-field communication; the tag information contains first information for invoking a target application and second information for executing a membership login process.

[0255] A page information sending module 1504, configured to send membership login page information to the first device based on the page information acquisition request, so that the first device displays a membership login page.

[0256] Based on Figure 15 the device, the embodiment of the present specification also provides some specific implementation schemes of the device, which are described below.

[0257] Optionally, the page information acquisition request includes the user identification information of the first device; the device may further include a judgment module, configured to judge 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 above page information sending module may include a first page information sending unit, configured to, if the judgment result indicates that the user is a member of the target object, send member login result information to the first device, so that the first device displays a member login result page.

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

[0260] Optionally, the above page information sending module may include a third page information sending unit, configured to:

[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 of 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 displays a member login result page.

[0263] Optionally, the request obtaining module may include a first payment request obtaining unit, the first operation further indicates an operation in which the user makes a payment by adopting a member payment method, and the first payment request obtaining unit may be configured to: obtain a first payment trigger request sent by the first device;

[0264] Based on the first payment trigger request, send the first transaction information of the user to the payment system of the trading party opposite to the first device; so that the payment system processes the payment service for the user based on the first transaction information; the first transaction information includes transaction identification information for indicating the transaction account information of the user and the member information of the user.

[0265] Optionally, the request obtaining module may include a second payment request obtaining unit, configured to: obtain 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 of 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 a payment by adopting a non-member payment method;

[0266] Based on the second payment trigger request, send the second transaction information of the user to the payment system associated with the second device; so that the payment system processes the payment service for the user based on the second transaction information; the second transaction information includes transaction identification information for representing the transaction account information of the user.

[0267] Optionally, the device may include a transaction processing module. If the judgment 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 first transaction information of the user to the payment system associated with the second device, so that the payment system processes the payment service for the user based on the first transaction information; the first transaction information includes transaction identification information for representing the transaction account information of the user and the membership information of the user.

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

[0269] Execute the payment process based on the payment processing request to obtain payment result information;

[0270] Send the payment result information to the first device.

[0271] Optionally, the transaction processing module may also be used to: send payment link information to the first device; the payment link information contains identification information representing the payment information to be confirmed;

[0272] Obtain the payment confirmation information provided by the first device, so that the server executes the corresponding payment processing process after receiving the payment confirmation information.

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

[0274] Based on the same idea, the embodiments of this specification also provide a device corresponding to the above method.

[0275] Figure 16 It is a schematic structural diagram of a device for displaying a member login page provided by the embodiments of this specification. As Figure 16 shown, the device 1600 may include:

[0276] At least one processor 1610; and,

[0277] A 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. The instructions are executed by the at least one processor 1610 so that the at least one processor 1610 can execute to implement the method for displaying the member login page as described above.

[0279] Based on the same idea, an embodiment of this specification also provides a computer-readable medium corresponding to the above method. Computer-readable instructions are stored on the computer-readable medium, and the computer-readable instructions can be executed by a processor to implement the method for displaying the member login page as described above.

[0280] Each embodiment in this specification is described in a progressive manner. For the same or similar parts among the embodiments, reference can be made to each other. Each embodiment focuses on the differences from other embodiments. In particular, for the above-mentioned device and equipment, since they are basically similar to the method embodiments, the description is relatively simple, and for the relevant parts, reference can be made to the partial 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 circuit structures such as diodes, transistors, switches, etc.) or software improvements (improvements to method flows). However, with the development of technology, many method flow improvements today can be regarded as direct improvements to hardware circuit structures. Designers almost always obtain the corresponding hardware circuit structure by programming the improved method flow into the hardware circuit. Therefore, it cannot be said that an improvement to a method flow cannot be implemented using a hardware entity module. For example, a Programmable Logic Device (PLD) (e.g., a Field Programmable Gate Array (FPGA)) is such an integrated circuit whose logical function is determined by the user programming the device. Designers can program themselves to "integrate" a digital system onto a single PLD without having to ask a chip manufacturer to design and fabricate a dedicated integrated circuit chip. Moreover, nowadays, instead of manually fabricating integrated circuit chips, this programming is mostly implemented using "logic compiler" software, which is similar to the software compiler used in program development and writing. The original code before compilation also has to be written in a specific programming language, which is called a Hardware Description Language (HDL). There is not just one type of HDL, but many, 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, RHDL (Ruby Hardware Description Language), etc. The most commonly used ones currently are VHDL (Very-High-Speed Integrated Circuit Hardware Description Language) and Verilog. Those skilled in the art should also be aware that by simply performing a little logical programming on the method flow using the above-mentioned several hardware description languages and programming it into an integrated circuit, it is easy to obtain the hardware circuit that implements the logical method flow.

[0282] The controller can be implemented in any suitable manner. For example, the controller can take the form of, for example, a microprocessor or a processor and a computer-readable medium storing computer-readable program code (such as software or firmware) executable by the (micro)processor, logic gates, switches, an application specific integrated circuit (ASIC), a programmable logic controller, and an embedded microcontroller. Examples of the controller include, but are not limited to, the following microcontrollers: ARC 625D, Atmel AT91SAM, Microchip PIC18F26K20, and Silicone Labs C8051F320. The memory controller can also be implemented as part of the control logic of the memory. Those skilled in the art also know that in addition to implementing the controller in the form of pure computer-readable program code, it is entirely possible to logically program the method steps to enable the controller to be implemented in the form of logic gates, switches, application specific integrated circuits, programmable logic controllers, and embedded microcontrollers to achieve the same function. Therefore, such a controller can be considered a hardware component, and the devices included therein for implementing various functions can also be regarded as the structures within the hardware component. Or even, the devices for implementing various functions can be regarded as either software modules for implementing the method or structures within the hardware component.

[0283] The systems, devices, modules, or units illustrated in the above embodiments can be specifically implemented by computer chips or entities, or by products with certain functions. A typical implementation device is a computer. Specifically, the computer can be, for example, a personal computer, a laptop computer, a cellular phone, a camera phone, a smart phone, 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 the convenience of description, the above devices are described by dividing them into various units according to their functions. Of course, when implementing the present application, the functions of each unit can be implemented in the same or multiple software and / or hardware.

[0285] Those skilled in the art should understand that the embodiments of the present invention can be provided as a method, a system, or a computer program product. Therefore, the present invention can take the form of a complete hardware embodiment, a complete software embodiment, or an embodiment combining software and hardware aspects. Moreover, the present invention can take the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk memories, CD-ROMs, optical memories, etc.) containing computer-usable program code.

[0286] The present 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 should be understood that each flow and / or block of the flowchart illustrations and / or block diagrams, and combinations of flows and / or blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions executed by the processor of the computer or other programmable data processing apparatus create means for implementing the functions specified in the flowchart Figure 1 for one or more of the flows and / or blocks Figure 1 and / or means for implementing the functions specified in one or more of the blocks.

[0287] These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means that implement the functions specified in the flowchart Figure 1 for one or more of the flows and / or blocks Figure 1 and / or means for implementing the functions specified in one or more of the blocks.

[0288] These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer-implemented process, such that the instructions executed on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart Figure 1 for one or more of the flows and / or blocks Figure 1 and / or means for implementing the functions specified in one or more of the blocks.

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

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

[0291] Computer readable media include permanent and non-permanent, removable and non-removable media that can be implemented by any method or technology to store information. Information can be computer readable instructions, data structures, program modules 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 technology, compact disk read-only memory (CD-ROM), digital versatile disk (DVD) or other optical storage, magnetic cassettes, magnetic disk storage or other magnetic storage devices or any other non-transmission media that can be used to store information that can be accessed by a computing device. As defined herein, computer readable media does not include temporary computer readable media (transitory media), such as modulated data signals and carrier waves.

[0292] It should also be noted that the terms "include", "comprises" or any other variations thereof are intended to cover non-exclusive inclusion, so that a process, method, commodity or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, commodity or device. In the absence of more restrictions, the elements defined by the sentence "comprises a ..." do not exclude the existence of other identical elements in the process, method, commodity or device including the elements.

[0293] Those skilled in the art will appreciate that the embodiments of the present application may be provided as methods, systems or computer program products. Therefore, the present application may adopt the form of a complete hardware embodiment, a complete software embodiment or an embodiment in combination with software and hardware. Moreover, the present application may adopt the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) that contain computer-usable program code.

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

[0295] The above are only embodiments of the present application and are not intended to limit the present application. For those skilled in the art, various changes and modifications can be made to the present application. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present application shall be included within the scope of the claims of the present application.

Claims

1. A member payment method, comprising: The first device obtains tag information of the NFC tag of the second device by means of near field communication; The tag information includes information for triggering a member login process and information for triggering a payment service processing process; Sending at least part of the tag information to a server; The server, when determining that the user of the first device is a member, executes the payment processing flow according to the member payment link; Obtain the payment result information fed back by the server and display the payment result page.

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, the method further comprises: Based on the information for activating the target application, the target application in the first device is activated.

3. The method according to claim 2, further comprising: The target application is used to send a page information acquisition request to the server.

4. The method according to claim 1, before displaying the payment result page, further comprising: Obtain member login result information fed back by the server, and display the member login result page; The member login result information is page information fed back 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, if the user of the first device is not a member of the target object, the method further comprises: Obtaining member authorization login page information fed back by the server, and displaying the member authorization login page; The member authorization login page information is page information fed back by the server after determining that the user of the first device is not a member of the target object.

6. The method according to claim 5, further comprising: Obtaining a first operation of a 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; Based on the first operation, sending a member login request to the server; Obtain the member login result information fed back by the server and display the member login result page.

7. The method according to claim 6, wherein the first operation further refers to an operation in which the user pays by using a member payment method, and the method further comprises: A first payment trigger request is sent to the server so that the server executes a corresponding payment processing flow.

8. The method according to claim 5, further comprising: Acquire a second operation of the user on a second control of the member authorization login page; The second operation is an operation indicating that the user agrees to pay by a non-member payment method; Send a second payment trigger request to the server so that the server executes the corresponding payment processing flow.

9. The method according to claim 1, before displaying the payment result page, further comprising: Display the payment response page; the payment response page is used to prompt the user that the payment is in progress.

10. The method according to claim 1, before obtaining the payment result information fed back by the server, further comprising: Acquire 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, payment confirmation information is sent to the server so that the server executes the corresponding payment processing flow after obtaining the payment confirmation information.

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

12. The method according to claim 11, wherein displaying a payment confirmation page based on the payment link information specifically comprises: Determining whether the user of the first device meets a preset payment condition; The preset payment conditions represent conditions that enable quick payment; The display of the payment confirmation page specifically includes: If the user does not meet the preset payment conditions, displaying the payment confirmation page; The payment result display page specifically includes: If the user meets the preset payment conditions, the payment result page is displayed.

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

14. The method according to claim 1, further comprising: Display member reminder page; The member reminder page contains information prompting the user to log in as a member or information prompting the user to make a payment through the member; Acquire a second operation of the user on the member prompt page; the second operation indicates consent to use the target application to log in as a member; Based on the second operation, the target application in the first device is invoked.

15. The method according to claim 3, wherein the step of using the target application to send a page information acquisition request to a server comprises: Obtaining the scenario parameter information in the information for triggering the member login process and the information for triggering the payment service processing process; Based on the scene parameter information, generate a page information acquisition request; Send the sending page information acquisition request to the server.

16. A member payment method, comprising: Acquire at least part 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 through near field communication; the tag information includes information for triggering a member login process and information for triggering a payment service processing process; Processing according to the member payment link according to at least part of the information in the tag information to generate payment result information; Send payment result information to the first device.

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

18. The method according to claim 16, before sending the payment result information, further comprising: The member login page information is sent to the first device so that the first device displays the member login page.

19. The method according to claim 18, further comprising: Determine whether the user of the first device is a member of the target object, and obtain a determination result; The sending of 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, member login result information is sent to the first device so that the first device displays a member login result page.

20. The method according to claim 19, further comprising: If the determination result indicates that the user is not a member of the target object, member authorization login page information is sent to the first device so that the first device displays the member authorization login page.

21. The method according to claim 20, further comprising: Obtaining a member login request sent by the first device; The member login request is generated by the first device based on a first operation of a 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; The member login result information is sent to the first device so that the first device displays the member login result page.

22. The method according to claim 21, wherein the first operation further refers to an operation in which the user pays by using a member payment method, and the method further comprises: Obtaining a first payment trigger request sent by the first device; Based on the first payment trigger request, the first transaction information of the user is sent to the payment system of the transaction party corresponding to the first device; so that the payment system processes the payment service for the user based on the first transaction information; the first transaction information includes transaction identification information for representing the transaction account information of the user and the membership information of the user.

23. The method according to claim 20, further comprising: Obtaining a second payment trigger request sent by the first device; The second payment triggering request is generated by the first device based on a second operation of the user on a second control of the member authorization login page; the second operation is an operation indicating that the user agrees to pay by a non-member payment method; Based on the second payment trigger request, the second transaction information of the user is sent to the payment system associated with the second device; so that the payment system processes the payment service for the user based on the second transaction information; the second transaction information includes transaction identification information for representing the transaction account information of the user.

24. The method according to claim 16, further comprising: Sending first transaction information of a user of the first device to a payment system associated with the second device so that the payment system processes payment services for the user based on the first transaction information; the first transaction information includes transaction identification information for representing the transaction account information of the user and the membership information of the user.

25. The method according to claim 24, further comprising: Acquire user identification information sent by the first device; Determining a user transaction account of the user according to the user identification information; Generate the transaction identification information corresponding to the user transaction account.

26. The method according to claim 16, further comprising: Obtaining a payment processing request generated by the payment system based on the transaction identification information, so that the server executes the payment process based on the payment processing request and obtains payment result information; The transaction identification information is used to indicate transaction account information of a user of the first device.

27. The method according to claim 16, further comprising: Sending payment link information to the first device; The payment link information includes identification information indicating payment information to be confirmed; Acquire the payment confirmation information provided by the first device so that the server executes the corresponding payment processing flow after acquiring the payment confirmation information.

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

29. A member payment device, comprising: An information acquisition module, used to acquire tag information of an NFC tag of a second device by means of near field communication; The tag information includes information for triggering a member login process and information for triggering a payment service processing process; A sending module, used for sending at least part of the tag information to a server; The server, when determining that the user of the first device is a member, executes the payment processing flow according to the member payment link; The page display module is used to obtain the payment result information fed back by the server and display the payment result page.

30. A member payment device, comprising: An information acquisition module, used to acquire at least part 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 through near field communication; the tag information includes information for triggering a member login process and information for triggering a payment service processing process; A payment processing module, configured to process at least part of 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.

31. A member payment device, 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, and the instructions are executed by the at least one processor to enable the at least one processor to perform the member payment method described in any one of claims 1 to 28.

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

Images