WO2017211019A1 - 一种支付方法、装置、终端以及服务器 - Google Patents
一种支付方法、装置、终端以及服务器 Download PDFInfo
- Publication number
- WO2017211019A1 WO2017211019A1 PCT/CN2016/099930 CN2016099930W WO2017211019A1 WO 2017211019 A1 WO2017211019 A1 WO 2017211019A1 CN 2016099930 W CN2016099930 W CN 2016099930W WO 2017211019 A1 WO2017211019 A1 WO 2017211019A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- dimensional code
- payment
- server
- terminal
- expiration time
- Prior art date
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q20/00—Payment architectures, schemes or protocols
- G06Q20/30—Payment architectures, schemes or protocols characterised by the use of specific devices or networks
- G06Q20/32—Payment architectures, schemes or protocols characterised by the use of specific devices or networks using wireless devices
- G06Q20/327—Short range or proximity payments by means of M-devices
- G06Q20/3276—Short range or proximity payments by means of M-devices using a pictured code, e.g. barcode or QR-code, being read by the M-device
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q20/00—Payment architectures, schemes or protocols
- G06Q20/08—Payment architectures
- G06Q20/12—Payment architectures specially adapted for electronic shopping systems
- G06Q20/127—Shopping or accessing services according to a time-limitation
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q20/00—Payment architectures, schemes or protocols
- G06Q20/30—Payment architectures, schemes or protocols characterised by the use of specific devices or networks
- G06Q20/32—Payment architectures, schemes or protocols characterised by the use of specific devices or networks using wireless devices
- G06Q20/327—Short range or proximity payments by means of M-devices
- G06Q20/3274—Short range or proximity payments by means of M-devices using a pictured code, e.g. barcode or QR-code, being displayed on the M-device
Definitions
- the present application relates to the field of computer technologies, and in particular, to a payment method, apparatus, terminal, and server.
- the mobile terminal can scan the two-dimensional code in the payment page generated on the PC to complete the payment, which greatly facilitates the user's payment, thereby promoting the prosperity of the mobile financial economy.
- the inventor found that at least the following problems exist in the prior art: when the payment request of an order is encapsulated into a two-dimensional code, after the user scans the two-dimensional code for payment, the page needs to respond in time to the payment result. Since the page cannot monitor whether the user has completed the payment, it is necessary to take the initiative to obtain the status of the order. Therefore, the polling request is frequently initiated and the user is informed of the payment result. If the user fails to make a payment for a long time, it means that a large number of requests need to be issued, which puts a lot of pressure on the server.
- the purpose of the embodiments of the present application is to provide a two-dimensional code payment method, a terminal, and a server, to solve the problem that the prior art fails to make a payment for a long time, and a large number of requests are issued, causing excessive server pressure.
- the embodiment of the present application provides the following technical solutions:
- an embodiment of the present application provides a payment method, which is applied to a terminal, where the method includes:
- the payment incomplete information is information that the payment operation is not completed within the two-dimensional code expiration time.
- the method further includes:
- the method further includes:
- the method includes:
- a mask layer is formed at a position opposite to the two-dimensional code region.
- the method includes:
- the two-dimensional code that generates the occlusion layer is activated according to the refresh request, and the server is polled.
- an embodiment of the present application provides a payment method, which is applied to a server, where the method includes:
- the terminal stops polling; wherein the payment incomplete information is information that the payment operation is not completed within the two-dimensional code expiration time.
- the method further includes:
- an embodiment of the present application provides a payment device, where the device includes:
- a sending module configured to send a two-dimensional code generation request to the server
- a first receiving module configured to receive a two-dimensional code address returned by the server according to the two-dimensional code generation request
- a first generating module configured to generate a two-dimensional code including a two-dimensional code expiration time according to the two-dimensional code address, and poll the server;
- a polling module for polling the server
- Stopping the module when receiving the payment incomplete information sent by the server, stopping polling the server; wherein the payment incomplete information is information that the payment operation is not completed within the expiration time of the two-dimensional code .
- the device further includes:
- a second receiving module configured to receive a two-dimensional code failure time returned by the server according to the two-dimensional code generation request
- the first generating module is further configured to: generate a two-dimensional code including a two-dimensional code expiration time according to the two-dimensional code expiration time and the two-dimensional code address.
- the device further includes:
- Preset module for presetting the expiration time of the QR code
- the first generation module is further specifically configured to:
- the device further includes a second generating module, configured to generate a cover layer at a position opposite to the two-dimensional code region.
- a second generating module configured to generate a cover layer at a position opposite to the two-dimensional code region.
- the device further comprises
- a third receiving module configured to receive a refresh request for refreshing under a payment page in which the two-dimensional code has expired
- an activation module configured to activate the two-dimensional code that generates the cover layer according to the refresh request.
- an embodiment of the present application provides a payment device, where the device includes:
- a receiving module configured to receive a two-dimensional code generation request sent by the terminal
- a first sending module configured to send a two-dimensional code address to the terminal according to the two-dimensional code generation request, so that the terminal generates a two-dimensional code including a two-dimensional code expiration time according to the two-dimensional code address. And polling;
- a second sending module configured to send the payment incomplete information to the terminal, so that the terminal stops polling; wherein the payment incomplete information is information that the payment operation is not completed within the two-dimensional code expiration time.
- the device further includes a third sending module, configured to send, according to the two-dimensional code generation request, a two-dimensional code expiration time to the terminal, so that the terminal according to the two-dimensional code expiration time and The two-dimensional code address generates a two-dimensional code including a two-dimensional code failure time.
- a terminal including:
- At least one processor and,
- the memory stores instructions executable by the at least one processor, the instructions being executed by the at least one processor to enable the at least one processor to perform the method as described above.
- the embodiment of the present application further provides a non-transitory computer readable storage medium, where the computer-readable storage medium stores computer-executable instructions, when the computer-executable instructions are executed by an electronic device, The electronic device is caused to perform the method of applying to the terminal as described above.
- the embodiment of the present application further provides a computer program product, the computer program product comprising a computer program stored on a non-transitory computer readable storage medium, the computer program comprising program instructions, when When the program instructions are executed by the electronic device, the electronic device is caused to perform the method applied to the terminal as described above.
- the embodiment of the present application further provides a server, including:
- At least one processor and,
- the memory stores instructions executable by the at least one processor, the instructions being executed by the at least one processor to enable the at least one processor to perform the method as described above.
- the embodiment of the present application further provides a non-transitory computer readable storage medium, where the computer-readable storage medium stores computer-executable instructions, when the computer-executable instructions are executed by an electronic device, The electronic device is caused to perform the application to the server method as described above.
- the embodiment of the present application further provides a computer program product, the computer program product comprising a computer program stored on a non-transitory computer readable storage medium, the computer program comprising program instructions, when When the program instructions are executed by the electronic device, the electronic device is caused to perform the application to the server method as described above.
- the terminal stops polling the server, reducing the payment of the terminal.
- the process constantly polls the server and puts extra stress on the server so that the server can handle other payment operations.
- FIG. 1 is a schematic application scenario of a two-dimensional code payment method according to an embodiment of the present application
- Figure 1a is a possible payment page of the possible application scenario shown in Figure 1;
- FIG. 2 is a schematic flowchart of a two-dimensional code payment method according to Embodiment 1 of the present application;
- FIG. 3 is a schematic flowchart of a two-dimensional code payment method provided in Embodiment 2 of the present application.
- FIG. 3a is a schematic diagram of a possible two-dimensional code failure pattern provided by Embodiment 1 of the present application.
- FIG. 5 is a schematic flowchart of a two-dimensional code payment method provided in Embodiment 4 of the present application.
- FIG. 6 is a schematic flowchart of a two-dimensional code payment method provided in Embodiment 5 of the present application.
- FIG. 7 is a schematic structural diagram of a payment apparatus according to Embodiment 6 of the present application.
- FIG. 8 is a schematic structural diagram of a payment apparatus according to Embodiment 7 of the present application.
- FIG. 9 is a schematic diagram showing the hardware structure of a terminal for processing a two-dimensional code payment method according to an embodiment of the present application.
- FIG. 10 is a hard disk of a server for processing a two-dimensional code payment method according to an embodiment of the present application. Schematic diagram of the structure.
- FIG. 1 is a schematic application scenario of a two-dimensional code payment method according to an embodiment of the present application.
- the application scenario includes a smart terminal 11 , a computer 12 , a business party 13 , and a third party payment platform 14 .
- the user 10 completes the order at the computer 12 and enters the payment page 1a1 through the computer 12.
- FIG. 1a is a possible payment page of the possible application scenario shown in FIG. 1.
- the payment page 1a1 includes a plurality of third party payment platforms, at least one of which has a third party payment platform supporting the two-dimensional code payment method 1a11.
- the payment page may also include different third-party platform payment methods, such as online banking payment and the like.
- the smart terminal 11 scans the two-dimensional code payment method 1a11. Under normal circumstances, after the scan code is successful, the user passes through the smart terminal 11 on the third-party payment platform 14 . The payment is completed. If the payment is successful, the third party payment platform 14 notifies the business party 13 that the payment is successful. At this time, the business party 13 can implement the next step, such as delivery, prompting the user to pay successfully, and the like.
- the payment front end of the computer 12 continuously polls the server 131 of the business party 13 until the business party 13 informs the payment front end user of the computer 12 that the payment is successful, and the payment front end of the computer 12 stops.
- the server 131 of the business party 13 is polled, and therefore, this method greatly increases the pressure on the server.
- the third-party payment platform 14 cannot send the user payment success information to the service party 13 faithfully or correctly, so that the service party 13 cannot further feedback the payment success information to the payment front end of the computer 12, so that the computer 12 is enabled.
- the payment front end stops polling the server 131 of the business party 13.
- FIG. 2 is a schematic flowchart diagram of a two-dimensional code payment method according to Embodiment 1 of the present application. The method includes:
- the user first completes registration, authentication, and login in the terminal mall. After logging in, the user performs an purchase item on the purchase page of the mall in the terminal, and completes the order operation for the purchased item, and enters the payment page.
- the payment page 1a includes various third-party payment platforms, such as an A payment platform, a B payment platform, a C online banking payment platform, a D-fast payment platform, and an E-phase payment platform.
- the at least one payment platform supports a two-dimensional code payment method. As shown in FIG.
- the A payment platform under the A payment platform, it supports two payment methods, the first one is a two-dimensional code payment method 1a11, and the second type is a computer-side payment method.
- the user can use the portable smart device to scan the two-dimensional code payment method 1a11, and then the payment can be made on the portable smart device.
- portable smart devices include smartphones, tablets, smart watches, and other portable smart devices.
- the user can also select a computer-side payment method to make a payment.
- the terminal sends a two-dimensional code generation request to the server, requesting the server to return the two-dimensional code address.
- the server responds to the two-dimensional code request and returns a two-dimensional code address to the terminal according to the IP address and port number of the terminal.
- the two-dimensional code generation request may be an Http request.
- the terminal may send a two-dimensional code generation request that conforms to the transmission protocol and the resolution protocol to the server through a wireless network or a wired network.
- the two-dimensional code generation request includes terminal identification information and two-dimensional code generation content information, and the server returns a two-dimensional code address to the terminal according to the terminal identification information.
- the two-dimensional code address may be a Uniform Resource Locator URL.
- the terminal generates a two-dimensional code including the expiration time of the two-dimensional code according to the QR code address URL returned by the server.
- the two-dimensional code failure time is the time period from the activation to the failure of the two-dimensional code. The failure here means that the user cannot scan the two-dimensional code again through the portable smart device.
- the setting of the two-dimensional code expiration time is set by the business party according to the purpose of the job.
- the expiration time of the two-dimensional code in the embodiment of the present application is 120 seconds.
- the server of the service party has not fed back the information of the user's payment success to the terminal, and the terminal automatically makes the two-dimensional code. Invalid.
- the polling is about whether the user has successfully paid.
- the payment success information of the user is fed back to the server of the service party by the third-party payment platform, and then the server of the service party further feeds back the payment success information to the payment front end of the terminal.
- the poll is an http request.
- the payment incomplete information may be information that the user does not complete the payment operation within the expiration time of the two-dimensional code, or may be caused by a network failure of the third-party payment platform or a server crash of the third-party payment platform.
- the server of the party does not receive the successful payment information sent by the third-party payment platform, and the server of the service party determines that the user has not completed the payment operation within the expiration time of the two-dimensional code.
- the terminal In the process of continuously polling the server, if the terminal receives the information that the user sent by the server does not complete the payment operation within the expiration time of the two-dimensional code, the terminal stops polling the server. If the result of the payment operation completed by the user sent by the server within the expiration time of the two-dimensional code is received, the payment success page is automatically jumped to prompt the user to successfully pay.
- the terminal stops polling the server. Therefore, with this approach, it reduces the terminal's constant polling of the server during the payment process and puts additional pressure on the server for the server to handle other payment operations.
- FIG. 3 is a schematic flowchart diagram of a two-dimensional code payment method according to Embodiment 2 of the present application. As shown in FIG. 3, the method includes:
- the setting of the two-dimensional code expiration time is set by the business party according to the purpose of the job.
- the expiration time of the two-dimensional code in the embodiment of the present application is 120 seconds.
- the server of the service party has not fed back the information of the user's payment success to the terminal, and the terminal automatically makes the two-dimensional code. Invalid.
- the two-dimensional code and the two-dimensional code failure time are corresponding, and the two-dimensional code failure time is a time period from the activation to the failure of the two-dimensional code, where the failure means that the user cannot pass the portable again.
- the smart device scans the QR code. When the two-dimensional code is valid for more than the two-dimensional code failure time, the two-dimensional code at this time begins to enter the failure state.
- a mask layer is generated at a position opposite to the two-dimensional code region.
- FIG. 3a is a schematic diagram of a possible two-dimensional code failure pattern provided by Embodiment 2 of the present application.
- the manner of invalidating the two-dimensional code is various.
- the cover layer 3a1 is generated at a position corresponding to the two-dimensional code area 1a11 on the payment page 1a1 to block the user.
- the two-dimensional code in the two-dimensional code area 3a11 is scanned, and from the side, the two-dimensional code in the two-dimensional code area 3a11 is also invalidated.
- the cover layer 3a1 here is a refresh page.
- the terminal can also generate a non-original two-dimensional code arbitrarily, and the user's portable smart device cannot correctly parse the two-dimensional code. On the one hand, the original two-dimensional code is invalidated.
- the terminal stops polling the server. Therefore, with this approach, it reduces the terminal's constant polling of the server during the payment process and puts additional pressure on the server for the server to handle other payment operations.
- FIG. 4 is a schematic flowchart diagram of a two-dimensional code payment method according to Embodiment 3 of the present application. As shown in FIG. 4, the method includes:
- the designer presets the two-dimensional code expiration time according to the work purpose.
- the preset two-dimensional code expiration time and the two-dimensional code address have a corresponding relationship.
- the designer presets a plurality of two-dimensional code failure schedules according to the purpose of the operation, and for different two-dimensional code addresses, by searching for the two-dimensional code failure schedule, matching the two-dimensional code failure time corresponding to the two-dimensional code address, Therefore, the two-dimensional code generated from the two-dimensional code address also corresponds to a specific two-dimensional code failure time. Therefore, the designer generates a two-dimensional code including a specific two-dimensional code failure time according to a specific two-dimensional code address by flexibly setting a two-dimensional code failure schedule.
- the two-dimensional code expiration time starts to run.
- the run here can be a countdown or an accumulated count.
- the preset two-dimensional code expiration time is 120 seconds, when the two-dimensional code failure time counts down to 0 seconds, and in the process, when the user reaches the timing end point in the terminal's payment page timing, the payment has not been completed.
- the business party has not feedback the information of the payment success to the terminal, the terminal automatically invalidates the two-dimensional code, and stops polling the server.
- the two-dimensional code expiration time starts from 0 seconds, when the time is accumulated to 120 seconds, and in the process, when the user reaches the timing end point in the timing of the payment page of the terminal, the payment has not been completed, and the business party The information about the successful payment has not been fed back to the terminal, and the terminal automatically invalidates the two-dimensional code and stops polling the server.
- the terminal may also set other characterizations instead of the expiration time of the two-dimensional code. For example, when the user enters the payment page of the terminal, the terminal automatically generates a representation of the non-QR code, wherein the representation includes the expiration time of the representation. The user has not completed the payment within the expiration time of the over-character, and the business party has not fed back the information of the payment success to the terminal, the terminal automatically invalidates the two-dimensional code, and stops polling the server.
- a mask layer is generated at a position opposite to the two-dimensional code region.
- the terminal stops polling the server. Therefore, with this approach, it reduces the terminal's constant polling of the server during the payment process and puts additional pressure on the server for the server to handle other payment operations.
- FIG. 5 is a schematic flowchart diagram of a two-dimensional code payment method according to Embodiment 4 of the present application. As shown in FIG. 5, the method includes:
- the front end of the payment page is provided with a refresh button.
- the user refreshes the payment page by clicking the refresh button, thereby generating a refresh request.
- the activation time of the QR code included in the activated QR code follows the activation of the QR code and begins to enter the timing state.
- the two-dimensional code failure time arrives, the two-dimensional code at this time enters a failure state.
- the terminal activates the two-dimensional code according to the refresh request, and the mask layer 3a1 generated at the opposite position of the two-dimensional code area 3a11 has been revoked, thereby displaying the two-dimensional code.
- the user can scan the QR code using a smart portable device to implement the payment operation.
- the terminal does not need to resend the two-dimensional code generation request to the server, and only needs to activate the two-dimensional code of the front end of the payment page to meet the scanning code requirement required for the next payment, thereby reducing the terminal access server band.
- the user does not need to re-enter the payment page, and only needs to refresh the payment page to obtain a new two-dimensional code, thereby facilitating the user to make a quick payment.
- the payment uncompleted information is information that the payment operation is not completed within the time limit of the two-dimensional code.
- the terminal stops polling the server. Therefore, with this approach, it reduces the terminal's constant polling of the server during the payment process and puts additional pressure on the server for the server to handle other payment operations.
- FIG. 6 is a schematic flowchart diagram of a two-dimensional code payment method according to Embodiment 5 of the present application. As shown in FIG. 6, the method includes:
- the terminal sends a two-dimensional code generation request to the server, requesting the server to return the two-dimensional code address.
- the server responds to the two-dimensional code request and returns a two-dimensional code address to the terminal according to the IP address and port number of the terminal.
- the two-dimensional code generation request may be an Http request.
- the terminal may send a two-dimensional code generation request that conforms to the transmission protocol and the resolution protocol to the server through a wireless network or a wired network.
- S62 Send a two-dimensional code address to the terminal according to the two-dimensional code generation request, so that the terminal generates a two-dimensional code including a two-dimensional code expiration time according to the two-dimensional code address, and performs polling;
- the two-dimensional code generation request includes terminal identification information and two-dimensional code generation content information, and the server returns a two-dimensional code address to the terminal according to the terminal identification information.
- the two-dimensional code address may be a Uniform Resource Locator URL.
- the terminal generates a two-dimensional code including the expiration time of the two-dimensional code according to the QR code address URL returned by the server.
- the two-dimensional code failure time is the time period from the activation to the failure of the two-dimensional code. The failure here means that the user cannot scan the two-dimensional code again through the portable smart device.
- the setting of the two-dimensional code expiration time is set by the business party according to the purpose of the job.
- the expiration time of the two-dimensional code in the embodiment of the present application is 120 seconds.
- the server of the service party has not fed back the information of the user's payment success to the terminal, and the terminal automatically makes the two-dimensional code. Invalid.
- the polling is about whether the user has successfully paid.
- the payment success information of the user is fed back to the server of the service party by the third-party payment platform, and then the server of the service party further feeds back the payment success information to the payment front end of the terminal.
- the poll is an http request.
- the payment uncompleted information is information that the payment operation is not completed within the time limit of the two-dimensional code.
- the payment incomplete information may be information that the user does not complete the payment operation within the expiration time of the two-dimensional code, or may be caused by a network failure of the third-party payment platform or a server crash of the third-party payment platform.
- the server of the party does not receive the successful payment information sent by the third-party payment platform, and the server of the service party determines that the user has not completed the payment operation within the expiration time of the two-dimensional code.
- the terminal In the process of continuously polling the server, if the terminal receives the information that the user sent by the server does not complete the payment operation within the expiration time of the two-dimensional code, the terminal stops polling the server. If the result of the payment operation completed by the user sent by the server within the expiration time of the two-dimensional code is received, the payment success page is automatically jumped to prompt the user to successfully pay.
- the terminal stops polling the server. Therefore, with this approach, it reduces the terminal's constant polling of the server during the payment process and puts additional pressure on the server for the server to handle other payment operations.
- FIG. 7 is a schematic structural diagram of a payment apparatus according to Embodiment 6 of the present application. As shown in Figure 7, the device 70 includes:
- the sending module 701 is configured to send a two-dimensional code generation request to the server;
- the first receiving module 702 is configured to receive a two-dimensional code address returned by the server according to the two-dimensional code generation request;
- a first generating module 703 configured to generate a two-dimensional code including a two-dimensional code expiration time according to the two-dimensional code address, and poll the server;
- a polling module 704 configured to poll the server
- the stopping module 705 is configured to stop polling the server when receiving the payment incomplete information sent by the server, where the payment incomplete information is an incomplete payment operation in the two-dimensional code expiration time information.
- the device 70 further includes:
- a second receiving module 706, configured to receive, by the server, a request according to the two-dimensional code generation request QR code expiration time; then:
- the first generation module 703 is further configured to: generate a two-dimensional code including a two-dimensional code failure time according to the two-dimensional code failure time and the two-dimensional code address.
- the device 70 further includes:
- the preset module 707 is configured to preset a two-dimensional code expiration time
- the first generating module 703 is further specifically configured to:
- the apparatus further includes a second generation module 708 for generating a cover layer at a position opposite to the two-dimensional code region.
- the device 70 further includes
- the third receiving module 709 is configured to receive a refresh request for refreshing under a payment page in which the two-dimensional code has expired;
- the activation module 710 is configured to activate the two-dimensional code for generating the cover layer according to the refresh request.
- the terminal stops polling the server. Therefore, with this approach, it reduces the terminal's constant polling of the server during the payment process and puts additional pressure on the server for the server to handle other payment operations.
- FIG. 8 is a schematic structural diagram of a payment apparatus according to Embodiment 7 of the present application. As shown in Figure 8, the apparatus 80 includes:
- the receiving module 801 is configured to receive a two-dimensional code generation request sent by the terminal;
- the first sending module 802 is configured to send a two-dimensional code address to the terminal according to the two-dimensional code generation request, so that the terminal generates a two-dimensional code including a two-dimensional code failure time according to the two-dimensional code address.
- the second sending module 803 is configured to send payment incomplete information to the terminal, so that the terminal stops polling, where the payment incomplete information is information that the payment operation is not completed within the time limit of the two-dimensional code .
- the device further includes a third sending module 804, configured to send, according to the two-dimensional code generation request, a two-dimensional code expiration time to the terminal, so that the terminal is invalid according to the two-dimensional code.
- the time and the two-dimensional code address generate a two-dimensional code including a two-dimensional code failure time.
- FIG. 9 is a hardware structure diagram of a terminal 90 for a two-dimensional code payment method according to an embodiment of the present application.
- the terminal 90 includes:
- One or more processors 901 and memory 902, one processor 901 is taken as an example in FIG.
- the processor 901 and the memory 902 may be connected by a bus or other means, as exemplified by a bus connection in FIG.
- the terminal that performs the two-dimensional code payment method may further include: an input device 903 and an output device 904.
- the processor 901, the memory 902, the input device 903, and the output device 904 may be connected by a bus or other means, as exemplified by a bus connection in FIG.
- the memory 902 is a non-volatile computer readable storage medium, and can be used for storing a non-volatile software program, a non-volatile computer executable program, and a module, such as a two-dimensional code payment method in the embodiment of the present application.
- Corresponding program instructions/modules for example, the transmitting module 701, the first receiving module 702, the first generating module 703, the polling module 704, the stopping module 705, the second receiving module 706, and the preset module 707 shown in FIG.
- the second generation module 708, the third receiving module 709, and the activation module 710) executes various functional applications and data processing of the server by executing non-volatile software programs, instructions, and modules stored in the memory 122, that is, implementing a two-dimensional code payment method of the above method embodiment.
- the memory 901 may include a storage program area and a storage data area, wherein the storage program area may store an operating system, an application required for at least one function; the storage data area may store data created according to usage of the payment device, and the like.
- memory 902 can include high speed random access memory, and can also include non-volatile memory, such as at least one magnetic disk storage device, flash memory device, or other non-volatile solid state storage device.
- memory 902 can optionally include memory remotely located relative to processor 901, which can be connected to the payment device over a network. Examples of such networks include, but are not limited to, the Internet, intranets, local area networks, mobile communication networks, and combinations thereof.
- the input device 903 can receive the input digital or character information and generate a key signal input related to user settings and function control of the two-dimensional code payment device.
- Output device 904 can include a display device such as a display screen.
- the one or more modules are stored in the memory 902, and when executed by the one or more processors 901, perform a two-dimensional code payment method in any of the foregoing method embodiments performed on the terminal side, For example, performing the method steps S21 to S24 in FIG. 2 described above, the method steps S31 to S36 in FIG. 3, implementing the method steps S41 to S46 in FIG. 4, and implementing the method steps S51 to S in FIG. S54, the functions of the modules 701-710 in FIG. 7 are implemented.
- the terminal of the embodiment of the present application exists in various forms, including but not limited to:
- Mobile communication devices These devices are characterized by mobile communication functions and are mainly aimed at providing voice and data communication.
- Such terminals include: smart phones (such as iPhone), multimedia phones, functional phones, and low-end phones.
- Ultra-mobile personal computer equipment This type of equipment belongs to the category of personal computers, has computing and processing functions, and generally has mobile Internet access.
- Such terminals include: PDAs, MIDs, and UMPC devices, such as the iPad.
- Portable entertainment devices These devices can display and play multimedia content. Such devices include: audio, video players (such as iPod), handheld game consoles, e-books, and smart toys and portable car navigation devices.
- An embodiment of the present application provides a non-transitory computer readable storage medium storing computer-executable instructions that, when executed by an electronic device, cause the electronic device to perform the above A two-dimensional code payment method in any one of the method embodiments applied to the terminal, for example, performing the method steps S21 to S24 in FIG. 2 described above, and the method steps S31 to S36 in FIG. 3, implementing the method in FIG.
- the method steps S41 to S46, and the method steps S51 to S54 in FIG. 5 are implemented to implement the functions of the functions of the modules 701-710 in FIG.
- FIG. 10 is a schematic diagram of a hardware structure of a server 100 for a two-dimensional code payment method according to an embodiment of the present application.
- the server 100 includes:
- One or more processors 1001 and a memory 1002, one processor 1001 is taken as an example in FIG.
- the processor 1001 and the memory 1002 may be connected by a bus or other means, as exemplified by a bus connection in FIG.
- the memory 1002 is a non-volatile computer readable storage medium, and can be used for storing a non-volatile software program, a non-volatile computer executable program, and a module, such as a two-dimensional code payment method in the embodiment of the present application.
- Corresponding program instructions/modules for example, the receiving module 801, the first transmitting module 802, and the second transmitting module 803 shown in FIG. 8).
- the processor 1001 executes various functional applications and data processing of the server by executing non-volatile software programs, instructions, and modules stored in the memory 1002, that is, implementing a two-dimensional code payment method of the above method embodiment.
- the memory 1002 may include a storage program area and an storage data area, wherein the storage program area may store an operating system, an application required for at least one function; the storage data area may store data created according to usage of the payment device, and the like. Further, the memory 1002 may include a high speed random access memory, and may also include a nonvolatile memory such as at least one magnetic disk storage device, flash memory device, or other nonvolatile solid state storage device. In some embodiments, the memory 1002 can optionally include memory remotely located relative to the processor 1001 that can be connected to the payment device over a network. Examples of such networks include, but are not limited to, the Internet, intranets, local area networks, mobile communication networks, and combinations thereof.
- the one or more modules are stored in the memory 1002, and when executed by the one or more processors 1001, perform a two-dimensional code payment method in any of the above-described method embodiments performed on the server side, For example, the method steps S61 to S63 in FIG. 6 and the functions of the modules 801-804 in FIG. 8 are implemented as described above.
- the server of the embodiment of the present application exists in various forms, including but not limited to:
- Mobile communication devices These devices are characterized by mobile communication functions and are provided Voice and data communication are the main goals.
- Such terminals include: smart phones (such as iPhone), multimedia phones, functional phones, and low-end phones.
- Ultra-mobile personal computer equipment This type of equipment belongs to the category of personal computers, has computing and processing functions, and generally has mobile Internet access.
- Such terminals include: PDAs, MIDs, and UMPC devices, such as the iPad.
- Portable entertainment devices These devices can display and play multimedia content. Such devices include: audio, video players (such as iPod), handheld game consoles, e-books, and smart toys and portable car navigation devices.
- An embodiment of the present application provides a non-transitory computer readable storage medium storing computer-executable instructions that, when executed by an electronic device, cause the electronic device to perform the above A two-dimensional code payment method in any of the method embodiments applied to the server, for example, performing the above-described method steps S61 to S63 in FIG. 6 to implement the functions of the modules 801-804 in FIG.
- the terminal stops polling the server. Therefore, with this approach, it reduces the terminal's constant polling of the server during the payment process and puts additional pressure on the server for the server to handle other payment operations.
- the device embodiments described above are merely illustrative, wherein the units described as separate components may or may not be physically separate, and the components displayed as units may or may not be physical units, ie may be located A place, or it can be distributed to multiple network units. Some or all of the modules may be selected according to actual needs to achieve the purpose of the solution of the embodiment.
- the various embodiments can be implemented by means of software plus a general hardware platform, and of course, by hardware.
- a person skilled in the art can understand that all or part of the process of implementing the above embodiments can be completed by a computer program to instruct related hardware, and the program can be stored in a computer readable storage medium.
- the storage medium may be a magnetic disk, an optical disk, a read-only memory (ROM), or a random access memory (RAM). Wait.
Landscapes
- Business, Economics & Management (AREA)
- Engineering & Computer Science (AREA)
- Accounting & Taxation (AREA)
- Strategic Management (AREA)
- Physics & Mathematics (AREA)
- General Business, Economics & Management (AREA)
- General Physics & Mathematics (AREA)
- Theoretical Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Finance (AREA)
- Cash Registers Or Receiving Machines (AREA)
- Financial Or Insurance-Related Operations Such As Payment And Settlement (AREA)
Abstract
本申请公开一种支付方法、装置、终端以及服务器。其中，该方法包括：向服务器发送二维码生成请求；接收所述服务器根据所述二维码生成请求返回的二维码地址；根据所述二维码地址，生成包括二维码失效时间的二维码，并且轮询所述服务器；当接收到所述服务器发送的支付未完成信息时，则停止轮询所述服务器；其中，所述支付未完成信息为所述二维码失效时间内未完成支付操作的信息。在本申请中，通过设置包括二维码失效时间的二维码，当用户在二维码失效时间之内未进行扫码并且完成支付，终端便停止轮询服务器，减少了终端在支付过程中不断轮询服务器而给服务器带来额外的压力，以便服务器处理其它支付操作。
Description
交叉参考
本申请要求于2016年6月6日提交中国专利局，申请号为
201610392616.7的中国专利申请的优先权，其全部内容通过引用结合在本
申请中。
本申请涉及计算机技术领域，尤其涉及一种支付方法、装置、终端以及服务器。
随着互联网技术的发展，移动终端可以对在PC端生成的支付页面中的二维码进行扫码而完成支付，极大方便了用户支付，从而促进移动金融经济的繁荣。
发明人在实现本申请的过程中，发现现有技术至少存在以下问题：当一个订单的支付请求被封装成二维码，用户扫描二维码支付后，页面需要及时作出支付结果的响应。因页面无法监测用户是否完成了支付，需要主动去获取订单的状态。因此会频繁发起轮询请求以及时告知用户支付结果。如果用户长时间未能进行支付，则意味着需要发出大量的请求，给服务器造成较大压力。
发明内容
为了克服上述技术问题，本申请实施例目的旨在提供一种二维码支付方法和终端以及服务器，以解决现有技术因用户长时间未能进行支付，而发出大量的请求造成服务器压力过大的技术问题。
为解决上述技术问题，本申请实施例提供以下技术方案：
在第一方面，本申请实施例提供一种支付方法，应用于终端，所述方法包括：
向服务器发送二维码生成请求；
接收所述服务器根据所述二维码生成请求返回的二维码地址；
根据所述二维码地址，生成包括二维码失效时间的二维码，并且轮询所述服务器；
当接收到所述服务器发送的支付未完成信息时，则停止轮询所述服务器；其中，所述支付未完成信息为所述二维码失效时间内未完成支付操作的信息。
可选地，所述方法还包括：
接收所述服务器根据所述二维码生成请求返回的二维码失效时间；则：
所述根据所述二维码地址生成包括二维码失效时间的二维码，具体为：
根据所述返回的二维码失效时间和所述二维码地址，生成包括二维码失效时间的二维码。
可选地，所述方法还包括：
预设二维码失效时间；则：
所述根据所述二维码地址，生成包括二维码失效时间的二维码，具体为：
根据所述预设的二维码失效时间和所述二维码地址，生成包括二维码失效时间的二维码。
可选地，所述停止轮询所述服务器之后，包括：
在所述二维码区域相对的位置生成遮盖层。
可选地，所述方法包括：
接收在二维码已经失效的支付页面下进行刷新的刷新请求；
根据所述刷新请求，激活所述生成遮盖层的二维码，并且轮询所述服务器。
在第二方面，本申请实施例提供一种支付方法，应用于服务器，所述方法包括：
接收终端发送的二维码生成请求；
根据所述二维码生成请求，向所述终端发送二维码地址，以使所述终端根据所述二维码地址，生成包括二维码失效时间的二维码和进行轮询；
向所述终端发送支付未完成信息，以使所述终端停止轮询；其中，所述支付未完成信息为所述二维码失效时间内未完成支付操作的信息。
可选地，所述方法还包括：
根据所述二维码生成请求，向所述终端发送二维码失效时间，以使所述终端根据所述二维码失效时间和所述二维码地址，生成包括二维码失效时间的二维码。
在第三方面，本申请实施例提供一种支付装置，所述装置包括：
发送模块，用于向服务器发送二维码生成请求；
第一接收模块，用于接收所述服务器根据所述二维码生成请求返回的二维码地址；
第一生成模块，用于根据所述二维码地址，生成包括二维码失效时间的二维码，并且轮询所述服务器；
轮询模块，用于轮询所述服务器；
停止模块，用于当接收到所述服务器发送的支付未完成信息时，则停止轮询所述服务器；其中，所述支付未完成信息为所述二维码失效时间内未完成支付操作的信息。
可选地，所述装置还包括：
第二接收模块，用于接收所述服务器根据所述二维码生成请求返回的二维码失效时间；则：
所述第一生成模块还具体用于：根据所述二维码失效时间和所述二维码地址，生成包括二维码失效时间的二维码。
可选地，所述装置还包括：
预设模块，用于预设二维码失效时间；则：
所述第一生成模块还具体用于：
根据所述预设的二维码失效时间和所述二维码地址，生成包括二维码失效时间的二维码。
可选地，所述装置还包括第二生成模块，用于在所述二维码区域相对的位置生成遮盖层。
可选地，所述装置还包括
第三接收模块，用于接收在二维码已经失效的支付页面下进行刷新的刷新请求；
激活模块，用于根据所述刷新请求，激活所述生成遮盖层的二维码。
在第四方面，本申请实施例提供一种支付装置，所述装置包括：
接收模块，用于接收终端发送的二维码生成请求；
第一发送模块，用于根据所述二维码生成请求，向所述终端发送二维码地址，以使所述终端根据所述二维码地址，生成包括二维码失效时间的二维码和进行轮询；
第二发送模块，用于向所述终端发送支付未完成信息，以使所述终端停止轮询；其中，所述支付未完成信息为所述二维码失效时间内未完成支付操作的信息。
可选地，所述装置还包括第三发送模块，用于根据所述二维码生成请求，向所述终端发送二维码失效时间，以使所述终端根据所述二维码失效时间和所述二维码地址，生成包括二维码失效时间的二维码。第五方面，本申请实施例还提供了一种终端，包括：
至少一个处理器；以及，
与所述至少一个处理器通信连接的存储器；其中，
所述存储器存储有可被所述至少一个处理器执行的指令，所述指令被所述至少一个处理器执行，以使所述至少一个处理器能够执行如上所述的方法。
第六方面，本申请实施例还提供了一种非易失性计算机可读存储介质，所述计算机可读存储介质存储有计算机可执行指令，当所述计算机可执行指令被电子设备执行时，使所述电子设备执行如上所述的应用于终端的方法。
第七方面，本申请实施例还提供了一种计算机程序产品，所述计算机程序产品包括存储在非易失性计算机可读存储介质上的计算机程序，所述计算机程序包括程序指令，当所述程序指令被电子设备执行时，使所述电子设备执行如上所述的应用于终端的方法。
第八方面，本申请实施例还提供了一种服务器，包括：
至少一个处理器；以及，
与所述至少一个处理器通信连接的存储器；其中，
所述存储器存储有可被所述至少一个处理器执行的指令，所述指令被所述至少一个处理器执行，以使所述至少一个处理器能够执行如上所述的方法。
第九方面，本申请实施例还提供了一种非易失性计算机可读存储介质，所述计算机可读存储介质存储有计算机可执行指令，当所述计算机可执行指令被电子设备执行时，使所述电子设备执行如上所述的应用于服务器方法。
第十方面，本申请实施例还提供了一种计算机程序产品，所述计算机程序产品包括存储在非易失性计算机可读存储介质上的计算机程序，所述计算机程序包括程序指令，当所述程序指令被电子设备执行时，使所述电子设备执行如上所述的应用于服务器方法。
在本申请实施例中，通过设置包括二维码失效时间的二维码，当用户在二维码失效时间之内未进行扫码并且完成支付，终端便停止轮询服务器，减少了终端在支付过程中不断轮询服务器而给服务器带来额外的压力，以便服务器处理其它支付操作。
一个或多个实施例通过与之对应的附图中的图片进行示例性说明，这些示例性说明并不构成对实施例的限定，附图中具有相同参考数字标号的元件表示为类似的元件，除非有特别申明，附图中的图不构成比例限制。
图1是本申请实施例提供一种二维码支付方法的可能应用场景；
图1a是图1所示的可能应用场景的一种可能支付页面；
图2是本申请实施例一提供的二维码支付方法的流程示意图；
图3是本申请实施例二提供的二维码支付方法的流程示意图；
图3a是本申请实施例一提供的一种可能的二维码失效样式示意图；
图4是本申请实施例三提供的二维码支付方法的流程示意图；
图5是本申请实施例四提供的二维码支付方法的流程示意图；
图6是本申请实施例五提供的二维码支付方法的流程示意图；
图7是本申请实施例六提供的一种支付装置的结构示意图；
图8是本申请实施例七提供的一种支付装置的结构示意图；
图9是本申请实施例提供的二维码支付方法的处理方法的终端的硬件结构示意图。
图10是本申请实施例提供的二维码支付方法的处理方法的服务器的硬
件结构示意图。
为了使本申请的目的、技术方案及优点更加清楚明白，以下结合附图及本申请实施例，对本申请进行进一步详细说明。应当理解，此处所描述的具体本申请实施例仅用以解释本申请，并不用于限定本申请。
图1是本申请实施例提供一种二维码支付方法的可能应用场景。在一些可能应用场景，如图1所示，该应用场景包括智能终端11、计算机12、业务方13以及第三方支付平台14。用户10在计算机12处完成下单，并通过计算机12处进入支付页面1a1。请参考图1a，图1a是图1所示的可能应用场景的一种可能支付页面。如图1a所示，在支付页面1a1处，支付页面1a1包括多种第三方支付平台，其中至少有一个第三方支付平台支持二维码支付方式1a11。在一些可能的实现方式中，支付页面还可以包括不同的第三方平台支付方式，比如说网银支付等等。如图1所示，用户10进入支付页面1a1后，采用智能终端11对二维码支付方式1a11进行扫码，在正常情况下，扫码成功后，用户通过智能终端11在第三方支付平台14完成支付，如果支付成功，第三方支付平台14通知业务方13用户支付成功，此时业务方13便可实施下一步骤，比如说发货、提示用户支付成功等等。
现有技术中，在用户进入支付页面1a1后，计算机12的支付前端不断轮询业务方13的服务器131，直至业务方13告知计算机12的支付前端用户支付成功，计算机12的支付前端才会停止轮询业务方13的服务器131，因此，该方法极大地增加了服务器的压力。在一些网络异常或者其它情况导致第三方支付平台14不能如实或者正确将用户支付成功信息发送给业务方13，导致业务方13不能进一步将支付成功信息反馈给计算机12的支付前端，以使计算机12的支付前端停止轮询业务方13的服务器131。
请再参考图1，在本申请实施例提供的可能应用场景中，通过在计算机12设置包括二维码失效时间的二维码，当用户在二维码失效时间之内未进行扫码并且完成支付，计算机12的支付前端便停止业务方13的服务器131。因此，采用该方法，其减少了计算机12在支付过程中不断轮询业务方13的服务器131而给服务器131带来额外的压力，同时也提高用户在支付过
程中用户体验，并且尽量避免一些异常情况而进一步加重服务器131的压力，从而使支付系统更加可靠的工作。本领域的技术人员应当明白：还可以在移动终端或者其它电子设备上设置包括二维码失效时间的二维码，此处不局限于上述所训导的实施方式。
实施例一
请参考图2，图2是本申请实施例一提供的二维码支付方法的流程示意图。该方法包括：
S21、向服务器发送二维码生成请求；
作为本申请实施例的一种实施方式，用户先在终端的商城完成注册、认证和登陆。登陆后，用户在终端中商城的购买页面进行选购物品，并且针对选购的物品完成下单的操作，并且进入支付页面。请再参考图1a，在支付页面1a1上，其包括多种第三方支付平台，比如说A支付平台、B支付平台、C网银支付平台、D快捷支付平台以及E分期支付平台。所述至少一个支付平台支持二维码支付方式。如图1a，在A支付平台下，其支持两种支付方式，第一种是二维码支付方式1a11，第二种是电脑端支付方式。用户使用便携式智能设备扫描二维码支付方式1a11，便可以在便携式智能设备进行支付。此处，便携式智能设备包括智能手机、平板电脑、智能手表以及其它便携式智能设备。可选地，用户还可以选择电脑端支付方式来进行支付。
此时，终端向服务器发送二维码生成请求，请求服务器返回二维码地址。服务器应答该二维码请求，根据终端的IP地址和端口号，对终端返回二维码地址。其中，该二维码生成请求可以是Http请求。
此处，终端可以通过无线网络或者有线网络将符合传输协议和解析协议的二维码生成请求，发送给服务器。
S22、接收所述服务器根据所述二维码生成请求返回的二维码地址；
该二维码生成请求包括终端身份识别信息和二维码生成内容信息，服务器根据该终端身份识别信息，对终端返回二维码地址。其中，该二维码地址可以是统一资源定位符(Uniform Resource Locator URL)。
S23、根据所述二维码地址，生成包括二维码失效时间的二维码，并且轮询所述服务器；
终端根据服务器返回的二维码地址URL，生成包括二维码失效时间的二维码。二维码失效时间是二维码从激活到失效的时间段，此处的失效指用户不能再次通过便携式智能设备对二维码进行扫码。
在本申请实施例中，二维码失效时间的设置是由业务方根据作业目的来自行设置。比如说，本申请实施例的二维码失效时间是120秒，从终端生成二维码开始，超过120秒业务方的服务器还没将用户支付成功的信息反馈给终端，终端自动使二维码失效。
在本申请实施例中，所述轮询是关于用户是否已经支付成功。其中，该用户支付成功信息是由第三方支付平台将支付成功信息反馈给业务方的服务器，然后业务方的服务器将该支付成功信息进一步地反馈给终端的支付前端。可选地，该轮询是http请求。
S24、当接收到所述服务器发送的支付未完成信息时，则停止轮询所述服务器。
在本申请实施例中，支付未完成信息可以是用户在二维码失效时间内未完成支付操作的信息，也可能是第三方支付平台由于网络故障或者第三方支付平台服务器崩溃等原因，使业务方的服务器未接收到第三方支付平台发送的成功支付信息而导致业务方的服务器判断用户在二维码失效时间内未完成支付操作的信息。
终端在对服务器不断轮询的过程中，如果接收到服务器发送的用户在二维码失效时间内未完成支付操作的信息，便停止轮询服务器。如果接收到服务器发送的用户在二维码失效时间内完成支付操作的结果，便自动跳转至支付成功页面，以提示用户支付成功。
在本申请实施例中，通过在终端设置包括二维码失效时间的二维码，当用户在二维码失效时间之内未进行扫码并且完成支付，终端便停止轮询服务器。因此，采用该方法，其减少了终端在支付过程中不断轮询服务器而给服务器带来额外的压力，以便服务器处理其它支付操作。
实施例二
请参考图3，图3是本申请实施例二提供的二维码支付方法的流程示意图。如图3所示，该方法包括：
S31、向服务器发送二维码生成请求；
S32、接收所述服务器根据所述二维码生成请求返回的二维码地址；
S33、接收所述服务器根据所述二维码生成请求返回的二维码失效时间；
在本申请实施例中，二维码失效时间的设置是由业务方根据作业目的来自行设置。比如说，本申请实施例的二维码失效时间是120秒，从终端生成二维码开始，超过120秒业务方的服务器还没将用户支付成功的信息反馈给终端，终端自动使二维码失效。
S34、根据所述返回的二维码失效时间和所述二维码地址，生成包括二维码失效时间的二维码，并且轮询所述服务器；
在本申请实施例中，此处的二维码和二维码失效时间是对应的，二维码失效时间是二维码从激活到失效的时间段，此处的失效指用户不能再次通过便携式智能设备对二维码进行扫码。当二维码处于有效的时间超过二维码失效时间时，此时的二维码开始进入失效状态。
S35、当接收到所述服务器发送的支付未完成信息时，则停止轮询所述服务器；其中，所述支付未完成信息为所述二维码失效时间内未完成支付操作的信息；
S36、在所述二维码区域相对的位置生成遮盖层。
请参考图3a，图3a是本申请实施例二提供的一种可能的二维码失效样式示意图。在本申请实施例中，使二维码失效的方式多种多样，比如说，如图3a所示，在支付页面1a1上的二维码区域1a11对应的位置生成遮盖层3a1，以遮挡用户对处于二维码区域3a11的二维码进行扫码，从侧面来说，也就使处于二维码区域3a11的二维码失效了。可选地，此处的遮盖层3a1是刷新页面。此处，终端还可以自行任意生成非原来的二维码，用户的便携式智能设备不能正确解析该二维码，从侧面来说，也就是使原来的二维码失效了。
在本申请实施例中，通过在终端设置包括二维码失效时间的二维码，当用户在二维码失效时间之内未进行扫码并且完成支付，终端便停止轮询服务器。因此，采用该方法，其减少了终端在支付过程中不断轮询服务器而给服务器带来额外的压力，以便服务器处理其它支付操作。
实施例三
请参考图4，图4是本申请实施例三提供的二维码支付方法的流程示意图。如图4所示，该方法包括：
S41、向服务器发送二维码生成请求；
S42、接收所述服务器根据所述二维码生成请求返回的二维码地址；
S43、预设二维码失效时间；
在本申请实施例中，设计者根据作业目的来自行预设二维码失效时间。
S44、根据所述预设的二维码失效时间和所述二维码地址，生成包括二维码失效时间的二维码，并且轮询所述服务器；
在本申请实施例中，预设的二维码失效时间和二维码地址之间是具有对应关系的。设计者根据作业目的，预先设置多个二维码失效时间表，对于不同的二维码地址，通过查找二维码失效时间表，匹配出对应于该二维码地址的二维码失效时间，因此根据二维码地址生成的二维码也对应于特定的二维码失效时间。因此，设计者通过灵活设置二维码失效时间表，根据特定的二维码地址，生成包括特定二维码失效时间的二维码。
在本申请实施例中，当用户进入终端的支付页面时，就开始二维码失效时间开始运行。此处的运行可是倒计时，也可以是累加计时。比如说事先预设二维码失效时间是120秒，当二维码失效时间倒计时至0秒时，并且在该过程中，当用户在终端的支付页面的计时到达计时终点时，尚未完成支付，并且业务方还没将支付成功的信息反馈给终端，终端自动使二维码失效，并且停止轮询服务器。又比如，二维码失效时间从0秒开始累计计时，当时间累加到120秒时，并且在该过程中，当用户在终端的支付页面的计时到达计时终点时，尚未完成支付，并且业务方还没将支付成功的信息反馈给终端，终端自动使二维码失效，并且停止轮询服务器。
进一步的，终端还可以设置其它表征物来代替二维码的失效时间。比如说，在用户进入终端的支付页面时，终端自动生成一个非二维码的表征物，其中该表征物包括表征物的失效时间。用户在超过表征物的失效时间内尚未完成支付，并且业务方还没将支付成功的信息反馈给终端，终端自动使二维码失效，并且停止轮询服务器。
S45、当接收到所述服务器发送的支付未完成信息时，则停止轮询所述服务器；其中，所述支付未完成信息为所述二维码失效时间内未完成支付
操作的信息；
S46、在所述二维码区域相对的位置生成遮盖层。
在本申请实施例中，通过在终端设置包括二维码失效时间的二维码，当用户在二维码失效时间之内未进行扫码并且完成支付，终端便停止轮询服务器。因此，采用该方法，其减少了终端在支付过程中不断轮询服务器而给服务器带来额外的压力，以便服务器处理其它支付操作。
实施例四
请参考图5，图5是本申请实施例四提供的二维码支付方法的流程示意图。如图5所示，该方法包括：
S51、接收在二维码已经失效的支付页面下进行刷新的刷新请求；
在本申请实施例中，支付页面的前端会设置刷新按钮，在二维码已经失效的支付页面的情况下，用户通过单击该刷新按钮对该支付页面进行刷新，从而产生刷新请求。
S52、根据所述刷新请求，激活所述生成遮盖层的二维码；
激活后的二维码所包括的二维码失效时间跟随着二维码的激活，开始进入计时状态。在本申请实施例中，当二维码失效时间到达时，此时的二维码进入失效状态。
请再参考图3a。在本申请实施例中，终端根据该刷新请求，激活该二维码，此时在二维码区域3a11相对的位置生成的遮盖层3a1已经被撤销，从而展示出二维码。用户使用智能便携式设备对该二维码进行扫码，便可以实现支付操作。采用此方式，一方面，无需终端重新向服务器发送二维码生成请求，只需要激活支付页面前端的二维码，便可以满足下一次支付所需的扫码的需要，因此减少终端访问服务器带来的额外负荷；另一方面，采用该方式，无需用户重新进入支付页面，只需要对支付页面进行刷新，便可以获取新的二维码，从而方便用户进行快捷地支付。
S53、轮询所述服务器；
S54、当接收到所述服务器发送的支付未完成信息时，则停止轮询所述服务器。
在本申请实施例中，支付未完成信息为该二维码失效时间内未完成支付操作的信息。
在本申请实施例中，通过在终端设置包括二维码失效时间的二维码，当用户在二维码失效时间之内未进行扫码并且完成支付，终端便停止轮询服务器。因此，采用该方法，其减少了终端在支付过程中不断轮询服务器而给服务器带来额外的压力，以便服务器处理其它支付操作。
实施例五
请参考图6，图6是本申请实施例五提供的二维码支付方法的流程示意图。如图6所示，该方法包括：
S61、接收终端发送的二维码生成请求；
此时，终端向服务器发送二维码生成请求，请求服务器返回二维码地址。服务器应答该二维码请求，根据终端的IP地址和端口号，对终端返回二维码地址。其中，该二维码生成请求可以是Http请求。
此处，终端可以通过无线网络或者有线网络将符合传输协议和解析协议的二维码生成请求，发送给服务器。
S62、根据所述二维码生成请求，向所述终端发送二维码地址，以使所述终端根据所述二维码地址，生成包括二维码失效时间的二维码和进行轮询；
该二维码生成请求包括终端身份识别信息和二维码生成内容信息，服务器根据该终端身份识别信息，对终端返回二维码地址。其中，该二维码地址可以是统一资源定位符(Uniform Resource Locator URL)。
终端根据服务器返回的二维码地址URL，生成包括二维码失效时间的二维码。二维码失效时间是二维码从激活到失效的时间段，此处的失效指用户不能再次通过便携式智能设备对二维码进行扫码。
在本申请实施例中，二维码失效时间的设置是由业务方根据作业目的来自行设置。比如说，本申请实施例的二维码失效时间是120秒，从终端生成二维码开始，超过120秒业务方的服务器还没将用户支付成功的信息反馈给终端，终端自动使二维码失效。
在本申请实施例中，所述轮询是关于用户是否已经支付成功。其中，该用户支付成功信息是由第三方支付平台将支付成功信息反馈给业务方的服务器，然后业务方的服务器将该支付成功信息进一步地反馈给终端的支付前端。可选地，该轮询是http请求。
S63、向所述终端发送支付未完成信息，以使所述终端停止轮询。
其中，所述支付未完成信息为所述二维码失效时间内未完成支付操作的信息。
在本申请实施例中，支付未完成信息可以是用户在二维码失效时间内未完成支付操作的信息，也可能是第三方支付平台由于网络故障或者第三方支付平台服务器崩溃等原因，使业务方的服务器未接收到第三方支付平台发送的成功支付信息而导致业务方的服务器判断用户在二维码失效时间内未完成支付操作的信息。
终端在对服务器不断轮询的过程中，如果接收到服务器发送的用户在二维码失效时间内未完成支付操作的信息，便停止轮询服务器。如果接收到服务器发送的用户在二维码失效时间内完成支付操作的结果，便自动跳转至支付成功页面，以提示用户支付成功。
在本申请实施例中，通过在终端设置包括二维码失效时间的二维码，当用户在二维码失效时间之内未进行扫码并且完成支付，终端便停止轮询服务器。因此，采用该方法，其减少了终端在支付过程中不断轮询服务器而给服务器带来额外的压力，以便服务器处理其它支付操作。
实施例六
请参考图7，图7是本申请实施例六提供的一种支付装置的结构示意图。如图7所示，该装置70包括：
发送模块701，用于向服务器发送二维码生成请求；
第一接收模块702，用于接收所述服务器根据所述二维码生成请求返回的二维码地址；
第一生成模块703，用于根据所述二维码地址，生成包括二维码失效时间的二维码，并且轮询所述服务器；
轮询模块704，用于轮询所述服务器；
停止模块705，用于当接收到所述服务器发送的支付未完成信息时，则停止轮询所述服务器；其中，所述支付未完成信息为所述二维码失效时间内未完成支付操作的信息。
可选地，该装置70还包括：
第二接收模块706，用于接收所述服务器根据所述二维码生成请求返回
的二维码失效时间；则：
所述第一生成模块703还具体用于：根据所述二维码失效时间和所述二维码地址，生成包括二维码失效时间的二维码。
可选地，该装置70还包括：
预设模块707，用于预设二维码失效时间；则：
所述第一生成模块703还具体用于：
根据所述预设的二维码失效时间和所述二维码地址，生成包括二维码失效时间的二维码。
可选地，该装置还包括第二生成模块708，用于在所述二维码区域相对的位置生成遮盖层。
可选地，该装置70还包括
第三接收模块709，用于接收在二维码已经失效的支付页面下进行刷新的刷新请求；
激活模块710，用于根据所述刷新请求，激活该生成遮盖层的二维码。
在本申请实施例中，通过在终端设置包括二维码失效时间的二维码，当用户在二维码失效时间之内未进行扫码并且完成支付，终端便停止轮询服务器。因此，采用该方法，其减少了终端在支付过程中不断轮询服务器而给服务器带来额外的压力，以便服务器处理其它支付操作。
实施七
请参考图8，图8是本申请实施例七提供的一种支付装置的结构示意图。如图8所示，该装置80包括：
接收模块801，用于接收终端发送的二维码生成请求；
第一发送模块802，用于根据所述二维码生成请求，向所述终端发送二维码地址，以使所述终端根据所述二维码地址，生成包括二维码失效时间的二维码和进行轮询；
第二发送模块803，用于向所述终端发送支付未完成信息，以使所述终端停止轮询；其中，所述支付未完成信息为所述二维码失效时间内未完成支付操作的信息。
可选地，该装置还包括第三发送模块804，用于根据所述二维码生成请求，向所述终端发送二维码失效时间，以使所述终端根据所述二维码失效
时间和所述二维码地址，生成包括二维码失效时间的二维码。
在本申请实施例中，通过在终端设置包括二维码失效时间的二维码，当用户在二维码失效时间之内未进行扫码并且完成支付，终端便停止轮询服务器。因此，采用该方法，其减少了终端在支付过程中不断轮询服务器而给服务器带来额外的压力，以便服务器处理其它支付操作。实施例八
请参考图9，是本申请实施例提供的一种二维码支付方法的终端90的硬件结构示意图，如图9所示，该终端90包括：
一个或多个处理器901以及存储器902，图9中以一个处理器901为例。
处理器901和存储器902可以通过总线或者其他方式连接，图9中以通过总线连接为例。
执行二维码支付方法的终端还可以包括：输入装置903和输出装置904。
处理器901、存储器902、输入装置903和输出装置904可以通过总线或者其他方式连接，图9中以通过总线连接为例。存储器902作为一种非易失性计算机可读存储介质，可用于存储非易失性软件程序、非易失性计算机可执行程序以及模块，如本申请实施例中的一种二维码支付方法对应的程序指令/模块(例如，附图7所示的发送模块701、第一接收模块702、第一生成模块703、轮询模块704、停止模块705、第二接收模块706、预设模块707、第二生成模块708、第三接收模块709、激活模块710)。处理器121通过运行存储在存储器122中的非易失性软件程序、指令以及模块，从而执行服务器的各种功能应用以及数据处理，即实现上述方法实施例一种二维码支付方法。
存储器901可以包括存储程序区和存储数据区，其中，存储程序区可存储操作系统、至少一个功能所需要的应用程序；存储数据区可存储根据支付装置的使用所创建的数据等。此外，存储器902可以包括高速随机存取存储器，还可以包括非易失性存储器，例如至少一个磁盘存储器件、闪存器件、或其他非易失性固态存储器件。在一些实施例中，存储器902可选包括相对于处理器901远程设置的存储器，这些远程存储器可以通过网络连接至支付装置。上述网络的实例包括但不限于互联网、企业内部网、局域网、移动通信网及其组合。
输入装置903可接收输入的数字或字符信息，以及产生与二维码支付装置的用户设置以及功能控制有关的键信号输入。输出装置904可包括显示屏等显示设备。所述一个或者多个模块存储在所述存储器902中，当被所述一个或者多个处理器901执行时，执行上述任意在终端侧执行的方法实施例中的一种二维码支付方法，例如，执行以上描述的图2中的方法步骤S21至步骤S24，图3中的方法步骤S31至步骤S36，实现图4中的方法步骤S41至步骤S46、实现图5中的方法步骤S51至步骤S54，实现图7中模块701-710的功能。
上述产品可执行本申请实施例所提供的方法，具备执行方法相应的功能模块和有益效果。未在本实施例中详尽描述的技术细节，可参见本申请实施例所提供的方法。
本申请实施例的终端以多种形式存在，包括但不限于:
(1)移动通信设备:这类设备的特点是具备移动通信功能，并且以提供话音、数据通信为主要目标。这类终端包括:智能手机(例如iPhone)、多媒体手机、功能性手机，以及低端手机等。
(2)超移动个人计算机设备:这类设备属于个人计算机的范畴，有计算和处理功能，一般也具备移动上网特性。这类终端包括:PDA、MID和UMPC设备等，例如iPad。
(3)便携式娱乐设备:这类设备可以显示和播放多媒体内容。该类设备包括:音频、视频播放器(例如iPod)，掌上游戏机，电子书，以及智能玩具和便携式车载导航设备。
(4)其他具有数据交互功能的电子装置。
本申请实施例提供了一种非易失性计算机可读存储介质，所述计算机可读存储介质存储有计算机可执行指令，该计算机可执行指令被电子设备执行时，可使得上述电子设备执行上述任意应用于终端的方法实施例中的一种二维码支付方法，例如，执行以上描述的图2中的方法步骤S21至步骤S24，图3中的方法步骤S31至步骤S36，实现图4中的方法步骤S41至步骤S46、实现图5中的方法步骤S51至步骤S54，实现图7中模块701-710的功能的功能。
实施例九
请参考图10，是本申请实施例提供的一种二维码支付方法的服务器100的硬件结构示意图，如图10所示，该服务器100包括：
一个或多个处理器1001以及存储器1002，图10中以一个处理器1001为例。
处理器1001和存储器1002可以通过总线或者其他方式连接，图10中以通过总线连接为例。存储器1002作为一种非易失性计算机可读存储介质，可用于存储非易失性软件程序、非易失性计算机可执行程序以及模块，如本申请实施例中的一种二维码支付方法对应的程序指令/模块(例如，附图8所示的接收模块801、第一发送模块802，第二发送模块803)。处理器1001通过运行存储在存储器1002中的非易失性软件程序、指令以及模块，从而执行服务器的各种功能应用以及数据处理，即实现上述方法实施例一种二维码支付方法。
存储器1002可以包括存储程序区和存储数据区，其中，存储程序区可存储操作系统、至少一个功能所需要的应用程序；存储数据区可存储根据支付装置的使用所创建的数据等。此外，存储器1002可以包括高速随机存取存储器，还可以包括非易失性存储器，例如至少一个磁盘存储器件、闪存器件、或其他非易失性固态存储器件。在一些实施例中，存储器1002可选包括相对于处理器1001远程设置的存储器，这些远程存储器可以通过网络连接至支付装置。上述网络的实例包括但不限于互联网、企业内部网、局域网、移动通信网及其组合。
所述一个或者多个模块存储在所述存储器1002中，当被所述一个或者多个处理器1001执行时，执行上述任意在服务器侧执行的方法实施例中的一种二维码支付方法，例如，执行以上描述的实现图6中的方法步骤S61至步骤S63和实现图8中模块801-804的功能。
上述产品可执行本申请实施例所提供的方法，具备执行方法相应的功能模块和有益效果。未在本实施例中详尽描述的技术细节，可参见本申请实施例所提供的方法。
本申请实施例的服务器以多种形式存在，包括但不限于:
(1)移动通信设备:这类设备的特点是具备移动通信功能，并且以提供
话音、数据通信为主要目标。这类终端包括:智能手机(例如iPhone)、多媒体手机、功能性手机，以及低端手机等。
(2)超移动个人计算机设备:这类设备属于个人计算机的范畴，有计算和处理功能，一般也具备移动上网特性。这类终端包括:PDA、MID和UMPC设备等，例如iPad。
(3)便携式娱乐设备:这类设备可以显示和播放多媒体内容。该类设备包括:音频、视频播放器(例如iPod)，掌上游戏机，电子书，以及智能玩具和便携式车载导航设备。
(4)其他具有数据交互功能的电子装置。
本申请实施例提供了一种非易失性计算机可读存储介质，所述计算机可读存储介质存储有计算机可执行指令，该计算机可执行指令被电子设备执行时，可使得上述电子设备执行上述任意应用于服务器的方法实施例中的一种二维码支付方法，例如，执行以上描述的实现图6中的方法步骤S61至步骤S63，实现图8中模块801-804的功能。
在本申请实施例中，通过在终端设置包括二维码失效时间的二维码，当用户在二维码失效时间之内未进行扫码并且完成支付，终端便停止轮询服务器。因此，采用该方法，其减少了终端在支付过程中不断轮询服务器而给服务器带来额外的压力，以便服务器处理其它支付操作。
以上所描述的装置实施例仅仅是示意性的，其中所述作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是或者也可以不是物理单元，即可以位于一个地方，或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部模块来实现本实施例方案的目的。
通过以上的实施方式的描述，本领域普通技术人员可以清楚地了解到各实施方式可借助软件加通用硬件平台的方式来实现，当然也可以通过硬件。本领域普通技术人员可以理解实现上述实施例方法中的全部或部分流程是可以通过计算机程序来指令相关的硬件来完成，所述的程序可存储于一计算机可读取存储介质中，该程序在执行时，可包括如上述各方法的实施例的流程。其中，所述的存储介质可为磁碟、光盘、只读存储记忆体(Read-Only Memory,ROM)或随机存储记忆体(Random Access Memory,RAM)
等。
最后应说明的是：以上实施例仅用以说明本申请的技术方案，而非对其限制；在本申请的思路下，以上实施例或者不同实施例中的技术特征之间也可以进行组合，步骤可以以任意顺序实现，并存在如上所述的本申请的不同方面的许多其它变化，为了简明，它们没有在细节中提供；尽管参照前述实施例对本申请进行了详细的说明，本领域的普通技术人员应当理解：其依然可以对前述各实施例所记载的技术方案进行修改，或者对其中部分技术特征进行等同替换；而这些修改或者替换，并不使相应技术方案的本质脱离本申请各实施例技术方案的范围。
Claims (20)
- 一种支付方法，所述方法应用于终端，其特征在于，所述方法包括：向服务器发送二维码生成请求；接收所述服务器根据所述二维码生成请求返回的二维码地址；根据所述二维码地址，生成包括二维码失效时间的二维码，并且轮询所述服务器；当接收到所述服务器发送的支付未完成信息时，则停止轮询所述服务器；其中，所述支付未完成信息为所述二维码失效时间内未完成支付操作的信息。
- 根据权利要求1所述的方法，其特征在于，所述方法还包括：接收所述服务器根据所述二维码生成请求返回的二维码失效时间；则：所述根据所述二维码地址，生成包括二维码失效时间的二维码，具体为：根据所述返回的二维码失效时间和所述二维码地址，生成包括二维码失效时间的二维码。
- 根据权利要求1所述方法，其特征在于，所述方法还包括：预设二维码失效时间；则：所述根据所述二维码地址，生成包括二维码失效时间的二维码，具体为：根据所述预设的二维码失效时间和所述二维码地址，生成包括二维码失效时间的二维码。
- 根据权利要求1至3任一所述的方法，其特征在于，所述停止轮询所述服务器之后，包括：在所述二维码区域相对的位置生成遮盖层。
- 根据权利要求4所述的方法，其特征在于，所述方法包括：接收在二维码已经失效的支付页面下进行刷新的刷新请求；根据所述刷新请求，激活所述生成遮盖层的二维码，并且轮询所述服务器。
- 一种支付方法，所述方法应用于服务器，其特征在于，所述方法包 括：接收终端发送的二维码生成请求；根据所述二维码生成请求，向所述终端发送二维码地址，以使所述终端根据所述二维码地址，生成包括二维码失效时间的二维码和进行轮询；向所述终端发送支付未完成信息，以使所述终端停止轮询；其中，所述支付未完成信息为所述二维码失效时间内未完成支付操作的信息。
- 根据权利要求6所述的方法，其特征在于，所述方法还包括：根据所述二维码生成请求，向所述终端发送二维码失效时间，以使所述终端根据所述二维码失效时间和所述二维码地址，生成包括二维码失效时间的二维码。
- 一种支付装置，其特征在于，所述装置包括：发送模块，用于向服务器发送二维码生成请求；第一接收模块，用于接收所述服务器根据所述二维码生成请求返回的二维码地址；第一生成模块，用于根据所述二维码地址，生成包括二维码失效时间的二维码，并且轮询所述服务器；轮询模块，用于轮询所述服务器；停止模块，用于当接收到所述服务器发送的支付未完成信息时，则停止轮询所述服务器；其中，所述支付未完成信息为所述二维码失效时间内未完成支付操作的信息。
- 根据权利要求8所述的装置，其特征在于，所述装置还包括：第二接收模块，用于接收所述服务器根据所述二维码生成请求返回的二维码失效时间；则：所述第一生成模块还具体用于：根据所述二维码失效时间和所述二维码地址，生成包括二维码失效时间的二维码。
- 根据权利要求8所述的装置，其特征在于，所述装置还包括：预设模块，用于预设二维码失效时间；则：所述第一生成模块还具体用于：根据所述预设的二维码失效时间和所述二维码地址，生成包括二维码失效时间的二维码。
- 根据权利要求8至10任一所述的装置，其特征在于，所述装置还包括第二生成模块，用于在所述二维码区域相对的位置生成遮盖层。
- 根据权利要求11所述的装置，其特征在于，所述装置还包括第三接收模块，用于接收在二维码已经失效的支付页面下进行刷新的刷新请求；激活模块，用于根据所述刷新请求，激活所述生成遮盖层的二维码。
- 一种支付装置，其特征在于，所述装置包括：接收模块，用于接收终端发送的二维码生成请求；第一发送模块，用于根据所述二维码生成请求，向所述终端发送二维码地址，以使所述终端根据所述二维码地址，生成包括二维码失效时间的二维码和进行轮询；第二发送模块，用于向所述终端发送支付未完成信息，以使所述终端停止轮询；其中，所述支付未完成信息为所述二维码失效时间内未完成支付操作的信息。
- 根据权利要求13所述的装置，其特征在于，所述装置还包括第三发送模块，用于根据所述二维码生成请求，向所述终端发送二维码失效时间，以使所述终端根据所述二维码失效时间和所述二维码地址，生成包括二维码失效时间的二维码。
- 一种终端，其特征在于，包括：至少一个处理器；以及，与所述至少一个处理器通信连接的存储器；其中，所述存储器存储有可被所述至少一个处理器执行的指令，所述指令被所述至少一个处理器执行，以使所述至少一个处理器能够执行权利要求1-5任一项所述的方法。
- 一种服务器，其特征在于，包括：至少一个处理器；以及，与所述至少一个处理器通信连接的存储器；其中，所述存储器存储有可被所述至少一个处理器执行的指令，所述指令被所述至少一个处理器执行，以使所述至少一个处理器能够执行权利要求6或7所述的方法。
- 一种非易失性计算机可读存储介质，其特征在于，所述计算机可读存储介质存储有计算机可执行指令，当所述计算机可执行指令被电子设备执行时，使所述电子设备执行权利要求1-5任一项所述的方法。
- 一种非易失性计算机可读存储介质，其特征在于，所述计算机可读存储介质存储有计算机可执行指令，当所述计算机可执行指令被电子设备执行时，使所述电子设备执行权利要求6或7所述的方法。
- 一种计算机程序产品，其特征在于，所述计算机程序产品包括存储在非易失性计算机可读存储介质上的计算机程序，所述计算机程序包括程序指令，当所述程序指令被电子设备执行时，使所述电子设备执行权利要求1-5任一项所述的方法。
- 一种计算机程序产品，其特征在于，所述计算机程序产品包括存储在非易失性计算机可读存储介质上的计算机程序，所述计算机程序包括程序指令，当所述程序指令被电子设备执行时，使所述电子设备执行权利要求6或7所述的方法。
Applications Claiming Priority (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201610392616.7A CN106096945A (zh) | 2016-06-06 | 2016-06-06 | 一种支付方法、装置、终端、服务器以及支付系统 |
| CN201610392616.7 | 2016-06-06 |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| WO2017211019A1 true WO2017211019A1 (zh) | 2017-12-14 |
Family
ID=57448260
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| PCT/CN2016/099930 WO2017211019A1 (zh) | 2016-06-06 | 2016-09-23 | 一种支付方法、装置、终端以及服务器 |
Country Status (2)
| Country | Link |
|---|---|
| CN (1) | CN106096945A (zh) |
| WO (1) | WO2017211019A1 (zh) |
Cited By (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111431974A (zh) * | 2020-03-12 | 2020-07-17 | 安徽富煌科技股份有限公司 | 一种基于乘车实名登记的安全出行管理系统 |
| CN111612115A (zh) * | 2020-06-15 | 2020-09-01 | 支付宝(杭州)信息技术有限公司 | 交通卡的计次方法、装置、扫码设备和计次卡服务器 |
| CN111970252A (zh) * | 2020-07-29 | 2020-11-20 | 腾讯科技（深圳）有限公司 | 一种二维码显示控制方法及装置 |
| CN113936780A (zh) * | 2021-10-15 | 2022-01-14 | 郑州大学第三附属医院(河南省妇幼保健院) | 医疗管理方法及系统 |
| CN114022153A (zh) * | 2021-11-09 | 2022-02-08 | 盐城金堤科技有限公司 | 支付结果确定方法及其装置、计算机存储介质、电子设备 |
Families Citing this family (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107248071A (zh) * | 2017-06-06 | 2017-10-13 | 深圳正品创想科技有限公司 | 一种提高二维码消费凭证的安全性的方法及装置 |
| CN107580064A (zh) * | 2017-09-18 | 2018-01-12 | 北京京东尚科信息技术有限公司 | 二维码信息发送方法、装置及存储介质 |
| CN109559389A (zh) * | 2018-11-19 | 2019-04-02 | 北京悦畅科技有限公司 | 一种停车优免券的推送方法、服务器和停车优免系统 |
| CN111523626A (zh) * | 2019-02-02 | 2020-08-11 | 腾讯科技（深圳）有限公司 | 一种电子码的显示方法以及相关装置 |
| CN111950661A (zh) * | 2019-05-14 | 2020-11-17 | 阿里巴巴集团控股有限公司 | 二维码的展示方法及装置 |
| KR102174616B1 (ko) * | 2019-09-18 | 2020-11-05 | 황교찬 | 결제시스템 및 이의 결제방법 |
| CN111080273A (zh) * | 2019-12-02 | 2020-04-28 | 广州伊的家网络科技有限公司 | 一种聚合支付方法及其服务器、商户端 |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101252499A (zh) * | 2008-03-28 | 2008-08-27 | 程凯征 | 一种检查邮件服务器是否有新邮件到达的邮件服务器动态轮询方法 |
| CN103886456A (zh) * | 2014-03-17 | 2014-06-25 | 黄昱钊 | 基于动态显示二维码的支付系统及其实现方法 |
| CN105243539A (zh) * | 2015-09-15 | 2016-01-13 | 重庆智韬信息技术中心 | 实现二维码安全支付的身份认证方法 |
Family Cites Families (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102346890A (zh) * | 2010-07-30 | 2012-02-08 | 李嘉辉 | 网络支付方法及系统 |
| CN102999837A (zh) * | 2012-12-03 | 2013-03-27 | 中国民生银行股份有限公司 | 电子货币交易处理方法和手机银行服务器 |
| CN103729765B (zh) * | 2014-01-15 | 2016-02-17 | 腾讯科技（深圳）有限公司 | 一种验证控制方法、终端、服务器、终端设备及系统 |
-
2016
- 2016-06-06 CN CN201610392616.7A patent/CN106096945A/zh active Pending
- 2016-09-23 WO PCT/CN2016/099930 patent/WO2017211019A1/zh active Application Filing
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101252499A (zh) * | 2008-03-28 | 2008-08-27 | 程凯征 | 一种检查邮件服务器是否有新邮件到达的邮件服务器动态轮询方法 |
| CN103886456A (zh) * | 2014-03-17 | 2014-06-25 | 黄昱钊 | 基于动态显示二维码的支付系统及其实现方法 |
| CN105243539A (zh) * | 2015-09-15 | 2016-01-13 | 重庆智韬信息技术中心 | 实现二维码安全支付的身份认证方法 |
Cited By (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111431974A (zh) * | 2020-03-12 | 2020-07-17 | 安徽富煌科技股份有限公司 | 一种基于乘车实名登记的安全出行管理系统 |
| CN111612115A (zh) * | 2020-06-15 | 2020-09-01 | 支付宝(杭州)信息技术有限公司 | 交通卡的计次方法、装置、扫码设备和计次卡服务器 |
| CN111612115B (zh) * | 2020-06-15 | 2023-10-20 | 支付宝(杭州)信息技术有限公司 | 交通卡的计次方法、装置、扫码设备和计次卡服务器 |
| CN111970252A (zh) * | 2020-07-29 | 2020-11-20 | 腾讯科技（深圳）有限公司 | 一种二维码显示控制方法及装置 |
| CN111970252B (zh) * | 2020-07-29 | 2023-08-29 | 腾讯科技（深圳）有限公司 | 一种二维码显示控制方法、装置、电子设备及存储介质 |
| CN113936780A (zh) * | 2021-10-15 | 2022-01-14 | 郑州大学第三附属医院(河南省妇幼保健院) | 医疗管理方法及系统 |
| CN113936780B (zh) * | 2021-10-15 | 2022-09-27 | 郑州大学第三附属医院(河南省妇幼保健院) | 医疗管理方法及系统 |
| CN114022153A (zh) * | 2021-11-09 | 2022-02-08 | 盐城金堤科技有限公司 | 支付结果确定方法及其装置、计算机存储介质、电子设备 |
Also Published As
| Publication number | Publication date |
|---|---|
| CN106096945A (zh) | 2016-11-09 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| WO2017211019A1 (zh) | 一种支付方法、装置、终端以及服务器 | |
| US10055730B2 (en) | Method, terminal, server, device, and system of verification control | |
| US10887311B2 (en) | Method and apparatus for requesting usage permission, and method and apparatus for acquiring usage permission | |
| US20150319173A1 (en) | Co-verification method, two dimensional code generation method, and device and system therefor | |
| US9635018B2 (en) | User identity verification method and system, password protection apparatus and storage medium | |
| US8516239B2 (en) | Virtual authentication proxy server and terminal authentication server | |
| JP2019506661A (ja) | 支払い処理方法及び装置並びにインテリジェントデバイス | |
| WO2014075566A1 (zh) | 敏感操作验证方法、终端设备、服务器和验证系统 | |
| CN103634109A (zh) | 操作权限验证方法和装置 | |
| WO2017076186A1 (zh) | 手持移动设备滑动验证的方法及装置 | |
| US10831816B2 (en) | Method for controlling electronic picture frame, electronic picture frame, electronic picture frame cloud platform and mobile terminal | |
| CN104702677B (zh) | 链接处理方法、装置和系统 | |
| CN103886456A (zh) | 基于动态显示二维码的支付系统及其实现方法 | |
| WO2016025756A1 (en) | Form filling method and related terminal | |
| CN104539571B (zh) | 信息交互方法、身份鉴权方法、服务器及终端 | |
| CN108574721B (zh) | 一种登录方法、装置和服务器、用户终端、可读存储介质 | |
| US20200412712A1 (en) | Display system, display method, and recording medium | |
| US20220398062A1 (en) | Screen projection status determining method and apparatus | |
| CN110866239A (zh) | 验证码请求处理方法、装置、设备及计算机存储介质 | |
| WO2018059033A1 (zh) | 一种验证方法、服务器和系统 | |
| CN104052757B (zh) | 基于手机中的客户端应用的身份识别系统及方法 | |
| US11991161B2 (en) | Non-transitory computer-readable medium having instructions, communication system, and server | |
| KR20150100156A (ko) | 웹 기반 게임에서 클라이언트의 요청 신호 검증 방법 | |
| CN110730162B (zh) | 一种页面的验证方法、移动终端、可读存储介质 | |
| CN105095303B (zh) | 快速链接推送方法及快速链接推送装置 |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| 121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 16904468 Country of ref document: EP Kind code of ref document: A1 |
|
| NENP | Non-entry into the national phase |
Ref country code: DE |
|
| 122 | Ep: pct application non-entry in european phase |
Ref document number: 16904468 Country of ref document: EP Kind code of ref document: A1 |