Payment management method and device, equipment and storage medium

Abstract

The invention provides a payment management method and device, equipment and a storage medium, which can be applied to scenes such as electronic payment and instant messaging. The method comprises the steps that first terminal equipment responds to sending operation of a first object on a first collection code picture, the first collection code picture to be sent is acquired, reminding information is displayed when it is detected that a collection code in the first collection code picture is an external collection code, and the external collection code is a collection code not recommended by a first enterprise; the reminding information is used for reminding the risk existing when the first object uses the collection code in the first collection code picture to collect the money. And if the collection code in the first collection code picture is the external collection code, the instant messaging server sends a risk notification to the administrator terminal device. According to the method, the personal collection behavior of the enterprise member can be accurately identified, the enterprise detection capability is improved, the manpower and time cost of collection management is reduced, and the payment management effect and efficiency are improved.

Description

Technical Field

[0001] This application relates to the field of computer technology, and in particular to a payment management method, apparatus, device, and storage medium. Background Technology

[0002] With the rapid development of electronic payment technology, users and businesses can complete fast and convenient payment activities through electronic payment. Electronic payment refers to the act of consumers, merchants, and financial institutions using secure electronic means to transmit payment information securely to banks or relevant processing institutions through an information network to realize monetary payment or fund transfer. Currently, electronic payment mainly includes online payment and mobile payment.

[0003] In current corporate payment practices, it is often difficult to avoid employees using personal or other payment codes to receive payments. This poses payment risks, increases the manpower and time costs of payment management, and makes it difficult for companies to accurately track payment activity data. Summary of the Invention

[0004] This application provides a payment management method, apparatus, device, and storage medium that can reduce the manpower and time costs for enterprises in collection management.

[0005] In a first aspect, this application provides a payment management method applied to a first terminal device, the method comprising:

[0006] In response to the first object sending the first payment code image in the instant messaging chat interface corresponding to the first enterprise, obtain the first payment code image to be sent;

[0007] The system displays a reminder message. This reminder message is generated when the payment code in the first payment code image is detected as an external payment code. The external payment code is a payment code that the first enterprise does not recommend. The reminder message is used to remind the first object of the risks involved in using the payment code in the first payment code image to receive payments.

[0008] Secondly, this application provides a payment management method applied to an instant messaging server, the method comprising:

[0009] A risk notification is sent to the administrator's terminal device. The risk notification is sent when it is detected that the payment code in the first payment code image is an external payment code. The external payment code is a payment code that the first enterprise does not recommend. The first payment code image is a payment code image to be sent by the first object in the instant messaging of the first enterprise. The risk notification is used to indicate that the first object is using an external payment code to receive payment.

[0010] Thirdly, this application provides a payment management method applied to an administrator terminal device, the method comprising:

[0011] The system receives a risk notification sent by an instant messaging server. The risk notification is used to indicate that the first object is using an external payment code to receive payment. The external payment code is a payment code that the first enterprise does not recommend. The risk notification is sent when the payment code in the first payment code image is detected to be an external payment code. The first payment code image is a payment code image that the first object is to send in the instant messaging of the first enterprise.

[0012] The risk notification will be displayed.

[0013] Fourthly, this application provides a payment management device applied to a first terminal device, the device comprising:

[0014] The acquisition unit is used to acquire the first payment code image to be sent in response to the sending operation of the first object in the instant messaging chat interface corresponding to the first enterprise.

[0015] The display unit is used to display reminder information. The reminder information is based on the detection of the payment code in the first payment code image, and is displayed when the payment code in the first payment code image is detected as an external payment code. The external payment code is a payment code that the first enterprise does not recommend. The reminder information is used to remind the first object of the risks involved in using the payment code in the first payment code image to receive payments.

[0016] In some embodiments, the display unit is specifically used to obtain activation information corresponding to the first enterprise, the activation information being used to indicate whether the first enterprise has activated external payment collection services; and to display the reminder information based on the activation information.

[0017] In some embodiments, the display unit is specifically configured to display the first payment code image and the reminder information in the instant messaging chat interface if the activation information indicates that the first enterprise has not activated the external payment service; and to display a reminder pop-up window, which includes the reminder information, if the activation information indicates that the first enterprise has activated the external payment service.

[0018] In some embodiments, the reminder pop-up further includes an option for receiving payments from outside the recipient, and a display unit is also configured to, in response to the first object's triggering operation on the option for receiving payments from outside the recipient in the reminder pop-up, display the external payment information corresponding to the first enterprise in the instant messaging chat interface.

[0019] In some embodiments, if the external payment information corresponding to the first enterprise is an external payment mini-program card, the display unit is further configured to respond to the triggering operation of the second object on the external payment mini-program card and jump to display the interface of the external payment mini-program.

[0020] In some embodiments, the reminder pop-up further includes a "Continue Sending Payment Code" option, and the display unit is also configured to display the first payment code image in the instant messaging chat interface in response to the first object's triggering operation of the "Continue Sending Payment Code" option.

[0021] In some embodiments, the display unit is specifically configured to send the first payment code image to an instant messaging server, receive the reminder information sent by the instant messaging server, and display the received reminder information, wherein the reminder information is sent by the instant messaging server when it detects that the payment code in the first payment code image is the external payment code; or, to detect the payment code in the first payment code image, and display the reminder information when it is detected that the payment code in the first payment code image is the external payment code.

[0022] In some embodiments, the display unit is specifically used to obtain a list of types of non-recommended payment codes corresponding to the first enterprise; perform type detection on the payment code in the first payment code image to obtain the type of the payment code in the first payment code image; if the type of the payment code in the first payment code image is one of the types in the list of non-recommended payment codes, then determine that the payment code in the first payment code image is the external payment code.

[0023] In some embodiments, the display unit is further configured to compare the first payment code image with payment code images cached in a first cache area, the first cache area including payment code images sent by the first object within a preset time period; if no payment code image matching the first payment code image is found in the first cache area, then a list of types of non-recommended payment codes corresponding to the first enterprise is obtained.

[0024] In some embodiments, the display unit is further configured to determine the payment code detection result of the second payment code image as the payment code detection result of the first payment code image if the first payment code image is consistent with the second payment code image in the first cache area, wherein the payment code detection result includes whether the payment code is the external payment code or the payment code is not the external payment code.

[0025] Fifthly, this application provides a payment management device applied to an instant messaging server, the device comprising:

[0026] The transceiver unit is used to send a risk notification to the administrator terminal device. The risk notification is sent when it is detected that the payment code in the first payment code image is an external payment code. The external payment code is a payment code that the first enterprise does not recommend. The first payment code image is a payment code image to be sent by the first object in the instant messaging of the first enterprise. The risk notification is used to indicate that the first object is using an external payment code to receive payment.

[0027] In some embodiments, the transceiver unit is further configured to send payment summary information to the administrator terminal device when a preset time arrives. The payment summary information includes at least one of a first description of payment collection using the external payment information corresponding to the first enterprise within a preset time period and a second description of payment collection using the external payment code.

[0028] In some embodiments, the transceiver unit is further configured to receive a first payment code image sent by a first terminal device, wherein the first payment code image is a payment code image to be sent by a first object in an instant messaging chat interface corresponding to a first enterprise; perform a legality check on the payment code in the first payment code image; and if the payment code in the first payment code image is an external payment code, send a reminder message to the first terminal device, wherein the reminder message is used to remind the first object of the risks involved in using the payment code in the first payment code image for payment.

[0029] In some embodiments, the transceiver unit is specifically configured to obtain a list of types of non-recommended payment codes corresponding to the first enterprise; perform type detection on the payment code in the first payment code image to obtain the type of the payment code in the first payment code image; if the type of the payment code in the first payment code image is one of the types in the list of non-recommended payment codes, then determine that the payment code in the first payment code image is the external payment code.

[0030] In some embodiments, the transceiver unit is further configured to compare the first payment code image with payment code images cached in a second cache, the second cache including payment code images sent by each terminal device within a preset time period; if no payment code image matching the first payment code image is found in the second cache, then a list of types of non-recommended payment codes corresponding to the first enterprise is obtained.

[0031] In some embodiments, the transceiver unit is further configured to determine the payment code detection result of the second payment code image as the payment code detection result of the first payment code image if the first payment code image is consistent with the second payment code image in the second cache area, wherein the payment code detection result includes whether the payment code is the external payment code or whether the payment code is not the external payment code.

[0032] Sixthly, this application provides a payment management device for use in an administrator terminal device, the device comprising:

[0033] The transceiver unit is used to receive a risk notification sent by an instant messaging server. The risk notification is used to indicate that the first object is using an external payment code to receive payment. The external payment code is a payment code that the first enterprise does not recommend. The risk notification is sent when the payment code in the first payment code image is detected to be an external payment code. The first payment code image is a payment code image to be sent by the first object in the instant messaging of the first enterprise.

[0034] A display unit is used to display the risk notification.

[0035] In some embodiments, the transceiver unit is further configured to receive payment summary information sent by the instant messaging server, the payment summary information including at least one of first description information of receiving payments using the first enterprise's external payment information within a preset time period and second description information of receiving payments using external payment codes; the display unit 32 is further configured to display the payment summary information.

[0036] In some embodiments, the display interface for the payment summary information further includes a "disable external payment code" option. The sending and receiving unit is also configured to send an external payment code disabling instruction to the instant messaging server in response to the administrator's triggering operation of the "disable external payment code" option. The external payment code disabling instruction is used to indicate that sending external payment codes in the instant messaging chat interface corresponding to the first enterprise is prohibited.

[0037] In some embodiments, if the first enterprise has not activated its external payment collection service, the display interface of the payment collection summary information further includes an option to activate external payment collection. The sending and receiving unit is also used to send an activation instruction to the instant messaging server in response to the administrator's triggering operation on the external payment collection option. The activation instruction is used to instruct the first enterprise to activate its external payment collection service.

[0038] In some embodiments, the second description information further includes a view details icon and a send / receive unit, which is also configured to display an external payment code usage details page in response to the administrator's trigger operation on the view details icon. The external payment code usage details page includes at least one of the following: object information of the external payment code sender, the type of external payment code used by the sender, the number of times different types of external payment codes are used, the sending time of the external payment code, and object information of the external payment code receiver.

[0039] In some embodiments, the external payment code usage details page further includes a disable external payment code option. The sending and receiving unit is also configured to send an external payment code disable instruction to the instant messaging server in response to the administrator's triggering operation of the disable external payment code option. The external payment code disable instruction is used to indicate that sending external payment codes in the instant messaging chat interface corresponding to the first enterprise is prohibited.

[0040] In a seventh aspect, this application provides an electronic device including a processor and a memory. The memory is used to store a computer program, and the processor is used to invoke and run the computer program stored in the memory to perform the methods described in any one of the first to third aspects.

[0041] Eighthly, a chip is provided for implementing the methods of various implementations of the first aspect described above. Specifically, the chip includes a processor for retrieving and running a computer program from a memory, causing a device equipped with the chip to perform the methods of any one of the first to third aspects described above.

[0042] Ninthly, a computer-readable storage medium is provided for storing a computer program that causes a computer to perform the methods of any one of the first to third aspects described above.

[0043] In a tenth aspect, a computer program product is provided, comprising computer program instructions that cause a computer to perform the methods of any one of the first to third aspects described above.

[0044] Eleventhly, a computer program is provided that, when run on a computer, causes the computer to perform the methods of any one of the first to third aspects described above.

[0045] In summary, this application proposes a novel payment management method. When a first party sends a first payment code image to the instant messaging service corresponding to a first enterprise via a first terminal device, the first terminal device, in response to the first party's sending operation, obtains the first payment code image to be sent. Then, the first terminal device verifies the payment code included in the first payment code image, or sends the first payment code image to the instant messaging server for verification. If it detects that the payment code in the first payment code image is an external payment code (where the external payment code is a payment code not recommended by the first enterprise), a reminder message is displayed. This reminder message addresses the risks associated with the first party using the payment code in the first payment code image for receiving payments. This method can accurately identify the individual payment behavior of enterprise members, reminding the first party and / or other parties in the instant messaging chat interface to exercise caution when making payments, thereby reducing the enterprise's payment risk. Furthermore, in this embodiment of the application, if it is detected that the payment code in the first payment code image is an external payment code, the instant messaging server sends a risk notification to the administrator's terminal device. This risk notification is used to indicate that the first object is using an external payment code to receive payment. In this way, the administrator can promptly understand the current non-recommended payment behavior, so as to promptly block it or collect statistics on non-recommended payment behavior, improve the enterprise's real-time data detection capabilities, reduce the manpower and time costs of payment management, enable the enterprise to accurately collect payment behavior data, and thus improve the effectiveness and efficiency of payment management. Attached Figure Description

[0046] To more clearly illustrate the technical solutions in the embodiments of the present invention, the accompanying drawings used in the description of the embodiments will be briefly introduced below. Obviously, the accompanying drawings described below are only some embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0047] Figure 1 A schematic diagram illustrating the implementation environment of a payment management method provided in this application embodiment;

[0048] Figure 2 A flowchart illustrating a payment management method provided in an embodiment of this application;

[0049] Figures 3A to 3D A diagram illustrating the opening of an instant messaging chat interface for the first recipient;

[0050] Figure 4 This is a schematic diagram of a reminder message displayed when the first company has not activated its external payment collection service.

[0051] Figure 5 A schematic diagram showing a notification message when a company activates its external payment collection service.

[0052] Figure 6 This is an illustration of the scenario where the external payment information corresponding to the first enterprise is the external payment mini-program card corresponding to the first enterprise.

[0053] Figure 7 This is a diagram illustrating the interface of the External Payment Collection Mini Program displayed after the External Payment Collection Mini Program card is triggered.

[0054] Figure 8 Another illustration of the pop-up notification;

[0055] Figure 9 Another illustration for reminding users of pop-up windows;

[0056] Figure 10 This is a diagram illustrating a risk notification.

[0057] Figure 11 This is a diagram illustrating the summary of payment information.

[0058] Figure 12 This is another illustration of the reminder message;

[0059] Figure 13 An illustration of a detailed page for using external payment QR codes;

[0060] Figure 14 A flowchart illustrating a payment management method provided in an embodiment of this application;

[0061] Figure 15 A diagram illustrating the activation of corporate payment functionality for the first enterprise;

[0062] Figure 16 This is a schematic diagram illustrating the processing of the first payment code image;

[0063] Figure 17 This is an illustration of sending a risk notification.

[0064] Figure 18 This is a schematic block diagram of a payment management device provided in an embodiment of this application;

[0065] Figure 19 This is a schematic block diagram of a payment management device provided in an embodiment of this application;

[0066] Figure 20 This is a schematic block diagram of a payment management device provided in an embodiment of this application;

[0067] Figure 21 This is a schematic block diagram of the electronic device provided in the embodiments of this application. Detailed Implementation

[0068] The technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, and not all embodiments. Based on the embodiments of this application, all other embodiments obtained by those of ordinary skill in the art without creative effort are within the scope of protection of this application.

[0069] 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. In embodiments of the invention, "B corresponding to A" means that B is associated with A. In one implementation, B can be determined based on A. However, it should also be understood that determining B based on A does not mean determining B solely based on A; B can also be determined based on A and / or other information. 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 server 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 these processes, methods, products, or devices. In the description of this application, unless otherwise stated, "a plurality of" means two or more.

[0070] The payment management method provided in this application can be applied to various fields such as electronic payment and instant messaging, so as to achieve efficient and accurate identification of the personal payment behavior of enterprise members in instant messaging applications, improve the enterprise's ability to analyze and manage payment data, and thus reduce the enterprise's manpower and time costs in payment management.

[0071] To facilitate understanding of the embodiments of this application, the relevant concepts involved in the embodiments of this application will first be introduced:

[0072] Electronic payment refers to the act of consumers, merchants, and financial institutions using secure electronic means to transmit payment information securely to banks or relevant processing institutions through information networks to realize monetary payments or fund transfers.

[0073] Electronic payment business types are categorized by the method of initiating electronic payment instructions into online payment, telephone payment, mobile payment, point-of-sale terminal transactions, ATM transactions, and other electronic payments.

[0074] Online payment is a form of electronic payment. Broadly speaking, online payment is a financial exchange between buyers and sellers that takes place based on the internet and utilizes digital financial instruments supported by banks. It realizes online monetary payments, cash transfers, fund clearing, and query statistics between buyers and financial institutions and merchants, thereby providing financial support for e-commerce services and other services.

[0075] Telephone payment is an offline form of electronic payment. It refers to a way in which consumers can use a telephone (landline, mobile phone, PHS) or other similar telephone terminal devices to make payments directly from their personal bank accounts through the banking system.

[0076] Mobile payment is a new type of payment method that uses mobile devices to complete payment wirelessly. The mobile terminals used for mobile payment can be mobile phones, PDAs, mobile PCs, etc.

[0077] With the rapid development of electronic payment technology, various third-party payment applications have emerged.

[0078] Instant messaging (IM) is a terminal service that allows two or more people to exchange text messages, files, voice, and video messages instantly over the internet. Instant messaging can be categorized by usage into instant messaging and web instant messaging, and by the platform it's used with into mobile instant messaging and PC instant messaging. Mobile instant messaging is represented by SMS, while web and video instant messaging are examples.

[0079] Enterprise instant messaging comes in two forms: one primarily for internal office work, establishing a communication platform for employees, reducing operating costs, and improving office efficiency; the other is based on instant messaging and integrates related applications. Currently, enterprise communication software is widely used by various types of enterprises.

[0080] Currently, instant messaging applications can facilitate corporate payment collection. However, in corporate payment collection, it is often difficult to prevent employees from using personal or other payment codes. This poses payment collection risks, increases the manpower and time costs of payment management, and makes it difficult for companies to accurately track payment collection data.

[0081] To address the aforementioned technical problems, this application proposes a payment management method. When a first user sends a first payment code image to the instant messaging service corresponding to a first enterprise via a first terminal device, the first terminal device, in response to the user's sending operation, acquires the first payment code image to be sent. Then, the first terminal device verifies the payment code included in the first payment code image, or sends the first payment code image to the instant messaging server for verification. If the payment code in the first payment code image is detected as an external payment code, a reminder message is displayed, indicating that the external payment code is not recommended by the first enterprise. This reminder message addresses the risks associated with the first user using the payment code in the first payment code image for receiving payments. This method accurately identifies the individual payment behavior of enterprise members, reminding the first user and / or other users in the instant messaging chat interface to exercise caution when making payments, thereby reducing the enterprise's payment risk. Furthermore, in this embodiment, if the payment code in the first payment code image is an external payment code, the instant messaging server sends a risk notification to the administrator's terminal device. This risk notification is used to indicate that the first object is using an external payment code to collect payments. In this way, the administrator can promptly understand the current non-recommended payment behavior in the enterprise, so as to promptly block or statistically analyze the non-recommended payment behavior, improve the enterprise's real-time data detection capabilities, reduce the manpower and time costs of payment management, enable the enterprise to accurately analyze payment behavior data, and thus improve the effectiveness and efficiency of payment management.

[0082] The implementation environment of the embodiments of this application is described below.

[0083] Figure 1 A schematic diagram illustrating the implementation environment of a payment management method provided in this application embodiment, as shown below. Figure 1 As shown, the implementation environment includes: a first terminal device 101, an instant messaging server 102, and an administrator terminal device 103. The first terminal device 101 can be understood as the terminal device used by the first object.

[0084] The first terminal device 101 is connected to the instant messaging server 102 via wired or wireless means. The instant messaging server 102 is connected to the administrator terminal device 103 via wired or wireless means.

[0085] In this embodiment, the first terminal device 101 is equipped with an instant messaging application client, such as an enterprise instant messaging application client. The first user can add multiple enterprises to the instant messaging application client, thus including multiple enterprises in the client. The first user can select one enterprise and access its corresponding chat interface. For example, the first user can select the first enterprise in the client and enter its corresponding instant messaging chat interface, where it can chat with employees of that enterprise. The instant messaging server 102 can be understood as the server-side or backend of the instant messaging application. It can receive messages sent by the instant messaging application client on the first terminal device 101 and also send messages to the instant messaging application client on the first terminal device 101. Simultaneously, the instant messaging server 102 can also send messages to and receive messages from the administrator terminal device 103.

[0086] In this embodiment, a first user opens the client of an instant messaging application installed on a first terminal device 101 and selects a first company within the client. In response to the first user's selection of the first company, the first terminal device 101 displays the instant messaging chat interface corresponding to the first company. The first user sends a first payment code image within this instant messaging chat interface. In response to the first user's sending of the first payment code image within the instant messaging chat interface corresponding to the first company, the first terminal device 101 obtains the first payment code image to be sent. Next, the first terminal device 101 verifies the legality of the payment code in the first payment code image, or the first terminal device 101 sends the first payment code image to the instant messaging server 102 so that the instant messaging server 102 verifies the legality of the payment code in the first payment code image. If it is determined that the payment code in the first payment code image is an external payment code (i.e., a payment code not recommended by the first company), the first terminal device 101 displays a reminder message. This reminder message is used to remind the first user of the risks associated with using the payment code in the first payment code image for receiving payments. This allows for accurate identification of individual payment collection behavior by company members, reminding the first recipient and / or other recipients in the instant messaging chat interface to exercise caution when making payments, thereby reducing the company's payment collection risk. Furthermore, in this embodiment, if the payment code in the first payment code image is an external payment code, the instant messaging server 102 sends a risk notification to the administrator's terminal device 103. This risk notification indicates that the first recipient is using an external payment code to collect payments. This allows the company administrator to promptly understand the current unrecommended payment collection behavior within the company, enabling timely intervention or statistical analysis of such behavior. This improves the company's real-time data detection capabilities, reduces the manpower and time costs of payment collection management, and allows the company to accurately collect payment behavior data, thereby improving the effectiveness and efficiency of payment management.

[0087] In some embodiments, the terminal device 101 includes, but is not limited to, desktop computers, laptops, smartphones, tablets, IoT devices, and portable wearable devices. IoT devices may be devices equipped with cameras and display devices, such as smart speakers, smart TVs, smart air conditioners, and smart in-vehicle systems. Portable wearable devices may be devices equipped with cameras and display devices, such as smartwatches, smart bracelets, and head-mounted devices. Terminal devices are often equipped with display devices, which may also be monitors, displays, touchscreens, etc., and touchscreens may also be touchscreens, touch panels, etc.

[0088] In some embodiments, the server 102 described above can be one or more servers. When there are multiple servers, at least two servers are used to provide different services, and / or at least two servers are used to provide the same service, such as providing the same service in a load-balanced manner. This application embodiment does not limit this. The server described above can be an independent physical server, a server cluster or distributed system composed of multiple physical servers, or a cloud server providing basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communication, middleware services, domain name services, security services, CDN (Content Delivery Network), and big data and artificial intelligence platforms. The server can also be a node in a blockchain.

[0089] It should be noted that the implementation environment of this application embodiment includes, but is not limited to, Figure 1 As shown.

[0090] The technical solutions of the embodiments of this application will be described in detail below through some examples. The following embodiments can be combined with each other, and the same or similar concepts or processes may not be described again in some embodiments.

[0091] Figure 2 This is a flowchart illustrating a payment management method provided in an embodiment of this application.

[0092] like Figure 2 As shown, the payment management method of this application embodiment includes the following steps:

[0093] S101, the first terminal device responds to the first object's sending operation of sending the first payment code image in the instant messaging chat interface corresponding to the first enterprise, and obtains the first payment code image to be sent.

[0094] The first terminal device in this embodiment is a terminal device used by a first object. This terminal device has an instant messaging client installed, such as an enterprise instant messaging client. The first object enters the instant messaging chat interface corresponding to the first enterprise by triggering the instant messaging client.

[0095] In some embodiments, a first object may join one or more instant messaging chat groups of enterprises, including the instant messaging chat group of the first enterprise. The first object can access the instant messaging chat interface of the first enterprise by triggering the instant messaging chat group of the first enterprise.

[0096] It should be noted that in this embodiment, the client display interfaces of different instant messaging applications are different, and the way the first object enters the instant messaging chat interface corresponding to the first enterprise is not entirely the same. Therefore, this embodiment does not limit the specific way the first object enters the instant messaging chat interface corresponding to the first enterprise, but determines it according to the type of instant messaging application used by the first object.

[0097] In one example, such as Figure 3A As shown, the first object triggers the client icon of the instant messaging application on the interface of the first terminal device, and enters the main interface of the instant messaging application. Figure 3B As shown, the main interface includes a list of one or more companies added by the first object. When the first object selects a first company from the list of one or more companies, the first terminal device responds to the first object's selection of the first company and enters... Figure 3C The main interface corresponding to the first enterprise is shown. This main interface includes a list of chat objects, which can include chat groups the first enterprise has joined and individual contacts the first enterprise has recently contacted. The first enterprise can select an individual contact or a chat group from this list to send a message. For example, as shown... Figure 3C As shown, assuming the first user selects the second user from the chat list, the first terminal device responds to the first user's selection of the second user's avatar and enters... Figure 3D The instant messaging chat interface shown is used for message exchange between the first and second parties.

[0098] In this embodiment, after the first user enters the instant messaging chat interface, it sends a first payment code image to the instant messaging chat interface. This embodiment does not limit the type of payment code included in the first payment code image; it can be any payment code capable of receiving payments. In response to the first user's sending operation of the first payment code image to the instant messaging chat interface, the first terminal device obtains the first payment code image to be sent. That is, in this embodiment, the first terminal device obtains the first payment code image to be sent before the first user sends it to the instant messaging chat interface.

[0099] S102, The first terminal device displays a reminder message.

[0100] The reminder message involves detecting the QR code in the first QR code image and displaying it when it is detected as an external QR code. External QR codes are those not recommended by the first company. The reminder message is used to remind the first user of the risks involved in using the QR code in the first QR code image to receive payments.

[0101] In this embodiment, after the first terminal device acquires the first payment code image to be sent, it displays a reminder message when it determines that the payment code in the first payment code image is an external payment code. This reminder message is used to alert the first recipient to the risks associated with using the payment code in the first payment code image for receiving payments. In other words, this embodiment checks whether the payment code in the first payment code image is an external payment code, which can accurately identify the individual payment behavior of enterprise members. Furthermore, by displaying a reminder message when it is determined that the payment code in the first payment code image is an external payment code, it reminds the first recipient and / or other recipients in the instant messaging chat interface to exercise caution when making payment transactions, thereby reducing the enterprise's payment risk.

[0102] The following describes the detection process for determining whether the payment code in the first payment code image is an external payment code in the embodiments of this application.

[0103] In this embodiment of the application, after the first object obtains the first payment code image to be sent, it can detect whether the payment code in the first payment code image is an external payment code in the following ways:

[0104] Method 1: After the first terminal device obtains the first payment code image to be sent, it checks the payment code included in the first payment code image to determine whether the payment code included in the first payment code image is an external payment code. Here, an external payment code can be understood as a payment code that the first enterprise does not recommend.

[0105] The following describes the specific process by which the first terminal device determines whether the payment code included in the first payment code image is an external payment code.

[0106] In some embodiments of Method 1, the first enterprise sets up one or more recommended payment codes, intending to receive payments through these codes. Based on this, the first terminal device can identify the first payment code image and compare the payment code included in the first payment code image with the first enterprise's recommended payment codes. If the payment code included in the first payment code image matches one of the first enterprise's recommended payment codes, then the payment code included in the first payment code image is determined not to be an external payment code. If the payment code included in the first payment code image does not match any of the first enterprise's recommended payment codes, then the payment code included in the first payment code image is determined to be an external payment code.

[0107] In some embodiments of Method 1, a list of types of payment codes that are not recommended can be set for the first enterprise, resulting in a list of such types. This list can be set by the administrator of the first enterprise or it can be a default list. When the first terminal device detects that a first object sends a first payment code image in the instant messaging chat interface corresponding to the first enterprise, it obtains the first payment code image and the list of types of payment codes that are not recommended by the first enterprise. This list includes at least one type of payment code that the first enterprise does not recommend. Thus, the first terminal device can perform type detection on the payment codes in the first payment code image to determine their type. For example, the first terminal device can perform image detection on the first payment code image to identify the type of the payment code in the image. Next, the type of the payment code in the first payment code image is compared with each of the unrecommended payment code types in the list of unrecommended payment code types corresponding to the first enterprise. If the type of the payment code in the first payment code image is one of the types in the list of unrecommended payment code types, then the payment code in the first payment code image is determined to be an external payment code, that is, a payment code not recommended by the first enterprise.

[0108] In some embodiments, the first terminal device caches recently sent QR code images by the first object, along with the QR code detection results of these images, in a local first cache. When the first object sends a first QR code image, the first terminal device first compares this first QR code image with the QR code images cached in the first cache to determine if the cached images include a QR code image that matches the first QR code image. If a second QR code image in the cache matches the first QR code image, the QR code detection result of the second QR code image is used as the QR code detection result of the first QR code image. This avoids the first terminal device performing duplicate validity checks on the same QR code images, thereby saving technical resources and improving image processing efficiency.

[0109] For example, suppose the information related to the QR code image cached in the first cache of the first terminal device is as shown in Table 1:

[0110] Table 1

[0111] QR code for receiving payment QR code payment test results QR code image 1 External payment QR code QR code image 2 External payment QR code …… ……

[0112] As shown in Table 1, the second cache of the first terminal device in this embodiment contains payment code images sent by the first object in a recent period, as well as the payment code detection results of these payment code images. Based on this, after receiving the first payment code image, the first terminal device matches the first payment code image with each payment code image cached in the first cache of the first terminal device. If the first payment code image matches the second payment code image in the payment code images cached by the first terminal device as shown in Table 1, then the payment code detection result of the second payment code image is determined as the payment code detection result of the first payment code image. For example, assuming that the first payment code image matches payment code image 2 in Table 1, then payment code image 2 is the second payment code image that matches the first payment code image, and thus the payment code detection result of payment code image 2 (i.e., external payment code) is determined as the payment code detection result of the first payment code image. That is, the payment code included in the first payment code image is an external payment code, i.e., a payment code not recommended by the first enterprise.

[0113] In some embodiments, if the QR code images cached in the first cache of the first terminal device do not include a QR code image matching the first QR code image, the first terminal device obtains a list of types of QR codes not recommended for the first enterprise; performs type detection on the QR codes in the first QR code image to obtain the type of the QR codes in the first QR code image; if the type of the QR codes in the first QR code image is one of the types in the list of types of QR codes not recommended, then the QR codes in the first QR code image are determined to be external QR codes.

[0114] For example, the first terminal device includes the list of types of non-recommended payment codes corresponding to the first enterprise, as shown in Table 2:

[0115] Table 2

[0116]

[0117]

[0118] In this implementation, the first terminal device parses the first payment code image to determine the type 'a' of the payment code included in the first payment code image. Then, it checks whether type 'a' of the payment code included in the first payment code image is included in the types of unrecommended payment codes shown in Table 2. If type 'a' of the payment code included in the first payment code image is one of the types of unrecommended payment codes shown in Table 2, then the payment code included in the first payment code image is determined to be an external payment code. In some embodiments, if type 'a' of the payment code included in the first payment code image does not belong to one of the types of unrecommended payment codes shown in Table 2, then the payment code included in the first payment code image is determined not to be an external payment code.

[0119] It should be noted that, in addition to determining the QR code detection result of the first QR code image through the above-mentioned method, the first terminal device can also determine it through other methods, such as through neural network model prediction. This application embodiment does not limit this.

[0120] The above describes the specific process by which the first terminal device determines the detection result of the payment code included in the first payment code image in Method 1.

[0121] In some embodiments, the detection result of the payment code included in the first payment code image can also be determined by the following method 2.

[0122] Method 2: After the first terminal device obtains the first payment code image to be sent, it sends the first payment code image to the instant messaging server. The instant messaging server checks the payment code included in the first payment code image to determine whether the payment code included in the first payment code image is an external payment code, that is, a payment code not recommended by the first enterprise.

[0123] The following describes the specific process by which an instant messaging server determines whether the payment code included in the first payment code image is an external payment code.

[0124] In some embodiments of Method 2, the first enterprise sets one or more recommended payment codes. Based on this, the server can identify the first payment code image and then compare the payment codes included in the first payment code image with the first enterprise's recommended payment codes. If the payment codes included in the first payment code image match one of the first enterprise's recommended payment codes, then it is determined that the payment codes included in the first payment code image are not external payment codes. If the payment codes included in the first payment code image do not match any of the first enterprise's recommended payment codes, then it is determined that the payment codes included in the first payment code image are external payment codes.

[0125] In some embodiments of Method 2, the instant messaging server includes a list of types of payment codes that are not recommended for the first enterprise. Thus, when the first terminal device detects that a first object has sent a first payment code image in the instant messaging chat interface corresponding to the first enterprise, it obtains the first payment code image and sends it to the instant messaging server. The instant messaging server obtains the list of types of payment codes that are not recommended for the first enterprise, which includes at least one type of payment code that the first enterprise does not recommend. In this way, the instant messaging server can perform type detection on the payment code in the first payment code image to determine the type of the payment code in the first payment code image; for example, the first terminal device can perform image detection on the first payment code image to identify the type of the payment code in the first payment code image. Next, the instant messaging server compares the type of the payment code in the first payment code image with each of the unrecommended payment code types in the list of unrecommended payment code types corresponding to the first enterprise. If the type of the payment code in the first payment code image is one of the types in the list of unrecommended payment code types, then the payment code in the first payment code image is determined to be an external payment code, that is, a payment code not recommended by the first enterprise.

[0126] In some embodiments, in this method 2, the instant messaging server caches recently sent QR code images from different objects and / or the first object, along with the QR code detection results of these images, in its local second cache. When the instant messaging server receives a first QR code image from the first terminal device, it first compares this first QR code image with the QR code images cached in the second cache to determine if the cached images include a QR code image that matches the first QR code image. If a second QR code image in the cache matches the first QR code image, the QR code detection result of the second QR code image is used as the QR code validity detection result of the first QR code image. This avoids the instant messaging server performing duplicate validity checks on the same QR code image, thereby saving technical resources and improving image processing efficiency.

[0127] For example, suppose the information related to the QR code images cached by the instant messaging server is shown in Table 1.

[0128] As shown in Table 1, the instant messaging server in this embodiment caches payment code images sent by different objects in a recent period, as well as the payment code detection results of these payment code images. Based on this, after receiving a first payment code image sent by a first terminal device, the instant messaging server matches the first payment code image with each payment code image cached by the first terminal device. If the first payment code image matches a second payment code image among the payment code images cached by the instant messaging server as shown in Table 1, then the payment code detection result of the second payment code image is determined as the payment code detection result of the first payment code image. For example, assuming the first payment code image matches payment code image 2 in Table 1, then payment code image 2 is the second payment code image that matches the first payment code image, and thus the payment code detection result of payment code image 2 (i.e., external payment code) is determined as the payment code detection result of the first payment code image. That is, the payment code included in the first payment code image is an external payment code (i.e., a payment code not recommended by the first enterprise).

[0129] In some embodiments, if the QR code images cached by the instant messaging server do not include a QR code image that matches the first QR code image, the instant messaging server obtains a list of types of QR codes that are not recommended for the first enterprise; performs type detection on the QR codes in the first QR code image to obtain the type of the QR codes in the first QR code image; if the type of the QR codes in the first QR code image is one of the types in the list of types of not recommended QR codes, then the QR codes in the first QR code image are determined to be external QR codes.

[0130] For example, the instant messaging server includes a list of discouraged payment code types as shown in Table 2. Specifically, the instant messaging server parses the first payment code image to determine the type 'a' of the payment code included in the first payment code image. Then, it checks whether type 'a' of the payment code included in the first payment code image is included in the list of discouraged payment code types shown in Table 2. If type 'a' of the payment code included in the first payment code image is one of the discouraged payment code types shown in Table 2, then the payment code included in the first payment code image is determined to be an external payment code. If type 'a' of the payment code included in the first payment code image does not belong to one of the discouraged payment code types shown in Table 2, then the payment code included in the first payment code image is determined not to be an external payment code.

[0131] It should be noted that, in addition to determining the payment code detection result included in the first payment code image through the above method, the instant messaging server can also determine it through other methods, such as through neural network model prediction. This application embodiment does not limit this.

[0132] The above describes the specific process by which the first terminal device or instant messaging server determines the detection result of the payment code included in the first payment code image.

[0133] In some embodiments, if the reminder information displayed by the first terminal device is generated by the first terminal device, in one example, if the payment code detection result of the first payment code image is determined by the first terminal device itself, then the first terminal device displays the reminder information when it detects that the payment code in the first payment code image is an external payment code. In one example, if the payment code detection result of the first payment code image is determined by the instant messaging server, then the instant messaging server sends the payment code detection result of the first payment code image to the first terminal device, and the first terminal device displays the reminder information when it detects that the payment code included in the first payment code image is an external payment code.

[0134] In some embodiments, if the notification information displayed by the first terminal device is generated by the instant messaging server, in one example, if the payment code detection result of the first payment code image is determined by the first terminal device itself, then the first terminal device sends the payment code detection result of the first payment code image to the instant messaging server. When the instant messaging server detects that the payment code included in the first payment code image is an external payment code, it generates notification information and sends the notification information to the first terminal device for display. In one example, if the payment code detection result of the first payment code image is determined by the instant messaging server, then when the instant messaging server detects that the payment code included in the first payment code image is an outsourced payment code, it generates notification information and sends the notification information to the first terminal device for display.

[0135] In some embodiments, this application demonstrates that a reminder message is displayed based on whether the first enterprise has activated its external payment collection service. In this case, S102 includes the following steps: S102-A and S102-B:

[0136] S102-A: The first terminal device obtains the activation information corresponding to the first enterprise. The activation information is used to indicate whether the first enterprise has activated the external payment collection business.

[0137] S102-B, the first terminal device displays a reminder message based on the activation information.

[0138] In this embodiment, the first enterprise can activate an external payment collection service to receive payments from external entities. In this embodiment, the display method of the reminder information can differ depending on whether the first enterprise has activated the external payment collection service or not. Therefore, before displaying the reminder information, the first terminal device first obtains the activation information corresponding to the first enterprise, which indicates whether the first enterprise has activated the external payment collection service. Then, based on whether the first enterprise has activated the external payment collection service, the display format of the reminder information is determined, and the reminder information is displayed accordingly.

[0139] This application embodiment does not limit the specific display format of the reminder information when the first enterprise has opened the external payment service and when the first enterprise has not opened the external payment service.

[0140] In one possible implementation, if the activation information corresponding to the first enterprise indicates that the first enterprise has not activated external payment collection services, then the first terminal device displays a first payment code image and a reminder message in the instant messaging chat interface. This application embodiment does not limit the specific display position of the reminder message in the instant messaging chat interface. For example, the reminder message can be displayed above or below the first payment code image.

[0141] In one example of this implementation, such as Figure 4 As shown, if the first terminal device determines that the first enterprise has not activated external payment services, upon detecting that the payment code included in the first payment code image sent by the first object in the instant messaging chat interface is an external payment code, the first terminal device will send the first payment code image to the instant messaging chat interface and display a reminder message below the first payment code image in the instant messaging chat interface. In other words, if the activation information corresponding to the first enterprise indicates that the first enterprise has not activated external payment services, then upon detecting that the payment code included in the first payment code image sent by the first object in the instant messaging chat interface is an external payment code, the first terminal device can directly send the first payment code image sent by the first object to the chat box of the instant messaging chat interface and display a reminder message in the chat box. Optionally, the first terminal device can also set the display transparency of the reminder message.

[0142] In one possible implementation, if the activation information indicates that the first enterprise has activated its external payment collection business, the first terminal device displays a reminder pop-up window, which includes a reminder message.

[0143] In one example of this implementation, such as Figure 5As shown, if the first terminal device determines that the first enterprise has activated its external payment collection service, and detects that the payment code included in the first payment code image sent by the first object in the instant messaging chat interface is an external payment code, the first terminal device will not send the first payment code image to the instant messaging chat interface. Instead, it will display a reminder pop-up window containing reminder information. For example, in the instant messaging chat interface, when the first object selects the "send image" option in the dialog box, selects the first payment code image from its local storage, and clicks "send," the first terminal device, in response to the triggering operation of the "send" option, obtains the first payment code image to be sent, and uses the above method to determine whether the payment code included in the first payment code image is an external payment code. If it is determined that the payment code included in the first payment code image is an external payment code, then it will display... Figure 5 The reminder pop-up window shown displays a reminder message. For example, this message might include: "The company has decided to use [External Payment Collection] to avoid risks such as unclear reconciliation and order skipping that could compromise operational security. Official payment tools are more trusted by customers and have higher conversion rates." This allows the first party to decide whether to continue sending the first payment code image to the instant messaging chat interface based on this reminder message. Therefore, in this implementation, the reminder message can also alert the first party to the risks associated with the payment code included in the first payment code image, enabling the first party to choose not to send the first payment code image to the instant messaging chat interface, thereby avoiding payment risks for the company and improving the company's external payment management.

[0144] In some embodiments, such as Figure 5 As shown, the pop-up notification also includes an option to use external payment collection. The first object can then trigger this option. In response to the first object's triggering of the external payment collection option in the pop-up notification, the first terminal device displays the external payment information corresponding to the first enterprise in the instant messaging chat interface.

[0145] This application embodiment does not limit the specific content of the external payment information corresponding to the first enterprise. For example, the external payment information corresponding to the first enterprise may be an image of the external payment code corresponding to the first enterprise. The payment code included in the external payment code image corresponding to the first enterprise is the payment code corresponding to the first enterprise, and other parties can transfer funds to the account of the first enterprise through the payment code corresponding to the first enterprise.

[0146] In one example, such as Figure 6 As shown, the external payment information corresponding to the first enterprise is the external payment mini-program card corresponding to the first enterprise. At this time, in response to the first object's trigger operation on the external payment option in the reminder pop-up window, the first terminal device displays the external payment mini-program card corresponding to the first enterprise in the instant messaging chat interface. For example, as shown... Figure 7As shown, if the second object triggers the external payment collection mini-program card corresponding to the first enterprise in the instant messaging chat interface, the first terminal device responds to the second object's triggering operation on the external payment collection mini-program card and jumps to display the external payment collection mini-program interface. The second object can complete the transfer payment to the first enterprise in the external payment collection mini-program interface.

[0147] In some embodiments, such as Figure 8 As shown, the pop-up notification can display the external payment collection mini-program card corresponding to the first enterprise. This card includes the enterprise information, such as its name. Optionally, the card also includes a "Please Pay" option; if the first user triggers this option, the first terminal device will redirect to display the external payment collection mini-program interface.

[0148] In some embodiments, such as Figure 9 As shown, the pop-up notification also includes a "Continue Sending Payment Code" option. If the first recipient decides to send the first payment code image to the instant messaging chat interface based on the notification information, the first recipient triggers the "Continue Sending Payment Code" option. In response to the first recipient's triggering of this option, the first terminal device displays the first payment code image in the instant messaging chat interface.

[0149] In some embodiments, when the payment code in the first payment code image is an external payment code, the instant messaging server sends a risk notification to the administrator's terminal device.

[0150] The risk notification is used to indicate that the first party is using an external payment code to receive payments.

[0151] In this embodiment of the application, in order to further improve the first enterprise's real-time detection capability of payment data, the instant messaging server sends a risk notification to the administrator terminal device when the payment code in the first payment code image is an external payment code, so as to remind the administrator that the first object is using an external payment code to receive payment.

[0152] In one example, if the QR code detection result of the first QR code image is completed by the first terminal device in this embodiment, the first terminal device sends the QR code detection result of the first QR code image to the instant messaging server. The instant messaging server then parses the QR code detection result of the first QR code image sent by the first terminal device. If it determines that the QR code included in the first QR code image is an external QR code, it sends a risk notification to the administrator terminal device. This risk notification indicates that the first entity is using an external QR code to receive payments.

[0153] In one example, if the payment code detection result of the first payment code image is obtained by the instant messaging server in this embodiment of the application, then when the instant messaging server determines that the payment code included in the first payment code image is an external payment code, it sends a risk notification to the administrator terminal device. The risk notification is used to indicate that the first object is using an external payment code to receive payment.

[0154] The administrator's terminal device displays a risk notification.

[0155] This application does not limit the specific method by which the instant messaging server sends risk notifications to the administrator's terminal device.

[0156] In one example, the instant messaging server sends a risk notification to the administrator's terminal device via SMS. The administrator can then view the risk notification in their SMS list.

[0157] In one example, an instant messaging application client is installed on the administrator's terminal device. The instant messaging server can send a notification message, including a risk notification, to the instant messaging application client on the administrator's terminal device. This allows the administrator to view the risk notification in the instant messaging application client.

[0158] In some embodiments, such as Figure 10 As shown, the risk notification also includes a description of the risks associated with using external QR codes for receiving payments.

[0159] In one embodiment, such as Figure 10 As shown, the risk notification also includes a "query details" option, which can be triggered by the administrator. In response to the administrator's triggering of this option, the administrator's terminal device can display detailed information about the first object sending the first payment code image, such as the time the first object sent the first payment code image and the type of payment code included in the first payment code image.

[0160] In some embodiments, the instant messaging server periodically sends payment summary information corresponding to a first enterprise to the administrator terminal device. For example, when a preset time arrives, the instant messaging server sends the payment summary information to the administrator terminal device, and the administrator terminal device receives and displays the payment summary information. The payment summary information includes at least one of a first description of payments received using the first enterprise's external payment information within a preset time period and a second description of payments received using an external payment code.

[0161] In one example, the instant messaging server periodically sends a daily summary of payments received by the first company to the administrator's terminal device. For example, ... Figure 11As shown, the instant messaging server sent the first company's payment summary information for May 16th. This payment summary information includes a first description of payments received using the first company's external payment information on that day, and a second description of payments received using external payment codes. For example... Figure 11 As shown, the first descriptive information includes the number of times the first enterprise's external payment information was used to receive payments on that day (e.g., 0). The first descriptive information includes the number of times external payment codes were used to receive payments on that day (e.g., 1), risk warning information, and information about the recipients of payments received using unknown external payment codes.

[0162] In some embodiments, such as Figure 11 As shown, the payment summary information display interface in this embodiment also includes a "Disable External Payment Code" option. When an administrator needs to prevent the first company's external payment code from receiving payments, this "Disable External Payment Code" option is triggered. In response to the administrator's triggering operation of the "Disable External Payment Code" option, the administrator's terminal device sends an external payment code disabling command to the instant messaging server. This command instructs that external payment codes be prohibited from being sent in the instant messaging chat interface corresponding to the first company. After receiving the external payment code disabling command, the instant messaging server prohibits the target from sending external payment codes in the instant messaging chat interface corresponding to the first company.

[0163] In one example, if sending an external payment QR code is disabled in the instant messaging chat interface corresponding to the first enterprise, and an image of an external payment QR code is sent to the instant messaging chat interface corresponding to the first enterprise, the following will be displayed: Figure 12 The interface shown does not include a send option, thus preventing the external payment code image from being sent to the first company's corresponding instant messaging chat interface.

[0164] In some embodiments, if the first enterprise has not activated its external payment collection service, such as Figure 11 As shown, the interface displaying the payment summary information may also include an option to enable external payment collection. The administrator can activate this option to enable external payment collection for the first company. For example, when the administrator activates this option, the administrator's terminal device responds by sending an activation command to the instant messaging server. This command instructs the first company to enable its external payment collection service. When the first company enables external payment collection, the next time the first recipient sends a payment code image that the first company does not recommend to the first company's instant messaging chat interface, it will display something like this. Figure 5 The reminder pop-up window shown.

[0165] In some embodiments, Figure 11The second description information also includes a "View Details" icon. When an administrator triggers the "View Details" icon, the administrator's terminal device responds by displaying a detailed usage page for the external payment code. This detailed usage page includes at least one of the following: object information of the recipient of the external payment code, the type of external payment code used by the recipient, the number of times different types of external payment codes have been used, the sending time of the external payment code, and object information of the recipient of the external payment code.

[0166] In one example, such as Figure 13 As shown, the details page for using the external payment code includes the object information of the recipient of the external payment code (e.g., the name of the first object), the type of external payment code used by the recipient (e.g., a payment code of type 1), the number of times different types of external payment codes are used (e.g., the first type of payment code is used once, and other types of payment codes are used 0 times), the sending time of the external payment code (e.g., 11:48 AM on May 16), and the object information of the recipient of the external payment code (e.g., the name of the second object).

[0167] In some embodiments, such as Figure 13 As shown, the detailed usage page for the external payment code can also include an option to disable all external payment codes. Administrators can trigger this option to prevent the sending of external payment codes within the instant messaging chat interface corresponding to the first enterprise. For example, when an administrator triggers this option, the administrator's terminal device, in response to the trigger operation, sends an external payment code disabling command to the instant messaging server. This command instructs that external payment codes should not be sent within the instant messaging chat interface corresponding to the first enterprise. After receiving the command, the instant messaging server prevents the recipient from sending external payment codes within the instant messaging chat interface corresponding to the first enterprise. In one example, if external payment codes are disabled within the instant messaging chat interface corresponding to the first enterprise, sending an external payment code image to that interface will display as shown below. Figure 12 The interface shown does not include a send option, thus preventing the external payment code image from being sent to the first company's corresponding instant messaging chat interface.

[0168] The payment management method provided in this application embodiment, when a first object sends a first payment code image in the instant messaging of a first enterprise through a first terminal device, the first terminal device responds to the first object's sending operation of the first payment code image by obtaining the first payment code image to be sent; then, the first terminal device performs a legality check on the payment code included in the first payment code image, or the first terminal device sends the first payment code image to the instant messaging server for legality check; when it is determined that the payment code in the first payment code image is an external payment code, a reminder message is displayed. This reminder message is used to remind the first object of the risks involved in using the payment code in the first payment code image for receiving payments. This can accurately identify the individual payment behavior of enterprise members, remind the first object and / or other objects in the instant messaging chat interface to be cautious in receiving and making payments, thereby reducing the enterprise's payment risk. Furthermore, in this embodiment, if the payment code in the first payment code image is an external payment code, the instant messaging server sends a risk notification to the administrator's terminal device. This risk notification is used to indicate that the first object is using an external payment code to receive payments. In this way, the enterprise administrator can promptly understand the current undesirable payment behaviors in the enterprise, so as to promptly block or statistically analyze the undesirable payment behaviors, improve the enterprise's real-time data detection capabilities, reduce the manpower and time costs of payment management, and enable the enterprise to accurately analyze payment behavior data, thereby improving the effectiveness and efficiency of payment management.

[0169] The foregoing provides an overall overview of the payment management method involved in the embodiments of this application. The following section will combine... Figure 14 The payment management method of this application embodiment will be further described.

[0170] Figure 14 This is a flowchart illustrating a payment management method provided in an embodiment of this application.

[0171] like Figure 14 As shown, the payment management method of this application embodiment includes the following steps:

[0172] S201, the first terminal device responds to the sending operation of the first object sending the first payment code image in the instant messaging chat interface corresponding to the first enterprise, and obtains the first payment code image to be sent.

[0173] In this embodiment, before acquiring the first payment image to be sent, the first terminal device first needs to determine whether the first enterprise has enabled the payment function provided in this embodiment. If it is determined that the first enterprise has enabled the payment function provided in this embodiment, the payment management method provided in this embodiment is executed to perform a legality check on the first payment code image sent by the first object. If it is detected that the payment code included in the first payment code image is an external payment code, a reminder message is displayed, and a risk notification is sent to the administrator terminal device. If it is determined that the first enterprise has not enabled the payment function provided in this embodiment, upon receiving the first payment code image sent by the first object, it is necessary to determine whether to enable the payment function provided in this embodiment for the first enterprise.

[0174] In this application embodiment, the payment function provided by this application embodiment can be enabled for the first enterprise in at least the following ways:

[0175] In one possible implementation, the administrator can manually enable the payment function provided in this application embodiment for the first enterprise.

[0176] In one possible implementation, in order to achieve full coverage of the target enterprise, the instant messaging application corresponding to the first enterprise can determine whether to enable the payment function provided in this application embodiment.

[0177] For example, such as Figure 15 As shown, determining whether to enable the payment function provided in this application embodiment can include: an object sending an image in the instant messaging chat interface corresponding to the first enterprise, and the first terminal device sending the image to the instant messaging server. The instant messaging server identifies and parses the image. If it determines that the image is a QR code image, it enables the payment function provided in this application embodiment for the first enterprise; or, if the instant messaging server detects that more than a preset number of images sent in the instant messaging chat interface corresponding to the first enterprise are QR code images, it enables the payment function provided in this application embodiment for the first enterprise. For ease of description, in some examples, the payment function provided in this application embodiment can be referred to as the enterprise payment function. When the instant messaging server enables the enterprise payment function for the first enterprise, the enterprise payment function of the first enterprise becomes effective. Of course, the above determination of whether the first enterprise enables the payment function provided in this application embodiment can be completely completed by the instant messaging client itself, and when it determines that the payment function provided in this application embodiment is enabled for the first enterprise, it sends a notification message to the instant messaging server, so that the instant messaging server can execute the payment management method of this application embodiment.

[0178] In practice, the proportion of QR code payments sent by an object is very low. If image recognition is enabled for all enterprises, it would unnecessarily consume the performance of terminals outside the target enterprise. Therefore, in this embodiment, asynchronous image recognition technology is used to determine whether an enterprise has made a payment request, thereby accurately covering the target enterprise. Specifically, when the first terminal device receives an image sent by an object in the instant messaging chat interface corresponding to the first enterprise, it displays the image in the instant messaging chat interface and then sends the image to the instant messaging server. The instant messaging server recognizes the image, and if it determines that the image is a QR code payment image, it enables the payment function provided by this embodiment for the first enterprise.

[0179] In the embodiments of this application, such as Figure 15 As shown, if the first enterprise activates the payment function provided in this application embodiment, when the first object sends the first payment code image in the instant messaging chat interface corresponding to the first enterprise, the first terminal device obtains the first payment code image to be sent and executes the following steps S202.

[0180] S202, The first terminal device sends the first QR code image to the instant messaging server.

[0181] S203. The instant messaging server detects the payment code in the first payment code image.

[0182] In some embodiments, the instant messaging server caches payment code images sent by different objects or the first object within a recent period, along with the payment code detection results of these images. Thus, when the instant messaging server receives a first payment code image sent by the first terminal device, it compares the first payment code image with the payment code images cached in the cache. If the first payment code image matches a second payment code image in the cache, the payment code detection result of the second image is determined as the payment code detection result of the first image. This avoids the instant messaging server performing duplicate validity checks on the same payment code image, thereby saving technical resources and improving image processing efficiency.

[0183] In some embodiments, if the QR code images cached by the instant messaging server do not include a QR code image matching the first QR code image, the instant messaging server determines the type of the first QR code image and, based on the type of the first QR code image, determines the QR code detection result of the first QR code image. For example, the instant messaging server includes a list of types of QR codes not recommended for the first enterprise. Specifically, the instant messaging server parses the first QR code image and determines that the QR code included in the first QR code image is of type 'a'. Then, it checks whether the locally stored list of types of types of types of types of types of QR codes includes type 'a' of the QR code included in the first QR code image. If the type 'a' of the QR code included in the first QR code image matches one of the types in the list of types of types of types of types of types of QR codes not recommended, then the QR code included in the first QR code image is determined to be an external QR code.

[0184] S204. If the payment code in the first payment code image is an external payment code, the instant messaging server sends a reminder message to the first terminal device.

[0185] The reminder message is used to alert the first recipient to the risks involved in using the payment code in the first payment code image to receive payments.

[0186] In the embodiments of this application, such as Figure 16 As shown, the first object sends a first payment code image to the instant messaging chat interface corresponding to the first enterprise through a first terminal device. The first terminal device then sends the first payment code image to the instant messaging server. Based on the above steps, the instant messaging server performs a validity check on the payment code in the first payment code image. If it determines that the payment code in the first payment code image is an external payment code, it sends a reminder message to the first terminal device.

[0187] This application embodiment does not limit the specific content of the reminder information; it only reminds the recipient in the instant messaging to the risks involved when using the payment code in the first payment code image to receive payment.

[0188] In one example, the reminder message in this application embodiment is as follows: "Using external payment codes to receive money may lead to unclear reconciliation, members skipping orders, etc., which poses risks to the safe operation of enterprises. It is recommended to use a safe payment method."

[0189] S205, The first terminal device displays a reminder message.

[0190] In some embodiments, the display method of the reminder information may differ depending on whether the first enterprise has activated the external payment collection service or not. Therefore, before displaying the reminder information, the first terminal device first obtains the activation information corresponding to the first enterprise, which indicates whether the first enterprise has activated the external payment collection service. Then, based on whether the first enterprise has activated the external payment collection service, the display format of the reminder information is determined, and the reminder information is displayed accordingly.

[0191] In one possible implementation, if the activation information corresponding to the first enterprise indicates that the first enterprise has not activated external payment collection services, then the first terminal device displays a first payment code image and a reminder message in the instant messaging chat interface. This application embodiment does not limit the specific display position of the reminder message in the instant messaging chat interface. For example, the reminder message can be displayed above or below the first payment code image.

[0192] In one possible implementation, if the activation information indicates that the first enterprise has activated its external payment collection business, the first terminal device displays a reminder pop-up window, which includes a reminder message.

[0193] In one example of this implementation, such as Figure 5 As shown, if the first terminal device determines that the first enterprise has activated its external payment collection service, and detects that the payment code included in the first payment code image sent by the first object in the instant messaging chat interface is an external payment code, the first terminal device will not send the first payment code image to the instant messaging chat interface. Instead, it will display a reminder pop-up window containing reminder information. For example, in the instant messaging chat interface, when the first object selects the "send image" option in the dialog box, selects the first payment code image from its local storage, and clicks "send," the first terminal device, in response to the triggering operation of the "send" option, obtains the first payment code image to be sent, and uses the above method to determine whether the payment code included in the first payment code image is an external payment code. If it is determined that the payment code included in the first payment code image is an external payment code, then it will display... Figure 5 The pop-up notification window displays a reminder message. This allows the first recipient to determine whether to continue sending the first payment code image to the instant messaging chat interface based on the reminder message. Therefore, in this implementation, the reminder message also alerts the first recipient to the risks associated with the payment code included in the first payment code image, enabling the first recipient to choose not to send the first payment code image to the instant messaging chat interface, thereby avoiding payment risks for the enterprise and improving the enterprise's management of external payments.

[0194] In some embodiments, such as Figure 5As shown, the pop-up notification also includes an option to use external payment collection. The first object can then trigger this option. In response to the first object's triggering of the external payment collection option in the pop-up notification, the first terminal device displays the external payment information corresponding to the first enterprise in the instant messaging chat interface.

[0195] For example, if the external payment information corresponding to the first enterprise is an external payment mini-program card, the method further includes: in response to the second object's trigger operation on the external payment mini-program card, jumping to display the interface of the external payment mini-program.

[0196] In some embodiments, such as Figure 9 As shown, the pop-up notification also includes a "Continue Sending Payment Code" option. If the first recipient decides to send the first payment code image to the instant messaging chat interface based on the notification information, the first recipient triggers the "Continue Sending Payment Code" option. In response to the first recipient's triggering of this option, the first terminal device displays the first payment code image in the instant messaging chat interface.

[0197] In some embodiments, the present application further includes the following step S206.

[0198] S206. When the payment code in the first payment code image is an external payment code, the instant messaging server sends a risk notification to the administrator's terminal device.

[0199] The first payment code image is the payment code image to be sent by the first object in the instant messaging of the first enterprise, and the risk notification is used to indicate that the first object is using an external payment code to receive payment.

[0200] S207, The administrator's terminal device displays a risk notification.

[0201] This application does not limit the specific method by which the instant messaging server sends risk notifications to the administrator's terminal device.

[0202] In the embodiments of this application, such as Figure 17 As shown, if the instant messaging server determines that the payment code in the first payment code image is an external payment code, it sends a risk notification to the administrator's terminal device.

[0203] In one example, the instant messaging server sends a risk notification to the administrator's terminal device via SMS. The administrator can then view the risk notification in their SMS list.

[0204] In one example, an instant messaging application client is installed on the administrator's terminal device. The instant messaging server can send a notification message, including a risk notification, to the instant messaging application client on the administrator's terminal device. This allows the administrator to view the risk notification in the instant messaging application client.

[0205] S208. When the preset time arrives, the instant messaging server sends the payment summary information to the administrator's terminal device.

[0206] The collection summary information includes at least one of the following: first description information of receiving payments using the first company's external collection information within a preset time period, and second description information of receiving payments using an external payment code.

[0207] S209. The administrator terminal device displays the payment summary information.

[0208] In some embodiments, the display interface for payment summary information further includes an option to disable external payment codes. The method further includes: in response to an administrator's triggering operation to disable the external payment code option, sending an external payment code disabling instruction to an instant messaging server. The external payment code disabling instruction is used to indicate that sending external payment codes in the instant messaging chat interface corresponding to the first enterprise is prohibited.

[0209] In some embodiments, if the first enterprise has not activated its external payment collection service, the display interface of the payment collection summary information also includes an option to activate external payment collection. The method further includes: in response to the administrator's triggering operation on the external payment collection option, sending an activation instruction to the instant messaging server, the activation instruction being used to instruct the first enterprise to activate its external payment collection service.

[0210] In some embodiments, the second description information further includes a view detail icon, and the method further includes: in response to the administrator's triggering operation to view the detail icon, displaying an external payment code usage detail page, the external payment code usage detail page including at least one of the following: object information of the external payment code sending object, the type of external payment code used by the sending object, the number of times different types of external payment codes are used, the sending time of the external payment code, and object information of the external payment code receiving object.

[0211] In some embodiments, the external payment code usage details page also includes a disable external payment code option, and the method further includes: in response to the administrator's triggering operation to disable the external payment code option, sending an external payment code disabling instruction to the instant messaging server, the external payment code disabling instruction being used to instruct that sending external payment codes in the instant messaging chat interface corresponding to the first enterprise is prohibited.

[0212] The specific implementation process of S208 and S209 can be referred to the above. Figure 11The relevant descriptions will not be repeated here.

[0213] The payment management method provided in this application embodiment involves a first terminal device responding to a first object sending a first payment code image in the instant messaging chat interface corresponding to a first enterprise. The first terminal device obtains the first payment code image to be sent and sends it to the instant messaging server. The instant messaging server performs a legality check on the payment code in the first payment code image. If it determines that the payment code in the first payment code image is an external payment code, the instant messaging server sends a reminder message to the first terminal device. The first terminal device displays the reminder message. In some embodiments, when the payment code in the first payment code image is an external payment code, the instant messaging server can also send a risk notification to an administrator terminal device, which displays the risk notification. In some embodiments, the instant messaging server sends a payment summary information to the administrator terminal device when a preset time arrives. Therefore, the payment management method of this application embodiment can accurately identify the payment behavior of individual enterprise members, reminding the first object and / or other objects in the instant messaging chat interface to be cautious in making payments, thereby reducing the enterprise's payment risk. Furthermore, in this embodiment, if the payment code in the first payment code image is an external payment code, the instant messaging server sends a risk notification and payment summary information to the administrator's terminal device. This allows the enterprise administrator to promptly understand the current discouraged payment behaviors within the enterprise, enabling timely intervention or statistical analysis of these behaviors. This improves the enterprise's real-time data detection capabilities, reduces the manpower and time costs of payment management, and allows the enterprise to accurately statistically analyze payment behavior data, thereby enhancing the effectiveness and efficiency of payment management.

[0214] The above text combined Figures 2 to 17 The method embodiments of this application are described in detail below, in conjunction with... Figure 21 The following describes in detail the device embodiments of this application.

[0215] Figure 18 This is a schematic block diagram of a payment management device provided in an embodiment of this application.

[0216] like Figure 18 As shown, the payment management device 10 is applied to the first terminal device and includes:

[0217] The acquisition unit 11 is used to acquire the first payment code image to be sent in response to the sending operation of the first object in the instant messaging chat interface corresponding to the first enterprise.

[0218] Display unit 12 is used to display reminder information. The reminder information is based on the detection of the payment code in the first payment code image, and is displayed when the payment code in the first payment code image is detected as an external payment code. The external payment code is a payment code that the first enterprise does not recommend. The reminder information is used to remind the first object of the risks involved in using the payment code in the first payment code image to receive payments.

[0219] In some embodiments, the display unit 12 is specifically used to obtain the activation information corresponding to the first enterprise, the activation information being used to indicate whether the first enterprise has activated its external payment collection business; and to display the reminder information based on the activation information.

[0220] In some embodiments, the display unit 12 is specifically configured to display the first payment code image and the reminder information in the instant messaging chat interface if the activation information indicates that the first enterprise has not activated the external payment service; and to display a reminder pop-up window, which includes the reminder information, if the activation information indicates that the first enterprise has activated the external payment service.

[0221] In some embodiments, the reminder pop-up also includes an option for receiving payments from outside the recipient. The display unit 12 is further configured to, in response to the first object's triggering operation of the option for receiving payments from outside the recipient in the reminder pop-up, display the external payment information corresponding to the first enterprise in the instant messaging chat interface.

[0222] In some embodiments, if the external payment information corresponding to the first enterprise is an external payment mini-program card, the display unit 12 is further configured to respond to the triggering operation of the second object on the external payment mini-program card and jump to display the interface of the external payment mini-program.

[0223] In some embodiments, the reminder pop-up also includes a "Continue Sending Payment Code" option, and the display unit 12 is further configured to display the first payment code image in the instant messaging chat interface in response to the first object's triggering operation of the "Continue Sending Payment Code" option.

[0224] In some embodiments, the display unit 12 is specifically configured to send the first payment code image to an instant messaging server, receive the reminder information sent by the instant messaging server, and display the received reminder information, wherein the reminder information is sent by the instant messaging server when it detects that the payment code in the first payment code image is the external payment code; or, to detect the payment code in the first payment code image, and display the reminder information when it is detected that the payment code in the first payment code image is the external payment code.

[0225] In some embodiments, the display unit 12 is specifically used to obtain a list of types of non-recommended payment codes corresponding to the first enterprise; perform type detection on the payment code in the first payment code image to obtain the type of the payment code in the first payment code image; if the type of the payment code in the first payment code image is one of the types in the list of non-recommended payment codes, then the payment code in the first payment code image is determined to be the external payment code.

[0226] In some embodiments, the display unit 12 is further configured to compare the first payment code image with payment code images cached in a first cache area, the first cache area including payment code images sent by the first object within a preset time period; if no payment code image matching the first payment code image is found in the first cache area, then a list of types of non-recommended payment codes corresponding to the first enterprise is obtained.

[0227] In some embodiments, the display unit 12 is further configured to determine the payment code detection result of the second payment code image as the payment code detection result of the first payment code image if the first payment code image is consistent with the second payment code image in the first cache area, wherein the payment code detection result includes whether the payment code is the external payment code or the payment code is not the external payment code.

[0228] It should be understood that the device embodiments and method embodiments can correspond to each other, and similar descriptions can be referred to the method embodiments. To avoid repetition, further details will not be provided here. Specifically, Figure 18 The apparatus shown can perform the embodiments of the above-described method, and the foregoing and other operations and / or functions of each module in the apparatus are respectively for implementing the method embodiments on the first terminal device side. For the sake of brevity, they will not be described in detail here.

[0229] Figure 19 This is a schematic block diagram of a payment management device provided in an embodiment of this application.

[0230] like Figure 19 As shown, the payment management device 20, applied to an instant messaging server, includes:

[0231] The transceiver unit 21 is used to send a risk notification to the administrator terminal device. The risk notification is sent when it is detected that the payment code in the first payment code image is an external payment code. The external payment code is a payment code that the first enterprise does not recommend. The first payment code image is a payment code image to be sent by the first object in the instant messaging of the first enterprise. The risk notification is used to indicate that the first object is using an external payment code to receive payment.

[0232] In some embodiments, the transceiver unit 21 is further configured to send payment summary information to the administrator terminal device when a preset time arrives. The payment summary information includes at least one of a first description of payment collection using the external payment information corresponding to the first enterprise within a preset time period and a second description of payment collection using the external payment code.

[0233] In some embodiments, the transceiver unit 21 is further configured to receive a first payment code image sent by a first terminal device, wherein the first payment code image is a payment code image to be sent by a first object in an instant messaging chat interface corresponding to a first enterprise; perform a legality check on the payment code in the first payment code image; and if the payment code in the first payment code image is an external payment code, send a reminder message to the first terminal device, wherein the reminder message is used to remind the first object of the risks involved in using the payment code in the first payment code image for payment.

[0234] In some embodiments, the transceiver unit 21 is specifically used to obtain a list of types of non-recommended payment codes corresponding to the first enterprise; perform type detection on the payment code in the first payment code image to obtain the type of the payment code in the first payment code image; if the type of the payment code in the first payment code image is one of the types in the list of non-recommended payment codes, then determine that the payment code in the first payment code image is the external payment code.

[0235] In some embodiments, the transceiver unit 21 is further configured to compare the first payment code image with payment code images cached in a second cache, the second cache including payment code images sent by each terminal device within a preset time period; if no payment code image matching the first payment code image is found in the second cache, then a list of types of non-recommended payment codes corresponding to the first enterprise is obtained.

[0236] In some embodiments, the transceiver unit 21 is further configured to determine the payment code detection result of the second payment code image as the payment code detection result of the first payment code image if the first payment code image is consistent with the second payment code image in the second cache area, wherein the payment code detection result includes whether the payment code is the external payment code or whether the payment code is not the external payment code.

[0237] It should be understood that the device embodiments and method embodiments can correspond to each other, and similar descriptions can be referred to the method embodiments. To avoid repetition, further details will not be provided here. Specifically, Figure 19 The apparatus shown can perform the embodiments of the above-described method, and the foregoing and other operations and / or functions of each module in the apparatus are respectively for implementing the above-described instant messaging server-side method embodiments, which will not be described in detail here for the sake of brevity.

[0238] Figure 20 This is a schematic block diagram of a payment management device provided in an embodiment of this application.

[0239] like Figure 20 As shown, the payment management device 30, applied to the administrator terminal device, includes:

[0240] The transceiver unit 31 is used to receive a risk notification sent by an instant messaging server. The risk notification is used to indicate that the first object is using an external payment code to receive payment. The external payment code is a payment code that the first enterprise does not recommend. The risk notification is sent when the payment code in the first payment code image is detected to be an external payment code. The first payment code image is a payment code image to be sent by the first object in the instant messaging of the first enterprise.

[0241] Display unit 32 is used to display the risk notification.

[0242] In some embodiments, the transceiver unit 31 is further configured to receive payment summary information sent by the instant messaging server, the payment summary information including at least one of first description information of receiving payments using the first enterprise's external payment information within a preset time period and second description information of receiving payments using external payment codes; the display unit 32 is further configured to display the payment summary information.

[0243] In some embodiments, the display interface for the payment summary information further includes an option to disable external payment codes. The sending and receiving unit 31 is also configured to send an external payment code disabling instruction to the instant messaging server in response to the administrator's triggering operation of the external payment code disabling option. The external payment code disabling instruction is used to indicate that sending external payment codes in the instant messaging chat interface corresponding to the first enterprise is prohibited.

[0244] In some embodiments, if the first enterprise has not activated its external payment collection service, the display interface of the payment collection summary information further includes an option to activate external payment collection. The sending and receiving unit 31 is also used to send an activation instruction to the instant messaging server in response to the administrator's triggering operation on the external payment collection option. The activation instruction is used to instruct the first enterprise to activate its external payment collection service.

[0245] In some embodiments, the second description information further includes a view details icon. The transceiver unit 31 is also configured to display an external payment code usage details page in response to the administrator's trigger operation on the view details icon. The external payment code usage details page includes at least one of the following: object information of the external payment code sender, the type of external payment code used by the sender, the number of times different types of external payment codes are used, the sending time of the external payment code, and object information of the external payment code receiver.

[0246] In some embodiments, the external payment code usage details page further includes a disable external payment code option. The sending and receiving unit 31 is also configured to send an external payment code disable instruction to the instant messaging server in response to the administrator's triggering operation of the disable external payment code option. The external payment code disable instruction is used to indicate that sending external payment codes in the instant messaging chat interface corresponding to the first enterprise is prohibited.

[0247] It should be understood that the device embodiments and method embodiments can correspond to each other, and similar descriptions can be referred to the method embodiments. To avoid repetition, further details will not be provided here. Specifically, Figure 20 The apparatus shown can perform the embodiments of the above-described method, and the foregoing and other operations and / or functions of each module in the apparatus are respectively for implementing the method embodiments on the administrator terminal device side. For the sake of brevity, they will not be described in detail here.

[0248] The apparatus of this application embodiment has been described above from the perspective of functional modules in conjunction with the accompanying drawings. It should be understood that this functional module can be implemented in hardware, in software instructions, or in a combination of hardware and software modules. Specifically, the steps of the method embodiments in this application can be completed by integrated logic circuits in the processor's hardware and / or by software instructions. The steps of the method disclosed in this application embodiment can be directly embodied as being executed by a hardware decoding processor, or by a combination of hardware and software modules in the decoding processor. Optionally, the software module can reside in a mature storage medium in the art, such as random access memory, flash memory, read-only memory, programmable read-only memory, electrically erasable programmable memory, registers, etc. This storage medium is located in memory, and the processor reads information from the memory and, in conjunction with its hardware, completes the steps in the above method embodiments.

[0249] Figure 21 This is a schematic block diagram of an electronic device provided in an embodiment of this application. The electronic device may be the first terminal device, an instant messaging server, or an administrator terminal device as described above.

[0250] like Figure 21 As shown, the electronic device 40 may include:

[0251] The system includes a memory 41 and a processor 42. The memory 41 stores a computer program 43 and transfers the program code 43 to the processor 42. In other words, the processor 42 can retrieve and run the computer program 43 from the memory 41 to implement the methods described in the embodiments of this application.

[0252] For example, the processor 42 can be used to execute the steps in the method 200 described above according to the instructions in the computer program 43.

[0253] In some embodiments of this application, the processor 42 may include, but is not limited to:

[0254] General-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc.

[0255] In some embodiments of this application, the memory 41 includes, but is not limited to:

[0256] Volatile memory and / or non-volatile memory. Non-volatile memory can be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), or flash memory. Volatile memory can be random access memory (RAM), which is used as an external cache. By way of example, but not limitation, many forms of RAM are available, such as Static RAM (SRAM), Dynamic RAM (DRAM), Synchronous DRAM (SDRAM), Double Data Rate SDRAM (DDR SDRAM), Enhanced Synchronous DRAM (ESDRAM), Synchronous Link DRAM (SLDRAM), and Direct Rambus RAM (DR RAM).

[0257] In some embodiments of this application, the computer program 43 may be divided into one or more modules, which are stored in the memory 41 and executed by the processor 42 to complete the page recording method provided in this application. The one or more modules may be a series of computer program instruction segments capable of performing specific functions, which describe the execution process of the computer program 43 in the electronic device.

[0258] like Figure 21 As shown, the electronic device 40 may further include:

[0259] Transceiver 44, which can be connected to processor 42 or memory 41.

[0260] The processor 42 can control the transceiver 44 to communicate with other devices; specifically, it can send information or data to other devices or receive information or data sent by other devices. The transceiver 44 may include a transmitter and a receiver. The transceiver 44 may further include antennas, and the number of antennas may be one or more.

[0261] It should be understood that the various components in the electronic device 40 are connected through a bus system, which includes a data bus, a power bus, a control bus, and a status signal bus.

[0262] According to one aspect of this application, a computer storage medium is provided that stores a computer program thereon, which, when executed by a computer, enables the computer to perform the methods of the above-described method embodiments. Alternatively, embodiments of this application also provide a computer program product containing instructions that, when executed by a computer, cause the computer to perform the methods of the above-described method embodiments.

[0263] According to another aspect of this application, a computer program product or computer program is provided, comprising computer instructions stored in a computer-readable storage medium. A processor of a computer device reads the computer instructions from the computer-readable storage medium and executes the computer instructions, causing the computer device to perform the method described in the above-described method embodiments.

[0264] In other words, when implemented using software, it can be implemented wholly or partially in the form of a computer program product. This computer program product includes one or more computer instructions. When these computer program instructions are loaded and executed on a computer, all or part of the processes or functions described in the embodiments of this application are generated. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, the computer instructions can be transmitted from one website, computer, server, or data center to another via wired (e.g., coaxial cable, fiber optic, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) means. The computer-readable storage medium can be any available medium that a computer can access or a data storage device such as a server or data center that integrates one or more available media. The available medium can be a magnetic medium (e.g., floppy disk, hard disk, magnetic tape), an optical medium (e.g., digital video disc (DVD)), or a semiconductor medium (e.g., solid-state disk (SSD)).

[0265] Those skilled in the art will recognize that the modules and algorithm steps of the various examples described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

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

[0267] The modules described as separate components may or may not be physically separate. The components shown as modules may or may not be physical modules; that is, they may be located in one place or distributed across multiple network units. Some or all of the modules can be selected to achieve the purpose of this embodiment according to actual needs. For example, the functional modules in the various embodiments of this application may be integrated into one processing module, or each module may exist physically separately, or two or more modules may be integrated into one module.

[0268] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

Claims

1. A payment management method, characterized in that, Applied to a first terminal device, the method includes: In response to the first object sending the first payment code image in the instant messaging chat interface corresponding to the first enterprise, obtain the first payment code image to be sent; The system displays a reminder message. This reminder message is generated when the payment code in the first payment code image is detected as an external payment code. The external payment code is a payment code that the first enterprise does not recommend. The reminder message is used to remind the first object of the risks involved in using the payment code in the first payment code image to receive payments.

2. The method according to claim 1, characterized in that, The displayed reminder information includes: Obtain the activation information corresponding to the first enterprise, wherein the activation information is used to indicate whether the first enterprise has activated the external payment collection business; Based on the activation information, the reminder information is displayed.

3. The method according to claim 2, characterized in that, The step of displaying the reminder information based on the activation information includes: If the activation information indicates that the first enterprise has not activated the external payment service, then the first payment code image and the reminder information are displayed in the instant messaging chat interface; If the activation information indicates that the first enterprise has activated the external payment collection service, a reminder pop-up window will be displayed, which includes the reminder information.

4. The method according to claim 3, characterized in that, The pop-up notification also includes an option to receive payments externally, and the method further includes: In response to the first object's triggering operation on the external payment collection option in the reminder pop-up window, the external payment collection information corresponding to the first enterprise is displayed in the instant messaging chat interface.

5. The method according to claim 4, characterized in that, The pop-up notification also includes an option to continue sending the payment code, and the method further includes: In response to the first object's triggering of the option to continue sending the payment code, the first payment code image is displayed in the instant messaging chat interface.

6. The method according to any one of claims 1-5, characterized in that, The displayed reminder information includes: Send the first payment code image to the instant messaging server, receive the notification information sent by the instant messaging server, and display the received notification information. The notification information is sent by the instant messaging server when it detects that the payment code in the first payment code image is the external payment code; or... The payment code in the first payment code image is detected, and when the payment code in the first payment code image is detected to be the external payment code, the reminder information is displayed.

7. The method according to claim 6, characterized in that, The detection of the payment code in the first payment code image includes: Obtain the list of types of non-recommended QR codes corresponding to the first enterprise; Perform type detection on the QR code in the first QR code image to obtain the type of the QR code in the first QR code image; If the type of the payment code in the first payment code image is one of the types in the list of unrecommended payment code types, then the payment code in the first payment code image is determined to be the external payment code.

8. The method according to claim 7, characterized in that, Before obtaining the list of types of non-recommended payment codes corresponding to the first enterprise, the method further includes: The first payment code image is compared with the payment code images cached in the first cache area, the first cache area including payment code images sent by the first object within a preset time period; The step of detecting the payment code in the first payment code image to obtain the type of payment code included in the first payment code image includes: If no payment code image matching the first payment code image is found in the first cache area, then the list of types of payment codes that are not recommended for the first enterprise is obtained.

9. A payment management method, characterized in that, Applied to an instant messaging server, the method includes: A risk notification is sent to the administrator's terminal device. The risk notification is sent when it is detected that the payment code in the first payment code image is an external payment code. The external payment code is a payment code that the first enterprise does not recommend. The first payment code image is a payment code image to be sent by the first object in the instant messaging of the first enterprise. The risk notification is used to indicate that the first object is using an external payment code to receive payment.

10. The method according to claim 9, characterized in that, The method further includes: When the preset time arrives, a collection summary information is sent to the administrator terminal device. The collection summary information includes at least one of the following: first description information of collection using the external collection information corresponding to the first enterprise within the preset time period and second description information of collection using the external collection code.

11. The method according to claim 10, characterized in that, The method further includes: Receive a first payment code image sent by a first terminal device, wherein the first payment code image is a payment code image to be sent by the first object in the instant messaging chat interface corresponding to the first enterprise; The payment code in the first payment code image is detected; If the payment code in the first payment code image is the external payment code, a reminder message is sent to the first terminal device. The reminder message is used to remind the first object of the risks involved in using the payment code in the first payment code image to receive payments.

12. The method according to claim 11, characterized in that, The detection of the payment code in the first payment code image includes: Obtain the list of types of non-recommended QR codes corresponding to the first enterprise; Perform type detection on the QR code in the first QR code image to obtain the type of the QR code in the first QR code image; If the type of the payment code in the first payment code image is one of the types in the list of unrecommended payment code types, then the payment code in the first payment code image is determined to be the external payment code.

13. The method according to claim 12, characterized in that, Before obtaining the list of types of non-recommended payment codes corresponding to the first enterprise, the method further includes: The first payment code image is compared with the payment code images cached in the second cache area, which includes payment code images sent by each terminal device within a preset time period. The step of obtaining the list of types of non-recommended payment codes corresponding to the first enterprise includes: If no payment code image matching the first payment code image is found in the second cache area, then the list of types of non-recommended payment codes corresponding to the first enterprise is obtained.

14. A payment management method, characterized in that, Applied to an administrator terminal device, the method includes: The system receives a risk notification sent by an instant messaging server. The risk notification is used to indicate that the first object is using an external payment code to receive payment. The external payment code is a payment code that the first enterprise does not recommend. The risk notification is sent when the payment code in the first payment code image is detected to be the external payment code. The first payment code image is a payment code image to be sent by the first object in the instant messaging of the first enterprise. The risk notification will be displayed.

15. The method according to claim 14, characterized in that, The method further includes: Receive payment summary information sent by the instant messaging server. The payment summary information includes at least one of the following: first description information of receiving payments using the first enterprise's external payment information within a preset time period and second description information of receiving payments using the external payment code. Display the summary information of the payments received.

16. The method according to claim 15, characterized in that, The interface for displaying the payment summary information also includes an option to disable external payment codes, and the method further includes: In response to the administrator's triggering of the option to disable external payment codes, an external payment code disabling instruction is sent to the instant messaging server. The external payment code disabling instruction is used to indicate that sending external payment codes in the instant messaging chat interface corresponding to the first enterprise is prohibited.

17. The method according to claim 15 or 16, characterized in that, If the first enterprise has not activated its external payment collection service, the display interface for the payment collection summary information also includes an option to activate external payment collection. The method further includes: In response to the administrator's triggering operation on the external payment collection option, an activation command is sent to the instant messaging server, the activation command being used to instruct the first enterprise to activate its external payment collection service.

18. The method according to claim 17, characterized in that, The second description information also includes viewing detailed icons, and the method further includes: In response to the administrator's triggering operation on the view details icon, the external payment code usage details page is displayed. The external payment code usage details page includes at least one of the following: object information of the external payment code sender, type of external payment code used by the sender, number of times different types of external payment codes are used, sending time of the external payment code, and object information of the external payment code receiver.

19. The method according to claim 18, characterized in that, The external payment code usage details page also includes an option to disable the external payment code, and the method further includes: In response to the administrator's triggering of the option to disable external payment codes, an external payment code disabling instruction is sent to the instant messaging server. The external payment code disabling instruction is used to indicate that sending external payment codes in the instant messaging chat interface corresponding to the first enterprise is prohibited.

20. A payment management device, characterized in that, Applied to a first terminal device, the device includes: The acquisition unit is used to acquire the first payment code image to be sent in response to the sending operation of the first object in the instant messaging chat interface corresponding to the first enterprise. The display unit is used to display reminder information. The reminder information is based on the detection of the payment code in the first payment code image, and is displayed when the payment code in the first payment code image is detected as an external payment code. The external payment code is a payment code that the first enterprise does not recommend. The reminder information is used to remind the first object of the risks involved in using the payment code in the first payment code image to receive payments.

21. A payment management device, characterized in that, The device, used in an instant messaging server, includes: The transceiver unit is used to send a risk notification to the administrator terminal device. The risk notification is sent when it is detected that the payment code in the first payment code image is an external payment code. The external payment code is a payment code that is not recommended by the first enterprise. The first payment code image is a payment code image to be sent by the first object in the instant messaging of the first enterprise. The risk notification is used to indicate that the first object is using an external payment code to receive payment.

22. A payment management device, characterized in that, The device, applied to an administrator terminal device, includes: The transceiver unit is used to receive a risk notification sent by an instant messaging server. The risk notification is used to indicate that the first object is using an external payment code to receive payment. The external payment code is a payment code that is not recommended by the first enterprise. The risk notification is sent when the payment code in the first payment code image is detected to be the external payment code. The first payment code image is a payment code image to be sent by the first object in the instant messaging of the first enterprise. The display unit is used to display the risk notification.

23. An electronic device, characterized in that, Including processor and memory; The memory is used to store computer programs; The processor is configured to execute the computer program to implement the method as described in any one of claims 1 to 8, 9 to 13, or 14 to 19.

24. A computer-readable storage medium, characterized in that, Used to store computer programs; The computer program causes the computer to perform the method as described in any one of claims 1 to 8, 9 to 13, or 14 to 19.

Images