CN111681117A - System, method and device for payment in treatment - Google Patents
System, method and device for payment in treatment Download PDFInfo
- Publication number
- CN111681117A CN111681117A CN202010450871.9A CN202010450871A CN111681117A CN 111681117 A CN111681117 A CN 111681117A CN 202010450871 A CN202010450871 A CN 202010450871A CN 111681117 A CN111681117 A CN 111681117A
- Authority
- CN
- China
- Prior art keywords
- payment
- target
- account
- plan
- preset
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q40/00—Finance; Insurance; Tax strategies; Processing of corporate or income taxes
- G06Q40/08—Insurance
Landscapes
- Business, Economics & Management (AREA)
- Accounting & Taxation (AREA)
- Finance (AREA)
- Engineering & Computer Science (AREA)
- Development Economics (AREA)
- Economics (AREA)
- Marketing (AREA)
- Strategic Management (AREA)
- Technology Law (AREA)
- Physics & Mathematics (AREA)
- General Business, Economics & Management (AREA)
- General Physics & Mathematics (AREA)
- Theoretical Computer Science (AREA)
- Financial Or Insurance-Related Operations Such As Payment And Settlement (AREA)
Abstract
The embodiment of the invention provides a system, a method and a device for payment on treatment. The system comprises: a trusted subsystem and an account management system; the trusted subsystem is used for receiving payment application operation of a user and acquiring a target payment plan of a target payment object in the payment application operation; if the number of the target payment plans is lower than a preset plan threshold value, executing a pending payment operation, and executing a subscriber cancellation operation on the target payment object when the remaining payment period number of the target payment object is zero and the account state is a preset state after the pending payment operation is detected to be completed; or if the number of the target payment plans is larger than or equal to a preset plan threshold value, sending a first obtaining operation carrying the identification number of the target payment object to the account management system; and the entrusted subsystem executes a user canceling operation on the target payment object when the account balance is judged to be lower than a preset balance threshold value and the account state is a preset state.
Description
Technical Field
The invention relates to the technical field of internet, in particular to a system, a method and a device for payment on treatment.
Background
In the field of insurance products, the treatment payment refers to a specific arrangement for paying pension to retirement plan beneficiaries; in the payment process, the trusted party acts as a corporate trusted party and needs to generate a payment plan for the corporation during each payment cycle. For the payment object which is completed by the term payment, the trustee is required to carry out the sales account for the payment object; however, when the payment is executed, the enterprise applies for the payment object only once, and the trustee cannot know whether the payment is completed or not, and needs the enterprise or the account manager to notify the trustee; thus, currently trusted parties only provide manual subscriber functions.
However, the manual account-cancelling function has a certain hysteresis, which results in a large amount of garbage payment plans generated for payment objects which are actually paid and occupy system memory; and because the number of payment objects is huge, a large labor cost is generated.
Disclosure of Invention
The embodiment of the invention provides a treatment payment system, a treatment payment method and a treatment payment device, which aim to solve the problem of limitation of manual account cancellation in a treatment payment process in the prior art.
In one aspect, an embodiment of the present invention provides a pending payment system, where the system includes: a trusted subsystem and an account management system;
the trusted subsystem is used for receiving payment application operation of a user and acquiring a target payment plan of a target payment object in the payment application operation, wherein the target payment plan comprises a plan generated in a current payment cycle and/or a plan remaining in a historical payment cycle;
if the number of the target payment plans is lower than a preset plan threshold value, executing a pending payment operation, and executing a subscriber cancellation operation on the target payment object when the remaining payment period number of the target payment object is zero and the account state is a preset state after the pending payment operation is detected to be completed;
or
If the number of the target payment plans is larger than or equal to a preset plan threshold value, sending a first obtaining operation carrying the identification number of the target payment object to the account management system;
the account management system is used for determining the account balance of the target payment object according to the identification number and sending the account balance to the trusted subsystem;
and the entrusted subsystem executes a user canceling operation on the target payment object when the account balance is judged to be lower than a preset balance threshold value and the account state is a preset state.
In one aspect, an embodiment of the present invention provides an encounter payment method, which is applied to a trusted subsystem of the encounter payment system, where the method includes:
receiving payment application operation of a user, and acquiring a target payment plan of a target payment object in the payment application operation, wherein the target payment plan comprises a plan generated in a current payment period and/or a plan remaining in a historical payment period;
if the number of the target payment plans is lower than a preset threshold value, executing a pending payment operation, and executing a user canceling operation on the target payment object when the remaining payment period number of the target payment object is zero and the account state is a preset state after the pending payment operation is detected to be completed;
or
If the number of the target payment plans is larger than or equal to a preset plan threshold value, determining the account balance of the target payment object, and executing a subscriber sales operation on the target payment object when the account balance is judged to be lower than the preset balance threshold value and the account state is a preset state.
On the other hand, an embodiment of the present invention further provides an acceptance payment device, which is applied to an entrusted subsystem of the acceptance payment system, and the device includes:
the operation receiving module is used for receiving payment application operation of a user and acquiring a target payment plan of a target payment object in the payment application operation, wherein the target payment plan comprises a plan generated in a current payment period and/or a plan remaining in a historical payment period;
the first account cancellation module is used for executing an account cancellation operation on the target payment object if the number of the target payment plans is lower than a preset threshold value, and when the fact that the payment operation is finished and the remaining payment period number of the target payment object is zero and the account state is in a preset state is detected;
or
And the second account cancelling module is used for determining the account balance of the target payment object if the number of the target payment plans is greater than or equal to a preset plan threshold value, and executing cancelling operation on the target payment object when the account balance is judged to be lower than the preset balance threshold value and the account state is in a preset state.
In yet another aspect, the present invention further provides an electronic device, which includes a memory, a processor and a computer program stored in the memory and executable on the processor, wherein the processor executes the computer program to implement the steps in the pending payment method as described above.
In still another aspect, an embodiment of the present invention further provides a computer-readable storage medium, on which a computer program is stored, where the computer program, when executed by a processor, implements the steps in the method for payment on encounter as described above.
In the embodiment of the invention, the trusted subsystem is used for receiving payment application operation of a user and acquiring a target payment plan of a target payment object in the payment application operation; executing a user canceling operation on the target payment object when the number of the target payment plans is judged to be lower than a preset plan threshold value and the payment waiting operation is completed, the remaining payment period number of the target payment object is zero and the account state is a preset state; or if the number of the target payment plans is greater than or equal to a preset plan threshold value, executing a user-canceling operation on the target payment object when the account balance is judged to be lower than the preset balance threshold value and the account state is a preset state; when the target payment object is detected to meet the account-cancelling condition, automatically cancelling the account, and avoiding the target object still generating a garbage payment plan and occupying a system memory; meanwhile, the entrusted subsystem automatically sells the user, so that the manual operation cost is saved.
Drawings
In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the drawings needed to be used in the description of the embodiments of the present invention will be briefly introduced below, and it is obvious that the drawings in the following description are only some embodiments of the present invention, and it is obvious for those skilled in the art that other drawings can be obtained according to these drawings without inventive labor.
Fig. 1 is an architecture diagram of a encounter payment system according to an embodiment of the present invention;
FIG. 2 is a diagram of a first exemplary application scenario in accordance with an embodiment of the present invention;
FIG. 3 is an interaction diagram of a second example of an embodiment of the present invention;
FIG. 4 is a flowchart illustrating the steps of a method for facilitating payment according to an embodiment of the present invention;
fig. 5 is a block diagram of a pending payment device according to an embodiment of the present invention;
fig. 6 is a block diagram of an electronic device according to an embodiment of the present invention.
Detailed Description
The technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are some, not all, embodiments of the present invention. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.
It should be appreciated that reference throughout this specification to "one embodiment" or "an embodiment" means that a particular feature, structure or characteristic described in connection with the embodiment is included in at least one embodiment of the present invention. Thus, the appearances of the phrases "in one embodiment" or "in an embodiment" in various places throughout this specification are not necessarily all referring to the same embodiment. Furthermore, the particular features, structures, or characteristics may be combined in any suitable manner in one or more embodiments.
In various embodiments of the present invention, it should be understood that the sequence numbers of the following processes do not mean the execution sequence, and the execution sequence of each process should be determined by its function and inherent logic, and should not constitute any limitation to the implementation process of the embodiments of the present invention.
In the embodiments provided herein, it should be understood that "B corresponding to A" means that B is associated with A from which B can be determined. It should also be understood that determining B from a does not mean determining B from a alone, but may be determined from a and/or other information.
Fig. 1 shows an architecture diagram of a pending payment system 100 according to an embodiment of the present invention.
As shown in fig. 1, an embodiment of the present invention provides a treatment payment system 100, including: a trusted subsystem 101 and an account pipe system 102; in the embodiment of the present invention, the example that the encounter payment system 100 is used for paying the annual fee of the enterprise is taken as an example, it can be understood that the encounter payment system 100 may also be used for paying other services.
The enterprise annuity is used as an endowment guarantee product, the enterprise annuity refers to a supplementary endowment fund service which is established by the enterprise according to the economic strength and the economic condition of the enterprise besides the compulsory endowment fund, and the enterprise annuity is a supplementary endowment fund system and aims to provide retirement income guarantee to a certain degree for the enterprise staff.
Specifically, the endowment insurance product takes an endowment insurance company as a consignee, receives the consignment of the consignee, and provides endowment insurance and fund management services related to the endowment insurance for the consignee, wherein the service items comprise scheme design, consignee management, account management, investment management, treatment payment, compensation delay, welfare plan, reservation incentive and the like.
Further, the encounter payment refers to a process of making payment for employees (i.e., payment objects) participating in the annuity plan according to the provision of annuities. For the payment objects meeting the payment application conditions, the selectable payment modes are one-time payment and staged payment, and the staged payment is divided into quota payment and periodic payment. One payment per payment period.
As a first example, referring to fig. 2, in the process of payment for a treatment, the enterprise serves as a trustee, and the trustee is entrusted to pay the relevant treatment for the payment object; the consignee is a legal person consignment organization which is entrusted by the consignor and manages the annual fund of the enterprise; the account managing party is a mechanism for receiving the entrusted party entrusts, managing the annual fund account of the enterprise and carrying out accounting.
The trusted subsystem 101 is a system for executing functions of a trusted party, and the trusted subsystem 101 is configured to receive a payment application operation of a user, and obtain a target payment plan of a target payment object in the payment application operation, where the target payment plan includes a plan generated in a current payment cycle and/or a plan remaining in a historical payment cycle.
The user is a client, usually an enterprise; the entrustor sends a payment application operation to the entrusted subsystem 101, and carries the identification number of the target payment object in the payment application operation, and each payment object can only apply for one payment usually; after receiving the payment application operation, the trusted subsystem 101 acquires a payment plan according to the identification number of the target payment object; the payment plan is a target payment plan for the target payment object.
In the current payment period, the target payment plan may have two types, one generated in the current payment period, and the other payment plan, i.e., the remaining unpaid payment plan in the historical payment period.
After acquiring all target payment plans for the target payment object, the trusted subsystem 101 determines a numerical relationship between the number of the target payment plans and a preset threshold, and according to different numerical relationships, the trusted subsystem 101 executes different operations. The preset threshold is the highest threshold of the unpaid payment plan that can be persisted.
Specifically, the operations performed by the trusted subsystem 101 are divided into two cases, case one or case two, depending on the number of target payment plans.
In case one, if the number of the target payment plans is lower than a preset plan threshold, the trusted subsystem 101 executes an operation of payment for treatment, and executes an operation of canceling the account for the target payment object when the remaining payment period number of the target payment object is zero and the account status is in a preset status after the completion of the operation of payment for treatment is detected;
and if the number of the target payment plans is lower than a preset plan threshold value, indicating that the number of the remaining target payment plans is normal and can execute the treatment payment operation, wherein the treatment payment operation is a treatment related to the target payment object.
After the pending payment operation of the current payment period is completed, when the trusted subsystem 101 detects that the remaining payment period number of the target payment object is zero and the account state is a preset state, the trusted subsystem 101 automatically executes a user canceling operation on the target payment object; specifically, the account status may include payment, payment or sale, etc.; the preset state may be set as a payment state, and the payment state indicates that the enterprise has started a payment process for the current account.
The remaining payment period is the payment period of the target object recorded by the trusted subsystem 101; the residual payment period is the difference between the initial period and the current payment period; for one-time payment, the initial period number of the payment object is 0, and for regular payment, the payment object is preset with the value of the initial period number; for a quota payment, the initial number of sessions is preset to an initial number of sessions, which is typically set to a larger number, such as 99.
Thus, for a payment object with a payment type of one-time payment or periodic payment, after completing the payment processing operation on the payment object in a certain payment period, the trusted subsystem 101 detects that the remaining payment period number is zero and the account status is the payment status, and automatically performs account cancellation on the payment object, so as to avoid that a useless garbage payment plan is generated for the target payment object subsequently and the system memory is occupied.
In case two, if the number of the target payment plans is greater than or equal to a preset plan threshold value, an abnormal condition may exist in an account of the target payment object, and a spam payment plan may exist in the target payment plan; the trusted subsystem 101 sends a first acquisition operation carrying the identification number of the target payment object to the account management system 102; the obtaining operation is used to obtain the account balance of the target payment object, which is the account of the target payment object maintained by the account management system 102, in which the total amount of treatment thereof that has not been paid to the target payment object is stored. The trusted subsystem 101 sends the first acquisition operation to the account pipe system 102, and carries the identification number of the target payment object in the first acquisition operation.
The account management system 102 is configured to determine an account balance of the target payment object according to the identification number, and send the account balance to the trusted subsystem 101; the account management system 102 searches for the account of the target object according to the identification number, and after determining the account balance, feeds back the account balance to the trusted subsystem 101.
When the trustee subsystem 101 judges that the account balance is lower than a preset balance threshold value and the account state is a preset state, executing a user canceling operation on the target payment object; optionally, the preset balance threshold is a lowest threshold for paying a treatment to the target payment object; when the account status of the target payment object is in the preset status and the account balance is not enough to pay once below the preset balance threshold, and the number of the remaining payment plans is large, which indicates that the target payment plan is an invalid payment plan, the trusted subsystem 101 automatically performs account cancellation on the target payment plan, so as to avoid generating useless garbage payment plans for the target payment object subsequently.
For a payment object that pays in a fixed amount, the trusted system typically presets its payment period number to a larger value, such as 99 days; thus, when the number of the target payment plans is judged to be large, the account balance needs to be checked; if the account balance is not enough to pay once again below the preset balance threshold, the target payment plan is an invalid plan, and the trusted subsystem 101 automatically performs account cancellation.
In addition, in the second case, if the trusted subsystem 101 determines that the account balance is not lower than the preset balance threshold, it sends an abnormal prompt message to prompt that there may be an abnormal situation in the account of the target payment object.
In the embodiment of the present invention, the trusted subsystem 101 is configured to receive a payment application operation of a user, and obtain a target payment plan of a target payment object in the payment application operation; executing a user canceling operation on the target payment object when the number of the target payment plans is judged to be lower than a preset plan threshold value and the payment waiting operation is completed, the remaining payment period number of the target payment object is zero and the account state is a preset state; or if the number of the target payment plans is greater than or equal to a preset plan threshold value, executing a user-canceling operation on the target payment object when the account balance is judged to be lower than the preset balance threshold value and the account state is a preset state; when the target payment object is detected to meet the account-cancelling condition, automatically cancelling the account, and avoiding the target object still generating a garbage payment plan and occupying a system memory; meanwhile, the entrusted subsystem 101 automatically sells users, so that the manual operation cost is saved. The embodiment of the invention solves the problem of limitation of manual account cancellation in the process of payment pending in the prior art.
It should be noted that, in the embodiment of the present invention, after the trusted subsystem 101 performs a payment on the target payment object, the trusted subsystem 101 still stores the historical data of the object to be subjected to the payment, including the payment plan and the relevant parameters of the payment operation of the object to be subjected to the payment.
Optionally, in this embodiment of the present invention, the encounter payment system further includes a hosting subsystem; the escrow subsystem is a mechanism for accepting an order from a consignee and escrowing the annual fund property of the enterprise, and serves as an escrow party.
The trusted subsystem performs a pending payment operation comprising: and sending a first payment instruction carrying the identification number to the account management system, wherein the first payment instruction is used for indicating the account management system to send a pending payment parameter of the target payment object to the escrow subsystem, and the pending payment parameter comprises payment content, amount, payment time and the like.
The entrusted subsystem receives the payment-to-be-encountered parameter fed back by the account management system and sends a second payment instruction carrying the payment-to-be-encountered parameter and the identification number to the hosting subsystem; the escrow subsystem pays for the treatment to the target payment object according to the second payment instruction.
Optionally, in an embodiment of the present invention, the account pipe system is further configured to: and receiving the first payment instruction, determining a pending payment parameter of the target payment object according to the identification number, and feeding back the pending payment parameter to the trusted subsystem.
After receiving the first payment instruction, the account management system searches an account according to the identification number in the first payment instruction, then determines specific parameters of treatment to be paid by the account in the current payment period, and then sends the parameters of the treatment payment to the trusted subsystem.
Optionally, in an embodiment of the present invention, the hosting subsystem is configured to: and receiving the second payment instruction, and paying the treatment to the target payment object according to the second payment instruction.
After determining the payment parameters to be met, the trusted subsystem sends a second payment instruction to the escrow subsystem; and the hosting subsystem pays the treatment to the treatment receiving account of the target payment object according to the second payment instruction.
As a second example, referring to fig. 3, fig. 3 shows a workflow of a pending payment system, which mainly includes the following steps:
step 1, the entrusting party sends a request for payment to be met to the entrusted subsystem.
Wherein the pending payment application is for the enterprise customer to submit an application to start payment, and the staff of each employee participating in the annuity plan applies only once.
And 2, the trusted subsystem acquires a target payment plan of the target payment object in the payment application operation.
Executing the step 3 when the number of the unmatched target payment plans is judged to be not more than a preset plan threshold (taking 5 as an example); otherwise, executing step 4.
And step 3, executing the pending payment operation, and executing step 5.
And 5, after the payment operation is finished, judging that the residual payment period number of the target payment object is zero and the account state is the payment state, and executing the 6 th step.
And 6, carrying out sales on the target payment object.
And 4, acquiring the account balance of the target payment object from the account management system by the trusted subsystem, and executing the 7 step.
Step 7, the trusted subsystem judges whether the account balance is lower than a preset balance threshold (such as zero), if so, the account state is a payment state, and the step 6 is executed; otherwise, executing step 8 and prompting the account to be abnormal.
Thus, for the payment object of one-time payment, after the first payment application of the consignor is completed, the residual payment period number is 1, and the account state of the member is payment; and the entrusted subsystem generates a first-time payment plan, judges that the currently unmatched payment plan is less than 5, makes a pending payment notification and executes a pending payment operation.
Then the remaining number of the payment period (the number of the period, i.e. the number of the payment plan) is 0 after the payment period is reduced by one, and then the entrusted subsystem judges that the remaining number of the period is 0 and the current account status is payment, and modifies the account status of the payment object into a sales account.
For the periodic payment personnel in the period, after the consignor completes the first payment application, the residual payment period number is the period number X required by the application, and the account state of the member is payment; and the entrusted subsystem generates a first-time payment plan, judges that the unmatched payment plan is less than 5, makes a pending payment notification and executes the pending payment operation.
Then, the remaining number of the payment period is X-1 after the payment period is reduced by one, the remaining number of the payment period is judged to be not 0, then the current account state is judged to be payment, and the process starts to wait for the generation of a payment plan again; entering circulation until the number of remaining period is 1, the account state of the member is payment, the system generates a first-period payment plan, the current unmatched payment plan is less than 5, and the trusted subsystem makes a notification of the payment for treatment; and then the trustee subsystem judges that the remaining period number is 0, the current account state is payment, and the account state of the system member is modified into account cancellation.
For the quota payment personnel in the period, after the consignor completes the first payment application, the period number cannot be judged due to the quota. The trusted subsystem defaults to the remaining number of periods 99. The account state of the payment object is payment, the trusted subsystem generates a first-time payment plan, judges that the current unmatched payment plan is smaller than 5, makes a pending payment notice, the remaining number of times after the payment number of times is reduced by one is 98, then judges that the current account state is payment and judges that the remaining number of times is not 0, the process starts to wait for the generation of the payment plan again, and enters a cycle.
And after circulating N times, when the unmatched payment plan is larger than 5, determining whether the account balance inquired at each period is 0 through the account management system. If the account status is 0 and the account status is payment, the trusted subsystem accounts the payment object for the sale; otherwise, generating abnormal prompt information so as to facilitate the manual intervention and the account management line to check whether the waiting personnel is the last payment or not and manually sell the account.
Further, as a third example, taking the entrusting party as enterprise a as an example, the payment period is 1 month, and the pending payment system mainly performs the following processes:
step one, enterprise a applies for a pending payment to the trusted subsystem for employee A, B, C; wherein, employee A is for one-time payment, employee B is for periodic payment (two-stage), and employee C is for quota payment.
And in the second step, in the first payment period, the trusted subsystem judges that the states of the three target payment objects are all payment, a payment plan is generated for each target payment object, and the remaining payment period numbers of the three are respectively as follows: stage A, 0; b, stage 1; c, stage 98.
The entrusted subsystem judges that the remaining payment period number of the employee A and the employee B is less than 5, sends a first payment instruction carrying the identification numbers of the employee A and the employee B to the account management system, acquires the pending payment parameters of the employee A and the employee B, carries the pending payment parameters in a second payment instruction and sends the second payment instruction to the trusteeship subsystem; the escrow subsystem performs a payment operation in accordance with the second payment instruction.
And after detecting that the payment operation to be met is completed, the trusted subsystem determines that the remaining payment period number of the employee A is zero and the account state is the payment state, and performs account cancellation on the employee A.
Meanwhile, the trusted subsystem judges that the remaining payment period number of the employee C is larger than 5, and if the account balance of the employee C obtained through the account and management system is larger than zero, the trusted subsystem executes payment operation on the employee C.
Employee B's remaining payment period is 1, employee C's remaining payment period is 98, and the next payment cycle is entered.
Thirdly, in the next payment period, the trusted subsystem judges that the states of the two target payment objects are both payment, and generates a payment plan for each target payment object, and the remaining payment period numbers of the two target payment objects are respectively as follows: b, stage 0; c, stage 97.
The trusted subsystem judges that the remaining payment period number of the employee B is less than 5, sends a first payment instruction carrying the identification number of the employee B to the account management system, acquires a pending payment parameter of the employee B, carries the pending payment parameter in a second payment instruction and sends the second payment instruction to the trusted subsystem; the escrow subsystem performs a payment operation in accordance with the second payment instruction.
And after detecting that the payment operation to be met is completed, the entrusted subsystem determines that the remaining payment period number of the employee B is zero and the account state is the payment state, and performs account cancellation on the employee B.
Meanwhile, the trusted subsystem judges that the remaining payment period number of the employee C is larger than 5, and if the account balance of the employee C obtained through the account and management system is larger than zero, the trusted subsystem executes payment operation on the employee C.
The remaining number of payment periods for employee C is 97 periods and the next payment period is entered.
And fourthly, in the next payment period, the trusted subsystem judges that the state of the employee C is payment, generates a payment plan for the employee C, and then subtracts 1 from the remaining payment period number of the employee C.
And the trusted subsystem judges that the remaining payment period number of the employee C is more than 5, acquires that the account balance of the employee C is more than zero through the account management system, and executes payment operation on the employee C.
And circularly carrying out the fourth step until a certain payment period, judging that the account balance of the employee C is less than or equal to zero, and carrying out account cancellation on the employee C.
In the embodiment of the invention, the trusted subsystem is used for receiving payment application operation of a user and acquiring a target payment plan of a target payment object in the payment application operation; executing a user canceling operation on the target payment object when the number of the target payment plans is judged to be lower than a preset plan threshold value and the payment waiting operation is completed, the remaining payment period number of the target payment object is zero and the account state is a preset state; or if the number of the target payment plans is greater than or equal to a preset plan threshold value, executing a user-canceling operation on the target payment object when the account balance is judged to be lower than the preset balance threshold value and the account state is a preset state; when the target payment object is detected to meet the account-cancelling condition, automatically cancelling the account, and avoiding the target object still generating a garbage payment plan and occupying a system memory; meanwhile, the entrusted subsystem automatically sells the user, so that the manual operation cost is saved. The embodiment of the invention solves the problem of limitation of manual account cancellation in the process of payment pending in the prior art.
Having described the exemplary embodiment of the invention, a method for customer-side payment is described with reference to the accompanying drawings.
Referring to fig. 4, an embodiment of the present invention provides an encounter payment method, which is applied to a trusted subsystem of an encounter payment system in the foregoing embodiment, and in conjunction with fig. 1, the encounter payment system includes: a trusted subsystem and an account management system; in the embodiment of the present invention, the example that the encounter payment system is used for paying the annual fee of the enterprise is taken, and it can be understood that the encounter payment system can also be used for paying other services.
The enterprise annuity is used as an endowment guarantee product, the enterprise annuity refers to a supplementary endowment fund service which is established by the enterprise according to the economic strength and the economic condition of the enterprise besides the compulsory endowment fund, and the enterprise annuity is a supplementary endowment fund system and aims to provide retirement income guarantee to a certain degree for the enterprise staff.
Specifically, the endowment insurance product takes an endowment insurance company as a consignee, receives the consignment of the consignee, and provides endowment insurance and fund management services related to the endowment insurance for the consignee, wherein the service items comprise scheme design, consignee management, account management, investment management, treatment payment, compensation delay, welfare plan, reservation incentive and the like.
Further, the encounter payment refers to a process of making payment for employees (i.e., payment objects) participating in the annuity plan according to the provision of annuities. For the payment objects meeting the payment application conditions, the selectable payment modes are one-time payment and staged payment, and the staged payment is divided into quota payment and periodic payment. One payment per payment period.
As a first example, referring to fig. 2, in the process of payment for a treatment, the enterprise serves as a trustee, and the trustee is entrusted to pay the relevant treatment for the payment object; the consignee is a legal person consignment organization which is entrusted by the consignor and manages the annual fund of the enterprise; the account managing party is a mechanism for receiving the entrusted party entrusts, managing the annual fund account of the enterprise and carrying out accounting.
The method comprises the following steps:
The user is a client, usually an enterprise; the entrustment sends a payment application operation to the entrusted subsystem, and the payment application operation carries an identification number of a target payment object, and each payment object can only apply for one payment usually; after receiving the payment application operation, the trusted subsystem acquires a payment plan according to the identification number of the target payment object; the payment plan is a target payment plan for the target payment object.
In the current payment period, the target payment plan may have two types, one generated in the current payment period, and the other payment plan, i.e., the remaining unpaid payment plan in the historical payment period.
And after acquiring all target payment plans aiming at the target payment object, the entrusted subsystem judges the numerical relationship between the number of the target payment plans and a preset threshold value, and executes different operations according to different numerical relationships. The preset threshold is the highest threshold of the unpaid payment plan that can be persisted.
Specifically, the operations performed by the trusted subsystem are divided into two cases, step 402 or step 403, depending on the number of target payment plans.
And if the number of the target payment plans is lower than a preset plan threshold value, indicating that the number of the remaining target payment plans is normal and can execute the treatment payment operation, wherein the treatment payment operation is a treatment related to the target payment object.
After the pending payment operation of the current payment period is finished, when the trusted subsystem detects that the remaining payment period number of the target payment object is zero and the account state is a preset state, the trusted subsystem automatically executes a user canceling operation on the target payment object; specifically, the account status may include payment, payment or sale, etc.; the preset state may be set as a payment state, and the payment state indicates that the enterprise has started a payment process for the current account.
The remaining payment period number is the payment period number of the target object recorded by the trusted subsystem; the residual payment period is the difference between the initial period and the current payment period; for one-time payment, the initial period number of the payment object is 0, and for regular payment, the payment object is preset with the value of the initial period number; for a quota payment, the initial number of sessions is preset to an initial number of sessions, which is typically set to a larger number, such as 99.
Therefore, for the payment object with the payment type of one-time payment or regular payment, after the trusted subsystem finishes the payment operation on the payment object in a certain payment period, the remaining payment period number of the trusted subsystem is detected to be zero and the account state is the payment state, and the trusted subsystem automatically performs account cancellation on the payment object, so that the situation that useless garbage payment plans are generated for the target payment object subsequently and the system memory is occupied is avoided.
The entrusted subsystem executes a user canceling operation on the target payment object when the account balance is judged to be lower than a preset balance threshold value and the account state is a preset state; optionally, the preset balance threshold is a lowest threshold for paying a treatment to the target payment object; when the account state of the target payment object is a preset state and the account balance is not enough to pay once below a preset balance threshold, and the number of the remaining payment plans is large, the target payment plan is an invalid payment plan, and the entrusted subsystem automatically sells the target payment plan to avoid generating useless garbage payment plans aiming at the target payment object subsequently.
For a payment object that pays in a fixed amount, the trusted system typically presets its payment period number to a larger value, such as 99 days; thus, when the number of the target payment plans is judged to be large, the account balance needs to be checked; if the account balance is not enough to pay once again when being lower than the preset balance threshold value, the target payment plan is an invalid plan, and the trusted subsystem automatically sells the account.
In addition, in step 403, if the trusted subsystem determines that the account balance is not lower than the preset balance threshold, an abnormal prompt message is sent to prompt that an account of the target payment object may have an abnormal condition.
Optionally, in this embodiment of the present invention, the step of determining the account balance of the target payment object includes:
sending a first acquisition operation carrying the identification number of the target payment object to the account management system;
and receiving the account balance of the target payment object sent by the account management system, wherein the account balance is determined by the account management system according to the identification number.
Optionally, in this embodiment of the present invention, the encounter payment system further includes: a hosting subsystem;
the step of performing a pending payment operation includes:
sending a first payment instruction carrying the identification number to the account management system, and receiving a pending payment parameter fed back by the account management system;
and sending a second payment instruction carrying the treatment payment parameter and the identification number to the hosting subsystem, wherein the second payment instruction is used for instructing the hosting subsystem to pay for treatment to the target payment object according to the second payment instruction.
In the embodiment of the invention, a payment application operation of a user is received, and a target payment plan of a target payment object in the payment application operation is obtained; executing a user canceling operation on the target payment object when the number of the target payment plans is judged to be lower than a preset plan threshold value and the payment waiting operation is completed, the remaining payment period number of the target payment object is zero and the account state is a preset state; or if the number of the target payment plans is greater than or equal to a preset plan threshold value, executing a user-canceling operation on the target payment object when the account balance is judged to be lower than the preset balance threshold value and the account state is a preset state; when the target payment object is detected to meet the account-cancelling condition, automatically cancelling the account, and avoiding the target object still generating a garbage payment plan and occupying a system memory; meanwhile, the entrusted subsystem automatically sells the user, so that the manual operation cost is saved. The embodiment of the invention solves the problem of limitation of manual account cancellation in the process of payment pending in the prior art.
With the foregoing description of the method for payment for handling service provided by the embodiment of the present invention, a device for payment for handling service provided by the embodiment of the present invention will be described with reference to the accompanying drawings.
Referring to fig. 5, an embodiment of the present invention further provides an apparatus for handling payment, which is applied to a trusted subsystem of a handling payment system in the above embodiment, where the apparatus includes:
an operation receiving module 501, configured to receive a payment application operation of a user, and obtain a target payment plan of a target payment object in the payment application operation, where the target payment plan includes a plan generated in a current payment cycle and/or a plan remaining in a historical payment cycle;
a first account cancellation module 502, configured to execute a pending payment operation if the number of the target payment plans is lower than a preset threshold, and execute an account cancellation operation on the target payment object when the remaining payment period number of the target payment object is zero and the account status is in a preset status after the completion of the pending payment operation is detected;
or
The second account cancelling module 503 is configured to determine an account balance of the target payment object if the number of the target payment plans is greater than or equal to a preset plan threshold, and perform a cancelling operation on the target payment object when it is determined that the account balance is lower than the preset balance threshold and an account status is a preset status.
Optionally, in this embodiment of the present invention, the second customer cancellation module 503 includes:
the first sending submodule is used for sending a first obtaining operation carrying the identification number of the target payment object to the account management system;
and the first receiving submodule is used for receiving the account balance of the target payment object sent by the account management system, wherein the account balance is determined by the account management system according to the identification number.
Optionally, in this embodiment of the present invention, the encounter payment system further includes: a hosting subsystem;
the first sales module 502 includes:
the parameter processing submodule is used for sending a first payment instruction carrying the identification number to the account pipe system and receiving a to-be-encountered payment parameter fed back by the account pipe system;
and the payment instruction submodule is used for sending a second payment instruction carrying the treatment payment parameter and the identification number to the hosting subsystem, and the second payment instruction is used for instructing the hosting subsystem to pay the treatment to the target payment object according to the second payment instruction.
The handling payment device provided in the embodiment of the present invention can implement each process implemented by the trusted subsystem of the handling payment in the embodiments of fig. 1 to fig. 4, and is not described herein again to avoid repetition.
In the embodiment of the present invention, the operation receiving module 501 receives a payment application operation of a user, and obtains a target payment plan of a target payment object in the payment application operation; the first subscriber module 502 executes subscriber operation on the target payment object when the number of the target payment plans is judged to be lower than a preset plan threshold value, and after the payment operation is completed, the remaining payment period number of the target payment object is zero and the account state is a preset state; if the number of the target payment plans is greater than or equal to a preset plan threshold value, the second account cancelling module 503 executes an account cancelling operation on the target payment object when the account balance is judged to be lower than the preset balance threshold value and the account state is a preset state; when the target payment object is detected to meet the account-cancelling condition, automatically cancelling the account, and avoiding the target object still generating a garbage payment plan and occupying a system memory; meanwhile, the entrusted subsystem automatically sells the user, so that the manual operation cost is saved. The embodiment of the invention solves the problem of limitation of manual account cancellation in the process of payment pending in the prior art.
In another aspect, an embodiment of the present invention further provides an electronic device, which includes a memory, a processor, a bus, and a computer program stored in the memory and executable on the processor, where the processor executes the computer program to implement the steps in the above-mentioned pending payment method.
For example, fig. 6 shows a schematic physical structure diagram of an electronic device.
As shown in fig. 6, the electronic device may include: a processor (processor)610, a communication Interface (Communications Interface)620, a memory (memory)630 and a communication bus 640, wherein the processor 610, the communication Interface 620 and the memory 630 communicate with each other via the communication bus 640. The processor 610 may call logic instructions in the memory 630 to perform the following method:
receiving a taxi taking application sent by a client, and acquiring a user level of a target object aimed at by the taxi taking application; the taxi taking application at least comprises a taxi taking parameter and a path parameter;
determining a preset taxi taking rule corresponding to the user level, wherein the preset taxi taking rule at least comprises available taxi taking parameters and path parameters of the target object;
and checking the taxi taking application according to the preset taxi taking rule.
Or
Receiving a vehicle using parameter and a path parameter of a user, carrying the vehicle using parameter and the path parameter in a vehicle driving application, and sending the vehicle using parameter and the path parameter to the server;
receiving an audit result of the taxi taking application from the server according to a preset taxi taking rule; the preset taxi taking rule at least comprises a taxi taking parameter and a path parameter which are available for the target object, and the preset taxi taking rule is determined by the server according to the user level of the user.
In addition, the logic instructions in the memory 630 may be implemented in software functional units and stored in a computer readable storage medium when the logic instructions are sold or used as independent products. Based on such understanding, the technical solution of the present invention may be embodied in the form of a software product, which is stored in a storage medium and includes instructions for causing a computer device (which may be a personal computer, a server, or a network device) to execute all or part of the steps of the method according to the embodiments of the present invention. And the aforementioned storage medium includes: a U-disk, a removable hard disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk or an optical disk, and other various media capable of storing program codes.
In still another aspect, an embodiment of the present invention further provides a computer-readable storage medium, on which a computer program is stored, where the computer program is implemented to, when executed by a processor, perform a method for payment on treatment provided by the foregoing embodiments, for example, including:
receiving a taxi taking application sent by a client, and acquiring a user level of a target object aimed at by the taxi taking application; the taxi taking application at least comprises a taxi taking parameter and a path parameter;
determining a preset taxi taking rule corresponding to the user level, wherein the preset taxi taking rule at least comprises available taxi taking parameters and path parameters of the target object;
and checking the taxi taking application according to the preset taxi taking rule.
Or
Receiving a vehicle using parameter and a path parameter of a user, carrying the vehicle using parameter and the path parameter in a vehicle driving application, and sending the vehicle using parameter and the path parameter to the server;
receiving an audit result of the taxi taking application from the server according to a preset taxi taking rule; the preset taxi taking rule at least comprises a taxi taking parameter and a path parameter which are available for the target object, and the preset taxi taking rule is determined by the server according to the user level of the user.
The above-described embodiments of the apparatus are merely illustrative, and the units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the modules may be selected according to actual needs to achieve the purpose of the solution of the present embodiment. One of ordinary skill in the art can understand and implement it without inventive effort.
Through the above description of the embodiments, those skilled in the art will clearly understand that each embodiment can be implemented by software plus a necessary general hardware platform, and certainly can also be implemented by hardware. With this understanding in mind, the above-described technical solutions may be embodied in the form of a software product, which can be stored in a computer-readable storage medium such as ROM/RAM, magnetic disk, optical disk, etc., and includes instructions for causing a computer device (which may be a personal computer, a server, or a network device, etc.) to execute the methods described in the embodiments or some parts of the embodiments.
Finally, it should be noted that: the above examples are only intended to illustrate the technical solution of the present invention, but not to limit it; although the present invention has been described in detail with reference to the foregoing embodiments, it will be understood by those of ordinary skill in the art that: the technical solutions described in the foregoing embodiments may still be modified, or some technical features may be equivalently replaced; and such modifications or substitutions do not depart from the spirit and scope of the corresponding technical solutions of the embodiments of the present invention.
Claims (10)
1. A encounter payment system, comprising: a trusted subsystem and an account management system;
the trusted subsystem is used for receiving payment application operation of a user and acquiring a target payment plan of a target payment object in the payment application operation, wherein the target payment plan comprises a plan generated in a current payment cycle and/or a plan remaining in a historical payment cycle;
if the number of the target payment plans is lower than a preset plan threshold value, executing a pending payment operation, and executing a subscriber cancellation operation on the target payment object when the remaining payment period number of the target payment object is zero and the account state is a preset state after the pending payment operation is detected to be completed;
or
If the number of the target payment plans is larger than or equal to a preset plan threshold value, sending a first obtaining operation carrying the identification number of the target payment object to the account management system;
the account management system is used for determining the account balance of the target payment object according to the identification number and sending the account balance to the trusted subsystem;
and the entrusted subsystem executes a user canceling operation on the target payment object when the account balance is judged to be lower than a preset balance threshold value and the account state is a preset state.
2. The encounter payment system of claim 1, further comprising: a hosting subsystem;
the trusted subsystem performs a pending payment operation comprising: sending a first payment instruction carrying the identification number to the account management system, and receiving a pending payment parameter fed back by the account management system;
and sending a second payment instruction carrying the payment-to-be-encountered parameter and the identification number to the hosting subsystem.
3. The encounter payment system of claim 2, wherein the account pipe system is further configured to: and receiving the first payment instruction, determining a pending payment parameter of the target payment object according to the identification number, and feeding back the pending payment parameter to the trusted subsystem.
4. The encounter payment system of claim 2, wherein the escrow subsystem is configured to: and receiving the second payment instruction, and paying the treatment to the target payment object according to the second payment instruction.
5. An acceptance payment method applied to the acceptance subsystem of the acceptance payment system according to any one of claims 1 to 4, the method comprising:
receiving payment application operation of a user, and acquiring a target payment plan of a target payment object in the payment application operation, wherein the target payment plan comprises a plan generated in a current payment period and/or a plan remaining in a historical payment period;
if the number of the target payment plans is lower than a preset threshold value, executing a pending payment operation, and executing a user canceling operation on the target payment object when the remaining payment period number of the target payment object is zero and the account state is a preset state after the pending payment operation is detected to be completed;
or
If the number of the target payment plans is larger than or equal to a preset plan threshold value, determining the account balance of the target payment object, and executing a subscriber sales operation on the target payment object when the account balance is judged to be lower than the preset balance threshold value and the account state is a preset state.
6. The encounter payment method of claim 5, wherein the step of determining the account balance of the target payment object comprises:
sending a first acquisition operation carrying the identification number of the target payment object to the account management system;
and receiving the account balance of the target payment object sent by the account management system, wherein the account balance is determined by the account management system according to the identification number.
7. The encounter payment method of claim 5, wherein the encounter payment system further comprises: a hosting subsystem;
the step of performing a pending payment operation includes:
sending a first payment instruction carrying the identification number to the account management system, and receiving a pending payment parameter fed back by the account management system;
and sending a second payment instruction carrying the treatment payment parameter and the identification number to the hosting subsystem, wherein the second payment instruction is used for instructing the hosting subsystem to pay for treatment to the target payment object according to the second payment instruction.
8. An acceptance payment apparatus applied to the acceptance subsystem of the acceptance payment system according to any one of claims 1 to 4, the apparatus comprising:
the operation receiving module is used for receiving payment application operation of a user and acquiring a target payment plan of a target payment object in the payment application operation, wherein the target payment plan comprises a plan generated in a current payment period and/or a plan remaining in a historical payment period;
the first account cancellation module is used for executing an account cancellation operation on the target payment object if the number of the target payment plans is lower than a preset threshold value, and when the fact that the payment operation is finished and the remaining payment period number of the target payment object is zero and the account state is in a preset state is detected;
or
And the second account cancelling module is used for determining the account balance of the target payment object if the number of the target payment plans is greater than or equal to a preset plan threshold value, and executing cancelling operation on the target payment object when the account balance is judged to be lower than the preset balance threshold value and the account state is in a preset state.
9. An electronic device comprising a processor, a memory and a computer program stored on the memory and executable on the processor, characterized in that the computer program, when executed by the processor, carries out the steps of the method of pending payment according to any one of claims 5 to 7.
10. A computer-readable storage medium, on which a computer program is stored which, when being executed by a processor, carries out the steps of the method of payment to encounter of any of claims 5 to 7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010450871.9A CN111681117B (en) | 2020-05-25 | 2020-05-25 | System, method and device for payment treatment |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010450871.9A CN111681117B (en) | 2020-05-25 | 2020-05-25 | System, method and device for payment treatment |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN111681117A true CN111681117A (en) | 2020-09-18 |
| CN111681117B CN111681117B (en) | 2023-09-12 |
Family
ID=72453565
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010450871.9A Active CN111681117B (en) | 2020-05-25 | 2020-05-25 | System, method and device for payment treatment |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111681117B (en) |
Citations (14)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2002099602A2 (en) * | 2001-06-06 | 2002-12-12 | Koresko V John J | A system and method for creating a defined benefit pension plan |
| CN1564211A (en) * | 2004-04-01 | 2005-01-12 | 周静 | Financial account having target account and its management system |
| US20070033124A1 (en) * | 2005-07-19 | 2007-02-08 | Herr Daniel P | Method and system for providing employer-sponsored retirement plan |
| TW200739441A (en) * | 2006-04-03 | 2007-10-16 | Shacom Com Inc | Method for conducting online financial transaction using competitive bidding mechanism for private mutual fund in segmentation type |
| CN101551893A (en) * | 2008-03-31 | 2009-10-07 | 乔美国际网路股份有限公司 | Annuity agreement system and method executed by annuity agreement system |
| US20120136752A1 (en) * | 2003-08-04 | 2012-05-31 | Vikas Gupta | Payment service that applies user-specified rules to divide payment amounts among multiple payment instruments |
| CN106296396A (en) * | 2016-08-18 | 2017-01-04 | 深圳前海微众银行股份有限公司 | The life cycle management method of finishing loan and device |
| CN106296201A (en) * | 2016-08-15 | 2017-01-04 | 广州地理研究所 | Bus Card equipment off-line credit payment verification method |
| CN106952156A (en) * | 2017-03-08 | 2017-07-14 | 中国银行股份有限公司 | The generation method and device of a kind of installment reimbursement plan |
| CN108122099A (en) * | 2017-12-08 | 2018-06-05 | 平安科技（深圳）有限公司 | Method, apparatus, storage medium and the terminal of produce clearing |
| CN108510397A (en) * | 2017-07-25 | 2018-09-07 | 平安科技（深圳）有限公司 | Annuity manages system, method, server and storage medium |
| CN109035043A (en) * | 2018-08-13 | 2018-12-18 | 中国建设银行股份有限公司 | A kind of supplementary pension payment system and method |
| CN109118373A (en) * | 2017-06-26 | 2019-01-01 | 平安科技（深圳）有限公司 | Supplementary pension method of commerce, device and computer readable storage medium |
| CN109255696A (en) * | 2018-07-28 | 2019-01-22 | 重庆小雨点小额贷款有限公司 | A kind of refund data determination method, device, server and computer storage medium |
-
2020
- 2020-05-25 CN CN202010450871.9A patent/CN111681117B/en active Active
Patent Citations (14)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2002099602A2 (en) * | 2001-06-06 | 2002-12-12 | Koresko V John J | A system and method for creating a defined benefit pension plan |
| US20120136752A1 (en) * | 2003-08-04 | 2012-05-31 | Vikas Gupta | Payment service that applies user-specified rules to divide payment amounts among multiple payment instruments |
| CN1564211A (en) * | 2004-04-01 | 2005-01-12 | 周静 | Financial account having target account and its management system |
| US20070033124A1 (en) * | 2005-07-19 | 2007-02-08 | Herr Daniel P | Method and system for providing employer-sponsored retirement plan |
| TW200739441A (en) * | 2006-04-03 | 2007-10-16 | Shacom Com Inc | Method for conducting online financial transaction using competitive bidding mechanism for private mutual fund in segmentation type |
| CN101551893A (en) * | 2008-03-31 | 2009-10-07 | 乔美国际网路股份有限公司 | Annuity agreement system and method executed by annuity agreement system |
| CN106296201A (en) * | 2016-08-15 | 2017-01-04 | 广州地理研究所 | Bus Card equipment off-line credit payment verification method |
| CN106296396A (en) * | 2016-08-18 | 2017-01-04 | 深圳前海微众银行股份有限公司 | The life cycle management method of finishing loan and device |
| CN106952156A (en) * | 2017-03-08 | 2017-07-14 | 中国银行股份有限公司 | The generation method and device of a kind of installment reimbursement plan |
| CN109118373A (en) * | 2017-06-26 | 2019-01-01 | 平安科技（深圳）有限公司 | Supplementary pension method of commerce, device and computer readable storage medium |
| CN108510397A (en) * | 2017-07-25 | 2018-09-07 | 平安科技（深圳）有限公司 | Annuity manages system, method, server and storage medium |
| CN108122099A (en) * | 2017-12-08 | 2018-06-05 | 平安科技（深圳）有限公司 | Method, apparatus, storage medium and the terminal of produce clearing |
| CN109255696A (en) * | 2018-07-28 | 2019-01-22 | 重庆小雨点小额贷款有限公司 | A kind of refund data determination method, device, server and computer storage medium |
| CN109035043A (en) * | 2018-08-13 | 2018-12-18 | 中国建设银行股份有限公司 | A kind of supplementary pension payment system and method |
Also Published As
| Publication number | Publication date |
|---|---|
| CN111681117B (en) | 2023-09-12 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US20010041993A1 (en) | Automated claim processing and attorney referral and selection | |
| US20190139049A1 (en) | Order Information Processing Methods, Apparatuses and Systems | |
| JP2006244492A (en) | System and method for determining vehicle salvage value | |
| US20090299784A1 (en) | Method, system and computer program for furnishing information to customer representatives | |
| CN108805691B (en) | Loan auditing method based on block chain and related equipment | |
| AU2009242481A1 (en) | System and method for benefit conversion | |
| US20160098803A1 (en) | Title document rules engine method and apparatus | |
| US20210125285A1 (en) | Method, device, storage medium and terminal for modifying account name | |
| US8737585B1 (en) | Systems and methods for treatment of inactive accounts | |
| CN112200673A (en) | Method, device and equipment for cashless bank right and readable storage medium | |
| CN114493843A (en) | Business approval method and device, electronic equipment and computer readable medium | |
| US10708384B2 (en) | Data processing method and system | |
| CN108038667B (en) | Policy generation method, device and equipment | |
| CN110362541A (en) | Document generating method, device, computer installation and storage medium | |
| US8478666B2 (en) | System and method for processing data related to management of financial assets | |
| CN111681117A (en) | System, method and device for payment in treatment | |
| US20230289692A1 (en) | Risk management system interface | |
| US20070112634A1 (en) | System and method for confirming customer transactions | |
| CN111798322A (en) | Data processing method and device for bank financing product | |
| CN110858348A (en) | Logistics information processing method and device | |
| CN112231634A (en) | Credit limit calculation method, system and equipment based on enterprise information | |
| CN111429248A (en) | Order issuing method and device for non-real-time insurance service | |
| CA3115343A1 (en) | Computer-implemented method of managing an insurance claim | |
| CN110246022B (en) | Financial management system and method | |
| JP2009123017A (en) | Automatic examination system |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |