A method, device, equipment and medium for displaying member login page

Abstract

The embodiments of this specification disclose a method, apparatus, device and medium for displaying a member login page. The scheme may include: a first device obtains tag information of an NFC tag of a second device through near field communication; the tag information includes first information for waking up 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 invoked; based on the second information, a page information acquisition request is sent to a server using the target application; the member login page information fed back by the server is obtained, and the member login page is displayed.

Description

Technical Field

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

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

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

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

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

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

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

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

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

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

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

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

[0013] Based on the page information acquisition request, the member login page information is sent to the first device so that the first device displays the member login page.

[0014] An embodiment of the present specification provides a device for displaying a member login page, including:

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

[0016] an application invoking module, configured to invoke the target application in the first device based on the first information;

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

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

[0019] An embodiment of the present specification provides a device for displaying a member login page, including:

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

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

[0022] The embodiment of this specification provides a device for displaying a member login page, including:

[0023] at least one processor; and,

[0024] a memory communicatively connected to the at least one processor; wherein,

[0025] The memory stores instructions that can be executed 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 for displaying a member login page.

[0026] An embodiment of the present specification provides a computer-readable medium on which computer-readable instructions are stored. The computer-readable instructions can be executed by a processor to implement a method for displaying a member login page.

[0027] An embodiment of the present specification realizes the following beneficial effects: a first device obtains tag information of an NFC tag of a second device by means of near field communication, and a member login page can be displayed using the first information and the second information in the tag information, so that a user can display the member login page by placing the first device close to the second device, making it more convenient for the user to log in as a member. BRIEF DESCRIPTION OF THE DRAWINGS

[0028] In order to more clearly illustrate the embodiments of this specification or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments recorded in this application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative labor.

[0029] Figure 1 This is a schematic diagram of an application scenario of a method for displaying a member login page in an embodiment of this specification;

[0030] Figure 2 A flowchart of a method for displaying a member login page provided in an embodiment of this specification;

[0031] Figure 3 A swimlane diagram of a method for displaying a member login page provided in an embodiment of this specification;

[0032] Figure 4 A schematic diagram of a member authorization login page provided in an embodiment of this specification;

[0033] Figure 5 A schematic diagram of a member login result page provided in an embodiment of this specification;

[0034] Figure 6 A schematic diagram of another member login result page provided in an embodiment of this specification;

[0035] Figure 7 This is a schematic diagram of another member authorization login page provided in an embodiment of this specification;

[0036] Figure 8 A schematic diagram of a payment result page provided in an embodiment of this specification;

[0037] Fig. 9 A schematic diagram of a payment confirmation page provided in an embodiment of this specification;

[0038] Fig.10 A schematic diagram of a login response page provided in an embodiment of this specification;

[0039] Fig.11 A schematic diagram of a member reminder page provided in an embodiment of this specification;

[0040] Fig.12 A schematic diagram of a payment response page provided in an embodiment of this specification;

[0041] Fig.13 A flowchart of a method for displaying a member login page provided in an embodiment of this specification;

[0042] Fig.14 The embodiments of this specification provide corresponding to Figure 2 A structural diagram of a device for displaying a member login page;

[0043] Fig.15 The embodiments of this specification provide corresponding to Fig.13 A structural diagram of a device for displaying a member login page;

[0044] Fig.16 A schematic diagram of the structure of a device for displaying a member login page provided in an embodiment of this specification. DETAILED DESCRIPTION

[0045] In order to make the purpose, technical solutions and advantages of one or more embodiments of this specification clearer, the technical solutions of one or more embodiments of this specification will be clearly and completely described below in combination with the specific embodiments of this specification and the corresponding drawings. Obviously, the described embodiments are only part of the embodiments of this specification, not all of the embodiments. Based on the embodiments in this specification, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of one or more embodiments of this specification.

[0046] The technical solutions provided by the embodiments of this specification are described in detail below in conjunction with the accompanying drawings.

[0047] In the related art, if a user wants to log in as a member or activate a membership, one way is that the user first needs to find the corresponding webpage, client or applet, then find the membership entrance, and then enter some verification information, such as account number, password, etc. before logging in as a member. Another way is that the user uses the code scanning capability of some clients in the mobile phone to scan the membership code provided by the merchant to log in as a member. These methods require the user to first find the webpage, client or applet, or open the corresponding client to scan the code before the member login page can be displayed, which is a cumbersome operation.

[0048] In order to solve the defects in the prior art, this solution provides the following embodiments:

[0049] Figure 1Schematic diagram of an application scenario of a method for displaying a member login page in an embodiment of this specification. Figure 1 As shown, the solution may include a first device 1, a second device 2, and a server 3. The first device 1 may obtain the tag information of the NFC tag by approaching the NFC tag of the second device 2, such as by sticking or touching it, using the near field communication function. The first device 1 may use the tag information to call up the target application in the first device, and display the member login page information obtained from the server 3 in the target application.

[0050] Next, a method for displaying a member login page provided in the embodiment of the specification is specifically described with reference to the accompanying drawings:

[0051] Figure 2 A flowchart of a method for displaying a member login page provided in an embodiment of this specification. From a program perspective, the execution subject of the process can be a program or application client installed in the first device. From a hardware perspective, the execution subject of the process can be a first device with a 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. The specific type of the device is not limited here.

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

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

[0054] The tag information includes first information for invoking the target application and second information for triggering the member login process. The second device may be a device associated with an NFC tag. For example, the NFC tag may be located on the second device, or may be separated from the second device and connected by wire or wirelessly. The first device has an NFC near-field communication function and may be used as an NFC card reader to obtain tag information of the NFC tag of the second device. An NFC tag may also be called an NFC card, which has components such as an NFC chip and a coil.

[0055] In this specification, the first device can be used as a card reader. When the NFC switch is turned on, it will send a signal in LPCD (Low Power Card Detection) mode, or a mixture of LPCD mode and normal card search. The first device is close to the NFC tag, such as touching or sticking to the second device. The tag coil in the NFC tag will affect the LPCD signal of the first device, in terms of amplitude or phase. The first device can determine that there is a tag nearby based on this impact, and then initiate an inquiry and enter the interaction process, which can be command interaction and data interaction. For example, the first device can obtain information in the NFC tag. For the specific NFC interaction process, please refer to the relevant technology, which will not be repeated here.

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

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

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

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

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

[0061] Step 208: Obtain the member login page information fed back by the server, and display the member login page.

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

[0063] In actual applications, different merchants or member service providers can set up member login pages that meet business needs based on actual needs. Optionally, the second information can include identification information of the member service provider, such as the identification information of the merchant served by the second device. The server can send the corresponding member login page information based on the identification information, and the corresponding member login page can be displayed in the first device.

[0064] It should be understood that the order of some steps in the method described in one or more embodiments of this specification can be interchanged according to actual needs, or some 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 may not be invoked.

[0065] Figure 2 In the method, the first device obtains the tag information of the NFC tag of the second device through near field communication, and uses the first information and the second information in the tag information to display the member login page, so that the user can bring the first device close to the second device to display the member login page, making it more convenient for the user to log in as a member.

[0066] In the embodiments of this specification, the above-mentioned member login page can be one page or multiple related pages. As an implementation method, if the user of the first device is already a member of the member providing service provider, the first device can display the login result page after obtaining the NFC tag information. If the user is not yet a member of the member providing service provider, a member authorization login page can be displayed to prompt the user to authorize to become a member, so that after obtaining the user's authorization, the user is determined to be a member. On the basis of the user authorizing the first device or server to save the relevant member information, if the user logs in as a member next time, after the user uses the first device to stick to the second device, the member authorization login page may not be displayed in the first device, and the member login result page may be directly displayed.

[0067] In order to more clearly illustrate the method of displaying information on the member login page provided in the embodiments of this specification, Figure 3 A swimlane diagram of a method for displaying a member login page provided in an embodiment of this specification, such as Figure 3 As shown, the method may include the following steps.

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

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

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

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

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

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

[0074] In actual applications, different member providing service providers may correspond to different member login pages. Optionally, as an implementation mode, based on the second information, using the target application to send a page information acquisition request to the server may specifically include:

[0075] Acquire scene parameter information in the second information;

[0076] Based on the scene parameter information, generate a page information acquisition request;

[0077] Send the sending page information acquisition request to the server.

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

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

[0080] The page information acquisition request is a request for requesting the server to feedback relevant information about member login.

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

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

[0083] In actual applications, the server can also feedback different page information for users in different statuses. For example, if the user has not registered before or has not authorized to register as a member of the target object corresponding to the second device through NFC communication, the server can feedback 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 been authorized as a member through NFC communication before, that is, the server has record information of the user as a member, there is no need to feedback 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 that the user knows whether he or she has logged in as a member.

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

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

[0086] Correspondingly, the first device executes step 314 of obtaining the member login page information fed back by the server and displaying the member login page, which may specifically include step 3142: obtaining the member authorization login page information fed back by the server and displaying the member authorization login page.

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

[0088] The member login page may include at least one of identification information of the target object corresponding to the member login page, information indicating content that the user needs to authorize, a control for confirming the member login, a control for exiting the member login, a control for payment using a member method, and a control for payment using a non-member method.

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

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

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

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

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

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

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

[0096] The server can generate member login result information based on the result of the member login for the user and feed it back to the first device. In actual applications, 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 acquired 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. Member registration or login can also be completed independently by the server. The specific member registration or login process is not specifically limited or repeated here, and you can refer to the relevant implementation method.

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

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

[0099] Correspondingly, the step 314 executed by the first device to obtain the member login page information fed back by the server and display the member login page may specifically include the step 3148: obtaining the member login result information fed back by the server and displaying the 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.

[0100] Figure 5 Schematic diagram of a member login result page provided in an embodiment of this specification. Figure 5 As shown, the page may include information 502 indicating the member login result. In actual applications, if the login is successful, the login result page may display information indicating the successful login, such as "Login Success"; if the login fails, information indicating the failed login, such as "Login Failed", and information on the reason for the failed login, such as "Login Timeout" may also be displayed; if the login fails, information prompting the user to log in again may also be displayed, and the like.

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

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

[0103] Figure 6 FIG. 1 is a schematic diagram of another member login result page provided in an embodiment of this specification. Figure 6 As shown, the page may include information 602 indicating the member login result. It may also include a control 604 for entering the member service page, and may also include a control 606 for exiting the current page. If the user clicks the control 604, the first device may jump from the page to the member service page containing member service information, and the page may contain member rights information that the user can enjoy, such as coupons, user member points, user member level, etc. If the user clicks the control 606, the member login result page may be exited.

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

[0105] Figure 7 FIG. 1 is a schematic diagram of another member authorization login page provided in the embodiments of this specification. Figure 7 As shown, the member authorization login page may include a control 702 indicating that the user agrees to register as a member and pay in a member manner. If the user operates the control, it means that the user agrees to register as a member and agrees to make the payment, and the user can enjoy the benefits of member payment. The user's operation on the control 702 can trigger the member registration and login process, and can also trigger the payment processing business process.

[0106] like Figure 7As shown, the member authorization login page may also include a control 704 indicating payment in a non-member mode. If the user operates the control, it means that the user has not authorized the member registration, but agrees to make the payment, and the payment processing business process may be triggered. In actual applications, the member authorization login page may also include a control indicating exiting the member login result page, or a control indicating that the user cancels or disagrees with the member login.

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

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

[0109] The payment trigger request may be generated by the first device based on a preset operation of the user on the member login result page. The preset operation may represent an operation of the user making a payment, an operation indicating that the user agrees to pay in a non-membership manner, or an operation indicating that the user agrees to pay in a member manner. Figure 7 In the member authorization login page shown, regardless of whether the user operates the control 702 indicating agreement to register as a member and pay in a member manner, or operates the control 704 indicating payment in a non-member manner, the first device can send a payment processing request to the server.

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

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

[0112] Among them, the server includes a program for processing user payment requests, and after obtaining the payment trigger request sent by the first device, the corresponding payment processing process can be executed. For example, the payment trigger request contains information about the two parties to the transaction and the amount of resources to be traded. According to the request, the server can transfer the payer's resources to the corresponding account of the payee. For another example, the server can also send the user information of the first device to the system or device of the transaction counterparty, so that the transaction counterparty 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 counterparty according to the order information provided by the transaction counterparty.

[0113] The transaction result information may be the result information obtained by the server processing the payment service, may be information indicating a successful transaction, or may be information indicating a failed transaction. The specific process of the server processing the payment service may refer to the relevant technology, which will not be described in detail here.

[0114] Correspondingly, the first device may also execute step 322: displaying a payment result page.

[0115] The first device may 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 may include the payment result information fed back by the server.

[0116] Figure 8 This is a schematic diagram of a payment result page provided in an embodiment of this specification. Figure 8 As shown, Figure 8 As shown, the transaction result page may include payment result information 802, such as payment success, payment failure, etc., and payment information 804 such as payment amount, payment method, transaction party, and preferential information; and may 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, and no specific limitation is made here.

[0117] The second information in the tag information of the embodiment of the present specification may include information for triggering a member login process, and may also include information for triggering a payment service processing process, for example, it may include some preset characters. The first device may send at least part of the information in the tag information to the server, and the server may trigger the payment service processing process based on some preset characters when determining whether the user is a member or not.

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

[0119] A first payment trigger request is sent to the server so that the server executes a corresponding payment processing flow.

[0120] The first payment trigger request may represent a payment trigger request for making payment in a member payment manner, and the server may process the request according to the member payment link.

[0121] In actual applications, in order 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 a first operation once, which can trigger member registration and login, and can also trigger the payment process. The first device can send a member login request to the server based on the first operation, and can also send a first payment trigger request to the server. These two requests can also be sent to the server as one request, or can be sent to the server separately.

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

[0123] Obtaining a first payment trigger request sent by the first device;

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

[0125] Among them, the payment system can represent the system for managing payment services of the other party to the transaction with the first device, and can also be understood as the payment system of the counterparty, which can also be called a cashier system, such as a merchant cashier counter, a merchant cashier counter, etc., or a payment device connected to the merchant cashier system, such as a second device. The payment system can send a payment request to the server based on the acquired transaction information, and the server performs payment processing and can also feedback the transaction results to both parties of the transaction. For example, cashier systems such as cashier counters, cashier equipment, self-service payment equipment, etc. set up in supermarkets, shopping malls, etc. The cashier system can determine the user payment account used for the transaction based on the transaction identification information. If the cashier system is used for collecting money, the user payment account can represent the payment account. If the cashier system is used for payment, the user payment account can represent the collection account. The cashier system can also correspond to a transaction account. The cashier system can generate a transaction request based on the acquired user payment account and the transaction account corresponding to the cashier system and send it to the server. The server can process the transaction request, for example, it can deduct the corresponding resources from the user payment account and add them to the transaction account corresponding to the cashier system. After the processing is completed, the server can feedback the payment result information to the server. For the specific transaction processing procedures, please refer to the relevant technologies. The cash register system can also process transactions according to the existing processing procedures, which will not be described in detail here.

[0126] In actual applications, the server can directly send the first transaction information to the payment system of the transaction party corresponding 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 in a wired or wireless manner. If the payment system can also read NFC information, the second device can also burn the acquired first transaction information into the NFC tag, and then the payment system can read the information using the NFC reading function.

[0127] 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 indicates a payment process for making a payment, the account can be a payment account. If the tag information contained in the NFC tag identifies a payment process for receiving a payment, the account can be a receiving account. This is not specifically limited here. In actual applications, the target application can be a terminal application with a payment function, and the user transaction account can also be a user account logged in to the terminal application.

[0128] In actual applications, the transaction identification information may be generated by the server according to the payment trigger request sent by the first device. The first device may request the server to generate the transaction identification information according to actual transaction requirements. The transaction identification information may be different in different payment processes.

[0129] As an implementation mode, the first device may send a payment trigger request including user identification information in the first device to the server; the server may generate transaction identification information for the user of the first device based on the acquired user identification information.

[0130] The user identification information may be a user ID, or may be a device identification of a mobile terminal, a user application identification of a user in a terminal application, or other identification information that can be used to determine a user transaction account. The server may determine the user transaction account based on the user identification information, and generate transaction identification information that corresponds to the user transaction account, so that the payment transaction may be processed using the user transaction account based on the transaction identification information.

[0131] In actual applications, the transaction identification information may also include a string representing a payment code, a string representing a transaction order number, etc. The server may process the transaction between the two parties based on the transaction identification information. The specific transaction identification information may be a string of characters, which may be a string that can be recognized by the server for processing payment services, and a string that complies with the payment rules of the payment application. For example, it may be a string starting with 28, or a string starting with 25, 30, etc. The length of the string may be 16 to 24 characters, or other lengths that meet the requirements. The specific form of the string is not specifically limited here. The relevant content of the transaction identification information may also refer to the relevant description in the aforementioned embodiment.

[0132] The user's membership information may include the user information used when registering as a member, such as mobile phone number, name, etc., and may also include membership identification information generated by the server for the member user, such as membership card number, member user number, etc. For details, please refer to the relevant technology, and no specific limitation or elaboration is made here.

[0133] In the embodiment of this specification, after determining that the user uses the member payment method, the server sends the transaction identification information and member information of the first device user to the payment system. The transaction identification information and member information can be included in one message and sent to the payment system, or they can be sent to the payment system separately.

[0134] In the embodiment of this specification, the member authorization login page may include a control indicating that a non-member payment method is used. Optionally, in the embodiment of this specification, the first device may also perform the following steps:

[0135] 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 using a non-member payment method;

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

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

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

[0139] 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 indicating that the user agrees to pay by a non-member payment method;

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

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

[0142] If the user does not agree to register as a member or chooses a non-member payment method to make a payment, the server does not need to send the user's membership information to the payment system, but can send transaction identification information representing the user's transaction account information to the payment system.

[0143] The server can process the payment service based on the request of the payment system and feedback the payment result information. Optionally, in the embodiment of this specification, the server can perform the following steps:

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

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

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

[0147] The payment result information may be the result information indicating a payment failure or the result information indicating a payment success. The specific process of the payment process can be referred to in the relevant technology and will not be described here. The server may also feed back the payment result information to the payment system, such as a POS machine, a merchant cash register, or other device with a display function.

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

[0149] In actual applications, in order to improve the security of payment, the server may also send the information to be traded to the first device before executing the relevant steps of resource transfer for both parties of the transaction, so that the server executes the relevant steps of resource transfer for both parties of the transaction after the first device automatically confirms based on the user's authorization or the user manually confirms. Optionally, the server in the embodiment of this specification may also perform the following steps:

[0150] Sending payment link information to the first device; the payment link information includes identification information indicating payment information to be confirmed;

[0151] Acquire payment confirmation information provided by the first device so that the server executes a corresponding payment processing flow after receiving the payment confirmation information.

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

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

[0154] Based on the payment link information, payment confirmation information is sent to the server so that the server executes the corresponding payment processing flow after obtaining the payment confirmation information.

[0155] Among them, the payment information to be confirmed may include information on the amount to be paid, information on the transaction counterparty, etc. The payment link information may 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 preset rules. As an implementation method, the link information to be paid may be information in a URL format, or a character string in another format that can be recognized by the first device. In actual applications, 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 based on the user's authorization, the server may not need to send the payment link information to the first device.

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

[0157] Based on the payment link information, displaying a payment confirmation page; the payment confirmation page includes payment information to be confirmed;

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

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

[0160] Fig. 9 A schematic diagram of a payment confirmation page provided in an embodiment of this specification is shown in FIG. Fig. 9 As shown, the payment confirmation page may include an area 902 for displaying payment information, which may specifically display the payment amount information, and may also display information such as the payment method, transaction party, transaction time, etc. The payment page may also include an operation control 906. If the user clicks on the control, it may indicate that the user agrees to make the payment, and the mobile terminal may generate confirmation information. In actual applications, the operation control may be a control for payment confirmation, or a control for canceling the payment. If the user does not click on the control indicating cancellation of payment within a preset time period, it may also indicate that the user agrees to make the payment, and the mobile terminal may also generate confirmation information for subsequent processes. Fig. 9As shown, the payment confirmation page may also include description information 906 for NFC payment, which is useful for users to understand the advantages or usage methods of NFC payment.

[0161] In actual applications, the payment amount information contained in the payment confirmation page can be the transaction amount determined by the merchant using the second device based on the actual transaction, or it can be entered by the user of the first device, for example, it can be entered in the payment confirmation page, or it can be entered in a page for user inputting the amount that is displayed before the payment confirmation page is displayed.

[0162] The fourth operation may indicate that the user confirms the payment operation, which may be a substantial operation or a non-substantial operation, such as the user confirming the payment operation. Fig. 9 The confirmation control shown or the control indicating payment cancellation not being clicked within a preset time period can indicate that the user confirms the payment operation.

[0163] The operations in the embodiments of this specification may refer to operations performed by the user's body, or operations performed according to voice, eye movement, etc. The specific operation type is not specifically limited here.

[0164] In actual applications, in order to improve payment efficiency, the first device may not display the payment confirmation page if the user meets certain preset conditions, such as a secure payment environment, the user has authorized the first device or the server to confirm the payment information, etc. Optionally, in the embodiments of this specification, the first device may also perform the following steps:

[0165] Determine whether the user of the first device meets preset payment conditions; the preset payment conditions represent conditions that enable quick payment.

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

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

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

[0169] As an implementation mode, the preset payment conditions may include at least one of being authorized to use the ultra-fast payment function, the user being a high-activity user of the target application, and being authorized to use the password-free payment function.

[0170] Among them, the ultra-fast payment function can represent a confirmation-free payment function, such as not displaying the payment confirmation page and other pages that require user confirmation information before the transaction result page, eliminating or reducing the user's payment confirmation related operations, which is an extremely fast payment method. In actual applications, users can enable the ultra-fast payment function in the relevant settings page of the target application. If the user has authorized the use of the ultra-fast payment function, it can be determined that the user meets the preset payment conditions, and the payment confirmation page can be displayed when the user pays via NFC.

[0171] Highly active users can refer to users whose activeness in using the payment application is greater than or equal to a preset threshold. In actual applications, the user's activity can be calculated based on factors such as the length of time and frequency of the user's login to the payment application. The user's activity can also be determined based on the frequency of the user using the payment application to scan the code for payment or input the payment code. For highly active users, a quick payment processing flow can be provided for the user, such as not displaying the payment page.

[0172] In actual applications, for highly active users, the ultra-fast payment function in the user's payment application can also be enabled by default, and the corresponding payment process can be provided to the user based on the status of the ultra-fast payment function.

[0173] The password-free payment function means that there is no need to enter a password to make a payment. Payment can be made through biometric features such as fingerprints, faces, voiceprints, irises, etc. as verification information. The authorization server can also automatically execute when processing transactions for users, without the user having to enter a password or biometric information for verification.

[0174] Considering that in actual applications, after obtaining the NFC tag information, the first device needs to parse the tag information before calling up the target application and then displaying the member login page. Before displaying the member login page, the first device needs to execute 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 this specification, the following steps can also be performed:

[0175] A login response page is displayed; the login response page includes prompt information indicating that the login is in progress.

[0176] Fig.10 Schematic diagram of a login response page provided in an embodiment of this specification. Fig.10 As shown, the login response page may include a prompt message 1002 indicating that the login is in progress. In actual applications, the login response page may also include information such as a target application identifier, a merchant identifier, etc. The login response page may be generated locally by the first device, or may be generated based on information fed back by the server.

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

[0178] Among them, after the server obtains the member login request sent by the first device, it can first send the login response page information to the first device, and then send the login result information to the first device after the login process is completed.

[0179] In order to ensure the security of user information, before invoking the target application in the first device, the first device may further perform the following steps:

[0180] Displaying a member reminder page; the member reminder page contains information prompting the user to log in as a member or information prompting the user to make a payment through the member;

[0181] The above-mentioned invoking the target application in the first device may specifically include:

[0182] Acquiring 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, the target application in the first device is invoked.

[0184] Fig.11 Schematic diagram of a member reminder page provided in the embodiment of this specification. Fig.11 As shown, the page may include information 1102 prompting the user to log in as a member, such as the words "click to log in as a member". The prompt information included in the page may be information prompting the user to pay through the member, such as the words "click to pay as a member".

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

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

[0187] In actual applications, the member prompt page may also include a download control for downloading the target application client. If the user clicks on the control, the first device may jump to display a download page for downloading the target application client, or the first device may download the target application from the application store. It may also display a prompt message indicating the download progress, and may start background download or installation. After the download or installation is completed, a prompt message indicating the download or installation completion may be displayed.

[0188] As an implementation method, if the first device is an iOS system, the first device is close to the NFC tag, and after obtaining the tag information, a member reminder page can be displayed. The member reminder 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 on the member reminder page to indicate consent to start the target application, the first device can call up the target application. The first device can execute a member login process based on the started target application, and can also execute a member payment process, such as displaying a member login page. In actual applications, during the user's operation on the member reminder page, the first device can collect the user's biometric information as payment verification information. If the user submits information indicating confirmation of member login and payment based on the member reminder page, it can indicate that the user has confirmed the payment information, or the payment confirmation page may not be displayed. Of course, the payment confirmation page can also be displayed according to actual needs. If the user has not turned on the ultra-fast payment function or does not meet the above-mentioned preset payment conditions, the first device can also display a payment confirmation page.

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

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

[0191] Fig.12 Schematic diagram of a payment response page provided in the embodiments of this specification. Fig.12 As shown, the payment response page may include prompt information 1202 indicating that payment is in progress, and may also include prompt information 1204 of the near field communication payment method used, such as the word NFC; it may also include relevant description information of the near field communication payment, such as Fig.12 The words "touch and pay" are shown.

[0192] The payment response page may be generated locally by the first device or based on the response information fed back by the server. The payment response page may also include progress information of the payment process, such as progress information in the form of percentage, information in the form of a progress bar, etc.

[0193] It is understandable that each display page in each embodiment of this specification can be a page displayed in a pop-up window, can be an H5 page, can be an application page in the target application, can be a web page, or can be a page in other forms, and no specific limitation is given 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 reminder page can be displayed in the form of a light application page, or can be displayed in the form of a notification page, etc.

[0194] In actual applications, in order to improve user experience and ensure user information security, the tag information in the NFC tag can be read only once. After the NFC tag information in the NFC tag is read, the tag information can be deleted from the NFC tag, or new tag information can be entered into the NFC tag. Of course, the tag information can also be set to be reusable, which can be set according to actual business needs, and is not specifically limited here.

[0195] In the embodiments of this specification, the target application can be an application with a payment function, or it can be other types of applications. In at least one embodiment of this specification, when a user needs to use membership payment, the user can use the first device to approach the NFC tag of the second device to obtain the tag information, and then use the target application to complete the membership login and payment, wherein the user can complete the membership login and payment by sticking or touching the first device and the second device, and the whole process does not require too much operation. If the user has not registered as a member, the first device can display the member login authorization page. After the user authorizes and agrees to the member registration, the first device and the server can register the user as a member and make payment based on the user's authorization. During the whole process, the user can only operate on the member login authorization page, and there is no need for too much operation, which can simplify the user operation steps.

[0196] In actual applications, in order to allow users to pay with awareness, pages such as payment confirmation pages may also be displayed. It is understandable that the various display pages provided in this specification may be set and displayed according to actual needs, as long as they comply with the business processing logic.

[0197] In the embodiments of this specification, if the second device has a display screen, the server may also send login result information, payment result information, etc. to the second device, and the second device may also display information indicating the login result, information indicating the payment result, etc. Before displaying the login result information and the payment result information, the second device may also display information indicating that the user is logging in as a member, or information indicating that payment is being made, etc. The second device may also reflect information at various business processing stages through voice broadcasts, prompt sounds, etc. The information displayed in the second device may be set according to actual needs, and no specific limitation is made here.

[0198] In actual applications, the first device can display the above-mentioned display pages in an 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 when handling the close state.

[0199] If the system program of the first device can accurately parse the content in the tag information, such as when the tag information is a link in the https format, 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 an unlocked state to complete member login or payment operations.

[0200] Based on the same idea, the embodiments of this specification also provide a method in which the server corresponding to the above-mentioned first device is the execution subject. Fig.13 The following is a flow chart of a method for displaying a member login page provided in an embodiment of this specification. Fig.13 As shown, the method may include the following steps:

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

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

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

[0204] The first device may display a member login page.

[0205] In actual applications, the tag information in the second device can be generated by the server according to actual needs. Specifically, it may include: obtaining a tag information acquisition request sent by the second device; based on the tag information acquisition request, generating tag information for burning into the NFC tag of the second device; the tag information includes first information for waking up the target application and second information for executing the member login process; sending 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 near field communication and execute the member login process.

[0206] The tag information acquisition request may be sent by the merchant or the user after determining that the user needs to log in as a member. For example, the second device may be connected to an operable cash register system or device. The second device may contain operable controls, such as when a cashier clicks a control indicating member payment in a cash register terminal, or when a user clicks a control indicating member login or payment in a self-service payment device. The second device or cash register system may send a tag information acquisition request to the server. The second device may be a part of a cash register system or a self-service payment device, or may be a device connected thereto.

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

[0208] The specific steps of the server to execute member login or payment can be found in the above embodiments and will not be repeated here.

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

[0210] The information acquisition module 1402 is used to acquire tag information of the NFC tag of the second device by means of near field communication; the tag information includes first information for invoking the target application and second information for triggering the member login process;

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

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

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

[0214] based on Fig.14 The present specification also provides some specific implementation schemes of the device, which are described below.

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

[0216] The member login result information fed back by the server is obtained, and a member login result page is displayed; the member login result information is page information fed back by the server after determining that the user of the first device is a member of the target object.

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

[0218] The member authorization login page information fed back by the server is obtained, and the 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 member of the target object.

[0219] Optionally, the page display module may include a first page display unit, which may be used to:

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

[0221] Based on the first operation, sending a member login request to the server;

[0222] Obtain the member login result information fed back by the server and display the member login result page.

[0223] Optionally, the first operation may also represent an operation in which the user pays by using a member payment method, and the request sending module may also be used to:

[0224] A first payment trigger request is sent to the server so that the server executes a corresponding payment processing flow.

[0225] Optionally, the page display module may include a second page display unit, which may be used to:

[0226] 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 using a non-member payment method;

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

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

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

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

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

[0232] A link acquisition unit, used to acquire payment link information provided by the server; the payment link information includes identification information indicating payment information to be confirmed;

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

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

[0235] A page display unit, used to display a payment confirmation page based on the payment link information; the payment confirmation page includes payment information to be confirmed;

[0236] The payment confirmation unit may be specifically configured to send payment confirmation information to the server based on a fourth operation performed by the user on the payment confirmation page.

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

[0238] a condition determination unit, configured to determine whether the user of the first device meets a preset payment condition; the preset payment condition indicates a condition for enabling quick payment;

[0239] The page display unit may be specifically configured to display the payment confirmation page if the user does not meet the preset payment conditions;

[0240] The above-mentioned displaying of the payment result page may specifically include: if the user meets the preset payment conditions, then displaying the payment result page.

[0241] Optionally, the page display module further includes a fourth page display unit, which can be used to:

[0242] A login response page is displayed; the login response page includes prompt information indicating that the login is in progress.

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

[0244] Displaying a member reminder page; the member reminder page contains information prompting the user to log in as a member or information prompting the user to make a payment through the member;

[0245] The above application awakening module can be specifically used to include:

[0246] Acquire a second operation of the user on the member prompt page; the second operation indicates consent to use the target application to log in as a member;

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

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

[0249] Acquire scene parameter information in the second information;

[0250] Based on the scene parameter information, generate a page information acquisition request;

[0251] Send the sending page information acquisition request to the server.

[0252] Based on the same idea, Fig.15 The embodiments of this specification provide corresponding to Fig.13 A schematic diagram of the structure of a device for displaying a member login page. Fig.15 As shown, the device may include:

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

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

[0255] based on Fig.15 The present specification also provides some specific implementation schemes of the device, which are described below.

[0256] Optionally, the page information acquisition request includes user identification information of the first device; the apparatus may further include a judgment module for judging whether the user of the first device is a member of the target object based on the user identification information to obtain a judgment result.

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

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

[0259] Optionally, the page information sending module may include a third page information sending unit, which is used to:

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

[0261] Send member login result information to the first device so that the first device displays a member login result page.

[0262] Optionally, the request acquisition module may include a first payment request acquisition unit, the first operation further represents an operation in which the user pays by using a member payment method, and the first payment request acquisition unit may be used to: acquire a first payment trigger request sent by the first device;

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

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

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

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

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

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

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

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

[0271] Acquire payment confirmation information provided by the first device so that the server executes a corresponding payment processing flow after receiving the payment confirmation information.

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

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

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

[0275] at least one processor 1610; and,

[0276] A memory 1630 in communication with the at least one processor; wherein:

[0277] The memory 1630 stores instructions 1620 that can be executed by the at least one processor 1610. The instructions are executed by the at least one processor 1610 so that the at least one processor 1610 can execute to implement the above-mentioned method of displaying a member login page.

[0278] Based on the same idea, the embodiment of this specification also provides a computer-readable medium corresponding to the above method. The computer-readable medium stores computer-readable instructions, which can be executed by a processor to implement the above method of displaying a member login page.

[0279] Each embodiment in this specification is described in a progressive manner, and the same or similar parts between the embodiments can be referred to each other, and each embodiment focuses on the differences from other embodiments. In particular, for the above-mentioned devices 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 partial description of the method embodiments.

[0280] In the 1990s, it was very clear whether the improvement of a technology was hardware improvement (for example, improvement of the circuit structure of diodes, transistors, switches, etc.) or software improvement (improvement of the method flow). However, with the development of technology, many improvements of the method flow today can be regarded as direct improvements of the hardware circuit structure. Designers almost always obtain the corresponding hardware circuit structure by programming the improved method flow into the hardware circuit. Therefore, it cannot be said that the improvement of a method flow cannot be implemented with hardware entity modules. For example, a programmable logic device (PLD) (such as a field programmable gate array (FPGA)) is such an integrated circuit whose logical function is determined by the user's programming of the device. Designers can "integrate" a digital system on a PLD by programming it themselves, without having to ask chip manufacturers to design and make dedicated integrated circuit chips. Moreover, nowadays, instead of manually making integrated circuit chips, this kind of programming is mostly implemented by "logic compiler" software, which is similar to the software compiler used when developing and writing programs, and the original code before compilation must also be written in a specific programming language, which is called hardware description language (HDL). There is not only one kind of HDL, but many kinds, such as ABEL (Advanced Boolean Expression Language), AHDL (Altera Hardware Description Language), Confluence, CUPL (Cornell University Programming Language), HDCal, JHDL (Java Hardware Description Language), Lava, Lola, MyHDL, PALASM, RHDL (Ruby Hardware Description Language), etc. The most commonly used ones are VHDL (Very-High-Speed ​​Integrated Circuit Hardware Description Language) and Verilog. Those skilled in the art should also know that it is only necessary to program the method flow slightly in the above-mentioned hardware description languages ​​and program it into the integrated circuit, and then it is easy to obtain the hardware circuit that implements the logic method flow.

[0281] The controller may be implemented in any suitable manner, for example, the controller may take the form of a microprocessor or processor and a computer-readable medium storing a computer-readable program code (e.g., software or firmware) executable by the (micro)processor, a logic gate, a switch, 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, and the memory controller may also be implemented as part of the control logic of the memory. It is also known to those skilled in the art that, in addition to implementing the controller in a purely computer-readable program code manner, the controller may be implemented in the form of a logic gate, a switch, an application-specific integrated circuit, a programmable logic controller, and an embedded microcontroller by logically programming the method steps. Therefore, such a controller may be considered as a hardware component, and the devices for implementing various functions included therein may also be considered as structures within the hardware component. Or even, the devices for implementing various functions may be considered as both software modules for implementing the method and structures within the hardware component.

[0282] The systems, devices, modules or units described in the above embodiments may be implemented by computer chips or entities, or by products with certain functions. A typical implementation device is a computer. Specifically, the computer may 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.

[0283] For the convenience of description, the above device is described in various units according to their functions. Of course, when implementing the present application, the functions of each unit can be implemented in the same or multiple software and / or hardware.

[0284] It will be appreciated by those skilled in the art that embodiments of the present invention may be provided as methods, systems, or computer program products. Therefore, the present invention may take the form of a complete hardware embodiment, a complete software embodiment, or an embodiment combining software and hardware. Furthermore, the present invention may 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-ROM, optical storage, etc.) containing computer-usable program code.

[0285] The present invention is described with reference to flowcharts and / or block diagrams of methods, devices (systems), and computer program products according to embodiments of the present invention. It should be understood that each process and / or block in the flowchart and / or block diagram, as well as the combination of processes and / or blocks in the flowchart and / or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing device to produce a machine, so that the instructions executed by the processor of the computer or other programmable data processing device generate instructions for implementing the processes in the flowchart and / or block diagram. Figure 1 A process or multiple processes and / or boxes Figure 1 A device that provides the functions specified in a block or multiple blocks.

[0286] These computer program instructions may also be stored in a computer-readable memory capable of directing a computer or other programmable data processing device to operate in a specific manner, so that the instructions stored in the computer-readable memory produce an article of manufacture comprising an instruction device, which implements the process Figure 1 A process or multiple processes and / or boxes Figure 1 A function specified in one or more boxes.

[0287] These computer program instructions can also be loaded onto a computer or other programmable data processing device so that a series of operating steps are executed on the computer or other programmable device to produce a computer-implemented process, thereby providing instructions for implementing the process. Figure 1 A process or multiple processes and / or boxes Figure 1 The steps for the functions specified in one or more boxes.

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

[0289] Memory may include non-permanent storage in a computer-readable medium, random access memory (RAM) and / or non-volatile memory in the form of read-only memory (ROM) or flash RAM. Memory is an example of a computer-readable medium.

[0290] Computer readable media include permanent and non-permanent, removable and non-removable media that can be implemented by any method or technology to store information. Information can be computer readable instructions, data structures, program modules or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technology, compact disk read-only memory (CD-ROM), digital versatile disk (DVD) or other optical storage, magnetic cassettes, magnetic disk storage or other magnetic storage devices or any other non-transmission media that can be used to store information that can be accessed by a computing device. As defined in this article, computer readable media does not include temporary computer readable media (transitory media), such as modulated data signals and carrier waves.

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

[0292] Those skilled in the art will appreciate that the embodiments of the present application may be provided as methods, systems or computer program products. Therefore, the present application may take the form of a complete hardware embodiment, a complete software embodiment or an embodiment combining software and hardware. Moreover, the present application may 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-ROM, optical storage, etc.) containing computer-usable program codes.

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

[0294] The above is only an embodiment of the present application and is not intended to limit the present application. For those skilled in the art, the present application may have various changes and variations. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present application should be included in the scope of the claims of the present application.

Claims

1. A method for displaying a member login page, comprising: The first device obtains tag information of the NFC tag of the second device by means of near field communication; The tag information includes first information for invoking the target application and second information for triggering the member login process; The target application triggers a member login process based on the second information; The first information includes an identifier of the target application; the second information includes information of the jump page and identifier information of the member providing service provider; Based on the first information, invoking the target application in the first device; Based on the second information, using the target application to send a page information acquisition request to a server; Obtain the member login page information fed back by the server, and display the member login page.

2. According to the method of claim 1, the step of obtaining the member login page information fed back by the server and displaying the member login page specifically comprises: Obtain member login result information fed back by the server, and display the member login result page; The member login result information is page information fed back by the server after determining that the user of the first device is a member of the target object.

3. According to the method of claim 1, the step of obtaining the member login page information fed back by the server and displaying the member login page specifically comprises: Obtaining member authorization login page information fed back by the server, and displaying the member authorization login page; The member authorization login page information is page information fed back by the server after determining that the user of the first device is not a member of the target object.

4. The method according to claim 3, further comprising: Obtaining a first operation of a user on a first control of the member authorization login page; The first operation is an operation indicating that the user agrees to become a member of the target object; Based on the first operation, sending a member login request to the server; Obtain the member login result information fed back by the server and display the member login result page.

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

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

7. The method according to any one of claims 2, 5 and 6, further comprising: Obtain payment result information fed back by the server; Based on the payment result information, a payment result page is displayed.

8. The method according to claim 7, before obtaining the payment result information fed back by the server, further comprising: Acquire payment link information provided by the server; the payment link information includes identification information indicating payment information to be confirmed; Based on the payment link information, payment confirmation information is sent to the server so that the server executes the corresponding payment processing flow after obtaining the payment confirmation information.

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

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

11. The method according to claim 2 or 4, Before displaying the member login result page, it also includes: Display the login response page; The login response page includes prompt information indicating that the login is in progress.

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

13. The method according to claim 1, wherein based on the second information, using the target application to send a page information acquisition request to a server specifically comprises: Acquire scene parameter information in the second information; Based on the scene parameter information, generate a page information acquisition request; Send the sending page information acquisition request to the server.

14. A method for displaying a member login page, comprising: Obtaining a page information acquisition request sent by the first device; The page information acquisition request is generated by the first device acquiring tag information of the NFC tag of the second device through near field communication; the tag information includes first information for invoking the target application and second information for executing the member login process; The target application triggers a member login process based on the second information; The first information includes an identifier of the target application; the second information includes information of the jump page and identifier information of the member providing service provider; Based on the page information acquisition request, the member login page information is sent to the first device so that the first device displays the member login page.

15. The method according to claim 14, The page information acquisition request includes user identification information of the first device; the method further includes: Based on the user identification information, determining whether the user of the first device is a member of the target object, and obtaining a determination result; The sending of member login page information to the first device specifically includes: If the determination result indicates that the user is a member of the target object, member login result information is sent to the first device so that the first device displays a member login result page.

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

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

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

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

20. The method according to claim 15, if the judgment result indicates that the user is a member of the target object, the method further comprises: The first transaction information of the user is sent to a payment system associated with the second device so that the payment system processes payment services for the user based on the first transaction information; the first transaction information includes transaction identification information for representing the transaction account information of the user and the membership information of the user.

21. The method according to claim 18, 19 or 20, further comprising: Obtaining a payment processing request generated by the payment system based on the transaction identification information; Execute the payment process based on the payment processing request to obtain payment result information; The payment result information is sent to the first device.

22. The method according to claim 21, before 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 includes identification information indicating payment information to be confirmed; Acquire the payment confirmation information provided by the first device so that the server executes the corresponding payment processing flow after acquiring the payment confirmation information.

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

24. A device for displaying a member login page, comprising: An information acquisition module, used to acquire tag information of an NFC tag of a second device by means of near field communication; The tag information includes first information for invoking the target application and second information for triggering the member login process; The target application triggers a member login process based on the second information; The first information includes an identifier of the target application; the second information includes information of the jump page and identifier information of the member providing service provider; 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 acquisition request to a server using the target application based on the second information; The page display module is used to obtain the member login page information fed back by the server and display the member login page.

25. A device for displaying a member login page, comprising: A request acquisition module, used to acquire a page information acquisition request sent by the first device; The page information acquisition request is generated by the first device acquiring tag information of the NFC tag of the second device through near field communication; the tag information includes first information for invoking the target application and second information for executing the member login process; The target application triggers a member login process based on the second information; The first information includes an identifier of the target application; the second information includes information of the jump page and identifier information of the member providing service provider; The page information sending module is used to send the member login page information to the first device based on the page information acquisition request, so that the first device displays the member login page.

26. A device for displaying a member login page, comprising: at least one processor; as well as, a memory communicatively connected to the at least one processor; wherein, The memory stores instructions that can be executed 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 execute the method for displaying a member login page according to any one of claims 1 to 23.

27. A computer-readable medium having computer-readable instructions stored thereon, wherein the computer-readable instructions can be executed by a processor to implement the method for displaying a member login page according to any one of claims 1 to 23.

Images