A project processing method and device, a computing device and a storage medium
By receiving user requests and conducting access audits, and establishing an account binding relationship, the problem that mutual insurance products cannot effectively protect the rights and interests of participants is solved, and the postpayment and credit review mechanism is realized, which improves users' enthusiasm for participation and protection experience.
Patent Information
- Application Number
- CN202110022403.6
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2018-11-28
- Publication Date
- 2024-11-01
- Estimated Expiration
- 2038-11-28
AI Technical Summary
Existing mutual insurance products cannot effectively protect the personal rights and interests of those participating in mutual assistance, especially lacking a rigid redemption mechanism when paying compensation.
By receiving user's request for participation in project, obtaining their health information and credit information based on the user's identification information for admission review, and establishing an account binding relationship for the user when the review is passed, allowing users to participate in the project, using postpayment and credit The audit mechanism ensures that users share expenses according to actual circumstances after accidents occur.
It improves users' enthusiasm for participating in projects and guarantees the protection of their experience, ensures that users' interests are not subject to unlimited losses, and at the same time, through health notification and credit review mechanisms, the transparency and fairness of insurance products are improved.
Smart Images

Figure CN112598402B_ABST
Abstract
Description
[0001] This application is a divisional application with application number 201811448955.8, application date November 28, 2018, and invention name “A project processing method and apparatus, a computing device and storage medium”. Technical Field
[0002] The present application relates to the field of insurance technology, and in particular to a project processing method and apparatus, a computing device and a storage medium. Background Art
[0003] At present, general commercial health insurance is priced according to the incidence of diseases, and users are required to pay a fixed premium in advance. When making claims, the amount of compensation is also determined based on the amount of premium paid. However, the existing mutual aid products are not insurance and do not promise rigid redemption. When a mutual aid participant applies for compensation, the personal rights and interests of the participants cannot be well protected. Summary of the invention
[0004] In view of this, the embodiments of this specification provide a project processing method and apparatus, a computing device and a storage medium to solve the technical defects existing in the prior art.
[0005] In a first aspect, the embodiments of this specification disclose a project processing method, including:
[0006] Receive a project participation request from a user, wherein the project participation request carries user identification information;
[0007] Acquire first user information and second user information of the user based on the user identification information;
[0008] Performing access review on the user based on the first user information and the second user information of the user and providing a review result, wherein the review result includes whether the user is allowed to participate in the project;
[0009] When the audit result allows the user to participate in the project, a binding relationship is established between the user identification information and the account corresponding to the user.
[0010] In a second aspect, the present specification discloses a project processing device, including:
[0011] A first receiving module is configured to receive a user's project participation request, wherein the project participation request carries user identification information;
[0012] A first acquisition module is configured to acquire first user information and second user information of a user based on the user identification information;
[0013] A first review module is configured to perform access review on the user based on the first user information and the second user information of the user and provide a review result, wherein the review result includes whether the user is allowed to participate in the project;
[0014] The first binding module is configured to establish a binding relationship between the user identification information and the account corresponding to the user when the audit result is to allow the user to participate in the project.
[0015] In a third aspect, an embodiment of the present specification discloses a computing device, including a memory, a processor, and computer instructions stored in the memory and executable on the processor, wherein when the processor executes the instructions, the steps of the project processing method described above are implemented when the instructions are executed by the processor.
[0016] In a fourth aspect, an embodiment of the present specification discloses a computer-readable storage medium storing computer instructions, which, when executed by a processor, implement the steps of the project processing method as described above.
[0017] The present specification provides a project processing method and apparatus, a computing device and a storage medium, wherein the method includes receiving a user's request to participate in a project, wherein the request to participate in the project carries user identification information; obtaining the user's first user information and second user information based on the user identification information; performing an access review on the user based on the user's first user information and second user information and providing a review result, wherein the review result includes whether the user is allowed to participate in the project; and when the review result is that the user is allowed to participate in the project, establishing a binding relationship between the user identification information and the user's corresponding account. BRIEF DESCRIPTION OF THE DRAWINGS
[0018] Figure 1 is a schematic diagram of a computing device provided in an embodiment of this specification;
[0019] Figure 2 is a flow chart of a project processing method provided in an embodiment of this specification;
[0020] Figure 3 This is a flowchart of a project processing method provided in an embodiment of this specification.
[0021] Figure 4 is a flow chart of a project processing method provided in an embodiment of this specification;
[0022] Figure 5 is a flow chart of a project processing method provided in an embodiment of this specification;
[0023] Figure 6 is a flow chart of a project processing method provided in an embodiment of this specification;
[0024] Figure 7 is a flow chart of a project processing method provided in an embodiment of this specification;
[0025] Figure 8 It is a structural diagram of a project processing device provided in an embodiment of this specification. DETAILED DESCRIPTION
[0026] Many specific details are described in the following description to facilitate a full understanding of the present application. However, the present application can be implemented in many other ways than those described herein, and those skilled in the art can make similar generalizations without violating the connotation of the present application, so the present application is not limited by the specific implementation disclosed below.
[0027] The terms used in one or more embodiments of this specification are only for the purpose of describing specific embodiments, and are not intended to limit one or more embodiments of this specification. The singular forms of "a", "said" and "the" used in one or more embodiments of this specification and the appended claims are also intended to include plural forms, unless the context clearly indicates other meanings. It should also be understood that the term "and / or" used in one or more embodiments of this specification refers to and includes any or all possible combinations of one or more associated listed items.
[0028] It should be understood that although the terms first, second, etc. may be used to describe various information in one or more embodiments of this specification, this information should not be limited to these terms. These terms are only used to distinguish the same type of information from each other. For example, without departing from the scope of one or more embodiments of this specification, the first may also be referred to as the second, and similarly, the second may also be referred to as the first. Depending on the context, the word "if" as used herein may be interpreted as "at the time of" or "when" or "in response to determining".
[0029] First, the terms involved in one or more embodiments of the present invention are explained.
[0030] Post-payment: refers to users who meet the conditions do not need to pay the insurance fee when joining, and can enjoy the insurance first. When there is a member who has an accident and claims, the premium will be evenly distributed to all members according to the actual situation of the claim. Different from general commercial health insurance, the price is based on the incidence of the disease, and users pay a fixed premium in advance.
[0031] Credit review: refers to the assessment of application conditions of users who apply to join. Only those who meet the conditions can join, and the platform is combined with the credit of the platform to develop for honest users.
[0032] Health declaration: refers to the confirmation of the insured's health status required by the insurance company when accepting the user's insurance application. Once the insurance company underwrites the insurance, the health declaration will become an integral part of the insurance contract.
[0033] In the present application, a project processing method and apparatus, a computing device and a storage medium are provided, which are described in detail one by one in the following embodiments.
[0034] Figure 1 1 is a block diagram showing a structure of a computing device 100 according to an embodiment of the present specification. The components of the computing device 100 include but are not limited to a memory 110 and a processor 120. The processor 120 is connected to the memory 110 via a bus 130, and a database 150 is used to store data.
[0035] The computing device 100 also includes an access device 140 that enables the computing device 100 to communicate via one or more networks 160. Examples of these networks include a public switched telephone network (PSTN), a local area network (LAN), a wide area network (WAN), a personal area network (PAN), or a combination of communication networks such as the Internet. The access device 140 may include one or more of any type of network interface (e.g., a network interface card (NIC)) whether wired or wireless, such as an IEEE 802.11 wireless local area network (WLAN) wireless interface, a World Wide Interoperability for Microwave Access (Wi-MAX) interface, an Ethernet interface, a universal serial bus (USB) interface, a cellular network interface, a Bluetooth interface, a near field communication (NFC) interface, and the like.
[0036] In one embodiment of the present specification, the above and Figure 1 Other components not shown in the figure may also be connected to each other, for example, via a bus. It should be understood that Figure 1 The computing device structure block diagram shown is only for the purpose of illustration, and is not intended to limit the scope of this specification. Those skilled in the art can add or replace other components as needed.
[0037] The computing device 100 may be any type of stationary or mobile computing device, including a mobile computer or mobile computing device (e.g., a tablet computer, a personal digital assistant, a laptop computer, a notebook computer, a netbook, etc.), a mobile phone (e.g., a smart phone), a wearable computing device (e.g., a smart watch, smart glasses, etc.), or other types of mobile devices, or a stationary computing device such as a desktop computer or PC. The computing device 100 may also be a mobile or stationary server.
[0038] The processor 120 may execute Figure 2 Steps in the method shown. Figure 2A project processing method provided by one or more embodiments of this specification is shown, including steps 202 to 208.
[0039] Step 202: Receive a project participation request from a user, wherein the project participation request carries user identification information.
[0040] In one or more embodiments of the present specification, the user identification information includes but is not limited to a unique project participation identification number generated for a certain user during the user's participation in the project, such as a user identification number composed of the user's name, ID number, insurance date and insurance serial number.
[0041] Step 204: Acquire the first user information and the second user information of the user based on the user identification information.
[0042] The first user information includes but is not limited to the user's health information, and the second user information includes but is not limited to the user's credit information.
[0043] In one or more embodiments of this specification, obtaining the first user information of the user includes:
[0044] Acquire first user information determined by the user based on a preset first user information report; or
[0045] The first user information of the user is obtained based on a preset first user information obtaining model.
[0046] The obtaining of the second user information of the user comprises:
[0047] The second user information of the user is obtained based on a preset credit evaluation model.
[0048] The first user information report includes but is not limited to a preset health measurement report, and the first user information acquisition model includes but is not limited to a preset health model.
[0049] Step 206: Based on the first user information and the second user information of the user, an access audit is performed on the user and an audit result is given. The audit result includes whether the user is allowed to participate in the project.
[0050] In one or more embodiments of the present specification, an access review is performed on the user based on the first user information and the second user information of the user and an review result is given, that is, whether the user meets the access review is determined based on the user's health information and credit information, and an review result is given.
[0051] Step 208: When the audit result is to allow the user to participate in the project, a binding relationship is established between the user identification information and the account corresponding to the user.
[0052] In one or more embodiments of the present specification, the audit result is to allow the user to participate in the project, that is, when the user's health information is healthy and the credit information is up to standard, it is determined that the user meets the access review and the user is allowed to participate in the project.
[0053] A binding relationship is established between the user identification information and the account corresponding to the user, that is, a binding relationship is established between the user identification information and the bank account corresponding to the user or the system deductible account.
[0054] In one or more embodiments of this specification, the following may also be included:
[0055] If the audit result indicates that the user is not allowed to participate in the project, a user blacklist will be established;
[0056] When the second user information of the user in the user blacklist satisfies the access review, obtaining the first user information of the user in the user blacklist according to a preset time interval;
[0057] In the case that the first user information of the user meets the access review, the user is allowed to participate in the project.
[0058] That is, in order to increase the enthusiasm of users to participate in the project, if the audit result is that the user is not allowed to participate in the project, a user blacklist will be established for users who have not passed the project participation audit, and then users whose credit information meets the standards and whose health information is sub-healthy will be selected from the user blacklist. The health information of these users will then be updated at regular intervals. When the health information of these users is healthy, these users will be allowed to participate in the project.
[0059] In another case, when the audit result is that the user is not allowed to participate in the project, after the user blacklist is established, it also includes:
[0060] If the first user information of the user in the user blacklist meets the preset requirement and the user pays a designated fee, the user is allowed to participate in the project.
[0061] That is, the user blacklist selects users whose health information is healthy but whose credit information does not meet the standards, and then allows these users to participate in the project if they agree to pay a specified fee, i.e., a deposit or pre-deposit fee. For example, if a user's health information is healthy but his credit information does not meet the standards, then if the user agrees to pre-deposit the fee, the user can be allowed to participate in the project.
[0062] In one or more embodiments of this specification, the project participation request carries the user's associated person information.
[0063] When the audit result is to allow the user to participate in the project, the method further includes:
[0064] Receive project participation requests from the user's designated associates.
[0065] The associated persons include but are not limited to the user's minor children, etc. If the audit result is to run the user participation project, the user can be allowed to add the minor children to participate in the project.
[0066] In one or more embodiments of the present specification, the project processing method enables user participation in the project through an audit model based on the user's first user information and second user information. This free way of participating in the project greatly improves the user's project participation experience, and enables the user's associated persons to participate in the project based on the user's basic data, thereby ensuring the sustainable development of the project.
[0067] See also Figure 3 One or more embodiments of the present specification provide a project processing method, including steps 302 to 316.
[0068] Step 302: Receive a project participation request from a user, wherein the project participation request carries user identification information.
[0069] Step 304: Acquire the first user information and the second user information of the user based on the user identification information.
[0070] Step 306: Based on the first user information and the second user information of the user, an access audit is performed on the user and an audit result is given. The audit result includes whether the user is allowed to participate in the project.
[0071] Step 308: When the audit result is to allow the user to participate in the project, a binding relationship is established between the user identification information and the account corresponding to the user.
[0072] In one or more embodiments of this specification, the specific implementation of steps 302 to 308 can refer to the above embodiments and will not be repeated here.
[0073] Step 310: Receive a mutual aid fund application request for a mutual aid fund case to be applied for, wherein the mutual aid fund application request carries the content of the mutual aid fund case to be applied for.
[0074] In one or more embodiments of the present specification, the content of the mutual aid fund case to be applied for includes but is not limited to the event and location of the case, and the specific detailed process of the case.
[0075] Step 312: When it is determined that the mutual aid fund case to be applied for needs to be applied for according to the content of the mutual aid fund case to be applied for, the share amount for each user currently participating in the project is determined according to the current number of people participating in the project and the mutual aid amount to be applied for in the mutual aid fund case to be applied for.
[0076] Step 314: If the shared amount does not exceed the preset sharing threshold, deduct money from the account corresponding to each user currently participating in the project.
[0077] In one or more embodiments of this specification, the preset apportionment threshold can be set according to actual conditions, and this application does not limit this. For example, the preset apportionment threshold can be 2 yuan, 5 yuan or 10 yuan.
[0078] For example, when the shared amount does not exceed the preset shared threshold, the shared amount for each current project user is determined to be 10 yuan based on the current number of users participating in the project and the total amount of mutual aid funds applied for in the mutual aid fund cases to be applied for.
[0079] In one or more embodiments of this specification, deducting money from the account corresponding to each current project participating user includes:
[0080] During the preset deduction period, deductions are made from the corresponding account of each user currently participating in the project until the deduction is successful or the deduction period ends.
[0081] The account corresponding to each user currently participating in the project includes a custom account and a non-custom account.
[0082] The custom account may be a designated bank account. For example, when it is necessary to deduct money from the account corresponding to each current project user, the money may be deducted from the designated bank account of the user. The non-custom account may be a random account. For example, when it is necessary to deduct money from the account corresponding to each current project user, the money may be deducted from the user's platform account first. If the deduction fails, the money may be deducted from other bound bank accounts of the user in sequence.
[0083] Step 316: When the shared amount exceeds the preset shared threshold, the shared amount equal to the preset shared threshold is deducted from the account corresponding to each user currently participating in the project, and the shared amount exceeding the preset shared threshold is deducted from the second account associated with the project.
[0084] Among them, the second account is an account associated with the project, that is, when the apportioned amount exceeds the preset apportionment threshold, after deducting the apportioned amount equal to the preset apportionment threshold from the account corresponding to each user currently participating in the project, the remaining apportioned amount is deducted from the second account associated with the project, that is, the remaining apportioned amount is borne by the project.
[0085] In one or more embodiments of the present specification, taking the preset apportionment threshold of 10 yuan as an example, when the apportionment amount exceeds the preset apportionment threshold, an apportionment amount equal to the preset apportionment threshold is deducted from the account corresponding to each user currently participating in the project, and the apportionment amount exceeding the preset apportionment threshold is deducted from the second account associated with the project.
[0086] If the apportioned amount is 20 yuan, and it is determined that the apportioned amount of 20 yuan exceeds the preset apportionment threshold of 10 yuan, an apportioned amount of 10 yuan, which is the same as the preset apportionment threshold, will be deducted from the account corresponding to each user currently participating in the project, and then the apportioned amount of each user currently participating in the project that exceeds the preset apportionment threshold will be deducted from the second account associated with the project, that is, 10 yuan for each user currently participating in the project.
[0087] In one or more embodiments of the present specification, deducting an apportionment amount equal to a preset apportionment threshold from an account corresponding to each user currently participating in the project includes:
[0088] During the preset deduction period, the apportionment amount equal to the preset apportionment threshold is deducted from the corresponding account of each current project user in a round-robin manner until the deduction is successful or the deduction period ends.
[0089] In actual use, when it is determined that the mutual aid fund case to be applied for needs to be applied for according to the content of the mutual aid fund case to be applied for, a deduction notice is issued to each user currently participating in the project.
[0090] See also Figure 4 In one or more embodiments of this specification, taking the project processing method applied to the M project platform as an example, the deduction of money from the account corresponding to each user currently participating in the project is described in detail.
[0091] There are two situations for deductions from the account corresponding to each user currently participating in the project. One is that no custom deduction channel is set, and the other is that an automatic deduction channel has been set.
[0092] Taking the case where no custom deduction channel is set as an example, the description includes steps 402 to 404.
[0093] Step 402: If the project balance, Y channel and H channel have been opened, deductions will be made from the balance, Y channel or H channel from 00:00:00 to 8:00:00 on the first day; if the deduction fails, deductions will continue from the balance, Y channel or H channel from 8:00:00 to 22:00:00 on the first day; if the deduction still fails, deductions will continue from the balance, Y channel or H channel from 00:00:00 to 8:00:00 on the second day; if the deduction still fails, deductions will continue from the balance, Y channel or H channel from 8:00:00 to 22:00:00 on the second day.
[0094] The above Y channel and H channel are both relevant internal channels corresponding to the M project platform. That is, if there is an internal channel corresponding to the M project platform, deductions will be made through the internal channel first.
[0095] If the deduction is successful, you can end the deduction process at any time. If the deduction is unsuccessful, you need to continue with the subsequent deduction process.
[0096] Step 404: If the balance, Y channel and H channel are not activated, deductions are made from the designated bank account from 8:00:00 to 22:00:00 on the first day; if the deduction fails, deductions are continued from the designated bank account from 8:00:00 to 22:00:00 on the second day.
[0097] Taking the set custom deduction channel as an example, the description includes steps 406 to 408.
[0098] Step 406: If the first deduction channel set in the custom setting is balance, Y channel and H channel, deduction will be made from the balance, Y channel or H channel from 00:00:00 to 8:00:00 on the first day; if the deduction fails, deduction will continue from the balance, Y channel or H channel from 8:00:00 to 22:00:00 on the first day; if the deduction still fails, deduction will continue from the balance, Y channel or H channel from 00:00:00 to 8:00:00 on the second day; if the deduction still fails, deduction will continue from the balance, Y channel or H channel from 8:00:00 to 22:00:00 on the second day.
[0099] Step 408: If the first deduction channel set in the custom setting is not the balance, Y channel, or H channel, but a bank account, deductions will be made from the designated bank account from 8:00:00 to 22:00:00 on the first day; if the deduction fails, deductions will continue from the designated bank account from 8:00:00 to 22:00:00 on the second day.
[0100] In one or more embodiments of the present specification, the above-mentioned withholding payment method can be combined with project-related accounts, bank account numbers, etc. to formulate the above-mentioned intelligent withholding initiation mechanism, which greatly improves the success rate of withholding.
[0101] In one or more embodiments of the present specification, the project processing method adopts a method in which the apportionment amount does not exceed the preset apportionment threshold, so that in each case of mutual aid funds to be applied for, the apportionment amount of each current project user does not exceed the preset apportionment threshold, so that each project participant can obtain project protection and ensure that his or her interests will not suffer unlimited losses.
[0102] See also Figure 5 Taking the project as a mutual aid project, the project participation request as a mutual aid project participation request, the first user information as health information, and the second user information as credit information as an example, a project processing method provided by one or more embodiments of this specification is described in detail, including steps 502 to 516.
[0103] Step 502: Receive a user's request for participating in a mutual aid project, wherein the request for participating in a mutual aid project carries user identification information.
[0104] Step 504: Acquire the user's health information and credit information based on the user identification information.
[0105] In one or more embodiments of the present specification, obtaining the user's health information includes but is not limited to: obtaining the user's health information determined based on a preset health report; or obtaining the user's health information based on a preset health model.
[0106] For example, a health calculation report is pre-set. After receiving a user's insurance request, the user's health information is calculated based on the health calculation report filled out by the user, and a health notice is generated. The health notice is easy for users to understand, and deconstructs the health notice content based on diseases, symptoms and common medical definitions, so that users can inform according to their own health conditions. The health information may include but is not limited to the user's health score or a result that can directly determine whether the user is healthy, sub-healthy or unhealthy, among which the health calculation report includes but is not limited to test questions such as height, weight, family medical history and personal medical history.
[0107] In addition, for users who are uncertain about their health issues, their health information can be obtained based on a preset health model. That is, after receiving a user's insurance request, the user's health information will be obtained based on an intelligent health question test. For example, the user's height, weight, and personal medical history will be asked first. If there is no personal medical history, the family medical history will be asked. If there is a personal medical history, a detailed test will be conducted on the personal medical history. Through this intelligent robot mode, the user's health information is obtained, which ensures the accuracy of health information acquisition and greatly improves the efficiency of health information acquisition. Regardless of the method used to obtain health information, the process data backtracking and result data recording of health notification can be provided, which can provide necessary data support for the subsequent determination of the mutual aid fund application for the mutual aid fund case to be applied for, and reduce disputes.
[0108] In one or more embodiments of the present specification, obtaining the credit information of a user includes but is not limited to: obtaining the credit information of a user based on a preset credit evaluation model.
[0109] In actual use, by combining the credit scores of the mutual aid platform, the risk control data of the insurance platform, the insurance company's industry fraud risk control data, and third-party authorization data, etc., through artificial intelligence model analysis, user profiles can be created, and a credit evaluation model for user access review can be gradually formed, and then the credit evaluation model can be used to judge the user's credit information.
[0110] For example, if a user has a credit score of 650 on the mutual aid platform and belongs to the overdue debt user group, the business blacklist user, the factual blacklist user, i.e. the mutual insurance claims user group, the insurance industry blacklist user group, and the behavioral blacklist user, then by obtaining the user's credit information through the preset credit evaluation model, it can be determined that the user's credit information does not meet the standards for access review, that is, the obtained user's credit information is not up to standard; otherwise, the obtained user's credit information meets the standard.
[0111] Step 506: Based on the health information and credit information of the user, the user is audited for access and an audit result is given, wherein the audit result includes whether the user is allowed to participate in mutual insurance.
[0112] Step 508: When the audit result allows the user to participate in mutual insurance, a binding relationship is established between the user identification information and the user's corresponding account.
[0113] Step 510: Receive a mutual aid fund application request for a mutual aid fund case to be applied for, wherein the mutual aid fund application request carries the content of the mutual aid fund case to be applied for.
[0114] Step 512: When it is determined that the mutual aid fund case to be applied for needs to be applied for mutual aid funds based on the content of the mutual aid fund case to be applied for, the share amount of each current mutual aid insured user is determined based on the current number of mutual aid insured persons and the mutual aid application amount of the mutual aid fund case to be applied for.
[0115] Step 514: When the shared amount does not exceed the preset sharing threshold, deduct money from the account corresponding to each current mutual aid insurance user.
[0116] Step 516: When the shared amount exceeds the preset shared threshold, a shared amount equal to the preset shared threshold is deducted from the account corresponding to each current insured user participating in the mutual aid project, and the shared amount exceeding the preset shared threshold is deducted from the second account associated with the mutual aid project.
[0117] It should be noted that the technical solution of the mutual aid project processing method and the technical solution of the above-mentioned project processing method belong to the same concept. For details not described in detail in the technical solution of the mutual aid project processing method, please refer to the description of the technical solution of the above-mentioned project processing method.
[0118] In one or more embodiments of the present specification, the project processing method is applied in a mutual aid project, so that mutual aid insured users can enjoy protection first and then participate in the sharing, and the sharing amount is calculated according to the actual loss and the situation where there is no objection through the claim disclosure, and the cost is shared according to the actual application case of mutual aid funds. Unlike general commercial health insurance, it is priced according to the incidence of the disease, and users are required to pay a fixed premium in advance. The sharing amount does not exceed the preset sharing threshold, so that for each mutual aid fund case to be applied for, the sharing amount of each current mutual aid insured user does not exceed the preset sharing threshold, so that each mutual aid insured person can ensure that his or her interests will not suffer unlimited losses when obtaining insurance protection.
[0119] See also Figure 6 , taking the project as an insurance project, the project participation request as an insurance participation request, the first user information as health information, the second user information as credit information, the mutual aid fund case to be applied for as a claim case, and the mutual aid fund application request as a claim request as an example, a project processing method provided in one or more embodiments of this specification is described in detail, including steps 602 to 616.
[0120] Step 602: Receive the user's insurance participation request, which carries user identification information.
[0121] Step 604: Obtain the user's health information and credit information based on the user identification information.
[0122] Step 606: Based on the health information and credit information of the user, the user is audited for access and an audit result is given, wherein the audit result includes whether the user is allowed to participate in insurance.
[0123] Step 608: When the audit result allows the user to participate in the insurance, a binding relationship is established between the user identification information and the user's corresponding account.
[0124] Step 610: Receive a claim request for a pending claim case, wherein the claim request carries the content of the pending claim case.
[0125] In one or more embodiments of this specification, claims settlement is a concrete manifestation of the insurance company's execution of the insurance contract, fulfillment of insurance obligations, and assumption of insurance liability. Specifically, it refers to the insurer's handling of claims filed by the insured after the insurance accident occurs. After the insured suffers a disaster, he or she should immediately file a claim application with the insurer or through a claims settlement agent, review the submitted documents according to the provisions of the insurance policy, find out whether the cause of the loss is within the scope of insurance, estimate the extent of the loss, determine the amount of compensation, and finally pay and close the case.
[0126] In actual use, the contents of the pending claims include but are not limited to major illness claims, hospitalization claims, etc.
[0127] Step 612: When it is determined that the pending claim case requires a claim based on its content, the share amount for each current insured user is determined based on the current number of insured persons and the claim amount of the pending claim case.
[0128] Step 614: When the shared amount does not exceed the preset sharing threshold, deduct money from the account corresponding to each current insured user.
[0129] In one or more embodiments of this specification, the preset apportionment threshold can be set according to actual conditions, and this is not limited in the present application. For example, the preset apportionment threshold can be 0.1 yuan.
[0130] For example, when it is determined that the pending claim case requires a claim based on its content, the apportionment amount for each current insured user is determined to be 0.05 yuan based on the current number of insured persons and the claim amount of the pending claim case.
[0131] At this time, if the apportionment amount of 0.05 yuan does not exceed the preset apportionment threshold of 0.1 yuan, 0.1 yuan will be deducted from the account corresponding to each current insured user.
[0132] In one or more embodiments of the present specification, the account corresponding to each currently insured user includes a custom account and a non-custom account.
[0133] The custom account may be a designated bank account. For example, when it is necessary to deduct money from the account corresponding to each current insured user, the money may be deducted from the designated bank account of the user. The non-customized account may be a random account. For example, when it is necessary to deduct money from the account corresponding to each current insured user, the money may be deducted from the user's platform account first. If the deduction fails, the money may be deducted from other bound bank accounts of the user in sequence.
[0134] In actual use, when it is determined that the pending claim case needs to be paid according to the content of the pending claim case, a deduction notice may be issued to each current insured user, wherein the deduction notice may be a system prompt or a text message notification.
[0135] Step 616: When the shared amount exceeds the preset shared threshold, a shared amount equal to the preset shared threshold is deducted from the account corresponding to each currently insured user, and the shared amount exceeding the preset shared threshold is deducted from the second account associated with the insurance item.
[0136] In one or more embodiments of the present specification, taking the preset apportionment threshold of 0.1 yuan as an example, a detailed description is given of deducting an apportionment amount equal to the preset apportionment threshold from the account corresponding to each current insured user when the apportionment amount exceeds the preset apportionment threshold, and deducting the apportionment amount in excess of the preset apportionment threshold from the second account associated with the insurance project.
[0137] If the shared amount is 0.2 yuan, and it is determined that the shared amount of 0.2 yuan exceeds the preset shared threshold of 0.1 yuan, a shared amount of 0.1 yuan equal to the preset shared threshold will be deducted from the account corresponding to each current insured user, and then the shared amount of each current insured user that exceeds the preset shared threshold will be deducted from the second account associated with the insurance project, that is, 0.1 yuan for each current insured user.
[0138] In one or more embodiments of this specification, deducting money from the account corresponding to each current insured user includes:
[0139] During the preset deduction period, deductions are made from the account corresponding to each current insured user until the deduction is successful or the deduction period ends;
[0140] The amount of the apportionment equal to the preset apportionment threshold is deducted from the account corresponding to each current insured user, including:
[0141] During the preset deduction period, the apportionment amount equal to the preset apportionment threshold is deducted from the account corresponding to each current insured user in a round-robin manner until the deduction is successful or the deduction period ends.
[0142] It should be noted that the technical solution of the insurance project processing method and the technical solution of the above-mentioned project processing method belong to the same concept. For details not described in detail in the technical solution of the insurance project processing method, please refer to the description of the technical solution of the above-mentioned project processing method.
[0143] In one or more embodiments of the present specification, the project processing method allows the insured users to enjoy the protection first and then participate in the sharing, and the sharing amount is calculated according to the actual loss and the situation where there is no objection through the claim disclosure, and the cost is shared according to the actual payment case. Different from general commercial health insurance, the price is based on the incidence of the disease, and the user pays a fixed premium first, and the sharing amount does not exceed the preset sharing threshold. The sharing amount does not exceed the preset sharing threshold for each pending claim case, so that the sharing amount of each current insured user does not exceed the preset sharing threshold for each case to be claimed, so that each insured person can ensure that his or her interests will not suffer unlimited losses when obtaining insurance protection.
[0144] See also Figure 7 Taking insurance platform A as an example, a project processing method provided by one or more embodiments of this specification is described, including steps 702 to 730.
[0145] Step 702: Receive an insurance application request from a user in insurance platform A, wherein the insurance application request carries user identification information.
[0146] Step 704: Based on the user identification information, the user's health information and credit information are obtained, and it is determined whether the user meets the entry insurance review requirements, allowing the user to participate in insurance at zero cost. If so, execute step 706; if not, execute step 708.
[0147] Step 706: Allow the user to participate in the insurance, and establish a binding relationship between the user identification information and the user's corresponding account.
[0148] Step 708: The user is not allowed to participate in insurance.
[0149] Step 710: User 1 appears, and insurance platform A receives a claim request from user 1 among the insured users for the pending claim case, wherein the claim request carries the content of the pending claim case.
[0150] Step 712: Insurance platform A determines whether the pending claim case requires a claim based on the content of the pending claim case. If so, execute step 714; if not, execute step 724.
[0151] Step 714: accept the claim case and determine the share amount for each current insured user based on the current number of insured persons and the claim amount of the pending claim case.
[0152] Step 716: The content of the claims and the apportioned amounts will be announced to the public on the 7th and 21st of each month.
[0153] In one or more embodiments of the present specification, public disclosure helps to eliminate false cases.
[0154] Step 718: When the apportioned amount does not exceed the preset apportionment threshold, deductions are made from the account corresponding to each currently insured user on the 14th and 28th of each month.
[0155] In one or more embodiments of the present specification, per capita apportionment in a single case = (compensation amount + management fee) / compensation day. In addition, the preset apportionment threshold is 0.1 yuan, that is, the upper limit of the apportionment amount for each insured person in a single case is 0.1 yuan.
[0156] Step 720: After all deductions are successful, the insurance platform A summarizes the total amount deducted from the account corresponding to each current insured user.
[0157] Step 722: Insurance platform A pays the compensation amount to user 1.
[0158] Step 724: The project review team of insurance platform A conducts a review of the claim case and determines whether to agree to share the claim amount. If yes, execute step 726; if no, execute step 728.
[0159] Step 726: Agree to share the cost and continue with step 712.
[0160] Step 728: Do not agree to the sharing and end the claim case.
[0161] Step 730: The insured person voluntarily withdraws and does not participate in the claim settlement.
[0162] In one or more embodiments of this specification, the project processing method allows the insured users to enjoy the protection first and then participate in the sharing, and the sharing amount is calculated according to the actual risk and the situation that there is no objection through the claim disclosure. The cost sharing is carried out according to the actual situation of the claim case. It is different from the general commercial health insurance, which is priced according to the incidence of the disease, allowing users to pay a fixed premium first, and adopts a method in which the sharing amount does not exceed the preset sharing threshold; and twice a month, twice a month. On the public announcement day, all confirmed claims cases that occurred during the period will be announced and objections will be accepted on the premise of moderately hiding sensitive information. The security funds generated by all claims cases without objection to the public announcement, plus the prescribed 10% management fee, will be shared by all insured users on the sharing day, and the actual amount of sharing will depend on the actual situation of each public announcement. However, in a single claim case, the amount shared by each user will not exceed 0.1 cent, so that each insured person can ensure that his or her interests will not suffer unlimited losses when obtaining insurance protection.
[0163] See also Figure 8 One or more embodiments of this specification provide a project processing device, including:
[0164] The first receiving module 802 is configured to receive a user's project participation request, wherein the project participation request carries user identification information;
[0165] A first acquisition module 804 is configured to acquire first user information and second user information of a user based on the user identification information;
[0166] A first review module 806 is configured to perform access review on the user based on the first user information and the second user information of the user and provide a review result, wherein the review result includes whether the user is allowed to participate in the project;
[0167] The first binding module 808 is configured to establish a binding relationship between the user identification information and the account corresponding to the user when the audit result is to allow the user to participate in the project.
[0168] Optionally, the device further comprises:
[0169] A second receiving module is configured to receive a mutual aid fund application request for a mutual aid fund application case, wherein the mutual aid fund application request carries the content of the mutual aid fund application case;
[0170] The first determination module is configured to determine the apportionment amount of each current participating project user according to the number of current project participants and the mutual aid amount to be applied for the mutual aid case, if it is determined that the mutual aid case needs to apply for mutual aid according to the content of the mutual aid case;
[0171] A first deduction module is configured to deduct money from an account corresponding to each current project participating user when the apportioned amount does not exceed a preset apportionment threshold;
[0172] The second deduction module is configured to deduct an apportionment amount equal to the preset apportionment threshold from the account corresponding to each user currently participating in the project when the apportionment amount exceeds the preset apportionment threshold, and deduct the apportionment amount that exceeds the preset apportionment threshold from the second account associated with the project.
[0173] Optionally, the project includes a mutual aid project, including:
[0174] A third receiving module is configured to receive a user's project participation request, wherein the project participation request carries user identification information;
[0175] A second acquisition module is configured to acquire first user information and second user information of the user based on the user identification information;
[0176] A second review module is configured to perform access review on the user based on the first user information and the second user information of the user and provide a review result, wherein the review result includes whether the user is allowed to participate in the project;
[0177] The second binding module is configured to establish a binding relationship between the user identification information and the account corresponding to the user when the audit result is to allow the user to participate in the project.
[0178] Optionally, the device further comprises:
[0179] A fourth receiving module is configured to receive a mutual aid fund application request for a mutual aid fund application case, wherein the mutual aid fund application request carries the content of the mutual aid fund application case;
[0180] The second determination module is configured to determine the share amount of each current participating project user according to the number of current project participants and the mutual aid amount to be applied for the mutual aid case, if it is determined that the mutual aid case needs to apply for mutual aid according to the content of the mutual aid case;
[0181] A third deduction module is configured to deduct money from an account corresponding to each current project participating user when the shared amount does not exceed a preset shared threshold;
[0182] The fourth deduction module is configured to deduct an apportionment amount equal to the preset apportionment threshold from the account corresponding to each user currently participating in the project, and to deduct the apportionment amount that exceeds the preset apportionment threshold from the second account associated with the project.
[0183] Optionally, the project is an insurance project, including:
[0184] A fifth receiving module is configured to receive a project participation request from a user, wherein the project participation request carries user identification information;
[0185] A third acquisition module is configured to acquire the first user information and the second user information of the user based on the user identification information;
[0186] A third review module is configured to perform access review on the user based on the first user information and the second user information of the user and provide a review result, wherein the review result includes whether the user is allowed to participate in the project;
[0187] The third binding module is configured to establish a binding relationship between the user identification information and the account corresponding to the user when the audit result is to allow the user to participate in the project.
[0188] Optionally, the device further comprises:
[0189] A sixth receiving module is configured to receive a mutual aid fund application request for a mutual aid fund application case, wherein the mutual aid fund application request carries the content of the mutual aid fund application case;
[0190] The third determination module is configured to determine the apportionment amount of each current participating project user according to the number of current project participants and the mutual aid amount to be applied for the mutual aid case, if it is determined that the mutual aid case needs to apply for mutual aid according to the content of the mutual aid case;
[0191] A fifth deduction module is configured to deduct money from an account corresponding to each current project participating user when the shared amount does not exceed a preset shared threshold;
[0192] The sixth deduction module is configured to deduct an apportionment amount equal to the preset apportionment threshold from the account corresponding to each user currently participating in the project, and to deduct the apportionment amount that exceeds the preset apportionment threshold from the second account associated with the project.
[0193] Optionally, the first acquisition module 804, the second acquisition module or the third acquisition module is further configured to:
[0194] Acquire first user information determined by the user based on a preset first user information report; or
[0195] The first user information of the user is obtained based on a preset first user information obtaining model.
[0196] Optionally, the first acquisition module 804, the second acquisition module or the third acquisition module is further configured to include:
[0197] The second user information of the user is obtained based on a preset credit evaluation model.
[0198] Optionally, the device further comprises:
[0199] A building module configured to build a user blacklist when the audit result is that the user is not allowed to participate in the project;
[0200] A fourth acquisition module is configured to acquire the first user information of the user in the user blacklist according to a preset time interval when the second user information of the user in the user blacklist meets the access review;
[0201] The fourth review module is configured to allow the user to participate in the project if the first user information of the user meets the access review requirements.
[0202] Optionally, the device further comprises:
[0203] The fee receiving module is configured to allow the user to participate in the project if the first user information of the user in the user blacklist meets the preset requirements and the user pays the specified fee.
[0204] Optionally, the project participation request carries information about the user's associated persons.
[0205] When the audit result is to allow the user to participate in the project, the device further includes:
[0206] The designated associated person receiving module is configured to receive a project participation request from a designated associated person of a user.
[0207] Optionally, the account corresponding to each user currently participating in the project includes a custom account and a non-custom account.
[0208] Optionally, the device further comprises:
[0209] The deduction notification sending module is configured to send a deduction notification to each user currently participating in the project when it is determined that the mutual aid fund case to be applied for requires application for mutual aid funds based on the content of the mutual aid fund case to be applied for.
[0210] Optionally, the first deduction module, the third deduction module or the fifth deduction module is further configured to:
[0211] During the preset deduction period, deductions are made from the corresponding account of each current project user until the deduction is successful or the deduction period ends;
[0212] The second deduction module, the fourth deduction module or the sixth deduction module is further configured to:
[0213] During the preset deduction period, the apportionment amount equal to the preset apportionment threshold is deducted from the corresponding account of each current project user in a round-robin manner until the deduction is successful or the deduction period ends.
[0214] In one or more embodiments of the present specification, the project processing device enables user participation in the project through an audit model based on the user's first user information and second user information. This free way of participating in the project greatly improves the user's project participation experience, and enables the user's associated persons to participate in the project based on the user's basic data, thereby ensuring the sustainable development of the project.
[0215] It should be noted that the technical solution of the project processing device and the technical solution of the above-mentioned project processing method belong to the same concept. For details not described in detail in the technical solution of the project processing device, please refer to the description of the technical solution of the above-mentioned project processing method.
[0216] An embodiment of the present application further provides a computer-readable storage medium storing computer instructions, which, when executed by a processor, implement the steps of the project processing method as described above.
[0217] The above is a schematic scheme of a computer-readable storage medium of this embodiment. It should be noted that the technical scheme of the storage medium and the technical scheme of the above-mentioned project processing method belong to the same concept, and the details not described in detail in the technical scheme of the storage medium can be referred to the description of the technical scheme of the above-mentioned project processing method.
[0218] The computer instructions include computer program codes, which may be in source code form, object code form, executable files or some intermediate forms, etc. The computer-readable medium may include: any entity or device capable of carrying the computer program code, recording medium, USB flash drive, mobile hard disk, magnetic disk, optical disk, computer memory, read-only memory (ROM), random access memory (RAM), electric carrier signal, telecommunication signal and software distribution medium, etc. It should be noted that the content contained in the computer-readable medium may be appropriately increased or decreased according to the requirements of legislation and patent practice in the jurisdiction. For example, in some jurisdictions, according to legislation and patent practice, computer-readable media do not include electric carrier signals and telecommunication signals.
[0219] It should be noted that, for the above-mentioned method embodiments, for the sake of simplicity of description, they are all expressed as a series of action combinations, but those skilled in the art should be aware that the present application is not limited by the described action sequence, because according to the present application, certain steps can be performed in other sequences or simultaneously. Secondly, those skilled in the art should also be aware that the embodiments described in the specification are all preferred embodiments, and the actions and modules involved are not necessarily required by the present application.
[0220] In the above embodiments, the description of each embodiment has its own emphasis. For parts that are not described in detail in a certain embodiment, reference can be made to the relevant descriptions of other embodiments.
[0221] The preferred embodiments of the present application disclosed above are only used to help explain the present application. The optional embodiments do not describe all the details in detail, nor do they limit the invention to the specific implementation methods described. Obviously, many modifications and changes can be made according to the content of this specification. This specification selects and specifically describes these embodiments in order to better explain the principles and practical applications of the present application, so that those skilled in the art can understand and use the present application well. The present application is limited only by the claims and their full scope and equivalents.
Claims
1. A project processing method, characterized in that: include: Receive a project participation request from a user, wherein the project participation request carries user identification information; Based on the user identification information, the first user information and the second user information of the user are obtained, and a process backtracking of health notification and result data records are provided, wherein the first user information is health information, and the method for obtaining the health information of the user is: obtaining the health information determined by the user based on a preset health report, or obtaining the health information of the user based on a preset health model; the second user information is credit information, and the method for obtaining the credit information is: combining the credit score of the mutual aid platform, the risk control data of the insurance platform, the industry fraud risk control data of the insurance company, and the third-party authorization data, through artificial intelligence model analysis, the user is profiled, and a credit evaluation model for user access review is gradually formed, and the credit evaluation model is used to judge the user's credit information to obtain the credit information; Performing access review on the user based on the first user information and the second user information of the user and providing a review result, wherein the review result includes whether the user is allowed to participate in the project; If the audit result allows the user to participate in the project, a binding relationship is established between the user identification information and the user's corresponding account; If the audit result indicates that the user is not allowed to participate in the project, a user blacklist will be established; When the second user information of the user in the user blacklist satisfies the access review, obtaining the first user information of the user in the user blacklist according to a preset time interval; If the first user information of the user meets the access review requirements, allow the user to participate in the project; If the first user information of the user in the user blacklist meets the preset requirement and the user pays a designated fee, the user is allowed to participate in the project, wherein the designated fee is a deposit or a pre-deposited fee.
2. The method according to claim 1, characterized in that Also includes: Receiving a mutual aid fund application request for a mutual aid fund application case, wherein the mutual aid fund application request carries the content of the mutual aid fund application case; In the case where it is determined that the mutual aid fund case to be applied for needs to be applied for according to the content of the mutual aid fund case to be applied for, the apportionment amount for each current project user is determined according to the number of current project participants and the mutual aid amount to be applied for in the mutual aid fund case to be applied for; When the apportionment amount does not exceed the preset apportionment threshold, the amount is deducted from the account corresponding to each user currently participating in the project; When the shared amount exceeds the preset shared threshold, the shared amount equal to the preset shared threshold is deducted from the account corresponding to each user currently participating in the project, and the shared amount exceeding the preset shared threshold is deducted from the second account associated with the project.
3. The method according to claim 1, characterized in that The projects mentioned include mutual aid projects, including: Receive a project participation request from a user, wherein the project participation request carries user identification information; Acquire first user information and second user information of the user based on the user identification information; Performing access review on the user based on the first user information and the second user information of the user and providing a review result, wherein the review result includes whether the user is allowed to participate in the project; When the audit result allows the user to participate in the project, a binding relationship is established between the user identification information and the account corresponding to the user.
4. The method according to claim 3, characterized in that Also includes: Receiving a mutual aid fund application request for a mutual aid fund application case, wherein the mutual aid fund application request carries the content of the mutual aid fund application case; In the case where it is determined that the mutual aid fund case to be applied for needs to be applied for according to the content of the mutual aid fund case to be applied for, the apportionment amount for each current project user is determined according to the number of current project participants and the mutual aid amount to be applied for in the mutual aid fund case to be applied for; When the apportionment amount does not exceed the preset apportionment threshold, the amount is deducted from the account corresponding to each user currently participating in the project; When the shared amount exceeds the preset shared threshold, the shared amount equal to the preset shared threshold is deducted from the account corresponding to each user currently participating in the project, and the shared amount exceeding the preset shared threshold is deducted from the second account associated with the project.
5. The method according to claim 1, characterized in that: The items mentioned are insurance items, including: Receive a project participation request from a user, wherein the project participation request carries user identification information; Acquire first user information and second user information of the user based on the user identification information; Performing access review on the user based on the first user information and the second user information of the user and providing a review result, wherein the review result includes whether the user is allowed to participate in the project; When the audit result allows the user to participate in the project, a binding relationship is established between the user identification information and the account corresponding to the user.
6. The method according to claim 5, characterized in that Also includes: Receiving a mutual aid fund application request for a mutual aid fund application case, wherein the mutual aid fund application request carries the content of the mutual aid fund application case; In the case where it is determined that the mutual aid fund case to be applied for needs to be applied for according to the content of the mutual aid fund case to be applied for, the apportionment amount for each current project user is determined according to the number of current project participants and the mutual aid amount to be applied for in the mutual aid fund case to be applied for; When the apportionment amount does not exceed the preset apportionment threshold, the amount is deducted from the account corresponding to each user currently participating in the project; When the shared amount exceeds the preset shared threshold, the shared amount equal to the preset shared threshold is deducted from the account corresponding to each user currently participating in the project, and the shared amount exceeding the preset shared threshold is deducted from the second account associated with the project.
7. The method according to any one of claims 1 to 6, characterized in that: The project participation request carries the user's associated person information. When the audit result is to allow the user to participate in the project, the method further includes: Receive project participation requests from the user's designated associates.
8. The method according to claim 2, 4 or 6, characterized in that: The account corresponding to each user currently participating in the project includes a custom account and a non-custom account.
9. The method according to claim 2, 4 or 6, characterized in that: Also includes: When it is determined according to the content of the mutual aid fund case that the mutual aid fund case needs to be applied for, a deduction notice is issued to each user currently participating in the project.
10. The method according to claim 2, 4 or 6, characterized in that: Deductions from the corresponding account of each current project user include: During the preset deduction period, deductions are made from the corresponding account of each current project user until the deduction is successful or the deduction period ends; The amount of apportionment equal to the preset apportionment threshold will be deducted from the account corresponding to each current participating project user, including: During the preset deduction period, the apportionment amount equal to the preset apportionment threshold is deducted from the corresponding account of each current project user in a round-robin manner until the deduction is successful or the deduction period ends.
11. A project processing device, characterized in that: include: A first receiving module is configured to receive a user's project participation request, wherein the project participation request carries user identification information; A first acquisition module is configured to acquire first user information and second user information of a user based on the user identification information, wherein the first user information is health information, and a method of acquiring the health information of the user is: acquiring the health information determined by the user based on a preset health report, or acquiring the health information of the user based on a preset health model; A first review module is configured to conduct an access review on the user based on the first user information and the second user information of the user and give a review result, wherein the review result includes whether the user is allowed to participate in the project, and the second user information is credit information, and the credit information is obtained by: combining the credit score of the mutual aid platform, the risk control data of the insurance platform, the industry fraud risk control data of the insurance company, and the third-party authorization data, through artificial intelligence model analysis, to profile the user, gradually form a credit evaluation model for user access review, and use the credit evaluation model to judge the user's credit information to obtain the credit information; A first binding module is configured to establish a binding relationship between the user identification information and the user's corresponding account when the audit result is to allow the user to participate in the project; A building module configured to build a user blacklist when the audit result is that the user is not allowed to participate in the project; A fourth acquisition module is configured to acquire the first user information of the user in the user blacklist according to a preset time interval when the second user information of the user in the user blacklist meets the access review; A fourth review module is configured to allow the user to participate in the project if the first user information of the user meets the access review requirements; The fee receiving module is configured to allow the user to participate in the project if the first user information of the user in the user blacklist meets the preset requirements and the user pays a specified fee, wherein the specified fee is a deposit or a pre-deposited fee.
12. The device according to claim 11, characterized in that The device also includes: A second receiving module is configured to receive a mutual aid fund application request for a mutual aid fund application case, wherein the mutual aid fund application request carries the content of the mutual aid fund application case; The first determination module is configured to determine the apportionment amount of each current participating project user according to the number of current project participants and the mutual aid amount to be applied for the mutual aid case, if it is determined that the mutual aid case needs to apply for mutual aid according to the content of the mutual aid case; A first deduction module is configured to deduct money from an account corresponding to each current project participating user when the apportioned amount does not exceed a preset apportionment threshold; The second deduction module is configured to deduct an apportionment amount equal to the preset apportionment threshold from the account corresponding to each user currently participating in the project when the apportionment amount exceeds the preset apportionment threshold, and deduct the apportionment amount that exceeds the preset apportionment threshold from the second account associated with the project.
13. The device according to claim 11, characterized in that The projects mentioned include mutual aid projects, including: A third receiving module is configured to receive a user's project participation request, wherein the project participation request carries user identification information; A second acquisition module is configured to acquire first user information and second user information of the user based on the user identification information; A second review module is configured to perform access review on the user based on the first user information and the second user information of the user and provide a review result, wherein the review result includes whether the user is allowed to participate in the project; The second binding module is configured to establish a binding relationship between the user identification information and the account corresponding to the user when the audit result is to allow the user to participate in the project.
14. The device according to claim 13, characterized in that Also includes: A fourth receiving module is configured to receive a mutual aid fund application request for a mutual aid fund application case, wherein the mutual aid fund application request carries the content of the mutual aid fund application case; The second determination module is configured to determine the share amount of each current participating project user according to the number of current project participants and the mutual aid amount to be applied for the mutual aid case, if it is determined that the mutual aid case needs to apply for mutual aid according to the content of the mutual aid case; A third deduction module is configured to deduct money from an account corresponding to each current project participating user when the shared amount does not exceed a preset shared threshold; The fourth deduction module is configured to deduct an apportionment amount equal to the preset apportionment threshold from the account corresponding to each user currently participating in the project, and to deduct the apportionment amount that exceeds the preset apportionment threshold from the second account associated with the project.
15. The device according to claim 11, characterized in that The items mentioned are insurance items, including: A fifth receiving module is configured to receive a project participation request from a user, wherein the project participation request carries user identification information; A third acquisition module is configured to acquire the first user information and the second user information of the user based on the user identification information; A third review module is configured to perform access review on the user based on the first user information and the second user information of the user and provide a review result, wherein the review result includes whether the user is allowed to participate in the project; The third binding module is configured to establish a binding relationship between the user identification information and the account corresponding to the user when the audit result is to allow the user to participate in the project.
16. The device according to claim 15, characterized in that Also includes: A sixth receiving module is configured to receive a mutual aid fund application request for a mutual aid fund application case, wherein the mutual aid fund application request carries the content of the mutual aid fund application case; The third determination module is configured to determine the apportionment amount of each current participating project user according to the number of current project participants and the mutual aid amount to be applied for the mutual aid case, if it is determined that the mutual aid case needs to apply for mutual aid according to the content of the mutual aid case; A fifth deduction module is configured to deduct money from an account corresponding to each current project participating user when the shared amount does not exceed a preset shared threshold; The sixth deduction module is configured to deduct an apportionment amount equal to the preset apportionment threshold from the account corresponding to each user currently participating in the project, and to deduct the apportionment amount that exceeds the preset apportionment threshold from the second account associated with the project.
17. The device according to any one of claims 11 to 16, characterized in that: The project participation request carries the user's associated person information. When the audit result is to allow the user to participate in the project, the device further includes: The designated associated person receiving module is configured to receive a project participation request from a designated associated person of a user.
18. The device according to claim 12, 14 or 16, characterized in that The account corresponding to each user currently participating in the project includes a custom account and a non-custom account.
19. The device according to claim 12, 14 or 16, characterized in that The device also includes: The deduction notification sending module is configured to send a deduction notification to each user currently participating in the project when it is determined that the mutual aid fund case to be applied for requires application for mutual aid funds based on the content of the mutual aid fund case to be applied for.
20. The device according to claim 12, characterized in that The first deduction module is further configured to: During the preset deduction period, deductions are made from the corresponding account of each current project user until the deduction is successful or the deduction period ends; The second deduction module is further configured to: During the preset deduction period, the apportionment amount equal to the preset apportionment threshold is deducted from the corresponding account of each current project user in a round-robin manner until the deduction is successful or the deduction period ends.
21. The device according to claim 14, characterized in that The third deduction module is further configured as follows: During the preset deduction period, deductions are made from the corresponding account of each current project user until the deduction is successful or the deduction period ends; The fourth deduction module is further configured to: During the preset deduction period, the apportionment amount equal to the preset apportionment threshold is deducted from the corresponding account of each current project user in a round-robin manner until the deduction is successful or the deduction period ends.
22. The device according to claim 16, characterized in that The fifth deduction module is further configured as follows: During the preset deduction period, deductions are made from the corresponding account of each current project user until the deduction is successful or the deduction period ends; The sixth deduction module is further configured as follows: During the preset deduction period, the apportionment amount equal to the preset apportionment threshold is deducted from the corresponding account of each current project user in a round-robin manner until the deduction is successful or the deduction period ends.
23. A computing device comprising a memory, a processor, and computer instructions stored in the memory and executable on the processor, characterized in that: When the processor executes the instruction, the steps of the method according to any one of claims 1 to 10 are implemented.
24. A computer-readable storage medium storing computer instructions, characterized in that: When the instruction is executed by a processor, the steps of the method described in any one of claims 1 to 10 are implemented.
