Message sending method, message processing method, message processing system and device

Abstract

This application discloses a message sending method, message processing method, message processing system, and apparatus, relating to the field of financial technology. The method includes: obtaining a target merchant ID through a message push component; determining the geographical location of the target merchant's payment terminal through the message push component; determining a target message receiving component for receiving messages based on the geographical location of the payment terminal and the target merchant ID through the message push component; establishing a data connection between the message push component and the target message receiving component; and sending the user payment result determined by the payment terminal to the target message receiving component through the message push component according to the data connection. This application solves the technical problem in the prior art where the excessively long data transmission link of transaction information leads to merchant cashiers being unable to obtain payment notifications via voice, or causing delays in payment notifications.

Description

Technical Field

[0001] This application relates to the field of financial technology, and more specifically, to a message sending method, a message processing method, a message processing system, and an apparatus. Background Technology

[0002] In the current payment ecosystem, with the widespread adoption of mobile payments, merchant voice notification apps, as a convenient payment notification tool, are widely used in various industries such as retail and catering. However, traditional voice notification mechanisms rely on multi-layered data transmission links. From the acquiring system to the merchant voice notification app, the data needs to pass through multiple backend systems and network nodes. This link typically involves the acquiring system sending the payment result to a message service node, which then pushes the transaction information in text form to the merchant voice notification app via the network. Finally, the app reads the text and converts it into a voice notification.

[0003] In this complex data transmission process, any anomaly at any stage, such as network fluctuations, server failures, or system delays, can interrupt or delay the transmission of transaction information. This risk not only affects the immediacy of payment confirmation but may also cause merchant cashiers to miss important payment notifications, thereby impacting merchant operational efficiency and customer payment experience. Especially during peak hours, a large number of payment transactions occur in rapid succession, increasing the pressure on the back-end system to process messages and making message push delays even more prominent, becoming a key bottleneck restricting the efficiency of the payment process.

[0004] There is currently no effective solution to the above problems. Summary of the Invention

[0005] This application provides a message sending method, message processing method, message processing system, and apparatus to at least solve the technical problem in the prior art where, due to the excessively long data transmission link of transaction information, any abnormality at any stage can cause messages to fail to be sent to the merchant's mobile client, resulting in merchant cashiers being unable to obtain payment notifications via voice or experiencing delays in payment notifications.

[0006] According to one aspect of this application, a message sending method is provided, comprising: obtaining a target merchant number through a message push component, wherein the target merchant number is a merchant identifier assigned to the message push component by the target merchant's payment terminal after detecting that a user has scanned a payment graphic code; determining the geographical location of the target merchant's payment terminal through the message push component; determining a target message receiving component for receiving messages based on the geographical location of the payment terminal and the target merchant number through the message push component; establishing a data connection between the message push component and the target message receiving component; and sending the user payment result determined by the payment terminal to the target message receiving component through the message push component according to the data connection, wherein the target message receiving component is used to generate voice information based on the user payment result.

[0007] Optionally, determining the geographical location of the target merchant's payment terminal through a push notification component includes: sending a location acquisition request to the target merchant's payment terminal through the push notification component, wherein the location acquisition request is used to request the payment terminal to grant location determination permission to the push notification component; and after detecting that the payment terminal agrees to the location acquisition request, reading the geographical location of the payment terminal through the push notification component.

[0008] Optionally, the message push component determines the target message receiving component based on the geographical location of the payment terminal, including: obtaining access permissions to the map software program built into the payment terminal through the message push component; based on the map software program, using the geographical location of the payment terminal as the center position, expanding outward by a preset distance along the target direction and / or target angle to obtain a search range; determining N message receiving components within the search range that already carry merchant numbers as N candidate message receiving components, where N is an integer greater than or equal to 1; and determining the target message receiving component from the N candidate message receiving components based on the target merchant number.

[0009] Optionally, the target message receiving component is determined from N candidate message receiving components based on the target merchant number, including: sending the target merchant number to the N candidate message receiving components through a message push component, wherein each candidate message receiving component verifies whether the merchant number it carries is the target merchant number and sends the verification result to the message push component; the candidate message receiving component that reports that the merchant number it carries is the target merchant number is selected as the target message receiving component through the message push component.

[0010] Optionally, establishing a data connection between the message push component and the target message receiving component includes: sending a data connection establishment request to the target message receiving component through the message push component; and establishing a data connection between the message push component and the target message receiving component after receiving a reply from the target message receiving component agreeing to establish a data connection.

[0011] Optionally, after sending the user payment result determined by the payment terminal to the target message receiving component based on the data connection via the message push component, the message sending method further includes: disconnecting the data connection via the message push component after determining that the target message receiving component has received the user payment result.

[0012] According to another aspect of this application, a message processing method is also provided, comprising: receiving a target merchant number sent by a message push component through a target message receiving component, and establishing a data connection between the message push component and the target message receiving component, wherein the target merchant number is a merchant identifier assigned to the message push component by the target merchant's payment terminal after detecting that a user has scanned a payment graphic code; the target message receiving component is determined by the geographical location of the payment terminal and the target merchant number; receiving, through the target message receiving component, a user payment result determined by the payment terminal and sent by the message push component according to the data connection; and generating voice information through the target message receiving component based on the user payment result.

[0013] According to another aspect of this application, a message processing system is also provided, comprising: a payment terminal, configured to send a target merchant code to a message push component after detecting that a user has scanned a payment graphic code, wherein the target merchant code is a merchant identifier of the target merchant; a message push component, configured to determine the geographical location of the payment terminal, and determine a target message receiving component for receiving messages based on the geographical location of the payment terminal and the target merchant code; and a target message receiving component, configured to establish a data connection with the message push component, receive a user payment result determined by the payment terminal and sent by the message push component based on the data connection, and generate voice information based on the user payment result.

[0014] According to another aspect of this application, a message sending device is also provided, comprising: a first acquisition unit for acquiring a target merchant number through a message push component, wherein the target merchant number is a merchant identifier assigned to the message push component by the target merchant's payment terminal after detecting that a user has scanned a payment graphic code; a first determination unit for determining the geographical location of the target merchant's payment terminal through the message push component; a second determination unit for determining a target message receiving component for receiving messages based on the geographical location of the payment terminal and the target merchant number through the message push component; a first establishment unit for establishing a data connection between the message push component and the target message receiving component; and a third determination unit for sending the user payment result determined by the payment terminal to the target message receiving component through the message push component according to the data connection, wherein the target message receiving component is used to generate voice information based on the user payment result.

[0015] According to another aspect of this application, a message sending apparatus is also provided, comprising: a sending unit, which receives a target merchant number sent by a message push component through a target message receiving component, and establishes a data connection between the message push component and the target message receiving component, wherein the target merchant number is a merchant identifier assigned to the message push component by the target merchant's payment terminal after detecting that a user has scanned a payment graphic code; the target message receiving component is determined by the geographical location of the payment terminal and the target merchant number; a receiving unit, which receives a user payment result determined by the payment terminal and sent by the message push component according to the data connection through the target message receiving component; and a generating unit, which generates voice information based on the user payment result through the target message receiving component.

[0016] According to another aspect of this application, a computer-readable storage medium is also provided, which includes a stored executable program, wherein the executable program controls the device where the computer-readable storage medium is located to perform the above-described method when it is running.

[0017] According to another aspect of this application, an electronic device is also provided, including one or more processors and a memory, the memory being used to store one or more programs, wherein when the one or more programs are executed by the one or more processors, the one or more processors cause the one or more processors to perform the message sending method or the message processing method described above.

[0018] According to another aspect of this application, a computer program product is also provided, including computer instructions that, when executed by a processor, implement the steps of the above-described method.

[0019] In this application, the target merchant ID is first obtained through a message push component. This target merchant ID is the merchant identifier assigned to the message push component by the target merchant's payment terminal after detecting a user scanning a payment graphic code. Next, the geographical location of the target merchant's payment terminal is determined through the message push component. Then, based on the geographical location of the payment terminal and the target merchant ID, the target message receiving component is determined. A data connection is then established between the message push component and the target message receiving component. Finally, the user's payment result, determined by the payment terminal, is sent to the target message receiving component through the data connection via the message push component. The target message receiving component generates voice information based on the user's payment result. This point-to-point instant messaging mechanism shortens the transaction information transmission path, achieving the technical effect of instant and accurate voice payment notification. This solves the technical problem in existing technologies where excessively long data transmission links for transaction information can lead to anomalies at any stage, resulting in messages failing to reach the merchant's mobile client, causing cashiers to be unable to receive payment notifications via voice, or experiencing delays in payment notifications. Attached Figure Description

[0020] The drawings described herein are used to provide a further understanding of the present application and constitute a part of the present application. The illustrative embodiments of the present application and their descriptions are used to explain the present application and do not constitute an improper limitation on the present application. In the drawings:

[0021] Figure 1 This is a flowchart of an optional message sending method according to an embodiment of this application;

[0022] Figure 2 This is a schematic diagram of an optional payment collection and checkout H5 structure according to an embodiment of this application;

[0023] Figure 3 This is a schematic diagram of an optional merchant voice broadcast APP structure according to an embodiment of this application;

[0024] Figure 4 This is a schematic diagram of an optional merchant login merchant voice broadcast APP according to an embodiment of this application;

[0025] Figure 5 This is a schematic diagram of an optional handshake connection during the customer payment stage according to an embodiment of this application;

[0026] Figure 6 This is a schematic diagram of message broadcasting during an optional customer payment stage according to an embodiment of this application;

[0027] Figure 7 This is a flowchart of an optional message processing method according to an embodiment of this application;

[0028] Figure 8 This is a schematic diagram of an optional message sending device according to an embodiment of this application;

[0029] Figure 9 This is a schematic diagram of an optional message processing apparatus according to an embodiment of this application. Detailed Implementation

[0030] In order to enable those skilled in the art to better understand the present invention, the following will clearly and completely describe the technical solutions in the embodiments of the present invention in conjunction with the drawings in the embodiments of the present invention. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments in the present invention, all other embodiments obtained by ordinary technicians in this field without making creative efforts should fall within the scope of protection of this application.

[0031] It should be noted that the terms "first," "second," etc., in the specification, claims, and accompanying drawings of this application are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that such data can be interchanged where appropriate so that the embodiments of this application described herein can be implemented in orders other than those illustrated or described herein. Furthermore, the terms "comprising" and "having," and any variations thereof, are intended to cover non-exclusive inclusion; for example, a process, method, system, product, or apparatus that comprises a series of steps or units is not necessarily limited to those steps or units explicitly listed, but may include other steps or units not explicitly listed or inherent to such processes, methods, products, or apparatus.

[0032] It should be noted that the information collected in this application (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for display, data used for analysis, etc.) are information and data authorized by the user or fully authorized by all parties. Furthermore, the collection, storage, use, processing, transmission, provision, disclosure, and application of this data all comply with relevant laws, regulations, and standards, necessary confidentiality measures have been taken, and they do not violate public order and good morals. Corresponding access points are provided for users to choose to authorize or refuse. For example, interfaces are set up between this system and relevant users or organizations, providing users with corresponding access points to choose to agree to or refuse automated decision-making results; if the user chooses to refuse, the process proceeds to the expert decision-making stage.

[0033] According to an embodiment of this application, a method embodiment for sending a message is provided. It should be noted that the steps shown in the flowchart in the accompanying drawings can be executed in a computer system such as a set of computer-executable instructions. Furthermore, although a logical order is shown in the flowchart, in some cases, the steps shown or described may be executed in a different order than that shown here.

[0034] Figure 1 This is a flowchart of an optional message sending method according to an embodiment of this application, such as... Figure 1 As shown, the method includes the following steps:

[0035] Step S101: Obtain the target merchant ID through the message push component.

[0036] In step S101, after detecting that the user has scanned the payment graphic code, the payment terminal with the target merchant number assigns a merchant identifier to the message push component.

[0037] It should be noted that the message push component can serve as the execution subject of the message sending method in this application embodiment. It is understood that the message sending method provided in this application embodiment can also be executed by other systems or devices, and this application embodiment does not specifically limit this.

[0038] Optionally, the message push component can be an SDK (Software Development Kit) integrated into the acquiring cashier H5 (a web application provided by the acquiring institution and embedded in the merchant's payment QR code). The acquiring cashier refers to the acquiring institution's payment H5 page called by the payment APP when a customer scans the merchant's payment QR code. On this payment H5 page, the customer enters the amount and payment password and submits the payment to complete the transaction.

[0039] Optionally, the target merchant ID is a unique identifier for a specific merchant in a payment transaction. It is key information for matching between the push and receive message components.

[0040] Step S102: Determine the geographical location of the target merchant's payment terminal through the message push component.

[0041] Optionally, before the customer completes the payment, the push notification component can obtain the real-time location information of the payment terminal by accessing the phone's map location permissions. This step narrows the search scope, allowing the push notification component to quickly locate the target message receiving component.

[0042] Step S103: Using the message push component, determine the target message receiving component for the message to be received based on the geographical location of the payment terminal and the target merchant number.

[0043] Optionally, a message push component can be used to determine nearby target message receiving components based on the geographical location of the payment terminal and the target merchant number.

[0044] Optionally, the target message receiving component can be integrated into the merchant's voice broadcast app. After a customer completes a payment at a merchant, the customer notifies the merchant's acquiring institution of the payment result. After processing the main transaction process, the acquiring institution sends the transaction result to the merchant's voice broadcast app installed on the merchant's mobile phone. At the same time, the acquiring institution's system backend pushes a broadcast notification to the merchant's voice broadcast app, informing the merchant that the payment has been completed and the payment amount.

[0045] Step S104: Establish a data connection between the message push component and the target message receiving component.

[0046] Optionally, after identifying the target message receiving component, the message push component sends a handshake connection request. Upon the target message receiving component's response, a data connection is established between the two parties. It should be noted that this connection is point-to-point, established directly between the front-end components, avoiding potential delays or failures during transmission in the back-end system, thus improving the efficiency and reliability of information transmission.

[0047] Step S105: The user payment result determined by the payment terminal is sent to the target message receiving component through the message push component based on the data connection.

[0048] In step S105, the target message receiving component is used to generate voice information based on the user's payment result.

[0049] Optionally, once the data connection is established, the message push component will send payment success information, including the payment result and payment amount, to the target message receiving component via the data connection. After receiving the information, the target message receiving component will generate a voice announcement based on the payment result, informing the merchant cashier that the transaction has been completed and the specific amount, thus realizing an instant voice notification function.

[0050] Optionally, Figure 2 This is a schematic diagram of an optional payment collection and checkout H5 structure according to an embodiment of this application, as shown below. Figure 2As shown, the H5 payment POS terminal integrates modules such as a password input module, an encryption module, a message sending module, other modules (functional modules), and a message push SDK. The password input module is primarily responsible for the customer's password input during the payment process. After purchasing goods or services, the customer needs to enter their payment password or confirm the payment amount on the H5 payment POS terminal to complete the payment process. The encryption module encrypts the payment information entered by the customer (including the payment amount and payment password) to ensure the security of sensitive information during transmission. Encryption is a crucial step in network security, preventing information from being intercepted or tampered with by third parties during transmission. After payment confirmation, the message sending module is responsible for constructing and sending a transaction message containing the payment result and payment amount. These messages are sent to the message push SDK for further processing and push notifications. Other modules represent other functional modules in the H5 payment POS terminal besides the three modules mentioned above. These may include user interface management, payment confirmation logic, error handling, etc., ensuring the normal operation of the H5 payment POS terminal and the smooth completion of the payment process. The message push SDK is integrated into the payment POS terminal... The software development kit (SDK) in the H5 platform is used to implement point-to-point message push functionality. It includes the following key functions: Setting Merchant ID: The message push SDK first needs to set the target merchant's ID to correctly push messages to the target merchant's payment terminal; Obtaining Mobile Phone Location: To ensure messages are pushed to the correct payment terminal, the SDK needs to obtain the real-time geographical location information of the mobile phone where the H5 platform is located; Sending Handshake Connection Request: The SDK sends a handshake connection request to nearby merchant voice broadcast apps to find payment terminals related to the current payment transaction; Establishing Connection: After receiving the merchant voice broadcast app's consent response, the message push SDK establishes a communication connection with the target message receiving SDK, preparing the necessary communication link for message push; Pushing Message Broadcast Message: Finally, the message push SDK pushes a message including the payment result and payment amount to the target message receiving SDK, which is used to generate a voice notification in the merchant voice broadcast app.

[0051] Optionally, Figure 3 This is a schematic diagram of an optional merchant voice broadcast APP structure according to an embodiment of this application, such as... Figure 3As shown in the diagram, this schematic includes a login module, a voice broadcast module, a message receiving module, other modules, and a message receiving SDK. The login module is the entry point for the merchant's voice broadcast app, allowing cashiers to log in and access the app's functions by entering a username and password. The login module ensures that only authorized users can use the app, improving system security. The voice broadcast module converts the payment result into a voice notification upon receiving transaction information, allowing cashiers to hear immediate payment confirmation. This module uses speech synthesis technology or pre-built voice files to generate corresponding voice information based on the payment status and amount. The message receiving module receives transaction messages pushed by the message push SDK in the acquiring cashier H5. It acts as the receiving end in the communication between the message receiving SDK and the cashier, ensuring that transaction information can be captured and processed by the app. The Message Receiving SDK is a key component in the merchant's voice broadcast app, used to achieve point-to-point reception of transaction information at the front end. Its functions include: setting the merchant ID: The Message Receiving SDK needs to match the merchant ID in the Message Push SDK to ensure that the received information is for the current merchant; obtaining the mobile phone's location: Similar to the Message Push SDK, the Message Receiving SDK also needs to obtain the mobile phone's geographical location information in real time so as to determine the identity of the recipient when the payment terminal H5 sends a connection request; responding to the connection request: When receiving a connection request from the Message Push SDK, the Message Receiving SDK will check the merchant ID in the request. If it matches, it will respond to agree; otherwise, it will refuse the connection; receiving the broadcast message: Once a connection is established with the Message Push SDK, the Message Receiving SDK will receive the transaction message containing the payment result and payment amount; calling the broadcast module for voice broadcast: Finally, the Message Receiving SDK sends the received payment result to the voice broadcast module, generates a voice notification, and plays it to the merchant cashier.

[0052] Optionally, Figure 4 This is a schematic diagram of an optional merchant login merchant voice broadcast APP according to an embodiment of this application, such as... Figure 4As shown, the first step is for the merchant cashier to enter their username and password. This is the beginning of the login process, requiring the user to enter their registered account and password on the merchant's voice broadcast app to verify their identity. This is the first line of defense to ensure that only authorized cashiers can access the app's functions. The second step involves calling the message receiving SDK method to assign a merchant ID to the SDK: Once authentication is successful, the merchant's voice broadcast app will call the corresponding method in the message receiving SDK to set the app's merchant ID. This step is crucial for point-to-point communication, ensuring that subsequent transaction information associated with that merchant ID can be received. The third step involves requesting location permissions: To support location-based communication, the app needs to obtain the phone's map location permissions. This requires the cashier to agree to allow the app to access their location information in order to... Upon receiving a transaction notification, the recipient can be identified based on geographical location; Step 4: Agree to obtain phone location permissions: Cashiers need to explicitly agree to the APP obtaining location information to ensure that the APP follows the user's wishes when processing sensitive information; Step 5: Real-time acquisition of phone location: Once location permissions are obtained, the APP will track and update the phone's location in real time. This is to quickly identify nearby merchant cashiers after the customer completes payment and push voice notifications to them; Step 6: Activate the connection request receiving interface: After completing all the above settings, the message receiving SDK will be in listening mode, ready to receive connection requests from the acquiring cashier H5 message push SDK. This is a preparatory step to establish a point-to-point communication link, ensuring that cashiers can receive transaction notifications from the payment site in a timely manner.

[0053] As can be seen from steps S101 to S105, in this application, the target merchant number is first obtained through the message push component. The target merchant number is the merchant identifier assigned to the message push component by the target merchant's payment terminal after detecting a user scanning a payment graphic code. Next, the geographical location of the target merchant's payment terminal is determined through the message push component. Then, based on the geographical location of the payment terminal and the target merchant number, the target message receiving component is determined. A data connection is then established between the message push component and the target message receiving component. Finally, the user payment result determined by the payment terminal is sent to the target message receiving component through the data connection via the message push component. The target message receiving component generates voice information based on the user payment result. This achieves the goal of shortening the transaction information transmission path through a point-to-point instant messaging mechanism, thereby realizing the technical effect of instant and accurate voice payment notification. This solves the technical problem in the prior art where, due to the excessively long data transmission link of transaction information, any abnormality at any stage can cause messages to fail to be sent to the merchant's mobile client, resulting in merchant cashiers being unable to obtain payment notifications via voice or experiencing delays in payment notifications.

[0054] In one optional embodiment, a location acquisition request is sent to the target merchant's payment terminal via a message push component. The location acquisition request is used to request the payment terminal to grant location determination permission to the message push component. After detecting that the payment terminal agrees to the location acquisition request, the geographical location of the payment terminal is read via the message push component.

[0055] Optionally, before the customer begins the payment process, the push notification component sends a location acquisition request to the target merchant's payment terminal. This request is achieved by calling the location function module in the payment terminal's H5 interface. The purpose is to activate the payment terminal's location service and obtain its current geographical location information so that, after successful payment, the system can quickly locate the target message receiving component that is geographically close to the payment terminal.

[0056] Optionally, after the push notification component sends a location acquisition request to the target merchant's payment terminal, the payment terminal will decide whether to grant the push notification component location access permission. This is achieved through the location permission management mechanism provided by the mobile operating system, which ensures user privacy while allowing the application to obtain necessary geographic location information. After detecting that the payment terminal agrees to the location acquisition request, the push notification component will detect this consent signal. The detection mechanism is usually implemented through a callback function or listener. Once the payment terminal agrees, the push notification component will start to obtain its geographic location information in real time.

[0057] As described above, at the start of a payment process, the message push component sends a location acquisition request to the receiving terminal, requesting permission to access its location. After the receiving terminal agrees, its geographical location is read, thus achieving accurate acquisition of geographical location in the front-end point-to-point message transmission mechanism. This process ensures that the message push component can accurately identify target message receiving components geographically close to the receiving terminal, thereby immediately pushing a voice announcement message to them after successful payment. This improves the immediacy and accuracy of payment notifications while effectively avoiding potential delays and stability issues in the back-end system transmission.

[0058] In one optional embodiment, access to the map software program built into the payment terminal is obtained through the message push component. Then, according to the map software program, the search range is obtained by expanding a preset distance outward along the target direction and / or target angle, with the geographical location of the payment terminal as the center position. N message receiving components that carry merchant numbers within the search range are selected as N candidate message receiving components, where N is an integer greater than or equal to 1. Then, the target message receiving component is determined from the N candidate message receiving components according to the target merchant number.

[0059] Optionally, when a customer begins the payment process by scanning the merchant's payment QR code, the push notification component integrated into the payment terminal's H5 interface immediately requests permission to access the map software program built into the payment terminal. This request aims to obtain location services to determine the accurate geographical location of the payment terminal. Access to the map software program is fundamental to implementing point-to-point push notifications; it allows the push notification component to obtain the phone's location information in real time, which is a prerequisite for subsequent functions.

[0060] Optionally, after obtaining location service permissions, the push notification component will construct a search range based on the current geographical location of the payment terminal as the center, extending outwards by a preset distance along a preset target direction and / or target angle. This search range is dynamic and can be parameterized according to the actual application scenario; for example, it may be set to a smaller range in a busy commercial area and a larger range in an open area. The definition of the search range ensures that the push notification component can efficiently search for nearby target message receiving components, reducing unnecessary searches and connection establishment, and improving the system's response speed and resource utilization efficiency. After defining the search range, the push notification component will search for all N message receiving components carrying valid merchant IDs within the range and use them as candidate message receiving components. Finally, the push notification component will select a unique target message receiving component from the N candidate message receiving components based on the target merchant ID of the current transaction.

[0061] As described above, the combined use of the message push component and map software program enables accurate identification and efficient connection to nearby message receiving components. This not only improves the success rate and response speed of message pushes but also ensures message accuracy and security, avoiding the delays and errors that may be introduced by traditional backend systems' layer-by-layer message push. By dynamically constructing the search range and filtering target message receiving components, this embodiment provides a more flexible and reliable point-to-point transmission mechanism for payment notifications, significantly improving the work efficiency of merchant cashiers in busy checkout environments and enhancing the customer payment experience.

[0062] In one optional embodiment, the target merchant ID is sent to N alternative message receiving components via a message push component. Each alternative message receiving component checks whether the merchant ID it carries is the target merchant ID and sends the verification result to the message push component. The message push component then selects the alternative message receiving component that reports that its merchant ID is the target merchant ID as the target message receiving component.

[0063] Optionally, the message push component broadcasts the target merchant number (i.e., the merchant information to which the current payment transaction belongs) to all message receiving components within the search range, i.e., N candidate message receiving components. After receiving the target merchant number, each candidate message receiving component checks its own pre-set merchant number to see if it matches the target merchant number. This is to ensure that the message is accurately sent to the payment terminal related to the current payment. After verification, each candidate message receiving component feeds back the verification result to the message push component, indicating whether it belongs to the target merchant. This feedback mechanism is an important part of two-way communication, enabling the message push component to take the next step based on the feedback information. Based on the received verification result, the message push component filters out the message receiving components that match the target merchant number and identifies them as the target message receiving component. This filtering process ensures that the transaction message is only sent to the correct payment terminal, avoiding mistransmission of information.

[0064] As described above, by implementing the steps outlined, this embodiment provides a reliable and efficient message push mechanism, ensuring accurate transmission of transaction information from the payment terminal (message push component) to the merchant's voice broadcast app (message receiving component). This mechanism reduces the latency of message processing in the backend system, avoids information transmission failures due to system node malfunctions, and enhances message security and privacy, as only payment terminals matching the target merchant's ID can receive the transaction information. Furthermore, the direct verification and selection process at the front end makes voice broadcast notifications more timely and accurate, effectively improving the efficiency of the merchant's payment process and user experience. This embodiment demonstrates the application potential of front-end technology in the field of payment notifications, providing merchants with a more intelligent and convenient method for payment confirmation.

[0065] In one optional embodiment, the message push component sends a data connection establishment request to the target message receiving component, and then, after receiving a reply from the target message receiving component agreeing to establish a data connection, a data connection is established between the message push component and the target message receiving component.

[0066] Optionally, at the moment of payment confirmation, the message push component immediately sends a data connection establishment request to the target message receiving component. The purpose of this request is to establish a stable communication channel to directly transmit the voice broadcast information of payment success between the payment POS H5 and the merchant voice broadcast APP. After receiving the target message receiving component's reply agreeing to establish a data connection, the message push component immediately establishes a data connection with the target message receiving component. This connection is point-to-point, bypassing the complex process of multi-layer message push in traditional back-end systems, ensuring the immediacy and reliability of information transmission. After the connection is established, the message push component begins to send messages broadcasting the transaction result.

[0067] Optionally, Figure 5 This is a schematic diagram of an optional handshake connection during the customer payment stage according to an embodiment of this application, such as... Figure 5 As shown, Step 1: Customer scans merchant's QR code: The payment process begins when the customer scans the merchant's QR code using their payment app. The QR code contains the merchant's unique identifier, used to identify which merchant the payment should be sent to. Step 2: Cashier H5 sends merchant ID to push notification SDK: After the customer scans the QR code, the push notification SDK in the cashier H5 uses the merchant ID parsed from the QR code as a parameter for subsequent point-to-point message sending. Step 3: Push notification SDK requests location permissions from customer: To determine the cashier's real-time location, the push notification SDK needs to obtain the phone's map location permissions. In order to search and determine the nearest merchant cashier's mobile phone; Step 4: Customer agrees to obtain mobile phone location permission: The customer needs to confirm and allow the cashier H5 to obtain their location information on their mobile phone. This is to ensure the customer's privacy and data security, and is also a necessary condition for realizing point-to-point message transmission; Step 5: Message push SDK obtains location and notifies nearby message receiving SDK: After obtaining the mobile phone's location permission, the message push SDK will monitor and obtain the mobile phone's geographical location information in real time, and then send a handshake connection request to the message receiving SDK integrated in the nearby merchant voice broadcast APP (e.g., within 50 meters); Step 6 Step 7: The message receiving SDK requests a random connection: When the message push SDK sends a connection request, the message receiving SDK in the nearby merchant's voice broadcast app will attempt to establish a connection. "Random connection" here refers to randomly selecting one SDK from multiple connectable SDKs to improve system fault tolerance and efficiency. Step 8: The message push SDK verifies the merchant ID in the connection request: After receiving the connection request, the message push SDK checks the requester's merchant ID to ensure it matches the merchant ID of the current payment transaction, preventing incorrect connections or error messages. Step 9: Request for "Agree": If the merchant ID in the connection request matches the merchant ID of the push notification SDK, the push notification SDK will return "Agree," allowing the connection to be established; otherwise, it will return "Reject." Step 1: Push notification SDK returns "Agree" for matching merchant IDs: If the merchant ID in the connection request matches the merchant ID of the push notification SDK, the push notification SDK will return "Agree," allowing the connection to be established. At this point, the push notification SDK and the message receiving SDK have completed their handshake connection for merchants with the same merchant ID; otherwise, it will return "Reject." It should be noted that the push notification SDK can establish connections with multiple message receiving SDKs simultaneously.

[0068] As shown above, by establishing a direct data connection and pushing information between the message push component and the target message receiving component, real-time voice notification of payment results is achieved, greatly improving the efficiency and reliability of payment confirmation information transmission. The point-to-point connection mechanism avoids the latency and stability issues that may be encountered in traditional backend system message pushes, ensuring the synchronization of payment results and voice notifications, and enhancing transaction transparency and user experience.

[0069] In an alternative embodiment, after determining that the target message receiving component has received the user's payment result, the data connection is disconnected via the message push component.

[0070] Optionally, once the user completes the payment and the payment confirmation is received by the H5 payment terminal, the message push component will be triggered to send the payment result and payment amount to the target message receiving component. During the connection establishment between the message push component and the target message receiving component, the message push component will continuously monitor the connection status to confirm whether the message has been successfully delivered. This monitoring function is implemented through the communication status management module within the message push component of the H5 payment terminal, ensuring the reliability and integrity of the message transmission process. Once the message push component confirms that the target message receiving component has successfully received the user's payment result, it will immediately perform a disconnection operation. This operation is implemented through the connection management module within the message push component, which is responsible for terminating the communication session with the target message receiving component and reclaiming the occupied system resources and network bandwidth.

[0071] Optionally, Figure 6 This is a schematic diagram of an optional message broadcast during the customer payment stage according to an embodiment of this application, such as... Figure 6As shown, the customer first enters the payment amount and payment password, which is the first step in the payment process. The customer enters the specific amount and password required for payment in the acquiring POS H5 interface to confirm the payment information. After the customer completes the payment information input, the acquiring POS H5 receives this information and prepares to process the payment. The POS H5 encrypts the customer's payment information and sends it to the acquiring institution's back-end system for verification and processing to ensure the security and validity of the payment. After receiving the payment information, the back-end system begins to execute the payment logic, including steps such as verifying the payment password and checking the account balance. The POS H5 receives confirmation information from the back-end system, indicating that the payment has been successfully executed. Then... After successful payment confirmation, the POS H5 will immediately invoke the integrated push notification SDK to send a message to the message receiving SDK, notifying the payment result. Subsequently, a push notification will be sent, including the payment result and amount. The push notification SDK sends detailed payment information (including the payment result and amount) to the message receiving SDK via point-to-point communication, eliminating the need for traditional multi-layered backend system forwarding. After the push notification is complete, the push notification SDK will disconnect from the message receiving SDK, releasing resources and reclaiming connection threads to ensure system stability and efficiency. Finally, the merchant's voice broadcast app (which integrates the message receiving SDK) generates a voice notification based on the received payment information, informing the merchant cashier that the payment has been successfully completed and the specific payment amount.

[0072] As shown above, by immediately disconnecting the data connection after payment confirmation, the push notification component significantly improves the resource utilization and system response speed of the front-end peer-to-peer messaging mechanism. This avoids maintaining unnecessary connections for extended periods, reducing communication latency and network congestion risks, while also alleviating system-level burden and freeing up more resources and bandwidth for subsequent payment transactions. This optimization not only improves the efficiency of the payment process but also enhances system stability and security, providing merchants and customers with a faster and more reliable payment experience.

[0073] According to an embodiment of this application, an embodiment of a message processing method is provided. It should be noted that the steps shown in the flowchart in the accompanying drawings can be executed in a computer system such as a set of computer-executable instructions. Furthermore, although a logical order is shown in the flowchart, in some cases, the steps shown or described may be executed in a different order than that shown here.

[0074] It should be noted that the target message receiving component serves as the execution subject of the message processing method in this application embodiment. It is understood that the message processing method provided in this application embodiment can also be executed by other systems or devices, and this application embodiment does not specifically limit this.

[0075] Figure 7 This is a flowchart of an optional message processing method according to an embodiment of this application, such as... Figure 7 As shown, the method includes the following steps:

[0076] Step S701: Receive the target merchant number sent by the message push component through the target message receiving component, and establish a data connection between the message push component and the target message receiving component.

[0077] In step S701, after detecting that the user has scanned the payment graphic code, the payment terminal with the target merchant number assigns a merchant identifier to the message push component.

[0078] In step S701, the target message receiving component is determined by the geographical location of the payment terminal and the target merchant number.

[0079] Optionally, after receiving the target merchant number through the target message receiving component, a data connection is established with the message push component, enabling direct communication between the front-ends.

[0080] Step S702: Receive the user payment result determined by the payment terminal, sent by the message push component based on the data connection, through the target message receiving component.

[0081] Optionally, the payment status information determined by the payment terminal includes key data such as payment success and payment amount. This information is sent in real time to the target message receiving component by the message push component based on the data connection after payment confirmation.

[0082] Step S703: Generate voice information based on the user's payment result through the target message receiving component.

[0083] Optionally, based on the user's payment result, a voice notification generated by the target message receiving component is used to announce the payment status, such as "Payment failed, please scan the code again".

[0084] This application also provides a message processing system. It should be noted that the message processing system of this application can be used to execute the message sending method and message processing method provided in this application. The message processing system provided in this application is described below.

[0085] According to an embodiment of this application, an embodiment of a message processing system is also provided. The system includes: a payment terminal, configured to send a target merchant code to a message push component after detecting that a user has scanned a payment graphic code, wherein the target merchant code is a merchant identifier of the target merchant; a message push component, configured to determine the geographical location of the payment terminal and determine a target message receiving component for receiving messages based on the geographical location of the payment terminal and the target merchant code; and a target message receiving component, configured to establish a data connection with the message push component, receive the user payment result determined by the payment terminal and sent by the message push component based on the data connection, and generate voice information based on the user payment result.

[0086] This application also provides a message sending device. It should be noted that the message sending device of this application can be used to execute the message sending method provided in this application. The message sending device provided in this application is described below.

[0087] According to an embodiment of this application, a message sending device is also provided. Figure 8 This is a schematic diagram of an optional message sending device according to an embodiment of this application, such as... Figure 8 As shown, the device includes: a first acquisition unit 801, a first determination unit 802, a second determination unit 803, a first establishment unit 804, and a third determination unit 805.

[0088] Optionally, the first acquisition unit 801 is used to acquire the target merchant number through the message push component, wherein the target merchant number is the merchant identifier assigned to the message push component by the target merchant's payment terminal after detecting that the user has scanned the payment graphic code; the first determination unit 802 is used to determine the geographical location of the target merchant's payment terminal through the message push component; the second determination unit 803 is used to determine the target message receiving component for receiving messages based on the geographical location of the payment terminal and the target merchant number through the message push component; the first establishment unit 804 is used to establish a data connection between the message push component and the target message receiving component; and the third determination unit 805 is used to send the user payment result determined by the payment terminal to the target message receiving component through the message push component according to the data connection, wherein the target message receiving component is used to generate voice information based on the user payment result.

[0089] Optionally, the first determining unit 802 includes: a first sending subunit and a first reading subunit. The first sending subunit is configured to send a location acquisition request to the target merchant's payment terminal via a message push component, wherein the location acquisition request is used to request the payment terminal to grant location determination permission to the message push component; the first reading subunit is configured to read the geographical location of the payment terminal via the message push component after detecting that the payment terminal has agreed to the location acquisition request.

[0090] Optionally, the second determining unit 803 includes: a first acquiring subunit, a first determining subunit, a second determining subunit, and a third determining subunit. The first acquiring subunit is used to acquire access permissions to the map software program built into the payment terminal via a message push component; the first determining subunit is used to obtain a search range based on the map software program, using the geographical location of the payment terminal as the center location, and extending outwards by a preset distance along the target direction and / or target angle; the second determining subunit is used to determine N message receiving components carrying merchant numbers within the search range as N candidate message receiving components, where N is an integer greater than or equal to 1; the third determining subunit is used to determine the target message receiving component from the N candidate message receiving components based on the target merchant number.

[0091] Optionally, the third determining subunit includes: a first sending module and a first determining module. The first sending module is used to send the target merchant number to N alternative message receiving components via a message push component. Each alternative message receiving component verifies whether its own merchant number matches the target merchant number and sends the verification result to the message push component. The first determining module is used by the message push component to select the alternative message receiving component whose merchant number matches the target merchant number as the target message receiving component.

[0092] Optionally, the first establishment unit 804 includes: a second sending subunit and a first establishment subunit. The second sending subunit is used to send a data connection establishment request to the target message receiving component via the message push component; the first establishment subunit is used to establish a data connection between the message push component and the target message receiving component after receiving a reply from the target message receiving component agreeing to establish a data connection.

[0093] Optionally, the message sending device further includes a processing unit, configured to disconnect the data connection via a message push component after determining that the target message receiving component has received the user's payment result.

[0094] This application also provides a message processing apparatus. It should be noted that the message processing apparatus of this application can be used to execute the message processing method provided in this application. The message processing apparatus provided in this application will be described below.

[0095] According to an embodiment of this application, a message processing apparatus is also provided. Figure 9 This is a schematic diagram of an optional message processing apparatus according to an embodiment of this application, such as... Figure 9 As shown, the device includes: a transmitting unit 901, a receiving unit 902, and a generating unit 903.

[0096] Optionally, the sending unit 901 receives the target merchant number sent by the message push component through the target message receiving component, and establishes a data connection between the message push component and the target message receiving component. The target merchant number is the merchant identifier assigned to the message push component by the target merchant's payment terminal after detecting that a user has scanned a payment graphic code. The target message receiving component is determined by the geographical location of the payment terminal and the target merchant number. The receiving unit 902 receives the user payment result determined by the payment terminal, sent by the message push component according to the data connection, through the target message receiving component. The generating unit 903 generates voice information based on the user payment result through the target message receiving component.

[0097] According to another aspect of this application, a computer-readable storage medium is also provided, which includes a stored executable program, wherein the executable program controls the device where the computer-readable storage medium is located to perform the above-described method when it is running.

[0098] According to another aspect of this application, an electronic device is also provided, comprising: a memory storing an executable program; and a processor for running the program, wherein the program executes the methods described above when it runs.

[0099] According to another aspect of this application, a computer program product is also provided, including computer instructions that, when executed by a processor, implement the steps of the above-described method.

[0100] The sequence numbers of the embodiments in this application are for descriptive purposes only and do not represent the superiority or inferiority of the embodiments.

[0101] In the above embodiments of this application, the descriptions of each embodiment have different focuses. For parts not described in detail in a certain embodiment, please refer to the relevant descriptions of other embodiments.

[0102] In the several embodiments provided in this application, it should be understood that the disclosed technical content can be implemented in other ways. The device embodiments described above are merely illustrative; for example, the division of units can be a logical functional division, and in actual implementation, there may be other division methods. For instance, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the displayed or discussed mutual coupling, direct coupling, or communication connection may be through some interfaces; the indirect coupling or communication connection between units or modules may be electrical or other forms.

[0103] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0104] In addition, the functional units in the various embodiments of the present application may be integrated into a single processing unit, or each unit may exist physically separately, or two or more units may be integrated into a single unit. The aforementioned integrated units may be implemented in the form of hardware or software functional units.

[0105] If the integrated unit is implemented as a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or all or part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as a USB flash drive, read-only memory (ROM), random access memory (RAM), portable hard drive, magnetic disk, or optical disk.

[0106] The above description is only a preferred embodiment of this application. It should be noted that for those skilled in the art, several improvements and modifications can be made without departing from the principle of this application, and these improvements and modifications should also be considered within the scope of protection of this application.

Claims

1. A message sending method, characterized in that, include: The target merchant number is obtained through the message push component. The target merchant number is the merchant identifier assigned to the message push component by the target merchant's payment terminal after detecting that the user has scanned the payment graphic code. The geographical location of the target merchant's payment terminal is determined through the message push component; The target message receiving component is determined based on the geographical location of the payment terminal and the target merchant number through the message push component. Establish a data connection between the message push component and the target message receiving component; The message push component sends the user payment result determined by the payment terminal to the target message receiving component according to the data connection, wherein the target message receiving component is used to generate voice information based on the user payment result; The method of determining the target message receiving component for receiving a message based on the geographical location of the payment terminal using the message push component includes: obtaining access permissions to the map software program built into the payment terminal through the message push component; using the geographical location of the payment terminal as the center position, expanding outward by a preset distance along the target direction and / or target angle according to the map software program to obtain a search range; determining N message receiving components that already carry merchant numbers within the search range as N candidate message receiving components, where N is an integer greater than or equal to 1; and determining the target message receiving component from the N candidate message receiving components according to the target merchant number. Determining the target message receiving component from the N candidate message receiving components based on the target merchant number includes: sending the target merchant number to the N candidate message receiving components through the message push component, wherein each candidate message receiving component verifies whether the merchant number it carries is the target merchant number and sends the verification result to the message push component; the message push component selects the candidate message receiving component that reports that its merchant number is the target merchant number as the target message receiving component.

2. The message sending method according to claim 1, characterized in that, Determining the geographical location of the target merchant's payment terminal through the message push component includes: The message push component sends a location acquisition request to the payment terminal of the target merchant, wherein the location acquisition request is used to request the payment terminal to grant the message push component permission to determine location. After detecting that the payment terminal agrees to the location acquisition request, the geographical location of the payment terminal is read through the message push component.

3. The message sending method according to claim 1, characterized in that, Establishing a data connection between the message push component and the target message receiving component includes: The message push component sends the data connection establishment request to the target message receiving component; After receiving a response from the target message receiving component agreeing to establish the data connection, the data connection between the message push component and the target message receiving component is established.

4. The message sending method according to claim 1, characterized in that, After the message sending component sends the user payment result determined by the payment terminal to the target message receiving component according to the data connection, the message sending method further includes: After determining that the target message receiving component has received the user's payment result, the data connection is disconnected through the message push component.

5. A message processing method, characterized in that, include: Access to the map software program built into the payment terminal is obtained through the message push component; According to the map software program, using the geographical location of the payment terminal as the center position, a search range is obtained by expanding outward by a preset distance along the target direction and / or target angle; N message receiving components carrying merchant numbers within the search range are identified as N candidate message receiving components, where N is an integer greater than or equal to 1; the target message receiving component is determined from the N candidate message receiving components based on the target merchant number; the target merchant number is sent to the N candidate message receiving components through the message push component, wherein each candidate message receiving component checks whether the merchant number it carries is the target merchant number and sends the verification result to the message push component; the candidate message receiving component that reports that its own merchant number is the target merchant number is selected as the target message receiving component through the message push component; The target message receiving component receives the target merchant number sent by the message push component and establishes a data connection between the message push component and the target message receiving component. The target merchant number is the merchant identifier assigned to the message push component by the target merchant's payment terminal after detecting that the user has scanned the payment graphic code. The target message receiving component is determined by the geographical location of the payment terminal and the target merchant number. The target message receiving component receives the user payment result determined by the payment terminal, which is sent by the message push component based on the data connection. The target message receiving component generates voice information based on the user's payment result.

6. A message processing system, characterized in that, include: A payment terminal is used to send a target merchant code to a message push component after detecting that a user has scanned a payment graphic code, wherein the target merchant code is the merchant identifier of the target merchant; The message push component is used to determine the geographical location of the payment terminal and determine the target message receiving component to receive the message based on the geographical location of the payment terminal and the target merchant number. The target message receiving component is used to establish a data connection with the message push component, receive the user payment result determined by the payment terminal and sent by the message push component according to the data connection, and generate voice information according to the user payment result; The message push component is further configured to obtain access permissions to the map software program built into the payment terminal; based on the map software program, using the geographical location of the payment terminal as the center location, expand outward by a preset distance along the target direction and / or target angle to obtain a search range; determine N message receiving components carrying merchant IDs within the search range as N candidate message receiving components, where N is an integer greater than or equal to 1; determine the target message receiving component from the N candidate message receiving components based on the target merchant ID; send the target merchant ID to the N candidate message receiving components through the message push component, wherein each candidate message receiving component checks whether its own merchant ID matches the target merchant ID and sends the verification result to the message push component; through the message push component, select the candidate message receiving component that reports that its own merchant ID matches the target merchant ID as the target message receiving component.

7. A message sending device, characterized in that, include: The first acquisition unit acquires the target merchant number through the message push component, wherein the target merchant number is the merchant identifier assigned to the message push component by the target merchant's payment terminal after detecting that the user has scanned the payment graphic code; The first determining unit determines the geographical location of the target merchant's payment terminal through the message push component; The second determining unit, through the message push component, determines the target message receiving component for receiving the message based on the geographical location of the payment terminal and the target merchant number. This includes: obtaining access permissions to the map software program built into the payment terminal through the message push component; using the geographical location of the payment terminal as the center position, expanding outwards by a preset distance along the target direction and / or target angle to obtain a search range based on the map software program; determining N message receiving components within the search range that already carry the merchant number as N candidate message receiving components, where N is an integer greater than or equal to 1; and determining the target message receiving component from the N candidate message receiving components based on the target merchant number. The process of determining the target message receiving component from the N candidate message receiving components based on the target merchant number includes: sending the target merchant number to the N candidate message receiving components via the message push component, wherein each candidate message receiving component verifies whether the merchant number it carries is the target merchant number and sends the verification result to the message push component; and the message push component selects the candidate message receiving component that reports that its merchant number is the target merchant number as the target message receiving component. The first establishment unit establishes a data connection between the message push component and the target message receiving component; The third determining unit, through the message push component, sends the user payment result determined by the payment terminal to the target message receiving component according to the data connection, wherein the target message receiving component is used to generate voice information based on the user payment result.

8. A message processing device, characterized in that, include: The target message receiving component determination unit is used to obtain access permissions to the map software program built into the payment terminal through the message push component; According to the map software program, using the geographical location of the payment terminal as the center position, a search range is obtained by expanding outward by a preset distance along the target direction and / or target angle; N message receiving components carrying merchant numbers within the search range are identified as N candidate message receiving components, where N is an integer greater than or equal to 1; the target message receiving component is determined from the N candidate message receiving components based on the target merchant number; the target merchant number is sent to the N candidate message receiving components through the message push component, wherein each candidate message receiving component checks whether the merchant number it carries is the target merchant number and sends the verification result to the message push component; the candidate message receiving component that reports that its own merchant number is the target merchant number is selected as the target message receiving component through the message push component; The sending unit receives the target merchant number sent by the message push component through the target message receiving component, and establishes a data connection between the message push component and the target message receiving component. The target merchant number is the merchant identifier assigned to the message push component by the target merchant's payment terminal after detecting that the user has scanned the payment graphic code. The target message receiving component is determined by the geographical location of the payment terminal and the target merchant number. The receiving unit receives, through the target message receiving component, the user payment result determined by the payment terminal and sent by the message push component based on the data connection; The generation unit generates voice information based on the user's payment result through the target message receiving component.

9. A computer-readable storage medium, characterized in that, The computer-readable storage medium includes a stored executable program, wherein, when the executable program is executed, it controls the device on which the computer-readable storage medium is located to perform the message sending method of any one of claims 1 to 4 or the message processing method of claim 5.

10. An electronic device, characterized in that, It includes one or more processors and a memory, the memory being used to store one or more programs, wherein when the one or more programs are executed by the one or more processors, the one or more processors cause the one or more processors to perform the message sending method of any one of claims 1 to 4 or the message processing method of claim 5.

11. A computer program product comprising computer instructions, characterized in that, When the computer instructions are executed by the processor, they implement the steps of the message sending method according to any one of claims 1 to 4 or the message processing method according to claim 5.

Images