Authentication methods for message data from transaction terminals, authentication backend, and POS terminals.
By introducing data authentication channels and transaction data channels into the POS terminal and using hash-processed bank card data comparison, the problem of POS transaction tampering has been solved, enabling real-time monitoring and accurate traceability of transactions.
Patent Information
- Application Number
- CN202211433040.6
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2022-11-16
- Publication Date
- 2026-11-10
- Estimated Expiration
- 2042-11-16
AI Technical Summary
Existing POS terminals are difficult to effectively monitor methods of POS transaction tampering, especially the risk of transactions conducted by multiple illegal terminals through legitimate terminals.
By introducing data authentication channels and transaction data channels into the POS terminal, the authentication backend receives binding relationship data and business data, compares them using hashed bank card data, and identifies the legality of the transaction data.
It enables real-time monitoring of POS transactions, prevents risks of merchant fraud and code fraud, provides accurate transaction traceability, and can monitor counterfeit transactions between multiple illegal terminals and legitimate terminals.
Smart Images

Figure CN116205645B_ABST
Abstract
Description
Technical Field
[0001] This application relates to the field of transaction monitoring, specifically to an authentication method for message data of a transaction terminal, an authentication backend, a POS terminal, a computer storage medium, and a computer program product. Background Technology
[0002] Existing POS terminals do not have very effective means of detecting POS transaction tampering.
[0003] For example, it is difficult to monitor the actual business interaction data of POS terminals, or to detect the risk of multiple illegal terminals conducting transactions but sending them through legal terminals.
[0004] The information disclosed above in the background section of this application is intended only to enhance the understanding of the overall background of this application and should not be construed as an admission or in any way implying that such information constitutes prior art known to those skilled in the art. Summary of the Invention
[0005] According to one aspect of this application, an authentication method for message data of a transaction terminal is provided. The method includes: an authentication backend receiving binding relationship data from the transaction terminal via a data authentication channel; the authentication backend receiving business data from an acceptance backend, the business data being received by the acceptance backend from the transaction terminal via a business data channel; and the authentication backend authenticating the business data based on the binding relationship data and feeding back the authentication result to the acceptance backend, wherein the data authentication channel is different from the business data channel; the binding relationship data is used to indicate the binding relationship between the business data obtained by the transaction terminal and the device ID of the transaction terminal. As a supplement or replacement to the above solution, in the above method, the transaction terminal is a POS terminal.
[0006] As a supplement or replacement to the above solution, in the above method, the POS terminal includes a card reader / QR code scanning module, and the authentication backend receives binding relationship data from the transaction terminal, including: the authentication backend directly receives merchant number, institution number, device ID, transaction time and hashed bank card data from the card reader / QR code scanning module via a data authentication channel, and the business data is the hashed bank card data.
[0007] As a supplement or replacement to the above solution, in the above method, the hashed bank card data is obtained by the card reader / QR code scanning module calling the communication module of the POS terminal to obtain the first bank card data and hash the first bank card data.
[0008] As a supplement or replacement to the above scheme, in the above method, the business data received by the authentication backend from the acceptance backend is obtained by the acceptance backend based on the received transaction message.
[0009] As a supplement or replacement to the above solution, in the above method, the POS terminal further includes a POS application module, and the transaction message is generated by the POS application module based on the acquired bank card data and provided to the acceptance backend via the transaction data channel.
[0010] As a supplement or replacement to the above scheme, in the above method, the authentication backend authenticates the business data based on the binding relationship data and feeds back the authentication result to the acceptance backend, including: the authentication backend compares the data sent by the transaction data channel with the data sent by the data authentication channel, and determines that there is altered transaction message data in the transaction data channel when the comparison is inconsistent.
[0011] As a supplement or replacement to the above scheme, in the above method, the authentication backend receives the merchant number, institution number, device ID and transaction time from the acceptance backend, and obtains the hashed bank card data based on the binding relationship data according to the merchant number, institution number, device ID and transaction time, and compares the obtained hashed bank card data with the bank card data sent by the acceptance backend.
[0012] As a supplement or replacement to the above scheme, in the above method, the authentication backend stores the binding relationship data to form a binding relationship table. When the authentication backend cannot find the binding relationship table based on the merchant number, the institution number, the device ID, and the transaction time, or finds multiple binding relationship tables, it is determined that there is altered transaction message data.
[0013] As a supplement or replacement to the above scheme, in the above method, if the authentication backend finds only one binding relationship table based on the merchant number, the institution number, the device ID, and the transaction time, and the obtained hashed bank card data is consistent with the bank card data sent by the acceptance backend, the comparison is determined to be successful; otherwise, the comparison fails.
[0014] According to another aspect of this application, an authentication backend is provided, the authentication backend comprising: a first receiving device for receiving binding relationship data from a transaction terminal via a data authentication channel; a second receiving device for receiving business data from an acceptance backend, the business data being received by the acceptance backend from the transaction terminal via a business data channel; and an authentication device for authenticating the business data based on the binding relationship data and feeding back the authentication result to the acceptance backend, wherein the data authentication channel is different from the business data channel; the binding relationship data is used to indicate the binding relationship between the business data obtained by the transaction terminal and the device ID of the transaction terminal.
[0015] As a supplement or replacement to the above scheme, the transaction terminal in the above authentication backend is a POS terminal.
[0016] As a supplement or replacement to the above solution, in the above authentication backend, the POS terminal includes a card reader / QR code scanning module, and the first receiving device is configured to receive merchant number, institution number, device ID, transaction time and hashed bank card data directly from the card reader / QR code scanning module via a data authentication channel, wherein the business data is the hashed bank card data.
[0017] As a supplement or replacement to the above scheme, in the above authentication backend, the hashed bank card data is obtained by the card reader / QR code scanning module calling the communication module of the POS terminal to obtain the first bank card data and hash the first bank card data.
[0018] As a supplement or replacement to the above scheme, in the above authentication backend, the business data received by the second receiving device is obtained by the acceptance backend based on the received transaction messages.
[0019] As a supplement or replacement to the above scheme, in the above authentication backend, the POS terminal also includes a POS application module, and the transaction message is generated by the POS application module based on the acquired bank card data and provided to the acceptance backend via the transaction data channel.
[0020] As a supplement or replacement to the above scheme, in the above authentication backend, the authentication device is configured to: compare the data sent by the transaction data channel with the data sent by the data authentication channel, and determine that there is altered transaction message data in the transaction data channel when the comparison is inconsistent.
[0021] As a supplement or replacement to the above solution, in the above authentication backend, the authentication backend is configured to: receive merchant number, institution number, device ID and transaction time from the acceptance backend; obtain hashed bank card data based on the binding relationship data according to the merchant number, institution number, device ID and transaction time; and compare the obtained hashed bank card data with the bank card data sent by the acceptance backend.
[0022] As a supplement or replacement to the above solution, in the above authentication backend, the authentication backend is configured to: store the binding relationship data to form a binding relationship table, wherein, when the authentication backend cannot find the binding relationship table based on the merchant number, the institution number, the device ID and the transaction time, or finds multiple binding relationship tables, it is determined that there is altered transaction message data.
[0023] As a supplement or replacement to the above scheme, in the above authentication backend, the authentication backend is configured to: when the authentication backend finds only one of the binding relationship tables based on the merchant number, the institution number, the device ID, and the transaction time, and the obtained hashed bank card data is consistent with the bank card data sent by the acceptance backend, the comparison is determined to be successful; otherwise, the comparison fails.
[0024] According to another aspect of this application, a POS terminal is provided, the POS terminal comprising: a card reader / QR code scanning module for providing binding relationship data to an authentication backend; and a POS application module for generating a transaction message based on the acquired bank card data and providing the transaction message to an acceptance backend, enabling the acceptance backend to obtain business data based on the received transaction message; wherein the binding relationship data is used to indicate the binding relationship between the business data obtained by the POS terminal and the device ID of the POS terminal, and wherein the authentication backend authenticates the business data based on the binding relationship data and feeds back the authentication result to the acceptance backend.
[0025] As a supplement or replacement to the above solution, in the above POS terminal, the card reader / QR code scanning module is configured to send the merchant number, institution number, device ID, transaction time and hashed bank card data directly to the authentication backend via the data authentication channel, wherein the business data is the hashed bank card data.
[0026] As a supplement or replacement to the above solution, the POS terminal may further include: a communication module, wherein the hashed bank card data is obtained by the card reader / QR code scanning module calling the communication module to obtain the first bank card data and hash the first bank card data.
[0027] As a supplement or replacement to the above solution, in the above POS terminal, the POS application module is configured to provide the transaction message to the acceptance backend via the transaction data channel.
[0028] According to another aspect of this application, a computer storage medium is provided, the medium including instructions that, when executed, perform the authentication method as described above.
[0029] According to another aspect of this application, a computer program product is provided, including a computer program that, when executed by a processor, implements the authentication method as described above.
[0030] The authentication scheme for message data of transaction terminals in one or more embodiments of this application receives binding relationship data from the transaction terminal and business data from the acceptance backend, and authenticates the business data based on the binding relationship data. This allows for real-time monitoring of whether a POS service provider is changing merchants to commit fraudulent transactions, thus preventing risks such as merchant fraud and code fraud. Furthermore, the authentication scheme for message data of transaction terminals in one or more embodiments of this application provides more accurate POS terminal transaction traceability, and can detect situations where multiple illegal terminals are engaging in fraudulent transactions with a single legitimate terminal.
[0031] By incorporating the figures in this article and subsequently the appendix Figure 1 The specific embodiments used to illustrate certain principles of this application will make other features and advantages of the methods and apparatus of this application clearer or more apparent. Attached Figure Description
[0032] Figure 1 This is a flowchart illustrating an embodiment of the authentication method for message data of a transaction terminal according to this application; Figure 2 This is a schematic diagram illustrating the structure of the authentication backend in one embodiment of this application; Figure 3 This is a schematic diagram illustrating the structure of a POS terminal according to an embodiment of this application; Figure 4 A data authentication channel according to one or more embodiments of this application is illustrated, which is different from the transaction data channel for uploading transaction messages; and Figure 5 This is a schematic diagram of the system interaction for implementing POS terminal card swiping transactions according to an embodiment of this application. Detailed Implementation
[0033] The following description illustrates specific embodiments of this application to teach those skilled in the art how to make and use this application. For the purpose of teaching the principles of the invention, some conventional aspects have been simplified or omitted. Those skilled in the art should understand that variations derived from these embodiments will fall within the scope of this application. Those skilled in the art should understand that the following features can be combined in various ways to form multiple variations of this application. Therefore, this application is not limited to the specific embodiments described below, but only to the claims and their equivalents.
[0034] It should also be noted that, for ease of description, only the parts relevant to this application are shown in the accompanying drawings, not all of them. Before discussing the exemplary embodiments in more detail, it should be mentioned that some exemplary embodiments are described as processes or methods depicted as flowcharts. Although the flowcharts describe the operations (or steps) as sequential processes, many of the operations can be performed in parallel, concurrently, or simultaneously. Furthermore, the order of the operations can be rearranged. The process can be terminated when its operation is completed, but it may also have additional steps not included in the drawings. The process may correspond to a method, function, procedure, subroutine, subprogram, etc.
[0035] Although exemplary embodiments are described as using multiple units to perform exemplary processes, it should be understood that these exemplary processes may also be performed by one or more modules.
[0036] Furthermore, the control logic of this application can be included as executable program instructions on a computer-readable medium, which are implemented by a processor or the like. Examples of computer-readable media include, but are not limited to, ROM, RAM, optical discs, magnetic tapes, floppy disks, flash drives, smart cards, and optical data storage devices. Computer-readable recording media can also be distributed across a networked computer system, enabling distributed storage and implementation of the computer-readable media.
[0037] Figure 1 This is a flowchart illustrating an embodiment of the message data authentication method 1000 for a transaction terminal according to this application. Figure 1 As shown, the authentication method 1000 includes the following steps: In step S110, the authentication backend receives binding relationship data from the transaction terminal via the data authentication channel; In step S120, the authentication backend receives business data from the acceptance backend, the business data being received by the acceptance backend from the transaction terminal via a business data channel; and In step S130, the authentication backend authenticates the business data based on the binding relationship data and feeds back the authentication result to the acceptance backend. The data authentication channel is different from the business data channel. The binding relationship data is used to indicate the binding relationship between the business data obtained by the transaction terminal and the device ID of the transaction terminal.
[0038] In the context of this application, the term "transaction terminal" is used to refer to a terminal for making transaction payments. In one or more embodiments, the transaction terminal is a POS terminal.
[0039] A POS terminal, also known as a point-of-sale (POS) terminal, mobile point-of-sale (POS) terminal, or mobile point-of-sale (POS) terminal, is used to provide non-cash settlement services to consumers. Banks provide domestic and foreign currency settlement services to merchants who have signed up for POS machine services. POS terminals can be classified by intelligence level into traditional POS machines and smart POS machines; by communication method into fixed POS machines and wireless POS machines; and by printing method into thermal POS machines, dot matrix POS machines, and electronic dot matrix POS machines. Furthermore, they can be classified by model into mobile phone POS machines, handheld POS machines, and desktop POS machines; and by operating system into Windows system POS machines and Android system POS machines. In one or more embodiments, the POS terminal can be implemented based on a user's smart terminal (e.g., a smartphone). For example, a user can download an app, authenticate, and bind their bank card to receive payments for their own and others' credit cards, thus turning the smartphone into a POS machine.
[0040] The term "message data" refers to transaction messages sent from a transaction terminal to a back-end server (including POS back-end, acceptance back-end, etc.). In one or more embodiments, the authentication back-end needs to authenticate this message data to monitor whether POS users or service providers are engaging in fraudulent transactions by changing merchants.
[0041] In the context of this application, the term "binding relationship data" is used to indicate the binding relationship between business data (e.g., bank card data) acquired by a transaction terminal (e.g., a POS terminal) and the device ID (e.g., terminal number) of the transaction terminal. In one or more embodiments, the binding relationship data includes merchant number, institution number, device ID, transaction time, and de-identified (e.g., hashed) bank card data.
[0042] The term "authentication backend" refers to the backend server used to authenticate binding relationship data to determine whether there is a risk of fraudulent transactions such as changing merchants. The term "acceptance backend" refers to the backend server used to accept transaction messages (e.g., determine whether a transaction is successful or failed). In one embodiment, the acceptance backend is located in the UnionPay acceptance network.
[0043] In one or more embodiments, "business data" refers to payment-related data that the authentication backend can use to compare with binding relationship data (or data authentication information). In one embodiment, business data is de-identified (e.g., hashed) bank card data.
[0044] In one embodiment, the authentication backend receiving binding relationship data from the transaction terminal (step S110) includes: the authentication backend receiving merchant number, institution number, device ID, transaction time, and hashed bank card data directly from the card reader / QR code scanning module in the POS terminal via the data authentication channel.
[0045] The Merchant ID refers to the unique identifier assigned to each POS terminal by the acquiring institution. The institution ID is the acquiring institution's identifier. In one embodiment, the institution ID is included within the Merchant ID, for example, as the first three digits of the Merchant ID. The Device ID (also known as the Terminal ID) is the unique machine terminal identifier assigned to each POS terminal by the acquiring institution. The Terminal ID is a unique and non-repeating identifier used to distinguish transaction amounts across different POS machines under a specific Merchant ID during later accounting checks, facilitating verification. A Merchant ID can have one or more POS machines. That is, multiple POS machines may share the same Merchant ID but have different Terminal IDs.
[0046] In one or more embodiments, the hashed bank card data is obtained by the card reader / QR code scanning module calling the communication module in the POS terminal to obtain the first bank card data and hash the first bank card data.
[0047] In the context of this application, "hashing," also known as hashing, is the process of transforming an input of arbitrary length into a fixed-length output using a hash algorithm. This output is called the hash value. This transformation is a compression mapping, meaning that the space of hash values is usually much smaller than the space of inputs. Different inputs may hash to the same output, making it impossible to determine a unique input value from the hash value. Therefore, the original bank card data cannot be reverse-engineered from the hashed bank card data, thus failing to protect sensitive data.
[0048] In one embodiment, in step S120, the business data received by the authentication backend from the acceptance backend is obtained by the acceptance backend based on the received transaction message. In one embodiment, the acceptance backend extracts the terminal number, merchant number, and hashed bank card data based on the received transaction message and sends them to the authentication backend.
[0049] In one embodiment, the transaction message is generated by the POS application module within the POS terminal based on the acquired bank card data and provided to the acceptance backend via the transaction data channel. For example, the POS application module receives bank card data from the card reader / QR code scanning module, assembles the transaction message according to the POS message structure, and sends it to the POS backend. Subsequently, the POS backend assembles the transaction message according to the requirements of the acceptance backend and sends it to the acceptance backend.
[0050] In step S130, the authentication backend authenticates the business data based on the binding relationship data and sends the authentication result back to the acceptance backend. In one embodiment, step S130 includes: the authentication backend comparing the data sent from the transaction data channel with the data sent from the data authentication channel, and determining that there is altered transaction message data in the transaction data channel when the comparison is inconsistent.
[0051] Here, "transaction data channel" refers to the channel for transmitting transaction messages. For example, in the transaction data channel, the POS application module sends the transaction message to the POS backend, and the POS backend then (according to the requirements of the acceptance backend) sends the transaction message to the acceptance backend. "Data authentication channel" differs from "transaction data channel"; it refers to the channel used to transmit binding relationship data (i.e., data authentication information). For example, in the data authentication channel, the card reader / QR code scanning module in the POS terminal sends binding relationship data to the authentication backend. During the transaction phase, the authentication backend compares the data sent from the transaction data channel with the data sent from the data authentication channel to determine if the transaction data channel has been altered.
[0052] One or more embodiments of this application propose a novel data authentication channel through which key information involved in the transaction process is collected and uploaded to the corresponding authentication backend, binding the data relationship. Subsequently, the key information of the actual transaction is compared with the data authentication information to monitor whether any alteration of transaction data has occurred on the transaction data channel.
[0053] Furthermore, those skilled in the art will readily understand that the authentication method 1000 for message data of a transaction terminal provided in one or more embodiments of this application can be implemented by a computer program. For example, the computer program is included in a computer program product, and when executed by a processor, it implements the authentication method 1000 for message data of a transaction terminal according to one or more embodiments of this application. As another example, when a computer storage medium (e.g., a USB flash drive) containing the computer program is connected to a computer, running the computer program executes the authentication method 1000 for message data of a transaction terminal according to one or more embodiments of this application.
[0054] refer to Figure 2 , Figure 2 A schematic diagram of the structure of an authentication backend 2000 according to an embodiment of this application is shown. Figure 2 As shown, the authentication backend 2000 includes a first receiving device 210, a second receiving device 220, and an authentication device 230. The first receiving device 210 receives binding relationship data from the transaction terminal via a data authentication channel; the second receiving device 220 receives business data from the acceptance backend, which is received by the acceptance backend from the transaction terminal via a business data channel; and the authentication device 230 authenticates the business data based on the binding relationship data and feeds back the authentication result to the acceptance backend. The data authentication channel is different from the business data channel. The binding relationship data indicates the binding relationship between the business data obtained by the transaction terminal and the device ID of the transaction terminal.
[0055] In the context of this application, the term "transaction terminal" is used to refer to a terminal for making transaction payments. In one or more embodiments, the transaction terminal is a POS terminal.
[0056] A POS terminal, also known as a point-of-sale (POS) terminal, mobile point-of-sale (POS) terminal, or mobile point-of-sale (POS) terminal, is used to provide non-cash settlement services to consumers. Banks provide domestic and foreign currency settlement services to merchants who have signed up for POS machine services. POS terminals can be classified by intelligence level into traditional POS machines and smart POS machines; by communication method into fixed POS machines and wireless POS machines; and by printing method into thermal POS machines, dot matrix POS machines, and electronic dot matrix POS machines. Furthermore, they can be classified by model into mobile phone POS machines, handheld POS machines, and desktop POS machines; and by operating system into Windows system POS machines and Android system POS machines. In one or more embodiments, the POS terminal can be implemented based on a user's smart terminal (e.g., a smartphone). For example, a user can download an app, authenticate, and bind their bank card to receive payments for their own and others' credit cards, thus turning the smartphone into a POS machine.
[0057] The term "message data" refers to transaction messages sent from a transaction terminal to a back-end server (including POS back-end, acceptance back-end, etc.). In one or more embodiments, the authentication back-end needs to authenticate this message data to monitor whether POS users or service providers are engaging in fraudulent transactions by changing merchants.
[0058] In the context of this application, the term "binding relationship data" is used to indicate the binding relationship between business data (e.g., bank card data) acquired by a transaction terminal (e.g., a POS terminal) and the device ID (e.g., terminal number) of the transaction terminal. In one or more embodiments, the binding relationship data includes merchant number, institution number, device ID, transaction time, and de-identified (e.g., hashed) bank card data.
[0059] The term "authentication backend" refers to the backend server used to authenticate binding relationship data to determine whether there is a risk of fraudulent transactions such as changing merchants. The term "acceptance backend" refers to the backend server used to accept transaction messages (e.g., determine whether a transaction is successful or failed). In one embodiment, the acceptance backend is located in the UnionPay acceptance network.
[0060] In one or more embodiments, "business data" refers to payment-related data that the authentication backend can use to compare with binding relationship data (or data authentication information). In one embodiment, business data is de-identified (e.g., hashed) bank card data.
[0061] In one embodiment, the POS terminal includes a card reader / QR code scanning module, and the first receiving device 210 is configured to receive merchant number, institution number, device ID, transaction time, and hashed bank card data directly from the card reader / QR code scanning module via a data authentication channel.
[0062] The Merchant ID refers to the unique identifier assigned to each POS terminal by the acquiring institution. The institution ID is the acquiring institution's identifier. In one embodiment, the institution ID is included within the Merchant ID, for example, as the first three digits of the Merchant ID. The Device ID (also known as the Terminal ID) is the unique machine terminal identifier assigned to each POS terminal by the acquiring institution. The Terminal ID is a unique and non-repeating identifier used to distinguish transaction amounts across different POS machines under a specific Merchant ID during later accounting checks, facilitating verification. A Merchant ID can have one or more POS machines. That is, multiple POS machines may share the same Merchant ID but have different Terminal IDs.
[0063] In one or more embodiments, the hashed bank card data is obtained by the card reader / QR code scanning module calling the communication module in the POS terminal to obtain the first bank card data and hash the first bank card data.
[0064] In the context of this application, "hashing," also known as hashing, is the process of transforming an input of arbitrary length into a fixed-length output using a hash algorithm. This output is called the hash value. This transformation is a compression mapping, meaning that the space of hash values is usually much smaller than the space of inputs. Different inputs may hash to the same output, making it impossible to determine a unique input value from the hash value. Therefore, the original bank card data cannot be reverse-engineered from the hashed bank card data, thus failing to protect sensitive data.
[0065] In one embodiment, the business data received by the second receiving device 220 is obtained by the acceptance backend based on the received transaction message. In one embodiment, the acceptance backend extracts the terminal number, merchant number, and hashed bank card data based on the received transaction message and sends them to the authentication backend.
[0066] In one embodiment, the transaction message is generated by the POS application module within the POS terminal based on the acquired bank card data and provided to the acceptance backend via the transaction data channel. For example, the POS application module receives bank card data from the card reader / QR code scanning module, assembles the transaction message according to the POS message structure, and sends it to the POS backend. Subsequently, the POS backend assembles the transaction message according to the requirements of the acceptance backend and sends it to the acceptance backend.
[0067] In one embodiment, the authentication device 230 is configured to: compare the data sent by the transaction data channel with the data sent by the data authentication channel, and determine that there is altered transaction message data in the transaction data channel when the comparison is inconsistent.
[0068] In this embodiment, the "transaction data channel" refers to the channel used to transmit transaction messages. For example, in the transaction data channel, the POS application module sends the transaction message to the POS backend, and the POS backend then (according to the requirements of the acceptance backend) sends the transaction message to the acceptance backend. The "data authentication channel" differs from the "transaction data channel"; it refers to the channel used to transmit binding relationship data (i.e., data authentication information). For example, in the data authentication channel, the card reader / QR code scanning module in the POS terminal sends binding relationship data to the authentication backend. During the transaction phase, the authentication backend compares the data sent from the transaction data channel with the data sent from the data authentication channel to determine whether the transaction data channel has been altered.
[0069] Go to Figure 3 This illustrates a structural schematic diagram of a POS terminal 3000 according to an embodiment of this application. Figure 3As shown, the POS terminal 3000 includes: a card reader / QR code scanning module 310, used to provide binding relationship data to the authentication backend; and a POS application module 320, used to generate a transaction message based on the acquired bank card data and provide the transaction message to the acceptance backend, so that the acceptance backend can obtain business data based on the received transaction message; wherein, the binding relationship data is used to indicate the binding relationship between the business data acquired by the POS terminal and the device ID of the POS terminal, and wherein the authentication backend authenticates the business data based on the binding relationship data and feeds back the authentication result to the acceptance backend.
[0070] In one embodiment, in the POS terminal 3000 described above, the card reader / QR code scanning module 310 is configured to send the merchant number, institution number, device ID, transaction time, and hashed bank card data to the authentication backend via a data authentication channel.
[0071] In one embodiment, the POS terminal 3000 may further include a communication module 330, wherein the hashed bank card data is obtained by the card reader / QR code scanning module 310 calling the communication module 330 to obtain the first bank card data and hashing the first bank card data, and the authentication ID is generated by the card reader / QR code scanning module when hashing the first bank card data.
[0072] In one embodiment, the POS application module 320 is configured to provide the transaction message to the acceptance backend via a transaction data channel, and the business data includes the hashed bank card data.
[0073] It's important to clarify that the "transaction data channel" refers to the channel used for transmitting transaction messages. For example, in the transaction data channel, the POS application module sends the transaction message to the POS backend, and the POS backend then (as required by the acceptance backend) sends the transaction message to the acceptance backend. The "data authentication channel," unlike the "transaction data channel," refers to the channel used for transmitting binding relationship data (i.e., data authentication information). For example, in the data authentication channel, the card reader / QR code scanning module within the POS terminal sends binding relationship data to the authentication backend. During the transaction phase, the authentication backend compares the data sent from the transaction data channel with the data sent from the data authentication channel to determine if the transaction data channel has been altered.
[0074] To better illustrate the difference between the data authentication channel and the transaction data channel, Figure 4 A data authentication channel according to one or more embodiments of this application is shown, which is different from the transaction data channel for uploading transaction messages.
[0075] exist Figure 4 In this system, the data authentication channel is used to transmit binding relationship data (i.e., data authentication information). Specifically, during the POS card reading or QR code scanning stage, the acquired business data information is bound to the generated device ID, and this data relationship is sent to the authentication backend through the data authentication channel. In contrast to the data authentication channel, the "transaction data channel" refers to the channel used to transmit transaction messages. During the transaction stage, the authentication backend compares the data sent from the transaction data channel with the data sent from the data authentication channel to determine if the transaction data channel has been altered.
[0076] Figure 5 This is a schematic diagram of a system interaction for implementing POS terminal card swiping transactions according to an embodiment of this application. Figure 5 As shown, in step 1, when a merchant initiates a transaction at the POS terminal, preparing to read the bank card; then, in step 2, the POS APP (i.e., the POS application module) sends a request to the card reader module to read the bank card, along with the merchant number and terminal number of this transaction; in step 3, the card reader module calls the terminal's communication module and completes the reading of the bank card data following the PBOC process; in step 4, the card reader module sends the hash value, institution number, merchant number, device unique ID, transaction time, and other information of the bank card data to the authentication backend through a secure channel, and the authentication backend binds and stores this data; then, in step 5, the card reader module returns the read bank card data to the POS APP; finally, in step 6, the POS APP obtains the bank card data, assembles a transaction message according to the POS message, and sends it to the POS terminal. The backend then proceeds as follows: In step 7, the POS backend assembles the transaction message according to the requirements of the acceptance backend and sends it to the acceptance backend; in step 8, the acceptance backend extracts the unique device ID, institution number, merchant number, transaction time, and hashed bank card data from the received transaction message and sends it to the authentication backend; then, in step 9, the authentication backend retrieves the hashed bank card data from the binding relationship table based on the unique device ID, institution number, merchant number, and transaction time (Note: If the binding relationship table is not found or multiple binding relationship tables are found, it indicates that the POS backend has altered the merchant data, and a comparison failure is returned. If only one binding relationship is found, the hash of the bank card data in the binding relationship is compared with the hash of the bank card data sent by the acceptance backend. If the comparison is inconsistent, it indicates that the card swipe data has been altered, and a comparison failure is returned. Otherwise, a comparison success is returned); in step 10, the authentication backend returns the comparison relationship to the acceptance backend; in step 11, the acceptance backend determines whether the transaction is successful or failed based on the comparison result and returns the transaction result to the POS backend; in step 12, the POS backend returns the transaction result to the POS application module within the POS terminal.
[0077] By comparing the data from the transaction data channel and the data authentication channel as described above, it can be determined whether the transaction data channel has been altered.
[0078] In summary, the authentication scheme for message data of transaction terminals in one or more embodiments of this application, by receiving binding relationship data from the transaction terminal and business data from the acceptance backend, and authenticating the business data based on the binding relationship data, can monitor in real time whether the POS service provider is changing merchants to commit fraudulent transactions, thus preventing risks such as merchant fraud and code fraud. Furthermore, the authentication scheme for message data of transaction terminals in one or more embodiments of this application can provide more accurate POS terminal transaction traceability, and can detect situations where multiple illegal terminals are conducting counterfeit transactions with a single legitimate terminal.
[0079] Those skilled in the art will understand that embodiments of this application can be provided as methods, apparatus, or computer program products. Therefore, this application can take the form of hardware, software, or a combination of hardware and software. Furthermore, this application can take the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk storage and optical storage) containing computer-usable program code.
[0080] This application is described with reference to flowchart illustrations and / or block diagrams of methods, apparatus (platform systems), and computer program products according to embodiments of this application. These computer program instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable processing device, causing the generation of a sequence of instructions that performs a specified operation.
[0081] Those skilled in the art should understand that the examples and embodiments shown in the specification of this application should be considered illustrative rather than restrictive, and various modifications and substitutions may be made without departing from the spirit and scope of this application as defined by the appended claims.
Claims
1. A method for authenticating message data of a transaction terminal, characterized in that, The method includes: The authentication backend receives binding relationship data from the transaction terminal via the data authentication channel; The authentication backend receives business data from the acceptance backend. This business data is received by the acceptance backend from the transaction terminal via a business data channel. The business data received by the authentication backend from the acceptance backend is obtained by the acceptance backend based on received transaction messages, which are then provided to the acceptance backend via the transaction data channel. The authentication backend authenticates the business data based on the binding relationship data and sends the authentication result back to the processing backend. The data authentication channel is different from the business data channel; The binding relationship data is used to indicate the binding relationship between the business data obtained by the transaction terminal and the device ID of the transaction terminal. The authentication backend authenticates the business data based on the binding relationship data and then sends the authentication result back to the processing backend, including: The authentication backend compares the data sent from the transaction data channel with the data sent from the data authentication channel, and determines that there is altered transaction message data in the transaction data channel if the comparison is inconsistent.
2. The method as described in claim 1, wherein, The transaction terminal is a POS terminal.
3. The method as described in claim 2, wherein, The POS terminal includes a card reader / QR code scanning module, and the authentication backend receives binding relationship data from the transaction terminal, including: The authentication backend receives the merchant number, institution number, device ID, transaction time, and hashed bank card data directly from the card reader / QR code scanning module via the data authentication channel, and the business data is the hashed bank card data.
4. The method of claim 3, wherein, The hashed bank card data is generated by the card reader / QR code scanning module calling the communication module of the POS terminal to obtain the first bank card data and hash the first bank card data.
5. The method as described in claim 3 or 4, wherein, The POS terminal also includes a POS application module, wherein the transaction message is generated by the POS application module based on the acquired bank card data.
6. The method of claim 1, wherein, The authentication backend receives the merchant number, institution number, device ID, and transaction time from the acceptance backend. Based on the merchant number, institution number, device ID, and transaction time, it obtains hashed bank card data from the binding relationship data and compares the obtained hashed bank card data with the bank card data sent from the acceptance backend.
7. The method of claim 6, wherein, The authentication backend stores the binding relationship data to form a binding relationship table. When the authentication backend cannot find the binding relationship table based on the merchant number, the institution number, the device ID, and the transaction time, or finds multiple binding relationship tables, it is determined that there is altered transaction message data.
8. The method of claim 7, wherein, If the authentication backend finds only one binding relationship table based on the merchant number, the institution number, the device ID, and the transaction time, and the obtained hashed bank card data matches the bank card data sent by the acceptance backend, the comparison is considered successful; otherwise, the comparison fails.
9. An authentication backend, characterized in that, The authentication backend includes: The first receiving device is used to receive binding relationship data from the transaction terminal via a data authentication channel; A second receiving device is configured to receive business data from the acceptance backend, the business data being received by the acceptance backend from the transaction terminal via a business data channel. The business data received by the second receiving device is obtained by the acceptance backend based on a received transaction message, which is provided to the acceptance backend via the transaction data channel. The authentication device is used to authenticate the business data based on the binding relationship data and to report the authentication result back to the processing backend. The data authentication channel is different from the business data channel; The binding relationship data is used to indicate the binding relationship between the business data obtained by the transaction terminal and the device ID of the transaction terminal. The authentication device is configured as follows: The data sent through the transaction data channel is compared with the data sent through the data authentication channel, and if the comparison is inconsistent, it is determined that there is altered transaction message data in the transaction data channel.
10. The authentication backend as described in claim 9, wherein, The transaction terminal is a POS terminal.
11. The authentication backend as described in claim 10, wherein, The POS terminal includes a card reader / QR code scanning module, and the first receiving device is configured to receive merchant number, institution number, device ID, transaction time, and hashed bank card data directly from the card reader / QR code scanning module via a data authentication channel, wherein the business data is the hashed bank card data.
12. The authentication backend as described in claim 11, wherein, The hashed bank card data is generated by the card reader / QR code scanning module calling the communication module of the POS terminal to obtain the first bank card data and hash the first bank card data.
13. The authentication backend as described in claim 11 or 12, wherein, The POS terminal also includes a POS application module, wherein the transaction message is generated by the POS application module based on the acquired bank card data.
14. The authentication backend as described in claim 9, wherein, The authentication backend is configured as follows: Receive merchant ID, institution ID, device ID, and transaction time from the processing backend; Based on the merchant number, the institution number, the device ID, and the transaction time, obtain the hashed bank card data according to the binding relationship data; as well as The hashed bank card data obtained is compared with the bank card data sent from the processing backend.
15. The authentication backend as described in claim 14, wherein, The authentication backend is configured as follows: The binding relationship data is stored to form a binding relationship table. If the authentication backend cannot find the binding relationship table based on the merchant number, the institution number, the device ID, and the transaction time, or finds multiple binding relationship tables, it is determined that there is altered transaction message data.
16. The authentication backend as described in claim 15, wherein, The authentication backend is configured as follows: If the authentication backend finds only one binding relationship table based on the merchant number, the institution number, the device ID, and the transaction time, and the obtained hashed bank card data matches the bank card data sent by the acceptance backend, the comparison is considered successful; otherwise, the comparison fails.
17. A POS terminal, characterized in that, The POS terminal includes: The card reader / QR code scanning module is used to provide the binding relationship data to the authentication backend; The POS application module is used to generate transaction messages based on the acquired bank card data and provide the transaction messages to the acceptance backend, so that the acceptance backend can obtain business data based on the received transaction messages. The POS application module is configured to provide the transaction messages to the acceptance backend via a transaction data channel. The binding relationship data is used to indicate the binding relationship between the business data obtained by the POS terminal and the device ID of the POS terminal. The authentication backend authenticates the business data based on the binding relationship data and feeds back the authentication result to the acceptance backend. The authentication backend authenticates the business data based on the binding relationship data and feeds back the authentication result to the acceptance backend includes: the authentication backend compares the data sent by the transaction data channel with the data sent by the data authentication channel, and determines that there is altered transaction message data in the transaction data channel when the comparison is inconsistent.
18. The POS terminal as described in claim 17, wherein, The card reader / QR code scanning module is configured to send the merchant number, institution number, device ID, transaction time, and hashed bank card data directly to the authentication backend via the data authentication channel. The business data is the hashed bank card data.
19. The POS terminal as described in claim 18, wherein, The POS terminal further includes a communication module, wherein the hashed bank card data is generated by the card reader / QR code scanning module calling the communication module to obtain the first bank card data and hash the first bank card data.
20. A computer storage medium comprising instructions that, when executed, perform the authentication method as described in any one of claims 1 to 8.
21. A computer program product, comprising a computer program, characterized in that, When the computer program is executed by the processor, it implements the authentication method as described in any one of claims 1 to 8.
Citation Information
Patent Citations
System and method for confirming electronic trade based on independent password equipment
CN104408622A
Payment authentication method and authentication system based on face recognition and hce
WO2017167037A1
