Multi-tenant designated driver cash withdrawing method and device and computer equipment

Abstract

The invention relates to a multi-tenant designated driver cash withdrawing method and device, computer equipment and a storage medium. The method comprises the following steps: acquiring a cash withdrawal request task record table at regular time; the cash withdrawal request task record table comprises cash withdrawal request tasks of all designated drivers; the withdrawal request task comprises a withdrawal account, a tenant to which the account belongs, a withdrawal mode, an identity authentication mode, a withdrawal amount and an account balance; performing grouping processing on each withdrawal request task according to the tenant list to obtain a withdrawal request task queue of the tenant to which the corresponding account belongs; the tenant list comprises tenants to which all accounts belong; sequentially executing the current to-be-executed cash withdrawal task in the cash withdrawal request task queue of the tenant to which each account belongs; wherein the current to-be-executed cash withdrawal task is the cash withdrawal request task of which the task state is an unexecuted state in the cash withdrawal request task queue corresponding to the current moment. The method can avoid the situation that the designated driver cannot withdraw the cash successfully for a long time.

Description

Technical Field

[0001] This application relates to the technical field of multi-tenant deployment in cloud platforms, and particularly to a method, device, computer device, and storage medium for a multi-tenant driver to withdraw cash for driving services on behalf of others. Background Art

[0002] The driving service on behalf of others has now become the preferred solution for car owners when they are unable or not suitable to drive themselves. For drivers providing driving services on behalf of others, the safe and quick withdrawal of the driving service fees is crucial. In the traditional method for a driver providing driving services on behalf of others to withdraw cash, the driver needs to initiate a cash withdrawal request when the user actively requests it, and after passing the identity verification, the system submits a transfer request to the payment channel platform.

[0003] However, in the traditional method for a driver providing driving services on behalf of others to withdraw cash, there are problems such as the driver being unable to successfully withdraw cash for a long time. Summary of the Invention

[0004] Based on this, in view of the above technical problems, it is necessary to provide a method, device, computer device, and storage medium for a multi-tenant driver to withdraw cash for driving services on behalf of others, which can avoid the situation where the driver is unable to successfully withdraw cash for a long time.

[0005] In a first aspect, a method for a multi-tenant driver to withdraw cash for driving services on behalf of others is provided. The method includes:

[0006] Regularly obtain a cash withdrawal request task record table; the cash withdrawal request task record table includes the cash withdrawal request tasks of each driver providing driving services on behalf of others; the cash withdrawal request task includes a cash withdrawal account, the tenant to which the account belongs, a cash withdrawal method, an identity authentication method, a cash withdrawal amount, and an account balance;

[0007] Group and process each cash withdrawal request task according to the tenant list to obtain a cash withdrawal request task queue for the tenant to which the account belongs; the tenant list includes all the tenants to which the accounts belong;

[0008] Sequentially execute the current cash withdrawal task to be executed in the cash withdrawal request task queue for the tenant to which the account belongs; where the current cash withdrawal task to be executed is the cash withdrawal request task in the cash withdrawal request task queue corresponding to the current moment and with a task status of not executed.

[0009] In one embodiment, a withdrawal request task record table is obtained at regular intervals, including: obtaining withdrawal request data after format verification at regular intervals; performing compliance verification and risk verification on the withdrawal request data after format verification to obtain a compliance risk verification result; wherein, the compliance risk verification result includes passing the verification or failing the verification; in response to the compliance risk verification result being passing the verification, a withdrawal request task is generated according to the withdrawal request data after format verification, and the withdrawal request task is recorded in the request task record table; in response to the compliance risk verification result being failing the verification, a compliance risk verification failure prompt message is output to the user terminal of the driver corresponding to the withdrawal request data after format verification; the compliance risk verification failure prompt message includes the compliance risk verification result and the reason for the compliance risk verification failure of the corresponding withdrawal request data after format verification.

[0010] In one embodiment, obtaining withdrawal request data after format verification at regular intervals includes: obtaining withdrawal request data after completing identity verification at regular intervals; performing format verification on the withdrawal request data after completing identity verification to obtain a format verification result; wherein, the format verification result includes passing the verification or failing the verification; in response to the format verification result being passing the verification, the withdrawal request data after completing identity verification is used as the withdrawal request data after format verification.

[0011] In one embodiment, obtaining withdrawal request data after completing identity verification at regular intervals includes: in response to receiving initial withdrawal request data sent by the user terminal of the driver, determining an identity verification method according to the initial withdrawal request data; wherein, the identity verification method includes SMS verification, video verification, face verification or password verification; controlling the user terminal of the driver to display an identity verification prompt box for the identity verification method; in response to an input operation being performed on the identity verification information in the identity verification prompt box, performing identity verification on the user terminal of the driver according to the identity verification information to obtain an identity verification result; the identity verification result includes successful verification or failed verification; in response to the identity verification result being successful verification, the initial withdrawal request data is used as the withdrawal request data after completing identity verification; in response to the identity verification result being failed verification, an identity verification failure prompt message is output to the user terminal of the driver corresponding to the initial withdrawal request data; wherein, the identity verification failure prompt message includes the identity verification result and the reason for the identity verification failure of the corresponding initial withdrawal request data.

[0012] In one embodiment, successively executing the current pending withdrawal task in the withdrawal request task queue of each tenant to which the account belongs includes: sending the current pending withdrawal task to the withdrawal processing platform of the withdrawal method corresponding to the current pending withdrawal task for withdrawal processing operations, so as to receive the withdrawal processing result sent by the withdrawal processing platform corresponding to the current pending withdrawal task.

[0013] In one embodiment, the method further includes: receiving a withdrawal processing result sent by a withdrawal processing platform corresponding to a currently to-be-executed withdrawal task; the withdrawal processing result includes successful execution or execution exception; in response to the withdrawal processing result corresponding to the currently to-be-executed withdrawal task being successful execution, recording and sending the withdrawal processing result corresponding to the currently to-be-executed withdrawal task to the user terminal of the driver for hire corresponding to the currently to-be-executed withdrawal task; updating the task status of the currently to-be-executed withdrawal task to an executed status, updating the currently to-be-executed withdrawal task according to the withdrawal request task queue corresponding to the currently to-be-executed withdrawal task, and returning to the step of sending each currently to-be-executed withdrawal task to the withdrawal processing platform corresponding to the withdrawal method for the withdrawal processing operation.

[0014] In one embodiment, the method further includes: in response to the withdrawal processing result corresponding to the currently to-be-executed withdrawal task being an execution exception, recording and sending the withdrawal processing result corresponding to the currently to-be-executed withdrawal task to the user terminal of the driver for hire corresponding to the currently to-be-executed withdrawal task.

[0015] In a second aspect, a multi-tenant driver for hire withdrawal device is provided, and the device includes:

[0016] Wherein, a record table acquisition module is configured to periodically acquire a withdrawal request task record table; the withdrawal request task record table includes withdrawal request tasks of each driver for hire; the withdrawal request task includes a withdrawal account, the tenant to which the account belongs, a withdrawal method, an identity authentication method, a withdrawal amount, and an account balance; a task grouping processing module is configured to group and process each withdrawal request task according to a tenant list to obtain a withdrawal request task queue of the tenant to which the corresponding account belongs; the tenant list includes all tenants to which the accounts belong; a task execution module is configured to sequentially execute the currently to-be-executed withdrawal tasks in the withdrawal request task queue of each tenant to which the account belongs; wherein, the currently to-be-executed withdrawal task is a withdrawal request task with an unexecuted status in the withdrawal request task queue corresponding to the current moment.

[0017] In a third aspect, a computer device is provided, and the computer device includes a memory and a processor. The memory stores a computer program, and when the processor executes the computer program, the steps of any one of the methods in the above method embodiments are implemented.

[0018] In a fourth aspect, a computer-readable storage medium is provided, and a computer program is stored on the computer-readable storage medium. When the computer program is executed by a processor, the steps of any one of the methods in the above method embodiments are implemented.

[0019] The above-mentioned multi-tenant driver cash withdrawal method, device, computer equipment and storage medium obtain a cash withdrawal request task record table at regular intervals; the cash withdrawal request task record table includes cash withdrawal request tasks of each driver; the cash withdrawal request task includes a cash withdrawal account, the tenant to which the account belongs, a cash withdrawal method, an identity authentication method, a cash withdrawal amount and an account balance; then, group and process each cash withdrawal request task according to the tenant list to obtain a cash withdrawal request task queue for the corresponding tenant to which the account belongs; the tenant list includes all tenants to which the accounts belong; then, sequentially execute the current pending cash withdrawal task in the cash withdrawal request task queue of each tenant to which the account belongs; where the current pending cash withdrawal task is a cash withdrawal request task with an unexecuted status in the cash withdrawal request task queue corresponding to the current moment, so that it is possible to avoid the server needing to process the cash withdrawal request tasks of a large number of drivers under multiple tenants at one time through the asynchronous grouping execution of the cash withdrawal request task queue, avoid the driver being unable to successfully withdraw cash for a long time, shorten the cash withdrawal response time of the driver, and improve the cash withdrawal success rate, efficiency and stability of the driver. Description of the Drawings

[0020] Figure 1 It is an application environment diagram of the multi-tenant driver cash withdrawal method in an embodiment;

[0021] Figure 2 It is the first process schematic diagram of the multi-tenant driver cash withdrawal method in an embodiment;

[0022] Figure 3 It is the process schematic diagram of regularly obtaining the cash withdrawal request task record table in an embodiment;

[0023] Figure 4 It is the process schematic diagram of regularly obtaining the cash withdrawal request data after format verification in an embodiment;

[0024] Figure 5 It is the process schematic diagram of regularly obtaining the cash withdrawal request data after completing identity verification in an embodiment;

[0025] Figure 6 It is the second process schematic diagram of the multi-tenant driver cash withdrawal method in an embodiment;

[0026] Figure 7 It is the structural block diagram of the multi-tenant driver cash withdrawal device in an embodiment;

[0027] Figure 8 It is the internal structure diagram of the computer equipment in an embodiment. Detailed Embodiments

[0028] In order to make the objectives, technical solutions and advantages of the present application more clear and understandable, the present application will be further described in detail below with reference to 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.

[0029] To facilitate the understanding of the present application, the present application will be described more comprehensively below with reference to the relevant accompanying drawings. Embodiments of the present application are shown in the drawings. However, the present application can be implemented in many different forms and is not limited to the embodiments described herein. On the contrary, the purpose of providing these embodiments is to make the disclosure of the present application more thorough and comprehensive.

[0030] Unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by those of ordinary skill in the technical field to which the present application belongs. The terms used in the specification of the present application herein are only for the purpose of describing specific embodiments and are not intended to limit the present application.

[0031] It can be understood that the terms "first", "second", etc. used in the present application can be used herein to describe various elements, but these elements are not limited by these terms. These terms are only used to distinguish the first element from another element. For example, without departing from the scope of the present application, the first resistor can be called the second resistor, and similarly, the second resistor can be called the first resistor. Both the first resistor and the second resistor are resistors, but they are not the same resistor.

[0032] It can be understood that in the following embodiments, "connection", if there is an electrical signal or data transmission between the connected circuits, modules, units, etc., should be understood as "electrical connection", "communication connection", etc.

[0033] As used herein, the singular forms "a", "an" and "the" may also include the plural forms unless the context clearly dictates otherwise. It should also be understood that the terms "comprising", "including" or "having", etc. specify the presence of the stated features, wholes, steps, operations, components, parts or combinations thereof, but do not preclude the presence or addition of one or more other features, wholes, steps, operations, components, parts or combinations thereof.

[0034] The multi-tenant method for a chauffeur to withdraw cash provided by the present application can be applied to an application environment as Figure 1 shown. Among them, the user terminal 102 of the chauffeur communicates with the server 104 through the network. Among them, the user terminal 102 of the chauffeur can be, but is not limited to, various personal computers, laptop computers, 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.

[0035] In a specific example, the method for a multi-tenant chauffeur to withdraw cash can, but is not limited to, adopt a software operation service platform (Software as a Service, SaaS). The above is only a specific example, and in actual applications, it can be flexibly set according to user needs, and no limitation is imposed here.

[0036] In one embodiment, as Figure 2 shown, a method for a multi-tenant chauffeur to withdraw cash is provided. Taking the server 104 in Figure 1 as an example, the method includes the following steps 201 to 203.

[0037] Step 201, regularly obtain the cash withdrawal request task record form.

[0038] Among them, the cash withdrawal request task record form includes the cash withdrawal request tasks of each chauffeur; the cash withdrawal request task includes the cash withdrawal account, the tenant to which the account belongs, the cash withdrawal method, the identity authentication method, the cash withdrawal amount, and the account balance. Specifically, the server 104 can regularly obtain the cash withdrawal request task record form.

[0039] In one of the embodiments, as Figure 3 shown, regularly obtaining the cash withdrawal request task record form includes steps 301 to 304.

[0040] Step 301, regularly obtain the cash withdrawal request data after format verification;

[0041] Step 302, perform compliance verification and risk verification on the cash withdrawal request data after format verification to obtain a compliance risk verification result;

[0042] Step 303, in response to the compliance risk verification result being passed, generate a cash withdrawal request task according to the cash withdrawal request data after format verification, and record the cash withdrawal request task in the request task record form;

[0043] Step 304, in response to the compliance risk verification result being failed, output a compliance risk verification failure prompt message to the user terminal of the chauffeur corresponding to the cash withdrawal request data after format verification.

[0044] Among them, the compliance risk verification result includes passed or failed; the compliance risk verification failure prompt message includes the compliance risk verification result and the reason for the compliance risk verification failure of the corresponding cash withdrawal request data after format verification.

[0045] Specifically, the server 104 periodically obtains the cash withdrawal request data after format verification; then, performs compliance verification and risk verification on the cash withdrawal request data after format verification to obtain a compliance risk verification result; next, in response to the compliance risk verification result being passed, generates a cash withdrawal request task according to the cash withdrawal request data after format verification, and records the cash withdrawal request task in the request task record table; then, in response to the compliance risk verification result being failed, outputs a compliance risk verification failure prompt message to the user terminal of the driver corresponding to the cash withdrawal request data after format verification, so as to avoid phenomena such as a large cash withdrawal amount, frequent cash withdrawals, and blacklisted accounts in the cash withdrawal request data after format verification, improving the security, orderliness, efficiency, and convenience of cash withdrawals for multi-tenant drivers.

[0046] In this embodiment, periodically obtain the cash withdrawal request data after format verification; then, perform compliance verification and risk verification on the cash withdrawal request data after format verification to obtain a compliance risk verification result; next, in response to the compliance risk verification result being passed, generate a cash withdrawal request task according to the cash withdrawal request data after format verification, and record the cash withdrawal request task in the request task record table; then, in response to the compliance risk verification result being failed, output a compliance risk verification failure prompt message to the user terminal of the driver corresponding to the cash withdrawal request data after format verification, for phenomena such as a large cash withdrawal amount, frequent cash withdrawals, and blacklisted accounts in the cash withdrawal request data after format verification, improving the security, orderliness, efficiency, and convenience of cash withdrawals for multi-tenant drivers.

[0047] In one of the embodiments, as Figure 4 shown, periodically obtaining the cash withdrawal request data after format verification includes steps 401 to 403.

[0048] Step 401, periodically obtain the cash withdrawal request data that has completed real-name authentication;

[0049] Step 402, perform format verification on the cash withdrawal request data that has completed real-name authentication to obtain a format verification result;

[0050] Step 403, in response to the format verification result being passed, use the cash withdrawal request data that has completed real-name authentication as the cash withdrawal request data after format verification.

[0051] Specifically, the format verification result includes verification passed or verification failed; specifically, the server 104 periodically obtains the withdrawal request data that has completed real-name authentication; then, performs format verification on the withdrawal request data that has completed real-name authentication to obtain a format verification result; then, in response to the format verification result being verification passed, uses the withdrawal request data that has completed real-name authentication as the withdrawal request data after format verification, so as to avoid the failure of the withdrawal of the multi-tenant chauffeur due to format anomalies in the withdrawal request data after format verification, and improve the accuracy, efficiency and convenience of the withdrawal of the multi-tenant chauffeur.

[0052] In a specific example, the periodically obtaining the withdrawal request data after format verification further includes:

[0053] In response to the format verification result being verification failed, judge the format correction difficulty according to the withdrawal request data that has completed real-name authentication; the format correction difficulty includes easy or difficult;

[0054] In response to the format verification difficulty being easy, perform format correction on the withdrawal request data that has completed real-name authentication to obtain the withdrawal request data after format verification;

[0055] In response to the format verification difficulty being difficult, output a format verification failure prompt message to the user terminal of the chauffeur corresponding to the withdrawal request data of real-name authentication; the format compliance risk verification failure prompt message includes the format verification result and the reason for format verification failure of the corresponding withdrawal request data of real-name authentication; the above is only a specific example, and it is flexibly set according to user needs in actual applications and is not limited here.

[0056] In this embodiment, periodically obtain the withdrawal request data that has completed real-name authentication; then, perform format verification on the withdrawal request data that has completed real-name authentication to obtain a format verification result; then, in response to the format verification result being verification passed, use the withdrawal request data that has completed real-name authentication as the withdrawal request data after format verification, so as to avoid the failure of the withdrawal of the multi-tenant chauffeur due to format anomalies in the withdrawal request data after format verification, and improve the accuracy, efficiency and convenience of the withdrawal of the multi-tenant chauffeur.

[0057] In one of the embodiments, as Figure 5 shown, periodically obtaining the withdrawal request data that has completed real-name authentication includes steps 501 to 505.

[0058] Step 501, in response to receiving the initial withdrawal request data sent by the user terminal of the chauffeur, determine the identity authentication method according to the initial withdrawal request data;

[0059] Step 502, control the user terminal of the chauffeur to display an identity authentication prompt box for the identity authentication method;

[0060] Step 503: In response to an input operation on the identity authentication information in the identity authentication prompt box, authenticate the user terminal of the driver by proxy according to the identity authentication information to obtain an identity authentication result;

[0061] Step 504: In response to the identity authentication result being successful authentication, use the initial cash withdrawal request data as the cash withdrawal request data after completing real-name authentication;

[0062] Step 505: In response to the identity authentication result being failed authentication, output an identity authentication failure prompt message to the user terminal of the driver by proxy corresponding to the initial cash withdrawal request data.

[0063] Among them, the identity authentication methods include SMS authentication, video authentication, face authentication or password authentication; the identity authentication results include successful authentication or failed authentication; the identity authentication failure prompt message includes the identity authentication result and the reason for identity authentication failure of the corresponding initial cash withdrawal request data.

[0064] Specifically, in response to receiving the initial cash withdrawal request data sent by the user terminal of the driver by proxy, the server 104 determines the identity authentication method according to the initial cash withdrawal request data; then, controls the user terminal of the driver by proxy to display an identity authentication prompt box for the identity authentication method; then, in response to an input operation on the identity authentication information in the identity authentication prompt box, authenticates the user terminal of the driver by proxy according to the identity authentication information to obtain an identity authentication result; then, in response to the identity authentication result being successful authentication, uses the initial cash withdrawal request data as the cash withdrawal request data after completing real-name authentication; finally, in response to the identity authentication result being failed authentication, outputs an identity authentication failure prompt message to the user terminal of the driver by proxy corresponding to the initial cash withdrawal request data, improving the security, accuracy, efficiency and convenience of the cash withdrawal of the drivers by proxy with multiple tenants.

[0065] In a specific example, before determining the identity authentication method according to the initial cash withdrawal request data in response to receiving the initial cash withdrawal request data sent by the user terminal of the driver by proxy, it includes:

[0066] In response to receiving the login information sent by the user terminal of the driver by proxy, perform login verification according to the login information to obtain a login result;

[0067] In response to the login result being successful login, update the login status of the user terminal of the driver by proxy from the non-logged-in status to the logged-in status;

[0068] In response to the login result being failed login, output a login failure prompt message to the user terminal of the driver by proxy. The above is only a specific example, and it is flexibly set according to user needs in actual applications and is not limited here.

[0069] In this embodiment, in response to receiving the initial cash withdrawal request data sent by the user terminal of the designated driver, the identity authentication method is determined according to the initial cash withdrawal request data; then, the user terminal of the designated driver is controlled to display an identity authentication prompt box for the identity authentication method; next, in response to an input operation on the identity authentication information in the identity authentication prompt box, the user terminal of the designated driver is authenticated according to the identity authentication information to obtain an identity authentication result; then, in response to the identity authentication result being successful authentication, the initial cash withdrawal request data is used as the cash withdrawal request data after completing real-name authentication; finally, in response to the identity authentication result being failed authentication, an identity authentication failure prompt message is output to the user terminal of the designated driver corresponding to the initial cash withdrawal request data, improving the security, accuracy, efficiency, and convenience of the cash withdrawal of multi-tenant designated drivers.

[0070] Step 202: Group and process each cash withdrawal request task according to the tenant list to obtain a cash withdrawal request task queue for the tenant to which the corresponding account belongs.

[0071] Among them, the tenant list includes all the tenants to which the accounts belong; a tenant is any service platform. Specifically, the server 104 groups and processes each cash withdrawal request task according to the tenant list to obtain a cash withdrawal request task queue for the tenant to which the corresponding account belongs, so that it is possible to avoid the server needing to process the cash withdrawal request tasks of a large number of designated drivers under multiple tenants at one time through the grouped execution of the cash withdrawal request task queue, and avoid the situation where the designated driver cannot successfully withdraw cash for a long time.

[0072] Step 203: Sequentially execute the current cash withdrawal task to be executed in the cash withdrawal request task queue for the tenant to which each account belongs.

[0073] Among them, the current cash withdrawal task to be executed is the cash withdrawal request task with an unexecuted task status in the cash withdrawal request task queue corresponding to the current moment. Specifically, the server 104 sequentially executes the current cash withdrawal task to be executed in the cash withdrawal request task queue for the tenant to which each account belongs, so that it is possible to avoid the server needing to process the cash withdrawal request tasks of a large number of designated drivers under multiple tenants at one time through the asynchronous grouped execution of the cash withdrawal request task queue, and avoid the situation where the designated driver cannot successfully withdraw cash for a long time, shortening the cash withdrawal response time of the designated driver and improving the cash withdrawal success rate, efficiency, and stability of the designated driver.

[0074] Based on this, the above-mentioned multi-tenant cash withdrawal method for chauffeurs obtains the cash withdrawal request task record table at regular intervals; the cash withdrawal request task record table includes the cash withdrawal request tasks of each chauffeur; the cash withdrawal request task includes the cash withdrawal account, the tenant to which the account belongs, the cash withdrawal method, the identity authentication method, the cash withdrawal amount, and the account balance; then, group and process each cash withdrawal request task according to the tenant list to obtain the cash withdrawal request task queue of the corresponding tenant to which the account belongs; the tenant list includes all tenants to which the accounts belong; then, sequentially execute the current pending cash withdrawal task in the cash withdrawal request task queue of each tenant to which the account belongs; among them, the current pending cash withdrawal task is the cash withdrawal request task with the task status of unexecuted in the cash withdrawal request task queue corresponding to the current moment, so as to avoid the server needing to process the cash withdrawal request tasks of a large number of chauffeurs under multiple tenants at one time, avoid chauffeurs being unable to successfully withdraw cash for a long time, shorten the cash withdrawal response time of chauffeurs, and improve the cash withdrawal success rate, efficiency, and stability of chauffeurs.

[0075] In one embodiment, as Figure 6 shown, sequentially executing the current pending cash withdrawal task in the cash withdrawal request task queue of each tenant to which the account belongs includes step 601.

[0076] Step 601, send the current pending cash withdrawal task to the cash withdrawal processing platform corresponding to the cash withdrawal method of the current pending cash withdrawal task for cash withdrawal processing operations, so as to receive the cash withdrawal processing result sent by the cash withdrawal processing platform corresponding to the current pending cash withdrawal task.

[0077] Specifically, the server 104 sends the current pending cash withdrawal task to the cash withdrawal processing platform corresponding to the cash withdrawal method of the current pending cash withdrawal task for cash withdrawal processing operations, so as to receive the cash withdrawal processing result sent by the cash withdrawal processing platform corresponding to the current pending cash withdrawal task, thus realizing the asynchronous grouped execution of the cash withdrawal request task queue, avoiding the server needing to process the cash withdrawal request tasks of a large number of chauffeurs under multiple tenants at one time, avoiding chauffeurs being unable to successfully withdraw cash for a long time, shortening the cash withdrawal response time of chauffeurs, and improving the cash withdrawal success rate, efficiency, and stability of chauffeurs.

[0078] In this embodiment, sending the current pending cash withdrawal task to the cash withdrawal processing platform corresponding to the cash withdrawal method of the current pending cash withdrawal task for cash withdrawal processing operations, so as to receive the cash withdrawal processing result sent by the cash withdrawal processing platform corresponding to the current pending cash withdrawal task, thus realizing the asynchronous grouped execution of the cash withdrawal request task queue, avoiding the server needing to process the cash withdrawal request tasks of a large number of chauffeurs under multiple tenants at one time, avoiding chauffeurs being unable to successfully withdraw cash for a long time, shortening the cash withdrawal response time of chauffeurs, and improving the cash withdrawal success rate, efficiency, and stability of chauffeurs.

[0079] In one embodiment, as Figure 6 shown, the method further includes steps 602 to 604.

[0080] Step 602, receiving a withdrawal processing result sent by a withdrawal processing platform corresponding to a currently pending withdrawal task;

[0081] Step 603, in response to the withdrawal processing result corresponding to the currently pending withdrawal task being successfully executed, recording and sending the withdrawal processing result corresponding to the currently pending withdrawal task to the user terminal of the driver for hire corresponding to the currently pending withdrawal task;

[0082] Step 604, updating the task status of the currently pending withdrawal task to an executed status, updating the currently pending withdrawal task according to the withdrawal request task queue corresponding to the currently pending withdrawal task, and returning to the step of sending each currently pending withdrawal task to the withdrawal processing platform corresponding to the withdrawal method corresponding to the currently pending withdrawal task for withdrawal processing operations.

[0083] Among them, the withdrawal processing result includes successful execution or execution exception; specifically, the server 104 receives the withdrawal processing result sent by the withdrawal processing platform corresponding to the currently pending withdrawal task; the withdrawal processing result includes successful execution or execution exception; then, in response to the withdrawal processing result corresponding to the currently pending withdrawal task being successfully executed, recording and sending the withdrawal processing result corresponding to the currently pending withdrawal task to the user terminal of the driver for hire corresponding to the currently pending withdrawal task; then, updating the task status of the currently pending withdrawal task to an executed status, updating the currently pending withdrawal task according to the withdrawal request task queue corresponding to the currently pending withdrawal task, and returning to the step of sending each currently pending withdrawal task to the withdrawal processing platform corresponding to the withdrawal method corresponding to the currently pending withdrawal task for withdrawal processing operations, which improves the withdrawal success rate, efficiency and convenience of the driver for hire.

[0084] In this embodiment, receiving the withdrawal processing result sent by the withdrawal processing platform corresponding to the currently pending withdrawal task; the withdrawal processing result includes successful execution or execution exception; then, in response to the withdrawal processing result corresponding to the currently pending withdrawal task being successfully executed, recording and sending the withdrawal processing result corresponding to the currently pending withdrawal task to the user terminal of the driver for hire corresponding to the currently pending withdrawal task; then, updating the task status of the currently pending withdrawal task to an executed status, updating the currently pending withdrawal task according to the withdrawal request task queue corresponding to the currently pending withdrawal task, and returning to the step of sending each currently pending withdrawal task to the withdrawal processing platform corresponding to the withdrawal method corresponding to the currently pending withdrawal task for withdrawal processing operations, which improves the withdrawal success rate, efficiency and convenience of the driver for hire.

[0085] In one embodiment, as Figure 6 shown, the method further includes step 605.

[0086] Step 605, in response to the cash withdrawal processing result corresponding to the currently to-be-executed cash withdrawal task being an execution exception, record and send the cash withdrawal processing result corresponding to the currently to-be-executed cash withdrawal task to the user terminal of the driver for hire corresponding to the currently to-be-executed cash withdrawal task.

[0087] Specifically, the server 104, in response to the cash withdrawal processing result corresponding to the currently to-be-executed cash withdrawal task being an execution exception, records and sends the cash withdrawal processing result corresponding to the currently to-be-executed cash withdrawal task to the user terminal of the driver for hire corresponding to the currently to-be-executed cash withdrawal task, improving the success rate, efficiency, and convenience of the driver for hire to withdraw cash.

[0088] In a specific example, after the step of, in response to the cash withdrawal processing result corresponding to the currently to-be-executed cash withdrawal task being an execution exception, record and send the cash withdrawal processing result corresponding to the currently to-be-executed cash withdrawal task to the user terminal of the driver for hire corresponding to the currently to-be-executed cash withdrawal task, further includes:

[0089] Resend the target currently to-be-executed cash withdrawal task to the cash withdrawal processing platform of the cash withdrawal method corresponding to the target currently to-be-executed cash withdrawal task for a cash withdrawal processing operation, so as to receive the cash withdrawal processing result sent by the cash withdrawal processing platform corresponding to the target currently to-be-executed cash withdrawal task; wherein, the target currently to-be-executed cash withdrawal task is the currently to-be-executed cash withdrawal task with the cash withdrawal processing result being an execution exception.

[0090] Through the above steps, the success rate of the driver for hire to withdraw cash is further improved. The above is only a specific example, and it can be flexibly set according to user needs in actual applications, and is not limited herein.

[0091] In this embodiment, in response to the cash withdrawal processing result corresponding to the currently to-be-executed cash withdrawal task being an execution exception, record and send the cash withdrawal processing result corresponding to the currently to-be-executed cash withdrawal task to the user terminal of the driver for hire corresponding to the currently to-be-executed cash withdrawal task, improving the success rate, efficiency, and convenience of the driver for hire to withdraw cash.

[0092] It should be understood that although Figures 2-6 the steps in the flowchart are shown in sequence according to the arrows, these steps are not necessarily executed in the order indicated by the arrows. Unless there is a clear indication in this article, the execution of these steps has no strict order limit, and these steps can be executed in other orders. Moreover, Figures 2-6At least a part of the steps therein may include multiple sub-steps or multiple stages, and these sub-steps or stages are not necessarily executed and completed at the same moment, but can be executed at different moments, and the execution order of these sub-steps or stages is not necessarily sequential, but can be executed alternately or in turn with at least a part of other steps or sub-steps or stages of other steps.

[0093] In a second aspect, as Figure 7 shown, a multi-tenant cash withdrawal device for driving service drivers is provided, and the device includes a record table acquisition module 710, a task grouping processing module 720, and a task execution module 730.

[0094] Among them, the record table acquisition module 710 is used to regularly acquire a cash withdrawal request task record table; the cash withdrawal request task record table includes cash withdrawal request tasks of each driving service driver; the cash withdrawal request task includes a cash withdrawal account, the tenant to which the account belongs, a cash withdrawal method, an identity authentication method, a cash withdrawal amount, and an account balance; the task grouping processing module 720 is used to group and process each cash withdrawal request task according to the tenant list to obtain a cash withdrawal request task queue of the tenant to which the corresponding account belongs; the tenant list includes all tenants to which the accounts belong; the task execution module 730 is used to sequentially execute the current to-be-executed cash withdrawal task in the cash withdrawal request task queue of each tenant to which the account belongs; among them, the current to-be-executed cash withdrawal task is a cash withdrawal request task in the cash withdrawal request task queue corresponding to the current moment and with a task status of unexecuted.

[0095] In one embodiment, the record table acquisition module 710 includes a record table recording unit.

[0096] Among them, the record table recording unit is used to regularly acquire the cash withdrawal request data after format verification; the record table recording unit is used to perform compliance verification and risk verification on the cash withdrawal request data after format verification to obtain a compliance risk verification result; among them, the compliance risk verification result includes verification passed or verification failed; the record table recording unit is used to, in response to the compliance risk verification result being verification passed, generate a cash withdrawal request task according to the cash withdrawal request data after format verification, and record the cash withdrawal request task in the request task record table; the record table recording unit is used to, in response to the compliance risk verification result being verification failed, output a compliance risk verification failure prompt message to the user terminal of the driving service driver corresponding to the cash withdrawal request data after format verification; the compliance risk verification failure prompt message includes the compliance risk verification result and the reason for the compliance risk verification failure of the corresponding cash withdrawal request data after format verification.

[0097] In one embodiment, the record table recording unit includes a format verification sub-unit.

[0098] Among them, the format verification subunit is used to regularly obtain the withdrawal request data that has completed real-name authentication; the format verification subunit is used to perform format verification on the withdrawal request data that has completed real-name authentication to obtain a format verification result; among them, the format verification result includes verification passed or verification failed; the format verification subunit is used to, in response to the format verification result being verification passed, use the withdrawal request data that has completed real-name authentication as the withdrawal request data after format verification.

[0099] In one embodiment, the format verification subunit includes an identity authenticator.

[0100] Among them, the identity authenticator is used to, in response to receiving the initial withdrawal request data sent by the user terminal of the driver, determine the identity authentication method according to the initial withdrawal request data; among them, the identity authentication method includes SMS authentication, video authentication, face authentication or password authentication; the identity authenticator is used to control the user terminal of the driver to display an identity authentication prompt box for the identity authentication method; the identity authenticator is used to, in response to an input operation on the identity authentication information in the identity authentication prompt box, perform identity authentication on the user terminal of the driver according to the identity authentication information to obtain an identity authentication result; the identity authentication result includes authentication successful or authentication failed; the identity authenticator is used to, in response to the identity authentication result being authentication successful, use the initial withdrawal request data as the withdrawal request data that has completed real-name authentication; the identity authenticator is used to, in response to the identity authentication result being authentication failed, output an identity authentication failure prompt message to the user terminal of the driver corresponding to the initial withdrawal request data; among them, the identity authentication failure prompt message includes the identity authentication result and the reason for identity authentication failure of the corresponding initial withdrawal request data.

[0101] In one embodiment, the task execution module 730 includes a task execution unit.

[0102] Among them, the task execution unit is used to send the current withdrawal task to be executed to the withdrawal processing platform of the withdrawal method corresponding to the current withdrawal task to be executed for withdrawal processing operations, so as to receive the withdrawal processing result sent by the withdrawal processing platform corresponding to the current withdrawal task to be executed.

[0103] In one embodiment, the task execution unit is further used for

[0104] Receive the withdrawal processing result sent by the withdrawal processing platform corresponding to the currently pending withdrawal task; the withdrawal processing result includes successful execution or execution exception; the task execution unit is further configured to record and send the withdrawal processing result corresponding to the currently pending withdrawal task to the user terminal of the driver corresponding to the currently pending withdrawal task in response to the withdrawal processing result corresponding to the currently pending withdrawal task being successful execution; the task execution unit is further configured to update the task status of the currently pending withdrawal task to the executed state, update the currently pending withdrawal task according to the withdrawal request task queue corresponding to the currently pending withdrawal task, and return to the step of sending each currently pending withdrawal task to the withdrawal processing platform corresponding to the withdrawal method corresponding to the currently pending withdrawal task for withdrawal processing operation.

[0105] In one embodiment, the task execution unit is further configured to record and send the withdrawal processing result corresponding to the currently pending withdrawal task to the user terminal of the driver corresponding to the currently pending withdrawal task in response to the withdrawal processing result corresponding to the currently pending withdrawal task being execution exception.

[0106] For the specific limitations of the multi-tenant driver withdrawal device, reference can be made to the limitations of the multi-tenant driver withdrawal method in the above text, which will not be elaborated here. Each module in the above multi-tenant driver withdrawal device can be implemented in whole or in part by software, hardware and their combination. The above modules can be embedded in or independent of the processor in the computer device in the form of hardware, or stored in the memory of the computer device in the form of software, so as to facilitate the processor to call and execute the operations corresponding to the above modules.

[0107] In one embodiment, a computer device is provided. The computer device can be a server, and its internal structure diagram can be as Figure 8 shown. The computer device includes a processor, a memory, a network interface and a database 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, a computer program and a database. The internal memory provides an environment for the operation of the operating system and the computer program in the non-volatile storage medium. The database of the computer device is used to store the withdrawal request task record table. 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, it implements a multi-tenant driver withdrawal method.

[0108] Those skilled in the art can understand that the structure shown in Figure Y is only a block diagram of some structures related to the solution of this application, and does not constitute a limitation on the computer device to which the solution of this application is applied. The specific computer device may include more or fewer components than those shown in the figure, or combine some components, or have a different component layout.

[0109] In a third aspect, a computer device is provided. The computer device includes a memory and a processor. The memory stores a computer program, and when the processor executes the computer program, the steps of any one of the methods in the above method embodiments are implemented.

[0110] In a fourth aspect, a computer-readable storage medium is provided. A computer program is stored on the computer-readable storage medium, and when the computer program is executed by the processor, the steps of any one of the methods in the above method embodiments are implemented.

[0111] Those of ordinary skill in the art can understand that all or part of the processes of implementing the methods in the above embodiments can be completed by instructing relevant hardware through a computer program. The computer program can be stored in a non-volatile computer-readable storage medium. When the computer program is executed, it may include the processes of the embodiments of the above methods. Among them, any reference to a memory, storage, database, or other medium used in the various embodiments provided in this application may include non-volatile and / or volatile memories. 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 (DDR SDRAM), enhanced SDRAM (ESDRAM), synchronous link DRAM (SLDRAM), Rambus direct RAM (RDRAM), direct memory bus dynamic RAM (DRDRAM), and Rambus dynamic RAM (RDRAM), etc.

[0112] The technical features of the above embodiments can be combined arbitrarily. For the sake of brevity of description, 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, it should be considered as the scope recorded in this specification.

[0113] The above-described embodiments merely represent several implementation manners of the present application. The description thereof is relatively specific and detailed, but it should not be construed as a limitation on the scope of the invention patent. It should be noted that for those of ordinary skill in the art, without departing from the concept of the present application, several modifications and improvements can still be made, and these all fall within the protection scope of the present application. Therefore, the protection scope of the patent of the present application shall be subject to the appended claims.

Claims

1. A method for a multi-tenant driver to withdraw cash, the method comprising: Get the withdrawal request task record table regularly; The cash withdrawal request task record table includes the cash withdrawal request tasks of each designated driver; The withdrawal request task includes the withdrawal account, the tenant to which the account belongs, the withdrawal method, the identity authentication method, the withdrawal amount and the account balance; Grouping and processing each of the withdrawal request tasks according to the tenant list to obtain a withdrawal request task queue of the corresponding tenant to which the account belongs; the tenant list includes all tenants to which the account belongs; Execute the current withdrawal tasks to be executed in the withdrawal request task queue of the tenant to which each of the accounts belongs in sequence; wherein the current withdrawal task to be executed is the withdrawal request task whose task status is unexecuted in the withdrawal request task queue corresponding to the current moment.

2. The method according to claim 1, characterized in that The timed acquisition withdrawal request task record table includes: Regularly obtain withdrawal request data after format verification; Performing compliance verification and risk verification on the withdrawal request data after the format verification to obtain a compliance risk verification result; wherein the compliance risk verification result includes verification pass or verification fail; In response to the compliance risk verification result being a passed verification, generating the withdrawal request task according to the withdrawal request data after the format verification, and recording the withdrawal request task in the request task record table; In response to the compliance risk verification result being a verification failure, a compliance risk verification failure prompt message is output to the user terminal of the designated driver corresponding to the withdrawal request data after the format verification; the compliance risk verification failure prompt message includes the compliance risk verification result and the compliance risk verification failure reason of the corresponding withdrawal request data after the format verification.

3. The method according to claim 2, characterized in that The periodically obtaining the withdrawal request data after format verification includes: Regularly obtain withdrawal request data that has completed real-name authentication; Performing format verification on the withdrawal request data that has completed real-name authentication to obtain a format verification result; wherein the format verification result includes verification pass or verification fail; In response to the format verification result being a passed verification, the withdrawal request data that has completed the real-name authentication is used as the withdrawal request data after the format verification.

4. The method according to claim 1, characterized in that: The timed acquisition of withdrawal request data that has completed real-name authentication includes: In response to receiving the initial withdrawal request data sent by the user terminal of the designated driver, determining the identity authentication method according to the initial withdrawal request data; wherein the identity authentication method includes SMS authentication, video authentication, face authentication or password authentication; Controlling the user terminal of the designated driver to display an identity authentication prompt box of the identity authentication method; In response to inputting the identity authentication information in the identity authentication prompt box, performing identity authentication on the user terminal of the designated driver according to the identity authentication information to obtain an identity authentication result; the identity authentication result includes authentication success or authentication failure; In response to the identity authentication result being successful, using the initial withdrawal request data as the withdrawal request data for completing the real-name authentication; In response to the identity authentication result being an authentication failure, an identity authentication failure prompt message is output to the user terminal of the designated driver corresponding to the initial cash withdrawal request data; wherein the identity authentication failure prompt message includes the identity authentication result and the identity authentication failure reason of the corresponding initial cash withdrawal request data.

5. The method according to claim 1, characterized in that: The sequentially executing the current withdrawal tasks to be executed in the withdrawal request task queue of the tenants to which each of the accounts belongs includes: The current withdrawal task to be executed is sent to the withdrawal processing platform of the withdrawal method corresponding to the current withdrawal task to be executed for withdrawal processing operation, so as to receive the withdrawal processing result sent by the withdrawal processing platform corresponding to the current withdrawal task to be executed.

6. The method according to claim 5, characterized in that The method further comprises: Receiving the withdrawal processing result sent by the withdrawal processing platform corresponding to the current withdrawal task to be executed; the withdrawal processing result includes successful execution or abnormal execution; In response to the cash withdrawal processing result corresponding to the current cash withdrawal task to be executed being successfully executed, recording and sending the cash withdrawal processing result corresponding to the current cash withdrawal task to the user terminal of the designated driver corresponding to the current cash withdrawal task to be executed; Update the task status of the current withdrawal task to be executed to an executed status, update the current withdrawal task to be executed according to the withdrawal request task queue corresponding to the current withdrawal task to be executed, and return to the step of sending each current withdrawal task to be executed to the withdrawal processing platform of the withdrawal method corresponding to the current withdrawal task to be executed for withdrawal processing operations.

7. The method according to claim 6, characterized in that The method further comprises: In response to the withdrawal processing result corresponding to the current withdrawal task to be executed being an execution exception, the withdrawal processing result corresponding to the current withdrawal task to be executed is recorded and sent to the user terminal of the designated driver corresponding to the current withdrawal task to be executed.

8. A multi-tenant driver cash withdrawal device, characterized in that: The device comprises: A record table acquisition module is used to periodically acquire a withdrawal request task record table; the withdrawal request task record table includes the withdrawal request tasks of each designated driver; the withdrawal request task includes the withdrawal account, the tenant to which the account belongs, the withdrawal method, the identity authentication method, the withdrawal amount and the account balance; A task grouping processing module, used for grouping and processing each of the withdrawal request tasks according to a tenant list, and obtaining a withdrawal request task queue of the tenant to which the corresponding account belongs; the tenant list includes all tenants to which the account belongs; The task execution module is used to execute the current withdrawal tasks to be executed in the withdrawal request task queue of the tenant to which each account belongs in sequence; wherein the current withdrawal task to be executed is the withdrawal request task whose task status is unexecuted in the withdrawal request task queue corresponding to the current moment.

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