Method, apparatus and device for displaying member login page, and medium

Abstract

Disclosed in embodiments of the present description are a method, apparatus and device for displaying a member login page, and a medium. The solution may comprise: a first device acquiring tag information of a near-field communication (NFC) tag of a second device by means of NFC, the tag information including first information for invoking a target application and second information for triggering a member login process; on the basis of the first information, invoking the target application in the first device; on the basis of the second information, using the target application to send a page information acquisition request to a server; and acquiring member login page information fed back by the server, and displaying a member login page.

Description

Method, device, equipment and medium for displaying member login page

[0001] The present application claims priority from the Chinese patent application No. 2024110697858 filed on August 5, 2024, and entitled "Method, device, equipment and medium for displaying member login page", the content of which is incorporated herein by reference in its entirety. TECHNICAL FIELD

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

[0003] In order to better provide services for users, more and more businesses adopt member mechanism, for example, merchants provide various benefits or preferential activities for members; for another example, some service providers provide richer reading information, videos, audio information and the like for member users.

[0004] How to provide a more convenient member login method is a technical problem to be solved.

[0005] SUMMARY

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

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

[0008] The method for displaying member login page provided by the embodiments of the present specification comprises:

[0009] The first device obtains the tag information of the NFC tag of the second device through near field communication; the tag information contains the first information for arousing the target application and the second information for executing the member login process;

[0010] Based on the first information, the target application in the first device is aroused;

[0011] Based on the second information, the target application sends a page information acquisition request to the server;

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

[0013] The method for displaying member login page provided by the embodiments of the present specification comprises:

[0014] acquire a page information acquisition request sent by a first device; the page information acquisition request is generated by the first device through a near field communication mode to acquire tag information of an NFC tag of a second device; the tag information contains first information used to arouse a target application and second information used to execute a member login process;

[0015] based on the page information acquisition request, send member login page information to the first device, so that the first device displays a member login page.

[0016] An apparatus for displaying a member login page provided by an embodiment of the present specification comprises:

[0017] An information acquisition module is configured to acquire tag information of an NFC tag of a second device through a near field communication mode; the tag information contains first information used to arouse a target application and second information used to trigger a member login process;

[0018] An application arousing module is configured to arouse the target application in the first device based on the first information.

[0019] A request sending module is configured to send a page information acquisition request to a server by using the target application based on the second information.

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

[0021] An apparatus for displaying a member login page provided by an embodiment of the present specification comprises:

[0022] A request acquisition module is configured to acquire a page information acquisition request sent by a first device; the page information acquisition request is generated by the first device through a near field communication mode to acquire tag information of an NFC tag of a second device; the tag information contains first information used to arouse a target application and second information used to execute a member login process;

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

[0024] An apparatus for displaying a member login page provided by an embodiment of the present specification comprises:

[0025] at least one processor; and

[0026] a memory in communication connection with the at least one processor; wherein

[0027] 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 a method of displaying a member login page.

[0028] The embodiment of the present specification provides a computer readable medium, which stores computer readable instructions, and the computer readable instructions can be executed by a processor to implement a method of displaying a member login page.

[0029] The embodiment of the present specification realizes the following beneficial effects: the first device obtains the tag information of the NFC tag of the second device through near field communication, and the first information and the second information in the tag information can be used to display a member login page, so that the user can display the member login page by placing the first device close to the second device, and the user can log in to the member more conveniently. BRIEF DESCRIPTION OF DRAWINGS

[0030] In order to more clearly illustrate the technical solutions in the embodiments of the present specification or the prior art, the following will briefly introduce the drawings needed to be used in the embodiment or prior art description. Obviously, the drawings in the following description are only some embodiments described in the present application, and for those skilled in the art, other drawings can also be obtained without creative labor.

[0031] Fig. 1 is a schematic diagram of an application scenario of a method of displaying a member login page in the embodiment of the present specification;

[0032] Fig. 2 is a flowchart of a method of displaying a member login page provided by the embodiment of the present specification;

[0033] Fig. 3 is a swim lane diagram of a method of displaying a member login page provided by the embodiment of the present specification;

[0034] Fig. 4 is a schematic diagram of a member authorization login page provided by the embodiment of the present specification;

[0035] Fig. 5 is a schematic diagram of a member login result page provided by the embodiment of the present specification;

[0036] Fig. 6 is a schematic diagram of another member login result page provided by the embodiment of the present specification;

[0037] Fig. 7 is a schematic diagram of another member authorization login page provided by the embodiment of the present specification;

[0038] Fig. 8 is a schematic diagram of a payment result page provided by the embodiment of the present specification;

[0039] Fig. 9 is a schematic diagram of a payment confirmation page provided by the embodiment of the present specification;

[0040] Fig. 10 is a schematic diagram of a login response page provided in an embodiment of the present specification;

[0041] Fig. 11 is a schematic diagram of a member prompt page provided in an embodiment of the present specification;

[0042] Fig. 12 is a schematic diagram of a payment response page provided in an embodiment of the present specification;

[0043] Fig. 13 is a schematic diagram of a method for displaying a member login page provided in an embodiment of the present specification;

[0044] Fig. 14 is a schematic diagram of a structure of an apparatus for displaying a member login page corresponding to Fig. 2 provided in an embodiment of the present specification;

[0045] Fig. 15 is a schematic diagram of a structure of an apparatus for displaying a member login page corresponding to Fig. 13 provided in an embodiment of the present specification;

[0046] Fig. 16 is a schematic diagram of a structure of an apparatus for displaying a member login page provided in an embodiment of the present specification. DETAILED DESCRIPTION

[0047] In order to make the purpose, technical solutions and advantages of one or more embodiments of the present specification clearer, the technical solutions of one or more embodiments of the present specification will be described clearly and completely below in combination with specific embodiments of the present specification and corresponding drawings. Obviously, the described embodiments are only a part of the embodiments of the present specification, rather than all the embodiments. Based on the embodiments in the present specification, all other embodiments obtained by a person of ordinary skill in the art without making creative labor fall within the scope of protection of one or more embodiments of the present specification.

[0048] The technical solutions provided by the embodiments of the present specification will be described in detail below in combination with the drawings.

[0049] In the related art, if a user wants to log in as a member or open a membership, one way is that the user needs to first find the corresponding webpage or client or applet, then find the member portal, and then input some verification information such as account number, password, etc. to log in as a member. Another way is that the user scans a member code provided by a merchant through the code scanning capability of some client in the mobile phone to log in as a member. These ways all need the user to first find the webpage or client or applet, or open the corresponding client to scan the code to display the member login page, which is relatively cumbersome to operate.

[0050] In order to solve the defects in the prior art, the present scheme provides the following embodiments:

[0051] Figure 1 is a schematic diagram of an application scenario of a method for displaying a member login page according to an embodiment of the present specification. As shown in Figure 1, the scheme can include a first device 1, a second device 2 and a server 3. The first device 1 can obtain the tag information of the NFC tag of the second device 2 by means of close proximity, such as pasting or touching, using the near field communication function. The first device 1 can use the tag information to invoke a target application in the first device and display the member login page information obtained from the server 3 in the target application.

[0052] Next, a method for displaying a member login page provided by an embodiment of the present specification will be described in detail in conjunction with the accompanying drawings:

[0053] Figure 2 is a flowchart of a method for displaying a member login page according to an embodiment of the present specification. From a program perspective, the execution subject of the flow can be a program or application client installed in the first device. From a hardware perspective, the execution subject of the flow can be a first device with near field communication function. The first device can be a mobile phone, a smart watch, a smart bracelet, a mobile computer, a wearable smart device, etc., and can also be other mobile terminals, and the specific type of the device is not limited here.

[0054] As shown in Figure 2, the flow can include the following steps:

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

[0056] The tag information contains first information for invoking a target application and second information for triggering a 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 it can be separated from the second device and connected by wired or wireless means. 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 referred to as an NFC card, which has components such as NFC chip, coil, etc.

[0057] In the specification, the first device can act as a card reader. When the NFC switch is turned on, the first device sends a signal in a low power card detection (LPCD) mode or a mixed mode of the LPCD mode and normal card detection. When the first device is close to the second device, for example, when the first device is in contact with or attached to the second device, the tag coil in the NFC tag has an influence on the amplitude or phase of the LPCD signal of the first device. The first device can determine that there is a tag nearby according to the influence, and then initiate an inquiry and enter an interaction process. The interaction process can be a command interaction and a data interaction. For example, the first device can obtain information in the NFC tag. For details of the NFC interaction process, refer to related technologies, which are not described herein.

[0058] The first information and the second information can be characters or strings in a preset format, for example, can be link information such as a URL (Universal Resource Locator) starting with http or https, or can be other forms of characters or strings that can be recognized by the first device. The first information and the second information can be information in the same string, or can be independent characters or strings, and are not specifically limited.

[0059] Step 204: arousing the target application in the first device based on the first information.

[0060] The first information is information for arousing the target application, and specifically can be an identifier of the target application, for example, a package name, a package signature, or the like, or can be other information agreed by the first device. The first device can start the target application based on the identifier. The target application can be an application client APP, can be an applet, or can be a system application, and the like. In actual application, the OS (Opening System) of the first device can arouse the corresponding target application according to the application package name.

[0061] Step 206: sending a page information acquisition request to a server by using the target application based on the second information.

[0062] The second information is information for triggering a member login process. The operating system of the first device can provide the second information to the target application. The target application can trigger the member login process based on the second information. It can be understood that the client application program of the target application can execute a process related to member login according to the second information. As an implementation manner, the second information can include information of a jump 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 a server according to the second information, and can also receive information fed back by the server.

[0063] Step 208: obtaining the member login page information fed back by the server, and displaying the member login page.

[0064] The server is a server capable of providing services for the target application. The server can determine the corresponding member login page information according to the page information acquisition request sent by the target application, and feed back the member login page information to the target application.

[0065] In actual application, different merchants or member service providers can set member login pages according to actual needs. Optionally, the second information can include identification information of the member service provider, for example, identification information of the merchant served by the second device. The server can determine the corresponding member login page information according to the identification information, and the first device can display the corresponding member login page.

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

[0067] In the method in FIG. 2, the first device obtains the tag information of the NFC tag of the second device through near field communication, and displays the member login page by using the first information and the second information in the tag information. In this way, the user can display the member login page by placing the first device close to the second device, so that the user can log in to the member more conveniently.

[0068] The member login page described in the embodiments of the present specification can be one page or multiple associated pages. As an implementation manner, if the user of the first device is already a member of the member service provider, the first device can display a login result page after obtaining the NFC tag information. If the user is not yet a member of the member service provider, a member authorization login page can be displayed to prompt the user to authorize to become a member, so as to determine the user as a member after obtaining the authorization of the user. On the basis that the first device or the server saves the related member information, if the user logs in to the member again next time, the first device can not display the member authorization login page, but can directly display the member login result page after the user uses the first device to paste the second device.

[0069] In order to more clearly illustrate the method for displaying the member login page information provided in the embodiments of the present specification, FIG. 3 is a swim lane diagram of a method for displaying a member login page provided in an embodiment of the present specification. As shown in FIG. 3, the method can include the following steps.

[0070] Step 302: The second device has a NFC tag containing tag information.

[0071] In practical application, the second device can be a device used by the member-providing service provider, or a device connected with the management system of the member-providing service provider. The member-providing service provider can burn the 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 member-providing service provider can be an object providing member services, such as some merchants with member services, such as supermarkets, shopping malls, bookstores, restaurants, hospitals, social service agencies, etc., or some public or non-public organizations, such as reading clubs, sports clubs, etc.

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

[0073] The tag information can include first information for arousing the target application and second information for triggering the member login process.

[0074] Step 306: Based on the first information, the target application in the first device is aroused.

[0075] Step 308: Based on the second information, the target application sends a page information acquisition request to the server.

[0076] In practical application, different member-providing service providers can correspond to different member login pages. Optionally, as an implementation manner, the above-mentioned sending a page information acquisition request to the server based on the second information by using the target application can specifically include:

[0077] Acquiring the scene parameter information in the second information;

[0078] Generating a page information acquisition request based on the scene parameter information;

[0079] Sending the page information acquisition request to the server.

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

[0081] Step 310: The server acquires the page information acquisition request sent by the first device.

[0082] The page information acquisition request is a request for the server to feed back information related to the member login.

[0083] Step 312: Based on the page information acquisition request, the member login page information is sent to the first device.

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

[0085] In actual application, the server can also feed back different page information for users in different states. For example, if the user has not registered before or has not authorized the registration of the target object corresponding to the second device by the NFC communication method, the server can feed back a page prompting the user to register or authorize to become a member; if the user is already a member of the target object or has authorized to become a member by the NFC communication method before, that is, there is record information of the user as a member in the server, there is no need to feed back a page prompting the user to register or authorize to become a member, and the login result page can be fed back to the first device so as to inform the user whether he has logged in as a member.

[0086] As an implementation mode, the page information acquisition request can include user identification information of the first device, for example, device identification information of the first device, or user identification information of the user in the first device or the target application, such as UID (User Identification, user identifier), mobile phone number, email account, application account, social account, etc. Before sending the member login page information to the first device, the server can further perform step 3122: based on the user identification information, judging whether the user of the first device is a member of the target object, and obtaining a judgment result.

[0087] Optionally, if the judgment result indicates that the user is not a member of the target object, the server can further perform step 3124: sending member authorization login page information to the first device.

[0088] Correspondingly, the step 314 performed by the first device to acquire the member login page information fed back by the server and display the member login page can further include step 3142: acquiring the member authorization login page information fed back by the server and displaying the member authorization login page.

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

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

[0091] FIG. 4 is a schematic diagram of a member authorization login page provided in an embodiment of the present specification. As shown in FIG. 4, the member authorization login page can include information 402 indicating content that the user needs to authorize, and the user can also view the specific authorization agreement content. The member authorization login page can also include a control 404 indicating confirmation of member login. If the user clicks the control, the target application can register the user as a member of the target object by using the user's mobile phone number and other information. For example, the target application can send a member registration request containing the user information to a server or system for managing member information. The server or system can record the user information of the user, and can also record information such as member benefits enjoyed by the user. The server for managing member information can be the same server as in the embodiment of the present specification or can be a different server.

[0092] As shown in FIG. 4, the member authorization login page can also include a control 406 indicating exit from member login. If the user clicks the 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 can also include identification information 408 of the target object, and so on.

[0093] Optionally, the method in the embodiment of the present specification can further include step 3146: the first device obtains a first operation of the user on the member authorization login page, and sends a member login request to the server.

[0094] The first operation is an operation indicating that the user agrees to become a member of the target object. Specifically, it can be a first operation on a first control of the member authorization login page, or an operation performed according to a preset operation instruction, or a substantial operation, or a non-substantial operation of the type of inaction. For example, in the process of displaying a prompt message for canceling authorization in a countdown manner, the user does not perform an operation indicating canceling of authorization for member login or registration, which can indicate that the user agrees to authorization for login or registration as a member.

[0095] Correspondingly, the server can perform step 3126: obtaining the member login request sent by the first device.

[0096] The member login request is generated by the first device based on a first operation of a first control of the member authorization login page by the user. The server can perform a member registration or login process according to the member login request sent by the first device, record the user as a member of the target object, or a member in a login state.

[0097] Step 3128: sending member login result information to the first device.

[0098] The server can generate member login result information according to the result of the member login of the user and feed back to the first device. In actual application, the server can interact with the device or system of the member service provider to complete the login or registration of the user member. For example, the obtained user information can be provided to the device or system of the member service provider, so that the member service provider can mark the user as a member user. The server can also independently complete the member registration or login. The specific member registration or login process is not limited and described here, and can be referred to the related implementation method.

[0099] Correspondingly, the first device can also perform step 3148: obtaining the member login result information fed back by the server and displaying a member login result page.

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

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

[0102] FIG. 5 is a schematic diagram of a member login result page provided in an embodiment of the present specification. As shown in FIG. 5, the page can include information 502 indicating the member login result. In actual application, if the login is successful, the login result page can display information indicating the login success, such as login success. If the login fails, information indicating the login failure can be displayed, such as login failure. Information indicating the reason for the login failure can also be displayed, such as login timeout. If the login fails, information prompting the user to log in again can also be displayed.

[0103] As shown in FIG. 5, the page can further include information 504 of the member service provider, such as the name of the merchant, logo information, and the like, and can also include identification information of the target application and the like. Identification information of near field communication, such as information of the NFC logo and the like, can also be included.

[0104] In actual applications, the login result page can automatically exit, such as the countdown information of "2 seconds" shown in FIG. 5. After the countdown ends, the login result page can automatically exit. The login result page can also exit based on the operation of the user. For example, the login result page can include an operation control. The user can click the control to exit the page or jump to another page.

[0105] FIG. 6 is a schematic diagram of another member login result page provided in the embodiments of the present specification. As shown in FIG. 6, the page can include information 602 indicating the login result of the member. The page can also include a control 604 for entering a member service page, and can also include a control 606 for exiting the current page. If the user clicks the control 604, the first device can jump from the page to a member service page including member service information. The member service information can include member benefits available to the user, such as coupons, member points, member levels, and the like. If the user clicks the control 606, the member login result page can be exited.

[0106] In actual applications, at some merchants that provide member services, transactions can also be conducted using a member payment method. Users using the member payment method can enjoy some member benefits, such as preferential member prices, coupons, member points, and the like. The member login method provided in the embodiments of the present specification can also be applied to the application scenario of payment.

[0107] FIG. 7 is a schematic diagram of another member authorization login page provided in the embodiments of the present specification. As shown in FIG. 7, the member authorization login page can include a control 702 indicating agreement to register as a member and use a member payment method. If the user operates the control, it indicates that the user agrees to register as a member and agrees to make a payment, and the user can enjoy the benefits of the member payment method. One operation of the user on the control 702 can trigger a member registration login process, or can trigger a payment processing business process.

[0108] As shown in FIG. 7, the member authorization login page can also include a control 704 indicating a non-member payment method. If the user operates the control, it indicates that the user does not authorize registration as a member, but agrees to make a payment, and a payment processing business process can be triggered. In actual applications, the member authorization login page can also include a control indicating exit from the member login result page, or a control indicating that the user cancels or disagrees with the member login.

[0109] It can be understood that the above is only a page example, and the specific page content can be set according to actual needs, which is not limited here.

[0110] Optionally, as shown in FIG. 3, the method in the embodiment of the present specification can further include step 316: sending a payment trigger request to the server.

[0111] The payment trigger request can be generated by the first device based on a preset operation of the user on the member login result page. The preset operation can represent the user's payment operation, which can be an operation indicating that the user agrees to pay in a non-member way, or an operation indicating that the user agrees to pay in a member way. As shown in the member authorization login page in FIG. 7, the first device can send a payment processing request to the server regardless of whether the user operates the control 702 indicating that the user agrees to register as a member and pay in a member way, or operates the control 704 indicating that the user pays in a non-member way.

[0112] Optionally, the server can further perform step 318: obtaining the payment trigger request and executing a payment processing procedure.

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

[0114] The server contains a program for processing payment requests by the user. After obtaining the payment trigger request sent by the first device, the server can execute a corresponding payment processing procedure. For example, the payment trigger request contains information of both parties of a transaction and information of the number of resources to be traded, and the server can transfer the resources of the payer to the account corresponding to the payee according to the request. For another example, the server can also send the user information of the first device to the system or device of the transaction counterpart, so that the transaction counterpart can generate order information and send it to the server. The server can also process the payment transaction between the first device and the transaction counterpart according to the order information provided by the transaction counterpart.

[0115] The transaction result information can be the result information obtained by the server processing the payment business, which can be information indicating a successful transaction or information indicating a failed transaction. The specific process of the server processing the payment business can be referred to related technologies, which will not be described in detail here.

[0116] Correspondingly, the first device can also perform step 322: displaying a payment result page.

[0117] The first device can obtain the payment result information fed back by the server, and display a payment result page based on the payment result information. The payment result page can contain the payment result information fed back by the server.

[0118] FIG. 8 is a schematic diagram of a payment result page according to an embodiment of the present specification. As shown in FIG. 8, the transaction result page can include information 802 of the payment result, such as payment success, payment failure, etc., and can also include payment information 804 such as payment amount, payment method, transaction party, and discount information, etc. The transaction result page can also include a control 806 for closing the transaction result page, such as a "complete" control. In actual applications, the specific content and format of the transaction result page can be set according to actual needs, which is not limited here.

[0119] The second information in the label information of the embodiments of the present specification can include information for triggering a member login process, and can also include information for triggering a payment business processing process, for example, can contain some preset characters. The first device can send at least part of the information in the label information to the server, and the server can trigger the payment business processing process in the case of determining that the user is a member or not a member according to some preset characters.

[0120] As an implementation manner, the first operation of the user on the member authorization login page acquired by the first device can also represent an operation of the user to pay by using a member payment method. Optionally, the first device can further perform the following steps:

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

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

[0123] In actual applications, to simplify user operations, the first payment trigger request can also be generated based on the first operation of the user on the member authorization login page, that is, the user performs one first operation, which can trigger member registration and login, or can trigger a payment process. The first device can send a member login request to the server based on the first operation, or can send a first payment trigger request to the server. The two requests can be sent to the server as one request, or can be sent to the server respectively.

[0124] Correspondingly, the server can also perform a processing step of the first payment trigger request. Optionally, the first device can further perform the following steps:

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

[0126] Based on the first payment trigger request, the first transaction information of the user is sent to a payment system of a transaction party opposite to the first device; so that the payment system processes payment service for the user based on the first transaction information; the first transaction information includes transaction identification information representing transaction account information of the user and member information of the user.

[0127] The payment system can represent a system for managing payment service of another party in transaction with the first device, and can also be understood as a payment system of a transaction counterparty, which can also be referred to as a cash register system, such as a merchant cash register, a merchant cash register, etc., or 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 can process the payment and also feed back the transaction result to the transaction parties. For example, the cash register system, cash register device, self-service payment device, etc. set in supermarkets, shopping malls and the like, the cash register system can determine the user payment account for transaction based on the transaction identification information. If the cash register system is used for collection, the user payment account can represent a payment account, and if the cash register system is used for payment, the user payment account can represent a collection account. The cash register system can also correspond to a transaction account, and 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 the transaction request, for example, can deduct the corresponding resources from the user payment account and add them to the transaction account corresponding to the cash register system. After processing, the server can feed back the payment result information to the server. The specific transaction processing flow can be referred to related technologies, and the cash register system can process the transaction according to the existing processing flow, which will not be described in detail here.

[0128] In practical applications, the server can directly send the first transaction information to the payment system of the transaction party opposite to the first device, or send the first transaction information to the payment system through the second device, wherein the second device can send the first transaction information to the payment system through wired or wireless means. If the payment system can also read the NFC information, the second device can also burn the obtained first transaction information into the NFC tag, and then the payment system reads the information by using the NFC reading function.

[0129] 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 payment, the account can be a payment account, and if the tag information contained in the NFC tag identifies a payment process for collecting money, the account can be a collection account, which is not limited here. In practical applications, the target application can be a terminal application with payment function, and the user transaction account can also be a user account logged in the terminal application.

[0130] In actual application, 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 the transaction identification information according to actual transaction demand. The transaction identification information can be different in different payment processes.

[0131] As an implementation, the first device can send a payment trigger request containing 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.

[0132] The user identification information can be a user ID, and can also be a device identification of a mobile terminal, a user application identification of a user in a terminal application, and the like, which can be used to determine the identification information of a user transaction account. The server can determine a user transaction account according to the user identification information, and generate transaction identification information having a corresponding relationship with the user transaction account, so that the user transaction account can be used to process payment transactions according to the transaction identification information subsequently.

[0133] In actual application, the transaction identification information can also include a string representing a payment code, a string representing a transaction order number, and the like. The server can process transactions between the two parties according to the transaction identification information. The specific transaction identification information can be a string of characters, which can be a string of characters that can be recognized by a server used to process payment services, and can be a string of characters that conforms to the payment rules of a payment application. For example, the string of characters can start with 28, or can start with 25, 30, and the like. The length of the string of characters can be 16 to 24 characters, or can be other lengths of characters according to demand. The specific form of the string of characters is not limited here. The related content of the transaction identification information can also be referred to the related description in the foregoing embodiments.

[0134] The member information of the user can include user information used when registering as a member, such as a mobile phone number, a name, and the like, and can also include member identification information generated by the server for a member user, such as a card number of a member card, a member user number, and the like. The specific details can be referred to related technologies, which are not limited and elaborated here.

[0135] In the embodiments of the present specification, after determining that the user uses the member payment method, the server sends the transaction identification information of the user of the first device and the member information to the payment system. The transaction identification information and the member information can be contained in one piece of information and sent to the payment system, or can be sent to the payment system respectively.

[0136] In the embodiments of the present specification, the member authorization login page can include a control representing a non-member payment method. Optionally, the first device can further perform the following steps in the embodiments of the present specification:

[0137] obtaining a second operation of the user on the second control of the member authorization login page; the second operation is an operation indicating that the user agrees to pay in a non-member payment manner;

[0138] sending a second payment trigger request to the server, so that the server performs a corresponding payment processing procedure.

[0139] The second payment trigger request can represent a payment trigger request for paying in a non-member payment manner, and the server can process the request according to a non-member payment link.

[0140] Correspondingly, the server can further perform the following steps:

[0141] obtaining 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 the second control of the member authorization login page; the second operation is an operation indicating that the user agrees to pay in a non-member payment manner;

[0142] based on the second payment trigger request, sending second transaction information of the user to a payment system associated with the second device; so that the payment system processes a payment service for the user based on the second transaction information; the second transaction information includes transaction identification information used to represent transaction account information of the user.

[0143] The transaction identification information and the payment system can refer to the contents in the foregoing embodiments. The specific process of sending the second transaction information to the payment system in this embodiment can refer to the contents of sending the first transaction information to the payment system in the foregoing embodiments, which will not be described here.

[0144] If the user does not agree to register as a member or chooses to pay in a non-member payment manner, the server does not need to send member information of the user to the payment system, and can send transaction identification information representing transaction account information of the user to the payment system.

[0145] The server can process the payment service based on a request of the payment system and feed back payment result information. Optionally, the server in the embodiments of the present specification can perform the following steps:

[0146] obtaining a payment processing request generated by the payment system based on the transaction identification information;

[0147] performing a payment procedure based on the payment processing request to obtain payment result information;

[0148] sending the payment result information to the first device.

[0149] The payment result information can be result information indicating a payment failure or result information indicating a payment success. The specific process of the payment flow can be referred to the related art, which will not be repeated here. The server can also feed back the payment result information to the payment system, such as a POS machine, a merchant cash register, or other devices with a display function.

[0150] In actual application, if the label information obtained by the first device contains information of the transaction counterpart, or also contains transaction amount information, the first device can send a payment request containing transaction counterpart information to the server, and the server can also process the transaction based on the payment request sent by the first device. The transaction counterpart information can include account information or identification information of the transaction counterpart, and can also include transaction amount information, and can also include type information or specific product name information of the transaction product. In this way, the server can execute a transaction processing flow based on the necessary information required by the transaction service, obtain payment result information, and also feed back the result information to the transaction counterpart. In this way, the server does not need to send the user transaction identification information of the first device to the service system, and does not need to generate transaction identification information, which can simplify the payment processing flow and improve the payment efficiency.

[0151] In actual application, in order to improve the security of payment, the server can also send information to be transacted to the first device before executing the steps of transferring resources to the transaction counterpart, so that the server executes the steps of transferring resources to the transaction counterpart after the first device automatically confirms or the user manually confirms on the basis of user authorization. Optionally, the server in the embodiments of the present specification can also execute the following steps:

[0152] Send payment link information to the first device; the payment link information contains identification information indicating payment information to be confirmed;

[0153] Obtain payment confirmation information provided by the first device, so that the server executes a corresponding payment processing flow after obtaining the payment confirmation information.

[0154] Optionally, the corresponding first device can execute the following steps:

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

[0156] Based on the payment link information, send payment confirmation information to the server, so that the server executes a corresponding payment processing flow after obtaining the payment confirmation information.

[0157] The payment information to be confirmed can include payment amount information, information of a transaction counterpart, and the like, and the payment link information can include a character string representing the payment information to be confirmed or a character string obtained by processing the payment information to be confirmed according to a preset rule. As an implementation, the payment link information can be a URL format information or a character string in another format recognizable by the first device. In actual application, the target application in the first device can send payment confirmation information to the server based on the payment link information. If the user does not need to confirm on the basis of user authorization, the server can also not need to issue the payment link information to the first device.

[0158] As an implementation, after the first device obtains the payment link information, the first device can also display a payment confirmation page to manually confirm the payment information to be confirmed by the user. Optionally, the first device in the embodiments of the present specification can also perform the following steps:

[0159] displaying a payment confirmation page based on the payment link information, wherein the payment confirmation page includes the payment information to be confirmed;

[0160] sending payment confirmation information to the server based on a fourth operation of the user on the payment confirmation page.

[0161] 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.

[0162] FIG. 9 is a schematic diagram of a payment confirmation page provided in the embodiments of the present specification. As shown in FIG. 9, the payment confirmation page can include a region 902 for displaying payment information, which can specifically display payment amount information, and can also display payment method, transaction counterpart, transaction time, and the like. The payment page can also include an operation control 906. If the user clicks the control, it can indicate that the user agrees to pay, and the mobile terminal can generate confirmation information. In actual application, the operation control can be a control for confirming payment, or a control for canceling payment. If the user does not click the control for canceling payment within a preset time period, it can also indicate that the user agrees to pay, and the mobile terminal can also generate confirmation information to proceed with subsequent processes. As shown in FIG. 9, the payment confirmation page can also include description information 906 for NFC payment, so that the user can understand the advantages or use method of NFC payment.

[0163] In actual application, the payment amount information included in the payment confirmation page can be a transaction amount determined by a merchant using a second device according to an actual transaction, or can be input by the user of the first device, for example, can be input in the payment confirmation page, or can be input in a page for inputting the amount before displaying the payment confirmation page.

[0164] The fourth operation can represent a user confirmation payment operation, which can be a substantive operation or a non-substantive operation. For example, the user can confirm the payment operation by clicking the confirmation control shown in FIG. 9 or not clicking the control representing canceling the payment within a preset time length.

[0165] The operation in each embodiment of the present specification can refer to an operation performed by a user's limbs or an operation performed according to voice, eye movement, etc. The specific operation type is not limited herein.

[0166] In actual applications, in order to improve the payment efficiency, the first device can also not display the payment confirmation page when the user meets some preset conditions, such as a safe payment environment, the user has authorized the first device or the server to confirm the payment information, etc. Optionally, the first device in the embodiments of the present specification can further perform the following steps: judging whether the user of the first device meets a preset payment condition; the preset payment condition represents a condition capable of performing fast payment.

[0167] If the user meets the preset payment condition, the first device can not display the payment confirmation page; if the user does not meet the preset payment condition, the first device displays the payment confirmation page.

[0168] The above-mentioned display of the payment confirmation page can specifically include: if the user does not meet the preset payment condition, the payment confirmation page is displayed.

[0169] The above-mentioned display of the payment result page can specifically include: if the user meets the preset payment condition, the payment result page is displayed. That is, the payment confirmation page can not be displayed before the payment result page is displayed.

[0170] As an implementation manner, the preset payment condition can include at least one of the following: the user has authorized to use the super-fast payment function, the user is a high-active user of the target application, and the user has authorized to use the password-free payment function.

[0171] The super-fast payment function can represent a payment function without confirmation, such as not displaying the payment confirmation page and other pages requiring user confirmation of information before the transaction result page, and reducing or eliminating the related operation of the user to confirm the payment, which is an extremely fast payment method. In actual applications, the user can enable the super-fast payment function on the related setting page of the target application. If the user has authorized to use the super-fast payment function, it can be determined that the user meets the preset payment condition, and the payment confirmation page can not be displayed when the user performs payment through NFC.

[0172] The high-active user can represent a user whose active degree of using the payment application is greater than or equal to a preset threshold. In actual application, the active degree of the user can be calculated by the time length and frequency of the user logging into the payment application. The active degree of the user can also be determined based on the frequency of the user using the payment application to make a payment by scanning a code or outputting a payment code. For the high-active user, a quick payment processing flow can be provided for the user, for example, a payment page can not be displayed.

[0173] In actual application, for the high-active user, the express payment function in the payment application of the user can also be in a default enabled state, or the user can be provided with a corresponding payment flow based on the state of the express payment function.

[0174] The password-free payment function can represent a function of making a payment without inputting a password. The payment can be made by using a fingerprint, a face, a voiceprint, an iris, or the like as verification information. The payment can also be automatically executed without the user inputting a password or biological feature information for verification when the server processes a transaction for the user.

[0175] In actual application, after the first device obtains the NFC tag information, the first device needs to parse the tag information before invoking the target application to display the member login page. Before displaying the member login page, the first device needs to perform some processes. 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 member login result page in the embodiment of the present specification, the following steps can also be performed:

[0176] The login response page is displayed. The login response page includes prompt information indicating that the login is in progress.

[0177] FIG. 10 is a schematic diagram of a login response page provided in an embodiment of the present specification. As shown in FIG. 10, the login response page can include prompt information 1002 indicating that the login is in progress. In actual application, the login response page can also include target application identification, merchant identification, and the like. The login response page can be generated locally by the first device, or can be generated according to the information fed back by the server.

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

[0179] The server can first send the login response page information to the first device after obtaining the member login request sent by the first device, and then send the login result information to the first device after the login process is completed.

[0180] In order to ensure the security of the user information, before arousing the target application in the first device, the first device can further perform the following steps: displaying 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 pay through a member.

[0181] The above arousing the target application in the first device can specifically include:

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

[0183] Based on the second operation, arousing the target application in the first device.

[0184] FIG. 11 is a schematic diagram of a member prompt page provided in an embodiment of the present specification. As shown in FIG. 11, the page can include information 1102 prompting the user to log in as a member, such as the words "click to log in as a member". The prompting information contained in the page can be information prompting the user to pay through a member, such as the information of the words "click to pay as a member".

[0185] As shown in FIG. 11, the member prompt page can further include an operation control 1104. If the user performs an operation of agreeing to use the target application to log in as a member with respect to the control, the first device can arouse the target application. The operation with respect to the member prompt page can be a substantive operation or a non-substantive operation, which is not specifically limited here. The member prompt page can further contain identification information of the target application, such as the name, logo, and the like.

[0186] If the target application is not installed in the mobile terminal or has been installed but the user has not registered to use the target application, after the user operates the operation control 1102, the user can also jump to a download page of a client for downloading the target application or a page for registering to use the target application, so as to log in as a member using the target application or to pay after logging in as a member.

[0187] In actual applications, the member prompt page can further include a download control for downloading the client of the target application. If the user clicks the control, the first device can jump to display a download page for downloading the client of the target application, or the first device can download the target application from an application market, and can also display prompting information representing the download progress, or start background downloading or installation, and display prompting information representing that the downloading or installation is completed after the downloading or installation is completed.

[0188] As an implementation, if the first device is an iOS system, the first device is close to the NFC tag, and the tag information is obtained, a member prompt page can be displayed. The member prompt page can be displayed in the form of a Clips card or in the form of a notification bar. If the user performs an operation indicating consent to start the target application on the member prompt page, the first device can invoke the target application. The first device can perform a member login process based on the started target application, or can perform a member payment process, such as displaying a member login page. In actual applications, during the operation of the user on the member prompt page, the first device can collect the biometric information of the user as payment verification information. If the user submits information indicating confirmation of member login and payment based on the member prompt page, it can indicate that the user has confirmed the payment information, or the payment confirmation page can not be displayed. Of course, the payment confirmation page can also be displayed according to actual needs. If the user does not enable the fast payment function or does not meet the above-mentioned preset payment conditions, the first device can also display the payment confirmation page.

[0189] As an implementation, if the first device is an Android system, the first device is close to the NFC tag, and the tag information is obtained, if the target application has been installed in the first device, the target application can be started, and a member login page can be displayed.

[0190] In actual applications, the server needs some time to process the transaction business corresponding to the first device, for example, 0.5 m seconds, 1 second, 2 seconds, etc. In order to improve the user experience, the first device can also display a payment response page before displaying the payment result page, which can be used to prompt the user that the payment is being processed.

[0191] FIG. 12 is a schematic diagram of a payment response page provided in an embodiment of the present specification. As shown in FIG. 12, the payment response page can include prompt information 1202 indicating that the payment is being processed, and can also include prompt information 1204 of the payment method using near field communication, such as the NFC symbol; and can also include related description information of near field communication payment, etc., such as the symbol of “pay by tapping once” shown in FIG. 12.

[0192] Among them, the payment response page can be generated locally by the first device, or can be generated based on the feedback response information of the server. The payment response page can also include progress information of the payment process, such as percentage form progress information, progress bar form information, etc.

[0193] It can be understood that each display page in each embodiment of the present specification can be a page displayed in a pop-up window, can be an H5 page, can be an application page in a target application, can be a web page, or can be another form of page, which is not specifically limited here. For example, the above-mentioned member authorization login page can be displayed in the form of a pop-up window in the member response page; the above-mentioned member prompt page can be displayed in the form of a light application page, or can be displayed in the form of a notification page, and the like.

[0194] In actual application, in order to improve user experience and ensure user information security, the tag information in the NFC tag can be read only once, and 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, which is not specifically limited here.

[0195] In the embodiments of the present specification, the target application can be an application with payment function, or can be another type of application. In at least one embodiment of the present specification, when the user needs to use the member payment, the user can use the first device to approach the NFC tag of the second device, obtain the tag information, and then use the target application to complete the member login and payment, wherein the user can complete the member login and payment after the first device and the second device are pasted or touched, and the whole process does not need too many operations. If the user has not registered as a member, the first device can display a member login authorization page, and after the user authorizes and agrees to register as a member, the first device and the server can register the user as a member and perform payment on the basis of user authorization, and the whole process can be operated by the user only on the member login authorization page, without too many operations, which can simplify the user operation steps.

[0196] In actual application, in order to enable the user to have a perceptual payment, a payment confirmation page or the like can also be displayed. It can be understood that various display pages provided by the present specification can be set to be displayed according to actual needs, as long as they meet the business processing logic.

[0197] In the embodiments of the present specification, if the second device has a display screen, the server can also send login result information, payment result information, and the like to the second device, and the second device can also display information indicating the login result, information indicating the payment result, and the like. The second device can also display information indicating that the user is in the member login process, information indicating that payment is in progress, and the like before displaying the login result information and the payment result information. The second device can also embody information of various business processing stages in the form of voice broadcast, prompt sound, and the like. The display information in the second device can be set according to actual needs, which is not specifically limited here.

[0198] In actual application, 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 close process or after handling the close state.

[0199] If the system program of the first device can accurately analyze the content in the tag information, such as the tag information being a https form link, 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, and complete the member login or payment operation.

[0200] Based on the same idea, the embodiments of the present specification also provide a method with the server corresponding to the above-mentioned first device as the execution subject. FIG. 13 is a flow diagram of a method for displaying a member login page provided by the embodiments of the present specification. As shown in FIG. 13, the method can include the following steps:

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

[0202] The page information obtaining request is generated by the first device through the near field communication mode to obtain the tag information of the NFC tag of the second device. The tag information contains the first information for arousing the target application and the second information for executing the member login process.

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

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

[0205] In actual application, the tag information in the second device can be generated by the server according to actual needs. Specifically, it can include: obtaining a tag information obtaining request sent by the second device; based on the tag information obtaining request, generating tag information for burning into the NFC tag of the second device; the tag information contains the first information for arousing the target application and the second information for executing the member login process; send the tag information to the second device, the second device can burn the tag information into the NFC tag, so that the first device can obtain the tag information through the near field communication mode and execute the member login process.

[0206] The label information acquisition request can be sent by the merchant or the user himself after determining that the user needs to log in as a member. For example, the second device can be connected to a cash register system or device, and the second device includes an operable control, such as a control clicked by a cashier in a cash register terminal to indicate member payment, or a control clicked by the user in a self-service payment device to indicate member login or payment. The second device or the cash register system can send a label information acquisition request to the server. The second device can be part of the cash register system or the self-service payment device, or a device connected thereto.

[0207] The server can also feed back the label information to the second device, or to the cash register system, which then sends the label information to the second device. The second device has the ability to burn the NFC label information into the NFC label. In this way, the user of the first device can log in as a member through the NFC method.

[0208] The specific steps for the server to perform member login or payment can be found in the foregoing embodiments, which will not be described here.

[0209] Based on the same idea, the present specification also provides a device corresponding to the above method. FIG. 14 is a structural schematic diagram of a device for displaying a member login page according to an embodiment of the present specification. As shown in FIG. 14, the device can include:

[0210] An information acquisition module 1402 is configured to acquire label information of an NFC tag of a second device through a near field communication method; the label information includes first information for invoking a target application and second information for triggering a member login process;

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

[0212] A request sending module 1406 is configured to send page information acquisition requests to a server through the target application based on the second information;

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

[0214] Based on the device of FIG. 14, the present specification also provides some specific implementation solutions of the device, which will be described below.

[0215] Optionally, the page display module can be specifically configured to 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 target object.

[0216] Optionally, the page display module can be specifically configured to: 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 target member.

[0217] Optionally, the page display module can include a first page display unit, which can be configured to: acquire 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.

[0218] Based on the first operation, the member login request is sent to the server.

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

[0220] Optionally, the first operation can also indicate an operation of the user paying by using a member payment method, and the request sending module can be further configured to: send a first payment trigger request to the server, so that the server performs a corresponding payment processing procedure.

[0221] Optionally, the page display module can include a second page display unit, which can be configured to: 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 using a non-member payment method.

[0222] Send a second payment trigger request to the server, so that the server performs a corresponding payment processing procedure.

[0223] Optionally, the page display module can include a third page display unit, which can be configured to: acquire payment result information fed back by the server; and based on the payment result information, display a payment result page.

[0224] Optionally, the apparatus can further include a payment processing module, which can include:

[0225] A link acquisition unit configured to acquire payment link information provided by the server; the payment link information includes identification information indicating to-be-confirmed payment information.

[0226] A payment confirmation unit configured to send payment confirmation information to the server based on the payment link information, so that the server performs a corresponding payment processing procedure after acquiring the payment confirmation information.

[0227] Optionally, the payment processing module further comprises a page display unit configured to display a payment confirmation page based on the payment link information, wherein the payment confirmation page comprises payment information to be confirmed.

[0228] The payment confirmation unit is specifically configured to send payment confirmation information to the server based on a fourth operation of the user on the payment confirmation page.

[0229] Optionally, the payment processing module further comprises a condition judging unit configured to judge whether the user of the first device meets a preset payment condition, wherein the preset payment condition represents a condition capable of enabling fast payment.

[0230] The page display unit is specifically configured to display the payment confirmation page if the user does not meet the preset payment condition.

[0231] The display of the payment result page specifically comprises displaying the payment result page if the user meets the preset payment condition.

[0232] Optionally, the page display module further comprises a fourth page display unit configured to display a login response page, wherein the login response page comprises prompt information indicating that the login is in progress.

[0233] Optionally, the page display module further comprises a fifth page display unit configured to display a member prompt page, wherein the member prompt page comprises information prompting the user to log in as a member or information prompting the user to make payment as a member.

[0234] The application arousing module is specifically configured to include:

[0235] The application arousing module is specifically configured to include:

[0236] The application arousing module is specifically configured to include:

[0237] Optionally, the request sending module is specifically configured to include:

[0238] The request sending module is specifically configured to include:

[0239] The request sending module is specifically configured to include:

[0240] The request sending module is specifically configured to include:

[0241] Based on the same idea, FIG. 15 is a structural schematic diagram of an apparatus for displaying a member login page according to the embodiment of the present specification corresponding to FIG. 13. As shown in FIG. 15, the apparatus can include:

[0242] The request obtaining module 1502 is configured to obtain a page information obtaining request sent by a first device, wherein the page information obtaining request is generated by the first device through near field communication to obtain tag information of an NFC tag of a second device, and the tag information comprises first information used to arouse a target application and second information used to perform a member login process.

[0243] The page information sending module 1504 is configured to send member login page information to the first device based on the page information obtaining request, so that the first device displays a member login page.

[0244] Based on the apparatus in FIG. 15, some specific embodiments of the present application are provided, which are described as follows.

[0245] Optionally, the page information obtaining request comprises user identification information of the first device, and the apparatus further comprises a judgment module configured to judge whether the user of the first device is a member of a target object based on the user identification information, and obtain a judgment result.

[0246] The page information sending module can comprise a first page information sending unit configured to send member login result information to the first device if the judgment result indicates that the user is a member of the target object, so that the first device displays a member login result page.

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

[0248] Optionally, the page information sending module can comprise a third page information sending unit configured to:

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

[0250] send member login result information to the first device, so that the first device displays a member login result page.

[0251] Optionally, the request obtaining module can comprise a first payment request obtaining unit, the first operation further indicates an operation of the user to make payment by using a member payment mode, and the first payment request obtaining unit can be configured to:

[0252] obtaining a first payment trigger request sent by the first device;

[0253] based on the first payment trigger request, sending first transaction information of the user to a payment system of a transaction party opposite to the first device, so that the payment system processes payment service for the user based on the first transaction information; the first transaction information comprises transaction identification information representing transaction account information of the user and member information of the user.

[0254] Optionally, the request obtaining module can comprise a second payment request obtaining unit, which can be configured to:

[0255] obtaining 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 representing that the user agrees to make payment in a non-member payment manner;

[0256] based on the second payment trigger request, sending second transaction information of the user to a payment system associated with the second device, so that the payment system processes payment service for the user based on the second transaction information; the second transaction information comprises transaction identification information representing transaction account information of the user.

[0257] Optionally, the apparatus can comprise a transaction processing module, and 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 configured to: send first transaction information of the user to a payment system associated with the second device, so that the payment system processes payment service for the user based on the first transaction information; the first transaction information comprises transaction identification information representing transaction account information of the user and member information of the user.

[0258] Optionally, the transaction processing module can be further configured to:

[0259] obtaining a payment processing request generated by the payment system based on the transaction identification information;

[0260] based on the payment processing request, performing a payment process to obtain payment result information;

[0261] sending the payment result information to the first device.

[0262] Optionally, the transaction processing module can be further configured to: send payment link information to the first device; the payment link information comprises identification information representing to-be-confirmed payment information;

[0263] Obtain payment confirmation information provided by the first device, so that the server performs corresponding payment processing procedure after the payment confirmation information.

[0264] Optionally, 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.

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

[0266] FIG. 16 is a structural schematic diagram of a device for displaying a member login page according to an embodiment of the present specification. As shown in FIG. 16, the device 1600 can include:

[0267] at least one processor 1610; and

[0268] a memory 1630 in communication with the at least one processor; wherein

[0269] The memory 1630 stores instructions 1620 executable by the at least one processor 1610, and the instructions are executed by the at least one processor 1610 to enable the at least one processor 1610 to perform the above-mentioned method for displaying a member login page.

[0270] Based on the same idea, the embodiments of the present specification also provide a computer readable medium corresponding to the above method. The computer readable medium stores computer readable instructions, and the computer readable instructions can be executed by a processor to implement the above-mentioned method for displaying a member login page.

[0271] Each of the embodiments in the present specification is described in a progressive manner, and the same or similar parts between each embodiment can be referred to each other. Each embodiment focuses on the difference 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 the relevant parts can be referred to the part of the method embodiment.

[0272] In the 1990s, it was quite obvious to distinguish whether an improvement in a technology was in hardware (e.g., improvement in circuit structures of diodes, transistors, switches, etc.) or in software (improvement in method flow). However, as technology has evolved, many improvements in method flow today can be considered as direct improvements in hardware circuit structures. Designers almost always obtain the corresponding hardware circuit structures by programming the improved method flow into hardware circuits. Therefore, it cannot be said that an improvement in a method flow cannot be implemented by hardware entity modules. For example, a programmable logic device (PLD) (e.g., a field programmable gate array (FPGA)) is an integrated circuit whose logic function is determined by user programming of the device. A digital system is "integrated" on a PLD by the designer programming it, rather than by asking a chip manufacturer to design and fabricate a custom integrated circuit chip. Moreover, instead of manually fabricating integrated circuit chips, this programming is now mostly implemented by "logic compiler" software, which is similar to software compilers used in program development, and the original code to be compiled is written in a specific programming language, which is called a hardware description language (HDL), and there are many such languages, 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., and the most commonly used are VHDL (Very-High-Speed Integrated Circuit Hardware Description Language) and Verilog. Those skilled in the art should be aware that, as long as the method flow is logically programmed in the above-mentioned hardware description languages and programmed into an integrated circuit, a hardware circuit implementing the logical method flow can be easily obtained.

[0273] The controller can be implemented in any suitable way, for example, the controller can take the form of a microprocessor or 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 which 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 will also know that, in addition to being implemented in pure computer readable program code, the controller can also be implemented to perform the same functions in the form of logic gates, switches, application specific integrated circuits, programmable logic controllers and embedded microcontrollers, etc. by logically programming the method steps. Therefore, such a controller can be considered as a hardware component, and the means included therein for implementing various functions can also be considered as structures within the hardware component. Alternatively, the means for implementing various functions can even be considered as both a software module implementing a method and a structure within a hardware component.

[0274] The systems, apparatuses, modules or units illustrated by 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 a combination of any of these devices.

[0275] For the sake of description, the above apparatuses are described in functional division and are described respectively. Of course, the functions of the units can be implemented in the same or multiple software and / or hardware in the implementation of the present application.

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

[0277] The computer program instructions can 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 which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart block or blocks.

[0278] These computer program instructions can 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 instructions which implement the function specified in the flowchart block or blocks.

[0279] These computer program instructions can 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 which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart block or blocks.

[0280] In one typical configuration, the computing device includes one or more processors (CPUs), input / output interfaces, network interfaces, and memory.

[0281] The memory can include non-persistent memory and / or volatile memory, such as random access memory (RAM) and / or cache memory, for storing, in general, data and / or program instructions. The memory can also include non-volatile memory, such as read-only memory (ROM), electrically programmable read-only memory (EPROM), electrically erasable read-only memory (EEPROM), flash memory, or non-volatile random access memory (NVRAM), for storing, in general, data and / or program instructions. The memory is an example of computer readable media.

[0282] Computer-readable media includes permanent and non-permanent, movable and non-movable media that can be implemented by any method or technology to store information. The 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 technologies, compact disc read-only memory (CD-ROM), digital versatile disc (DVD) or other optical storage, magnetic cassette, magnetic tape disk storage or other magnetic storage devices, or any other non-transmission medium that can be used to store information accessible to a computing device. According to the definition herein, computer-readable media does not include transitory media such as modulated data signals and carriers.

[0283] It should also be noted that the terms "comprising", "containing", or any other variant thereof are intended to cover non-exclusive inclusion, such that a process, method, article or apparatus that comprises a list of elements does not only include those elements, but also other elements not explicitly listed or inherent to such process, method, article or apparatus. Without more limitations, the element defined by the statement "comprising a" does not exclude the presence of additional identical elements in the process, method, article or apparatus that includes the element.

[0284] Those skilled in the art will appreciate that embodiments of the present application can be provided as a method, system or computer program product. Accordingly, the present application can take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present application can take the form of a computer program product implemented on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROMs, optical storage devices, etc.) containing computer usable program code.

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

[0286] The above merely provides an example of the present application, and is not intended to limit the present application. Any modification, equivalent replacement, improvement, etc. within the spirit and principle of the present application should be included in the scope of claims of the present application.

Claims

1. A method for displaying a member login page, comprising: a first device acquires tag information of a NFC tag of a second device through near field communication; the tag information contains first information for arousing a target application and second information for triggering a member login process; based on the first information, the target application in the first device is aroused; based on the second information, the target application sends a page information acquisition request to a server; member login page information fed back by the server is acquired, and a member login page is displayed. 2.The method of claim 1, wherein the member login page information fed back by the server is acquired, and the member login page is displayed, specifically comprising: member login result information fed back by the server is acquired, and a member login result page is displayed; the member login result information is page information fed back by the server after determining that a user of the first device is a target member. 3.The method of claim 1, wherein the member login page information fed back by the server is acquired, and the member login page is displayed, specifically comprising: member authorization login page information fed back by the server is acquired, and a member authorization login page is displayed; 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 target member. 4.The method of claim 3, further comprising: a first operation of a user on a first control of the member authorization login page is acquired; the first operation is an operation indicating that the user agrees to become a member of the target object; based on the first operation, a member login request is sent to the server; member login result information fed back by the server is acquired, and a member login result page is displayed. 5.The method of claim 4, wherein the first operation further indicates an operation of the user paying by using a member payment method, and the method further comprises: a first payment trigger request is sent to the server; the server is configured to execute a corresponding payment processing procedure. 6.The method of claim 3, further comprising: a second operation of a user on a second control of the member authorization login page is acquired; the second operation is an operation indicating that the user agrees to pay by using a non-member payment method; a second payment trigger request is sent to the server; the server is configured to execute a corresponding payment processing procedure. 7.The method of any one of claims 2, 5, and 6, further comprising: payment result information fed back by the server is acquired; based on the payment result information, a payment result page is displayed. 8.The method of claim 7, wherein before the payment result information fed back by the server is acquired, further comprising: payment link information provided by the server is acquired; the payment link information contains identification information indicating to-be-confirmed payment information; based on the payment link information, payment confirmation information is sent to the server; the server is configured to execute a corresponding payment processing procedure after the payment confirmation information is acquired.

9. The method of claim 8, wherein the sending the payment confirmation information to the server based on the payment link information comprises: displaying a payment confirmation page based on the payment link information, wherein the payment confirmation page comprises payment information to be confirmed; and sending the payment confirmation information to the server based on a fourth operation of the user on the payment confirmation page.

10. The method of claim 9, wherein the displaying the payment confirmation page based on the payment link information comprises: determining whether the user of the first device meets a preset payment condition; wherein the preset payment condition represents a condition under which fast payment is enabled; and wherein the displaying the payment confirmation page comprises: displaying the payment confirmation page if the user does not meet the preset payment condition; and wherein the displaying the payment result page comprises: displaying the payment result page if the user meets the preset payment condition.

11. The method of claim 2 or 4, wherein the displaying the member login result page further comprises: displaying a login response page, wherein the login response page comprises prompt information indicating that the login is in progress.

12. The method of claim 1, wherein the invoking the target application in the first device further comprises: displaying a member prompt page, wherein the member prompt page comprises information prompting the user to log in as a member or information prompting the user to make a payment as a member; and wherein the invoking the target application in the first device comprises: obtaining a second operation of the user on the member prompt page, wherein the second operation represents an operation of agreeing to log in as a member using the target application; and invoking the target application in the first device based on the second operation.

13. The method of claim 1, wherein the sending a page information acquisition request to the server using the target application based on the second information comprises: obtaining scene parameter information in the second information; generating the page information acquisition request based on the scene parameter information; and sending the page information acquisition request to the server.

14. The method of claim 13, wherein the scene parameter information represents parameter information related to a member login scene, and the scene parameter information comprises at least one of the following: identification information of a target object that provides a member service, identification information of a second device, business identification information representing a member login business to be processed, and token information generated using a Token mechanism.

15. The method of claim 1, wherein the first information comprises identification information of the target application, and the identification information comprises at least one of the following: an application package name and a package signature.

16. The method of claim 10, wherein the preset payment condition comprises at least one of the following: authorization to use an express payment function, the user being a high-active user of the target application, and authorization to use a password-free payment function, wherein the express payment function represents a payment function that does not require confirmation, the high-active user represents a user whose activity level of using a payment application is greater than or equal to a preset threshold, and the password-free payment function represents a payment function that does not require input of a password. ​ ​ ​ ​ ​ ​ ​ ​ ​ ​ ​ ​ ​ ​ ​ ​ ​ 17. The method of claim 1, wherein the second information comprises identification information of a member-provided service provider; and wherein the member login page is a member login page corresponding to the member-provided service provider.

18. The method of claim 3, wherein the member authorization login page comprises at least one of information indicating content that needs to be authorized by a user, a control indicating confirmation of member login, a control indicating exit of member login, and identification information of a target object; or the member authorization login page comprises at least one of a control indicating agreement to register as a member and pay by using a member mode, a control indicating payment by using a non-member mode, a control indicating exit of a member login result page, and a control indicating cancellation or disagreement of member login by a user.

19. The method of claim 2, wherein the member login result page comprises at least one of information indicating success of login, information indicating failure of login, information indicating a reason for failure of login, information indicating a member-provided service provider, identification information indicating near field communication, countdown information, an operation control indicating exit of the page or jumping to another page, and a control for entering a member service page.

20. The method of claim 7, wherein the payment result page comprises at least one of information of a payment result, payment information, and a control for closing the payment result page; the information of the payment result comprises at least one of information indicating success of payment or failure of payment; and the payment information comprises at least one of a payment amount, a payment mode, a transaction party, and discount information.

21. The method of claim 8, wherein the payment link information is in a URL format.

22. The method of claim 8, wherein the payment information to be confirmed comprises at least one of information of an amount to be paid and information of a transaction party.

23. The method of claim 9, wherein the payment confirmation page comprises at least one of an area for displaying payment information, an operation control, and description information for NFC payment; the area for displaying payment information is used to display at least one of information of a payment amount, information of a payment mode, information of a transaction party, and information of a transaction time; the operation control comprises at least one of a control for confirming payment and a control for canceling payment; and the information of the payment amount comprises a transaction amount determined by a merchant using the second device according to an actual transaction or a transaction amount input by a user of the first device.

24. The method of claim 12, further comprising, if the first device does not have an installed client of a target application or has an installed client but a user has not registered to use the target application: displaying a download page for downloading the client of the target application or a page for registering to use the target application.

25. The method of claim 12, wherein the member prompt page comprises a control for downloading a client of the target application; or the member prompt page is displayed in at least one of a light application Clips card form and a notification bar form.

26. The method of claim 7, further comprising, before the payment result page is displayed: display a payment response page for prompting that a payment is being processed; the payment response page includes at least one of prompt information indicating that a payment is being processed, information indicating a payment method of using near field communication, and description information indicating a use method of near field communication payment.

27. The method of claim 1, wherein the tag information comprises information in a URL format.

28. The method of claim 1, wherein the second device presents at least one of information indicating a login result, information indicating a payment result, information indicating that a user is in a member login process, and information indicating that a payment is being processed, using at least one of a screen display, voice broadcasting, and a prompt sound.

29. A method for displaying a member login page, comprising: receiving a page information acquisition request sent by a first device; the page information acquisition request is generated by the first device by acquiring tag information of a NFC tag of a second device using near field communication; the tag information includes first information for invoking a target application and second information for performing a member login process; based on the page information acquisition request, sending member login page information to the first device; the first device is configured to display a member login page.

30. The method of claim 29, wherein the page information acquisition request includes user identification information of the first device; the method further comprises: based on the user identification information, determining whether a user of the first device is a member of a target object, to obtain a determination result; the sending of the member login page information to the first device specifically comprises: if the determination result indicates that the user is a member of the target object, sending member login result information to the first device; the first device is configured to display a member login result page.

31. The method of claim 30, further comprising: if the determination result indicates that the user is not a member of the target object, sending member authorization login page information to the first device; the first device is configured to display a member authorization login page.

32. The method of claim 31, further comprising: receiving 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 first control of the member authorization login page by a user; the first operation is an operation indicating that the user agrees to become a member of the target object; sending member login result information to the first device; the first device is configured to display a member login result page.

33. The method of claim 32, wherein the first operation further indicates an operation of the user making a payment by using a member payment method, the method further comprises: receiving a first payment trigger request sent by the first device; sending, based on the first payment trigger request, first transaction information of the user to a payment system of a transaction party opposite to the first device; the payment system being configured to process payment service for the user based on the first transaction information; the first transaction information comprising transaction identification information representing transaction account information of the user and member information of the user.

34. The method of claim 31, further comprising: obtaining a second payment trigger request sent by the first device; the second payment trigger request being 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 being an operation representing that the user agrees to make payment in a non-member payment manner; sending, based on the second payment trigger request, second transaction information of the user to a payment system associated with the second device; the payment system being configured to process payment service for the user based on the second transaction information; the second transaction information comprising transaction identification information representing transaction account information of the user.

35. The method of claim 30, if the judgment result indicates that the user is a member of the target object, the method further comprising: sending first transaction information of the user to a payment system associated with the second device; the payment system being configured to process payment service for the user based on the first transaction information; the first transaction information comprising transaction identification information representing transaction account information of the user and member information of the user.

36. The method of claim 33 or 34 or 35, further comprising: obtaining a payment processing request generated by the payment system based on the transaction identification information; performing a payment process based on the payment processing request to obtain payment result information; sending the payment result information to the first device.

37. The method of claim 36, before the obtaining the payment processing request generated by the payment system based on the transaction identification information, further comprising: sending payment link information to the first device; the payment link information containing identification information representing to-be-confirmed payment information; obtaining payment confirmation information provided by the first device and performing corresponding payment processing process.

38. The method of claim 37, the payment confirmation information being sent by the first device based on a fourth operation of the user on a payment confirmation page displayed in the first device based on the payment link information.

39. The method of claim 33 or 34 or 35, the transaction identification information comprising at least one of a string representing a payment code and a string representing a transaction order number.

40. The method of claim 33, the payment system representing a system of another party for managing payment service in a transaction with the first device, and the sending the first transaction information of the user to the payment system of the transaction party opposite to the first device specifically comprising: the second device sending the first transaction information to the payment system in a wired or wireless manner.

41. The method of claim 19, wherein the tag information comprises at least one of a transaction partner information and a transaction amount information; and the method further comprises: receiving a payment request sent by the first device, wherein the payment request comprises necessary information required for a transaction, and the necessary information comprises at least one of a transaction partner information, a transaction amount information, a transaction product type information, or a specific product name information; performing a transaction process based on the payment request; and obtaining a payment result information.

42. An apparatus for displaying a member login page, comprising: an information obtaining module configured to obtain tag information of a NFC tag of a second device via near field communication (NFC); the tag information comprises first information for invoking a target application and second information for triggering a member login process; an application invoking module configured to invoke the target application in the first device based on the first information; a request sending module configured to send a page information obtaining request to a server via the target application based on the second information; and a page displaying module configured to obtain member login page information fed back by the server and display a member login page.

43. An apparatus for displaying a member login page, comprising: a request obtaining module configured to obtain a page information obtaining request sent by a first device; the page information obtaining request is generated by the first device based on tag information of a NFC tag of a second device obtained via near field communication (NFC), and the tag information comprises first information for invoking a target application and second information for performing a member login process; a page information sending module configured to send member login page information to the first device based on the page information obtaining request; and the first device is configured to display a member login page.

44. An apparatus for displaying a member login page, comprising: at least one processor; and a memory connected with 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 method for displaying a member login page according to any one of claims 1 to 23.

45. A computer readable medium having computer readable instructions stored thereon, wherein the computer readable instructions are executable by a processor to implement the method for displaying a member login page according to any one of claims 1 to 41.

Images