WO2019223231A1 - 实现交易信息验证的方法和装置 - Google Patents

实现交易信息验证的方法和装置 Download PDF

Info

Publication number
WO2019223231A1
WO2019223231A1 PCT/CN2018/112025 CN2018112025W WO2019223231A1 WO 2019223231 A1 WO2019223231 A1 WO 2019223231A1 CN 2018112025 W CN2018112025 W CN 2018112025W WO 2019223231 A1 WO2019223231 A1 WO 2019223231A1
Authority
WO
WIPO (PCT)
Prior art keywords
transaction information
public key
key source
encryption result
transaction
Prior art date
Application number
PCT/CN2018/112025
Other languages
English (en)
French (fr)
Inventor
李志波
张理
Original Assignee
赢威能源有限公司
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 赢威能源有限公司 filed Critical 赢威能源有限公司
Publication of WO2019223231A1 publication Critical patent/WO2019223231A1/zh

Links

Images

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06QINFORMATION 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/00Payment architectures, schemes or protocols
    • G06Q20/04Payment circuits
    • G06Q20/06Private payment circuits, e.g. involving electronic currency used among participants of a common payment scheme
    • G06Q20/065Private payment circuits, e.g. involving electronic currency used among participants of a common payment scheme using e-cash
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06QINFORMATION 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/00Payment architectures, schemes or protocols
    • G06Q20/38Payment protocols; Details thereof
    • G06Q20/382Payment protocols; Details thereof insuring higher security of transaction
    • G06Q20/3829Payment protocols; Details thereof insuring higher security of transaction involving key management

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 vouchers, in order to verify the authenticity of transaction information (eg, transaction address, etc.), the owner of the transaction address usually encrypts a pre-negotiated message or initiates a payment based on the transaction address.
  • transaction information eg, transaction address, etc.
  • An embodiment of the present disclosure provides a method for verifying transaction information, including: encrypting transaction information by using a private key of a digital certificate to obtain a transaction information encryption result to implement transaction information verification.
  • An embodiment of the present disclosure further provides a device for verifying transaction information, including an encryption module, configured to: use a private key of a digital certificate to encrypt the transaction information to obtain a transaction information encryption result to implement transaction information verification.
  • 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, causes the at least one processor to execute the foregoing method for verifying transaction information.
  • 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.
  • 10 device for verifying transaction information
  • 20 encryption module
  • 30 data interface
  • 40 decryption module
  • 50 data interface
  • 60 verification module
  • 70 payment 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 through active inquiry, request, or the like.
  • 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 payment of digital credentials.
  • 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 certificate may be embodied as a digital currency, and the digital currency may be a cryptocurrency such as Bitcoin.
  • 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 a 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 by actively querying, requesting, 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 for digital credentials.
  • the decryption module 40 may be configured to: decrypt at least one of the transaction information encryption result and the public key source encryption result based on a request or an initiative. For example, the decryption module 40 decrypts at least one of the encryption result of the transaction information and the encryption result of the public key source based on a request from the payee or other third party; At least one of the transaction information encryption result and the public key source encryption result is decrypted.
  • 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 certificate may be embodied as a digital currency, and the digital currency may be a cryptocurrency such as Bitcoin. .
  • 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 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 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)
  • Accounting & Taxation (AREA)
  • Engineering & Computer Science (AREA)
  • Finance (AREA)
  • Strategic Management (AREA)
  • Physics & Mathematics (AREA)
  • General Business, Economics & Management (AREA)
  • General Physics & Mathematics (AREA)
  • Theoretical Computer Science (AREA)
  • Computer Security & Cryptography (AREA)
  • Financial Or Insurance-Related Operations Such As Payment And Settlement (AREA)
  • Storage Device Security (AREA)

Abstract

本申请提供了一种实现交易信息验证的方法,包括:利用数字证书的私钥对交易信息进行加密得到交易信息加密结果,以实现交易信息验证。本申请还提供了一种实现交易信息验证的装置,包括加密模块,用于:利用数字证书的私钥对交易信息进行加密得到交易信息加密结果,以实现交易信息验证。本申请还提供了一种电子设备,包括:至少一个处理器;以及与所述至少一个处理器通信连接的存储器;其中,所述存储器存储有可被所述至少一个处理器执行的指令,所述指令被所述至少一个处理器执行时,使所述至少一个处理器执行上述的实现交易信息验证的方法。本申请还提供了一种服务器,包含上述的实现交易信息验证的装置。

Description

实现交易信息验证的方法和装置 技术领域
本申请涉及数据处理领域,例如涉及一种实现交易信息验证的方法和装置。
背景技术
在进行涉及数字凭证的交易时,为了验证交易信息(例如,交易地址等)的真实性,通常由该交易地址的拥有者基于该交易地址加密一段提前商定的消息或发起一笔支付。
发明内容
本公开实施例提供了一种实现交易信息验证的方法,包括:利用数字证书的私钥对交易信息进行加密得到交易信息加密结果,以实现交易信息验证。
本公开实施例还提供了一种实现交易信息验证的装置,包括加密模块,用于:利用数字证书的私钥对交易信息进行加密得到交易信息加密结果,以实现交易信息验证。
本公开实施例还提供了一种服务器,包含上述的实现交易信息验证的装置。
本公开实施例还提供了一种计算机可读存储介质,存储有计算机可执行指令,所述计算机可执行指令设置为执行上述的实现交易信息验证的方法。
本公开实施例还提供了一种计算机程序产品,所述计算机程序产品包括存储在计算机可读存储介质上的计算机程序,所述计算机程序包括程序指令,当所述程序指令被计算机执行时,使所述计算机执行上述的实现交易信息验证的方法。
本公开实施例还提供了一种电子设备,包括:
至少一个处理器;以及
与所述至少一个处理器通信连接的存储器;其中,
所述存储器存储有可被所述至少一个处理器执行的指令,所述指令被所 述至少一个处理器执行时,使所述至少一个处理器执行上述的实现交易信息验证的方法。
附图说明
一个或多个实施例通过与之对应的附图进行示例性说明,这些示例性说明和附图并不构成对实施例的限定,附图中具有相同参考数字标号的元件表示为类似的元件,附图不构成比例限制,并且其中:
图1为本公开实施例的实现交易信息验证的方法示意图;
图2为本公开实施例的对交易信息进行加密的方法示意图;
图3为本公开实施例的对公钥来源进行加密的方法示意图;
图4为本公开实施例的对交易信息加密结果进行解密的方法示意图;
图5为本公开实施例的对交易信息进行验证的方法示意图;
图6为本公开实施例的对公钥来源加密结果进行解密的方法示意图;
图7为本公开实施例的对公钥来源进行验证的方法示意图;
图8为本公开实施例的实现交易信息验证的装置示意图;
图9为本公开实施例的对交易信息进行加密的装置示意图;
图10为本公开实施例的提供交易信息加密结果的装置示意图;
图11为本公开实施例的对公钥来源进行加密的装置示意图;
图12为本公开实施例的提供公钥来源加密结果的装置示意图;
图13为本公开实施例的对交易信息加密结果进行解密的装置示意图;
图14为本公开实施例的接收交易信息加密结果的装置示意图;
图15为本公开实施例的对交易信息进行验证的装置示意图;
图16为本公开实施例的对公钥来源加密结果进行解密的装置示意图;
图17为本公开实施例的接收公钥来源加密结果的装置示意图;
图18为本公开实施例的对公钥来源进行验证的装置示意图;
图19为本公开实施例的实现支付操作的装置示意图;以及
图20为本公开实施例的电子设备的结构示意图。
附图标记:
10:实现交易信息验证的装置;20:加密模块;30:数据接口;40:解密模块;50:数据接口;60:验证模块;70:支付模块。
具体实施方式
为了能够更加详尽地了解本公开实施例的特点与技术内容,下面结合附图对本公开实施例的实现进行详细阐述,所附附图仅供参考说明之用,并非用来限定本公开实施例。在以下的技术描述中,为方便解释起见,通过多个细节以提供对所披露实施例的充分理解。然而,在没有这些细节的情况下,一个或多个实施例仍然可以实施。在其它情况下,为简化附图,熟知的结构和装置可以简化展示。
参见图1,本公开实施例提供了一种实现交易信息验证的方法,包括:利用数字证书实现交易信息的验证。
参见图2,所述利用数字证书实现交易信息的验证可以包括:利用所述数字证书的私钥对所述交易信息进行加密得到交易信息加密结果。
作为一个实施例,可以提供所述交易信息加密结果。例如,收款方(操作实体可以是收款方设备,例如收款方的网站服务器等;以下亦同)可以向付款方(操作实体可以是付款方设备,例如付款方的客户端等终端设备;以下亦同)发送所述交易信息加密结果。
作为一个实施例,可以提供所述交易信息。例如,收款方可以向付款方发送所述交易信息。
作为一个实施例,可以提供公钥来源。例如,收款方可以向付款方发送所述公钥来源。
参见图3,可以利用所述数字证书的私钥对所述公钥来源进行加密得到公钥来源加密结果。
作为一个实施例,对所述交易信息、公钥来源中至少之一进行的加密可以是基于请求或主动发起的。例如,收款方基于付款方或其他第三方的请求对所述交易信息、公钥来源中至少之一进行加密;或,收款方基于预设的策略、条件等主动对所述交易信息、公钥来源中至少之一进行加密。
作为一个实施例,可以提供所述公钥来源加密结果。例如,收款方可以向付款方发送所述公钥来源加密结果。
作为一个实施例,所述交易信息加密结果、公钥来源加密结果、交易信息、公钥来源中至少之一可以是直接或间接提供的。例如,收款方可以直接 或间接向付款方发送所述交易信息加密结果、公钥来源加密结果、交易信息、公钥来源中至少之一。
作为一个实施例,所述间接提供可以包括通过交易中介提供。例如,收款方可以通过交易网站(操作实体可以是交易网站的设备,例如交易网站的网站服务器等;以下亦同)等交易中介向付款方发送所述交易信息加密结果、公钥来源加密结果、交易信息、公钥来源中至少之一。
参见图4,所述利用数字证书实现交易信息验证可以包括:利用所述数字证书的公钥对所述交易信息在加密后得到的交易信息加密结果进行解密得到所述交易信息。
作为一个实施例,在解密所述交易信息加密结果之前,可以接收所述交易信息加密结果。例如,付款方可以接收来自收款方的所述交易信息加密结果;或,付款方可以通过主动查询、请求等方式从收款方主动获取所述交易信息加密结果。
作为一个实施例,可以接收所述交易信息。例如,付款方可以接收来自收款方的所述交易信息;或,付款方可以通过主动查询、请求等方式从收款方主动获取所述交易信息。
参见图5,可以利用所述接收到的交易信息以及所述解密得到的交易信息进行验证,在验证通过后触发支付操作。例如,付款方可以利用接收自或获取自收款方的所述交易信息以及付款方解密得到的交易信息进行验证,在验证通过后触发支付操作。
作为一个实施例,所述验证可以包括:对比所述接收到的交易信息以及所述解密得到的交易信息之间的一致性,在所述接收到的交易信息与所述解密得到的交易信息之间具有一致性时确认验证通过。例如,付款方可以比较接收自或获取自收款方的所述交易信息是否与付款方解密得到的交易信息相同,在付款方接收自或获取自收款方的所述交易信息与付款方解密得到的交易信息相同时,确认验证通过。
参见图6,可以利用所述数字证书的公钥对公钥来源在加密后得到的公钥来源加密结果进行解密得到所述公钥来源。
作为一个实施例,在解密所述公钥来源加密结果之前,可以接收所述公钥来源加密结果。例如,付款方可以接收来自收款方的所述公钥来源加密结 果;或,付款方可以通过主动查询、请求等方式从收款方主动获取所述公钥来源加密结果。
作为一个实施例,可以接收所述公钥来源。例如,付款方可以接收来自收款方的所述公钥来源;或,付款方可以通过主动查询、请求等方式从收款方主动获取所述公钥来源。
作为一个实施例,可以根据所述接收到的公钥来源获取所述公钥。例如,付款方可以通过接收、主动请求等方式从所述公钥来源获取(例如:下载)所述公钥。
参见图7,可以利用所述接收到的公钥来源以及所述解密得到的公钥来源进行验证,在验证通过后触发支付操作。例如,付款方可以利用接收自或获取自收款方的所述公钥来源以及付款方解密得到的公钥来源进行验证,在验证通过后触发支付操作。
作为一个实施例,所述验证可以包括:对比所述接收到的公钥来源以及所述解密得到的公钥来源之间的一致性,在所述接收到的公钥来源与所述解密得到的公钥来源之间具有一致性时确认验证通过。例如,付款方可以比较接收自或获取自收款方的所述公钥来源是否与付款方解密得到的公钥来源相同,在付款方接收自或获取自收款方的所述交易信息与付款方解密得到的公钥来源相同时,确认验证通过。
作为一个实施例,所述支付操作可以包括支付数字凭证。
作为一个实施例,对所述交易信息加密结果、公钥来源加密结果中至少之一进行的解密可以是基于请求或主动发起的。例如,付款方基于收款方或其他第三方的请求对所述交易信息加密结果、公钥来源加密结果中至少之一进行解密;或,付款方基于预设的策略、条件等主动对所述交易信息加密结果、公钥来源加密结果中至少之一进行解密。
作为一个实施例,所述交易信息加密结果、公钥来源加密结果、交易信息、公钥来源中至少之一可以是直接或间接接收的。例如,付款方可以直接或间接接收来自收款方的所述交易信息加密结果、公钥来源加密结果、交易信息、公钥来源中至少之一。
作为一个实施例,所述间接接收可以包括通过交易中介接收。例如,付款方可以通过交易网站等交易中介接收来自收款方的所述交易信息加密结 果、公钥来源加密结果、交易信息、公钥来源中至少之一。
作为一个实施例,所述数字证书可以包括超文本安全传送协议(Hypertext Transfer Protocol Secure,HTTPS)证书;也可以包括安全套接层(Secure Socket Layer,SSL)证书、安全传输层(Transport Layer Security,TLS)证书等。
所述交易信息可以包括交易地址(例如:支付地址;以下亦同)、交易数额(例如:支付数额;以下亦同)中至少之一。
作为一个实施例,所述公钥来源可以包括HTTPS网站的统一资源定位符(Uniform Resource Locator,URL)。
作为一个实施例,所述数字凭证可以体现为数字货币,所述数字货币可以是比特币等加密货币。
参见图8,本公开实施例还提供了一种实现交易信息验证的装置10,用于:利用数字证书实现交易信息的验证。所述装置10可以设置于收款方(操作实体可以是收款方设备,例如收款方的网站服务器等;以下亦同)。
参见图9,所述装置10可以包括加密模块20,用于:利用所述数字证书的私钥对所述交易信息进行加密得到交易信息加密结果。
参见图10,所述装置10还可以包括数据接口30,用于:提供所述交易信息加密结果。例如,数据接口30可以向付款方发送所述交易信息加密结果。
所述数据接口30还可以用于提供所述交易信息。例如,数据接口30可以向付款方发送所述交易信息。
所述数据接口30还可以用于提供公钥来源。例如,数据接口30可以向付款方发送所述公钥来源。
参见图11,所述加密模块20可以用于:利用所述数字证书的私钥对所述公钥来源进行加密得到公钥来源加密结果。
作为一个实施例,所述加密模块20可以用于:基于请求或主动发起对所述交易信息、公钥来源中至少之一的加密。例如,加密模块20基于付款方或其他第三方的请求对所述交易信息、公钥来源中至少之一进行加密;或,加密模块20基于预设的策略、条件等主动对所述交易信息、公钥来源中至少之一进行加密。
参见图12,所述数据接口30可以用于:提供所述公钥来源加密结果。例如,数据接口30可以向付款方发送所述公钥来源加密结果。
作为一个实施例,所述数据接口30可以用于:直接或间接提供所述交易信息加密结果、公钥来源加密结果、交易信息、公钥来源中至少之一。例如:数据接口30可以直接或间接向付款方发送所述交易信息加密结果、公钥来源加密结果、交易信息、公钥来源中至少之一。
作为一个实施例,所述数据接口30可以用于:通过交易中介提供所述交易信息加密结果、公钥来源加密结果、交易信息、公钥来源中至少之一。例如,数据接口30可以通过交易网站等交易中介向付款方发送所述交易信息加密结果、公钥来源加密结果、交易信息、公钥来源中至少之一。
参见图13,所述装置10可以包括解密模块40,用于:利用所述数字证书的公钥对所述交易信息在加密后得到的交易信息加密结果进行解密得到所述交易信息。
参见图14,所述装置10可以包括数据接口50,用于:在解密所述交易信息加密结果之前,接收所述交易信息加密结果。例如,数据接口50可以接收来自收款方的所述交易信息加密结果;或,数据接口50可以通过主动查询、请求等方式从收款方主动获取所述交易信息加密结果。
作为一个实施例,所述数据接口50可以用于:接收所述交易信息。例如,数据接口50可以接收来自收款方的所述交易信息;或,数据接口50可以通过主动查询、请求等方式从收款方主动获取所述交易信息。
参见图15,所述装置10可以包括验证模块60,用于:利用所述接收到的交易信息以及所述解密得到的交易信息进行验证,在验证通过后触发支付操作。例如,验证模块60可以利用接收自或获取自收款方的所述交易信息以及付款方解密得到的交易信息进行验证,在验证通过后触发支付操作。
作为一个实施例,所述验证模块60可以用于:对比所述接收到的交易信息以及所述解密得到的交易信息之间的一致性,在所述接收到的交易信息与所述解密得到的交易信息之间具有一致性时确认验证通过。例如,验证模块60可以比较接收自或获取自收款方的所述交易信息是否与解密模块40解密得到的交易信息相同,在接收自或获取自收款方的所述交易信息与解密模块40解密得到的交易信息相同时,确认验证通过。
参见图16,所述解密模块40可以用于:利用所述数字证书的公钥对公钥来源在加密后得到的公钥来源加密结果进行解密得到所述公钥来源。
参加图17,所述数据接口50可以用于:在解密所述公钥来源加密结果之前,接收所述公钥来源加密结果。例如,数据接口50可以接收来自收款方的所述公钥来源加密结果;或,数据接口50可以通过主动查询、请求等方式从收款方主动获取所述公钥来源加密结果。
作为一个实施例,所述数据接口50可以用于:接收所述公钥来源。例如,数据接口50可以接收来自收款方的所述公钥来源;或,数据接口50可以通过主动查询、请求等方式从收款方主动获取所述公钥来源。
作为一个实施例,所述数据接口50可以用于:根据所述接收到的公钥来源获取所述公钥。例如,数据接口50可以通过接收、主动请求等方式从所述公钥来源获取(例如:下载)所述公钥。
参见图18,所述验证模块60可以用于:利用所述接收到的公钥来源以及所述解密得到的公钥来源进行验证,在验证通过后触发支付操作。例如,验证模块60可以利用接收自或获取自收款方的所述公钥来源以及解密模块40解密得到的公钥来源进行验证,在验证通过后触发支付操作。
作为一个实施例,所述验证模块60可以用于:对比所述接收到的公钥来源以及所述解密得到的公钥来源之间的一致性,在所述接收到的公钥来源与所述解密得到的公钥来源之间具有一致性时确认验证通过。例如,验证模块60可以比较接收自或获取自收款方的所述公钥来源是否与解密模块40解密得到的公钥来源相同,在接收自或获取自收款方的所述交易信息与解密模块40解密得到的公钥来源相同时,确认验证通过。
参加图19,所述装置10可以包括支付模块70,用于:根据所述验证模块60的触发执行支付操作。
作为一个实施例,所述支付模块70可以用于:支付数字凭证。
作为一个实施例,所述解密模块40可以用于:基于请求或主动发起对所述交易信息加密结果、公钥来源加密结果中至少之一进行的解密。例如,解密模块40基于收款方或其他第三方的请求对所述交易信息加密结果、公钥来源加密结果中至少之一进行解密;或,解密模块40基于预设的策略、条件等主动对所述交易信息加密结果、公钥来源加密结果中至少之一进行解密。
作为一个实施例,所述数据接口50可以用于:直接或间接接收所述交易信息加密结果、公钥来源加密结果、交易信息、公钥来源中至少之一。例如, 数据接口50可以直接或间接接收来自收款方的所述交易信息加密结果、公钥来源加密结果、交易信息、公钥来源中至少之一。
作为一个实施例,所述数据接口50可以用于:通过交易中介接收所述交易信息加密结果、公钥来源加密结果、交易信息、公钥来源中至少之一。例如,数据接口50可以通过交易网站等交易中介接收来自收款方的所述交易信息加密结果、公钥来源加密结果、交易信息、公钥来源中至少之一。
作为一个实施例,所述数字证书可以包括HTTPS证书;也可以包括SSL证书、TLS证书等。
所述交易信息可以包括交易地址、交易数额中至少之一。
作为一个实施例,所述公钥来源可以包括HTTPS网站的URL。
作为一个实施例,所述数字凭证可以体现为数字货币,所述数字货币可以是比特币等加密货币。。
上述的公钥可由付款方以及其他第三方等缓存。
上述各种数据(例如:交易信息加密结果、公钥来源加密结果、交易信息、公钥来源等)的提供、获取、加密、解密等,也可以是通过第三方等其他途径实现的。
本公开实施例还提供了一种服务器,包含上述实施例的实现交易信息验证的装置10,例如:包含加密模块20、数据接口30中至少之一,或包含解密模块40、数据接口50、验证模块60、支付模块70中至少之一。
本公开实施例还提供了一种计算机可读存储介质,存储有计算机可执行指令,所述计算机可执行指令设置为执行上述实施例的实现交易信息验证的方法,例如:与加密模块20、数据接口30中至少之一相关的方法,或与解密模块40、数据接口50、验证模块60、支付模块70中至少之一相关的方法。
本公开实施例还提供了一种计算机程序产品,所述计算机程序产品包括存储在计算机可读存储介质上的计算机程序,所述计算机程序包括程序指令,当所述程序指令被计算机执行时,使所述计算机执行上述实施例的实现交易信息验证的方法,例如:与加密模块20、数据接口30中至少之一相关的方法,或与解密模块40、数据接口50、验证模块60、支付模块70中至少之一相关的方法。
上述的计算机可读存储介质可以是暂态计算机可读存储介质,也可以是 非暂态计算机可读存储介质。
本公开实施例还提供了一种电子设备,其结构如图20所示,该电子设备200包括:
至少一个处理器(processor)201,图20中以一个处理器201为例;和存储器(memory)202,还可以包括通信接口(Communication Interface)203和总线204。其中,处理器201、通信接口203、存储器202可以通过总线204完成相互间的通信。通信接口203可以用于信息传输。处理器201可以调用存储器202中的逻辑指令,以执行上述实施例的实现交易信息验证的方法,例如:与加密模块20、数据接口30中至少之一相关的方法,或与解密模块40、数据接口50、验证模块60、支付模块70中至少之一相关的方法。
此外,上述的存储器202中的逻辑指令可以通过软件功能单元的形式实现并作为独立的产品销售或使用时,可以存储在一个计算机可读取存储介质中。
存储器202作为一种计算机可读存储介质,可用于存储软件程序、计算机可执行程序,如本公开实施例中的方法对应的程序指令/模块。处理器201通过运行存储在存储器202中的软件程序、指令以及模块,从而执行功能应用以及数据处理,即实现上述方法实施例中的实现交易信息验证的方法,例如:与加密模块20、数据接口30中至少之一相关的方法,或与解密模块40、数据接口50、验证模块60、支付模块70中至少之一相关的方法。
存储器202可包括存储程序区和存储数据区,其中,存储程序区可存储操作系统、至少一个功能所需的应用程序;存储数据区可存储根据终端设备的使用所创建的数据等。此外,存储器202可以包括高速随机存取存储器,还可以包括非易失性存储器。
本公开实施例的实现交易信息验证的方案,提高了交易信息验证的安全性和效率。
本公开实施例的技术方案可以以软件产品的形式体现出来,该计算机软件产品存储在一个存储介质中,包括一个或多个指令用以使得一台计算机设备(可以是个人计算机,服务器,或者网络设备等)执行本公开实施例所述方法的全部或部分步骤。而前述的存储介质可以是非暂态存储介质,包括:U盘、移动硬盘、只读存储器(ROM,Read-Only Memory)、随机存取存储 器(RAM,Random Access Memory)、磁碟或者光盘等多种可以存储程序代码的介质,也可以是暂态存储介质。
当用于本申请中时,虽然术语“第一”、“第二”等可能会在本申请中使用以描述各元件,但这些元件不应受到这些术语的限制。这些术语仅用于将一个元件与另一个元件区别开。比如,在不改变描述的含义的情况下,第一元件可以叫做第二元件,并且同样第,第二元件可以叫做第一元件,只要所有出现的“第一元件”一致重命名并且所有出现的“第二元件”一致重命名即可。第一元件和第二元件都是元件,但可以不是相同的元件。
本申请中使用的用词仅用于描述实施例并且不用于限制权利要求。如在实施例以及权利要求的描述中使用的,除非上下文清楚地表明,否则单数形式的“一个”(a)、“一个”(an)和“所述”(the)旨在同样包括复数形式。类似地,如在本申请中所使用的术语“和/或”是指包含一个或一个以上相关联的列出的任何以及所有可能的组合。另外,当用于本申请中时,术语“包括”(comprise)及其变型“包括”(comprises)和/或包括(comprising)等指陈述的特征、整体、步骤、操作、元素,和/或组件的存在,但不排除一个或一个以上其它特征、整体、步骤、操作、元素、组件和/或这些的分组的存在或添加。
所描述的实施例中的各方面、实施方式、实现或特征能够单独使用或以任意组合的方式使用。所描述的实施例中的各方面可由软件、硬件或软硬件的结合实现。所描述的实施例也可以由存储有计算机可读代码的计算机可读介质体现,该计算机可读代码包括可由至少一个计算装置执行的指令。所述计算机可读介质可与任何能够存储数据的数据存储装置相关联,该数据可由计算机系统读取。用于举例的计算机可读介质可以包括只读存储器、随机存取存储器、CD-ROM、HDD、DVD、磁带以及光数据存储装置等。所述计算机可读介质还可以分布于通过网络联接的计算机系统中,这样计算机可读代码就可以分布式存储并执行。
上述技术描述可参照附图,这些附图形成了本申请的一部分,并且通过描述在附图中示出了依照所描述的实施例的实施方式。虽然这些实施例描述的足够详细以使本领域技术人员能够实现这些实施例,但这些实施例是非限制性的;这样就可以使用其它的实施例,并且在不脱离所描述的实施例的范 围的情况下还可以做出变化。比如,流程图中所描述的操作顺序是非限制性的,因此在流程图中阐释并且根据流程图描述的两个或两个以上操作的顺序可以根据若干实施例进行改变。作为另一个例子,在若干实施例中,在流程图中阐释并且根据流程图描述的一个或一个以上操作是可选的,或是可删除的。另外,某些步骤或功能可以添加到所公开的实施例中,或两个以上的步骤顺序被置换。所有这些变化被认为包含在所公开的实施例以及权利要求中。
另外,上述技术描述中使用术语以提供所描述的实施例的透彻理解。然而,并不需要过于详细的细节以实现所描述的实施例。因此,实施例的上述描述是为了阐释和描述而呈现的。上述描述中所呈现的实施例以及根据这些实施例所公开的例子是单独提供的,以添加上下文并有助于理解所描述的实施例。上述说明书不用于做到无遗漏或将所描述的实施例限制到本公开的精确形式。根据上述教导,若干修改、选择适用以及变化是可行的。在某些情况下,没有详细描述为人所熟知的处理步骤以避免不必要地影响所描述的实施例。

Claims (26)

  1. 一种实现交易信息验证的方法,其特征在于,包括:利用数字证书的私钥对交易信息进行加密得到交易信息加密结果,以实现交易信息验证。
  2. 根据权利要求1所述的方法,其特征在于,还包括:提供所述交易信息加密结果。
  3. 根据权利要求1或2所述的方法,其特征在于,还包括:提供所述交易信息。
  4. 根据权利要求3所述的方法,其特征在于,还包括:提供公钥来源。
  5. 根据权利要求4所述的方法,其特征在于,还包括:利用所述数字证书的私钥对所述公钥来源进行加密得到公钥来源加密结果。
  6. 根据权利要求5所述的方法,其特征在于,对所述交易信息、公钥来源中至少之一进行的加密是基于请求或主动发起的。
  7. 根据权利要求5所述的方法,其特征在于,还包括:提供所述公钥来源加密结果。
  8. 根据权利要求7所述的方法,其特征在于,所述交易信息加密结果、公钥来源加密结果、交易信息、公钥来源中至少之一是直接或间接提供的。
  9. 根据权利要求8所述的方法,其特征在于,所述间接提供包括通过交易中介提供。
  10. 根据权利要求1所述的方法,其特征在于,
    所述数字证书包括超文本安全传送协议HTTPS证书;
    所述交易信息包括交易地址、交易数额中至少之一。
  11. 根据权利要求4所述的方法,其特征在于,所述公钥来源包括HTTPS网站的统一资源定位符URL。
  12. 一种实现交易信息验证的装置,其特征在于,包括加密模块,用于:利用数字证书的私钥对交易信息进行加密得到交易信息加密结果,以实现交易信息验证。
  13. 根据权利要求12所述的装置,其特征在于,还包括数据接口,用于:提供所述交易信息加密结果。
  14. 根据权利要求13所述的装置,其特征在于,所述数据接口还用于:提供所述交易信息。
  15. 根据权利要求14所述的装置,其特征在于,所述数据接口还用于:提供公钥来源。
  16. 根据权利要求15所述的装置,其特征在于,所述加密模块还用于:利用所述数字证书的私钥对所述公钥来源进行加密得到公钥来源加密结果。
  17. 根据权利要求16所述的装置,其特征在于,所述加密模块用于:基于请求或主动发起对所述交易信息、公钥来源中至少之一的加密。
  18. 根据权利要求16所述的装置,其特征在于,所述数据接口还用于:提供所述公钥来源加密结果。
  19. 根据权利要求17所述的装置,其特征在于,所述数据接口用于:直接或间接提供所述交易信息加密结果、公钥来源加密结果、交易信息、公钥来源中至少之一。
  20. 根据权利要求19所述的装置,其特征在于,所述数据接口用于:通过交易中介提供所述交易信息加密结果、公钥来源加密结果、交易信息、公钥来源中至少之一。
  21. 根据权利要求12所述的装置,其特征在于,
    所述数字证书包括HTTPS证书;
    所述交易信息包括交易地址、交易数额中至少之一。
  22. 根据权利要求15所述的装置,其特征在于,所述公钥来源包括HTTPS网站的URL。
  23. 一种电子设备,其特征在于,包括:
    至少一个处理器;以及
    与所述至少一个处理器通信连接的存储器;其中,
    所述存储器存储有可被所述至少一个处理器执行的指令,所述指令被所述至少一个处理器执行时,使所述至少一个处理器执行权利要求1-11任一项所述的方法。
  24. 一种服务器,其特征在于,包含权利要求12-22任一项所述的装置。
  25. 一种计算机可读存储介质,其特征在于,存储有计算机可执行指令,所述计算机可执行指令设置为执行权利要求1-11任一项所述的方法。
  26. 一种计算机程序产品,其特征在于,所述计算机程序产品包括存储在计算机可读存储介质上的计算机程序,所述计算机程序包括程序指令,当所述程序指令被计算机执行时,使所述计算机执行权利要求1-11任一项所述的方法。
PCT/CN2018/112025 2018-05-24 2018-10-26 实现交易信息验证的方法和装置 WO2019223231A1 (zh)

Applications Claiming Priority (2)

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

Publications (1)

Publication Number Publication Date
WO2019223231A1 true WO2019223231A1 (zh) 2019-11-28

Family

ID=64005304

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2018/112025 WO2019223231A1 (zh) 2018-05-24 2018-10-26 实现交易信息验证的方法和装置

Country Status (2)

Country Link
CN (1) CN108764867A (zh)
WO (1) WO2019223231A1 (zh)

Families Citing this family (2)

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

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20160189151A1 (en) * 2014-12-31 2016-06-30 Ebay Enterprise, Inc. Distributed authentication for mobile devices
CN107248994A (zh) * 2017-06-26 2017-10-13 联动优势科技有限公司 一种信息发送方法、处理方法及装置
CN107528886A (zh) * 2017-07-25 2017-12-29 中国科学院计算技术研究所 区块链全网拆分方法与系统
CN107851245A (zh) * 2015-05-21 2018-03-27 万事达卡国际股份有限公司 用于将基于区块链的资产关联到法定货币账户的方法和系统
CN108063752A (zh) * 2017-11-02 2018-05-22 暨南大学 一种基于区块链与代理重加密技术的可信基因检测及数据共享方法
CN108764867A (zh) * 2018-05-24 2018-11-06 北京比特大陆科技有限公司 一种实现交易信息验证的方法和装置

Family Cites Families (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
AU2010100533B4 (en) * 2010-04-02 2010-12-16 Isx Ip Ltd Method and system for verifying transactions
CN106651331B (zh) * 2016-12-22 2019-11-29 飞天诚信科技股份有限公司 一种基于数字货币的电子交易方法及系统
CN107077674B (zh) * 2016-12-29 2021-06-11 达闼机器人有限公司 交易验证处理方法、装置及节点设备
CN107911222B (zh) * 2017-11-21 2020-08-28 沃通电子认证服务有限公司 数字签名生成、验证方法及其设备和存储介质

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20160189151A1 (en) * 2014-12-31 2016-06-30 Ebay Enterprise, Inc. Distributed authentication for mobile devices
CN107851245A (zh) * 2015-05-21 2018-03-27 万事达卡国际股份有限公司 用于将基于区块链的资产关联到法定货币账户的方法和系统
CN107248994A (zh) * 2017-06-26 2017-10-13 联动优势科技有限公司 一种信息发送方法、处理方法及装置
CN107528886A (zh) * 2017-07-25 2017-12-29 中国科学院计算技术研究所 区块链全网拆分方法与系统
CN108063752A (zh) * 2017-11-02 2018-05-22 暨南大学 一种基于区块链与代理重加密技术的可信基因检测及数据共享方法
CN108764867A (zh) * 2018-05-24 2018-11-06 北京比特大陆科技有限公司 一种实现交易信息验证的方法和装置

Also Published As

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

Similar Documents

Publication Publication Date Title
US20210367795A1 (en) Identity-Linked Authentication Through A User Certificate System
AU2022204148B2 (en) Methods and apparatus for providing blockchain participant identity binding
US11985239B2 (en) Forward secrecy in transport layer security (TLS) using ephemeral keys
WO2017045552A1 (zh) 一种在ssl或tls通信中加载数字证书的方法和装置
USRE49673E1 (en) Systems and methods for secure data exchange
US9137017B2 (en) Key recovery mechanism
US8438628B2 (en) Method and apparatus for split-terminating a secure network connection, with client authentication
US20190173873A1 (en) Identity verification document request handling utilizing a user certificate system and user identity document repository
WO2016107320A1 (zh) 网站安全信息的加载方法和浏览器装置
WO2017024934A1 (zh) 实现电子签章的方法、装置及签章服务器
US11196561B2 (en) Authorized data sharing using smart contracts
US11829502B2 (en) Data sharing via distributed ledgers
WO2020233235A1 (zh) 一种区块链的数据验证方法和装置
US9800556B2 (en) Systems and methods for providing data security services
TWI663865B (zh) 基於跨鏈架構的身分識別管理系統及其方法
US20220407729A1 (en) Data processing method and apparatus, device, and medium
US20210392004A1 (en) Apparatus and method for authenticating device based on certificate using physical unclonable function
US9578016B2 (en) Optimizing secure communications between a client authenticating server and a mobile client
TWI734729B (zh) 實現電子簽章的方法、裝置及簽章伺服器
WO2021082222A1 (zh) 通信方法、存储方法、运算方法及装置
WO2019223231A1 (zh) 实现交易信息验证的方法和装置
WO2019223232A1 (zh) 实现交易信息验证的方法和装置
WO2019223276A1 (zh) 实现交易信息验证的方法和装置
US20240187221A1 (en) Agile cryptographic deployment service
US20210056624A1 (en) Secure communication framework for crypto-exchange services using asymmetric and symmetric encryption

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: 18920015

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: 18920015

Country of ref document: EP

Kind code of ref document: A1