CN113807854B - Method, apparatus, system, electronic device and medium for electronic payment - Google Patents

Method, apparatus, system, electronic device and medium for electronic payment Download PDF

Info

Publication number
CN113807854B
CN113807854B CN202011594722.6A CN202011594722A CN113807854B CN 113807854 B CN113807854 B CN 113807854B CN 202011594722 A CN202011594722 A CN 202011594722A CN 113807854 B CN113807854 B CN 113807854B
Authority
CN
China
Prior art keywords
seed
login
payment
response
determining
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Active
Application number
CN202011594722.6A
Other languages
Chinese (zh)
Other versions
CN113807854A (en
Inventor
张振华
樊宁
姚博勋
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Jingdong Technology Holding Co Ltd
Original Assignee
Jingdong Technology Holding Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Jingdong Technology Holding Co Ltd filed Critical Jingdong Technology Holding Co Ltd
Priority to CN202011594722.6A priority Critical patent/CN113807854B/en
Publication of CN113807854A publication Critical patent/CN113807854A/en
Application granted granted Critical
Publication of CN113807854B publication Critical patent/CN113807854B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

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/38—Payment protocols; Details thereof
    • G06Q20/40—Authorisation, e.g. identification of payer or payee, verification of customer or shop credentials; Review and approval of payers, e.g. check credit lines or negative lists
    • G06Q20/401—Transaction verification
    • G06Q20/4014—Identity check for transactions
    • 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/38—Payment protocols; Details thereof
    • G06Q20/382—Payment protocols; Details thereof insuring higher security of transaction
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00—Network architectures or network communication protocols for network security
    • H04L63/08—Network architectures or network communication protocols for network security for authentication of entities
    • H04L63/083—Network architectures or network communication protocols for network security for authentication of entities using passwords
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
    • H04L9/08—Key distribution or management, e.g. generation, sharing or updating, of cryptographic keys or passwords
    • H04L9/0891—Revocation or update of secret information, e.g. encryption key update or rekeying
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L2209/00—Additional information or applications relating to cryptographic mechanisms or cryptographic arrangements for secret or secure communication H04L9/00
    • H04L2209/56—Financial cryptography, e.g. electronic payment or e-cash

Landscapes

  • Engineering & Computer Science (AREA)
  • Business, Economics & Management (AREA)
  • Accounting & Taxation (AREA)
  • Computer Security & Cryptography (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Strategic Management (AREA)
  • Physics & Mathematics (AREA)
  • General Business, Economics & Management (AREA)
  • General Physics & Mathematics (AREA)
  • Theoretical Computer Science (AREA)
  • Finance (AREA)
  • Signal Processing (AREA)
  • Computer Hardware Design (AREA)
  • Computing Systems (AREA)
  • General Engineering & Computer Science (AREA)
  • Financial Or Insurance-Related Operations Such As Payment And Settlement (AREA)

Abstract

The embodiment of the disclosure discloses a method, a device, a system, a server, a terminal and a medium for electronic payment. One embodiment of the method comprises the following steps: acquiring a login state corresponding to a target user terminal; in response to receiving a seed acquisition request sent by the target user side, updating a seed corresponding to the login state, wherein the seed is used for generating a payment code; and sending the updated seeds to the target user terminal. According to the embodiment, only unique seeds are guaranteed to be effective at the same time, so that after an account is logged in offline, code scanning payment operation can be carried out on equipment which is logged in later only after another equipment logs in the account, and the risk of malicious account taking is reduced.

Description

Method, apparatus, system, electronic device and medium for electronic payment
Technical Field
Embodiments of the present disclosure relate to the field of computer technology, and in particular, to a method, an apparatus, a system, an electronic device, and a medium for electronic payment.
Background
With the development of mobile payment technology, a payment mode by presenting a payment code is increasingly used for convenience and rapidness.
In the prior art, based on the seed issued by the server, the payment terminal can generally generate a payment code by using a preset algorithm. In an actual application scene, the situation that the same user can pay after logging in a plurality of devices can occur, so that the risk of malicious account withdrawal exists.
Disclosure of Invention
Embodiments of the present disclosure propose methods, apparatuses, systems, electronic devices, and media for electronic payment.
In a first aspect, embodiments of the present disclosure provide a method for electronic payment, applied to a server, the method including: acquiring a login state corresponding to a target user terminal; in response to receiving a seed acquisition request sent by the target user side, updating a seed corresponding to the login state, wherein the seed is used for generating a payment code; and sending the updated seeds to the target user terminal.
In some embodiments, the obtaining the login state corresponding to the target ue includes: responding to a login request sent by a target user terminal, and determining whether login equipment information is included in the login request; in response to determining that the login request includes login device information, verifying user login verification information included in the login request; and generating a login state corresponding to the target user side in response to determining that the user login verification information passes verification.
In some embodiments, after obtaining the login state corresponding to the target client, the method further includes: generating and storing a corresponding relation between the login state and login equipment information; and updating the seed corresponding to the login state in response to receiving the seed acquisition request sent by the target user side, including: in response to receiving a seed acquisition request sent by a target user side, determining whether the seed acquisition request comprises login equipment information; in response to determining that the login device information is included in the seed acquisition request, determining whether the login device information included in the seed acquisition request matches the login device information in the stored correspondence; in response to determining a match, a seed corresponding to the login state is updated.
In some embodiments, the method further comprises: in response to receiving the code scanning payment request, determining whether a target seed corresponding to the code scanning payment request is consistent with the updated seed, wherein the code scanning payment request comprises payment code information, and a payment code indicated by the payment code information is generated based on the target seed; and responding to the fact that the seeds corresponding to the payment codes are consistent with the updated seeds, and paying according to the code scanning payment request.
In a second aspect, embodiments of the present disclosure provide a method for electronic payment, applied to a terminal, the method comprising: in response to detecting the payment code generation operation, obtaining a seed for generating the payment code; generating prompt information representing prohibition of payment in response to determining that the acquired seed is invalid; and displaying prompt information.
In some embodiments, the obtaining the seed for generating the payment code includes: determining the state of network connection between the server and the server for issuing seeds; in response to determining that the state of the network connection belongs to an offline state, locally acquiring the last acquired seed as a seed for generating a payment code; in response to determining that the state of the network connection belongs to an online state, sending a seed acquisition request to a server for issuing seeds; and receiving the seeds sent by the server.
In some embodiments, the method further comprises: in response to determining that the acquired seed has not failed, a payment code is generated.
In a third aspect, embodiments of the present disclosure provide an apparatus for electronic payment, applied to a server, the apparatus including: the first acquisition unit is configured to acquire a login state corresponding to the target user terminal; the updating unit is configured to respond to the received seed acquisition request sent by the target user side and update the seed corresponding to the login state, wherein the seed is used for generating a payment code; and the sending unit is configured to send the updated seeds to the target user side.
In some embodiments, the first obtaining unit includes: the first determining module is configured to determine whether login equipment information is included in a login request or not in response to receiving the login request sent by the target user side; a verification module configured to verify user login verification information included in the login request in response to determining that the login device information is included in the login request; and the generation module is configured to generate a login state corresponding to the target user side in response to determining that the user login verification information passes verification.
In some embodiments, the apparatus further comprises: and a first generation unit configured to generate and store a correspondence between the login state and login device information. The updating unit includes: the second determining module is configured to determine whether the seed acquisition request comprises login equipment information or not in response to receiving the seed acquisition request sent by the target user side; a third determining module configured to determine, in response to determining that the login device information is included in the seed acquisition request, whether the login device information included in the seed acquisition request matches the login device information in the stored correspondence; and an updating module configured to update the seed corresponding to the login state in response to determining the match.
In some embodiments, the apparatus further comprises: the determining unit is configured to determine whether a target seed corresponding to the code scanning payment request is consistent with the updated seed or not in response to receiving the code scanning payment request, wherein the code scanning payment request comprises payment code information, and a payment code indicated by the payment code information is generated based on the target seed; and the payment unit is configured to pay according to the code scanning payment request in response to determining that the seed corresponding to the payment code is consistent with the updated seed.
In a fourth aspect, embodiments of the present disclosure provide an apparatus for electronic payment, applied to a terminal, the apparatus comprising: a second acquisition unit configured to acquire a seed for generating a payment code in response to detection of a payment code generation operation; a second generation unit configured to generate prompt information characterizing prohibition of payment in response to determining that the acquired seed is invalid; and a display unit configured to display the prompt information.
In some embodiments, the second obtaining unit includes: a fourth determining module configured to determine a state of a network connection with a server for issuing the seed; an acquisition module configured to acquire, from the local, a last acquired seed as a seed for generating a payment code in response to determining that the state of the network connection belongs to an offline state; the transmission module is configured to send a seed acquisition request to a server for issuing seeds in response to determining that the state of network connection belongs to an online state; and receiving the seeds sent by the server.
In some embodiments, the apparatus further comprises: and a third generation unit configured to generate a payment code in response to determining that the acquired seed has not failed.
In a fifth aspect, embodiments of the present disclosure provide a system for electronic payment, the system comprising: the server side is configured to acquire a login state corresponding to the target user side; in response to receiving a seed acquisition request sent by a target user side, updating a seed corresponding to a login state, wherein the seed is used for generating a payment code; the updated seeds are sent to a target user terminal; the target user side is configured to send a seed acquisition request to the server side; receiving seeds sent by a server; a payment code is generated based on the received seed.
In some embodiments, the system further comprises: a payee configured to obtain a payment code; sending a code scanning payment request to a server; receiving payment result information sent by a server; and, the server is further configured to: in response to receiving the code scanning payment request, determining whether a target seed corresponding to the code scanning payment request is consistent with the updated seed, wherein the code scanning payment request comprises payment code information, and a payment code indicated by the payment code information is generated based on the target seed; responding to the fact that the seeds corresponding to the payment codes are consistent with the updated seeds, and paying according to the code scanning payment request; and sending payment result information to a receiving end.
In a sixth aspect, embodiments of the present disclosure provide an electronic device, comprising: one or more processors; a storage device having one or more programs stored thereon; the one or more programs, when executed by the one or more processors, cause the one or more processors to implement the method as described in any of the implementations of the first and second aspects.
In a seventh aspect, embodiments of the present disclosure provide a computer readable medium having stored thereon a computer program which, when executed by a processor, implements a method as described in any one of the implementations of the first and second aspects.
According to the method, the device, the system, the electronic equipment and the medium for electronic payment, which are provided by the embodiment of the invention, by receiving the seed acquisition request sent by the target user side as the trigger condition for updating the seed corresponding to the login state, only the unique seed is ensured to be effective at the same moment, so that after the account is logged in offline, the code scanning payment operation is carried out on the equipment which can only be logged in later after the account is logged in by another equipment. And whether the obtained seeds fail or not is judged, and payment is forbidden when the seeds fail, so that the risk of malicious account withdrawal is reduced.
Drawings
Other features, objects and advantages of the present disclosure will become more apparent upon reading of the detailed description of non-limiting embodiments, made with reference to the following drawings:
FIG. 1 is an exemplary system architecture diagram in which an embodiment of the present disclosure may be applied;
FIG. 2 is a flow chart of one embodiment of a method for electronic payment applied to a server according to the present disclosure;
FIG. 3 is a flow chart of one embodiment of a method for electronic payment applied to a terminal in accordance with the present disclosure;
FIG. 4 is a schematic structural diagram of one embodiment of an apparatus for electronic payment applied to a server according to the present disclosure;
FIG. 5 is a schematic structural view of one embodiment of an apparatus for electronic payment applied to a terminal according to the present disclosure;
FIG. 6 is a timing diagram of interactions between various devices in one embodiment of a system for electronic payment according to the present disclosure;
fig. 7 is a schematic structural diagram of an electronic device suitable for use in implementing embodiments of the present disclosure.
Detailed Description
The present disclosure is described in further detail below with reference to the drawings and examples. It is to be understood that the specific embodiments described herein are merely illustrative of the invention and are not limiting of the invention. It should be noted that, for convenience of description, only the portions related to the present invention are shown in the drawings.
It should be noted that, without conflict, the embodiments of the present disclosure and features of the embodiments may be combined with each other. The present disclosure will be described in detail below with reference to the accompanying drawings in conjunction with embodiments.
Fig. 1 illustrates an exemplary architecture 100 of a device for electronic payment or a method for electronic payment to which the present disclosure may be applied.
As shown in fig. 1, a system architecture 100 may include terminal devices 101, 102, 103, a network 104, and a server 105. The network 104 is used as a medium to provide communication links between the terminal devices 101, 102, 103 and the server 105. The network 104 may include various connection types, such as wired, wireless communication links, or fiber optic cables, among others.
The terminal devices 101, 102, 103 interact with the server 105 via the network 104 to receive or send messages or the like. Various communication client applications, such as a web browser application, a shopping class application, a search class application, an instant messaging tool, a mailbox client, a mobile payment class application, etc., may be installed on the terminal devices 101, 102, 103.
The terminal devices 101, 102, 103 may be hardware or software. When the terminal devices 101, 102, 103 are hardware, they may be various electronic devices having a display screen and supporting mobile payment, including but not limited to smartphones, tablets, smartphones, and the like. When the terminal devices 101, 102, 103 are software, they can be installed in the above-listed electronic devices. Which may be implemented as multiple software or software modules (e.g., software or software modules for providing distributed services) or as a single software or software module. The present invention is not particularly limited herein.
The server 105 may be a server providing various services, such as a background server providing support for mobile payment type applications on the terminal devices 101, 102, 103. The background server may analyze the received seed acquisition request, generate a corresponding processing result (for example, updated seed) according to the request, and may also feed back the generated processing result to the terminal device.
The server may be hardware or software. When the server is hardware, the server may be implemented as a distributed server cluster formed by a plurality of servers, or may be implemented as a single server. When the server is software, it may be implemented as a plurality of software or software modules (e.g., software or software modules for providing distributed services), or as a single software or software module. The present invention is not particularly limited herein.
It should be noted that, the method for electronic payment provided by the embodiment of the present disclosure may be performed by the server 105, or may be performed by the terminal devices 101, 102, 103, and accordingly, the apparatus for electronic payment may be disposed in the server 105, or may be disposed in the terminal devices 101, 102, 103.
It should be understood that the number of terminal devices, networks and servers in fig. 1 is merely illustrative. There may be any number of terminal devices, networks, and servers, as desired for implementation.
With continued reference to fig. 2, a flow 200 of one embodiment of a method for electronic payment according to the present disclosure is shown. The method for electronic payment comprises the following steps:
step 201, obtaining a login state corresponding to a target user terminal.
In this embodiment, the execution body of the method for electronic payment (such as the server 105 shown in fig. 1) may obtain the login status corresponding to the target user terminal through a wired connection manner or a wireless connection manner. The login state may be used to identify the user and the login state thereof. The target client may be a client used by a user to send a login request.
As an example, the execution body may first receive a login request sent by the target user side. The login request may include login verification information of the user. The login authentication information of the user may include, for example, a user name and a password. Then, the execution body may verify the login verification information of the user. In response to determining that the authentication passes, the executing body may generate a login state corresponding to login authentication information of the user. The login state may be used to characterize that the user indicated by the login verification information is in a login state.
In some optional implementations of this embodiment, the executing body may acquire the login state corresponding to the target user side through the following steps:
first, in response to receiving a login request sent by a target user terminal, determining whether login equipment information is included in the login request.
In these implementations, in response to receiving a login request sent by the target client, the executing entity may determine whether login device information is included in the login request. The login device information may be generally used to uniquely identify a device corresponding to the target ue.
And a second step of verifying user login verification information included in the login request in response to determining that the login device information is included in the login request.
In these implementations, in response to determining that the received login request includes login device information, the executing entity may verify user login verification information included in the login request in various ways. The login authentication information of the user may include a user name and a password, for example.
Third, generating a login state corresponding to the target user terminal in response to determining that the user login verification information passes verification
In these implementations, in response to determining that the user login authentication information is verified, the executing entity may generate a login state corresponding to the target user side. The login state may be used to characterize that the user indicated by the login verification information is in a login state.
Based on the above optional implementation manner, since the request sent when the login state is stolen often does not include login device information, the risk of account loss caused by the theft of the login state can be reduced by adopting the above manner.
In some optional implementations of this embodiment, based on the login device information included in the login request, the execution body may further generate and store a correspondence between the login state and the login device information.
Based on the optional implementation manner, the execution body may bind login device information with a login state.
Step 202, in response to receiving the seed acquisition request sent by the target user terminal, updating the seed corresponding to the login state.
In this embodiment, in response to receiving the seed obtaining request sent by the target ue, the executing body may update the seed corresponding to the login state obtained in step 201. Wherein the seed may be used to generate a payment code. The execution body may store a plurality of login states and seeds corresponding to the login states. Moreover, the seeds may be updated, such as by invalidating the original seeds, to create new seeds.
In some optional implementations of this embodiment, in response to receiving the seed acquisition request sent by the target ue, the executing body may update the seed corresponding to the login state according to the following steps:
first, in response to receiving a seed acquisition request sent by a target user terminal, determining whether the seed acquisition request includes login device information.
In these implementations, in response to receiving a seed acquisition request sent by the target client, the execution body may determine whether the received seed acquisition request includes login device information.
And a second step of determining, in response to determining that the login device information is included in the seed acquisition request, whether the login device information included in the seed acquisition request matches the login device information in the stored correspondence.
In these implementations, in response to determining that the login device information is included in the received seed acquisition request, the execution body may determine whether the login device information is included in the received seed acquisition request.
And thirdly, updating the seed corresponding to the login state in response to the determination of the match.
In these implementations, in response to determining a match, the executing entity may update the seed corresponding to the login state obtained in step 201 in a manner consistent with the foregoing description.
And 203, sending the updated seeds to a target user terminal.
In this embodiment, the execution body may send the updated seed in step 202 to the target ue.
In some optional implementations of this embodiment, the executing body may continue to execute the following steps:
first, in response to receiving a code scanning payment request, determining whether a target seed corresponding to the code scanning payment request is consistent with the updated seed.
In these implementations, in response to receiving the barcode payment request, the execution body may determine whether a target seed corresponding to the barcode payment request is consistent with the updated seed. The code scanning payment request may include payment code information. The payment code indicated by the payment code information is typically generated based on the target seed. The above manner of generating the payment code information based on the seed may adopt various dynamic payment code generation manners, which are not described herein.
And secondly, responding to the fact that the seeds corresponding to the payment codes are consistent with the updated seeds, and paying according to the code scanning payment request.
In these implementations, the executing entity may pay according to the code scanning payment request in response to determining that the seed corresponding to the payment code is consistent with the updated seed. As an example, the executing entity may deduct the payment amount indicated by the barcode payment request from an account corresponding to the payment code information. The executing body may then increase the payment amount in the collection account indicated by the swipe code payment request.
Currently, one of the existing technologies generally updates the seed based on a preset time interval, so that the same user can pay after logging in a plurality of devices, and there is a risk that the account is maliciously drawn. By receiving the seed acquisition request sent by the target user side as the trigger condition for updating the seed corresponding to the login state, the method provided by the embodiment of the invention realizes that only the unique seed is ensured to be effective at the same time, so that after the account is logged in offline, the code scanning payment operation can only be carried out on the equipment logged in later after the account is logged in by another equipment, and the risk of malicious account extraction is reduced.
With continued reference to fig. 3, fig. 3 illustrates a flow 300 of one embodiment of a method for electronic payment according to the present disclosure. The method for electronic payment comprises the following steps:
in response to detecting the payment code generation operation, a seed for generating the payment code is obtained, step 301.
In the present embodiment, in response to detecting the payment code generation operation, the execution subject of the method for electronic payment (such as the terminals 101, 102, 103 shown in fig. 1) may acquire the seed for generating the payment code through a wired connection manner or a wireless connection manner. As an example, the payment code generation operation described above may include the user clicking on a "payment code" button. As yet another example, the payment code generation operation described above may also include an "open payment code" voice.
In some optional implementations of this embodiment, in response to detecting the payment code generation operation, the executing entity may obtain the seed for generating the payment code by:
first, the state of the network connection with the server for seed delivery is determined.
In these implementations, the executing entity may determine the status of the network connection with the server for issuing the seed in various ways. Thus, the execution subject can determine whether it is in an offline state or an online state.
In response to determining that the state of the network connection belongs to the offline state, the last acquired seed is acquired locally as a seed for generating the payment code.
In these implementations, in response to determining that the state of the network connection determined in the first step belongs to an offline state, the executing body may locally obtain a last obtained seed as a seed for generating the payment code.
It should be noted that, the executing body generally saves the obtained seed as a backup locally. Alternatively, the executing body may delete the seed stored before after the new seed is acquired, so as to save only the seed acquired last time.
Thirdly, in response to determining that the state of network connection belongs to an online state, sending a seed acquisition request to a server for issuing seeds; and receiving the seeds sent by the server.
In these implementations, in response to determining that the state of the network connection determined in the first step belongs to an online state, the execution body may first send a seed acquisition request to a server for issuing a seed. Then, the execution body may receive the seed sent by the server.
In some optional implementations of this embodiment, based on the login device information included in the login request, the execution body may further generate and store a correspondence between the login state and the login device information.
In response to determining that the acquired seed is invalid, a hint information is generated that characterizes the prohibited payment, step 302.
In this embodiment, in response to determining that the seed obtained in step 301 is invalid, the executing entity may generate prompt information indicating prohibition of payment. As an example, the execution body may directly send the verification information including the seed obtained in step 301 to the server to verify whether the seed is invalid. As yet another example, the executing entity may further send the payment code generated based on the seed acquired in step 301 to a server of the payment system to verify whether the payment code is invalid. Since the payment code is generated according to a preset algorithm based on the seed, the validity of the payment code can be regarded as consistent with the validity of the seed. The prompt information indicating prohibition of payment may include various forms such as "payment failure", "payment code invalid", and the like.
Step 303, displaying a prompt message.
In this embodiment, the execution body may display the prompt information generated in step 302 in various manners.
In some alternative implementations of the present embodiment, the executing entity may also generate a payment code in response to determining that the acquired seed has not failed.
In these implementations, the executing entity may also generate a payment code in response to determining that the acquired seed has not failed. Specifically, the execution body may be generated according to a preset algorithm based on a seed. The preset algorithm may be consistent with a manner of verifying the payment code by a server for verifying the payment code in the payment system.
Currently, one of the existing technologies is that a payment terminal generates a payment code based on a locally stored seed issued by a server by using a preset algorithm, so that the payment code is stolen when the seed stored in the payment terminal is leaked. By judging whether the obtained seeds fail or not, the payment is forbidden when the seeds fail, so that the risk of theft of the payment code is reduced.
With further reference to fig. 4, as an implementation of the method shown in the above figures, the present disclosure provides an embodiment of an apparatus for electronic payment, which corresponds to the method embodiment shown in fig. 2, and which is particularly applicable in various electronic devices.
As shown in fig. 4, the apparatus 400 for electronic payment provided in the present embodiment includes a first obtaining unit 401, an updating unit 402, and a transmitting unit 403. The first obtaining unit 401 is configured to obtain a login state corresponding to the target user terminal; an updating unit 402, configured to update a seed corresponding to the login state in response to receiving a seed acquisition request sent by the target user side, where the seed is used to generate a payment code; and a sending unit 403 configured to send the updated seed to the target user terminal.
In the present embodiment, in the apparatus 400 for electronic payment: the specific processes of the first obtaining unit 401, the updating unit 402, and the sending unit 403 and the technical effects thereof may refer to the descriptions related to step 201, step 202, and step 203 in the corresponding embodiment of fig. 2, and are not repeated herein.
In some optional implementations of this embodiment, the first obtaining unit may include a first determining module (not shown in the figure), a checking module (not shown in the figure), and a generating module (not shown in the figure). The first determining module may be configured to determine, in response to receiving a login request sent by the target user side, whether the login request includes login device information. The verification module may be configured to verify user login verification information included in the login request in response to determining that login device information is included in the login request. The generation module may be configured to generate a login state corresponding to the target user side in response to determining that the user login verification information is verified.
In some optional implementations of this embodiment, the apparatus 400 for electronic payment may further include: and a first generation unit configured to generate and store a correspondence between the login state and login device information. The updating unit may include a second determining module (not shown in the figure), a third determining module (not shown in the figure), and an updating module (not shown in the figure). The second determining module may be configured to determine, in response to receiving a seed acquisition request sent by the target user side, whether the seed acquisition request includes login device information. The third determination module may be configured to determine, in response to determining that the login device information is included in the seed acquisition request, whether the login device information included in the seed acquisition request matches the login device information in the stored correspondence. The update module may be configured to update the seed corresponding to the login state in response to determining the match.
In some optional implementations of this embodiment, the apparatus 400 for electronic payment may further include: a determination unit (not shown in the figure) and a payment unit (not shown in the figure). Wherein the determining unit may be further configured to determine, in response to receiving the code scanning payment request, whether the target seed corresponding to the code scanning payment request is consistent with the updated seed. The code scanning payment request may include payment code information. The payment code indicated by the payment code information may be generated based on the target seed. The payment unit may be configured to pay according to the code scanning payment request in response to determining that the seed corresponding to the payment code is consistent with the updated seed.
According to the device provided by the embodiment of the disclosure, the updating unit 402 uses the seed acquisition request sent by the received target user side as the trigger condition for updating the seed corresponding to the login state, so that only the unique seed is ensured to be effective at the same time, and therefore, after the account is logged in offline, the code scanning payment operation can only be carried out on the equipment logged in later after the account is logged in by another equipment, and the risk of malicious account taking is reduced.
With further reference to fig. 5, as an implementation of the method shown in the above figures, the present disclosure provides an embodiment of an apparatus for electronic payment, which corresponds to the method embodiment shown in fig. 3, and which is particularly applicable in various electronic devices.
As shown in fig. 5, the apparatus 500 for electronic payment provided in the present embodiment includes a second obtaining unit 501, a second generating unit 502, and a display unit 503. Wherein the second obtaining unit 501 is configured to obtain a seed for generating a payment code in response to detecting a payment code generation operation; a second generating unit 502 configured to generate prompt information characterizing prohibition of payment in response to determining that the acquired seed is invalid; and a display unit 503 configured to display the prompt information.
In some optional implementations of this embodiment, the second obtaining unit may include a fourth determining module (not shown in the figure), an obtaining module (not shown in the figure), and a transmitting module (not shown in the figure). Wherein the fourth determining module may be configured to determine a state of a network connection with a server for issuing the seed. The acquisition module may be configured to acquire, from the local, a last acquired seed as a seed for generating the payment code in response to determining that the state of the network connection belongs to the offline state. The transmission module may be configured to send a seed acquisition request to a server for issuing a seed in response to determining that the state of the network connection belongs to an online state; and receiving the seeds sent by the server.
In some optional implementations of this embodiment, the apparatus 500 for electronic payment may further include: a third generation unit (not shown in the figure) configured to generate a payment code in response to determining that the acquired seed has not failed.
The device provided in the above embodiment of the present disclosure determines, through the second generating unit 502, whether the obtained seed is invalid, and prohibits payment when the seed is invalid, thereby reducing the risk of theft of the payment code.
With further reference to fig. 6, a timing 600 of interactions between various devices in one embodiment of a method for electronic payment is shown. The system for electronic payment may include: a server (e.g., server 105 shown in fig. 1) and a target client (e.g., terminal devices 101, 102, 103 shown in fig. 1). The server may be configured to obtain a login state corresponding to the target user side; in response to receiving a seed acquisition request sent by a target user side, updating a seed corresponding to a login state, wherein the seed is used for generating a payment code; and sending the updated seeds to the target user side. The target client may be configured to send a seed acquisition request to a server; receiving seeds sent by a server; a payment code is generated based on the received seed.
In some optional implementations of the present embodiment, the system may further include: a payee configured to obtain a payment code; sending a code scanning payment request to a server; and receiving payment result information sent by the server. The server may be further configured to: in response to receiving the code scanning payment request, determining whether a target seed corresponding to the code scanning payment request is consistent with the updated seed; responding to the fact that the seeds corresponding to the payment codes are consistent with the updated seeds, and paying according to the code scanning payment request; and sending payment result information to a receiving end. The code scanning payment request may include payment code information. The payment code indicated by the payment code information may be generated based on the target seed.
As shown in fig. 6, in step 601, the server obtains a login state corresponding to the target client.
In step 602, the target ue sends a seed acquisition request to the server.
In this embodiment, the target ue and the seed obtaining request may be identical to those described in steps 201 and 202 in the foregoing embodiments.
In step 603, in response to receiving the seed acquisition request sent by the target client, the server updates the seed corresponding to the login state.
In step 604, the server sends the updated seed to the target client.
Step 605, the target ue receives the seed sent by the server.
In step 606, the target subscriber terminal generates a payment code based on the received seed.
In this embodiment, the target ue may generate the payment code through a preset algorithm based on the received seed.
The steps 601, 603 and 604 are identical to the steps 201, 202 and 203 and their optional implementation manners in the foregoing embodiments, and the descriptions of the steps 201, 202 and 203 and their optional implementation manners also apply to the steps 601, 603 and 604, which are not repeated herein.
In some alternative implementations of the present embodiment, the timing of the interaction may further include the steps of:
In step 607, the payee obtains the payment code.
In this embodiment, the payee may obtain the payment code generated in step 606 through a code scanning device (e.g., a code scanning gun).
In step 608, the payee sends a scan payment request to the server.
In this embodiment, the payee may send a swipe payment request to the server. Wherein the above-described swipe code payment request may be consistent with the description of the alternative implementation of step 203 in the previous embodiments.
In step 609, in response to receiving the code scanning payment request, the server determines whether the target seed corresponding to the code scanning payment request is consistent with the updated seed.
In this embodiment, the payment code information may be included in the swipe code payment request. The payment code indicated by the payment code information may be generated based on the target seed. The above step 609 may correspond to the corresponding description of an alternative implementation of step 203 in the previous embodiment.
In step 610, in response to determining that the seed corresponding to the payment code is consistent with the updated seed, the server performs payment according to the payment request of the scan code.
The above step 610 may be consistent with the corresponding description of an alternative implementation of step 203 in the previous embodiment.
In step 611, the server sends payment result information to the payee.
In this embodiment, the payment result information may be used to indicate the result of the code-scanning payment. As an example, the above-described payment result information may be "payment success".
In step 612, the receiving end receives the payment result information sent by the server.
According to the system for electronic payment provided by the embodiment of the application, the server side receives the seed acquisition request sent by the target user side as the trigger condition for updating the seed corresponding to the login state, so that only the unique seed is ensured to be effective at the same time, and after the account is logged in offline, the code scanning payment operation is carried out on the equipment which can only be logged in later after the account is logged in by the other equipment. And whether the obtained seeds fail or not is judged through the user side, and payment is forbidden when the seeds fail, so that the risk of malicious account withdrawal is reduced.
Referring now to fig. 7, a schematic diagram of a configuration of an electronic device (e.g., terminal device 101, 102, 103 or server 105 in fig. 1) 700 suitable for use in implementing embodiments of the present application is shown. The server illustrated in fig. 7 is merely an example, and should not impose any limitation on the functionality and scope of use of embodiments of the present application.
As shown in fig. 7, the electronic device 700 may include a processing means (e.g., a central processor, a graphics processor, etc.) 701, which may perform various appropriate actions and processes according to a program stored in a Read Only Memory (ROM) 702 or a program loaded from a storage means 708 into a Random Access Memory (RAM) 703. In the RAM 703, various programs and data required for the operation of the electronic device 700 are also stored. The processing device 701, the ROM 702, and the RAM 703 are connected to each other through a bus 704. An input/output (I/O) interface 705 is also connected to bus 704.
In general, the following devices may be connected to the I/O interface 705: input devices 706 including, for example, a touch screen, touchpad, keyboard, mouse, etc.; an output device 707 including, for example, a liquid crystal display (LCD, liquid Crystal Display), a speaker, a vibrator, and the like; storage 708 including, for example, magnetic tape, hard disk, etc.; and a communication device 709. The communication means 709 may allow the electronic device 700 to communicate wirelessly or by wire with other devices to exchange data. While fig. 7 shows an electronic device 700 having various means, it is to be understood that not all of the illustrated means are required to be implemented or provided. More or fewer devices may be implemented or provided instead. Each block shown in fig. 7 may represent one device or a plurality of devices as needed.
In particular, according to embodiments of the present application, the processes described above with reference to flowcharts may be implemented as computer software programs. For example, embodiments of the present application include a computer program product comprising a computer program embodied on a computer readable medium, the computer program comprising program code for performing the method shown in the flowcharts. In such an embodiment, the computer program may be downloaded and installed from a network via communication device 709, or installed from storage 708, or installed from ROM 702. When being executed by the processing means 701, performs the above-described functions defined in the methods of the embodiments of the present application.
It should be noted that, the computer readable medium according to the embodiments of the present disclosure may be a computer readable signal medium or a computer readable storage medium, or any combination of the two. The computer readable storage medium can be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or a combination of any of the foregoing. More specific examples of the computer-readable storage medium may include, but are not limited to: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In an embodiment of the present disclosure, a computer readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device. Whereas in embodiments of the present disclosure, the computer-readable signal medium may comprise a data signal propagated in baseband or as part of a carrier wave, with computer-readable program code embodied therein. Such a propagated data signal may take any of a variety of forms, including, but not limited to, electro-magnetic, optical, or any suitable combination of the foregoing. A computer readable signal medium may also be any computer readable medium that is not a computer readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device. Program code embodied on a computer readable medium may be transmitted using any appropriate medium, including but not limited to: electrical wires, fiber optic cables, RF (Radio Frequency), and the like, or any suitable combination thereof.
The computer readable medium may be contained in the electronic device; or may exist alone without being incorporated into the electronic device. The computer readable medium carries one or more programs which, when executed by the electronic device, cause the electronic device to: acquiring a login state corresponding to a target user terminal; in response to receiving a seed acquisition request sent by the target user side, updating a seed corresponding to the login state; the updated seeds are sent to the target user side; or alternatively
In response to detecting the payment code generation operation, obtaining a seed for generating the payment code; generating prompt information representing prohibition of payment in response to determining that the acquired seed is invalid; and displaying prompt information.
Computer program code for carrying out operations of embodiments of the present disclosure may be written in one or more programming languages, including an object oriented programming language such as Java, smalltalk, C ++ and conventional procedural programming languages, such as the "C" programming language or similar programming languages. The program code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the case of a remote computer, the remote computer may be connected to the user's computer through any kind of network, including a Local Area Network (LAN) or a Wide Area Network (WAN), or may be connected to an external computer (for example, through the Internet using an Internet service provider).
The flowcharts and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various embodiments of the present disclosure. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams and/or flowchart illustration, and combinations of blocks in the block diagrams and/or flowchart illustration, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.
The units involved in the embodiments described in the present disclosure may be implemented by means of software, or may be implemented by means of hardware. The described units may also be provided in a processor, for example, described as: a processor comprises a first acquisition unit, an updating unit and a sending unit; or a processor comprises a second acquisition unit, a second generation unit and a display unit. The names of these units do not limit the unit itself in some cases, and for example, the first obtaining unit may also be described as "a unit that obtains a login state corresponding to the target user side".
The foregoing description is only of the preferred embodiments of the present disclosure and description of the principles of the technology being employed. It will be appreciated by those skilled in the art that the scope of the invention in the embodiments of the present disclosure is not limited to the specific combination of the above technical features, but encompasses other technical features formed by any combination of the above technical features or their equivalents without departing from the spirit of the invention. Such as the above-described features, are mutually substituted with (but not limited to) the features having similar functions disclosed in the embodiments of the present disclosure.

Claims (12)

1. The method for electronic payment is applied to a server and comprises the following steps:
acquiring a login state corresponding to a target user side, and generating and storing a corresponding relation between the login state and login equipment information;
in response to receiving a seed acquisition request sent by the target user side, updating a seed corresponding to the login state, wherein the seed is used for generating a payment code;
the updated seeds are sent to the target user side;
the responding to the receiving of the seed acquisition request sent by the target user side, updating the seed corresponding to the login state, includes: responding to a seed acquisition request sent by the target user side, and determining whether the seed acquisition request comprises login equipment information; in response to determining that the seed acquisition request includes login device information, determining whether the login device information included in the seed acquisition request matches login device information in the stored correspondence; in response to determining a match, updating a seed corresponding to the login state; and
The method further comprises the steps of: in response to receiving a code scanning payment request, determining whether a target seed corresponding to the code scanning payment request is consistent with the updated seed, wherein the code scanning payment request comprises payment code information, and a payment code indicated by the payment code information is generated based on the target seed; and responding to the fact that the seeds corresponding to the payment codes are consistent with the updated seeds, and paying according to the code scanning payment request.
2. The method of claim 1, wherein the obtaining the login state corresponding to the target client comprises:
responding to a login request sent by the target user side, and determining whether login equipment information is included in the login request;
in response to determining that the login request includes login equipment information, verifying user login verification information included in the login request;
and generating a login state corresponding to the target user terminal in response to the fact that the user login verification information is confirmed to pass verification.
3. A method for electronic payment, applied to a terminal, comprising:
in response to detecting a payment code generation operation, acquiring a seed for generating the payment code from a server;
Generating prompt information representing prohibition of payment in response to determining that the acquired seed is invalid;
displaying the prompt information;
the method according to claim 1 or 2 is implemented by the server.
4. A method according to claim 3, wherein the obtaining a seed for generating the payment code comprises:
determining the state of network connection between the server and the server for issuing seeds;
in response to determining that the state of the network connection belongs to an offline state, locally acquiring the last acquired seed as the seed for generating the payment code;
responding to the determination that the state of the network connection belongs to an online state, and sending a seed acquisition request to the server for issuing seeds; and receiving the seeds sent by the server.
5. The method according to claim 3 or 4, wherein the method further comprises:
in response to determining that the acquired seed has not failed, a payment code is generated.
6. An apparatus for electronic payment, applied to a server, comprises:
the first acquisition unit is configured to acquire a login state corresponding to the target user side and generate and store a corresponding relation between the login state and login equipment information;
An updating unit configured to update a seed corresponding to the login state in response to receiving a seed acquisition request sent by the target user side, wherein the seed is used for generating a payment code;
a sending unit configured to send the updated seed to the target user terminal;
wherein the updating unit is further configured to: responding to a seed acquisition request sent by the target user side, and determining whether the seed acquisition request comprises login equipment information; in response to determining that the seed acquisition request includes login device information, determining whether the login device information included in the seed acquisition request matches login device information in the stored correspondence; in response to determining a match, updating a seed corresponding to the login state; and
the apparatus further comprises: a determining unit configured to determine whether a target seed corresponding to a code scanning payment request is consistent with the updated seed in response to receiving the code scanning payment request, wherein the code scanning payment request includes payment code information, and a payment code indicated by the payment code information is generated based on the target seed; and the payment unit is configured to pay according to the code scanning payment request in response to determining that the seed corresponding to the payment code is consistent with the updated seed.
7. The apparatus of claim 6, wherein the first acquisition unit comprises:
the first determining module is configured to determine whether login equipment information is included in a login request sent by the target user side or not in response to receiving the login request;
a verification module configured to verify user login verification information included in the login request in response to determining that login device information is included in the login request;
and the generation module is configured to generate a login state corresponding to the target user side in response to determining that the user login verification information passes verification.
8. An apparatus for electronic payment, applied to a terminal, comprising:
a second acquisition unit configured to acquire a seed for generating a payment code from a server in response to detection of a payment code generation operation;
a second generation unit configured to generate prompt information characterizing prohibition of payment in response to determining that the acquired seed is invalid;
a display unit configured to display the prompt information;
the method according to claim 1 or 2 is implemented by the server.
9. The apparatus of claim 8, wherein the second acquisition unit comprises:
A fourth determining module configured to determine a state of a network connection with a server for issuing the seed;
an acquisition module configured to acquire, from locally, a last acquired seed as the seed for generating the payment code in response to determining that the state of the network connection belongs to an offline state;
the transmission module is configured to send a seed acquisition request to the server for issuing seeds in response to determining that the state of the network connection belongs to an online state; and receiving the seeds sent by the server.
10. A system for electronic payment, comprising:
the server side is configured to acquire a login state corresponding to the target user side, and generate and store a corresponding relation between the login state and login equipment information; responding to a seed acquisition request sent by the target user side, and determining whether the seed acquisition request comprises login equipment information; in response to determining that the seed acquisition request includes login device information, determining whether the login device information included in the seed acquisition request matches login device information in the stored correspondence; in response to determining a match, updating a seed corresponding to the login state, wherein the seed is used to generate a payment code; the updated seeds are sent to the target user side;
The target user terminal is configured to send a seed acquisition request to the server terminal; receiving seeds sent by the server; generating a payment code based on the received seed
The server is further configured to: in response to receiving a code scanning payment request, determining whether a target seed corresponding to the code scanning payment request is consistent with the updated seed, wherein the code scanning payment request comprises payment code information, and a payment code indicated by the payment code information is generated based on the target seed; and responding to the fact that the seeds corresponding to the payment codes are consistent with the updated seeds, and paying according to the code scanning payment request.
11. An electronic device, comprising:
one or more processors;
a storage device having one or more programs stored thereon;
when executed by the one or more processors, causes the one or more processors to implement the method of any of claims 1-5.
12. A computer readable medium having stored thereon a computer program, wherein the program when executed by a processor implements the method of any of claims 1-5.
CN202011594722.6A 2020-12-29 2020-12-29 Method, apparatus, system, electronic device and medium for electronic payment Active CN113807854B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202011594722.6A CN113807854B (en) 2020-12-29 2020-12-29 Method, apparatus, system, electronic device and medium for electronic payment

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202011594722.6A CN113807854B (en) 2020-12-29 2020-12-29 Method, apparatus, system, electronic device and medium for electronic payment

Publications (2)

Publication Number Publication Date
CN113807854A CN113807854A (en) 2021-12-17
CN113807854B true CN113807854B (en) 2024-02-09

Family

ID=78943578

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202011594722.6A Active CN113807854B (en) 2020-12-29 2020-12-29 Method, apparatus, system, electronic device and medium for electronic payment

Country Status (1)

Country Link
CN (1) CN113807854B (en)

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107040369A (en) * 2016-10-26 2017-08-11 阿里巴巴集团控股有限公司 Data transmission method, apparatus and system
CN109146470A (en) * 2018-08-24 2019-01-04 北京小米移动软件有限公司 Generate the method and device of payment code
CN109583872A (en) * 2018-11-30 2019-04-05 阿里巴巴集团控股有限公司 Method of payment and device
CN110012048A (en) * 2018-11-22 2019-07-12 阿里巴巴集团控股有限公司 Message identification code generation method, device, electronic equipment and computer storage medium
CN112036882A (en) * 2020-08-31 2020-12-04 维沃移动通信有限公司 Account login method and device and electronic equipment

Family Cites Families (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108681896A (en) * 2018-03-29 2018-10-19 阿里巴巴集团控股有限公司 Displaying, recognition methods and the device of Quick Response Code

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107040369A (en) * 2016-10-26 2017-08-11 阿里巴巴集团控股有限公司 Data transmission method, apparatus and system
CN109146470A (en) * 2018-08-24 2019-01-04 北京小米移动软件有限公司 Generate the method and device of payment code
CN110012048A (en) * 2018-11-22 2019-07-12 阿里巴巴集团控股有限公司 Message identification code generation method, device, electronic equipment and computer storage medium
CN109583872A (en) * 2018-11-30 2019-04-05 阿里巴巴集团控股有限公司 Method of payment and device
CN112036882A (en) * 2020-08-31 2020-12-04 维沃移动通信有限公司 Account login method and device and electronic equipment

Also Published As

Publication number Publication date
CN113807854A (en) 2021-12-17

Similar Documents

Publication Publication Date Title
CN112688983A (en) Proxy right management device, terminal device and storage medium
CN107403112B (en) Data checking method and equipment thereof
CN108449186B (en) Security verification method and device
CN114840379A (en) Log generation method, device, server and storage medium
CN109150898B (en) Method and apparatus for processing information
CN109218338B (en) Information processing system, method and device
CN107315672B (en) Method and device for monitoring server
CN110855655B (en) Information verification method, device, equipment and storage medium
CN113807854B (en) Method, apparatus, system, electronic device and medium for electronic payment
CN108933802B (en) Method and apparatus for monitoring operation
CN113079085B (en) Business service interaction method, business service interaction device, business service interaction equipment and storage medium
CN109685508B (en) Transaction data processing method and device, electronic equipment and readable storage medium
CN109741069B (en) Transaction data processing method and device, electronic equipment and readable storage medium
CN111786936A (en) Method and device for authentication
CN111598544B (en) Method and device for processing information
CN111092949B (en) Method and device for registering equipment
CN110688677B (en) Method and device for executing intelligent contracts
CN108471635B (en) Method and apparatus for connecting wireless access points
CN113283891A (en) Information processing method and device and electronic equipment
CN112733113A (en) Device authentication method, device, system, electronic device and medium
CN108804713B (en) Image output method, electronic device, and computer-readable medium
CN108811036B (en) Method and apparatus for displaying wireless access point information
CN112084114A (en) Method and apparatus for testing an interface
CN112101907A (en) Method and system for handling accumulation fund service on line
CN110597525A (en) Method and apparatus for installing applications

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination
GR01 Patent grant
GR01 Patent grant