CN108564363A - A kind of transaction processing method, server, client and system - Google Patents
A kind of transaction processing method, server, client and system Download PDFInfo
- Publication number
- CN108564363A CN108564363A CN201810165018.5A CN201810165018A CN108564363A CN 108564363 A CN108564363 A CN 108564363A CN 201810165018 A CN201810165018 A CN 201810165018A CN 108564363 A CN108564363 A CN 108564363A
- Authority
- CN
- China
- Prior art keywords
- information
- transaction
- encrypted
- encrypted information
- client
- 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.)
- Granted
Links
Classifications
-
- G—PHYSICS
- G06—COMPUTING OR CALCULATING; 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
- G06Q20/3823—Payment protocols; Details thereof insuring higher security of transaction combining multiple encryption tools for a 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/12—Applying verification of the received information
-
- G—PHYSICS
- G06—COMPUTING OR CALCULATING; 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
- G06Q20/3821—Electronic credentials
- G06Q20/38215—Use of certificates or encrypted proofs of transaction rights
-
- 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/04—Network architectures or network communication protocols for network security for providing a confidential data exchange among entities communicating through data packet networks
- H04L63/0428—Network architectures or network communication protocols for network security for providing a confidential data exchange among entities communicating through data packet networks wherein the data content is protected, e.g. by encrypting or encapsulating the payload
Landscapes
- Engineering & Computer Science (AREA)
- Computer Security & Cryptography (AREA)
- Business, Economics & Management (AREA)
- Computer Hardware Design (AREA)
- Accounting & Taxation (AREA)
- Signal Processing (AREA)
- Computer Networks & Wireless Communication (AREA)
- General Engineering & Computer Science (AREA)
- Computing Systems (AREA)
- Finance (AREA)
- Theoretical Computer Science (AREA)
- General Physics & Mathematics (AREA)
- General Business, Economics & Management (AREA)
- Physics & Mathematics (AREA)
- Strategic Management (AREA)
- Financial Or Insurance-Related Operations Such As Payment And Settlement (AREA)
- Storage Device Security (AREA)
Abstract
本说明书实施例提供一种交易处理方法、服务器、客户端及系统，所述方法包括：用户客户端生成交易信息，对所述交易信息进行加密处理得到第二加密信息，向商家客户端发送所述交易信息、第二加密信息以及预先获取的第一信息、第一加密信息；商家客户端分别对所述第一加密信息和所述第二加密信息进行验证，若验证结果均为可信，保存所述交易信息；商家客户端对包括交易信息和第二加密信息的第三信息进行加密处理得到第三加密信息，与服务器建立通信连接后发送所述第三信息和第三加密信息至服务器；服务器分别对第三加密信息和第三信息中的第二加密信息进行验证，若验证结果均为可信，获取所述交易信息，完成交易。
The embodiment of this specification provides a transaction processing method, server, client, and system. The method includes: the user client generates transaction information, encrypts the transaction information to obtain second encrypted information, and sends the transaction information to the merchant client. The transaction information, the second encrypted information, the pre-acquired first information, and the first encrypted information; the merchant client verifies the first encrypted information and the second encrypted information respectively, and if the verification results are all credible, Save the transaction information; the merchant client encrypts the third information including the transaction information and the second encrypted information to obtain the third encrypted information, and sends the third information and the third encrypted information to the server after establishing a communication connection with the server ; The server respectively verifies the third encrypted information and the second encrypted information in the third information, and if the verification results are all credible, acquires the transaction information and completes the transaction.
Description
Technical Field
The embodiment of the specification relates to the technical field of information processing, in particular to a transaction processing method, a server, a client and a system.
Background
With the development of internet online transaction technology, more and more users have become more accustomed to performing online transactions. Compared with the traditional cash transaction mode or card swiping transaction mode, the online transaction can save transaction time and improve transaction efficiency. However, internet online transactions typically require network support.
Currently, transactions may also be effected while one of the merchant or the user is offline. For example, when the user client is in an offline state, the online merchant client may scan and acquire offline token information of the user client, and then interact with the server according to the acquired offline token information of the user to complete internet transactions. When the merchant client is in an offline state, the user client can scan and acquire the offline token information of the merchant client, and then interacts with the server according to the acquired user offline token information to complete the internet transaction. However, when the server is down or the merchant client and the user client are in an offline state at the same time, neither the merchant client nor the user client can establish communication connection with the server, and at this time, the transaction cannot be completed. Therefore, it is desirable to provide a transaction method that can still complete internet transactions when a merchant client and a user client are offline or a server goes down.
Disclosure of Invention
An object of the embodiments of the present disclosure is to provide an information identification method, a server, a client, and a system, which can still complete a transaction when a merchant client and a user client cannot be communicatively connected to the server at the same time.
The embodiment of the specification is realized by the following steps:
a transaction processing method, comprising:
the method comprises the steps that a user client generates transaction information, encrypts the transaction information to obtain second encryption information, and sends the transaction information, the second encryption information, and pre-acquired first information and first encryption information to a merchant client;
the merchant client receives first information, first encryption information, transaction information and second encryption information sent by the user client, verifies the first encryption information and the second encryption information respectively, and stores the transaction information if the verification result is credible;
the merchant client encrypts third information comprising the transaction information and the second encryption information to obtain third encryption information, establishes communication connection with the server and sends the third information and the third encryption information to the server;
and the server receives the third information and the third encrypted information, verifies the third encrypted information and the second encrypted information in the third information respectively, and if the verification result is credible, acquires the transaction information and completes the transaction.
A transaction processing method, comprising:
a user client generates transaction information;
the user client encrypts the transaction information to obtain second encrypted information;
and the user client sends the transaction information, the second encryption information, and the pre-acquired first information and the pre-acquired first encryption information to the merchant client.
A transaction processing method, comprising:
the merchant client receives first information, first encryption information, transaction information and second encryption information sent by a user client;
the merchant client verifies the first encryption information and the second encryption information respectively, and if the verification results are credible, the transaction information is stored;
the merchant client encrypts third information comprising the transaction information and the second encryption information to obtain third encryption information;
and the merchant client establishes communication connection with the server and sends the third information and the third encryption information to the server.
A transaction processing method, comprising:
the server receives third information and third encrypted information; the third information includes: transaction information and second encryption information;
and the server respectively verifies the third encrypted information and the second encrypted information in the third information, and if the verification results are credible, the transaction information is acquired, and the transaction is completed.
A transaction processing system comprising: a user client, a merchant client and a server;
the user client is used for generating transaction information, encrypting the transaction information to obtain second encryption information, and sending the transaction information, the second encryption information, and pre-acquired first information and first encryption information to the merchant client;
the merchant client is used for receiving first information, first encryption information, transaction information and second encryption information sent by the user client, respectively verifying the first encryption information and the second encryption information, and if the verification result is credible, storing the transaction information; encrypting third information comprising the transaction information and the second encryption information to obtain third encryption information; the third information and the third encryption information are sent to the server;
the server is used for receiving the third information and the third encrypted information, verifying the third encrypted information and the second encrypted information in the third information respectively, and if the verification result is credible, acquiring the transaction information and completing the transaction.
A client, comprising: the system comprises a transaction information generation module, a user encryption module, a user storage module and a user sending module;
the transaction information generating module is used for generating transaction information; the transaction information includes: a first token, a transaction time, a transaction amount, and a universal unique identification code;
the user encryption module is used for encrypting the transaction information to obtain second encryption information;
the user storage module is used for storing first information and first encryption information which are acquired in advance; the first encrypted information is information obtained by encrypting the first information; the first information includes: the method comprises the steps that a first token, an offline payment identifier and a public key of a user client side are obtained;
and the user sending module is used for sending the transaction information, the second encryption information, the first information and the first encryption information to the merchant client.
A client, comprising: the system comprises a merchant receiving module, a merchant verification module, a merchant encryption module, a merchant storage module and a merchant sending module;
the merchant receiving module is used for receiving first information, first encryption information, transaction information and second encryption information sent by a user client; the first information includes: the method comprises the steps that a first token, an offline payment identifier and a public key of a user client side are obtained; the first encrypted information is information obtained by encrypting the first information; the transaction information includes: a first token, a transaction time, a transaction amount, and a universal unique identification code; the second encrypted information is obtained by encrypting the transaction information;
the merchant verification module is used for respectively verifying the first encryption information and the second encryption information;
the merchant encryption module is used for encrypting third information comprising the transaction information and the second encryption information to obtain third encryption information;
the merchant storage module is used for storing the transaction information, the third information and the third encryption information;
and the merchant sending module is used for sending the third information and the third encrypted information to the server after the client establishes communication connection with the server.
A server, comprising: the system comprises a server receiving module, a server verifying module and a transaction completing module;
the server receiving module is used for receiving third information and third encrypted information; the third information includes: transaction information and second encryption information; the transaction information includes: a first token, a transaction time, a transaction amount, and a universal unique identification code; the second encrypted information is obtained by encrypting the transaction information; the third information is obtained by encrypting the third information;
the server verification module is used for verifying the third encrypted information and second encrypted information in the third information respectively;
and the transaction completion module is used for acquiring the transaction information and completing the transaction when the verification result of the server verification module is credible.
As can be seen from the above, in one or more embodiments of the present specification, when a transaction occurs, if neither a user client nor a merchant client can establish a communication connection with a server, the user client generates transaction information, the transaction information is encrypted by using a private key of the user client and then sent to the merchant, the merchant verifies a message sent from the user client, if a verification result is trusted, the transaction information of the user client is considered as trusted information, the transaction information is stored, after the merchant client establishes a communication connection with the server, the transaction information is sent to the server, and the server verifies that the transaction information is trusted, and then the transaction is completed. By using the embodiments provided by the specification, the transaction between the user client and the merchant client can be ensured to be realized when the user client and the merchant client cannot establish communication connection with the server. The merchant client and the server verify the transaction information respectively, so that the reliability of the transaction information can be ensured, and the security of the transaction is ensured.
Drawings
In order to more clearly illustrate one or more embodiments or prior art solutions of the present disclosure, the drawings used in the description of the embodiments or prior art will be briefly described below, it is obvious that the drawings in the following description are only some embodiments described in the present disclosure, and other drawings can be obtained by those skilled in the art without inventive efforts.
FIG. 1 is a schematic flow chart diagram illustrating one embodiment of a transaction processing method provided herein;
FIG. 2 is a flow diagram of another embodiment of a transaction processing method provided herein;
FIG. 3 is a flow diagram of one embodiment of a method for user client-side transaction processing as provided herein;
FIG. 4 is a flow diagram of one embodiment of a merchant client-side transaction processing method provided herein;
FIG. 5 is a flow diagram of one embodiment of a server-side transaction processing method provided herein;
fig. 6 is a block diagram of a hardware structure of a computer terminal in an embodiment of the present specification;
FIG. 7 is a system diagram illustrating the architecture of one embodiment of a transaction processing system provided herein;
FIG. 8 is a block diagram illustrating the architecture of one embodiment of a user client for transaction processing provided herein;
FIG. 9 is a block diagram of one embodiment of a merchant client for transaction processing as provided herein;
fig. 10 is a block diagram of one embodiment of a server for transaction processing provided by the present specification.
Detailed Description
The embodiment of the specification provides a transaction processing method, a server, a client and a system.
In order to make those skilled in the art better understand the technical solutions in the present specification, the technical solutions in the embodiments of the present specification will be clearly and completely described below with reference to the drawings in the embodiments of the present specification, and it is obvious that the described embodiments are only a part of the embodiments of the present specification, and not all of the embodiments. All other embodiments obtained by a person of ordinary skill in the art based on the embodiments in the present specification without any creative effort shall fall within the protection scope of the present specification.
An embodiment of a transaction processing method of the present specification is described below. FIG. 1 is a schematic flow chart diagram of one embodiment of an information identification method provided herein, which provides method steps as described in the embodiments or flowcharts, but may include more or fewer steps based on routine or non-inventive labor. The order of steps recited in the embodiments is merely one manner of performing the steps in a multitude of orders and does not represent the only order of execution. In practice, the system or apparatus may be implemented in a sequential or parallel manner (e.g., in the context of parallel processors or multi-threaded processing) as the embodiments or methods shown in the figures are executed. As shown in fig. 1 in particular, the method may comprise the following steps.
S102: the user client sends a connection request to the server.
In one embodiment, the user client may be a hardware device, such as a cell phone, a tablet computer, or the like. In another embodiment, the user client may also be a client application for transactions, such as a pay-for-use application or the like.
The user client may issue a connection request to the server. The connection request may include: user identification, timestamp, hash value.
The user identification may be used to uniquely identify the user. The user identification may be a user name, a user number, etc.
The timestamp may be the time at which the connection request was issued.
The hash value may be determined from the user identification and the timestamp. For example, it may be a hash value calculated from the user identifier and the timestamp. The timestamps are different and the resulting hash values may be different.
S104: the server receives the connection request of the user client, generates first information corresponding to the user client, encrypts the first information to obtain first encrypted information, and sends the first information and the first encrypted information to the user client.
After receiving the connection request of the user client, the server may generate first information corresponding to the user client.
The first information may include: the first token, the offline payment identification and the public key of the user client.
The first token may be information representing the identity of the user client. The first token may include: a timestamp, a user client version, a user identification, and a random number. Generally, if a user initiates a connection request multiple times, the first tokens corresponding to the multiple connection requests may be different.
The offline payment identifier may be an identifier indicating that offline payment is allowed.
The server may encrypt the first information to obtain first encrypted information. Specifically, the server may encrypt the first information by using a server private key to obtain first encrypted information.
In one embodiment, the server may calculate a digest value of the first information, and encrypt the digest value of the first information using the server private key to obtain first encrypted information.
The server may send the first information and the first encryption information to the user client.
S106: and the user client receives and stores the first information and the first encryption information sent by the server.
The user client may receive the first information and the first encryption information sent by the server. The user client may store the first information and the first encryption information.
S108: the user client generates transaction information, encrypts the transaction information to obtain second encryption information, and sends the transaction information, the second encryption information, and the first information and the first encryption information which are obtained in advance to the merchant client.
When the user client performs a transaction, if the user client is in an offline state, the user client may generate transaction information.
The transaction information may include: the transaction system comprises a first token, transaction time, transaction amount and a Universal Unique Identifier (UUID). The transaction information may be used to uniquely identify a transaction.
The user client may encrypt the transaction information to obtain second encrypted information. Specifically, the user client may encrypt the transaction information by using a private key of the user client to obtain second encrypted information.
In one embodiment, the user client may calculate a digest value of the transaction information, and encrypt the digest value of the transaction information using a private key of the user client, so as to obtain second encrypted information.
The private key of the user client may be pre-stored. And the private key of the user client is sent to the user client by the server in advance.
In one application scenario, when a user client first connects to an internet login server, a login request may be sent to the server. The login request may be for logging in an account of the user for the transaction. For example, a login request may be issued to a server for a payment transaction. The connection request may be a request to log into a user transaction account. Specifically, the method may include: a user name and a user password. After receiving a connection request sent by a user client, the server can verify an account and a password of the user client. If the verification result is correct, the server can generate a public key and a private key of the user client, send the private key of the user client to the user client, and store the public key of the user client on the server.
In one embodiment, when the user client is reinstalled, the login request can be sent to the server again, and the server can send the private key of the user client to the user client again in response to the login request.
After the user client encrypts the transaction information to obtain second encryption information, the user client may send the transaction information, the second encryption information, the first encryption information, and the first information to the merchant client.
In one embodiment, the user client may establish a communication connection with the merchant client by using a bluetooth, a local area network, or the like, and send the transaction information, the second encryption information, the first encryption information, and the first information to the merchant client.
In another embodiment, the user client may also convert the transaction information, the second encryption information, the first encryption information, and the first information into a digital object unique identifier for identification by the merchant client. The digital object unique identifier may include: bar codes, two-dimensional codes or character codes, etc. For example, the user client may convert the second encrypted information, the first encrypted information, and the first information into a two-dimensional code for scanning by the merchant client.
In another embodiment, the user client may further convert the transaction information, the second encryption information, the first encryption information, and the first information into sound wave data to be sent to the merchant client.
S110: the merchant client receives first information, first encryption information, transaction information and second encryption information sent by the user client, verifies the first encryption information and the second encryption information respectively, and stores the transaction information if the verification result is credible.
The merchant client may receive the first information, the first encrypted information, the transaction information, and the second encrypted information sent by the user client.
In one embodiment, the merchant client may receive the first information, the first encrypted information, the transaction information, and the second encrypted information sent by the user client through a communication connection established with the user client, such as a bluetooth communication connection, a local area network connection, and the like.
In another embodiment, the merchant client may obtain the first information, the first encrypted information, the transaction information, and the second encrypted information from the user client by identifying a unique identifier for the digital object.
In another embodiment, the merchant client may further obtain the first information, the first encrypted information, the transaction information, and the second encrypted information sent by the user client by receiving sound wave data.
The merchant client verifies the first encryption information and the second encryption information respectively, and may specifically include: the merchant client may perform first verification on the first encrypted information, and may perform second verification on the second encrypted information if the first verification result is trusted.
In one embodiment, the merchant client may perform a first verification of the first encrypted information using a public key of the server.
In an embodiment, the first verification of the first encrypted information by the merchant client using the public key of the server may specifically include: the merchant client can decrypt the first encrypted information by using the public key of the server to obtain first decrypted information, calculate the digest value of the first information, compare whether the digest values of the first decrypted information and the first information are the same, and if so, determine that the first verification result is credible.
If the first verification result is credible, it may be indicated that the first information sent by the user client is credible information. It may then be indicated that the first token in the first information, the offline payment identity and the public key of the user client are all trusted.
Further, the merchant client may perform a second verification of the second encrypted information. Specifically, the merchant client may verify the second encrypted information using a public key of the user client in the first information.
In one embodiment, the merchant client may verify the second encrypted information using the public key of the user client in the first information may include: the merchant client may decrypt the second encrypted information using the public key of the user client to obtain second decrypted information, calculate a digest value of the transaction information, compare whether the digest value of the transaction information is the same as the second decrypted information, and if so, determine that a second verification result is authentic.
If the second verification result is credible, the transaction information sent by the user client can be represented as credible information. The merchant client may store the transaction information.
S112: and the merchant client encrypts third information comprising the transaction information and the second encryption information to obtain third encryption information, establishes communication connection with the server and sends the third information and the third encryption information to the server.
The third information may be information including the transaction information and the second encryption information.
The merchant client may encrypt the third information to obtain third encrypted information. Specifically, the merchant client may encrypt the third information by using a private key of the merchant client to obtain third encrypted information.
And after the merchant client recovers the network, or after the server recovers the work. The merchant client and the server may establish a communication connection.
The merchant client may send the third information and third encrypted information to the server.
S114: and the server receives the third information and the third encrypted information, verifies the third encrypted information and the second encrypted information in the third information respectively, and if the verification result is credible, acquires the transaction information and completes the transaction.
The server may receive the third information and the third encrypted information sent by the merchant client.
In one embodiment, the verifying the second encrypted information of the third encrypted information and the third information by the server respectively may include: the server may perform third verification on the third encrypted information, and may perform fourth verification on the second encrypted information in the third information if a third verification result is trusted.
In one embodiment, the server may verify the third encrypted information using a merchant client public key. Specifically, the server may decrypt the third encrypted information by using the merchant client public key to obtain third decrypted information, calculate a digest value of the third information, compare whether the digest values of the third decrypted information and the third information are the same, and if the digest values of the third decrypted information and the third information are the same, the third verification result may be trusted.
And if the third verification result is credible, the third information is credible.
Further, a fourth verification may be performed on the second encrypted information in the third information. Specifically, the second encrypted information in the third information may be verified by using a user client public key. Specifically, the server may decrypt, by using a public key of the user client, the second encrypted information in the third information to obtain fourth decrypted information, calculate a digest value of the transaction information, compare whether the digest values of the fourth decrypted information and the transaction information are the same, and if the digest values of the fourth decrypted information and the transaction information are the same, determine that a fourth verification result may be trusted.
And if the fourth verification result is credible, the transaction information is credible. The server can obtain the transaction information, and can complete the transaction according to the transaction information. For example, the server may complete services such as deduction of a user account, collection of money for a merchant user, and the like according to the transaction amount in the transaction information.
In one embodiment, after the server completes the transaction, the transaction method may further include S116: the server may also send a notification message to the user client and/or the merchant client that the transaction is complete.
Based on the transaction processing method provided by the above embodiment, the present specification also provides an embodiment of a transaction processing method at the stage of transaction behavior occurrence. Fig. 2 is a flow chart of another embodiment of a transaction processing method provided herein. Referring to fig. 2, the transaction processing method may include the following steps.
S202: the user client generates transaction information, encrypts the transaction information to obtain second encryption information, and sends the transaction information, the second encryption information, and the pre-acquired first information and the pre-acquired first encryption information to the merchant client.
The transaction information may include: a first token, a transaction time, a transaction amount, and a universal unique identification code. The transaction information may be used to uniquely identify a transaction.
The user client may encrypt the transaction information to obtain second encrypted information. Specifically, the user client may encrypt the transaction information by using a private key of the user client to obtain second encrypted information.
The first information and the first encryption information may be acquired in advance. The first information and the first encryption information may be acquired from a server. The first information and the first encryption information may be stored at the user client.
The first information may include: the first token, the offline payment identification and the public key of the user client.
The first token may be information representing the identity of the user client.
The offline payment identifier may be an identifier indicating that offline payment is allowed.
The first encrypted information may be information obtained by encrypting the first information using a server private key.
In one embodiment, the user client sends the transaction information, the second encryption information, and the first information and the first encryption information acquired in advance to the merchant client, and any one of the following may be used: the user client can establish communication connection with the merchant client in a Bluetooth mode, a local area network mode and the like, and sends the transaction information, the second encryption information, the first encryption information and the first information to the merchant client; or, the user client may convert the transaction information, the second encryption information, the first encryption information, and the first information into a unique identifier of a digital object for the merchant client to identify; or, the user client may convert the transaction information, the second encryption information, the first encryption information, and the first information into sound wave data and send the sound wave data to the merchant client.
S204: the merchant client receives first information, first encryption information, transaction information and second encryption information sent by the user client, verifies the first encryption information and the second encryption information respectively, and stores the transaction information if the verification result is credible.
In one embodiment, the merchant client may receive the first information, the first encrypted information, the transaction information, and the second encrypted information sent by the user client through a communication connection established with the user client, such as a bluetooth communication connection, a local area network connection, and the like.
In another embodiment, the merchant client may obtain the first information, the first encrypted information, the transaction information, and the second encrypted information from the user client by identifying a unique identifier for the digital object.
In another embodiment, the merchant client may further obtain the first information, the first encrypted information, the transaction information, and the second encrypted information sent by the user client by receiving sound wave data.
After receiving the first information, the first encryption information, the transaction information and the second encryption information sent by the user client, the merchant client can respectively verify the first encryption information and the second encryption information, and if the verification result is credible, the merchant client stores the transaction information.
Specifically, the merchant client may perform first verification on the first encrypted information, perform second verification on the second encrypted information if the first verification result is trusted, and store the transaction information if the second verification result is trusted.
In one embodiment, the merchant client may perform a first verification of the first encrypted information using a public key of the server.
In one embodiment, the merchant client may perform a second verification of the second encrypted information using a public key of the user client in the first information.
S206: and the merchant client encrypts third information comprising the transaction information and the second encryption information to obtain third encryption information, establishes communication connection with the server and sends the third information and the third encryption information to the server.
The merchant client may encrypt the third information to obtain third encrypted information. The third information may include: the transaction information and second encryption information.
In one embodiment, the merchant client may encrypt the third information by using a private key of the merchant client, so as to obtain third encrypted information.
And after the merchant client recovers the network, or after the server recovers the work. The merchant client and the server may establish a communication connection.
The merchant client may send the third information and third encrypted information to the server.
S208: and the server receives the third information and the third encrypted information, verifies the third encrypted information and the second encrypted information in the third information respectively, and if the verification result is credible, acquires the transaction information and completes the transaction.
The server receives the third information and the third encrypted information, and can verify second encrypted information in the third encrypted information and the third information respectively. Specifically, the server may perform third verification on the third encrypted information, and may perform fourth verification on the second encrypted information in the third information if the third verification result is trusted.
And if the fourth verification result is credible, the transaction information is credible. The server may obtain the transaction information and complete a transaction according to the transaction information.
After the server completes the transaction, the transaction method may further include S210: the server sends a notification message of the completion of the transaction to the user client and/or the merchant client.
Based on the transaction processing method provided by the above embodiment, the present specification further provides an embodiment of a transaction processing method at the user client side. FIG. 3 is a flow chart of one embodiment of a method for processing a transaction at a client of a user as provided by the present specification. Referring to fig. 3, the method may include the following steps.
S302: the user client generates transaction information.
S304: and the user client encrypts the transaction information to obtain second encrypted information.
S306: and the user client sends the transaction information, the second encryption information, and the first information and the first encryption information which are acquired in advance to a merchant client.
The present specification also provides embodiments of a transaction processing method at a merchant client side. FIG. 4 is a flow diagram of one embodiment of a merchant client-side transaction processing method provided herein. Referring to fig. 4, the method may include the following steps.
S402: the merchant client receives first information, first encryption information, transaction information and second encryption information sent by a user client;
s404: and the merchant client verifies the first encryption information and the second encryption information respectively, and if the verification results are credible, the transaction information is stored.
S406: the merchant client encrypts third information comprising the transaction information and the second encryption information to obtain third encryption information;
s408: and the merchant client establishes communication connection with the server and sends the third information and the third encryption information to the server.
The present specification also provides embodiments of a transaction processing method on the server side. FIG. 5 is a flow diagram of one embodiment of a server-side transaction processing method provided herein. Referring to fig. 5, the method may include the following steps.
S502: the server receives third information and third encrypted information; the third information includes: transaction information and second encryption information;
s504: and the server respectively verifies the third encrypted information and the second encrypted information in the third information, and if the verification results are credible, the transaction information is acquired, and the transaction is completed.
In one embodiment, the transaction method may further include: the server sends a notification message of the completion of the transaction to the user client and/or the merchant client.
In the embodiments provided by this specification, when a transaction occurs, if both the user client and the merchant client cannot establish communication connection with the server, the user client generates transaction information, the transaction information is encrypted by using a private key of the user client and then sent to the merchant client, the merchant client verifies a message sent by the user client, if the verification result is trusted, the transaction information of the user client is considered as trusted information, the transaction information is stored, after the merchant client establishes communication connection with the server, the transaction information is sent to the server, and the server verifies that the transaction information is trusted, and then the transaction is completed. By using the embodiments provided by the specification, the transaction between the user client and the merchant client can be ensured to be realized when the user client and the merchant client cannot establish communication connection with the server. The merchant client and the server verify the transaction information respectively, so that the reliability of the transaction information can be ensured, and the security of the transaction is ensured.
In the method embodiment provided by the embodiment of the present application, the step executed by the merchant client, the step executed by the server, and the step executed by the user client may be executed in a mobile terminal, a computer terminal, or a similar computing device, respectively.
Taking an example of the present invention running on a computer terminal, fig. 6 is a block diagram of a hardware structure of a computer terminal in this embodiment. As shown in fig. 6, the computer terminal may include one or more processors 102 (only one shown), a memory 104 for storing data, and a transmission module 106 for communication functions.
The processor 102 may include a Central Processing Unit (CPU) or a Graphics Processing Unit (GPU), but may also include other single-chip computers with logic processing capability, logic gates, integrated circuits, and the like, or a suitable combination thereof.
The memory 104 may be used to store software programs and modules of application software, such as program instructions/modules corresponding to the search method in the embodiment of the present invention, and the processor 102 executes various functional applications and data processing by running the software programs and modules stored in the memory 104, that is, implementing the page display method in the above embodiment. The memory 104 may include high speed random access memory, and may also include non-volatile memory, such as one or more magnetic storage devices, flash memory, or other non-volatile solid-state memory. In some examples, the memory 104 may further include memory located remotely from the processor 102, which may be connected to the page display device via a network. Examples of such networks include, but are not limited to, the internet, intranets, local area networks, mobile communication networks, and combinations thereof. When the method is implemented, the memory can also be implemented in a cloud memory mode, and the specific implementation mode is not limited in this specification.
The transmission module 106 may be used to receive or transmit data via a network. The specific examples of the network described above may include a wireless network provided by a communication provider of the page display apparatus. In one example, the transmission module 106 includes a Network adapter (NIC) that can be connected to other Network devices through a base station to communicate with the internet. In one example, the transmission module 106 may be a Radio Frequency (RF) module, which is used for communicating with the internet in a wireless manner.
It will be understood by those skilled in the art that the structure shown in fig. 6 is only an illustration, and is not intended to limit the structure of the computer terminal. For example, the computer terminal may also include more or fewer components than shown in fig. 6, and may also include other Processing hardware, such as a GPU (Graphics Processing Unit), for example, or have a different configuration than that shown in fig. 6.
Based on the transaction method, the specification further provides a system, a server, a user client and a merchant client. The systems, servers, user clients, and merchant clients described may include systems (including distributed systems), software (applications), modules, components, devices, etc. that utilize the methods described in embodiments of the present description in conjunction with any necessary equipment to implement the hardware. Based on the same innovative concept, the system, the server and the client provided by the specification are as described in the following embodiments. Because the implementation schemes and methods for solving the problems of the system, the server, the user client and the merchant client are similar, the implementation of the system, the server, the user client and the merchant client in the embodiments of the present description can refer to the implementation of the foregoing methods, and repeated details are not repeated. Although the means described in the embodiments below are preferably implemented in software, an implementation in hardware, or a combination of software and hardware is also possible and contemplated.
FIG. 7 is a system diagram illustrating an embodiment of a transaction processing system provided herein. As shown in fig. 7, the transaction processing system may include: user client 200, merchant client 400, and server 600.
In one embodiment of the method of the present invention,
the user client 200 is configured to generate transaction information, encrypt the transaction information to obtain second encryption information, and send the transaction information, the second encryption information, and the first information and the first encryption information that are obtained in advance to the merchant client 400;
the merchant client 400 is configured to receive first information, first encryption information, transaction information, and second encryption information sent by the user client 200, verify the first encryption information and the second encryption information respectively, and store the transaction information if the verification result is trusted; encrypting third information comprising the transaction information and the second encryption information to obtain third encryption information; and is used for establishing a communication connection with the server 600, and sending the third information and the third encrypted information to the server 600;
the server 600 is configured to receive the third information and the third encrypted information, verify the third encrypted information and the second encrypted information in the third information, and if the verification result is that the third encrypted information and the second encrypted information in the third information are authentic, acquire the transaction information, and complete the transaction.
In another embodiment, the server 600 may be further configured to send a notification message of transaction completion to the user client 200 and/or the merchant client 400 after completing the transaction.
FIG. 8 is a block diagram of one embodiment of a user client for transaction processing provided herein. Referring to fig. 8, the user client may include: a transaction information generation module 802, a user encryption module 804, a user storage module 806, and a user transmission module 808.
The transaction information generation module 802 may be configured to generate transaction information. The transaction information may include: a first token, a transaction time, a transaction amount, and a universal unique identification code.
The user encryption module 804 may be configured to encrypt the transaction information to obtain second encryption information.
The user storage module 806 may be configured to store the first information and the first encryption information acquired in advance. The first encryption information may be information obtained by encrypting the first information. The first information may include: the first token, the offline payment identification and the public key of the user client.
The user sending module 808 may be configured to send the transaction information, the second encryption information, the first information, and the first encryption information to the merchant client.
FIG. 9 is a block diagram of one embodiment of a merchant client for transaction processing as provided herein. Referring to FIG. 9, the merchant client may include: a merchant receive module 902, a merchant verification module 904, a merchant encryption module 906, a merchant storage module 908, and a merchant transmit module 910.
In one embodiment of the method of the present invention,
the merchant receiving module 902 may be configured to receive first information, first encryption information, transaction information, and second encryption information sent by a user client. The first information may include: the first token, the offline payment identification and the public key of the user client. The first encryption information may be information obtained by encrypting the first information. The transaction information may include: a first token, a transaction time, a transaction amount, and a universal unique identification code. The second encryption information may be information obtained by encrypting the transaction information.
The merchant verification module 904 may be configured to verify the first encrypted information and the second encrypted information, respectively.
The merchant encryption module 906 may be configured to encrypt third information including the transaction information and the second encryption information to obtain third encryption information.
The merchant storage module 908 may be configured to store the transaction information, the third information, and the third encrypted information.
The merchant sending module 910 may be configured to send the third information and the third encrypted information to the server after the client establishes a communication connection with the server.
Fig. 10 is a block diagram of one embodiment of a server for transaction processing provided by the present specification. Referring to fig. 10, the server may include: a server receive module 1002, a server verification module 1004, and a transaction completion module 1006.
In one embodiment of the method of the present invention,
the server receiving module 1002 may be configured to receive third information and third encrypted information. The third information may include: transaction information and second encryption information. The transaction information may include: a first token, a transaction time, a transaction amount, and a universal unique identification code. The second encryption information may be information obtained by encrypting the transaction information. The third information may be information obtained by encrypting the third information.
The server verification module 1004 may be configured to verify the third encrypted information and the second encrypted information in the third information, respectively.
The transaction completion module 1006 may be configured to obtain the transaction information to complete the transaction when the verification result of the server verification module is trusted.
In another embodiment, the server may further include: a message notification module 1008, configured to send a notification message of completion of the transaction to the user client and/or the merchant client.
The transaction processing method or apparatus provided in the embodiments of the present specification may be implemented in a computer by a processor executing corresponding program instructions, for example, implemented at a PC end using a c + + language of a windows operating system, or implemented at an intelligent terminal using, for example, android and iOS system programming languages, and implemented based on processing logic of a quantum computer.
Specifically, another aspect of the present specification further provides a server, including a processor and a memory, where the memory stores computer program instructions executed by the processor, and the execution of the computer program instructions may implement steps executed by the server in the method embodiment.
In another aspect, the present specification further provides a client, including a processor and a memory, where the memory stores computer program instructions executed by the processor, and the execution of the computer program instructions may implement steps executed by a user client side or a merchant client side in the method embodiment.
Therefore, the embodiments of the transaction processing system, the user client, the merchant client and the server provided by the specification and the method embodiments provided by the specification are based on the same innovative concept, and therefore, the embodiments of the transaction processing system, the user client, the merchant client and the server provided by the specification can achieve the technical effects of the method embodiments provided by the specification.
The foregoing description has been directed to specific embodiments of this disclosure. Other embodiments are within the scope of the following claims. In some cases, the actions or steps recited in the claims may be performed in a different order than in the embodiments and still achieve desirable results. In addition, the processes depicted in the accompanying figures do not necessarily require the particular order shown, or sequential order, to achieve desirable results. In some embodiments, multitasking and parallel processing may also be possible or may be advantageous.
In the 90 s of the 20 th century, improvements in a technology could clearly distinguish between improvements in hardware (e.g., improvements in circuit structures such as diodes, transistors, switches, etc.) and improvements in software (improvements in process flow). However, as technology advances, many of today's process flow improvements have been seen as direct improvements in hardware circuit architecture. Designers almost always obtain the corresponding hardware circuit structure by programming an improved method flow into the hardware circuit. Thus, it cannot be said that an improvement in the process flow cannot be realized by hardware physical modules. For example, a Programmable Logic Device (PLD), such as a Field Programmable Gate Array (FPGA), is an integrated circuit whose Logic functions are determined by programming the Device by a user. A digital system is "integrated" on a PLD by the designer's own programming without requiring the chip manufacturer to design and fabricate application-specific integrated circuit chips. Furthermore, nowadays, instead of manually making an integrated Circuit chip, such Programming is often implemented by "logic compiler" software, which is similar to a software compiler used in program development and writing, but the original code before compiling is also written by a specific Programming Language, which is called Hardware Description Language (HDL), and HDL is not only one but many, such as abel (advanced Boolean Expression Language), ahdl (alternate Language Description Language), traffic, pl (core unified Programming Language), HDCal, JHDL (Java Hardware Description Language), langue, Lola, HDL, laspam, hardsradware (Hardware Description Language), vhjhd (Hardware Description Language), and vhigh-Language, which are currently used in most common. It will also be apparent to those skilled in the art that hardware circuitry that implements the logical method flows can be readily obtained by merely slightly programming the method flows into an integrated circuit using the hardware description languages described above.
The controller may be implemented in any suitable manner, for example, the controller may take the form of, for example, a microprocessor or processor and a computer-readable medium storing computer-readable program code (e.g., software or firmware) executable by the (micro) processor, logic gates, switches, an Application Specific Integrated Circuit (ASIC), a programmable logic controller, and an embedded microcontroller, examples of which include, but are not limited to, the following microcontrollers: ARC 625D, Atmel AT91SAM, Microchip PIC18F26K20, and Silicone Labs C8051F320, the memory controller may also be implemented as part of the control logic for the memory. Those skilled in the art will also appreciate that, in addition to implementing the controller as pure computer readable program code, the same functionality can be implemented by logically programming method steps such that the controller is in the form of logic gates, switches, application specific integrated circuits, programmable logic controllers, embedded microcontrollers and the like. Such a controller may thus be considered a hardware component, and the means included therein for performing the various functions may also be considered as a structure within the hardware component. Or even means for performing the functions may be regarded as being both a software module for performing the method and a structure within a hardware component.
The apparatuses, modules or units illustrated in the above embodiments may be implemented by a computer chip or an entity, or implemented by a product with certain functions. One typical implementation device is a computer. In particular, the computer may be, for example, a personal computer, a laptop computer, a cellular telephone, a camera phone, a smartphone, a personal digital assistant, a media player, a navigation device, an email device, a game console, a tablet computer, a wearable device, or a combination of any of these devices.
For convenience of description, the above devices are described as being divided into various units by function, and are described separately. Of course, the functions of the various elements may be implemented in the same one or more software and/or hardware implementations of the present description.
As will be appreciated by one skilled in the art, embodiments of the present invention may be provided as a method, apparatus, or computer program product. Accordingly, the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present invention may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.
The present invention is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (devices), and computer program products according to embodiments of the invention. It will be understood that each flow and/or block of the flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
In a typical configuration, a computing device includes one or more processors (CPUs), input/output interfaces, network interfaces, and memory.
The memory may include forms of volatile memory in a computer readable medium, Random Access Memory (RAM) and/or non-volatile memory, such as Read Only Memory (ROM) or flash memory (flash RAM). Memory is an example of a computer-readable medium.
Computer-readable media, including both non-transitory and non-transitory, removable and non-removable media, may implement information storage by any method or technology. The information may be computer readable instructions, data structures, modules of a program, or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), Static Random Access Memory (SRAM), Dynamic Random Access Memory (DRAM), other types of Random Access Memory (RAM), Read Only Memory (ROM), Electrically Erasable Programmable Read Only Memory (EEPROM), flash memory or other memory technology, compact disc read only memory (CD-ROM), Digital Versatile Discs (DVD) or other optical storage, magnetic cassettes, magnetic tape magnetic disk storage, graphene storage or other magnetic storage devices, or any other non-transmission medium that can be used to store information that can be accessed by a computing device. As defined herein, a computer readable medium does not include a transitory computer readable medium such as a modulated data signal and a carrier wave.
It should also be noted that the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other like elements in a process, method, article, or apparatus that comprises the element.
As will be appreciated by one skilled in the art, embodiments of the present description may be provided as a method, apparatus or computer program product. Accordingly, the description may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the description may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.
This description may be described in the general context of computer-executable instructions, such as program modules, being executed by a computer. Generally, program modules include routines, programs, objects, components, data structures, etc. that perform particular tasks or implement particular abstract data types. The specification may also be practiced in distributed computing environments where tasks are performed by remote processing devices that are linked through a communications network. In a distributed computing environment, program modules may be located in both local and remote computer storage media including memory storage devices.
The embodiments in the present specification are described in a progressive manner, and the same and similar parts among the embodiments are referred to each other, and each embodiment focuses on the differences from the other embodiments. In particular, as for the device and server embodiments, since they are substantially similar to the method embodiments, the description is simple, and the relevant points can be referred to the partial description of the method embodiments.
The above description is only an example of the present specification, and is not intended to limit the present specification. Various modifications and alterations to this description will become apparent to those skilled in the art. Any modification, equivalent replacement, improvement or the like made within the spirit and principle of the present specification should be included in the scope of the claims.
Claims (34)
Priority Applications (3)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201810165018.5A CN108564363B (en) | 2018-02-28 | 2018-02-28 | A transaction processing method, server, client and system |
| TW107146772A TW201937425A (en) | 2018-02-28 | 2018-12-24 | Transaction processing method, server, client, and system |
| PCT/CN2019/073818 WO2019165875A1 (en) | 2018-02-28 | 2019-01-30 | Transaction processing method, server, client, and system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201810165018.5A CN108564363B (en) | 2018-02-28 | 2018-02-28 | A transaction processing method, server, client and system |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN108564363A true CN108564363A (en) | 2018-09-21 |
| CN108564363B CN108564363B (en) | 2020-10-13 |
Family
ID=63532196
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201810165018.5A Active CN108564363B (en) | 2018-02-28 | 2018-02-28 | A transaction processing method, server, client and system |
Country Status (3)
| Country | Link |
|---|---|
| CN (1) | CN108564363B (en) |
| TW (1) | TW201937425A (en) |
| WO (1) | WO2019165875A1 (en) |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2019165875A1 (en) * | 2018-02-28 | 2019-09-06 | 阿里巴巴集团控股有限公司 | Transaction processing method, server, client, and system |
| WO2021109694A1 (en) * | 2019-12-03 | 2021-06-10 | 支付宝(杭州)信息技术有限公司 | Payment result acquisition method and apparatus, payment device, and cash register device |
Families Citing this family (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111160895A (en) * | 2019-12-27 | 2020-05-15 | 支付宝实验室(新加坡)有限公司 | Service processing method and device based on graphic code, electronic equipment and storage medium |
| TWI758859B (en) * | 2020-09-14 | 2022-03-21 | 華南商業銀行股份有限公司 | Offline transaction system and offline transaction method |
| TWI770676B (en) * | 2020-11-17 | 2022-07-11 | 玉山商業銀行股份有限公司 | System and method for online transaction processing |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104318437A (en) * | 2014-10-11 | 2015-01-28 | 上海众人科技有限公司 | Online payment system and payment method for virtual prepaid card |
| CN104751334A (en) * | 2013-12-31 | 2015-07-01 | 腾讯科技（深圳）有限公司 | Service processing method, device and system |
| CN105229683A (en) * | 2013-02-11 | 2016-01-06 | 高朋股份有限公司 | Consumer devices payment token manages |
| CN106327186A (en) * | 2016-08-31 | 2017-01-11 | 中城智慧科技有限公司 | Offline payment method based on NFC |
| CN106875186A (en) * | 2016-06-20 | 2017-06-20 | 阿里巴巴集团控股有限公司 | A kind of offline payment method and device |
| CN206312224U (en) * | 2016-09-23 | 2017-07-07 | 深圳市微付充科技有限公司 | Payment system |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN108564363B (en) * | 2018-02-28 | 2020-10-13 | 阿里巴巴集团控股有限公司 | A transaction processing method, server, client and system |
-
2018
- 2018-02-28 CN CN201810165018.5A patent/CN108564363B/en active Active
- 2018-12-24 TW TW107146772A patent/TW201937425A/en unknown
-
2019
- 2019-01-30 WO PCT/CN2019/073818 patent/WO2019165875A1/en not_active Ceased
Patent Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105229683A (en) * | 2013-02-11 | 2016-01-06 | 高朋股份有限公司 | Consumer devices payment token manages |
| CN104751334A (en) * | 2013-12-31 | 2015-07-01 | 腾讯科技（深圳）有限公司 | Service processing method, device and system |
| CN104318437A (en) * | 2014-10-11 | 2015-01-28 | 上海众人科技有限公司 | Online payment system and payment method for virtual prepaid card |
| CN106875186A (en) * | 2016-06-20 | 2017-06-20 | 阿里巴巴集团控股有限公司 | A kind of offline payment method and device |
| CN106327186A (en) * | 2016-08-31 | 2017-01-11 | 中城智慧科技有限公司 | Offline payment method based on NFC |
| CN206312224U (en) * | 2016-09-23 | 2017-07-07 | 深圳市微付充科技有限公司 | Payment system |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2019165875A1 (en) * | 2018-02-28 | 2019-09-06 | 阿里巴巴集团控股有限公司 | Transaction processing method, server, client, and system |
| WO2021109694A1 (en) * | 2019-12-03 | 2021-06-10 | 支付宝(杭州)信息技术有限公司 | Payment result acquisition method and apparatus, payment device, and cash register device |
Also Published As
| Publication number | Publication date |
|---|---|
| WO2019165875A1 (en) | 2019-09-06 |
| CN108564363B (en) | 2020-10-13 |
| TW201937425A (en) | 2019-09-16 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US10951424B2 (en) | Method, apparatus, and electronic device for communication between blockchain nodes, and method, apparatus, and electronic device for blockchain-based certificate management | |
| US10917394B2 (en) | Data operations using a proxy encryption key | |
| EP3195558B1 (en) | Efficient and reliable attestation | |
| US10164963B2 (en) | Enforcing server authentication based on a hardware token | |
| US20170032111A1 (en) | Approaches for providing multi-factor authentication credentials | |
| TW201830302A (en) | Business process method and device, data share system, and storage medium | |
| JP2020509674A (en) | Two-dimensional code generation method and device, and two-dimensional code recognition method and device | |
| CN108564363A (en) | A kind of transaction processing method, server, client and system | |
| CN115374175A (en) | Method and device for tracking task execution progress based on microservice architecture | |
| CN111199037A (en) | Login method, system and device | |
| TW202130160A (en) | Session establishing method and cross-border payment method, apparatus, and system | |
| US10944578B2 (en) | Identity verification | |
| CN112434348A (en) | Data verification processing method, device and equipment | |
| US12032663B2 (en) | Cross-session issuance of verifiable credential | |
| CN106257879A (en) | A kind of method and apparatus downloading application | |
| CN114499828B (en) | Communication method, Internet of Things terminal, gateway device and Internet of Things system | |
| CN110990492B (en) | Information processing method, device and equipment | |
| US8904508B2 (en) | System and method for real time secure image based key generation using partial polygons assembled into a master composite image | |
| CN115442027B (en) | Scheme request verification method, device and equipment | |
| CN115037548A (en) | System, method and device for data security multi-party computation based on block chain | |
| CN116032626B (en) | A method and device for autonomous driving to safely and legally access WEB backend services | |
| CN109255596B (en) | A method and device for receiving a password red envelope | |
| CN106850712B (en) | Money flow verification system and method for third party payment platform | |
| CN118590306A (en) | Service request verification method, device, equipment, storage medium and program product | |
| HK40031266B (en) | Binding processing method, device and equipment |
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 | ||
| TR01 | Transfer of patent right | ||
| TR01 | Transfer of patent right |
Effective date of registration: 20201021 Address after: Cayman Enterprise Centre, 27 Hospital Road, George Town, Grand Cayman Islands Patentee after: Innovative advanced technology Co.,Ltd. Address before: Cayman Enterprise Centre, 27 Hospital Road, George Town, Grand Cayman Islands Patentee before: Advanced innovation technology Co.,Ltd. Effective date of registration: 20201021 Address after: Cayman Enterprise Centre, 27 Hospital Road, George Town, Grand Cayman Islands Patentee after: Advanced innovation technology Co.,Ltd. Address before: Greater Cayman, British Cayman Islands Patentee before: Alibaba Group Holding Ltd. |