CN108230006B - Ticket management method and server - Google Patents
Ticket management method and server Download PDFInfo
- Publication number
- CN108230006B CN108230006B CN201710010435.8A CN201710010435A CN108230006B CN 108230006 B CN108230006 B CN 108230006B CN 201710010435 A CN201710010435 A CN 201710010435A CN 108230006 B CN108230006 B CN 108230006B
- Authority
- CN
- China
- Prior art keywords
- ticket
- information
- verification
- key
- dealer
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
- 238000007726 management method Methods 0.000 title claims abstract description 25
- 238000012795 verification Methods 0.000 claims abstract description 129
- 238000012550 audit Methods 0.000 claims description 16
- 238000010200 validation analysis Methods 0.000 claims description 2
- 238000000034 method Methods 0.000 claims 7
- 239000003999 initiator Substances 0.000 description 2
- 238000013474 audit trail Methods 0.000 description 1
- 230000002349 favourable effect Effects 0.000 description 1
- 235000012054 meals Nutrition 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q30/00—Commerce
- G06Q30/02—Marketing; Price estimation or determination; Fundraising
- G06Q30/0207—Discounts or incentives, e.g. coupons or rebates
- G06Q30/0211—Determining the effectiveness of discounts or incentives
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q40/00—Finance; Insurance; Tax strategies; Processing of corporate or income taxes
- G06Q40/02—Banking, e.g. interest calculation or account maintenance
Landscapes
- Business, Economics & Management (AREA)
- Accounting & Taxation (AREA)
- Finance (AREA)
- Engineering & Computer Science (AREA)
- Strategic Management (AREA)
- Development Economics (AREA)
- Theoretical Computer Science (AREA)
- Marketing (AREA)
- Physics & Mathematics (AREA)
- General Business, Economics & Management (AREA)
- General Physics & Mathematics (AREA)
- Economics (AREA)
- Technology Law (AREA)
- Entrepreneurship & Innovation (AREA)
- Game Theory and Decision Science (AREA)
- Financial Or Insurance-Related Operations Such As Payment And Settlement (AREA)
- Management, Administration, Business Operations System, And Electronic Commerce (AREA)
Abstract
A ticket management method and a server. The ticket management method comprises the following steps: the manager provides a first portion of the first verification information to the ticket dealer, and performs an encryption operation on the first verification information with the first key to generate a first ticket voucher. Then, when the ticket trader receives the transaction request and a second ticket voucher accompanying the transaction request, the ticket trader executes decryption operation on the second ticket voucher by using a second key corresponding to the first key to obtain second cancel information. When the ticket dealer judges that the second verification information comprises the first part of verification information, the ticket dealer confirms that the second ticket voucher is equal to the first ticket voucher, agrees to the transaction request, and requests the manager for money corresponding to the first verification information according to the second ticket voucher. The manager gives money corresponding to the first approval-cancellation information to the ticket dealer.
Description
Technical Field
The present invention relates to a ticket management method, and more particularly, to a ticket management method with a secure transaction mechanism.
Background
In recent years, a consumption pattern of group purchase has been prevalent, and group purchase refers to a purchase initiated by a consumer, inviting other consumers to purchase the same product, and after the number of people is reached, the initiator orders the product to a store and wins a favorable price. With the development of online shopping, manufacturers develop a group-buying platform combining online space and group-buying concepts, so that the manufacturers can replace the role of the initiator to strive for preferential prices for various merchants, and consumers can buy goods at the preferential prices directly from the group-buying platform without inviting other consumers to buy the goods together. The group buying platform is a bulk of ticket traders selling tickets corresponding to commodities, such as meal tickets, movie tickets, lodging tickets and the like, and consumers can sell the tickets to the merchants to redeem the corresponding commodities after the tickets are purchased by the ticket traders.
The operation mode of the ticket dealer is: the consumer purchases the ticket from the ticket merchant and pays the fee to the trusted bank, and the ticket merchant provides the ticket to the consumer and requests payment from the trusted bank after the consumer checks and sells the ticket to the merchant. However, in the above operation mode, since the ticket seller generates the ticket proof, verifies the verification information and requests the bank to pay, the ticket seller can request the bank to pay before the consumer verifies the ticket, which results in the condition that the trust item is empty.
Disclosure of Invention
The invention provides a ticket management method and a server, which are used for establishing an encrypted secure transaction mechanism among a consumer, a ticket merchant and a trust server.
According to an embodiment of the invention, a ticket management method comprises the steps of: the manager provides a first part of verification information of the first verification information to the ticket dealer, and the manager performs encryption operation on the first verification information by using the first key to generate a first ticket voucher; when the ticket dealer receives the transaction request and a second ticket voucher accompanying the transaction request, the ticket dealer performs decryption operation on the second ticket voucher by using a second key corresponding to the first key to obtain second cancel information; when the ticket dealer judges that the second verification information comprises the first part of verification information, the ticket dealer confirms that the second ticket voucher is equal to the first ticket voucher, agrees to the transaction request, and requests the manager for money corresponding to the first verification information according to the second ticket voucher; and the manager gives a money corresponding to the first approval-cancellation information to the ticket dealer.
The server according to an embodiment of the present invention includes a ticket issuing unit, an encryption unit, and a verification unit. The ticket issuing unit is used for providing a first part of verification and cancellation information of the first verification and cancellation information to a ticket dealer, and the encryption unit is used for performing encryption operation on the first verification and cancellation information by using a first key to generate a first ticket voucher. When the verification unit receives a money request message from the ticket dealer, whether the money request message is related to the first ticket voucher is judged so as to pay money corresponding to the first verification information to the ticket dealer.
With the above structure, the ticket management method and the server disclosed by the application provide a ticket proof for a consumer in two ways, and provide a ticket seller with verification and cancellation information corresponding to the ticket proof. Therefore, the ticket merchant can only request money from the server of the trusted bank according to the ticket voucher provided by the consumer, and the possibility of emptying the trusted bank caused by the fact that the ticket merchant generates the ticket voucher, verifies the verification and cancellation information and requests money from the bank in the prior art is avoided.
The foregoing description of the disclosure and the following detailed description are presented to illustrate and explain the principles and spirit of the invention and to provide further explanation of the invention as claimed.
Drawings
Fig. 1 is a server according to an embodiment of the invention.
FIG. 2 is a flowchart illustrating a ticket management method according to an embodiment of the invention.
FIG. 3 is a flowchart illustrating a ticket management method according to an embodiment of the invention.
FIG. 4 is a flowchart illustrating a ticket management method according to an embodiment of the invention.
FIG. 5 is a flowchart illustrating a ticket management method according to an embodiment of the invention.
FIG. 6 is a flowchart illustrating a ticket management method according to an embodiment of the invention.
FIG. 7 is a flowchart illustrating a ticket management method according to an embodiment of the invention.
FIG. 8 is a flowchart illustrating a ticket management method according to an embodiment of the invention.
[ notation ] to show
10 server
101 ticket issuing unit
103 encryption unit
105 authentication unit
20 consumers
30 ticket trader
40 Merchant
S201 to S205
S301 to S309
S401 to S405
S501-S505 steps
S601 to S607 Steps
S701 to S711
Steps S801 to S809
Detailed Description
The detailed features and advantages of the present invention are described in detail in the following embodiments, which are sufficient for a person skilled in the art to understand the technical contents of the present invention and to implement the present invention, and the related objects and advantages of the present invention can be easily understood by those skilled in the art from the disclosure of the present specification, claims and drawings. The following examples further illustrate the aspects of the present invention in detail, but are not intended to limit the scope of the present invention in any way.
Referring to fig. 1, fig. 1 is a server according to an embodiment of the invention. As shown in fig. 1, the server 10 includes a ticket issuing unit 101, an encryption unit 103, and a verification unit 105. Wherein the server 10 is communicatively connected to the consumer 20 and the ticket merchant 30, respectively. In one embodiment, the server 10 is a computer host, and the ticket issuing unit 101 is software or a special processor, for example, for providing the ticket dealer 30 with the first part of the first verification information. The encryption unit 103, such as software or a special processor, performs an encryption operation on the first audit information with the first key to provide the first ticket voucher to the ticket issuing unit 101. In one embodiment, the ticket issuing unit 101 provides the first ticket voucher to the consumer 20. The verification unit 105, such as software or a special processor, determines whether the request information is associated with the first ticket voucher when the server 10 receives a request message from the ticket merchant 30, so as to pay the ticket merchant 30 a money corresponding to the first approval information.
Referring to fig. 1 and 2, fig. 2 is a flowchart illustrating a ticket management method according to an embodiment of the invention. In a first embodiment, the server 10 is a server of a trusted bank cooperating with the ticket merchant 30. In step S201, when the consumer 20 purchases the ticket about the merchant 40 from the ticket merchant 30, the encryption unit 103 of the server 10 generates the first verification information and generates the server public key and the server private key corresponding to each other. Next, in step S203, the encryption unit 103 encrypts the first verification information with the server private key to generate a first ticket credential. In step S205, the ticket issuing unit 101 of the server 102 provides the first audit information and the server public key to the ticket seller 30, and provides the first ticket voucher to the consumer 20.
Referring to fig. 1 and fig. 3, fig. 3 is a flowchart illustrating a ticket management method according to an embodiment of the invention. In a first embodiment, when the consumer 20 wishes to audit the ticket with the merchant 40, the consumer 20 provides a second ticket voucher to the merchant 40, and the merchant 40 transmits a transaction request and the second ticket voucher to the ticket dealer 30. In steps S301 to S305, when the ticket dealer 30 receives the transaction request and the second ticket voucher, the ticket dealer 30 decrypts the second ticket voucher with the server public key to obtain the second verification and cancellation information, and determines whether the second verification and cancellation information is equal to the first verification and cancellation information. In step S307, when the ticket dealer 30 determines that the second verification information is equal to the first verification information, that is, the second ticket voucher is equal to the first ticket voucher, the ticket dealer 30 will approve the transaction request and transmit the verification result to the merchant 40, and the merchant 40 then verifies the ticket of the user 20. In step 309, the ticket merchant 30 requests payment from the server 10 corresponding to the first audit trail information with the second ticket voucher. Then, when the server 10 receives the money requesting information of the ticket dealer 30, that is, the second ticket voucher, the verification unit 105 of the server 10 determines whether the second ticket voucher is equal to the first ticket voucher, and when the second ticket voucher is equal to the first ticket voucher, the verification unit 105 pays the ticket dealer 30 with money corresponding to the first verification and cancellation information. In step S307', when the ticket dealer 30 determines that the second verification information is not equal to the first verification information, that is, the second ticket voucher is different from the first ticket voucher, the ticket dealer 30 rejects the transaction request and returns the verification result to the merchant 40, so that the merchant 40 can know that the consumer 20 provides the wrong ticket voucher.
In a second embodiment, please refer to fig. 1 and 4, fig. 4 is a flowchart illustrating a ticket management method according to an embodiment of the invention. The server 10 is the server of a trusted bank cooperating with the ticket merchant 30, the ticket merchant 30 providing the server 10 with a ticket merchant public key. In step S401, when the consumer 20 purchases the ticket with respect to the merchant 40 from the ticket merchant 30, the encryption unit 103 of the server 10 generates the first verification information including the first verification information and the verification code. Next, in step S403, the encryption unit 103 encrypts the first verification information with the ticket merchant public key to generate a first ticket voucher. In step S405, the ticket issuing unit 101 of the server 102 provides the first partial verification information to the ticket merchant 30 and provides the first ticket voucher to the consumer 20.
Referring to fig. 1 and 5, fig. 5 is a flowchart illustrating a ticket management method according to an embodiment of the invention. In a second embodiment, when the consumer 20 wishes to audit the ticket with the merchant 40, the consumer 20 provides a second ticket voucher to the merchant 40, and the merchant 40 transmits a transaction request and the second ticket voucher to the ticket dealer 30. In steps S501 to S505, when the ticket dealer 30 receives the transaction request and the second ticket voucher, the ticket dealer 30 decrypts the second ticket voucher with the ticket dealer private key corresponding to the ticket dealer public key provided to the server 10 to obtain the second verification information, and determines whether the second verification information includes the first part of the verification information. In step S507, when the ticket dealer 30 determines that the second verification information includes the first part of the verification information, that is, the second ticket voucher is equal to the first ticket voucher, the ticket dealer 30 will approve the transaction request and transmit the verification result to the merchant 40, and the merchant 40 then verifies the ticket of the user 20. In step S509, the ticket seller 30 obtains the verification code according to the first verification information and the second verification information. In step S511, the ticket trader 30 requests money corresponding to the first approval/cancellation information from the server 10 with the validation code. Next, when the server 10 receives the money requesting information of the ticket dealer 30, i.e. the verification code, the verification unit 105 of the server 10 determines whether the verification code provided by the ticket dealer 30 is equal to the verification code in the first ticket voucher, and when the verification unit 105 determines that the two verification codes are equal, pays the money corresponding to the first verification information to the ticket dealer 30. In step S407', when the ticket dealer 30 determines that the second verification information does not include the first part of the verification information, that is, the second ticket voucher is different from the first ticket voucher, the ticket dealer 30 rejects the transaction request and returns the verification result to the merchant 40, so that the merchant 40 can know that the consumer 20 provides the wrong ticket voucher.
In a third embodiment, please refer to fig. 1 and 6, fig. 6 is a flowchart illustrating a ticket management method according to an embodiment of the invention. The server 10 is the server of a trusted bank cooperating with the ticket merchant 30, the ticket merchant 30 providing the server 10 with a ticket merchant public key. In step S601, when the consumer 20 purchases the ticket about the merchant 40 from the ticket merchant 30, the encryption unit 103 of the server 10 generates the first verification information and generates the server public key and the server private key corresponding to each other. Next, in step S603, the encryption unit 103 encrypts the first cancel verification information with the server private key to generate a first digital signature. In step S605, the encryption unit 103 encrypts the first digital signature with the ticket provider public key to generate the first ticket certificate. In step S607, the ticket issuing unit 101 provides the first audit information and the server public key to the ticket merchant 30 and provides the first ticket voucher to the consumer 20.
Referring to fig. 1 and 7, fig. 7 is a flowchart illustrating a ticket management method according to an embodiment of the invention. In a third embodiment, when the consumer 20 wishes to audit the ticket with the merchant 40, the consumer 20 provides a second ticket voucher to the merchant 40, and the merchant 40 transmits a transaction request and the second ticket voucher to the ticket dealer 30. In steps S701 to S705, when the ticket dealer 30 receives the transaction request and the second ticket voucher, the ticket dealer 30 decrypts the second ticket voucher to obtain the second digital signature by using the ticket dealer private key corresponding to the ticket dealer public key provided to the server 10, and then decrypts the second digital signature by using the server public key to obtain the second verification and cancellation information. In step S707, the ticket quotient 30 determines whether the second verification information is equal to the first verification information. In step S709, when the ticket dealer 30 determines that the second cancel verification information is equal to the first cancel verification information, that is, the second digital signature is equal to the first digital signature. The ticket dealer 30 will agree to the transaction request and return the verification result to the merchant 40, and the merchant 40 will then reimburse the ticket from the user 20. In step S711, the ticket trader 30 requests money corresponding to the first approval/cancellation information from the server 10 with the second digital signature. Next, when the server 10 receives the information of the request of the ticket dealer 30, i.e., the second digital signature, the verification unit 105 of the server 10 determines whether the second digital signature is equal to the first digital signature in the first ticket certificate. When the verification unit 105 determines that the second digital signature is equal to the first digital signature, money corresponding to the first approval/cancellation information is paid to the ticket seller 30. In step S709', when the ticket dealer 30 determines that the second verification information is not equal to the first verification information, the ticket dealer 30 rejects the transaction request and returns the verification result to the merchant 40, so that the merchant 40 can know that the consumer 20 provides the wrong ticket voucher.
Referring to fig. 1 and 8, fig. 8 is a flowchart illustrating a ticket management method according to an embodiment of the invention. In step S801, an administrator, for example, the server 10, provides the ticket dealer 30 with the first part of the first approval/disapproval information. In the foregoing first embodiment, the first part of the verification information is the first verification information. In the second embodiment, the first verification information includes the first verification information and the verification code, and the server 10 provides only the first verification information to the ticket seller 30. In the third embodiment, the first part of the cancel verification information is the first cancel verification information.
In step S803, the server 10 encrypts the first audit information with the first key to generate the first ticket certificate. In the first embodiment, the first key is a server private key of the server 10, and the server 10 encrypts the first verification information with the server private key to generate the first ticket voucher and provides the first ticket voucher to the consumer 20. In the second embodiment, the first key is the ticket dealer public key, and the server 10 encrypts the first verification information with the ticket dealer public key to generate the first ticket voucher, and provides the first ticket voucher to the consumer 20. In a third embodiment, the first key comprises a server private key and a ticket merchant public key, the server 10 encrypts the first verification information with the server private key to generate a first digital signature, encrypts the first digital signature with the ticket merchant public key to generate a first ticket certificate, and provides the first ticket certificate to the consumer 20.
In step S805, when the ticket dealer 30 receives the transaction request and the second ticket voucher associated with the transaction request, the ticket dealer 30 performs a decryption operation on the second ticket voucher with a second key corresponding to the first key to obtain second cancel information. In the first embodiment, the second key is the server public key corresponding to the server private key, and when the ticket dealer 30 receives the transaction request and the second ticket voucher from the consumer 20, the ticket dealer 30 decrypts the second ticket voucher with the server public key to obtain the second verification information. In the second embodiment, the second key is a ticket dealer private key corresponding to the ticket dealer public key, and when the ticket dealer 30 receives the transaction request and the second ticket voucher from the consumer 20, the ticket dealer 30 decrypts the second ticket voucher with the ticket dealer private key to obtain the second verification and cancellation information. In the third embodiment, the second key comprises the server public key and the ticket dealer private key, when the ticket dealer 30 receives the transaction request and the second ticket certificate from the consumer 20, the ticket dealer 30 decrypts the second ticket certificate with the private key to obtain the second digital signature, and then decrypts the second digital signature to obtain the second verification information.
In step S807, when the ticket dealer 30 determines that the second verification information includes the first part of the verification information, it confirms that the second ticket voucher is equal to the first ticket voucher, approves the transaction request, and requests the server 10 for payment corresponding to the first verification information according to the second ticket voucher. In the first embodiment, when the ticket dealer 30 determines that the second verification information includes the first part of the verification information, i.e., the second verification information is equal to the first verification information, it is confirmed that the second ticket voucher from the consumer 20 is equal to the first ticket voucher provided by the server 10, so that the ticket dealer 30 approves the transaction request and requests money from the server 10 with the second ticket voucher. In the second embodiment, when the ticket dealer 30 determines that the second verification information includes the first part of verification information, the second ticket voucher is determined to be equal to the first ticket voucher, the transaction request is granted, the verification code is obtained according to the second verification information corresponding to the second ticket voucher and the first part of verification information, and the payment is requested from the server 10 by the verification code. In the third embodiment, when the ticket dealer 30 determines that the second verification information is equal to the first verification information, it is determined that the second ticket voucher is equal to the first ticket voucher, so that the ticket dealer 30 approves the transaction request, and requests money from the server 10 with the second digital signature obtained according to the second ticket voucher in step S805.
In step S809, the server 10 pays the ticket dealer 30 a money corresponding to the first approval-and-cancellation information. When the server 10 receives the information of the payment request from the ticket dealer 30, i.e., the second ticket voucher, the verification code, or the second digital signature obtained according to the second ticket voucher, and the server 10 determines that the information of the payment request is associated with the first ticket voucher, the payment corresponding to the first verification information is given to the ticket dealer 30.
It should be noted that, in the above embodiment, although the consumer 20 obtains the first ticket proof from the ticket issuing unit 101, when the consumer 20 wants to check the ticket against the merchant 40, the merchant 40 and the ticket merchant 30 first consider the ticket proof provided by the consumer 20 as the second ticket proof, then verify the second ticket proof, and determine whether it is equal to the first ticket proof, so as to confirm that the ticket proof provided by the consumer 20 corresponds to the ticket purchased by the consumer to the ticket merchant 30 and related to the merchant 40.
With the above structure, the ticket management method and the server disclosed by the application provide a ticket proof for a consumer in two ways, and provide a verification and cancellation information corresponding to the ticket proof for a ticket merchant. Therefore, the ticket merchant can only request money from the server according to the ticket voucher provided by the consumer, and the possibility of emptying the trust due to the fact that the ticket merchant generates the ticket voucher, verifies the verification and cancellation information and requests money from the bank in the prior art is avoided.
Claims (16)
1. A ticket management method, comprising:
the manager only provides a first part of the verification information of the first verification information to the ticket dealer;
the administrator uses the first key to perform encryption operation on the first verification and cancellation information to generate a first ticket certificate;
when the ticket trader receives a trading request and a second ticket voucher accompanying the trading request, the ticket trader executes decryption operation on the second ticket voucher by a second key corresponding to the first key to obtain second verification and cancellation information;
when the ticket trader judges that the second verification information comprises the first part of verification information, the second ticket voucher is confirmed to be equal to the first ticket voucher, the transaction request is agreed, and money corresponding to the first verification information is requested to the manager according to the second ticket voucher; and
the manager pays the money corresponding to the first verification and cancellation information to the ticket seller.
2. The method of claim 1, wherein the first key is a private key of the administrator and the second key is a public key of the administrator.
3. The method as in claim 1, wherein the first audit information is equal to the first portion audit information and the second ticket voucher is provided to the administrator at the step of requesting the money corresponding to the first audit information from the administrator based on the second ticket voucher.
4. The method of claim 1, wherein said first key is a public key of said ticket dealer and said second key is a private key of said ticket dealer.
5. The method as claimed in claim 4, wherein the first audit information comprises the first partial audit information and a validation code, and the step of requesting the money corresponding to the first audit information from the administrator according to the second ticket voucher comprises:
obtaining the verification code according to the first part of the verification information and the second verification information obtained by performing the decryption operation on the second ticket voucher; and
the passcode is provided to the manager to request the payment.
6. The method of claim 1, wherein said first key comprises a first public key of said ticket dealer and a second private key of said administrator, and said second key comprises a second public key of said administrator and a first private key of said ticket dealer.
7. The method according to claim 6, wherein the step of the administrator performing the encryption operation on the first audit information with the first key to generate the first ticket voucher comprises:
performing the encryption operation on the first verification information by using the second private key to generate a first digital signature; and
the first public key is used for performing the encryption operation on the first digital signature to generate the first ticket certificate.
8. The method of claim 7, wherein the step of performing the decryption operation on the second ticket voucher with the second key to obtain the second revocation information comprises:
performing the decryption operation on the second ticket voucher with the first private key to obtain a second digital signature; and
executing the decryption operation on the second digital signature by using the second public key to obtain second cancel verification information;
wherein the second digital signature is provided to the administrator at the step of requesting the funds corresponding to the first audit information from the administrator based on the second ticket voucher.
9. A server, comprising:
the ticket issuing unit is used for providing only a first part of verification and cancellation information of the first verification and cancellation information to a ticket dealer;
an encryption unit for performing an encryption operation on the first verification and cancellation information by using a first key to generate a first ticket certificate; and
and the verification unit is used for judging whether the debit information is related to the first ticket voucher or not when receiving the debit information from the ticket dealer so as to pay money corresponding to the first verification information to the ticket dealer.
10. The server of claim 9, wherein the first key is a private key of the server, and the ticket issuing unit further provides a public key of the server to the ticket dealer.
11. The server of claim 9, wherein the verification unit verifies whether the debit information is equal to the first ticket voucher to fund the ticket dealer corresponding to the first cancellation information.
12. The server of claim 9, wherein said first key is a public key of said ticket dealer.
13. The server according to claim 12, wherein the first approval information includes the first part of the approval information and a verification code, and the verification unit verifies whether the request information includes the verification code to pay the ticket merchant the money corresponding to the first approval information.
14. The server of claim 9, wherein said first key comprises a first public key of said ticket dealer and a second private key of said server.
15. The server according to claim 14, wherein the encryption unit performs the encryption operation on the first audit information with the second private key to generate a first digital signature, and performs the encryption operation on the first digital signature with the first public key to generate a first ticket voucher.
16. The server according to claim 15, wherein the verifying unit verifies whether the debit information is associated with the first digital signature to pay the ticket merchant the money corresponding to the first approval/disapproval information.
Applications Claiming Priority (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| TW105140804A TWI651675B (en) | 2016-12-09 | 2016-12-09 | Ticket management method and server |
| TW105140804 | 2016-12-09 |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN108230006A CN108230006A (en) | 2018-06-29 |
| CN108230006B true CN108230006B (en) | 2021-08-24 |
Family
ID=62657278
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201710010435.8A Active CN108230006B (en) | 2016-12-09 | 2017-01-06 | Ticket management method and server |
Country Status (2)
| Country | Link |
|---|---|
| CN (1) | CN108230006B (en) |
| TW (1) | TWI651675B (en) |
Families Citing this family (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111523961B (en) * | 2020-03-17 | 2024-03-08 | 口碑(上海)信息技术有限公司 | Resource information processing method, client and server |
Citations (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| TW200943892A (en) * | 2008-04-08 | 2009-10-16 | Univ Chaoyang Technology | Mobile ticket system based on mobile device |
| CN102509141A (en) * | 2011-10-31 | 2012-06-20 | 广东商学院 | Electronic group-buying coupon and usage and system of electronic group-buying coupon |
| CN102930603A (en) * | 2012-09-25 | 2013-02-13 | 捷达威数位科技股份有限公司 | Ticketing system and method thereof |
| CN103093375A (en) * | 2012-12-31 | 2013-05-08 | 邬国锐 | Electronic coupon processing system and method |
| CN103136672A (en) * | 2011-11-30 | 2013-06-05 | 中国联合网络通信集团有限公司 | Group buying information transmission method and group buying system |
| CN104881698A (en) * | 2015-05-28 | 2015-09-02 | 程序 | Two dimensional code generation and verification method |
| CN104951958A (en) * | 2015-05-18 | 2015-09-30 | 深圳再来信息技术有限公司 | Cancel-after-verification system and method for electronic certificates |
| CN105528717A (en) * | 2015-12-25 | 2016-04-27 | 吴伟荣 | Generating and using equipment of coupons and using method thereof |
| CN105745678A (en) * | 2013-09-20 | 2016-07-06 | 维萨国际服务协会 | Secure remote payment transaction processing including consumer authentication |
Family Cites Families (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US8225089B2 (en) * | 1996-12-04 | 2012-07-17 | Otomaku Properties Ltd., L.L.C. | Electronic transaction systems utilizing a PEAD and a private key |
| FR2887050B1 (en) * | 2005-06-14 | 2007-10-05 | Viaccess Sa | METHOD AND SYSTEM FOR SECURING A TRANSACTION IN A TELECOMMUNICATION NETWORK |
| JP2008003987A (en) * | 2006-06-26 | 2008-01-10 | Economize Co Ltd | Premium ticket trading system, premium ticket trading method, premium ticket trading program and storage medium |
| US20120101951A1 (en) * | 2010-10-22 | 2012-04-26 | Michael Li | Method and System for Secure Financial Transactions Using Mobile Communications Devices |
| CN104217345A (en) * | 2013-05-29 | 2014-12-17 | 芝贝利有限公司 | Realizing method and system for electronic discount coupons |
| TW201504964A (en) * | 2013-07-23 | 2015-02-01 | Yi-Li Huang | Secure mobile device shopping system and method |
| CN104021468B (en) * | 2014-07-01 | 2017-09-05 | 广州云移信息科技有限公司 | Support retail shop's intelligent management marketer terminal of Quick Response Code and one-dimension code scanning management |
| CN105956892B (en) * | 2016-04-15 | 2020-01-10 | 腾讯科技（深圳）有限公司 | Virtual bill exchange method, device and system |
| CN106022428A (en) * | 2016-05-13 | 2016-10-12 | 广州云移信息科技有限公司 | An information processing method and system based on two-dimensional codes |
-
2016
- 2016-12-09 TW TW105140804A patent/TWI651675B/en active
-
2017
- 2017-01-06 CN CN201710010435.8A patent/CN108230006B/en active Active
Patent Citations (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| TW200943892A (en) * | 2008-04-08 | 2009-10-16 | Univ Chaoyang Technology | Mobile ticket system based on mobile device |
| CN102509141A (en) * | 2011-10-31 | 2012-06-20 | 广东商学院 | Electronic group-buying coupon and usage and system of electronic group-buying coupon |
| CN103136672A (en) * | 2011-11-30 | 2013-06-05 | 中国联合网络通信集团有限公司 | Group buying information transmission method and group buying system |
| CN102930603A (en) * | 2012-09-25 | 2013-02-13 | 捷达威数位科技股份有限公司 | Ticketing system and method thereof |
| CN103093375A (en) * | 2012-12-31 | 2013-05-08 | 邬国锐 | Electronic coupon processing system and method |
| CN105745678A (en) * | 2013-09-20 | 2016-07-06 | 维萨国际服务协会 | Secure remote payment transaction processing including consumer authentication |
| CN104951958A (en) * | 2015-05-18 | 2015-09-30 | 深圳再来信息技术有限公司 | Cancel-after-verification system and method for electronic certificates |
| CN104881698A (en) * | 2015-05-28 | 2015-09-02 | 程序 | Two dimensional code generation and verification method |
| CN105528717A (en) * | 2015-12-25 | 2016-04-27 | 吴伟荣 | Generating and using equipment of coupons and using method thereof |
Also Published As
| Publication number | Publication date |
|---|---|
| TWI651675B (en) | 2019-02-21 |
| TW201822106A (en) | 2018-06-16 |
| CN108230006A (en) | 2018-06-29 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US20210350360A1 (en) | Crypto currency chargeback system | |
| US20200043009A1 (en) | Method and system for hosted order page/silent order post | |
| US20130198080A1 (en) | System and method of providing tokenization as a service | |
| WO2015183901A2 (en) | System and method for marketplace software platform | |
| KR20090045400A (en) | Method and system for processing internet purchase transactions | |
| WO2013019567A2 (en) | Passing payment tokens through an hop/sop | |
| KR20190114396A (en) | Method, apparatus and computer-readable medium for providing transaction service based on blockchain | |
| AU775065B2 (en) | Payment method and system for online commerce | |
| KR101395896B1 (en) | Settlement System and Method for trade protecting in social commerce and computer-readable recording medium with program therefor | |
| KR20220016752A (en) | Rental-pay management server and operation method thereof | |
| US10424014B2 (en) | Systems and methods for providing seller-initiated financing in private sales | |
| KR101701450B1 (en) | Method of providing authentication service for electronic commerce payment and server thereof | |
| CN108230006B (en) | Ticket management method and server | |
| JP3843093B2 (en) | Payment system | |
| WO2020154576A1 (en) | Cryptographic transactions supporting real world requirements | |
| KR100623429B1 (en) | Transaction intermediate system and method of transacting using thereof | |
| JP2001297275A (en) | Radio telephone device, store device, and method and system for clearance using these | |
| KR20220039441A (en) | Mobile Gift Certificate Operation and Management System for being able to be deducted from the balance | |
| US20210125177A1 (en) | Authentication network for transaction data | |
| KR20160028066A (en) | System and method for an used car sales | |
| KR102608806B1 (en) | Service apparatus for voucher trading and operating method thereof | |
| KR102635992B1 (en) | A service platform that provides a marketplace for trading carbon credits, and system and method for providing the same | |
| KR100767416B1 (en) | Merchandise coupon circulation method | |
| KR20000030790A (en) | Electronic Commerce Method & System with Reliability and Protection of Individual Information between Two Parties | |
| KR20060136062A (en) | System for payment using Escrow Money in electronic commerce and method thereof |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |