WO2019223276A1 - Method and device for realizing authentication of transaction information - Google Patents

Abstract

A method and device for realizing authentication of transaction information. The method comprises: using a digital certificate to realize authentication of transaction information. An electronic apparatus comprises: at least one processor; and a storage device in a communication connection with the at least one processor, wherein the storage device stores an instruction executable by the at least one processor, and when executing the instruction, the at least one processor implements the method for realizing authentication of transaction information. A server comprises the device for realizing authentication of transaction information.

Description

Method and device for realizing transaction information verification Technical field

The present application relates to the field of data processing, for example, to a method and device for implementing transaction information verification.

Background technique

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.

However, the existing information encryption methods are easy to be stolen and have low security.

Summary of the Invention

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; and

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.

BRIEF DESCRIPTION OF THE DRAWINGS

One or more embodiments are exemplarily described by corresponding drawings. These exemplary descriptions and drawings do not limit the embodiments. Elements with the same reference numerals in the drawings are shown as similar elements. The drawings do not constitute a scale limitation, and in which:

1 is a schematic diagram of a method for implementing transaction information verification according to an embodiment of the present disclosure;

2 is a schematic diagram of a method for encrypting transaction information according to an embodiment of the present disclosure;

3 is a schematic diagram of a method for encrypting a public key source according to an embodiment of the present disclosure;

4 is a schematic diagram of a method for decrypting an encrypted result of transaction information according to an embodiment of the present disclosure;

5 is a schematic diagram of a method for verifying transaction information according to an embodiment of the present disclosure;

6 is a schematic diagram of a method for decrypting a public key source encryption result according to an embodiment of the present disclosure;

7 is a schematic diagram of a method for verifying a public key source according to an embodiment of the present disclosure;

8 is a schematic diagram of a device for implementing transaction information verification according to an embodiment of the present disclosure;

9 is a schematic diagram of an apparatus for encrypting transaction information according to an embodiment of the present disclosure;

10 is a schematic diagram of an apparatus for providing a result of encrypting transaction information according to an embodiment of the present disclosure;

11 is a schematic diagram of a device for encrypting a public key source according to an embodiment of the present disclosure;

12 is a schematic diagram of an apparatus for providing a public key source encryption result according to an embodiment of the present disclosure;

13 is a schematic diagram of an apparatus for decrypting a result of encrypting transaction information according to an embodiment of the present disclosure;

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;

18 is a schematic diagram of a device for verifying a public key source according to an embodiment of the present disclosure;

19 is a schematic diagram of a device for implementing a payment operation according to an embodiment of the present disclosure; and

FIG. 20 is a schematic structural diagram of an electronic device according to an embodiment of the present disclosure.

Reference signs:

10: Device for verifying transaction information;

20: encryption module;

30: data interface;

40: decryption module;

50: data interface;

60: verification module;

70: payment module.

Detailed ways

In order to understand the features and technical contents of the embodiments of the present disclosure in more detail, the implementation of the embodiments of the present disclosure will be described in detail below with reference to the accompanying drawings. In the following technical description, for convenience of explanation, various details are provided to provide a full understanding of the disclosed embodiments. However, without these details, one or more embodiments can still be implemented. In other cases, to simplify the drawings, well-known structures and devices may simplify the display.

Referring to FIG. 1, an embodiment of the present disclosure provides a method for verifying transaction information, which includes: using a digital certificate to verify transaction information.

Referring to FIG. 2, 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.

As an embodiment, the transaction information encryption result may be provided. For example, the payee (the operating entity can be the payee's device, such as the payee's website server, etc .; the same applies below) to 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.

As an embodiment, the transaction information may be provided. For example, the payee may send the transaction information to the payer.

As an embodiment, a public key source may be provided. For example, the payee may send the public key source to the payer.

Referring to FIG. 3, the public key source can be encrypted by using the private key of the digital certificate to obtain a public key source encryption result.

As an embodiment, the encryption of at least one of the transaction information and the public key source may be based on a request or an initiative. For example, 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.

As an embodiment, the public key source encryption result may be provided. For example, the payee may send the public key source encryption result to the payer.

As an embodiment, 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. For example, 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.

As an embodiment, the indirect providing may include providing through a transaction intermediary. For example, 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). , Transaction information, and at least one of the public key sources.

Referring to FIG. 4, 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.

As an embodiment, before decrypting the transaction information encryption result, the transaction information encryption result may be received. For example, 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.

As an embodiment, the transaction information may be received. For example, 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.

Referring to FIG. 5, 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. For example, 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.

As an embodiment, 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. For example, 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.

Referring to FIG. 6, 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.

As an embodiment, before decrypting the public key source encryption result, the public key source encryption result may be received. For example, 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.

As an embodiment, the public key source may be received. For example, 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.

As an embodiment, the public key may be obtained according to the received public key source. For example, the payer may obtain (eg, download) the public key from the public key source by receiving, actively requesting, or the like.

Referring to FIG. 7, 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. For example, 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.

As an embodiment, 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 When there is consistency between the public key sources, the verification is confirmed. For example, 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. When the source of the public key decrypted by the party is the same, it is confirmed that the verification passes.

As an embodiment, the payment operation may include paying digital currency.

As an embodiment, 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. For example, 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.

As an embodiment, 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. For example, 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.

As an embodiment, the indirect receiving may include receiving through a transaction intermediary. For example, 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.

As an embodiment, 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.

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).

As an embodiment, the public key source may include a Uniform Resource Locator (URL) of an HTTPS website.

As an embodiment, the digital currency may be a cryptocurrency.

Referring to FIG. 8, 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).

Referring to FIG. 9, 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.

Referring to FIG. 10, the device 10 may further include a data interface 30, configured to provide an encryption result of the transaction information. For example, 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. For example, 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. For example, the data interface 30 may send the public key source to the payer.

Referring to FIG. 11, 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.

As an embodiment, 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.

Referring to FIG. 12, the data interface 30 may be configured to provide the public key source encryption result. For example, the data interface 30 may send the public key source encryption result to the payer.

As an embodiment, 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. For example, 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.

As an embodiment, 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. For example, 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.

Referring to FIG. 13, 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.

Referring to FIG. 14, the apparatus 10 may include a data interface 50 for receiving the transaction information encryption result before decrypting the transaction information encryption result. For example, 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.

As an embodiment, the data interface 50 may be configured to receive the transaction information. For example, 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.

Referring to FIG. 15, 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. For example, 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.

As an embodiment, 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.

Referring to FIG. 16, 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.

Referring to FIG. 17, the data interface 50 may be configured to: before decrypting the public key source encryption result, receive the public key source encryption result. For example, 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.

As an embodiment, the data interface 50 may be configured to receive the public key source. For example, 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.

As an embodiment, the data interface 50 may be configured to obtain the public key according to the received public key source. For example, the data interface 50 may obtain (for example, download) the public key from the public key source by receiving, actively requesting, or the like.

Referring to FIG. 18, 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. For example, 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.

As an embodiment, 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.

As shown in FIG. 19, the device 10 may include a payment module 70 for performing a payment operation according to a trigger of the verification module 60.

As an embodiment, the payment module 70 may be configured to pay digital currency.

As an embodiment, 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.

As an embodiment, 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. For example, 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.

As an embodiment, 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. For example, 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.

As an embodiment, 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.

As an embodiment, the public key source may include a URL of an HTTPS website.

As an embodiment, 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 (for example, the encryption result of the transaction information, the encryption result of the public key source, the transaction information, and the source of the public key, etc.) 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. When the program instructions are executed by a computer, 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.

In addition, the 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. In addition, 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.

No matter which aspect, for example, method aspect, device aspect, etc., 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.

As an embodiment, 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, and the data processing device may be a digital certificate processing device.

In addition, when the digital certificate is related to or embodied as digital currency, 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.

When used in this application, although the terms "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. For example, without changing the meaning of the description, 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 words used in this application are used to describe embodiments only and not to limit the claims. As used in the description of the embodiments and claims, the singular forms "a" (a), "an" and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise . Similarly, the term "and / or" as used in this application means any and all possible combinations containing one or more of the associated listings. In addition, the terms "comprise" and variations thereof "comprises" and / or "comprising" when used in this application refer to stated features, wholes, steps, operations, elements, and / or The presence of components does not exclude the presence or addition of one or more other features, wholes, steps, operations, elements, components, and / or groups of these.

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.

The above technical description can be referred to the accompanying drawings, which form a part of the present application, and show in the drawings an implementation according to the described embodiments. Although the embodiments are described in sufficient detail to enable those skilled in the art to implement the embodiments, the embodiments are non-limiting; thus, other embodiments can be used without departing from the scope of the described embodiments. Situations can also make changes. For example, the order of operations described in the flowchart is non-limiting, so the order of two or more operations explained in the flowchart and described according to the flowchart can be changed according to several embodiments. As another example, in several embodiments, one or more operations illustrated in the flowchart and described in accordance with the flowchart are optional or deleteable. In addition, certain steps or functions may be added to the disclosed embodiments, or two or more steps may be sequentially replaced. All of these variations are considered to be included in the disclosed embodiments and the claims.

In addition, terminology is used in the foregoing technical description to provide a thorough understanding of the described embodiments. However, too detailed details are not required to implement the described embodiments. Therefore, the foregoing description of the embodiments has been presented for the purposes of illustration and description. The embodiments presented in the above description and the examples disclosed based on these embodiments are provided separately to add context and help to understand the described embodiments. The above description is not intended to be exhaustive or to limit the described embodiments to the precise form of the disclosure. Based on the above teachings, several modifications, alternatives, and variations are possible. In some cases, well-known process steps have not been described in detail to avoid unnecessarily affecting the described embodiments.

Claims (39)

A method for realizing transaction information verification, which comprises: using digital certificates to implement verification of transaction information. The method according to claim 1, wherein the verifying the transaction information by using a digital certificate comprises: encrypting the transaction information by using a private key of the digital certificate to obtain a transaction information encryption result. The method according to claim 2, further comprising: providing an encrypted result of the transaction information. The method according to claim 2 or 3, further comprising: providing the transaction information. The method according to claim 4, further comprising: providing a public key source. The method according to claim 5, further comprising: using a private key of the digital certificate to encrypt the public key source to obtain a public key source encryption result. The method according to claim 6, further comprising: providing an encryption result of the public key source. The method according to claim 1, wherein the verifying the transaction information by using a digital certificate comprises: decrypting a transaction information encryption result obtained by encrypting the transaction information using a public key of the digital certificate to obtain The transaction information. The method according to claim 8, before decrypting the transaction information encryption result, further comprising: receiving the transaction information encryption result. The method according to claim 8 or 9, further comprising: receiving the transaction information. The method according to claim 10, further comprising: using the received transaction information and the decrypted transaction information for verification, and triggering a payment operation after the verification is passed. The method according to claim 11, further comprising: using 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 method according to claim 12, further comprising: receiving the public key source encryption result before decrypting the public key source encryption result. The method according to claim 12 or 13, further comprising: receiving the public key source. The method according to claim 14, further comprising: obtaining the public key according to the received public key source. The method according to claim 14, further comprising: using the received public key source and the decrypted public key source for verification, and triggering a payment operation after the verification is passed. The method according to claim 1 or 8, wherein: The digital certificate includes a Hypertext Security Transfer Protocol (HTTPS) certificate; The transaction information includes at least one of a transaction address and a transaction amount. The method according to claim 5 or 12, wherein the public key source comprises a Uniform Resource Locator (URL) of an HTTPS website. A device for verifying transaction information is characterized in that it is used for: verifying transaction information by using a digital certificate. The device according to claim 19, wherein the device comprises an encryption module, configured to: use the private key of the digital certificate to encrypt the transaction information to obtain a transaction information encryption result. The device according to claim 20, further comprising a data interface, configured to provide an encrypted result of the transaction information. The device according to claim 21, wherein the data interface is further configured to provide the transaction information. The device according to claim 22, wherein the data interface is further configured to provide a public key source. The device according to claim 23, wherein the encryption module is further 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 device according to claim 24, wherein the data interface is further configured to: provide the public key source encryption result. The device according to claim 19, wherein the device comprises a decryption module, configured to: use a public key of the digital certificate to decrypt a transaction information encryption result obtained after the transaction information is encrypted to obtain the Trading Information. The device according to claim 26, further comprising a data interface, configured to: before decrypting the transaction information encryption result, receive the transaction information encryption result. The device according to claim 27, wherein the data interface is further configured to: receive the transaction information. The device according to claim 28, further comprising a verification module, 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 device according to claim 29, wherein the decryption module is further 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 device according to claim 30, wherein the data interface is further configured to: before decrypting the public key source encryption result, receive the public key source encryption result. The apparatus according to claim 30 or 31, wherein the data interface is further configured to: receive the public key source. The device according to claim 32, wherein the data interface is further configured to obtain the public key according to the received public key source. The device according to claim 32, wherein the verification module is further configured to perform verification using the received public key source and the decrypted public key source, and trigger a payment operation after the verification is passed. The device according to claim 29 or 34, further comprising a payment module, configured to perform a payment operation according to a trigger of the verification module. The device according to claim 19 or 26, wherein: The digital certificate includes an HTTPS certificate; The transaction information includes at least one of a transaction address and a transaction amount. The device according to claim 23 or 30, wherein the public key source includes a URL of an HTTPS website. An electronic device, comprising: At least one processor; and 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 any one of claims 1-7, 17-18 Or the method according to any one of claims 1, 8-18. A server, comprising the device according to any one of claims 19-25, 36-37 or any one of claims 19, 26-37.

Images