Payment verification method and device, computer equipment and storage medium

Abstract

The invention relates to a payment verification method and device, computer equipment and a storage medium. The method comprises the following steps: acquiring payment verification messages corresponding to multiple tenants sent by a server; analyzing the payment verification message corresponding to each tenant to obtain a corresponding payment verification task; determining a corresponding operation equipment type according to each payment verification task; and calling an operation device corresponding to the operation device type, and performing payment verification on the payment verification task through the operation device. By adopting the method, the payment verification efficiency can be improved, and a multi-tenant environment is supported.

Description

Technical Field

[0001] The present application relates to the field of computer technology, and in particular to a payment verification method, apparatus, computer equipment and storage medium. Background Art

[0002] In the field of e-commerce and financial technology, payment verification is a key link to ensure the security and validity of transactions. Traditional payment verification methods usually involve multiple steps, including manually creating an order, selecting a payment method and device, and manually executing the payment process. These methods are often time-consuming and prone to errors.

[0003] Currently, there are some automated payment verification solutions on the market, such as automated testing frameworks integrated with APIs, which can simulate user operations and automatically execute payment processes. However, these solutions are usually limited to specific payment channels or devices and do not support the complexity of multi-tenant environments. Summary of the invention

[0004] Based on this, it is necessary to provide a payment verification method, device, computer equipment and storage medium that can improve payment verification efficiency and support a multi-tenant environment in response to the above technical problems.

[0005] A payment verification method, the method comprising:

[0006] Obtaining a payment verification message corresponding to the multi-tenant sent by the server, wherein the server generates the payment verification message based on the multi-tenant information, user behavior information, and payment type information;

[0007] Parse the payment verification message corresponding to each tenant and obtain the corresponding payment verification task;

[0008] Determine the corresponding operation device type according to each payment verification task;

[0009] The operating device corresponding to the operating device type is called up, and payment verification is performed on the payment verification task through the operating device.

[0010] In one embodiment, the server generates a payment verification message based on the multi-tenancy, user behavior information and payment type information, including:

[0011] The server obtains user behavior information and determines the corresponding product information based on the user behavior information;

[0012] The server determines the corresponding tenant based on the product information;

[0013] The server obtains different payment type information of the tenant;

[0014] The server assembles user behavior information, product information, and tenant information to obtain the order to be paid;

[0015] The server generates corresponding payment links based on the order to be paid and different payment type information;

[0016] The server generates a payment verification message based on the order to be paid, the payment link and the payment type information.

[0017] In one embodiment, the server generates a payment verification message according to the order to be paid, the payment link and the payment type information, including:

[0018] The server associates tasks and verification plans for payment links;

[0019] The server generates a payment verification message based on the order to be paid, the associated payment link and the payment type information.

[0020] In one embodiment, calling up an operating device corresponding to the operating device type includes:

[0021] Obtain the operating device type in each payment verification task;

[0022] The operation device corresponding to the operation device type is called through the automated testing tool.

[0023] In one embodiment, performing payment verification on a payment verification task by operating a device includes:

[0024] Open the target application on the operating device;

[0025] Control the target application to perform payment verification on the payment verification task.

[0026] In one embodiment, controlling the target application to perform payment verification on the payment verification task includes:

[0027] Obtain the payment verification link and payment verification information of the payment verification task;

[0028] Control the target application to access the payment verification link, call the payment interface, and perform payment verification on the payment verification information.

[0029] In one embodiment, after performing payment verification on the payment verification task by operating the device, the method includes:

[0030] Get device verification results;

[0031] The device verification result is returned to the server, so that the server can provide feedback based on the device verification result.

[0032] A payment verification device, comprising:

[0033] An acquisition module, used to acquire a payment verification message corresponding to the multi-tenant sent by the server, wherein the server generates the payment verification message based on the multi-tenant information, the user behavior information and the payment type information;

[0034] The parsing module is used to parse the payment verification message corresponding to each tenant and obtain the corresponding payment verification task;

[0035] A determination module, used to determine the corresponding operation device type according to each payment verification task;

[0036] The verification module is used to call up the operating device corresponding to the operating device type and perform payment verification on the payment verification task through the operating device.

[0037] A computer device comprises a memory, a processor and a computer program stored in the memory and executable on the processor, wherein when the processor executes the computer program, the following steps are implemented:

[0038] Obtaining a payment verification message corresponding to the multi-tenant sent by the server, wherein the server generates the payment verification message based on the multi-tenant information, user behavior information, and payment type information;

[0039] Parse the payment verification message corresponding to each tenant and obtain the corresponding payment verification task;

[0040] Determine the corresponding operation device type according to each payment verification task;

[0041] The operating device corresponding to the operating device type is called up, and payment verification is performed on the payment verification task through the operating device.

[0042] A computer-readable storage medium stores a computer program, which, when executed by a processor, implements the following steps:

[0043] Obtaining a payment verification message corresponding to the multi-tenant sent by the server, wherein the server generates the payment verification message based on the multi-tenant information, user behavior information, and payment type information;

[0044] Parse the payment verification message corresponding to each tenant and obtain the corresponding payment verification task;

[0045] Determine the corresponding operation device type according to each payment verification task;

[0046] The operating device corresponding to the operating device type is called up, and payment verification is performed on the payment verification task through the operating device.

[0047] The above-mentioned payment verification method, device, computer equipment and storage medium obtain the payment verification message corresponding to the multiple tenants sent by the server; parse the payment verification message corresponding to each tenant to obtain the corresponding payment verification task; determine the corresponding operation device type according to each payment verification task; call up the operation device corresponding to the operation device type, and perform payment verification on the payment verification task through the operation device. Therefore, the server automatically assembles the product information and generates the payment verification message according to the needs of different tenants and users, and sends it to the client. The client performs payment verification on the payment verification message, verifies it through the operation device corresponding to the operation type, and automatically operates to simulate the user to complete the payment process, realizes fully automatic payment verification, improves payment verification efficiency, and supports multi-tenant environments. BRIEF DESCRIPTION OF THE DRAWINGS

[0048] Figure 1 A diagram of an application environment of a payment verification method in an embodiment;

[0049] Figure 2 A schematic diagram of a payment verification method in one embodiment;

[0050] Figure 3 A flowchart of the operation steps of the server in one embodiment;

[0051] Figure 4 A schematic diagram of a process for generating a payment verification message in one embodiment;

[0052] Figure 5 A schematic diagram of a flow chart of steps for operating a device invocation in one embodiment;

[0053] Figure 6 A schematic diagram of a payment verification process in one embodiment;

[0054] Figure 7 A schematic diagram of a process flow of a target application verification step in one embodiment;

[0055] Figure 8 A schematic diagram of a process for obtaining a device verification result in one embodiment;

[0056] Fig. 9 It is a structural block diagram of a payment verification device in one embodiment;

[0057] Fig.10 FIG. 4 is a diagram showing the internal structure of a computer device in one embodiment. DETAILED DESCRIPTION

[0058] In order to make the purpose, technical solution and advantages of the present application more clearly understood, the present application is further described in detail below in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain the present application and are not used to limit the present application.

[0059] The payment verification method provided in this application can be applied to Figure 1 In the application environment shown, the terminal 102 communicates with the server 104 through the network. The terminal 102 can be, but is not limited to, various personal computers, laptops, smart phones, tablet computers, and portable wearable devices, and the server 104 can be implemented by an independent server or a server cluster composed of multiple servers.

[0060] Specifically, the terminal 102 obtains the payment verification messages corresponding to the multiple tenants sent by the server 104, parses the payment verification messages corresponding to each tenant, obtains the corresponding payment verification tasks, determines the corresponding operating device types according to each payment verification task, calls up the operating device corresponding to the operating device type, and performs payment verification on the payment verification tasks through the operating device.

[0061] In one embodiment, Figure 2 As shown, a payment verification method is provided, which is applied to Figure 1 The server in the example is used as an example to illustrate, including the following steps:

[0062] Step 202, obtaining the payment verification message corresponding to the multi-tenants sent by the server, and the server generates the payment verification message based on the multi-tenant information, user behavior information and payment type information.

[0063] Among them, the payment verification message is used to verify the payment operation of the user under the tenant. The payment verification message is generated by the server. The server automatically assembles the information required to generate the goods and generate the order according to the tenant and the user, and then generates it based on the payment-related information. The payment-related information includes the payment channel, payment method and payment device.

[0064] Specifically, the server generates payment verification messages corresponding to multiple tenants based on multi-tenant information, user behavior information and payment type information, and sends the payment verification messages of each tenant to a message queue. The messages in the message queue are sent to the client asynchronously.

[0065] Step 204: parse the payment verification message corresponding to each tenant to obtain the corresponding payment verification task.

[0066] Specifically, after obtaining the payment verification message, the payment verification message is parsed to obtain the corresponding payment verification task. Specifically, the payment verification message can be interpreted, the message content in the payment verification message is obtained, the message content is interpreted, and the payment verification task is obtained.

[0067] Step 206: Determine the corresponding operating device type according to each payment verification task.

[0068] Specifically, the operating device type in the payment verification task is obtained, where the operating device type is the type of the operating device that performs the payment verification, such as an Android system or an IOS system.

[0069] Step 208: call up the operating device corresponding to the operating device type, and perform payment verification on the payment verification task through the operating device.

[0070] Specifically, after determining the operating device type, call up the operating device corresponding to the operating device type, open the designated application on the operating device, verify the payment verification task through the designated application, and execute the payment operation, including automatically filling in the payment information and completing the payment.

[0071] In the above payment verification method, the payment verification message corresponding to the multiple tenants sent by the server is obtained; the payment verification message corresponding to each tenant is parsed to obtain the corresponding payment verification task; the corresponding operation device type is determined according to each payment verification task; the operation device corresponding to the operation device type is called up, and the payment verification task is verified through the operation device. Therefore, the server automatically assembles the product information and generates the payment verification message according to the needs of different tenants and users, and sends it to the client. The client verifies the payment verification message and verifies it through the operation device corresponding to the operation type. The automatic operation simulates the user to complete the payment process, realizes fully automatic payment verification, improves the payment verification efficiency, and supports multi-tenant environments.

[0072] In one embodiment, Figure 3 As shown, the server generates a payment verification message based on multi-tenant information, user behavior information and payment type information, including:

[0073] Step 302: The server obtains user behavior information and determines corresponding product information according to the user behavior information.

[0074] Step 304: The server determines corresponding tenant information based on the product information.

[0075] Step 306: The server obtains different payment type information under the tenant information.

[0076] Among them, user behavior information is information related to user behavior, and the corresponding product information can be determined through the user behavior information, and the user behavior information can be parsed to obtain information related to the product in the user behavior information to obtain product information. For example, the user behavior information is information related to the refueling of the user's vehicle, and the gas station where the user refuels can be determined through the information related to the refueling of the user's vehicle to obtain product information.

[0077] Each product is associated with corresponding tenant information. Therefore, after determining the product information, the tenant to which it belongs is determined through the product information. Furthermore, the tenant pre-associates multiple different payment types based on actual business conditions and actual application scenarios. After determining the tenant, the different payment type information associated with the tenant is obtained. The payment type information includes payment channel, payment method and payment device.

[0078] Step 308: The server assembles the user behavior information, product information and tenant information to obtain the order to be paid.

[0079] Step 310: The server generates a corresponding payment link according to the order to be paid and different payment type information.

[0080] Step 312: The server generates a payment verification message according to the order to be paid, the payment link and the payment type information.

[0081] Specifically, the server assembles the user behavior information, product information and tenants to obtain the order to be paid. Further, the server generates a payment link based on the order to be paid and different payment type information, where the payment link can be an H5 payment link.

[0082] After obtaining the payment link, the server assembles the order to be paid, the payment link and the payment type information to generate a payment verification message. The payment verification message is used to verify whether the payment operation can be paid normally.

[0083] In one embodiment, Figure 4 As shown, the server generates a payment verification message based on the order to be paid, the payment link and the payment type information, including:

[0084] Step 402, the server associates the payment link with the task and the verification plan.

[0085] Step 404: the server generates a payment verification message according to the order to be paid, the associated payment link and the payment type information.

[0086] The payment link can be associated with tasks and verification plans according to actual business needs and actual application scenarios, and the associated payment link, payment type information, and order to be paid can be used to generate a payment verification message. When verifying the payment verification message, verification can be performed according to the tasks and verification plans.

[0087] In one embodiment, Figure 5 As shown, calling up the operating device corresponding to the operating device type includes:

[0088] Step 502: Obtain the operating device type in each payment verification task.

[0089] Step 504: Call the operating device corresponding to the operating device type through the automated testing tool.

[0090] The operating device type is the type of operating device for payment verification, such as an Android system or an IOS system. Specifically, after obtaining the payment verification task, the operating device type in the payment verification task is obtained, and then the operating device corresponding to the operating type is called through the automated testing tool App i um. The automated testing tool App i um can implement cross-platform payment execution, including automatically opening payment links on different operating systems and devices, executing payment operations, and verifying payment results.

[0091] In one embodiment, Figure 6 As shown, the payment verification task is performed by operating the device, including:

[0092] Step 602: Open the target application in the operating device.

[0093] Step 604: Control the target application to perform payment verification on the payment verification task.

[0094] Among them, the target application is installed on the operating device, and the target application here is used to perform payment verification on the payment verification task. After determining the operating device, open the target application in the operating device, and control the target application to perform payment verification on the payment verification task, including automatically filling in payment information and completing payment.

[0095] In one embodiment, Figure 7 As shown, the target application is controlled to perform payment verification on the payment verification task, including:

[0096] Step 702: Obtain the payment verification link and payment verification information of the payment verification task.

[0097] Step 704, control the target application to access the payment verification link, call the payment interface, and perform payment verification on the payment verification information.

[0098] Among them, controlling the target application to perform payment verification on the payment verification task may specifically include parsing the payment verification task, obtaining the payment verification link and payment verification information in the payment verification task, and the payment verification information includes payment information and payment password.

[0099] Further, open the target application, control the target application to access the payment verification link, enter the payment verification page, call the payment interface, enter the payment verification information in the payment verification page, for example, fill in the payment information and payment account password, etc., to realize the payment verification of the payment verification information.

[0100] In one embodiment, Figure 8 As shown, after the payment verification task is performed by operating the device, the following steps are included:

[0101] Step 802, obtaining device verification results.

[0102] Step 804, returning the device verification result to the server, so that the server provides feedback according to the device verification result.

[0103] Among them, after the operating device performs payment verification on the payment verification task, a device verification result is generated. The client needs to return the device verification result to the server. After the server receives the device verification result, it needs to provide feedback based on the device verification result. The device verification result includes payment status, such as payment success, payment failure, payment cancellation, payment timeout, etc. This information needs to be returned to the server. After the server collects this information, it will provide feedback to understand the reasons for the payment verification, etc., to avoid the same problem in the next payment verification.

[0104] It should be understood that, although the various steps in the above-mentioned flow chart are displayed in sequence according to the indication of the arrows, these steps are not necessarily executed in sequence according to the order indicated by the arrows. Unless there is a clear explanation in this article, the execution of these steps is not strictly limited in order, and these steps can be executed in other orders. Moreover, at least a part of the steps in the above-mentioned flow chart may include a plurality of sub-steps or a plurality of stages, and these sub-steps or stages are not necessarily executed at the same time, but can be executed at different times, and the execution order of these sub-steps or stages is not necessarily to be carried out in sequence, but can be executed in turn or alternately with other steps or at least a part of the sub-steps or stages of other steps.

[0105] In one embodiment, Fig. 9 As shown, a payment verification device 900 is provided, comprising: an acquisition module 902, a parsing module 904, a determination module 906 and a verification module 908, wherein:

[0106] The acquisition module 902 is used to acquire the payment verification message corresponding to the multi-tenants sent by the server, wherein the server generates the payment verification message based on the multi-tenant information, user behavior information and payment type information.

[0107] The parsing module 904 is used to parse the payment verification message corresponding to each tenant to obtain a corresponding payment verification task.

[0108] The determination module 906 is used to determine the corresponding operation device type according to each payment verification task.

[0109] The verification module 908 is used to call up the operating device corresponding to the operating device type, and perform payment verification on the payment verification task through the operating device.

[0110] In one embodiment, the verification module 908 obtains the type of operating device in each payment verification task, and calls the operating device corresponding to the operating device type through an automated testing tool.

[0111] In one embodiment, the verification module 908 opens the target application in the operating device and controls the target application to perform payment verification on the payment verification task.

[0112] In one embodiment, the verification module 908 obtains the payment verification link and payment verification information of the payment verification task, controls the target application to access the payment verification link, calls the payment interface, and performs payment verification on the payment verification information.

[0113] In one embodiment, the payment verification apparatus 900 obtains the device verification result, and returns the device verification result to the server, so that the server provides feedback according to the device verification result.

[0114] For the specific definition of the payment verification device, please refer to the definition of the payment verification method above, which will not be repeated here. Each module in the above-mentioned payment verification device can be implemented in whole or in part by software, hardware and a combination thereof. The above-mentioned modules can be embedded in or independent of the processor in the computer device in the form of hardware, or can be stored in the memory of the computer device in the form of software, so that the processor can call and execute the operations corresponding to the above modules.

[0115] In one embodiment, a computer device is provided. The computer device may be a terminal, and its internal structure diagram may be as follows: Fig.10 As shown. The computer device includes a processor, a memory, a network interface, a display screen and an input device connected through a system bus. Among them, the processor of the computer device is used to provide computing and control capabilities. The memory of the computer device includes a non-volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system and a computer program. The internal memory provides an environment for the operation of the operating system and the computer program in the non-volatile storage medium. The network interface of the computer device is used to communicate with an external terminal through a network connection. When the computer program is executed by the processor, a payment verification method is implemented. The display screen of the computer device can be a liquid crystal display screen or an electronic ink display screen, and the input device of the computer device can be a touch layer covering the display screen, or a key, trackball or touchpad set on the computer device housing, or an external keyboard, touchpad or mouse, etc.

[0116] Those skilled in the art will understand that Fig.10 The structure shown in the figure is only a block diagram of a part of the structure related to the solution of the present application, and does not constitute a limitation on the computer device to which the solution of the present application is applied. The specific computer device may include more or fewer components than those shown in the figure, or combine certain components, or have a different arrangement of components.

[0117] In one embodiment, a computer device is provided, including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor implements the following steps when executing the computer program: obtaining a payment verification message corresponding to multiple tenants sent by a server, wherein the server generates the payment verification message based on the multiple tenant information, the user behavior information, and the payment type information;

[0118] Parse the payment verification message corresponding to each tenant and obtain the corresponding payment verification task;

[0119] Determine the corresponding operation device type according to each payment verification task;

[0120] The operating device corresponding to the operating device type is called up, and payment verification is performed on the payment verification task through the operating device.

[0121] In one embodiment, when the processor executes the computer program, the processor further implements the following steps:

[0122] Obtain the operating device type in each payment verification task;

[0123] The operation device corresponding to the operation device type is called through the automated testing tool.

[0124] In one embodiment, when the processor executes the computer program, the processor further implements the following steps:

[0125] Open the target application on the operating device;

[0126] Control the target application to perform payment verification on the payment verification task.

[0127] In one embodiment, when the processor executes the computer program, the processor further implements the following steps:

[0128] Obtain the payment verification link and payment verification information of the payment verification task;

[0129] Control the target application to access the payment verification link, call the payment interface, and perform payment verification on the payment verification information.

[0130] In one embodiment, when the processor executes the computer program, the processor further implements the following steps:

[0131] Get device verification results;

[0132] The device verification result is returned to the server, so that the server can provide feedback based on the device verification result.

[0133] In one embodiment, a computer-readable storage medium is provided, on which a computer program is stored, and when the computer program is executed by a processor, the following steps are implemented: obtaining a payment verification message corresponding to multiple tenants sent by a server, wherein the server generates the payment verification message based on the multi-tenant information, the user behavior information, and the payment type information;

[0134] Parse the payment verification message corresponding to each tenant and obtain the corresponding payment verification task;

[0135] Determine the corresponding operation device type according to each payment verification task;

[0136] The operating device corresponding to the operating device type is called up, and payment verification is performed on the payment verification task through the operating device.

[0137] In one embodiment, when the processor executes the computer program, the processor further implements the following steps:

[0138] Obtain the operating device type in each payment verification task;

[0139] The operation device corresponding to the operation device type is called through the automated testing tool.

[0140] In one embodiment, when the processor executes the computer program, the processor further implements the following steps:

[0141] Open the target application on the operating device;

[0142] Control the target application to perform payment verification on the payment verification task.

[0143] In one embodiment, when the processor executes the computer program, the processor further implements the following steps:

[0144] Obtain the payment verification link and payment verification information of the payment verification task;

[0145] Control the target application to access the payment verification link, call the payment interface, and perform payment verification on the payment verification information.

[0146] In one embodiment, when the processor executes the computer program, the processor further implements the following steps:

[0147] Get device verification results;

[0148] The device verification result is returned to the server, so that the server can provide feedback based on the device verification result.

[0149] Those of ordinary skill in the art can understand that all or part of the processes in the above-mentioned embodiment methods can be completed by instructing related hardware through a computer program, and the computer program can be stored in a non-volatile computer-readable storage medium. When the computer program is executed, it can include the processes of the embodiments of the above-mentioned methods. Among them, any reference to memory, storage, database or other media used in the embodiments provided in this application may include non-volatile and / or volatile memory. Non-volatile memory may include read-only memory (ROM), programmable ROM (PROM), electrically programmable ROM (EPROM), electrically erasable programmable ROM (EEPROM) or flash memory. Volatile memory may include random access memory (RAM) or external cache memory. By way of illustration and not limitation, RAM is available in many forms, such as static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rate SDRAM (DDRSDRAM), enhanced SDRAM (ESDRAM), synchronous link DRAM (SLDRAM), RAMbus direct RAM (RDRAM), direct RAMbus dynamic RAM (DRDRAM), and RAMbus dynamic RAM (RDRAM), etc.

[0150] The technical features of the above embodiments may be combined arbitrarily. To make the description concise, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this specification.

[0151] The above-mentioned embodiments only express several implementation methods of the present application, and the descriptions thereof are relatively specific and detailed, but they cannot be understood as limiting the scope of the invention patent. It should be pointed out that, for a person of ordinary skill in the art, several variations and improvements can be made without departing from the concept of the present application, and these all belong to the protection scope of the present application. Therefore, the protection scope of the patent of the present application shall be subject to the attached claims.

Claims

1. A payment verification method, the method comprising: Obtaining a payment verification message corresponding to the multi-tenant sent by the server, wherein the server generates the payment verification message based on the multi-tenant information, the user behavior information and the payment type information; Parsing the payment verification message corresponding to each of the tenants to obtain the corresponding payment verification task; Determining a corresponding operating device type according to each of the payment verification tasks; An operating device corresponding to the operating device type is called up, and payment verification is performed on the payment verification task through the operating device.

2. The method according to claim 1, characterized in that The server generates a payment verification message based on the multi-tenant information, the user behavior information and the payment type information, including: The server obtains user behavior information and determines corresponding product information according to the user behavior information; The server determines corresponding tenant information according to the product information; The server obtains different payment type information under the tenant information; The server assembles the user behavior information, the product information and the tenant information to obtain an order to be paid; The server generates a corresponding payment link according to the order to be paid and the different payment type information; The server generates a payment verification message according to the order to be paid, the payment link and the payment type information.

3. The method according to claim 2, characterized in that The server generates a payment verification message according to the order to be paid, the payment link and the payment type information, including: The server associates a task and a verification plan with the payment link; The server generates a payment verification message according to the order to be paid, the associated payment link and the payment type information.

4. The method according to claim 1, characterized in that The calling up the operating device corresponding to the operating device type includes: Obtaining the type of operating device in each of the payment verification tasks; The operation device corresponding to the operation device type is called by an automated testing tool.

5. The method according to claim 1, characterized in that The performing payment verification on the payment verification task by the operating device includes: Opening a target application in the operating device; The target application is controlled to perform payment verification on the payment verification task.

6. The method according to any one of claim 5, characterized in that: The controlling the target application to perform payment verification on the payment verification task includes: Obtaining a payment verification link and payment verification information for the payment verification task; The target application is controlled to access the payment verification link, call a payment interface, and perform payment verification on the payment verification information.

7. The method according to claim 1, characterized in that After the payment verification is performed on the payment verification task by the operating device, the method includes: Get device verification results; The device verification result is returned to the server, so that the server provides feedback according to the device verification result.

8. A payment verification device, characterized in that: The device comprises: An acquisition module, used to acquire a payment verification message corresponding to the multi-tenant sent by the server, wherein the server generates the payment verification message based on the multi-tenant information, the user behavior information and the payment type information; A parsing module, used to parse the payment verification message corresponding to each of the tenants to obtain a corresponding payment verification task; A determination module, used to determine a corresponding operation device type according to each payment verification task; The verification module is used to call up the operating device corresponding to the operating device type, and perform payment verification on the payment verification task through the operating device.

9. A computer device comprising a memory, a processor and a computer program stored in the memory and executable on the processor, characterized in that: When the processor executes the computer program, the steps of the method according to any one of claims 1 to 7 are implemented.

10. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 7 are implemented.

Images