A three-pillar payment management method and device

Abstract

The embodiment of the present invention provides a management method and device for three-pillar payment, which is applied to a blockchain platform, including: when receiving the payment rules of the target account under each pillar type of the three-pillar model of pension, the payment rules are stored on the blockchain platform; when receiving the payment application of the target account, the target blockchain node is determined based on the account information and pillar type in the payment application, and the pillar type corresponding to the payment rules in the target blockchain node is the same as the pillar type in the payment application; based on the payment restriction rules under the preset target pillar type and the payment rules in the target blockchain node, the abnormal situation of the payment data in the payment application is determined; and the payment application is managed based on the abnormal situation of the payment data. The embodiment of the present invention can complete the payment business using the data in different blockchain nodes, and realizes the unified management of the payment business in the three pillars.

Description

Technical Field

[0001] The present invention relates to the field of data processing technology, and in particular to a management method and device for three-pillar payment. Background Art

[0002] The three-pillar pension model is a pension system model widely adopted internationally. Among them, the first pillar: legally enforced public pensions. The first pillar is generally a public pension plan enforced by government law, which aims to provide the most basic pension security for retirees. At the same time, the government provides ultimate responsibility and security for public pensions. The second pillar: an occupational pension plan jointly paid by enterprises and individuals. In some countries, occupational pension plans jointly paid by enterprises and individuals have become the main body of the pension system. The third pillar: an individual pension savings plan. The third pillar is an individual pension savings plan based on personal wishes and a fully accumulated system, with voluntary contributions from individuals.

[0003] At present, since the payment process and payment rules under each pillar are the same, in order to improve the efficiency of payment business and avoid interference between payment businesses of different pillars, payment business under each pillar is usually handled by different regulatory agencies.

[0004] However, although the above-mentioned control method is conducive to the management of payment services by the regulatory agencies, it is not user-friendly and requires users to apply for payment services under each pillar at different regulatory agencies. Summary of the invention

[0005] The embodiment of the present invention provides a three-pillar payment management method and device to solve the problem of inconvenience and low efficiency in user payment application under the three-pillar pension model in the prior art.

[0006] In a first aspect, an embodiment of the present invention provides a three-pillar payment management method, which is applied to a blockchain platform, and the method includes:

[0007] Upon receiving the payment rules of the target account under each pillar type of the three-pillar pension model, the payment rules are stored on the blockchain platform, wherein the payment rules under different pillar types are stored in different blockchain nodes of the blockchain platform;

[0008] Upon receiving a payment application from a target account, determining a target blockchain node based on the account information and pillar type in the payment application, wherein the pillar type corresponding to the payment rule in the target blockchain node is the same as the pillar type in the payment application;

[0009] Determine the abnormality of the payment data in the payment application based on the payment restriction rules under the preset target pillar type and the payment rules in the target blockchain node, wherein the target pillar type is the same as the pillar type in the payment application;

[0010] The payment application is managed based on the abnormality of the payment data.

[0011] Optionally, the blockchain platform stores payment restriction rules under each pillar type, and different restriction rule identifiers are set in the blockchain platform corresponding to the payment restriction rules under different pillar types, wherein the payment rules under the target pillar type include restriction rule identifiers corresponding to the payment restriction rules under the target pillar type.

[0012] Optionally, upon receiving a payment application from a target account, determining a target blockchain node based on account information and a pillar type in the payment application includes:

[0013] Upon receiving a payment application from a target account and the payment application meets the target conditions, determining a target blockchain node based on the account information and pillar type in the payment application;

[0014] The target condition includes any one of the following:

[0015] The pillar type in the payment application is the first pillar;

[0016] The pillar type in the payment application is not the first pillar, and the target account has completed payment under the first pillar.

[0017] Optionally, when the target pillar type is the first pillar, determining the abnormality of the payment data in the payment application based on the preset payment restriction rules under the target pillar type and the payment rules in the target blockchain node includes:

[0018] Determine the amount payable in the target account based on the payment rules in the target blockchain node;

[0019] Determine the limit amount range of the target account based on the payment limit rules under the target pillar type;

[0020] Based on the numerical relationships between the payable amount, the limit amount range and the payment data in the payment application, an abnormality of the payment data in the payment application is determined.

[0021] Optionally, when the target pillar type is the second pillar, determining the abnormality of the payment data in the payment application based on the preset payment restriction rules under the target pillar type and the payment rules in the target blockchain node includes:

[0022] Determine the amount payable in the target account based on the payment rules in the target blockchain node;

[0023] Determine the limit amount range of the target account based on the payment limit rules under the target pillar type;

[0024] Determine a target ratio value by taking the ratio of the payment amount of the target account under the first pillar and the second pillar respectively;

[0025] Based on the first numerical relationship and the second numerical relationship, it is determined that the payment data in the payment application is abnormal, wherein the first numerical relationship includes the numerical relationships between the payable amount and the limit amount range and the payment data in the payment application, and the second numerical relationship includes: the numerical relationship between the target ratio value and the preset ratio range, and the preset ratio range is a ratio range determined based on the correlation relationship between the first pillar and the second pillar in the three-pillar pension model.

[0026] Optionally, when the target pillar type is the third pillar, determining the abnormality of the payment data in the payment application based on the preset payment restriction rules under the target pillar type and the payment rules in the target blockchain node includes:

[0027] Determine the limit amount range of the target account based on the payment limit rules under the target pillar type;

[0028] Based on the numerical relationship between the limit amount range and the payment data in the payment application, an abnormality of the payment data in the payment application is determined.

[0029] In a second aspect, an embodiment of the present invention further provides a three-pillar payment management system, which is applied to a blockchain platform, and the device includes:

[0030] Upon receiving the payment rules of the target account under each pillar type of the three-pillar pension model, the payment rules are stored on the blockchain platform, wherein the payment rules under different pillar types are stored in different blockchain nodes of the blockchain platform;

[0031] Upon receiving a payment application from a target account, determining a target blockchain node based on the account information and pillar type in the payment application, wherein the pillar type corresponding to the payment rule in the target blockchain node is the same as the pillar type in the payment application;

[0032] Determine the abnormality of the payment data in the payment application based on the payment restriction rules under the preset target pillar type and the payment rules in the target blockchain node, wherein the target pillar type is the same as the pillar type in the payment application;

[0033] The payment application is managed based on the abnormality of the payment data.

[0034] Optionally, the blockchain platform stores payment restriction rules under each pillar type, and different restriction rule identifiers are set in the blockchain platform corresponding to the payment restriction rules under different pillar types, wherein the payment rules under the target pillar type include restriction rule identifiers corresponding to the payment restriction rules under the target pillar type.

[0035] In the third aspect, an embodiment of the present invention further provides an electronic device, comprising: a processor, a communication interface, a memory and a communication bus; wherein the processor, the communication interface and the memory communicate with each other through the communication bus; the memory is used to store computer programs; the processor is used to implement the steps in the three-pillar payment management method as described above when executing the program stored in the memory.

[0036] In a fourth aspect, an embodiment of the present invention further provides a computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements the steps in the three-pillar payment management method as described above.

[0037] In an embodiment of the present invention, blockchain technology is used to store the user's payment rules under different pillars in different blockchain nodes of the blockchain platform when the payment rules of the target account under each pillar type of the three-pillar model of pension are received. Thus, when a payment application of the target account is received, the target blockchain node is determined based on the account information and pillar type in the payment application, and the payment application is managed by using the payment rules in the target blockchain node and the payment restriction rules under the preset target pillar type. Among them, the pillar type in the payment application can be any pillar type, that is, the user can apply for payment services under each pillar type, and only needs to adjust the pillar type in the payment application adaptively according to the needs, which reduces the user's operations and improves the processing efficiency; at the same time, it also avoids mutual interference in the payment service processing process under different pillars. BRIEF DESCRIPTION OF THE DRAWINGS

[0038] In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the accompanying drawings required for use in the description of the embodiments of the present invention will be briefly introduced below. Obviously, the accompanying drawings in the following description are only some embodiments of the present invention. For ordinary technicians in this field, other accompanying drawings can be obtained based on these accompanying drawings without paying creative labor.

[0039] Figure 1 A flowchart of the steps of the three-pillar payment management method provided by the embodiment of the present invention;

[0040] Figure 2 A schematic diagram of the application architecture of the three-pillar payment management method provided by an embodiment of the present invention;

[0041] Figure 3 A flowchart of the execution steps of the payment management contract for the first pillar provided by an embodiment of the present invention;

[0042] Figure 4 A flowchart of the execution steps of the payment management contract for the second pillar provided by an embodiment of the present invention;

[0043] Figure 5 A flowchart of the execution steps of the payment management contract for the third pillar provided by an embodiment of the present invention;

[0044] Figure 6 A structural block diagram of a three-pillar payment management device provided by an embodiment of the present invention;

[0045] Figure 7 This is a structural block diagram of an electronic device provided by an embodiment of the present invention. DETAILED DESCRIPTION

[0046] The following will be combined with the drawings in the embodiments of the present invention to clearly and completely describe the technical solutions in the embodiments of the present invention. Obviously, the described embodiments are part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of the present invention.

[0047] It should be understood that the references to "one embodiment" or "an embodiment" throughout the specification mean that the specific features, structures, or characteristics associated with the embodiment are included in at least one embodiment of the present invention. Therefore, the references to "in one embodiment" or "in an embodiment" appearing throughout the specification do not necessarily refer to the same embodiment. In addition, these specific features, structures, or characteristics may be combined in any suitable manner in one or more embodiments.

[0048] In various embodiments of the present invention, it should be understood that the size of the serial numbers of the following processes does not mean the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of the present invention.

[0049] See also Figure 1 , an embodiment of the present invention provides a three-pillar payment management method, which is applied to a blockchain platform. The blockchain platform is a platform or system built using blockchain technology. The three-pillar payment management method may include:

[0050] Step 101: Upon receiving the payment rules of the target account under each pillar type of the three-pillar pension model, the payment rules are stored on the blockchain platform.

[0051] It should be noted that the payment rules are the payment rules that need to be followed or satisfied when an account handles payment services. It is understandable that the payment rules under different pillar types in the three-pillar model of pension are different, and the payment rules of different accounts under the same pillar type may be the same or different. Specifically, the payment rules can be determined based on the payment business in the three-pillar model of pension, that is, the user fills in the data table based on the payment business in the three-pillar model of pension, and sends the filled-in data table as the payment rules to the blockchain platform. Here, the payment rules under different pillar types are stored in different blockchain nodes of the blockchain platform. Different payment rules are stored through different blockchain nodes. Among them, different payment rules can be payment rules for the same account under different pillar types, or they can be payment rules for different accounts under the same pillar type.

[0052] Step 102: Upon receiving a payment application from a target account, determine the target blockchain node based on the account information and pillar type in the payment application.

[0053] It should be noted that the payment application is an application submitted by the target account to the blockchain platform during the payment process, which contains the account information of the target account, so that the blockchain platform can distinguish the target account from other accounts, and find data related to the target account rather than other accounts. Specifically, the account information may include the enterprise number, employee number, employee ID number, etc., but is not limited to this. The payment application also includes the pillar type, which can inform the blockchain platform which pillar type the target account pays for. Specifically, the pillar types include: the first pillar, the second pillar and the third pillar, and the pillar in the payment application is any of the above three pillar types.

[0054] In the case where the pillar type in the payment application is the target pillar type, when searching for the payment rules of the target account under the target pillar type in a large number of blockchain nodes storing payment rules on the blockchain platform, the target pillar type is matched with the pillar type corresponding to the payment rules in each blockchain node. If the match is successful, the two pillar types are the same, and the corresponding blockchain node is the target blockchain node. That is, the pillar type corresponding to the payment rules in the target blockchain node is the same as the pillar type in the payment application.

[0055] Step 103: Based on the payment restriction rules under the preset target pillar type and the payment rules in the target blockchain node, determine the abnormal situation of the payment data in the payment application.

[0056] It should be noted that the payment rules and payment restriction rules under the same pillar type are used to determine the abnormal situation of the payment data in the payment application. Among them, the same pillar type is the pillar type in the payment application. That is, the target pillar type is the same as the pillar type in the payment application.

[0057] It is understandable that the payment restriction rules are the restriction rules set by the payment service for the fees paid by the account when the account handles the payment service. In the three-pillar model of pension, the payment restriction rules under different pillar types are different. It is understandable that the payment restriction rules under the same pillar type do not distinguish between accounts, that is, the payment restriction rules of different accounts under the same pillar type are the same. Therefore, all the payment restriction rules under each pillar type can be stored in the blockchain platform in advance.

[0058] The abnormal situations of payment data in the payment application can be divided into two categories, namely, data abnormalities and data without abnormalities. Among them, data abnormalities can indicate payment violations, and data without abnormalities can indicate no payment violations.

[0059] Step 104: Manage the payment application based on the abnormal situation of the payment data.

[0060] It should be noted that if there is no abnormality in the payment data, the payment process can be started and the payment service can be successfully processed. If the payment data is abnormal, the payment service can be stopped and a notification can be issued to remind the user, such as sending an email to a fixed email address indicating payment violations, but not limited to this.

[0061] In the embodiment of the present invention, blockchain technology is used to store the user's payment rules under different pillars in different blockchain nodes of the blockchain platform when the payment rules of the target account under each pillar type of the three-pillar model of pension are received. Thus, when the payment application of the target account is received, the target blockchain node is determined based on the account information and pillar type in the payment application, and the payment application is managed by using the payment rules in the target blockchain node and the payment restriction rules under the preset target pillar type. Among them, the pillar type in the payment application can be any pillar type, that is, the user can apply for the payment service under each pillar type, and only needs to adjust the pillar type in the payment application adaptively according to the demand, which reduces the user's operation and improves the processing efficiency; at the same time, it also avoids mutual interference in the payment service processing process under different pillars.

[0062] Optionally, the blockchain platform stores payment restriction rules under each pillar type, and different restriction rule identifiers are set in the blockchain platform corresponding to the payment restriction rules under different pillar types, wherein the payment rules under the target pillar type include the restriction rule identifiers corresponding to the payment restriction rules under the target pillar type.

[0063] It should be noted that the blockchain platform can process payment services under each pillar type, and therefore will store payment restriction rules under each pillar type. In order to distinguish different payment restriction rules, different restriction rule identifiers can be set for each payment restriction rule, and the restriction rule identifier can be a unique identifier composed of one or more of numbers, letters, and special symbols, so that different payment restriction rules have different restriction rule identifiers.

[0064] Since payment rules and payment restriction rules need to be used simultaneously when determining abnormal situations of payment data, and there is a corresponding relationship between the two rules, that is, both are for the same pillar type, therefore, for ease of use, the restriction rule identifier of the corresponding payment restriction rule can be set in the payment rule.

[0065] Preferably, the payment rules and payment restriction rules can be stored in the form of a data table. Specifically, as shown in Table 1 below, the payment rules are stored in the form of Table 1.

[0066]

[0067] Table 1

[0068] In Table 1, different field names are encoded and represented by field codes.

[0069] The payment restriction rules may be stored in the form of Table 2 below.

[0070]

[0071]

[0072] Table 2

[0073] In Table 2, different field names are encoded and represented using field codes.

[0074] Correspondingly, when the payment rules and payment restriction rules are stored in the form of Table 1 and Table 2, the payment application can also be in the form of a data table, as shown in Table 3 below.

[0075]

[0076] Table 3

[0077] Different field names are coded and expressed using field codes in Table 3. In Table 3, the enterprise number, employee number, and employee ID number belong to account information, the account level is the pillar type, and the payment type and actual payment amount are payment data.

[0078] It is understandable that for the above Table 3, the Ministry of Human Resources and Social Security can be used as the endorsement node, and each enterprise has no right to view payment applications outside of the enterprise; for the above Table 1, the Ministry of Human Resources and Social Security can also be used as the endorsement node, but only the Ministry of Human Resources and Social Security can set to view the payment data; for the above Table 2, all enterprises and the Ministry of Human Resources and Social Security can see it. In this way, when users submit payment applications, they can obtain payment restriction rules from the blockchain platform as a reference.

[0079] In an embodiment of the present invention, different payment restriction rules are provided with different restriction rule identifiers, and the payment rules include restriction rule identifiers corresponding to the payment restriction rules under the same pillar type. This facilitates finding the corresponding payment restriction rules after determining the payment rules applicable to the payment application, and at the same time, the payment restriction rules can be reused without storing the payment restriction rules for different accounts.

[0080] Optionally, upon receiving a payment application from a target account, determining a target blockchain node based on account information and a pillar type in the payment application includes:

[0081] Upon receiving a payment application from a target account, and if the payment application meets the target conditions, determining the target blockchain node based on the account information and pillar type in the payment application;

[0082] The target condition includes any of the following:

[0083] The pillar type in the payment application is the first pillar;

[0084] The pillar type in the payment application is not the first pillar, and the target account has completed payment under the first pillar.

[0085] It should be noted that in the three-pillar pension model, if you want to handle the payment business of the second or third pillar, you need to have successfully handled the payment business under the first pillar, that is, you have completed the payment under the first pillar; otherwise, you cannot continue to handle the payment business. The non-first pillar here refers to the second or third pillar.

[0086] In an embodiment of the present invention, when the target account applies for payment of the second pillar or the third pillar, the target account is required to have completed the payment under the first pillar, thereby realizing the payment business demand for the second pillar or the third pillar in the three-pillar pension model.

[0087] Optionally, when the target pillar type is the first pillar, based on the payment restriction rules preset under the target pillar type and the payment rules in the target blockchain node, determining the abnormal situation of the payment data in the payment application includes:

[0088] Based on the payment rules in the target blockchain node, the amount payable in the target account is determined.

[0089] It should be noted that the amount payable by the target account is the amount of payment made by the target account according to the payment rules in the target blockchain node. For example, if the payment rule is 4% of the pre-tax salary, and the pre-tax salary of the target account is 10,000 yuan, then the amount payable = 10,000 yuan × 4% = 400 yuan.

[0090] Based on the payment limit rules under the target pillar type, determine the limit amount range of the target account.

[0091] It should be noted that the target account limit amount range is the reasonable amount range that the target account must follow when paying according to the payment limit rules under the target pillar type, that is, the paid fees should be within the limit amount range. For example, if the payment limit rule is [0%, 8%] of the pre-tax salary, and the pre-tax salary of the target account is 10,000 yuan, the limit amount range is [0 yuan, 800 yuan].

[0092] Based on the numerical relationships between the amount payable, the limit amount range and the payment data in the payment application, the abnormal situation of the payment data in the payment application is determined.

[0093] It should be noted that the payment data in the payment application is the fees paid in the target account. If the fees paid in the target account are equal to the amount payable and the fees paid in the target account are within the limit amount range, it means that there is no abnormality in the payment data, that is, the payment is not in violation of the regulations. Otherwise, it is considered as payment abnormality, that is, payment violation.

[0094] In the embodiment of the present invention, the amount payable and the limit amount range of the target account are determined through payment rules and payment limit rules respectively, and then based on the numerical relationship between the amount payable and the limit amount range and the payment data respectively, the abnormal situation of the payment data is determined, thereby realizing the verification of whether there is any abnormality in the payment data under the first pillar.

[0095] Optionally, when the target pillar type is the second pillar, based on the payment restriction rules preset under the target pillar type and the payment rules in the target blockchain node, determining the abnormal situation of the payment data in the payment application includes:

[0096] Based on the payment rules in the target blockchain node, the amount payable in the target account is determined.

[0097] It should be noted that the amount payable by the target account is the amount of payment made by the target account according to the payment rules in the target blockchain node. For example, if the payment rule is 4% of the pre-tax salary, and the pre-tax salary of the target account is 10,000 yuan, then the amount payable = 10,000 yuan × 4% = 400 yuan.

[0098] Based on the payment limit rules under the target pillar type, determine the limit amount range of the target account.

[0099] It should be noted that the target account limit amount range is the reasonable amount range that the target account must follow when paying according to the payment limit rules under the target pillar type, that is, the paid fees should be within the limit amount range. For example, if the payment limit rule is [0%, 8%] of the pre-tax salary, and the pre-tax salary of the target account is 10,000 yuan, the limit amount range is [0 yuan, 800 yuan].

[0100] The target ratio value is determined by taking the ratio of the payment amount of the target account under the first pillar and the second pillar respectively.

[0101] It should be noted that the target ratio is the ratio of the payment amount of the target account under the first pillar and the second pillar. For example, if the payment amount of the target account under the first pillar and the second pillar is 100 yuan and 800 yuan respectively, the target ratio = 100 / 800 = 1 / 8 = 0.125.

[0102] Based on the first numerical relationship and the second numerical relationship, it is determined that there is an abnormality in the payment data in the payment application.

[0103] It should be noted that the first numerical relationship includes the numerical relationship between the payable amount, the limit amount range and the payment data in the payment application, and the second numerical relationship includes: the numerical relationship between the target ratio value and the preset ratio range, which is a ratio range determined based on the relationship between the first pillar and the second pillar in the three-pillar model of pension. It can be understood that the payment amount under the first pillar and the second pillar in the three-pillar model of pension needs to meet a certain ratio, that is, the preset ratio range.

[0104] The payment data in the payment application is the fees paid by the target account. If the fees paid by the target account are equal to the amount payable, and the fees paid by the target account are within the limit amount range, and the target ratio value is within the preset ratio range, it means that there is no abnormality in the payment data, that is, the payment is not in violation of the rules. Otherwise, it is considered as payment abnormality, that is, payment violation.

[0105] In an embodiment of the present invention, the amount payable and the limit amount range of the target account are determined respectively through payment rules and payment limit rules, and then a first numerical relationship is determined based on the numerical relationship between the amount payable and the limit amount range and the payment data respectively, and a second numerical relationship is determined based on the ratio between the payment amounts of the target account under the first pillar and the second pillar and the numerical relationship with a preset proportion range, and the abnormal situation of the payment data is determined based on the two numerical relationships, thereby realizing the verification of whether there is an abnormality in the payment data under the second pillar.

[0106] Optionally, when the target pillar type is the third pillar, based on the payment restriction rules preset under the target pillar type and the payment rules in the target blockchain node, determining the abnormal situation of the payment data in the payment application includes:

[0107] Based on the payment limit rules under the target pillar type, determine the limit amount range of the target account.

[0108] It should be noted that the target account limit amount range is the reasonable amount range that the target account must follow when paying according to the payment limit rules under the target pillar type, that is, the paid fees should be within the limit amount range. For example, if the payment limit rule is [0%, 8%] of the pre-tax salary, and the pre-tax salary of the target account is 10,000 yuan, the limit amount range is [0 yuan, 800 yuan].

[0109] It is understandable that since the third pillar is paid by individuals, the corresponding payment rules. Here, in order to facilitate the unification of each pillar, an empty payment rule can be stored corresponding to the third pillar, and any payment amount satisfies the payment rule.

[0110] Based on the numerical relationship between the limit amount range and the payment data in the payment application, determine the abnormal situation of the payment data in the payment application.

[0111] It should be noted that the payment data in the payment application refers to the fees paid by the target account. If the fees paid by the target account are within the limit range, it means that there is no abnormality in the payment data, that is, the payment is not in violation of the regulations. Otherwise, it is considered as payment abnormality, that is, payment violation.

[0112] In the embodiment of the present invention, the limit amount range of the target account is determined by the payment limit rules, and then the abnormal situation of the payment data is determined based on the numerical relationship between the limit amount range and the payment data, thereby realizing the verification of whether there is any abnormality in the payment data under the third pillar.

[0113] Optionally, the payment rules include: payment basis, individual ratio, and enterprise ratio, wherein the payment basis is a basis for calculating the amount payable, and specifically, the payment basis may be pre-tax salary, but is not limited thereto.

[0114] Based on the payment rules in the target blockchain node, determine the amount payable by the target account, including:

[0115] Based on the payment benchmark and individual ratio in the target blockchain node, the amount payable by the individual is calculated;

[0116] Based on the payment benchmark and enterprise ratio in the target blockchain node, the amount payable by the enterprise is calculated;

[0117] The amount payable by individuals and the amount payable by enterprises shall be determined as the amount payable of the target account.

[0118] It should be noted that when determining the numerical relationship between the amount payable and the payment data, the payment data includes the individual payment amount and the enterprise payment amount, and the individual payment amount is compared with the individual payable amount, and the enterprise payment amount is compared with the enterprise payable amount.

[0119] In the embodiment of the present invention, the corresponding payment amount is refined through the individual ratio and the enterprise ratio in the payment rules.

[0120] Optionally, the payment restriction rules include: payment comparison benchmark, individual proportion range, enterprise proportion range, and overall proportion range, wherein the payment comparison benchmark is the basis for calculating the restricted amount range. Specifically, the payment comparison benchmark can be pre-tax salary, first pillar contribution amount, second pillar contribution amount, and third pillar contribution amount, but is not limited to this.

[0121] Based on the payment limit rules under the target pillar type, determine the limit amount range of the target account, including:

[0122] Based on the payment comparison benchmark and personal ratio range in the target blockchain node, the personal limit amount range is calculated;

[0123] Based on the payment comparison benchmark and enterprise ratio range in the target blockchain node, the enterprise limit amount range is calculated;

[0124] Based on the payment comparison benchmark and the overall ratio range in the target blockchain node, the overall limit amount range is calculated;

[0125] The personal limit amount range, corporate limit amount range and overall limit amount range are determined as the amount payable for the target account.

[0126] It should be noted that when determining the numerical relationship between the restricted amount range and the payment data, the payment data includes personal payment amounts and corporate payment amounts. The personal payment amount is compared with the personal restricted amount range, the corporate payment amount is compared with the corporate restricted amount range, and the sum of the personal payment amount and the corporate payment amount is compared with the overall restricted amount range.

[0127] In the embodiment of the present invention, the limit amount range is refined through the individual proportion range, enterprise proportion range, and overall proportion range in the payment limit rule.

[0128] like Figure 2 As shown, it is a schematic diagram of the application architecture of the three-pillar payment management method provided by an embodiment of the present invention, wherein the accounts under each pillar can apply for payment to the blockchain platform. The payment application under the first and second pillars is applied by the enterprise. The payment application under the third pillar is completed by the individual. Each pillar can initiate the payment process independently without any order restriction. The payment management contract of each pillar is called separately on the blockchain platform, and the payment automation payment management control is performed in each contract.

[0129] For the payment management contract of the first pillar, when the target account initiates the payment process according to its contract content, the specific process is as follows: Figure 3 As shown, the payment application includes the enterprise number, employee ID number, payment month, account level (pillar type), enterprise actual payment, individual actual payment, etc., for example, as shown in Table 4:

[0130]

[0131] Table 4

[0132] Step 301 is the abnormal judgment process of the enterprise part payment amount, step 302 is the abnormal judgment process of the individual part payment amount, and step 303 is the abnormal judgment process of the overall part (enterprise part + individual part) payment amount. Among them, step 301 and step 302 are not distinguished in order and can also be executed at the same time.

[0133] Here, first, step 301 is introduced: reading the payment rules stored in each blockchain node in the blockchain platform according to the enterprise number and employee number, and determining the corresponding payment rules. For example, the payment rules determined according to Table 4 are shown in Table 5 below:

[0134]

[0135] Table 5

[0136] According to Table 5, the payment basis number of the enterprise is B001. According to the case assumption, the payment basis is the pre-tax salary of 10,000. That is, the payment basis amount is determined according to the enterprise number, employee number, and payment basis number.

[0137] According to Table 5, the employee's corporate contribution rate is 8%, and the amount payable by the enterprise is 10,000 x 8%, which equals 800 yuan. That is, the amount payable is calculated based on the contribution base amount and contribution rate.

[0138] Determine whether the amount payable by the enterprise is equal to the amount actually paid by the enterprise. If not, issue a warning of violation of the amount payable by the enterprise. If they are equal, read the payment restriction rules according to the enterprise number, account level, and account type. For example, the payment restriction rules can be as shown in Table 6:

[0139]

[0140] Table 6

[0141] The proportion restriction rule numbers (R001, R002, R003) in Table 5 are associated with Table 6, and it can be seen that R002 corresponds to the restriction rules for the first pillar enterprise part. The comparison benchmark is the pre-tax salary of 10,000, the lower limit is 0%, and the upper limit is 8%. After calculation, it is found that the restriction amount range is [0, 800]. If the actual paid-in amount of the enterprise exceeds the restriction amount range, a violation warning of the enterprise proportion exceeding the standard will be pushed.

[0142] For step 302, the process is similar to step 301, except that step 302 is used to determine the abnormality of the amount of personal payment, and the data used is the data related to the individual. For example, the payment ratio used in Table 5 is 4%, and the amount payable for the personal part is calculated as 10000×4%, which equals 400 yuan. The lower limit ratio used in Table 6 is 0%, and the upper limit ratio is 4%. The calculation shows that the limit amount range is [0, 400], which will not be repeated here.

[0143] Similarly, for step 303, the enterprise payment and the individual payment are regarded as a whole, then the total actual payment amount = 400 + 800 = 1200, the lower limit ratio used in Table 6 is 0%, and the upper limit ratio is 12%. The calculation shows that the limit amount range is [0, 1200], which will not be repeated here.

[0144] For the payment management contract of the second pillar, when the target account initiates the payment process according to its contract content, the specific process is as follows: Figure 4 As shown, the payment application includes the enterprise number, employee ID number, payment month, account level (pillar type), enterprise actual payment, individual actual payment, etc., for example, it can be shown in the above Table 4. Then it is determined whether the first pillar has been paid. If not, a warning of failure to pay the first pillar is pushed. If so, it is determined whether the enterprise payment amount is abnormal, whether the individual payment amount is abnormal, and whether the overall payment amount is abnormal. The judgment process is the same as Figure 3 If the payment data in the payment application are normal, read the payment amount of the first pillar and the ratio limit of the payment amount of the second pillar to the first pillar, and judge whether the payment data is abnormal based on the ratio of the payment amount of the second pillar to the payment amount of the first pillar and the ratio limit. If so, push the warning of the violation of the ratio exceeding the limit, otherwise end.

[0145] For the payment management contract of the third pillar, when the target account initiates the payment process according to its contract content, the specific process is as follows: Figure 5 As shown, the payment application includes the enterprise number, employee ID number, payment month, account level (pillar type), enterprise actual payment, individual actual payment, etc., for example, as shown in the above Table 4. Then determine whether the payment has been made under the first pillar. If not, push the warning of unpaid first pillar. If so, read the payment rule restriction list, that is, the payment restriction rule. By reading the comparison benchmark type, extracting the benchmark value, and reading the proportion restriction, it is determined whether the payment data is abnormal. If so, push the warning of exceeding the standard violation. If not, end.

[0146] In the embodiment of the present invention, the payment restriction rules of the three pillars are set up based on blockchain technology to reach consensus, be credible and traceable. Based on blockchain contract technology, automatic payment management on the chain is realized, the management process is open and transparent, and unified management of the payment of the three pillars is realized.

[0147] The above introduces the three-pillar payment management method provided by the embodiment of the present invention. The following will introduce the three-pillar payment management device provided by the embodiment of the present invention in conjunction with the accompanying drawings.

[0148] See also Figure 6 The embodiment of the present invention also provides a three-pillar payment management device, which is applied to a blockchain platform, and the device includes:

[0149] The storage module 61 is used for storing the payment rules of the target account under each pillar type of the three-pillar model of pension on the blockchain platform upon receiving the payment rules, wherein the payment rules under different pillar types are stored in different blockchain nodes of the blockchain platform;

[0150] A query module 62, configured to determine a target blockchain node based on the account information and the pillar type in the payment application when receiving a payment application of a target account, wherein the pillar type corresponding to the payment rule in the target blockchain node is the same as the pillar type in the payment application;

[0151] A verification module 63, configured to determine an abnormality of the payment data in the payment application based on a preset payment restriction rule under the target pillar type and a payment rule in the target blockchain node, wherein the target pillar type is the same as the pillar type in the payment application;

[0152] The management module 64 is used to manage the payment application based on the abnormal situation of the payment data.

[0153] Optionally, the blockchain platform stores payment restriction rules under each pillar type, and different restriction rule identifiers are set in the blockchain platform corresponding to the payment restriction rules under different pillar types, wherein the payment rules under the target pillar type include the restriction rule identifiers corresponding to the payment restriction rules under the target pillar type.

[0154] Optionally, the query module 62 is specifically configured to determine the target blockchain node based on the account information and the pillar type in the payment application when receiving the payment application of the target account and the payment application meets the target condition;

[0155] The target condition includes any of the following:

[0156] The pillar type in the payment application is the first pillar;

[0157] The pillar type in the payment application is not the first pillar, and the target account has completed payment under the first pillar.

[0158] Optionally, when the target pillar type is the first pillar, the verification module 63 includes:

[0159] A first determining unit, configured to determine the amount payable by the target account based on the payment rules in the target blockchain node;

[0160] A second determination unit is used to determine a limit amount range of the target account based on the payment limit rule under the target pillar type;

[0161] The first verification unit is used to determine the abnormality of the payment data in the payment application based on the numerical relationship between the amount payable, the limit amount range and the payment data in the payment application.

[0162] Optionally, when the target pillar type is the second pillar, the verification module 63 includes:

[0163] A third determining unit, configured to determine the amount payable by the target account based on the payment rules in the target blockchain node;

[0164] A fourth determination unit, configured to determine a limit amount range of a target account based on a payment limit rule under a target pillar type;

[0165] A fifth determining unit is used to determine a target ratio value by taking the ratio of the payment amount of the target account under the first pillar and the second pillar respectively;

[0166] The second verification unit is used to determine the abnormal situation of the payment data in the payment application based on the first numerical relationship and the second numerical relationship, wherein the first numerical relationship includes the numerical relationship between the payable amount and the limit amount range and the payment data in the payment application respectively, and the second numerical relationship includes: the numerical relationship between the target ratio value and the preset ratio range, and the preset ratio range is a ratio range determined based on the correlation relationship between the first pillar and the second pillar in the three-pillar pension model.

[0167] Optionally, when the target pillar type is the third pillar, the verification module 63 includes:

[0168] A sixth determination unit, configured to determine a limit amount range of a target account based on a payment limit rule under a target pillar type;

[0169] The third verification unit is used to determine the abnormality of the payment data in the payment application based on the numerical relationship between the limit amount range and the payment data in the payment application.

[0170] The three-pillar payment management device provided by the embodiment of the present invention can achieve Figures 1 to 5 To avoid repetition, the various processes of implementing the management method of the three-pillar payment in the method embodiment will not be repeated here.

[0171] In an embodiment of the present invention, blockchain technology is used to store the user's payment rules under different pillars in different blockchain nodes of the blockchain platform when the payment rules of the target account under each pillar type of the three-pillar model of pension are received. Thus, when the payment application of the target account is received, the target blockchain node is determined based on the account information and pillar type in the payment application, and the payment application is managed by using the payment rules in the target blockchain node and the payment restriction rules under the preset target pillar type. Among them, the pillar type in the payment application can be any pillar type, that is, the user can apply for the payment service under each pillar type, and only needs to adjust the pillar type in the payment application according to the demand adaptively, which reduces the user's operation and improves the processing efficiency; at the same time, it also avoids mutual interference in the payment service processing process under different pillars.

[0172] On the other hand, an embodiment of the present invention also provides an electronic device, including a memory, a processor, a bus, and a computer program stored in the memory and executable on the processor, wherein the processor implements the steps in the above-mentioned three-pillar payment management method when executing the program.

[0173] Here is an example: Figure 7 A schematic diagram of the physical structure of an electronic device is shown.

[0174] like Figure 7 As shown, the electronic device may include: a processor 710, a communication interface 720, a memory 730 and a communication bus 740, wherein the processor 710, the communication interface 720 and the memory 730 communicate with each other through the communication bus 740. The processor 710 may call the logic instructions in the memory 730 to execute the following method:

[0175] Upon receiving the payment rules of the target account under each pillar type of the three-pillar model of pension, the payment rules are stored on the blockchain platform, wherein the payment rules under different pillar types are stored in different blockchain nodes of the blockchain platform;

[0176] Upon receiving a payment application from a target account, determining a target blockchain node based on the account information and pillar type in the payment application, wherein the pillar type corresponding to the payment rule in the target blockchain node is the same as the pillar type in the payment application;

[0177] Determine the abnormality of the payment data in the payment application based on the payment restriction rules under the preset target pillar type and the payment rules in the target blockchain node, where the target pillar type is the same as the pillar type in the payment application;

[0178] Manage payment applications based on anomalies in payment data.

[0179] In addition, the logic instructions in the above-mentioned memory 730 can be implemented in the form of a software functional unit and can be stored in a computer-readable storage medium when it is sold or used as an independent product. Based on such an understanding, the technical solution of the present invention, in essence, or the part that contributes to the prior art or the part of the technical solution, can be embodied in the form of a software product, and the computer software product is stored in a storage medium, including a number of instructions for a computer device (which can be a personal computer, a server, or a network device, etc.) to perform all or part of the steps of the method described in each embodiment of the present invention. The aforementioned storage medium includes: U disk, mobile hard disk, read-only memory (ROM, Read-Only Memory), random access memory (RAM, Random Access Memory), disk or optical disk and other media that can store program codes.

[0180] On the other hand, an embodiment of the present invention further provides a computer-readable storage medium having a computer program stored thereon, which is implemented when the computer program is executed by a processor to execute the three-pillar payment management method provided in the above embodiments, for example, including:

[0181] Upon receiving the payment rules of the target account under each pillar type of the three-pillar model of pension, the payment rules are stored on the blockchain platform, wherein the payment rules under different pillar types are stored in different blockchain nodes of the blockchain platform;

[0182] Upon receiving a payment application from a target account, determining a target blockchain node based on the account information and pillar type in the payment application, wherein the pillar type corresponding to the payment rule in the target blockchain node is the same as the pillar type in the payment application;

[0183] Determine the abnormality of the payment data in the payment application based on the payment restriction rules under the preset target pillar type and the payment rules in the target blockchain node, where the target pillar type is the same as the pillar type in the payment application;

[0184] Manage payment applications based on anomalies in payment data.

[0185] The device embodiments described above are merely illustrative, wherein the units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, they may be located in one place, or they may be distributed on multiple network units. Some or all of the modules may be selected according to actual needs to achieve the purpose of the scheme of this embodiment. Ordinary technicians in this field can understand and implement it without paying creative labor.

[0186] Through the description of the above implementation methods, those skilled in the art can clearly understand that each implementation method can be implemented by means of software plus a necessary general hardware platform, and of course, it can also be implemented by hardware. Based on this understanding, the above technical solution is essentially or the part that contributes to the prior art can be embodied in the form of a software product, and the computer software product can be stored in a computer-readable storage medium, such as ROM / RAM, a disk, an optical disk, etc., including a number of instructions for a computer device (which can be a personal computer, a server, or a network device, etc.) to execute the methods described in each embodiment or some parts of the embodiments.

[0187] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present invention, rather than to limit it. Although the present invention has been described in detail with reference to the aforementioned embodiments, those skilled in the art should understand that they can still modify the technical solutions described in the aforementioned embodiments, or make equivalent replacements for some of the technical features therein. However, these modifications or replacements do not deviate the essence of the corresponding technical solutions from the spirit and scope of the technical solutions of the embodiments of the present invention.

Claims

1. A three-pillar payment management method, characterized in that: Applied to a blockchain platform, the method comprises: Upon receiving the payment rules of the target account under each pillar type of the three-pillar pension model, the payment rules are stored on the blockchain platform, wherein the payment rules under different pillar types are stored in different blockchain nodes of the blockchain platform; Upon receiving a payment application from a target account, determining a target blockchain node based on the account information and pillar type in the payment application, wherein the pillar type corresponding to the payment rule in the target blockchain node is the same as the pillar type in the payment application; Determine the abnormality of the payment data in the payment application based on the payment restriction rules under the preset target pillar type and the payment rules in the target blockchain node, wherein the target pillar type is the same as the pillar type in the payment application; Managing the payment application based on the abnormality of the payment data; The determining of abnormal conditions of payment data in the payment application based on the payment restriction rules under the preset target pillar type and the payment rules in the target blockchain node includes: In the case where the target pillar type is the first pillar, determining the amount payable by the target account based on the payment rules in the target blockchain node; Determine the limit amount range of the target account based on the payment limit rules under the target pillar type; Determine an abnormality of the payment data in the payment application based on the numerical relationship between the payable amount, the limit amount range and the payment data in the payment application; In the case where the target pillar type is the second pillar, determining the amount payable by the target account based on the payment rules in the target blockchain node; Determine the limit amount range of the target account based on the payment limit rules under the target pillar type; Determine a target ratio value by taking the ratio of the payment amount of the target account under the first pillar and the second pillar respectively; Based on the first numerical relationship and the second numerical relationship, it is determined that the payment data in the payment application is abnormal, wherein the first numerical relationship includes the numerical relationship between the payable amount and the limit amount range and the payment data in the payment application, respectively, and the second numerical relationship includes: the numerical relationship between the target ratio value and the preset ratio range, and the preset ratio range is a ratio range determined based on the correlation relationship between the first pillar and the second pillar in the three-pillar pension model; In the case where the target pillar type is the third pillar, determining the limit amount range of the target account based on the payment limit rules under the target pillar type; Based on the numerical relationship between the limit amount range and the payment data in the payment application, an abnormality of the payment data in the payment application is determined.

2. The method according to claim 1, characterized in that The blockchain platform stores payment restriction rules under each pillar type, and different restriction rule identifiers are set in the blockchain platform corresponding to the payment restriction rules under different pillar types, wherein the payment rules under the target pillar type include the restriction rule identifiers corresponding to the payment restriction rules under the target pillar type.

3. The method according to claim 1, characterized in that The step of determining the target blockchain node based on the account information and the pillar type in the payment application upon receiving the payment application of the target account includes: Upon receiving a payment application from a target account and the payment application meets the target conditions, determining a target blockchain node based on the account information and pillar type in the payment application; The target condition includes any one of the following: The pillar type in the payment application is the first pillar; The pillar type in the payment application is not the first pillar, and the target account has completed payment under the first pillar.

4. A three-pillar payment management device, characterized in that: Applied to the blockchain platform, the device includes: A storage module, configured to, upon receiving payment rules of a target account under each pillar type of the three-pillar pension model, store the payment rules on the blockchain platform, wherein payment rules under different pillar types are stored in different blockchain nodes of the blockchain platform; A query module, configured to, upon receiving a payment application from a target account, determine a target blockchain node based on the account information and pillar type in the payment application, wherein the pillar type corresponding to the payment rule in the target blockchain node is the same as the pillar type in the payment application; A verification module, configured to determine an abnormality of the payment data in the payment application based on a payment restriction rule under a preset target pillar type and a payment rule in the target blockchain node, wherein the target pillar type is the same as the pillar type in the payment application; A management module, used for managing the payment application based on the abnormal situation of the payment data; The verification module comprises: A first determining unit, configured to determine, when the target pillar type is the first pillar, an amount payable in the target account based on a payment rule in the target blockchain node; A second determining unit is used to determine a limit amount range of the target account based on the payment limit rule under the target pillar type when the target pillar type is the first pillar; A first verification unit is used to determine an abnormality of the payment data in the payment application based on the numerical relationship between the payable amount, the limit amount range and the payment data in the payment application when the target pillar type is the first pillar; A third determining unit, configured to determine, when the target pillar type is the second pillar, an amount payable in the target account based on a payment rule in the target blockchain node; A fourth determining unit, configured to determine a limit amount range of a target account based on a payment limit rule under the target pillar type when the target pillar type is the second pillar; A fifth determining unit, configured to determine a target proportion value by taking the proportion of the payment amounts of the target account under the first pillar and the second pillar respectively when the target pillar type is the second pillar; A second verification unit is used for determining, when the target pillar type is the second pillar, based on a first numerical relationship and a second numerical relationship, that the payment data in the payment application is abnormal, wherein the first numerical relationship includes the numerical relationship between the payable amount and the limit amount range and the payment data in the payment application, respectively, and the second numerical relationship includes: the numerical relationship between the target proportion value and a preset proportion range, and the preset proportion range is a proportion range determined based on the association relationship between the first pillar and the second pillar in the three-pillar pension model; A sixth determining unit, configured to determine a limit amount range of a target account based on a payment limit rule under the target pillar type when the target pillar type is the third pillar; The third verification unit is used to determine the abnormality of the payment data in the payment application based on the numerical relationship between the limit amount range and the payment data in the payment application when the target pillar type is the third pillar.

5. The device according to claim 4, characterized in that The blockchain platform stores payment restriction rules under each pillar type, and different restriction rule identifiers are set in the blockchain platform corresponding to the payment restriction rules under different pillar types, wherein the payment rules under the target pillar type include the restriction rule identifiers corresponding to the payment restriction rules under the target pillar type.

6. An electronic device, characterized in that: include: A processor, a communication interface, a memory and a communication bus; wherein the processor, the communication interface and the memory communicate with each other via the communication bus; Memory, used to store computer programs; The processor is used to implement the steps in the three-pillar payment management method as described in any one of claims 1 to 3 when executing the program stored in the memory.

7. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores a computer program, which, when executed by a processor, implements the steps of the three-pillar payment management method as described in any one of claims 1 to 3.

Images