[go: up one dir, main page]

WO2019223276A1 - Procédé et dispositif de réalisation de l'authentification d'informations de transaction - Google Patents

Procédé et dispositif de réalisation de l'authentification d'informations de transaction Download PDF

Info

Publication number
WO2019223276A1
WO2019223276A1 PCT/CN2018/117567 CN2018117567W WO2019223276A1 WO 2019223276 A1 WO2019223276 A1 WO 2019223276A1 CN 2018117567 W CN2018117567 W CN 2018117567W WO 2019223276 A1 WO2019223276 A1 WO 2019223276A1
Authority
WO
WIPO (PCT)
Prior art keywords
transaction information
public key
key source
encryption result
verification
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.)
Ceased
Application number
PCT/CN2018/117567
Other languages
English (en)
Chinese (zh)
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.)
Winway Energy Ltd
Original Assignee
Winway Energy 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 Winway Energy Ltd filed Critical Winway Energy Ltd
Publication of WO2019223276A1 publication Critical patent/WO2019223276A1/fr
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Images

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/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

Definitions

  • the present application relates to the field of data processing, for example, to a method and device for implementing transaction information verification.
  • the owner of the transaction address When conducting transactions involving digital currencies, in order to verify the authenticity of transaction information (for example, a transaction address, etc.), the owner of the transaction address usually encrypts a previously agreed message or initiates a payment based on the transaction address.
  • transaction information for example, a transaction address, etc.
  • the embodiments of the present disclosure provide a method and a device for verifying transaction information, so as to improve the security of transaction information.
  • An embodiment of the present disclosure provides a method for implementing transaction information verification, which includes: using digital certificates to implement transaction information verification.
  • An embodiment of the present disclosure further provides a device for verifying transaction information, which is used to implement verification of transaction information by using a digital certificate.
  • An embodiment of the present disclosure further provides a server including the foregoing device for verifying transaction information.
  • An embodiment of the present disclosure also provides a computer-readable storage medium storing computer-executable instructions configured to perform the foregoing method for implementing verification of transaction information.
  • An embodiment of the present disclosure also provides a computer program product.
  • the computer program product includes a computer program stored on a computer-readable storage medium.
  • the computer program includes program instructions. When the program instructions are executed by a computer, The computer executes the method for verifying transaction information described above.
  • An embodiment of the present disclosure further provides an electronic device, including:
  • At least one processor At least one processor
  • a memory connected in communication with the at least one processor; wherein,
  • the memory stores instructions executable by the at least one processor, and when the instructions are executed by the at least one processor, the at least one processor is caused to execute the foregoing method for implementing transaction information verification.
  • FIG. 1 is a schematic diagram of a method for implementing transaction information verification according to an embodiment of the present disclosure
  • FIG. 2 is a schematic diagram of a method for encrypting transaction information according to an embodiment of the present disclosure
  • FIG. 3 is a schematic diagram of a method for encrypting a public key source according to an embodiment of the present disclosure
  • FIG. 4 is a schematic diagram of a method for decrypting an encrypted result of transaction information according to an embodiment of the present disclosure
  • FIG. 5 is a schematic diagram of a method for verifying transaction information according to an embodiment of the present disclosure
  • FIG. 6 is a schematic diagram of a method for decrypting a public key source encryption result according to an embodiment of the present disclosure
  • FIG. 7 is a schematic diagram of a method for verifying a public key source according to an embodiment of the present disclosure.
  • FIG. 8 is a schematic diagram of a device for implementing transaction information verification according to an embodiment of the present disclosure
  • FIG. 9 is a schematic diagram of an apparatus for encrypting transaction information according to an embodiment of the present disclosure.
  • FIG. 10 is a schematic diagram of an apparatus for providing a result of encrypting transaction information according to an embodiment of the present disclosure
  • FIG. 11 is a schematic diagram of a device for encrypting a public key source according to an embodiment of the present disclosure
  • FIG. 12 is a schematic diagram of an apparatus for providing a public key source encryption result according to an embodiment of the present disclosure
  • FIG. 13 is a schematic diagram of an apparatus for decrypting a result of encrypting transaction information according to an embodiment of the present disclosure
  • FIG. 14 is a schematic diagram of an apparatus for receiving an encrypted result of transaction information according to an embodiment of the present disclosure
  • 15 is a schematic diagram of a device for verifying transaction information according to an embodiment of the present disclosure.
  • 16 is a schematic diagram of an apparatus for decrypting a public key source encryption result according to an embodiment of the present disclosure
  • 17 is a schematic diagram of an apparatus for receiving a public key source encryption result according to an embodiment of the present disclosure
  • FIG. 18 is a schematic diagram of a device for verifying a public key source according to an embodiment of the present disclosure
  • FIG. 19 is a schematic diagram of a device for implementing a payment operation according to an embodiment of the present disclosure.
  • FIG. 20 is a schematic structural diagram of an electronic device according to an embodiment of the present disclosure.
  • decryption module 40: decryption module
  • an embodiment of the present disclosure provides a method for verifying transaction information, which includes: using a digital certificate to verify transaction information.
  • the verification of transaction information by using a digital certificate may include: encrypting the transaction information by using a private key of the digital certificate to obtain a transaction information encryption result.
  • the transaction information encryption result may be provided.
  • the payee the operating entity can be the payee's device, such as the payee's website server, etc .; the same applies below
  • the payer the operating entity can be the payer's device, such as the payer's client terminal and other devices ; The same applies hereinafter) to send the transaction information encryption result.
  • the transaction information may be provided.
  • the payee may send the transaction information to the payer.
  • a public key source may be provided.
  • the payee may send the public key source to the payer.
  • the public key source can be encrypted by using the private key of the digital certificate to obtain a public key source encryption result.
  • the encryption of at least one of the transaction information and the public key source may be based on a request or an initiative.
  • the payee encrypts at least one of the transaction information and public key source based on a request from the payer or other third party; or, the payee actively proactively encrypts the transaction information based on preset policies, conditions, etc.
  • At least one of the public key sources is encrypted.
  • the public key source encryption result may be provided.
  • the payee may send the public key source encryption result to the payer.
  • At least one of the transaction information encryption result, public key source encryption result, transaction information, and public key source may be provided directly or indirectly.
  • the payee may directly or indirectly send at least one of the transaction information encryption result, the public key source encryption result, the transaction information, and the public key source to the payer.
  • the indirect providing may include providing through a transaction intermediary.
  • the payee may send the transaction information encryption result and the public key source encryption result to the payer through a transaction intermediary (the operating entity may be a device of the transaction website, such as the website server of the transaction website; the same applies below).
  • the operating entity may be a device of the transaction website, such as the website server of the transaction website; the same applies below).
  • Transaction information and at least one of the public key sources.
  • implementing transaction information verification by using a digital certificate may include: using a public key of the digital certificate to decrypt a transaction information encryption result obtained after the transaction information is encrypted to obtain the transaction information.
  • the transaction information encryption result may be received before decrypting the transaction information encryption result.
  • the payer may receive the transaction information encryption result from the payee; or, the payer may actively obtain the transaction information encryption result from the payee through active inquiry, request, or the like.
  • the transaction information may be received.
  • the payer may receive the transaction information from the payee; or, the payer may actively obtain the transaction information from the payee through active inquiry, request, or the like.
  • the received transaction information and the decrypted transaction information may be used for verification, and a payment operation may be triggered after the verification is passed.
  • the payer may use the transaction information received from or obtained from the payee and the transaction information decrypted by the payer for verification, and trigger the payment operation after the verification is passed.
  • the verification may include comparing the consistency between the received transaction information and the decrypted transaction information, and comparing the received transaction information with the decrypted transaction information. Confirm the verification when there is consistency between the two.
  • the payer may compare whether the transaction information received from or obtained from the payee is the same as the transaction information decrypted by the payer, and the transaction information received from or obtained from the payee is decrypted with the payer. When the obtained transaction information is the same, it is confirmed that the verification is passed.
  • the public key source can be decrypted by using the public key of the digital certificate to decrypt the public key source encryption result obtained by the public key source after encryption.
  • the public key source encryption result may be received before decrypting the public key source encryption result.
  • the payer may receive the public key source encryption result from the payee; or, the payer may actively obtain the public key source encryption result from the payee by actively querying, requesting, etc.
  • the public key source may be received.
  • the payer may receive the public key source from the payee; or, the payer may actively obtain the public key source from the payee through active inquiry, request, and the like.
  • the public key may be obtained according to the received public key source.
  • the payer may obtain (eg, download) the public key from the public key source by receiving, actively requesting, or the like.
  • the received public key source and the decrypted public key source may be used for verification, and a payment operation may be triggered after the verification is passed.
  • the payer may use the public key source received from or obtained from the payee and the public key source decrypted by the payer for verification, and trigger the payment operation after the verification is passed.
  • the verification may include comparing the consistency between the received public key source and the decrypted public key source, and comparing the received public key source with the decrypted
  • the verification is confirmed.
  • the payer may compare whether the source of the public key received or obtained from the payee is the same as the source of the public key decrypted by the payer.
  • the transaction information received from or obtained from the payee is compared with the payment.
  • the source of the public key decrypted by the party is the same, it is confirmed that the verification passes.
  • the payment operation may include paying digital currency.
  • the decryption of at least one of the transaction information encryption result and the public key source encryption result may be based on a request or an initiative.
  • the payer decrypts at least one of the transaction information encryption result and the public key source encryption result based on a request from the payee or another third party; or, the payer proactively decrypts the transaction information based on preset policies, conditions, etc.
  • At least one of the transaction information encryption result and the public key source encryption result is decrypted.
  • At least one of the transaction information encryption result, public key source encryption result, transaction information, and public key source may be received directly or indirectly.
  • the payer may directly or indirectly receive at least one of the transaction information encryption result, the public key source encryption result, the transaction information, and the public key source from the payee.
  • the indirect receiving may include receiving through a transaction intermediary.
  • the payer may receive at least one of the transaction information encryption result, the public key source encryption result, the transaction information, and the public key source from the payee through a transaction intermediary such as a transaction website.
  • the digital certificate may include a Hypertext Transfer Protocol (HTTPS) certificate; it may also include a Secure Sockets Layer (SSL) certificate, a Transport Layer Security (TLS) ) Certificates, etc.
  • HTTPS Hypertext Transfer Protocol
  • SSL Secure Sockets Layer
  • TLS Transport Layer Security
  • the transaction information may include at least one of a transaction address (for example: a payment address; the same applies hereinafter) and a transaction amount (for example: a payment amount; the same applies hereinafter).
  • a transaction address for example: a payment address; the same applies hereinafter
  • a transaction amount for example: a payment amount; the same applies hereinafter
  • the public key source may include a Uniform Resource Locator (URL) of an HTTPS website.
  • URL Uniform Resource Locator
  • the digital currency may be a cryptocurrency.
  • an embodiment of the present disclosure further provides a device 10 for implementing transaction information verification, which is used to implement verification of transaction information by using a digital certificate.
  • the device 10 may be installed on a payee (the operating entity may be a payee device, such as a web server of the payee; the same applies hereinafter).
  • the device 10 may include an encryption module 20, configured to encrypt the transaction information by using the private key of the digital certificate to obtain a transaction information encryption result.
  • the device 10 may further include a data interface 30, configured to provide an encryption result of the transaction information.
  • the data interface 30 may send the transaction information encryption result to the payer.
  • the data interface 30 may also be used to provide the transaction information.
  • the data interface 30 may send the transaction information to a payer.
  • the data interface 30 may also be used to provide a public key source.
  • the data interface 30 may send the public key source to the payer.
  • the encryption module 20 may be configured to: use the private key of the digital certificate to encrypt the public key source to obtain a public key source encryption result.
  • the encryption module 20 may be configured to: based on a request or actively initiate encryption of at least one of the transaction information and a public key source. For example, the encryption module 20 encrypts at least one of the transaction information and the public key source based on a request from a payer or other third party; or, the encryption module 20 actively encrypts the transaction information based on preset policies, conditions, etc. At least one of the public key sources is encrypted.
  • the data interface 30 may be configured to provide the public key source encryption result.
  • the data interface 30 may send the public key source encryption result to the payer.
  • the data interface 30 may be configured to directly or indirectly provide at least one of the transaction information encryption result, a public key source encryption result, transaction information, and a public key source.
  • the data interface 30 may directly or indirectly send at least one of the transaction information encryption result, the public key source encryption result, the transaction information, and the public key source to the payer.
  • the data interface 30 may be configured to provide at least one of the transaction information encryption result, a public key source encryption result, transaction information, and a public key source through a transaction intermediary.
  • the data interface 30 may send at least one of the transaction information encryption result, the public key source encryption result, the transaction information, and the public key source to the payer through a transaction intermediary such as a transaction website.
  • the apparatus 10 may include a decryption module 40, configured to: decrypt the transaction information encryption result obtained by encrypting the transaction information using the public key of the digital certificate to obtain the transaction information.
  • a decryption module 40 configured to: decrypt the transaction information encryption result obtained by encrypting the transaction information using the public key of the digital certificate to obtain the transaction information.
  • the apparatus 10 may include a data interface 50 for receiving the transaction information encryption result before decrypting the transaction information encryption result.
  • the data interface 50 may receive the transaction information encryption result from the payee; or, the data interface 50 may actively obtain the transaction information encryption result from the payee through an active query, request, or the like.
  • the data interface 50 may be configured to receive the transaction information.
  • the data interface 50 may receive the transaction information from the beneficiary; or, the data interface 50 may actively obtain the transaction information from the beneficiary through active inquiry, request, and the like.
  • the device 10 may include a verification module 60, configured to perform verification by using the received transaction information and the decrypted transaction information, and trigger a payment operation after the verification is passed.
  • the verification module 60 may use the transaction information received from or obtained from the payee and the transaction information decrypted by the payer for verification, and trigger a payment operation after the verification is passed.
  • the verification module 60 may be configured to compare the consistency between the received transaction information and the decrypted transaction information, and compare the received transaction information with the decrypted transaction information. When there is consistency between the transaction information, it is confirmed that the verification is passed. For example, the verification module 60 may compare whether the transaction information received or obtained from the payee is the same as the transaction information decrypted by the decryption module 40. The transaction information received or obtained from the payee is compared with the decryption module 40. When the decrypted transaction information is the same, it is confirmed that the verification is passed.
  • the decryption module 40 may be configured to: use the public key of the digital certificate to decrypt the public key source encryption result obtained by the public key source after encryption to obtain the public key source.
  • the data interface 50 may be configured to: before decrypting the public key source encryption result, receive the public key source encryption result.
  • the data interface 50 may receive the public key source encryption result from the payee; or, the data interface 50 may actively obtain the public key source encryption result from the payee through an active query, request, or the like.
  • the data interface 50 may be configured to receive the public key source.
  • the data interface 50 may receive the public key source from the payee; or, the data interface 50 may actively obtain the public key source from the payee through active query, request, or the like.
  • the data interface 50 may be configured to obtain the public key according to the received public key source.
  • the data interface 50 may obtain (for example, download) the public key from the public key source by receiving, actively requesting, or the like.
  • the verification module 60 may be configured to perform verification by using the received public key source and the decrypted public key source, and trigger a payment operation after the verification is passed.
  • the verification module 60 may use the public key source received from or obtained from the payee and the public key source decrypted by the decryption module 40 to perform verification, and trigger a payment operation after the verification is passed.
  • the verification module 60 may be configured to compare the consistency between the received public key source and the decrypted public key source, and compare the received public key source with the decrypted public key source. When the source of the decrypted public key is consistent, it is confirmed that the verification passes. For example, the verification module 60 may compare whether the source of the public key received or obtained from the payee is the same as the source of the public key decrypted by the decryption module 40. The transaction information received from or obtained from the payee is decrypted. When the source of the public key decrypted by the module 40 is the same, it is confirmed that the verification is passed.
  • the device 10 may include a payment module 70 for performing a payment operation according to a trigger of the verification module 60.
  • the payment module 70 may be configured to pay digital currency.
  • the data interface 50 may be configured to directly or indirectly receive at least one of the transaction information encryption result, a public key source encryption result, transaction information, and a public key source.
  • the data interface 50 may directly or indirectly receive at least one of the transaction information encryption result, the public key source encryption result, the transaction information, and the public key source from the payee.
  • the data interface 50 may be configured to receive at least one of the transaction information encryption result, the public key source encryption result, the transaction information, and the public key source through a transaction intermediary.
  • the data interface 50 may receive at least one of the transaction information encryption result, the public key source encryption result, the transaction information, and the public key source from the payee through a transaction intermediary such as a transaction website.
  • the digital certificate may include an HTTPS certificate, and may also include an SSL certificate, a TLS certificate, and the like.
  • the transaction information may include at least one of a transaction address and a transaction amount.
  • the public key source may include a URL of an HTTPS website.
  • the digital currency may be a cryptocurrency.
  • the public key mentioned above can be cached by the payer and other third parties.
  • the provision, acquisition, encryption, and decryption of the above-mentioned various data may also be achieved through other channels such as a third party.
  • An embodiment of the present disclosure further provides a server including the device 10 for verifying transaction information in the foregoing embodiment, for example, including at least one of an encryption module 20 and a data interface 30, or including a decryption module 40, a data interface 50, and verification. At least one of the module 60 and the payment module 70.
  • An embodiment of the present disclosure further provides a computer-readable storage medium storing computer-executable instructions configured to execute the method for implementing transaction information verification in the foregoing embodiment, for example, with the encryption module 20 and data A method related to at least one of the interfaces 30, or a method related to at least one of the decryption module 40, the data interface 50, the verification module 60, and the payment module 70.
  • An embodiment of the present disclosure also provides a computer program product.
  • the computer program product includes a computer program stored on a computer-readable storage medium.
  • the computer program includes program instructions.
  • the computer executes the method for verifying transaction information in the foregoing embodiment, for example, a method related to at least one of the encryption module 20 and the data interface 30, or the decryption module 40, the data interface 50, the verification module 60, and the payment module 70. At least one of the related methods.
  • the computer-readable storage medium may be a transitory computer-readable storage medium, or may be a non-transitory computer-readable storage medium.
  • An embodiment of the present disclosure further provides an electronic device, whose structure is shown in FIG. 20.
  • the electronic device 200 includes:
  • At least one processor 201, and one processor 201 is taken as an example in FIG. 20; and the memory 202 may further include a communication interface 203 and a bus 204.
  • the processor 201, the communication interface 203, and the memory 202 can complete communication with each other through the bus 204.
  • the communication interface 203 can be used for information transmission.
  • the processor 201 may call the logical instructions in the memory 202 to execute the method for verifying transaction information in the foregoing embodiment, for example, a method related to at least one of the encryption module 20 and the data interface 30, or a method related to the decryption module 40 and data. A method related to at least one of the interface 50, the verification module 60, and the payment module 70.
  • logic instructions in the memory 202 can be implemented in the form of software functional units and sold or used as an independent product, and can be stored in a computer-readable storage medium.
  • the memory 202 is a computer-readable storage medium and can be used to store software programs and computer-executable programs, such as program instructions / modules corresponding to the methods in the embodiments of the present disclosure.
  • the processor 201 executes functional applications and data processing by running software programs, instructions, and modules stored in the memory 202, that is, implementing the method for verifying transaction information in the foregoing method embodiment, for example, interfaces with the encryption module 20 and data A method related to at least one of 30, or a method related to at least one of the decryption module 40, the data interface 50, the verification module 60, and the payment module 70.
  • the memory 202 may include a storage program area and a storage data area, where the storage program area may store an operating system and application programs required for at least one function; the storage data area may store data created according to the use of the terminal device, and the like.
  • the memory 202 may include a high-speed random access memory, and may further include a non-volatile memory.
  • the solution for verifying transaction information in the embodiments of the present disclosure improves the security and efficiency of transaction information verification.
  • the data processing described in this application may include at least one of setting, calculation, judgment, transmission, storage, management, etc. based on or performed on the data.
  • the data processing may be data processing related to a digital certificate by a data processing device
  • the digital certificate may be obtained through the data processing
  • the data processing device may be a digital certificate processing device.
  • the digital certificate processing device may be a digital currency mining machine, and the digital currency may be a cryptocurrency such as Bitcoin.
  • the technical solution of the embodiment of the present disclosure may be embodied in the form of a software product.
  • the computer software product is stored in a storage medium and includes one or more instructions for making a computer device (which may be a personal computer, a server, or a network). Equipment, etc.) perform all or part of the steps of the method described in the embodiments of the present disclosure.
  • the foregoing storage medium may be a non-transitory storage medium, including: a U disk, a mobile hard disk, a read-only memory (ROM, Read-Only Memory), a random access memory (RAM, Random Access Memory), a magnetic disk, or an optical disc A medium that can store program code, or a transient storage medium.
  • first, second, etc. may be used in this application to describe various elements, these elements should not be limited by these terms. These terms are only used to distinguish one element from another.
  • the first element can be called the second element, and likewise, the second element can be called the first element, as long as all occurrences of the "first element” are renamed consistently and all occurrences of The “second component” can be renamed consistently.
  • the first element and the second element are both elements, but may not be the same element.
  • the aspects, implementations, implementations or features in the described embodiments can be used individually or in any combination.
  • Various aspects in the described embodiments may be implemented by software, hardware, or a combination of software and hardware.
  • the described embodiments may also be embodied by a computer-readable medium storing computer-readable code, the computer-readable code including instructions executable by at least one computing device.
  • the computer-readable medium can be associated with any data storage device capable of storing data, which can be read by a computer system.
  • Computer-readable media for example may include read-only memory, random-access memory, CD-ROM, HDD, DVD, magnetic tape, and optical data storage devices.
  • the computer-readable medium can also be distributed among computer systems connected through a network, so that the computer-readable code can be stored and executed in a distributed manner.

Landscapes

  • Business, Economics & Management (AREA)
  • Engineering & Computer Science (AREA)
  • Accounting & Taxation (AREA)
  • Computer Security & Cryptography (AREA)
  • Finance (AREA)
  • Strategic Management (AREA)
  • Physics & Mathematics (AREA)
  • General Business, Economics & Management (AREA)
  • General Physics & Mathematics (AREA)
  • Theoretical Computer Science (AREA)
  • Financial Or Insurance-Related Operations Such As Payment And Settlement (AREA)
  • Storage Device Security (AREA)

Abstract

L'invention concerne un procédé et un dispositif pour réaliser l'authentification d'informations de transaction. Le procédé consiste à : utiliser un certificat numérique pour réaliser l'authentification d'informations de transaction. Un appareil électronique comprend : au moins un processeur ; et un dispositif de stockage dans une connexion de communication avec ledit processeurs. Le dispositif de stockage stocke une instruction exécutable par ledit processeur, et lors de l'exécution de l'instruction, ledit processeur met en œuvre le procédé pour réaliser l'authentification d'informations de transaction. Un serveur comprend le dispositif pour réaliser l'authentification d'informations de transaction.
PCT/CN2018/117567 2018-05-24 2018-11-27 Procédé et dispositif de réalisation de l'authentification d'informations de transaction Ceased WO2019223276A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201810506808.5 2018-05-24
CN201810506808.5A CN108764921A (zh) 2018-05-24 2018-05-24 一种实现交易信息验证的方法和装置

Publications (1)

Publication Number Publication Date
WO2019223276A1 true WO2019223276A1 (fr) 2019-11-28

Family

ID=64005374

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2018/117567 Ceased WO2019223276A1 (fr) 2018-05-24 2018-11-27 Procédé et dispositif de réalisation de l'authentification d'informations de transaction

Country Status (2)

Country Link
CN (1) CN108764921A (fr)
WO (1) WO2019223276A1 (fr)

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108764921A (zh) * 2018-05-24 2018-11-06 北京比特大陆科技有限公司 一种实现交易信息验证的方法和装置

Citations (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102609841A (zh) * 2012-01-13 2012-07-25 东北大学 一种基于数字证书的远程移动支付系统及支付方法
CN104182876A (zh) * 2013-05-24 2014-12-03 中国电信股份有限公司 安全支付交易方法和系统
US20160080157A1 (en) * 2014-09-16 2016-03-17 Keypasco Ab Network authentication method for secure electronic transactions
CN106651331A (zh) * 2016-12-22 2017-05-10 飞天诚信科技股份有限公司 一种基于数字货币的电子交易方法及系统
CN108764867A (zh) * 2018-05-24 2018-11-06 北京比特大陆科技有限公司 一种实现交易信息验证的方法和装置
CN108764921A (zh) * 2018-05-24 2018-11-06 北京比特大陆科技有限公司 一种实现交易信息验证的方法和装置
CN108846650A (zh) * 2018-05-24 2018-11-20 北京比特大陆科技有限公司 一种实现交易信息验证的方法和装置

Family Cites Families (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20100250947A1 (en) * 2006-10-18 2010-09-30 Kamfu Wong System and method of preventing spam by using pay-charge-contribution and authentication means
US20090183000A1 (en) * 2008-01-16 2009-07-16 Scott Krig Method And System For Dynamically Granting A DRM License Using A URL
AU2010100533B4 (en) * 2010-04-02 2010-12-16 Isx Ip Ltd Method and system for verifying transactions
CN107077674B (zh) * 2016-12-29 2021-06-11 达闼机器人有限公司 交易验证处理方法、装置及节点设备
CN107911222B (zh) * 2017-11-21 2020-08-28 沃通电子认证服务有限公司 数字签名生成、验证方法及其设备和存储介质

Patent Citations (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102609841A (zh) * 2012-01-13 2012-07-25 东北大学 一种基于数字证书的远程移动支付系统及支付方法
CN104182876A (zh) * 2013-05-24 2014-12-03 中国电信股份有限公司 安全支付交易方法和系统
US20160080157A1 (en) * 2014-09-16 2016-03-17 Keypasco Ab Network authentication method for secure electronic transactions
CN106651331A (zh) * 2016-12-22 2017-05-10 飞天诚信科技股份有限公司 一种基于数字货币的电子交易方法及系统
CN108764867A (zh) * 2018-05-24 2018-11-06 北京比特大陆科技有限公司 一种实现交易信息验证的方法和装置
CN108764921A (zh) * 2018-05-24 2018-11-06 北京比特大陆科技有限公司 一种实现交易信息验证的方法和装置
CN108846650A (zh) * 2018-05-24 2018-11-20 北京比特大陆科技有限公司 一种实现交易信息验证的方法和装置

Also Published As

Publication number Publication date
CN108764921A (zh) 2018-11-06

Similar Documents

Publication Publication Date Title
US11985239B2 (en) Forward secrecy in transport layer security (TLS) using ephemeral keys
US12401505B2 (en) Agile cryptographic deployment service
US20210367795A1 (en) Identity-Linked Authentication Through A User Certificate System
US12278916B2 (en) Data processing method and apparatus, device, and medium
USRE49673E1 (en) Systems and methods for secure data exchange
WO2017045552A1 (fr) Procédé et dispositif pour charger un certificat numérique dans une communication de couche de prise sécurisée (ssl) ou de sécurité de couche de transport (tls)
WO2020233235A1 (fr) Procédé et appareil de vérification de données de chaîne de blocs
US20240048361A1 (en) Key Management for Cryptography-as-a-service and Data Governance Systems
TWI663865B (zh) 基於跨鏈架構的身分識別管理系統及其方法
US12141248B2 (en) Systems and methods for whitebox device binding
CN106960343B (zh) 一种电子现金安全支付方法与装置
CN110519304A (zh) 基于tee的https双向认证方法
CN110602075A (zh) 一种加密访问控制的文件流处理的方法、装置及系统
US9578016B2 (en) Optimizing secure communications between a client authenticating server and a mobile client
CN111049789A (zh) 域名访问的方法和装置
WO2019223232A1 (fr) Procédé et dispositif d'authentification d'informations de transaction
WO2021082222A1 (fr) Procédé et appareil de communication, procédé et appareil de stockage, et procédé et appareil d'utilisation
WO2019223231A1 (fr) Procédé et dispositif de réalisation d'une authentification d'informations de transaction
WO2019223276A1 (fr) Procédé et dispositif de réalisation de l'authentification d'informations de transaction
CN107809412A (zh) 使用目标网站的网站证书私钥进行解密的方法与设备
CN115529129B (zh) 加密通信方法、系统、计算机设备、可读存储介质及程序产品
US20250156860A1 (en) Security authentication method, apparatus and system for digital currency transaction
US20240048532A1 (en) Data exchange protection and governance system
CN116318897A (zh) 一种数据传输方法、系统、装置、计算机设备及存储介质
CN116405319B (zh) 基于区块链的碳金融凭证共享方法和装置、设备和介质

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 18919760

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 18919760

Country of ref document: EP

Kind code of ref document: A1