CN116703536A - Ticket transaction data processing method and system - Google Patents
Ticket transaction data processing method and system Download PDFInfo
- Publication number
- CN116703536A CN116703536A CN202310989340.0A CN202310989340A CN116703536A CN 116703536 A CN116703536 A CN 116703536A CN 202310989340 A CN202310989340 A CN 202310989340A CN 116703536 A CN116703536 A CN 116703536A
- Authority
- CN
- China
- Prior art keywords
- ticket
- data
- target
- transaction
- container
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
- 238000003672 processing method Methods 0.000 title claims abstract description 14
- 238000012795 verification Methods 0.000 claims abstract description 47
- 238000012545 processing Methods 0.000 claims abstract description 46
- 238000012790 confirmation Methods 0.000 claims abstract description 22
- 238000012986 modification Methods 0.000 claims abstract description 22
- 230000004048 modification Effects 0.000 claims abstract description 22
- 238000000034 method Methods 0.000 claims abstract description 14
- 238000004891 communication Methods 0.000 claims description 12
- 238000002955 isolation Methods 0.000 abstract 1
- 238000011161 development Methods 0.000 description 2
- 230000006399 behavior Effects 0.000 description 1
- 230000009286 beneficial effect Effects 0.000 description 1
- 238000012937 correction Methods 0.000 description 1
- 238000007405 data analysis Methods 0.000 description 1
- 230000007547 defect Effects 0.000 description 1
- 238000010586 diagram Methods 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
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/06—Buying, selling or leasing transactions
- G06Q30/0601—Electronic shopping [e-shopping]
- G06Q30/0633—Lists, e.g. purchase orders, compilation or processing
- G06Q30/0635—Processing of requisition or of purchase orders
- G06Q30/0637—Approvals
Landscapes
- Business, Economics & Management (AREA)
- Accounting & Taxation (AREA)
- Finance (AREA)
- Development Economics (AREA)
- Economics (AREA)
- Marketing (AREA)
- Strategic Management (AREA)
- Physics & Mathematics (AREA)
- General Business, Economics & Management (AREA)
- General Physics & Mathematics (AREA)
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Management, Administration, Business Operations System, And Electronic Commerce (AREA)
Abstract
The invention relates to the field of data processing, and discloses a ticket transaction data processing method and system, wherein the method comprises the following steps: the ticket data server generates a ticket target data container according to the ticket target, generates a ticket target information list according to ticket target information, and sends the ticket target information list to the ticket target data container; and the ticket data isolation processing module is used for verifying the transaction information through the information verification module if the verification is passed and returning the transaction confirmation information to the ticket target data container if the verification is not passed according to the request data transmitted by the ticket service terminal, and the ticket target data container is used for carrying out modification confirmation and identity information completion on the ticket target information list to complete the ticket target information list modification and complete ticket transaction data processing. By the method and the device, invalid high-concurrency transaction request data is avoided, and the safe processing of ticket data is ensured.
Description
Technical Field
The invention relates to the field of data processing, in particular to a ticket business transaction data processing method and system.
Background
With the continuous development of society, ticket business has become one of the common behaviors in people's lives. The rapid development of electronic commerce and internet technology makes ticket transactions more and more convenient and efficient. However, conventional ticketing transactions still have some problems and challenges, such as: large-scale transaction data processing: with the popularization of the internet, ticketing platforms face a large number of users and transactions, and huge transaction data including order information, payment records, refund requests and the like need to be processed. Data security and privacy: the transaction data relates to personal information and payment information of users, and data security needs to be ensured to prevent data leakage and illegal access. Data analysis and decision support: the ticket business data contains rich information, and the ticket business platform can be helped to perform optimal operation, formulate accurate marketing strategies and the like by analyzing the data. Transaction instantaneity requirements: for ticketing transactions for thermal shows or events, users often want to be able to purchase tickets in real time, thus requiring handling highly concurrent transaction requests.
Thus, high concurrency transaction requests are completed while ensuring secure processing of ticket data.
Disclosure of Invention
The invention aims to overcome the defects of the prior art and provides a ticket business transaction data processing method, which comprises the following steps:
firstly, a ticket data server generates a ticket target data container according to ticket targets, generates a ticket target information list according to ticket target information, and sends the ticket target information list to the ticket target data container;
step two, the isolated ticket data processing module judges the type of ticket data service according to the request data transmitted by the ticket service terminal, if the ticket data is the ticket data inquiry service, the step six is entered, and if the ticket data is the ticket transaction service, the step three is entered;
step three, the request information verification module in the isolated ticket data processing module performs repeated verification on the request data transmitted by the ticket service terminal, if the verification is passed, the ticket target in the request data transmitted by the ticket service terminal is obtained, the ticket transaction module in the isolated ticket data processing module generates a ticket transaction sub-container corresponding to the ticket service terminal, and the request data is written into the ticket transaction sub-container corresponding to the ticket service terminal to enter step four; if the verification is not passed, returning prompt information to the ticket service terminal;
step four, the isolated ticket data processing module is in communication connection with the ticket target data container according to ticket targets of the request data in the ticket transaction sub-container corresponding to the ticket service terminal, the ticket target data container correspondingly modifies the ticket target information list according to the ticket target transaction data in the request data, if the ticket target information list is in a modifiable state, the ticket target information list enters a state to be confirmed, and returns the tradable information to the ticket transaction sub-container, and the step five is entered; if the state is in an unmodified state, returning the information of reaching the upper limit of the transaction to a ticket transaction sub-container, returning the ticket transaction sub-container to the corresponding ticket service terminal, closing the ticket transaction sub-container of the corresponding ticket service terminal, and entering a step seven;
step five, the ticket business sub-container verifies the transaction information through the information verification module, if the verification is passed, the transaction confirmation information is returned to the ticket business target data container, the ticket business target data container carries out modification confirmation and identity information completion on the ticket business target information list, the ticket business target information list modification is completed, and meanwhile, the ticket business sub-container corresponding to the ticket business service terminal is closed, and step seven is entered; if the ticket target data container does not receive the transaction confirmation information within the set transaction window time, the ticket target data container cancels the modification of the ticket target information list and closes the ticket transaction sub-container corresponding to the ticket service terminal;
step six, acquiring a ticket target information list through a ticket information inquiry module of the ticket target data container, and acquiring inquiry information through the ticket target information list;
and step seven, returning the ticket target information list which is in an unmodified state to the ticket data server, generating ticket information according to the ticket target information list, and finishing ticket transaction data processing.
Further, the ticket data server generates a ticket target data container according to the ticket target, and the ticket data server generates a ticket target information list according to ticket target information, including:
the ticket data server generates corresponding ticket target data containers according to different ticket targets, and generates a ticket target information list according to the number and types of the ticket targets.
Further, the request information verification module in the isolated ticket data processing module performs repeatability verification on the request data transmitted by the ticket service terminal, and the method comprises the following steps:
the isolated ticket data processing module inquires whether a ticket transaction sub-container corresponding to the ticket service terminal exists in the isolated ticket data processing module according to the information of the ticket service terminal, and if not, the verification is passed; otherwise, the verification is not passed.
Further, the ticket target data container correspondingly modifies the ticket target information list according to ticket target transaction data in the request data, and includes:
the ticket target transaction data comprise the types and the corresponding numbers of the ticket targets, and the number of the ticket target information list is correspondingly reduced according to the types and the corresponding numbers of the ticket targets.
Further, the ticket transaction sub-container verifies transaction information through the information verification module, wherein the verification comprises verification of identity information of ticket purchasing personnel and verification of payment success information, if the identity information of ticket purchasing personnel and the payment success information are both verified, the verification is passed, and otherwise, the verification is not passed.
Further, the transaction confirmation information is returned to the ticket target data container, the ticket target data container carries out modification confirmation and identity information completion on the ticket target information list, and the ticket target information list modification is completed, including:
and associating the identity information with the corresponding number of ticket target types in the ticket target information list to complete the modification confirmation of the ticket target information list.
A ticket transaction data processing system applies the ticket transaction data processing method, which comprises a ticket data server, an isolated ticket data processing module, a communication module and a ticket service terminal;
the ticket data server is connected with the isolated ticket data processing module, and the isolated ticket data processing module and the ticket service terminal are respectively connected with the communication module in a communication way.
The beneficial effects of the invention are as follows: by the technical scheme provided by the invention, the same ticket service terminal can be prevented from sending repeated data requests, invalid high-concurrency transaction request data is avoided, and the safe processing of ticket data is ensured.
Drawings
FIG. 1 is a flow chart of a ticket transaction data processing method;
FIG. 2 is a schematic diagram of a ticket transaction data processing system.
Detailed Description
The technical solution of the present invention will be described in further detail with reference to the accompanying drawings, but the scope of the present invention is not limited to the following description.
For the purpose of making the technical solution and advantages of the present invention more apparent, the present invention will be further described in detail with reference to the accompanying drawings and examples. It should be understood that the particular embodiments described herein are illustrative only and are not intended to limit the invention, i.e., the embodiments described are merely some, but not all, of the embodiments of the invention. The components of the embodiments of the present invention generally described and illustrated in the figures herein may be arranged and designed in a wide variety of different configurations.
Thus, the following detailed description of the embodiments of the invention, as presented in the figures, is not intended to limit the scope of the invention, as claimed, but is merely representative of selected embodiments of the invention. All other embodiments, which can be made by a person skilled in the art without making any inventive effort, are intended to be within the scope of the present invention. It is noted that relational terms such as "first" and "second", and the like, are used solely to distinguish one entity or action from another entity or action without necessarily requiring or implying any actual such relationship or order between such entities or actions.
Moreover, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising one … …" does not exclude the presence of other like elements in a process, method, article or apparatus that comprises the element.
The features and capabilities of the present invention are described in further detail below in connection with the examples.
As shown in fig. 1, a ticket transaction data processing method includes the following steps:
firstly, a ticket data server generates a ticket target data container according to ticket targets, generates a ticket target information list according to ticket target information, and sends the ticket target information list to the ticket target data container;
step two, the isolated ticket data processing module judges the type of ticket data service according to the request data transmitted by the ticket service terminal, if the ticket data is the ticket data inquiry service, the step six is entered, and if the ticket data is the ticket transaction service, the step three is entered;
step three, the request information verification module in the isolated ticket data processing module performs repeated verification on the request data transmitted by the ticket service terminal, if the verification is passed, the ticket target in the request data transmitted by the ticket service terminal is obtained, the ticket transaction module in the isolated ticket data processing module generates a ticket transaction sub-container corresponding to the ticket service terminal, and the request data is written into the ticket transaction sub-container corresponding to the ticket service terminal to enter step four; if the verification is not passed, returning prompt information to the ticket service terminal;
step four, the isolated ticket data processing module is in communication connection with the ticket target data container according to ticket targets of the request data in the ticket transaction sub-container corresponding to the ticket service terminal, the ticket target data container correspondingly modifies the ticket target information list according to the ticket target transaction data in the request data, if the ticket target information list is in a modifiable state, the ticket target information list enters a state to be confirmed, and returns the tradable information to the ticket transaction sub-container, and the step five is entered; if the state is in an unmodified state, returning the information of reaching the upper limit of the transaction to a ticket transaction sub-container, returning the ticket transaction sub-container to the corresponding ticket service terminal, closing the ticket transaction sub-container of the corresponding ticket service terminal, and entering a step seven;
step five, the ticket business sub-container verifies the transaction information through the information verification module, if the verification is passed, the transaction confirmation information is returned to the ticket business target data container, the ticket business target data container carries out modification confirmation and identity information completion on the ticket business target information list, the ticket business target information list modification is completed, and meanwhile, the ticket business sub-container corresponding to the ticket business service terminal is closed, and step seven is entered; if the ticket target data container does not receive the transaction confirmation information within the set transaction window time, the ticket target data container cancels the modification of the ticket target information list and closes the ticket transaction sub-container corresponding to the ticket service terminal;
step six, acquiring a ticket target information list through a ticket information inquiry module of the ticket target data container, and acquiring inquiry information through the ticket target information list;
and step seven, returning the ticket target information list which is in an unmodified state to the ticket data server, generating ticket information according to the ticket target information list, and finishing ticket transaction data processing.
The ticket data server generates a ticket target data container according to ticket targets, and generates a ticket target information list according to ticket target information, comprising:
the ticket data server generates corresponding ticket target data containers according to different ticket targets, and generates a ticket target information list according to the number and types of the ticket targets.
The request information verification module in the isolated ticket data processing module performs repeatability verification on the request data transmitted by the ticket service terminal, and the method comprises the following steps:
the isolated ticket data processing module inquires whether a ticket transaction sub-container corresponding to the ticket service terminal exists in the isolated ticket data processing module according to the information of the ticket service terminal, and if not, the verification is passed; otherwise, the verification is not passed.
The ticket target data container correspondingly modifies the ticket target information list according to ticket target transaction data in the request data, and comprises the following steps:
the ticket target transaction data comprise the types and the corresponding numbers of the ticket targets, and the number of the ticket target information list is correspondingly reduced according to the types and the corresponding numbers of the ticket targets.
The ticket transaction sub-container verifies transaction information through the information verification module, wherein the transaction information comprises identification information confirmation and payment success information confirmation of ticket purchasing personnel, if the identification information and the payment success information of the ticket purchasing personnel are confirmed, the verification is passed, and otherwise, the verification is not passed.
The transaction confirmation information is returned to the ticket target data container, the ticket target data container carries out modification confirmation and identity information completion on the ticket target information list, and the ticket target information list modification is completed, and the method comprises the following steps:
and associating the identity information with the corresponding number of ticket target types in the ticket target information list to complete the correction confirmation of the ticket target information list.
As shown in fig. 2, a ticket transaction data processing system, to which the ticket transaction data processing method is applied, includes a ticket data server, an isolated ticket data processing module, a communication module and a ticket service terminal;
the ticket data server is connected with the isolated ticket data processing module, and the isolated ticket data processing module and the ticket service terminal are respectively connected with the communication module in a communication way.
The foregoing is merely a preferred embodiment of the invention, and it is to be understood that the invention is not limited to the form disclosed herein but is not to be construed as excluding other embodiments, but is capable of numerous other combinations, modifications and environments and is capable of modifications within the scope of the inventive concept, either as taught or as a matter of routine skill or knowledge in the relevant art. And that modifications and variations which do not depart from the spirit and scope of the invention are intended to be within the scope of the appended claims.
Claims (7)
1. A ticket business data processing method is characterized by comprising the following steps:
firstly, a ticket data server generates a ticket target data container according to ticket targets, generates a ticket target information list according to ticket target information, and sends the ticket target information list to the ticket target data container;
step two, the isolated ticket data processing module judges the type of ticket data service according to the request data transmitted by the ticket service terminal, if the ticket data is the ticket data inquiry service, the step six is entered, and if the ticket data is the ticket transaction service, the step three is entered;
step three, the request information verification module in the isolated ticket data processing module performs repeated verification on the request data transmitted by the ticket service terminal, if the verification is passed, the ticket target in the request data transmitted by the ticket service terminal is obtained, the ticket transaction module in the isolated ticket data processing module generates a ticket transaction sub-container corresponding to the ticket service terminal, and the request data is written into the ticket transaction sub-container corresponding to the ticket service terminal to enter step four; if the verification is not passed, returning prompt information to the ticket service terminal;
step four, the isolated ticket data processing module is in communication connection with the ticket target data container according to ticket targets of the request data in the ticket transaction sub-container corresponding to the ticket service terminal, the ticket target data container correspondingly modifies the ticket target information list according to the ticket target transaction data in the request data, if the ticket target information list is in a modifiable state, the ticket target information list enters a state to be confirmed, and returns the tradable information to the ticket transaction sub-container, and the step five is entered; if the state is in an unmodified state, returning the information of reaching the upper limit of the transaction to a ticket transaction sub-container, returning the ticket transaction sub-container to the corresponding ticket service terminal, closing the ticket transaction sub-container of the corresponding ticket service terminal, and entering a step seven;
step five, the ticket business sub-container verifies the transaction information through the information verification module, if the verification is passed, the transaction confirmation information is returned to the ticket business target data container, the ticket business target data container carries out modification confirmation and identity information completion on the ticket business target information list, the ticket business target information list modification is completed, and meanwhile, the ticket business sub-container corresponding to the ticket business service terminal is closed, and step seven is entered; if the ticket target data container does not receive the transaction confirmation information within the set transaction window time, the ticket target data container cancels the modification of the ticket target information list and closes the ticket transaction sub-container corresponding to the ticket service terminal;
step six, acquiring a ticket target information list through a ticket information inquiry module of the ticket target data container, and acquiring inquiry information through the ticket target information list;
and step seven, returning the ticket target information list which is in an unmodified state to the ticket data server, generating ticket information according to the ticket target information list, and finishing ticket transaction data processing.
2. The ticket transaction data processing method according to claim 1, wherein the ticket data server generates a ticket target data container according to ticket targets, and the ticket data server generates a ticket target information list according to ticket target information, comprising:
the ticket data server generates corresponding ticket target data containers according to different ticket targets, and generates a ticket target information list according to the number and types of the ticket targets.
3. The ticket transaction data processing method according to claim 2, wherein the request information verification module in the isolated ticket data processing module performs repeatability verification on the request data transmitted by the ticket service terminal, and the method comprises the steps of:
the isolated ticket data processing module inquires whether a ticket transaction sub-container corresponding to the ticket service terminal exists in the isolated ticket data processing module according to the information of the ticket service terminal, and if not, the verification is passed; otherwise, the verification is not passed.
4. The ticket transaction data processing method according to claim 1, wherein the ticket target data container correspondingly modifies a ticket target information list according to ticket target transaction data in the request data, and includes:
the ticket target transaction data comprise the types and the corresponding numbers of the ticket targets, and the number of the ticket target information list is correspondingly reduced according to the types and the corresponding numbers of the ticket targets.
5. The method for processing ticket transaction data according to claim 1, wherein the ticket transaction sub-container verifies transaction information through the information verification module, including verification of identity information of ticket purchasing personnel and verification of payment success information, and if both the identity information of ticket purchasing personnel and the payment success information are verified, the verification is passed, otherwise, the verification is not passed.
6. The method of claim 5, wherein the step of returning transaction confirmation information to the ticket target data container, the ticket target data container performing modification confirmation and identity information completion on the ticket target information list to complete ticket target information list modification comprises:
and associating the identity information with the corresponding number of ticket target types in the ticket target information list to complete the modification confirmation of the ticket target information list.
7. A ticket transaction data processing system, characterized in that a ticket transaction data processing method according to any one of claims 1-6 is applied, comprising a ticket data server, an isolated ticket data processing module, a communication module and a ticket service terminal;
the ticket data server is connected with the isolated ticket data processing module, and the isolated ticket data processing module and the ticket service terminal are respectively connected with the communication module in a communication way.
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN202310989340.0A CN116703536B (en) | 2023-08-08 | 2023-08-08 | Ticket transaction data processing method and system |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN202310989340.0A CN116703536B (en) | 2023-08-08 | 2023-08-08 | Ticket transaction data processing method and system |
Publications (2)
Publication Number | Publication Date |
---|---|
CN116703536A true CN116703536A (en) | 2023-09-05 |
CN116703536B CN116703536B (en) | 2023-10-24 |
Family
ID=87836092
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
CN202310989340.0A Active CN116703536B (en) | 2023-08-08 | 2023-08-08 | Ticket transaction data processing method and system |
Country Status (1)
Country | Link |
---|---|
CN (1) | CN116703536B (en) |
Cited By (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN117707097A (en) * | 2024-02-04 | 2024-03-15 | 广州泽亨实业有限公司 | Machining center control method and system |
Citations (7)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN102214323A (en) * | 2010-04-02 | 2011-10-12 | 彭晟罡 | Background management server, mobile terminal, and ticket booking system and method |
US20190012451A1 (en) * | 2015-05-14 | 2019-01-10 | Alclear, Llc | Biometric ticketing |
CN112016994A (en) * | 2020-08-14 | 2020-12-01 | 北京首钢自动化信息技术有限公司 | Ticket management method and device, readable storage medium and electronic equipment |
CN112348974A (en) * | 2020-10-28 | 2021-02-09 | 四川瑞云信通科技有限公司 | PRT novel automatic ticket selling and checking method and system |
CN114358943A (en) * | 2022-01-12 | 2022-04-15 | 平安普惠企业管理有限公司 | Online bill processing method and device, electronic equipment and storage medium |
CN115619552A (en) * | 2022-09-29 | 2023-01-17 | 中国建设银行股份有限公司 | Asynchronous processing method and device of transaction bill, electronic equipment and medium |
CN116415697A (en) * | 2021-12-31 | 2023-07-11 | 倍施特科技(集团)股份有限公司 | Networking ticketing system and interaction method thereof |
-
2023
- 2023-08-08 CN CN202310989340.0A patent/CN116703536B/en active Active
Patent Citations (7)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN102214323A (en) * | 2010-04-02 | 2011-10-12 | 彭晟罡 | Background management server, mobile terminal, and ticket booking system and method |
US20190012451A1 (en) * | 2015-05-14 | 2019-01-10 | Alclear, Llc | Biometric ticketing |
CN112016994A (en) * | 2020-08-14 | 2020-12-01 | 北京首钢自动化信息技术有限公司 | Ticket management method and device, readable storage medium and electronic equipment |
CN112348974A (en) * | 2020-10-28 | 2021-02-09 | 四川瑞云信通科技有限公司 | PRT novel automatic ticket selling and checking method and system |
CN116415697A (en) * | 2021-12-31 | 2023-07-11 | 倍施特科技(集团)股份有限公司 | Networking ticketing system and interaction method thereof |
CN114358943A (en) * | 2022-01-12 | 2022-04-15 | 平安普惠企业管理有限公司 | Online bill processing method and device, electronic equipment and storage medium |
CN115619552A (en) * | 2022-09-29 | 2023-01-17 | 中国建设银行股份有限公司 | Asynchronous processing method and device of transaction bill, electronic equipment and medium |
Non-Patent Citations (3)
Title |
---|
KARIN SIEBENHANDL等: "A User-Centered Design Approach to Self-Service Ticket Vending Machines", 《IEEE TRANSACTIONS ON PROFESSIONAL COMMUNICATION》, vol. 56, no. 2, pages 138 - 159, XP011514290, DOI: 10.1109/TPC.2013.2257213 * |
李煜平: "地铁互联网票务平台技术方案分析", 《城市轨道交通研究》, vol. 23, no. 03, pages 179 - 182 * |
杨舟等主编: "《城市轨道交通客运组织》", 中国建材工业出版社, pages: 149 * |
Cited By (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN117707097A (en) * | 2024-02-04 | 2024-03-15 | 广州泽亨实业有限公司 | Machining center control method and system |
CN117707097B (en) * | 2024-02-04 | 2024-05-10 | 广州泽亨实业有限公司 | Machining center control method and system |
Also Published As
Publication number | Publication date |
---|---|
CN116703536B (en) | 2023-10-24 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US8261977B2 (en) | Methods and systems for using an interface and protocol extensions to perform a financial transaction | |
US20140214670A1 (en) | Method for verifying a consumer's identity within a consumer/merchant transaction | |
US20140250016A1 (en) | Method and System for Controlling Risk in a Payment Transaction | |
CN110929816A (en) | Two-dimensional code validity control method and system | |
US20090178120A1 (en) | Electronic verification service systems and methods | |
CN116703536B (en) | Ticket transaction data processing method and system | |
WO2015062290A1 (en) | Methods and systems for authentications and online transactions | |
SK1832003A3 (en) | Method and system for facilitation of wireless e-commerce transactions | |
SK1822003A3 (en) | Method and system for facilitation of wireless e-commerce transactions | |
US20040098339A1 (en) | Method and apparatus for identifying an entity with which transactions are prohibited | |
WO2022134836A1 (en) | Article value evaluation method and apparatus, and computer device and storage medium | |
WO2018140700A1 (en) | Secure authentication and financial attributes services | |
US9197648B2 (en) | System and method for verifying the identity of an internet user | |
US20230014954A1 (en) | Systems and methods for product ordering and delivery for inmates | |
US20160335630A1 (en) | Method for Providing Secured Card Transactions During Card Not Present (CNP) Transactions | |
US20030061154A1 (en) | Systems and methods to facilitate an acquisition of information associated with a requested financial account | |
JP2008199618A (en) | Method, system, and computer program for using personal communication device to obtain additional information | |
US20020013900A1 (en) | User authentication device and electric commerce system using the device | |
CN104052605A (en) | Single System for Authenticating Entities Across Different Third Party Platforms | |
CN111340452A (en) | Method and device for opening account for public client | |
WO2022271652A1 (en) | Prioritizing holds when selecting transactions for transaction-based knowledge-based authentication | |
JP4211193B2 (en) | Personal authentication device in network | |
US20210185036A1 (en) | Secure authentication system | |
JP2002298042A (en) | Method and system for settlement of credit card, settling server, initial authentication method, authentication method, and authentication server | |
CN113159788A (en) | Transaction data processing method and device, storage medium and electronic equipment |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
PB01 | Publication | ||
PB01 | Publication | ||
SE01 | Entry into force of request for substantive examination | ||
SE01 | Entry into force of request for substantive examination | ||
GR01 | Patent grant | ||
GR01 | Patent grant |