Multi-dimensional payment state sensing system

Abstract

The invention discloses a multi-dimensional payment state sensing system, and belongs to the technical field of mobile payment. The system comprises a display module and a payment state synchronization module, the display module comprises a merchant display unit, a customer display unit and a voice broadcast module, the payment state synchronization module adopts a long connection mechanism, and the display module adopts a differential marking technology, so that real-time synchronization and visual presentation of payment states are realized; the interaction efficiency of two transaction parties is obviously improved; the system effectively solves the problems of delayed feedback, information asymmetry and the like of a traditional payment state through cooperation of a merchant and customer double-end display unit, a voice broadcast module and the like, realizes multi-dimensional perception of the payment state, and reduces the risk of communication interruption at the same time.

Description

Technical Field

[0001] The present invention belongs to the technical field of mobile payment and relates to a multi-dimensional payment status perception system. Background Art

[0002] Modern payment methods have undergone three technological iterations: cash, card payments, and mobile payments. Cash, the first and most primitive form of payment, traces its origins to the formation of the ancient monetary economy. The physical properties of metal and paper currency dictate that transactions can be completed without relying on external systems, a feature that has long ensured its dominance in regions with weak infrastructure. Its continued popularity stems from its ubiquity and legal enforceability. However, drawbacks such as inefficient manual counting, the risk of counterfeit currency, and the inability to trace transaction processes ultimately led to the rise of electronic payment technology.

[0003] The second phase of card payments originated with the invention of credit cards in the 1950s. The combination of magnetic stripe cards and POS terminals enabled electronic payments for the first time. Its core technology lies in the integration of banking networks and merchant terminals, replacing the physical circulation of cash. This phase lasted for decades thanks to its high degree of standardization, support for large-value transactions, and cross-regional settlement. However, its reliance on POS terminals and centralized clearing networks led to issues such as response delays and high fees, ultimately leading to its gradual replacement with the widespread adoption of mobile internet.

[0004] Mobile payment, an emerging and currently most frequently used technology, stems from the widespread adoption of smartphones and wireless networks in the early 21st century. Alipay and Apple Pay, for example, digitize payment behavior through technologies like QR codes and NFC. Its explosive growth is attributed to three key advantages: reduced hardware costs (requiring only a smart terminal), improved efficiency for small payments, and seamless integration with online scenarios (such as e-commerce and social media red envelopes). However, while originally designed for user convenience, mobile payment has proven problematic in business-to-business scenarios such as multi-merchant collaboration and high-concurrency order management, resulting in feedback delays, insufficient status synchronization, a lack of intuitive payment status feedback, and a failure to substantially improve management efficiency.

[0005] Current mainstream mobile payment terminals suffer from three major technical shortcomings: First, order status synchronization relies on manual refreshes or network callbacks, which can easily lead to missed orders or duplicate charges during peak periods due to delays. Second, the limited feedback mechanism requires merchants to frequently check the screen or paper receipts, precluding multimodal methods (such as audio and visual prompts) to quickly understand transaction results. Third, the interaction interface is not separated, with customers and merchants sharing the same screen, leading to privacy risks and lengthy operation processes. While existing split-screen payment devices achieve physical separation of interfaces, they fail to overcome the technical barriers of status synchronization delays and unintuitive feedback, making them difficult to meet the demands of high-concurrency transaction scenarios.

[0006] With the surge in transaction frequency, payment systems must simultaneously meet real-time, accurate, and user-friendly requirements. Existing technologies, due to architectural limitations, cannot synchronize payment status across multiple terminals, including merchant terminals, customer terminals, and backend systems. Furthermore, they lack multi-channel feedback mechanisms such as visual, auditory, and tactile collaborative prompts. Therefore, a payment system integrating real-time data synchronization and multimodal interaction is urgently needed to address key issues in existing technologies, such as delayed order status perception and disconnected human-computer interaction. Summary of the Invention

[0007] The purpose of this application is to provide a multi-dimensional payment status perception system, which solves the problems raised in the above background technology by adopting a long connection mechanism and differentiated marking distinction technology.

[0008] To achieve the above objectives, this application discloses a multi-dimensional payment status perception system, including: A display module, which provides interactive information display for customers and merchants; Payment status synchronization module, the payment status synchronization module continuously communicates with the payment platform server through a long connection mechanism, establishes a TCP connection through a three-way handshake, and the connection will remain continuously open to provide a channel for subsequent payment data transmission. The connection channel can continuously exchange data packets without the need to re-establish the connection for each communication. The payment status synchronization module regularly sends empty data packets to the payment platform server through a heartbeat mechanism to detect link activity and prevent forced disconnection. When the payment status synchronization module detects a connection interruption, it automatically triggers a reconnection mechanism to restore the communication link, obtain payment results in real time, and trigger information updates on the display module to ensure that the display interface of the display module is updated synchronously with the payment status.

[0009] Furthermore, the display module includes a merchant display unit facing merchants and a customer display unit facing customers. The merchant display unit displays the current order queue in real time, including the order amount, order waiting time for payment and payment status; the customer display unit displays the customer order content, order amount and generated payment QR code in real time.

[0010] Furthermore, the payment status is distinguished into pending payment, paid and cancelled payment status by differential marks.

[0011] Furthermore, the mechanism layer of the long connection mechanism includes: a control layer, a protocol layer and a network layer; The control layer performs active maintenance of long connections and event-driven payment status. The control layer sends heartbeat packets regularly to maintain connection activity. After receiving the heartbeat packet from the payment platform server, it confirms the link availability, receives real-time status notifications from the payment platform, and triggers order updates on the display module. If the payment platform server fails to respond due to network delay timeout, reconnection is triggered. The protocol layer defines the communication protocol format and handles the encryption / decryption and distribution of data packets, including a sending end and a receiving end. The sending end encapsulates the protocol header and the body, generates a protocol packet, and sends a binary data stream. The receiving end receives the protocol header, parses the packet header to verify the legitimacy of the protocol header, receives the body if the verification passes, generates a protocol packet, decrypts the protocol packet, and distributes the protocol packet according to the packet type. The network layer handles the sending and receiving of the underlying data stream and is divided into a sending queue and a receiving queue. The network layer stores the protocol packets generated by the protocol layer into the sending queue according to priority, and writes the data to the corresponding connection channel through the asynchronous IO thread. The network layer asynchronously reads the data stream from the connection channel, reorganizes it into complete protocol packets in sequence to form a receiving queue, and the receiving queue data packets are submitted to the protocol layer for parsing according to priority.

[0012] Furthermore, the control layer is composed of a heartbeat maintenance unit, a reconnection control unit and an event-driven unit. The heartbeat maintenance unit is used to send heartbeat packets, perform response detection of heartbeat packets returned, and dynamically adjust the heartbeat interval based on network delay; The reconnection control unit is used to handle connection anomalies, monitor heartbeat return anomalies and payment status event anomalies triggered by the heartbeat maintenance unit, immediately reconnect for the first disconnection, perform time-delayed connections for subsequent reconnections, and reset the heartbeat interval and synchronize unconfirmed payment status after successful reconnection; The event-driven unit coordinates the responses of each module based on the publish-subscribe model, dynamically selects the distribution path according to the event type, pushes payment events to the display module and inserts them into the priority processing queue, and network delay events trigger cross-module collaboration. For example, a successful reconnection event will synchronously wake up the heartbeat maintenance unit to reset the heartbeat interval.

[0013] Furthermore, the transmitting end of the protocol layer is composed of a protocol header encapsulation unit, a body encapsulation unit and a data encryption unit. The protocol header encapsulation unit converts the data into a binary stream according to the field order of packet type, data length, timestamp and check code, calculates the check code and fills it into the end of the protocol header, and outputs the protocol header binary data; The Body encapsulation unit is responsible for converting service data into a standardized binary format, using TLV encoding to generate TLV triples according to the service field definition, sequentially splicing all TLV structures into a binary stream, recording the total length and submitting it to the protocol header encapsulation unit. The protocol header encapsulation unit fills the data length field accordingly to ensure that the header and body strictly match; The data encryption unit performs end-to-end protection on the Body data.

[0014] Furthermore, the network layer is composed of a sending queue management unit, an asynchronous I / O core unit, and a receiving queue processing unit. The sending queue management unit dynamically adjusts the priority of data packets through multi-level feedback, giving payment events the highest priority and preemptively processing them, and listing heartbeat packets as ordinary queues. When the sending queue times out, the priority of the data packet is automatically downgraded and retried. If three consecutive failures occur, the connection reestablishment process of the reconnection control unit is triggered. The asynchronous I / O core unit manages the read and write operations of all connection channels through multiplexing connections, separating the high-priority payment data channel from the heartbeat data channel. When it detects that payment data is ready, it immediately interrupts the current low-priority task and prioritizes the data transmission of the payment channel. If two consecutive I / O operation timeouts occur on the same channel, the channel is automatically marked as abnormal. The event-driven unit publishes a network interruption event to trigger the reconnection process. After the reconnection is successful, the receiving queue prioritizes the backlog of unconfirmed payment data to ensure state synchronization. The receiving queue processing unit marks the payment data packet as high-priority verification according to the protocol header type, and marks the heartbeat packet as ordinary verification. The high-priority verification is directly assigned to the protocol layer receiving end for verification and decryption. If it is detected that the data packet verification fails continuously, the link detection of the reconnection control unit is triggered. The heartbeat packet is submitted to the heartbeat maintenance unit after verification, and all successfully processed data packets are timestamped.

[0015] Furthermore, the display module also includes a voice broadcast module. After the payment status is updated to paid, the voice broadcast module plays a preset voice template through a built-in speaker. The voice broadcast module supports volume adjustment and voice content customization.

[0016] The present invention adopts the above technical solution, which has the following beneficial effects: This application's multi-dimensional payment status perception system utilizes a persistent connection mechanism and differentiated tagging technology to achieve real-time synchronization and visual presentation of payment status, significantly improving the efficiency of interaction between both parties. By integrating display units on both the merchant and customer sides, voice broadcasting, and other modules, the system effectively addresses issues such as delayed payment status feedback and information asymmetry, while also reducing the risk of communication interruptions caused by network fluctuations.

[0017] The three-tier architecture design of the persistent connection mechanism ensures the reliability and security of data transmission. Its heartbeat detection and automatic reconnection functions significantly enhance system stability. Differentiated status markings make the payment process more transparent. The voice broadcast function further enhances status perception and enables multi-dimensional perception of payment status, providing a complete solution for real-time, multi-dimensional perception of payment status for high-frequency payment scenarios such as supermarkets and restaurants. BRIEF DESCRIPTION OF THE DRAWINGS

[0018] The drawings described herein are used to provide a further understanding of the present invention, constitute a part of this application, and do not constitute an improper limitation of the present invention. In the drawings: Figure 1 This is a schematic diagram of the system structure of this application; Figure 2 This is a schematic diagram of the long connection mechanism layer of the payment status synchronization module of this application; Figure 3 This is the long connection flow chart of the payment status synchronization module for this application. DETAILED DESCRIPTION

[0019] The present invention will be described in detail below with reference to the accompanying drawings and specific embodiments. The exemplary embodiments and descriptions of the present invention are used to explain the present invention but are not intended to limit the present invention.

[0020] Example 1 See also Figure 1 The present application discloses a multi-dimensional payment status perception system, including: a display module, which provides interactive information display for customers and merchants; a payment status synchronization module, which continuously communicates with the payment platform server through a long connection mechanism, establishes a TCP connection through a three-way handshake, and the connection will remain in a continuously open state to provide a channel for subsequent payment data transmission. The connection channel can continuously exchange data packets without the need to re-establish a connection for each communication. The payment status synchronization module periodically sends empty data packets to the payment platform server through a heartbeat mechanism to detect link activity and prevent forced disconnection. When the payment status synchronization module detects a connection interruption, it automatically triggers a reconnection mechanism to restore the communication link, obtain payment results in real time, and trigger information updates of the display module to ensure that the display interface of the display module is updated synchronously with the payment status.

[0021] It should be further explained that the display module includes a merchant display unit facing merchants and a customer display unit facing customers. The merchant display unit displays the current order queue in real time, including the order amount, order waiting time for payment and payment status; the customer display unit displays the customer's order content, order amount and generated payment QR code in real time.

[0022] Furthermore, the payment status is distinguished into pending payment, paid and cancelled payment status by differential marks.

[0023] In some embodiments, different color blocks are used to distinguish between the statuses of pending payment, paid, and canceled payment. In other embodiments, different shapes, patterns, or combinations thereof, as well as combinations of colors, shapes, and patterns, are used to distinguish between the statuses of pending payment, paid, and canceled payment.

[0024] Furthermore, the payment status synchronization module realizes continuous communication between the display module and the payment platform server through a long connection mechanism. The payment status synchronization module establishes a TCP connection with the payment platform server through a three-way handshake. The connection will remain open to provide a channel for subsequent multiple data transmissions. The connection channel can continuously exchange data packets without the need to re-establish a connection for each communication. The payment status synchronization module periodically sends empty data packets to the payment platform server through a heartbeat mechanism to detect link activity and prevent forced disconnection by a firewall or router due to network idleness. When the payment status synchronization module detects a connection interruption, it automatically triggers a reconnection mechanism to restore the communication link.

[0025] See also Figure 2 and Figure 3 ,Furthermore, the mechanism layer of the long connection mechanism includes: a control layer, a protocol layer and a network layer; The control layer performs active maintenance of long connections and event-driven payment status. The control layer sends heartbeat packets regularly to maintain connection activity. After receiving the heartbeat packet from the payment platform server, it confirms the link availability. If the payment platform server does not respond after a timeout, it triggers reconnection and receives real-time status notifications from the payment platform, triggering order updates on the display module. The protocol layer defines the communication protocol format and handles the encryption / decryption and distribution of data packets, including a sending end and a receiving end. The sending end encapsulates the protocol header and the body, generates a protocol packet, and sends a binary data stream. The receiving end receives the protocol header, parses the packet header to verify the legitimacy of the protocol header, receives the body if the verification passes, generates a protocol packet, decrypts the protocol packet, and distributes the protocol packet according to the packet type. The network layer handles the sending and receiving of the underlying data stream and is divided into a sending queue and a receiving queue. The network layer stores the protocol packets generated by the protocol layer into the sending queue according to priority, and writes the data to the corresponding connection channel through the asynchronous IO thread. The network layer asynchronously reads the data stream from the connection channel, reorganizes it into complete protocol packets in sequence to form a receiving queue, and the receiving queue data packets are submitted to the protocol layer for parsing according to priority.

[0026] It should be further explained that the control layer is composed of a heartbeat maintenance unit, a reconnection control unit and an event-driven unit. The heartbeat maintenance unit is used to send heartbeat packets, perform response detection on returned heartbeat packets, and dynamically adjust the heartbeat interval based on network delay. The reconnection control unit is used to handle connection anomalies, monitor heartbeat return anomalies and payment status event anomalies triggered by the heartbeat maintenance unit, immediately reconnect for the first disconnection, perform time-delayed connections for subsequent reconnections, and reset the heartbeat interval and synchronize unconfirmed payment status after successful reconnection; The event-driven unit coordinates the responses of each module based on the publish-subscribe model, dynamically selects the distribution path according to the event type, pushes payment events to the display module and inserts them into the priority processing queue, and network delay events trigger cross-module collaboration. For example, a successful reconnection event will synchronously wake up the heartbeat maintenance unit to reset the heartbeat interval.

[0027] It should be further explained that the sending end of the protocol layer is composed of a protocol header encapsulation unit, a body encapsulation unit, and a data encryption unit. The protocol header encapsulation unit converts the data into a binary stream according to the field order of packet type, data length, timestamp, and check code, calculates the check code and fills it into the end of the protocol header, and outputs the protocol header binary data; The Body encapsulation unit is responsible for converting service data into a standardized binary format, using TLV encoding to generate TLV triples according to the service field definition, sequentially splicing all TLV structures into a binary stream, recording the total length and submitting it to the protocol header encapsulation unit. The protocol header encapsulation unit fills the data length field accordingly to ensure that the header and body strictly match; The data encryption unit performs end-to-end protection on the Body data.

[0028] It should be further explained that the network layer consists of a sending queue management unit, an asynchronous I / O core unit, and a receiving queue processing unit. The sending queue management unit dynamically adjusts the priority of data packets through multi-level feedback, giving payment events the highest priority and preemptively processing them. It lists heartbeat packets as ordinary queues. When the sending queue times out, it automatically downgrades the priority of the data packet and retries. If three consecutive failures occur, the reconnection control unit triggers the connection reconstruction process. The asynchronous I / O core unit manages the read and write operations of all connection channels through multiplexing connections, separating the high-priority payment data channel from the heartbeat data channel. When it detects that payment data is ready, it immediately interrupts the current low-priority task and prioritizes the data transmission of the payment channel. If two consecutive I / O operation timeouts occur on the same channel, the channel is automatically marked as abnormal. The event-driven unit publishes a network interruption event to trigger the reconnection process. After the reconnection is successful, the receiving queue prioritizes the backlog of unconfirmed payment data to ensure state synchronization. The receiving queue processing unit marks the payment data packet as high-priority verification according to the protocol header type, and marks the heartbeat packet as ordinary verification. The high-priority verification is directly assigned to the protocol layer receiving end for verification and decryption. If it is detected that the data packet verification fails continuously, the link detection of the reconnection control unit is triggered. The heartbeat packet is submitted to the heartbeat maintenance unit after verification, and all successfully processed data packets are timestamped.

[0029] In some embodiments of the present application, the display module also includes a voice broadcast module. After the payment status is updated to paid, the voice broadcast module plays a preset voice template through the built-in speaker. The voice broadcast module supports volume adjustment and voice content customization.

[0030] This embodiment also records an application example of a multi-dimensional payment status perception system, in which merchants provide relevant information and register for the system application. An electronic device equipped with the multi-dimensional payment status perception system is deployed to the merchant counter. The merchant binds the display module. After selecting the product, the customer scans the QR code to enter the payment interface and verify the payment. The system generates an order, but the order is in an unpaid state. The order information is pushed to the display module and displayed in red. There is no voice broadcast at this time. After the user completes the payment through fingerprint or payment password, the corresponding order status changes to payment success. The updated order status is immediately pushed to the display module by the system, and the status is displayed in green on the display module interface, and the successfully paid order amount is broadcast. During use, if there are abnormal situations such as network disconnection, the display module will give an abnormal prompt to remind the user to deal with the abnormality. If the order data is abnormal due to network disconnection or other reasons, the system will pull the latest data in time after returning to normal.

[0031] In the description of the present invention, unless otherwise expressly specified or limited, the terms "mounted," "connected," and "connected" should be understood in a broad sense. For example, they may refer to a fixed connection, an indirect connection via an intermediate medium, internal communication between two components, or an interaction between two components. Those skilled in the art will understand the specific meanings of these terms in the present invention based on specific circumstances.

[0032] In the description of the present invention, the terms "upper", "lower", "front", "back", "vertical", "horizontal", "top", "bottom", "inside", "outside", etc., indicating the orientation or position relationship, are based on the orientation or position relationship shown in the accompanying drawings. They are only for the convenience of describing the present invention and simplifying the description, and do not indicate or imply that the device or element referred to must have a specific orientation, be constructed and operate in a specific orientation. Therefore, they should not be understood as limiting the present invention.

[0033] The terms "first," "second," and "third" (if any) in the description and claims of the present invention and the accompanying drawings are used to distinguish similar objects and are not necessarily used to describe a particular order or precedence. It should be understood that the terms used in this manner are interchangeable where appropriate, so that the embodiments of the present invention described can be practiced in orders other than those illustrated or described herein.

[0034] In addition, the terms "comprises" and "having" and any variations thereof are intended to cover a non-exclusive inclusion. For example, a process, method, system, product or service tool that includes a series of steps or elements is not necessarily limited to those steps or elements expressly listed but may include other steps or elements not expressly listed or inherent to such process, method, product or service tool.

[0035] Finally, it should be noted that the contents of the above embodiments are only used to illustrate the technical solutions of the present invention, rather than to limit the same. Although the present invention has been described in detail with reference to the aforementioned embodiments, it should be understood by those skilled in the art that, without departing from the structure of the present invention, several variations and improvements can be made, which should also be regarded as within the scope of protection of the present invention, and will not affect the effect of the implementation of the present invention and the practicality of the patent.

Claims

1. A multi-dimensional payment status perception system, characterized by: It includes a display module, which provides interactive information display for customers and merchants; Payment status synchronization module, the payment status synchronization module continuously communicates with the payment platform server through a long connection mechanism, establishes a TCP connection through a three-way handshake, and the connection will remain continuously open to provide a channel for subsequent payment data transmission. The connection channel can continuously exchange data packets without the need to re-establish the connection for each communication. The payment status synchronization module regularly sends empty data packets to the payment platform server through a heartbeat mechanism to detect link activity and prevent forced disconnection. When the payment status synchronization module detects a connection interruption, it automatically triggers a reconnection mechanism to restore the communication link, obtain payment results in real time, and trigger information updates on the display module to ensure that the display interface of the display module is updated synchronously with the payment status.

2. The multi-dimensional payment status perception system according to claim 1, characterized in that: The mechanism layer of the long connection mechanism includes: control layer, protocol layer and network layer; The control layer performs active maintenance of long connections and event-driven payment status. The control layer sends heartbeat packets regularly to maintain connection activity. After receiving the heartbeat packet from the payment platform server, it confirms the link availability, receives real-time status notifications from the payment platform, and triggers order updates on the display module. If the payment platform server fails to respond due to network delay timeout, reconnection is triggered. The protocol layer defines the communication protocol format and handles the encryption / decryption and distribution of data packets, including a sending end and a receiving end. The sending end encapsulates the protocol header and the body, generates a protocol packet, and sends a binary data stream. The receiving end receives the protocol header, parses the packet header to verify the legitimacy of the protocol header, receives the body if the verification passes, generates a protocol packet, decrypts the protocol packet, and distributes the protocol packet according to the packet type. The network layer handles the sending and receiving of the underlying data stream and is divided into a sending queue and a receiving queue. The network layer stores the protocol packets generated by the protocol layer into the sending queue according to priority, and writes the data to the corresponding connection channel through the asynchronous IO thread. The network layer asynchronously reads the data stream from the connection channel, reorganizes it into complete protocol packets in sequence to form a receiving queue, and the receiving queue data packets are submitted to the protocol layer for parsing according to priority.

3. The multi-dimensional payment status perception system according to claim 2, characterized in that: The control layer is composed of a heartbeat maintenance unit, a reconnection control unit and an event-driven unit. The heartbeat maintenance unit is used to send heartbeat packets, perform response detection on returned heartbeat packets, and dynamically adjust the heartbeat interval based on network delay. The reconnection control unit is used to handle connection anomalies, monitor heartbeat return anomalies and payment status event anomalies triggered by the heartbeat maintenance unit, immediately reconnect for the first disconnection, perform time-delayed connections for subsequent reconnections, and reset the heartbeat interval and synchronize unconfirmed payment status after successful reconnection; The event-driven unit coordinates the responses of each module based on the publish-subscribe model, dynamically selects the distribution path according to the event type, pushes payment events to the display module and inserts them into the priority processing queue, and network delay events trigger cross-module collaboration. For example, a successful reconnection event will synchronously wake up the heartbeat maintenance unit to reset the heartbeat interval.

4. The multi-dimensional payment status perception system according to claim 2, characterized in that: The sending end of the protocol layer is composed of a protocol header encapsulation unit, a body encapsulation unit and a data encryption unit. The protocol header encapsulation unit converts the data into a binary stream according to the field order of packet type, data length, timestamp and check code, calculates the check code and fills it into the end of the protocol header, and outputs the protocol header binary data; The Body encapsulation unit is responsible for converting service data into a standardized binary format, using TLV encoding to generate TLV triples according to the service field definition, sequentially splicing all TLV structures into a binary stream, recording the total length and submitting it to the protocol header encapsulation unit. The protocol header encapsulation unit fills the data length field accordingly to ensure that the header and body strictly match; The data encryption unit performs end-to-end protection on the Body data.

5. The multi-dimensional payment status perception system according to claim 2, characterized in that: The network layer consists of a sending queue management unit, an asynchronous I / O core unit, and a receiving queue processing unit. The sending queue management unit dynamically adjusts the priority of data packets through multi-level feedback, giving payment events the highest priority and preemptively processing them. It also lists heartbeat packets as ordinary queues. When the sending queue times out, it automatically downgrades the priority of the data packet and retries. If three consecutive failures occur, the reconnection control unit triggers the connection reestablishment process. The asynchronous I / O core unit manages the read and write operations of all connection channels through multiplexing connections, separating the high-priority payment data channel from the heartbeat data channel. When it detects that payment data is ready, it immediately interrupts the current low-priority task and prioritizes the data transmission of the payment channel. If two consecutive I / O operation timeouts occur on the same channel, the channel is automatically marked as abnormal. The event-driven unit publishes a network interruption event to trigger the reconnection process. After the reconnection is successful, the receiving queue prioritizes the backlog of unconfirmed payment data to ensure state synchronization. The receiving queue processing unit marks the payment data packet as high-priority verification according to the protocol header type, and marks the heartbeat packet as ordinary verification. The high-priority verification is directly assigned to the protocol layer receiving end for verification and decryption. If it is detected that the data packet verification fails continuously, the link detection of the reconnection control unit is triggered. The heartbeat packet is submitted to the heartbeat maintenance unit after verification, and all successfully processed data packets are timestamped.

6. The multi-dimensional payment status perception system according to claim 1, characterized in that: The display module includes a merchant display unit facing merchants and a customer display unit facing customers. The merchant display unit displays the current order queue in real time, including the order amount, order waiting time for payment and payment status; the customer display unit displays the customer's order content, order amount and generated payment QR code in real time.

7. The multi-dimensional payment status perception system according to claim 6, characterized in that: The payment status is distinguished by differential marks into pending payment, paid and cancelled payment status.

8. The multi-dimensional payment status perception system according to claim 6, characterized in that: The display module also includes a voice broadcast module. After the payment status is updated to paid, the voice broadcast module plays a preset voice template through a built-in speaker. The voice broadcast module supports volume adjustment and voice content customization.

Images