WO2019196257A1 - 一种自动还款方法、***及终端设备 - Google Patents

一种自动还款方法、***及终端设备 Download PDF

Info

Publication number
WO2019196257A1
WO2019196257A1 PCT/CN2018/097529 CN2018097529W WO2019196257A1 WO 2019196257 A1 WO2019196257 A1 WO 2019196257A1 CN 2018097529 W CN2018097529 W CN 2018097529W WO 2019196257 A1 WO2019196257 A1 WO 2019196257A1
Authority
WO
WIPO (PCT)
Prior art keywords
repayment
amount
deduction operation
less
repayment amount
Prior art date
Application number
PCT/CN2018/097529
Other languages
English (en)
French (fr)
Inventor
陈文博
Original Assignee
平安科技(深圳)有限公司
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by 平安科技(深圳)有限公司 filed Critical 平安科技(深圳)有限公司
Publication of WO2019196257A1 publication Critical patent/WO2019196257A1/zh

Links

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06QINFORMATION 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
    • G06Q20/00Payment architectures, schemes or protocols
    • G06Q20/22Payment schemes or models
    • G06Q20/24Credit schemes, i.e. "pay after"
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06QINFORMATION 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
    • G06Q20/00Payment architectures, schemes or protocols
    • G06Q20/08Payment architectures
    • G06Q20/10Payment architectures specially adapted for electronic funds transfer [EFT] systems; specially adapted for home banking systems
    • G06Q20/102Bill distribution or payments
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06QINFORMATION 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
    • G06Q20/00Payment architectures, schemes or protocols
    • G06Q20/08Payment architectures
    • G06Q20/10Payment architectures specially adapted for electronic funds transfer [EFT] systems; specially adapted for home banking systems
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06QINFORMATION 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/00Finance; Insurance; Tax strategies; Processing of corporate or income taxes
    • G06Q40/02Banking, e.g. interest calculation or account maintenance
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06QINFORMATION 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/00Finance; Insurance; Tax strategies; Processing of corporate or income taxes
    • G06Q40/03Credit; Loans; Processing thereof

Definitions

  • the present application belongs to the field of electronic financial technologies, and in particular, to an automatic repayment method, system and terminal device.
  • the credit card repayment platform or other lending platform in the prior art cannot directly read the balance of the user's bank card.
  • the prior art usually uses a one-time deduction to deduct money. That is, how much the user owes money, and directly deducts the associated bank card according to the total amount owed. Once the balance in the bank card is less than the total amount owed by the user, the user's repayment failure will occur, resulting in the user appearing. Bad records of overdue payments will also generate more interest and require subsequent repayment by the user.
  • multiple different loans may be associated with the same bank card for repayment, such as a repayment bank card that will borrow money from the credit card, the loan app, and the wallet itself.
  • the user may need to make multiple repayments for the bank card within one month, and the existing debit method often only follows the rule of repayment time priority, which borrowing first arrives at the repayment time. Which one is directly paid first, and all of them are debited by the above-mentioned one-time deduction, so that the management efficiency of the user's repayment is low, and the balance in the user's bank card cannot be used for the user. Carry out intelligent repayments.
  • the existing automatic repayment method has the problem that the degree of intelligence is low and the automatic repayment cannot be performed in the case where the balance of the user's bank card is insufficient.
  • the embodiment of the present application provides an automatic repayment method, system, and terminal device, so as to solve the problem that the existing automatic repayment method has a low degree of intelligence, and cannot automatically repay the balance of the user's bank card.
  • the problem
  • a first aspect of the present application provides an automatic repayment method comprising:
  • the dichotomy method is used to re-determine the repayment amount corresponding to the deduction operation and the deduction operation is performed again, and the repayment amount is less than the preset amount threshold, and the automatic repayment process is ended.
  • the automatic repayment method, system and terminal device provided by the application provide repayment according to the priority and the minimum repayment amount by determining the priority of each repayment amount, and the balance of the user repayment account is insufficient to pay off the repayment
  • the dichotomy method is used to re-determine the repayment amount and the deduction operation is performed again, and the delinquency of the user’s arrears and the balance of the account to which the repayment is due is reasonably and effectively deducted.
  • the use of the balance of the account for repayment to minimize the adverse effects caused by overdue repayment of users, effectively solve the problem that the existing automatic repayment method is low in intelligence and cannot be insufficient in the balance of the user's bank card. Under the issue of automatic repayment.
  • FIG. 1 is a schematic flowchart of an implementation method of an automatic repayment method according to Embodiment 1 of the present application;
  • step S101 is a schematic flowchart of an implementation process of step S101 corresponding to the first embodiment provided by the second embodiment of the present application;
  • step S104 is a schematic flowchart of an implementation process of step S104 corresponding to the first embodiment provided by the third embodiment of the present application;
  • step S104 is a schematic flowchart of an implementation process of step S104 corresponding to the first embodiment provided in Embodiment 4 of the present application;
  • FIG. 5 is a schematic structural diagram of an automatic repayment system according to Embodiment 5 of the present application.
  • FIG. 6 is a schematic structural diagram of a priority determining module 101 in a corresponding embodiment 5 according to Embodiment 6 of the present application;
  • FIG. 7 is a schematic structural diagram of a dichotomy deduction module 104 corresponding to the fifth embodiment provided in Embodiment 7 of the present application;
  • FIG. 8 is a schematic structural diagram of a dichotomy deduction module 104 according to Embodiment 5 of Embodiment 8 of the present application;
  • FIG. 9 is a schematic diagram of a terminal device provided in Embodiment 9 of the present application.
  • Embodiment 1 is a diagrammatic representation of Embodiment 1:
  • this embodiment provides an automatic repayment method, which specifically includes:
  • Step S101 Determine the priority of each of the to-be-paid funds according to the degree of association between the payment to be repaid and the credit information system and the daily overdue interest of the payment.
  • not all borrowing channels are related to the credit information system.
  • most corporate lending platforms only calculate the repayment amount and daily overdue interest of the repayment, but not with the credit system. Association. Therefore, it is necessary to judge whether the respective payments to be repaid are related to the credit information system. Since the repayment of the repayments associated with the credit information system will directly affect the credit of the user, in order to minimize the impact on the credit of the user when the account balance is insufficient to pay off all the arrears, the priority is The repayments associated with the credit information system are repaid.
  • the overdue interest rates specified by different borrowing channels are different.
  • a credit card is calculated as a daily overdue interest rate with a five-thousandth of a million overdue interest rate.
  • the corporate lending platform calculates the daily rate based on the overdue interest rate of five thousandths.
  • Overdue interest Since the amount of each payment to be repaid is also different, the daily overdue interest for each repayment is also different.
  • the daily overdue interest for each repayment is equal to the amount of the repayment.
  • the amount to be repaid is multiplied by the overdue interest rate.
  • the priority of the outstanding payment is determined, and the priority of the pending payment associated with the credit information system is higher than the unpaid amount associated with the credit information system.
  • Priority is given to further determine the priority of each pending payment based on the daily overdue interest of the outstanding payment.
  • the priority of the daily overdue interest is higher than the priority of the daily overdue interest.
  • the repayment amount 1 is the repayment amount associated with the credit information system, and the daily overdue interest is 2 yuan; the repayment amount 2 is also the repayment amount related to the credit information system, and the overdue interest for each period is 1 Yuan; the repayment amount 3 is not related to the credit information system, and its daily overdue interest is 2 yuan; the repayment amount 4 is not associated with the credit information system, and its daily overdue interest is 3 yuan, then the priority of the repayment amount 1 The degree is higher than the priority of the payment 2, the priority of the payment 2 is higher than the priority of the payment 3, and the priority of the payment 3 is greater than the priority of the payment 4.
  • Step S102 Read the minimum repayment amount of each of the to-be-paid amounts.
  • the minimum repayment amount refers to the minimum repayment amount when the repayment amount does not affect the credit of the user or does not generate overdue interest during the current repayment operation.
  • the credit investigation is conducted through the credit database, and the minimum repayment amount of each payment is set according to the credit degree of the user.
  • the credit degree database is used to find the credit degree of the user on each lending platform, and the minimum repayment amount of each repayment amount is set for the credit degree of different lending platforms. The higher the credit setting, the lower the minimum repayment amount, and the lower the credit setting, the higher the minimum repayment amount.
  • the minimum repayment amount of the above-mentioned payment can also be set by each lending platform according to the amount of each payment to be repaid.
  • Step S103 According to the repayment priority, the minimum repayment amount corresponding to each of the to-be-repaid amounts is sequentially deducted in the account to which the to-be-paid amount belongs, and the deduction is detected after each deduction operation is performed. Whether the operation was successful.
  • the balance of the account is not enough to deduct the total amount of all the repayments to be repaid, first read the minimum repayment amount of each repayment amount, and then deduct the respective deductions in the account to which the repayment is due according to the repayment priority.
  • the deduction operation is performed by issuing a debit request for deducting the minimum repayment amount corresponding to the to-be-paid amount to the account to which the payment is to be made.
  • the deduction operation it is detected whether the deduction operation is successful after each deduction operation is performed. If the balance of the account is greater than or equal to the minimum repayment amount corresponding to the pending payment, the deduction operation is successful. If the balance of the account is less than the minimum repayment amount corresponding to the pending payment, the deduction operation fails. Specifically, when the minimum repayment amount corresponding to the debit request is successfully deducted from the account, the deduction of the success signal is fed back, and it is detected whether the deduction operation succeeds, that is, whether there is a feedback deduction success signal, and if the deduction success signal is detected, it indicates This deduction operation is successful; otherwise, it indicates that the deduction operation failed.
  • Step S104 If it is detected that the current deduction operation fails, the dichotomy method is used to re-determine the repayment amount corresponding to the current deduction operation and the deduction operation is performed again until the repayment amount is less than the preset amount threshold, and the automatic repayment process is ended. .
  • the dichotomy method is used to re-determine the repayment amount corresponding to the deduction operation and perform the deduction operation again.
  • the amount of repayment determined by the dichotomy is specifically that half of the minimum repayment amount of the repayment amount is used as the repayment amount of the current deduction operation, and a deduction request for deducting the repayment amount is issued to the account to which it belongs.
  • the current deduction operation if the current deduction operation is successful, it indicates that the balance of the account is less than the minimum repayment amount of the to-be-paid amount and is greater than or equal to half of the minimum repayment amount of the repayment amount before the deduction operation. .
  • the amount of repayment corresponding to the next deduction operation is determined again by the dichotomy method, that is, the repayment amount corresponding to the next deduction operation is half of the repayment amount corresponding to the deduction operation (the minimum repayment amount of the repayment amount) 1/4), and reissue the debit of the repayment amount to the account to which it belongs.
  • the current deduction operation fails, it indicates that the balance of the account is less than half of the minimum repayment amount of the pending payment before the deduction operation, and the repayment amount corresponding to the next deduction operation is also determined by the dichotomy again. , that is, the amount of repayment corresponding to the next deduction operation is half of the repayment amount corresponding to the current deduction operation (a quarter of the minimum repayment amount of the repayment amount), and re-issued the deductible repayment to the account to which it belongs.
  • the automatic repayment process ends until the repayment amount is less than the preset amount threshold.
  • the dichotomy method is used to determine the repayment amount and the deduction operation is performed again, the balance of the account to which it belongs can be deducted indefinitely.
  • the preset amount threshold automatically ends the automatic repayment process when the repayment amount is less than the preset amount threshold.
  • the automatic repayment method further includes:
  • Step S105 After the automatic repayment process ends, generate a repayment status report and send it to the user end, wherein the repayment status report includes account information that has not successfully deducted the minimum repayment amount.
  • the repayment status of all the repayments is obtained, and the repayment status report is sent to the user end, and the repayment status report includes the account information that has not successfully deducted the minimum repayment amount.
  • the repayment report you can know the repayment of the repayments on the day, whether there are still outstanding payments for which the minimum repayment amount has not been successfully deducted, the amount of the repayments that have not been successfully deducted from the minimum repayment amount, and the repayment The amount of all the repayment amount of the repayment amount and the information of the next repayment period.
  • the repayment report can be sent to the terminal device of the associated account by SMS, or through the terminal device.
  • the relevant application in the query queries the repayment status report, which is not limited here.
  • step S101 before performing step S101, all the amounts to be repaid of all the to-be-paid money are read first, and a deduction request for deducting the total amount of the repayment amount is issued to the account to which it belongs.
  • the balance of the account is greater than or equal to the total amount to be repaid, that is, the repayment operation of all outstanding payments has been completed. If the deduction operation fails, the balance of the account is less than the total amount to be repaid, and step S101 is performed.
  • the deduction operation of deducting the minimum repayment amount corresponding to each repayment amount in the account to which the repayment amount belongs it indicates that the minimum repayment amount of all the repayments has been paid off.
  • the balance of the account to which the account belongs is predicted based on the historical repayment record, and the deduction operation is performed based on the predicted balance, and the balance of the account is utilized to maximize the repayment. That is, the deduction request of the predicted balance is deducted from the account to which the payment is to be made, and it is detected whether the current deduction operation is successful. If it is detected that the current deduction operation is unsuccessful, step S104 is performed.
  • the preset balance threshold is set, and when the account is deducted, the deduction amount is deducted.
  • the account will analyze whether the account balance is less than the preset balance threshold after deducting the repayment amount according to the repayment amount and account balance. If yes, no deduction will be made.
  • the account to which the payment is to be automatically added is automatically The minimum repayment amount corresponding to each pending payment is deducted in turn.
  • the automatic repayment method provided by the embodiment provides repayment according to the priority and the minimum repayment amount by determining the priority of each repayment amount, and the balance of the repayment account of the user is insufficient to pay off the minimum repayment of each repayment amount.
  • the dichotomy method is used to re-determine the repayment amount and the deduction operation is carried out again, and the delinquency of the user’s arrears and the balance of the account to which the payment is made is reasonably and effectively deducted, and the balance of the account can be utilized to the maximum extent.
  • Repayment to minimize the adverse effects caused by overdue repayment of users, effectively solve the problem that the existing automatic repayment method has low intelligence and cannot automatically repay the balance of the user's bank card. problem.
  • Embodiment 2 is a diagrammatic representation of Embodiment 1:
  • step S101 in the first embodiment specifically includes:
  • Step S201 sequentially determining whether each of the to-be-paid amounts is associated with the credit information system.
  • the repayment operation of the pending payment related to the credit information system can avoid the impact of overdue repayment on the credit of the user.
  • Step S202 If the to-be-repaid amount is associated with the credit information system, the to-be-paid amount is placed in the leader of the queue in the priority queue, and the office associated with the credit information system is associated with the daily overdue interest rate. The repayment amount is prioritized.
  • the pending payments are prioritized, and the pending payments associated with the credit reporting system are placed in the head of the priority queue, and then in accordance with each of the daily payments associated with the credit reporting system.
  • the amount of overdue interest is prioritized, and the amount of the outstanding overdue interest is placed before the daily overdue interest is low.
  • Step S203 If the to-be-repaid amount is not associated with the credit information system, the to-be-paid amount is placed at the end of the queue in the priority queue, and is not associated with the credit information system according to the daily overdue interest rate. The pending payments are prioritized.
  • the pending payment that is not associated with the credit system is placed at the end of the priority queue, and then according to the daily overdue interest of each pending payment that is not associated with the credit system.
  • the repayments are prioritized, and the daily repayments with high overdue interest are placed before the daily overdue interest is low.
  • the priority of the outstanding payment associated with the credit system and the daily overdue interest is higher than the priority of the outstanding payment associated with the credit system and the daily overdue interest.
  • the priority of the outstanding payment related to the credit information system and the daily overdue interest is higher than the priority of the outstanding payment that is not associated with the credit system and the daily overdue interest is not associated with the credit system.
  • the priority of the daily overdue interest is higher than the priority of the outstanding payment that is not associated with the credit system and the daily overdue interest is low.
  • the repayment amount 1 is the repayment amount associated with the credit information system, and the daily overdue interest is 2 yuan; the repayment amount 2 is also the repayment amount related to the credit information system, and the overdue interest for each period is 1 Yuan; the repayment amount 3 is not associated with the credit information system, and its daily overdue interest is 2 yuan; the repayment amount 4 is not associated with the credit information system, and its daily overdue interest is 3 yuan, then the priority queue is: Priority of Repayment 1 > Priority of Repayment 2 > Priority of Repayment 3 > Priority of Repayment 4.
  • Embodiment 3 is a diagrammatic representation of Embodiment 3
  • step S104 in the first embodiment specifically includes:
  • Step S301 Set the repayment amount corresponding to the current deduction operation to be 1/2 of the minimum repayment amount of the unpaid repayment amount.
  • the balance of the account to which the repayment is due is less than the minimum repayment amount of the unpaid repayment amount.
  • the repayment amount corresponding to the current deduction operation will be Set to 1/2 of the minimum repayment amount of the pending payment for the last deduction.
  • Step S302 Determine whether the repayment amount is less than the preset amount threshold.
  • the set repayment amount is less than the preset amount threshold.
  • the above-mentioned preset amount threshold refers to an amount (for example, 0.1 yuan) set in advance in order to avoid the deduction operation with meaning.
  • Step S303 If the repayment amount is less than the preset amount threshold, the automatic repayment process ends.
  • the repayment amount corresponding to the deduction operation is less than the preset amount threshold, it indicates that the balance of the account to which the repayment amount belongs is less than twice the threshold of the preset amount, and the deduction operation has no meaning at this time. At this point, the automatic repayment process ends.
  • Step S304 If the repayment amount is not less than the preset amount threshold, the deduction operation is performed according to the repayment amount, and the repayment amount corresponding to the next deduction operation is set as the repayment corresponding to the current deduction operation. 1/2 of the amount, and if the repayment amount corresponding to the next deduction operation is not less than the preset amount threshold, the deduction operation is performed again until the repayment amount is less than the preset amount threshold, and the end is Automatic repayment process.
  • the deduction request for deducting the repayment amount is issued to the account to which the repayment amount belongs, in order to make maximum use of the balance of the account to be repaid,
  • the repayment amount corresponding to the next deduction operation is set to 1/2 of the repayment amount corresponding to the deduction operation (ie, 1/4 of the minimum repayment amount of the repayment amount), and it is judged again whether the repayment amount is less than the prepayment amount.
  • the amount threshold is set, and the deduction operation is performed again if the repayment amount is not less than the preset amount threshold.
  • the balance of the account to which the repayment amount belongs is less than twice the threshold of the preset amount. At this time, the deduction operation is meaningless, so the automatic repayment process ends.
  • the repayment amount corresponding to the next deduction operation is set to 1/2 of the repayment amount corresponding to the current deduction operation. If the current deduction operation is successful, it indicates that the balance of the account is less than the minimum repayment amount of the to-be-paid amount and is greater than or equal to half of the minimum repayment amount of the repayment amount before the deduction operation. At this time, the amount of repayment corresponding to the next deduction operation is determined again by the dichotomy method, that is, the repayment amount corresponding to the next deduction operation is half of the repayment amount corresponding to the deduction operation (the minimum repayment amount of the repayment amount) 1/4), and reissue the debit of the repayment amount to the account to which it belongs.
  • the repayment amount corresponding to the next deduction operation is also determined by the dichotomy again. , that is, the amount of repayment corresponding to the next deduction operation is half of the repayment amount corresponding to the current deduction operation (a quarter of the minimum repayment amount of the repayment amount), and re-issued the deductible repayment to the account to which it belongs.
  • a deduction request for the amount is also determined by the dichotomy again. , that is, the amount of repayment corresponding to the next deduction operation is half of the repayment amount corresponding to the current deduction operation (a quarter of the minimum repayment amount of the repayment amount), and re-issued the deductible repayment to the account to which it belongs.
  • Embodiment 4 is a diagrammatic representation of Embodiment 4:
  • step S104 in the first embodiment specifically includes:
  • Step S401 The estimated account balance is obtained according to the historical repayment record prediction.
  • the account balance of the account may be estimated according to the historical repayment history of the account, and the account balance of the account per month is predicted by obtaining the automatic repayment record of the N months before the account.
  • the predicted account balance for each month is averaged, and the average is used as the estimated account balance, where N is an integer greater than one.
  • N is an integer greater than one.
  • the abnormal points in the obtained automatic repayment records of the first N months can be eliminated, and the prediction is performed based on the repayment records after the abnormal points are removed.
  • Step S402 Set the repayment amount corresponding to the current deduction operation to the estimated account balance.
  • the balance of the account to which the repayment is due is less than the minimum repayment amount of the unpaid repayment amount.
  • the repayment amount corresponding to the current deduction operation will be Set to estimate the account balance.
  • Step S403 Determine whether the repayment amount is less than the preset amount threshold.
  • the set repayment amount is less than the preset amount threshold.
  • the above-mentioned preset amount threshold refers to an amount (for example, 0.1 yuan) set in advance in order to avoid the deduction operation with meaning.
  • Step S404 If the repayment amount is less than the preset amount threshold, the automatic repayment process ends.
  • Step S405 If the repayment amount is not less than the preset amount threshold, the deduction operation is performed according to the repayment amount, and the repayment amount corresponding to the next deduction operation is set as the repayment corresponding to the current deduction operation. 1/2 of the amount, and if the repayment amount corresponding to the next deduction operation is not less than the preset amount threshold, the deduction operation is performed again until the repayment amount is less than the preset amount threshold, and the end is Automatic repayment process.
  • the deduction request for deducting the repayment amount is issued to the account to which the repayment amount belongs, in order to make maximum use of the balance of the account to be repaid,
  • the repayment amount corresponding to the next deduction operation is set to 1/2 of the repayment amount corresponding to the current deduction operation (that is, 1/4 of the estimated account balance), and it is determined again whether the repayment amount is less than the preset amount threshold.
  • the deduction operation is performed again if the repayment amount is not less than the preset amount threshold.
  • the balance of the account to which the repayment amount belongs is less than twice the threshold of the preset amount. At this time, the deduction operation is meaningless, so the automatic repayment process ends.
  • the repayment amount corresponding to the next deduction operation is set to 1/2 of the repayment amount corresponding to the current deduction operation. If the current deduction operation is successful, it indicates that the balance of the account is greater than or equal to the estimated account balance before the deduction operation. At this time, the amount of repayment corresponding to the next deduction operation is determined by the dichotomy method, that is, the repayment amount corresponding to the next deduction operation is half of the repayment amount corresponding to the deduction operation (1/2 of the estimated account balance) And reissue the debit request for deducting the repayment amount from the account to which it belongs.
  • the repayment amount corresponding to the next deduction operation is determined again by the dichotomy method, that is, the next deduction operation.
  • the corresponding repayment amount is half of the repayment amount corresponding to the deduction operation (1/2 of the estimated account balance), and the deduction request for deducting the repayment amount is reissued to the account to which it belongs.
  • Embodiment 5 is a diagrammatic representation of Embodiment 5:
  • the embodiment provides an automatic repayment system 100 for performing the method steps in the first embodiment, including: a priority determination module 101, a reading module 102, and a minimum repayment amount deduction module 103. And a dichotomy deduction module 104.
  • the priority determining module 101 is configured to determine the priority of each of the to-be-paid funds according to the degree of association between the payment to be repaid and the crediting system and the daily overdue interest of the to-be-paid amount.
  • the reading module 102 is configured to read the minimum repayment amount of each of the to-be-paid amounts.
  • the minimum repayment amount deduction module 103 is configured to sequentially deduct the minimum repayment amount corresponding to each of the to-be-paid amounts in the account to which the to-be-paid amount belongs according to the repayment priority, and perform each deduction operation After execution, check whether the deduction operation is successful.
  • the dichotomy deduction module 104 is configured to re-determine the repayment amount corresponding to the current deduction operation and perform the deduction operation again by using the dichotomy method if the current deduction operation fails, until the repayment amount is less than the preset amount threshold, and the end Automatic repayment process.
  • the above automatic repayment system further comprises: a report generation module.
  • the report generation module is configured to generate a repayment status report and send the report to the client after the automatic repayment process ends, wherein the repayment status report includes account information that has not successfully deducted the minimum repayment amount.
  • the automatic repayment system provided by the embodiment of the present application is based on the same concept as the method embodiment shown in FIG. 1 of the present application, and the technical effects thereof are the same as those of the method embodiment shown in FIG. 1 of the present application.
  • the content refer to the description in the method embodiment shown in FIG. 1 of the present application, and details are not described herein again.
  • the priority determining module 101 in the fifth embodiment includes a structure for performing the method steps in the embodiment corresponding to FIG. 2, and includes: an association determining unit 201, a first The sorting unit 202 and the second sorting unit 203.
  • the association determining unit 201 is configured to sequentially determine whether each of the to-be-paid funds is associated with the credit information system.
  • the first sorting unit 202 is configured to: when the to-be-paid amount is associated with the credit information system, place the to-be-paid amount in the priority queue in the priority queue, and according to the daily overdue interest rate, the credit information system The associated to-be-paid amount is prioritized.
  • the second sorting unit 203 is configured to: when the to-be-repaid amount is not associated with the credit information system, place the to-be-paid amount in the priority queue at the end of the queue, and follow the high-low interest rate of the daily overdue interest The pending payments associated with the letter system are prioritized.
  • the dichotomy subtraction module 104 in the fifth embodiment includes a structure for performing the method steps in the embodiment corresponding to FIG. 3, and includes: an amount setting unit 301, and a judging unit. 302. End unit 303 and dichotomy unit 304.
  • the amount setting unit 301 is configured to set the repayment amount corresponding to the deduction operation to be 1/2 of the minimum repayment amount of the deducted payment.
  • the determining unit 302 is configured to determine whether the repayment amount is less than the preset amount threshold.
  • the ending unit 303 is configured to end the automatic repayment process if the repayment amount is less than the preset amount threshold.
  • the dichotomy deduction unit 304 is configured to perform a deduction operation according to the repayment amount if the repayment amount is not less than the preset amount threshold, and set the repayment amount corresponding to the next deduction operation as the current deduction operation. And corresponding to the 1/2 of the repayment amount, and performing the deduction operation again if the repayment amount corresponding to the next deduction operation is not less than the preset amount threshold, until the repayment amount is less than the preset The amount threshold, ending the automatic repayment process.
  • the binary method deduction module 104 in the fifth embodiment includes a structure for performing the method steps in the embodiment corresponding to FIG. 4, which includes: an estimating unit 401, and an amount setting.
  • the estimating unit 401 is configured to obtain an estimated account balance based on the historical repayment record prediction.
  • the amount setting unit 402 is configured to set the repayment amount corresponding to the current deduction operation to the estimated account balance.
  • the determining unit 403 is configured to determine whether the repayment amount is less than the preset amount threshold.
  • the ending unit 404 is configured to end the automatic repayment process if the repayment amount is less than the preset amount threshold.
  • the dichotomy deduction unit 405 is configured to perform a deduction operation according to the repayment amount if the repayment amount is not less than the preset amount threshold, and set the repayment amount corresponding to the next deduction operation to the current deduction And operating the corresponding repayment amount 1/2, and performing the deduction operation again if the repayment amount corresponding to the next deduction operation is not less than the preset amount threshold, until the repayment amount is less than the pre-payment Set the amount threshold to end the automatic repayment process.
  • FIG. 9 is a schematic diagram of a terminal device provided in Embodiment 9 of the present application.
  • the terminal device 9 of this embodiment includes a processor 90, a memory 91, and computer readable instructions 92, such as programs, stored in the memory 91 and executable on the processor 90.
  • the processor 90 executes the computer readable instructions 92, the steps in the embodiments of the various automatic repayment methods described above are implemented, such as steps S101 to S104 shown in FIG.
  • the processor 90 implements the functions of the modules/units in the above-described system embodiments when the computer readable instructions 92 are executed, such as the functions of the modules 101-104 shown in FIG.
  • the computer readable instructions 92 may be partitioned into one or more modules/units that are stored in the memory 91 and executed by the processor 90, To complete this application.
  • the one or more modules/units may be a series of computer readable instruction instruction segments capable of performing a particular function, the instruction segments being used to describe the execution of the computer readable instructions 92 in the terminal device 9.
  • the computer readable instructions 92 can be segmented into a priority determination module, a read module, a minimum repayment amount deduction module, and a dichotomy subtraction module, each module having a specific function as described above.
  • the terminal device 9 may be a computing device such as a desktop computer, a notebook, a palmtop computer, and a cloud management server.
  • the terminal device may include, but is not limited to, a processor 90 and a memory 91. It will be understood by those skilled in the art that FIG. 9 is only an example of the terminal device 9, does not constitute a limitation of the terminal device 9, may include more or less components than those illustrated, or combine some components, or different components.
  • the terminal device may further include an input/output device, a network access device, a bus, and the like.
  • the so-called processor 90 can be a central processing unit (Central Processing Unit, CPU), can also be other general-purpose processors, digital signal processors (DSP), application specific integrated circuits (Application Specific Integrated Circuit (ASIC), Field-Programmable Gate Array (FPGA) or other programmable logic device, discrete gate or transistor logic device, discrete hardware components, etc.
  • the general purpose processor may be a microprocessor or the processor or any conventional processor or the like.
  • the memory 91 may be an internal storage unit of the terminal device 9, such as a hard disk or a memory of the terminal device 9.
  • the memory 91 may also be an external storage device of the terminal device 9, for example, a plug-in hard disk provided on the terminal device 9, a smart memory card (SMC), and a secure digital (SD). Card, flash card (Flash Card) and so on.
  • the memory 91 may also include both an internal storage unit of the terminal device 9 and an external storage device.
  • the memory 91 is configured to store the computer readable instructions and other programs and data required by the terminal device.
  • the memory 91 can also be used to temporarily store data that has been output or is about to be output.
  • each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.
  • the above integrated unit can be implemented in the form of hardware or in the form of a software functional unit.

Landscapes

  • Business, Economics & Management (AREA)
  • Accounting & Taxation (AREA)
  • Finance (AREA)
  • Engineering & Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • Strategic Management (AREA)
  • General Business, Economics & Management (AREA)
  • General Physics & Mathematics (AREA)
  • Theoretical Computer Science (AREA)
  • Economics (AREA)
  • Development Economics (AREA)
  • Marketing (AREA)
  • Technology Law (AREA)
  • Financial Or Insurance-Related Operations Such As Payment And Settlement (AREA)

Abstract

本申请适用于电子金融技术领域,提供了一种自动还款方法、***及终端设备,方法包括:根据待还款项与征信体系的关联度及所述待还款项的每日逾期利息,确定各个所述待还款项的优先度;读取各个所述待还款项的最低还款数额;根据所述还款优先度,在所述待还款项所属的账户中依次扣除各个所述待还款项对应的所述最低还款数额,并在每一次扣除操作执行后检测本次扣除操作是否成功;若检测到当次扣除操作失败,则采用二分法重新确定当次扣除操作对应的还款数额并再次进行扣除操作,直至所述还款数额小于预设金额阈值,结束自动还款进程。能够最大限度的利用待还款项所属的账户的余额进行还款,最大限度地降低由于用户逾期还款的而导致的不良影响。

Description

一种自动还款方法、***及终端设备
本申请申明享有2018年04月09日递交的申请号为201810309702.6、名称为“一种自动还款方法、***及终端设备”中国专利申请的优先权,该中国专利申请的整体内容以参考的方式结合在本申请中。
技术领域
本申请属于电子金融技术领域,尤其涉及一种自动还款方法、***及终端设备。
背景技术
用户在利用***或者其他借贷平台借款后,为了方便还款,一般都会设置关联好自己的银行卡,当到还款日期时,由***还款平台或者其他借贷平台自动从所关联的银行卡中进行扣款。
为了保护用户的财产安全,现有技术中***还款平台或者其他借贷平台无法直接读取用户银行卡的余额,为了实现自动还款,现有技术通常采用一次性扣款的方式进行扣款,即用户欠款多少钱就直接按照所欠的总额来对关联的银行卡进行扣款,一但银行卡中的余额小于用户欠款总额,就会导致用户还款失败的情况出现,导致用户出现逾期不还款的不良记录,同时也会产生更多的利息需要用户后续进行偿还。
同时,由于用户在使用钱包应用进行借贷还款管理时,可能会将多笔不同的借款关联在同一张银行卡上进行还款,如将向***、借贷app以及钱包自身借款的还款银行卡设置为同一张,此时一个月内用户该银行卡可能需要进行多次还款扣款,而现有的扣款方法往往都只是遵循还款时间优先的规则,哪笔借款先到了还款时间就直接先还哪笔,且都是使用上述的一次扣款的方式来进行每笔还款的扣款,使得对用户还款的管理效率是否低下,无法利用用户银行卡中的余额来为用户进行智能化的还款。
综上所述,现有自动还款方法存在智能化程度低下,无法在用户银行卡余额不足的情况下进行自动还款的问题。
技术问题
有鉴于此,本申请实施例提供了一种自动还款方法、***及终端设备,以解决现有自动还款方法存在智能化程度低下,无法在用户银行卡余额不足的情况下进行自动还款的问题。
技术解决方案
本申请的第一方面提供了一种自动还款方法,包括:
根据待还款项与征信体系的关联度及所述待还款项的每日逾期利息,确定各个所述待还款项的优先度;
读取各个所述待还款项的最低还款数额;
根据所述还款优先度,在所述待还款项所属的账户中依次扣除各个所述待还款项对应的所述最低还款数额,并在每一次扣除操作执行后检测本次扣除操作是否成功;
若检测到当次扣除操作失败,则采用二分法重新确定当次扣除操作对应的还款数额并再次进行扣除操作,所述还款数额小于预设金额阈值,结束自动还款进程。
有益效果
本申请提供的一种自动还款方法、***及终端设备,通过确定各个待还款项的优先度,根据优先度和最低还款数额进行还款,在用户还款账户余额不足以还清各个待还款项的最低还款数额的情况下,采用二分法重新确定还款数额并再次进行扣除操作,合理有效地针对用户的欠款情况及待还款项所属的账户的余额进行扣款,能够最大限度的利用账户的余额进行还款,最大限度地降低由于用户逾期还款的而导致的不良影响,有效地解决了现有自动还款方法存在智能化程度低下,无法在用户银行卡余额不足的情况下进行自动还款的问题。
附图说明
图1是本申请实施例一提供的一种自动还款方法的实现流程示意图;
图2是本申请实施例二提供的对应实施例一步骤S101的实现流程示意图;
图3是本申请实施例三提供的对应实施例一步骤S104的实现流程示意图;
图4是本申请实施例四提供的对应实施例一步骤S104的实现流程示意图;
图5是本申请实施例五提供的一种自动还款***的结构示意图;
图6是本申请实施例六提供的对应实施例五中优先度确定模块101的结构示意图;
图7是本申请实施例七提供的对应实施例五中二分法扣除模块104的结构示意图;
图8是本申请实施例八提供的对应实施例五中二分法扣除模块104的结构示意图;
图9是本申请实施例九提供的终端设备的示意图。
本发明的实施方式
以下描述中,为了说明而不是为了限定,提出了诸如特定***结构、技术之类的具体细节,以便透彻理解本申请实施例。然而,本领域的技术人员应当清楚,在没有这些具体细节的其它实施例中也可以实现本申请。在其它情况中,省略对众所周知的***、装置、电路以及方法的详细说明,以免不必要的细节妨碍本申请的描述。
为了说明本申请所述的技术方案,下面通过具体实施例来进行说明。
实施例一:
如图1所示,本实施例提供了一种自动还款方法,其具体包括:
步骤S101:根据待还款项与征信体系的关联度及所述待还款项的每日逾期利息,确定各个所述待还款项的优先度。
在实际应用中,并非所有的借款渠道都与征信体系有关联,如大多数的企业借贷平台只会计算待还款项的还款数额和每日逾期利息,而不会与征信体系有所关联。因此需要判断各个待还款项是否与征信体系的关联度。由于与征信体系关联的待还款项的还款情况会直接影响到用户的信用,为了在账户余额不足以还清所有欠款的情况下,最大限度的避免对用户的信用造成影响,优先对与征信体系关联的待还款项进行还款操作。
在实际应用中,不同借款渠道规定的逾期利率各不相同,例如***是以万分之五的逾期利率来计算每日逾期利息,企业借贷平台是以千分之五的逾期利率来计算每日逾期利息。且由于各个待还款项的待还款数额也各不相同,因此每笔待还款项的每日逾期利息也各不相同,其中,每笔待还款项的每日逾期利息等于该待还款项的待还款数额乘以逾期利率。为了减小用户的逾期成本,在自动还款时需要考虑各个待还款项的每日逾期利息,优先对每日逾期利息高的待还款项进行还款操作。
在具体应用中,首先根据待还款项与征信体系的关联度确定待还款项的优先度,与征信体系关联的待还款项的优先度高于未与征信体系关联的待还款项的优先度,再根据待还款项的每日逾期利息进一步确定各个待还款项的优先度,每日逾期利息高的待还款项的优先度高于每日逾期利息低的待还款项的优先度。示例性的,待还款项1是与征信体系关联的待还款项,其每日逾期利息为2元;待还款项2也是与征信体系关系的待还款项,期每期逾期利息为1元;待还款项3未与征信体系关联,其每日逾期利息为2元;待还款项4也未与征信体系关联,其每日逾期利息为3元,则待还款项1的优先度高于待还款项2的优先度,待还款项2的优先度高于待还款项3的优先度,待还款项3的优先度大于待还款项4的优先度。
步骤S102:读取各个所述待还款项的最低还款数额。
在具体应用中,最低还款数额是指待还款项在当期还款操作中不会对用户的信用产生影响或不会产生逾期利息时最低的还款数额。
在具体应用中,通过信用度数据库进行信用调查,针对用户的信用度设置各个待还款项的最低还款数额。示例性的,通过信用度数据库查找该用户在各个借贷平台的信用度,针对不同借贷平台的信用度设置每笔待还款项的最低还款数额。信用度高的设置较低的最低还款数额,信用度低的设置较高的最低还款数额。在具体应用中,上述待还款项的最低还款数额还可以由各个借贷平台根据各个待还款项的待还款数额进行设置。
步骤S103:根据所述还款优先度,在所述待还款项所属的账户中依次扣除各个所述待还款项对应的所述最低还款数额,并在每一次扣除操作执行后检测本次扣除操作是否成功。
在具体应用中,由于偿还全部待还款项的最低还款数额便能避免对用户的信用产生影响也不会产生逾期利息,在对全部待还款项进行自动还款时,为了避免待还款项所属的账户的余额不足以扣除全部待还款项的全部待还款数额,先读取各个待还款项的最低还款数额,再根据还款优先度,在待还款项所属的账户中依次扣除各个待还款项对应的最低还款数额。通过向待还款项所属的账户发出扣除该待还款项对应的最低还款数额的扣款请求进行扣除操作。
在具体应用中,在每一次扣除操作执行后检测本次扣除操作是否成功。若该账户的余额大于或等于该待还款项对应的最低还款数额则本次扣除操作成功。若该账户的余额小于该待还款项对应的最低还款数额则本次扣除操作失败。具体的,当成功从该账户扣除扣款请求对应的最低还款数时会反馈扣除成功信号,检测本次扣除操作是否成功即检测是否有反馈的扣除成功信号,若检测到扣除成功信号则表明本次扣除操作成功;反之,则表明本次扣除操作失败。
步骤S104:若检测到当次扣除操作失败,则采用二分法重新确定当次扣除操作对应的还款数额并再次进行扣除操作,直至所述还款数额小于预设金额阈值,结束自动还款进程。
在具体应用中,当次扣除操作失败,则说明所属的账户的余额不足以扣除该待还款项的最低还款数额。此时,为了最大限度的对该待还款项进行还款操作,减少逾期利息,采用二分法重新确定当次扣除操作对应的还款数额并再次进行扣除操作。通过二分法确定还款数额具体是将该待还款项的最低还款数额的一半作为当次扣除操作的还款数额,向所属的账户发出扣除还款数额的扣款请求。
在具体应用中,若当次扣除操作成功,则表明当次扣除操作之前,所述账户的余额小于该待还款项的最低还款数额且大于或等于该待还款项的最低还款数额的一半。此时再次通过二分法确定下次扣除操作对应的还款数额,即下次扣除操作对应的还款数额为当次扣除操作对应的还款数额的一半(为该待还款项的最低还款数额的1/4),并向所属的账户重新发出扣除还款数额的扣款请求。若当次扣除操作失败,则表明当次扣除操作之前,所述账户的余额小于该待还款项的最低还款数额的一半,此时同样再次通过二分法确定下次扣除操作对应的还款数额,即下次扣除操作对应的还款数额为当次扣除操作对应的还款数额的一半(为该待还款项的最低还款数额的1/4),并向所属的账户重新发出扣除还款数额的扣款请求。直至还款数额小于预设金额阈值,结束自动还款进程。
在具体应用中,由于采用二分法确定还款数额并再次进行扣除操作可以无限度对所属的账户的余额进行扣除操作,然而当还款数额过小时,再继续进行扣除操作已经没有意义,因此设置预设金额阈值,当还款数额小于该预设金额阈值时,自动结束自动还款进程。
在一个实施例中,上述自动还款方法还包括:
步骤S105:在所述自动还款进程结束后,生成还款情况报告并发送至用户端,其中,所述还款情况报告包括未成功扣除最低还款数额的账户信息。
在具体应用中,在自动还款进程结束后,获取全部待还款项的还款情况,并生成还款情况报告发送至用户端,还款情况报告包括未成功扣除最低还款数额的账户信息。通过还款情况报告可以知悉当日的待还款项的还款情况、是否还存在未成功扣除最低还款数额的待还款项,未成功扣除最低还款数额的待还款项所需的数额、还清全部待还款项的还款数额所需的数额以及下次还款期限等信息,需要说明的是,可以通过短信方式将还款情况报告发送至关联的账户的终端设备中,也可以通过终端设备中相关的应用程序查询该还款情况报告,在此不加以限制。
在一个实施例中,在执行步骤S101之前,先读取全部待还款项的全部待还款数额,向所属的账户发出扣除全部待还款数额的扣款请求,若扣除操作成功,则说明所属的账户的余额大于或等于全部待还款数额,即已经完成全部待还款项的还款操作。若扣除操作失败则说明所述账户的余额小于全部待还款数额,此时执行步骤S101。
在一个实施例中,若在待还款项所属的账户中依次扣除各个待还款项对应的最低还款数额的扣除操作均成功,表明全部待还款项的最低还款数额已经还清。此时,根据历史还款记录预测所属的账户的余额,根据预测的余额进行扣除操作,最大限度地利用账户的余额进行还款。即向待还款项所属的账户中扣除预测的余额的扣款请求,并检测当次扣除操作是否成功,若检测到当次扣除操作不成功,则执行步骤S104。
在一个实施例中,由于待还款项所属的账户可能会用于其他用途,为了避免该账户的余额不能满足其他用途的需求,设置预设余款阈值,当向账户发出扣除还款数额扣除请求时,账户会根据还款数额和账户余额分析扣除还款数额后账户余额是否小于预设余款阈值。若是,则不进行扣款。在一个实施例中,通过检测待还款项所属的账户的资金流水情况,在检测到所属的账户的流水收入超过全部待还款项的最低还款数额之和时,自动在待还款项所属的账户中依次扣除各个待还款项对应的最低还款数额。
本实施例提供的自动还款方法,通过确定各个待还款项的优先度,根据优先度和最低还款数额进行还款,在用户还款账户余额不足以还清各个待还款项的最低还款数额的情况下,采用二分法重新确定还款数额并再次进行扣除操作,合理有效地针对用户的欠款情况及待还款项所属的账户的余额进行扣款,能够最大限度的利用账户的余额进行还款,最大限度地降低由于用户逾期还款的而导致的不良影响,有效地解决了现有自动还款方法存在智能化程度低下,无法在用户银行卡余额不足的情况下进行自动还款的问题。
实施例二:
如图2所示,在本实施例中,实施例一中的步骤S101具体包括:
步骤S201:依次判断各个所述待还款项是否与征信体系相关联。
在具体应用中,由于与征信体系关联的待还款项的还款情况会直接影响到用户的信用,因此需要依次判断各个待还款项是否与征信体系相关联。在自动还款的过程中,先对与征信体系相关联的待还款项进行还款操作,能够避免逾期还款对用户的信用造成影响。
步骤S202:若所述待还款项与征信体系相关联,则在优先度队列中将所述待还款项置于队首,并按照每日逾期利息的高低将与征信体系相关联的所述待还款项进行优先度排序。
在具体应用中,将待还款项进行优先度排序,将与征信体系相关联的待还款项置于优先度队列的队首,再按照各个与征信体系相关联的待还款项的每日逾期利息的高低,对该待还款项进行优先度排序,将每日逾期利息高的待还款项置于每日逾期利息低的待还款项之前。
步骤S203:若所述待还款项未与征信体系相关联,则在优先度队列中将所述待还款项置于队尾,并按照每日逾期利息的高低将未与征信体系相关联的所述待还款项进行优先度排序。
在具体应用中,将未与征信体系相关联的待还款项置于优先度队列的队尾,再按照各个未与征信体系相关联的待还款项的每日逾期利息的高低,对该待还款项进行优先度排序,将每日逾期利息高的待还款项置于每日逾期利息低的待还款项之前。
也就是说,在优先度队列中,与征信体系相关联且每日逾期利息高的待还款项的优先度高于与征信体系相关联且每日逾期利息低的待还款项的优先度,与征信体系相关联且每日逾期利息低的待还款项的优先度高于未与征信体系相关联且每日逾期利息高的待还款项的优先度,未与征信体系相关联且每日逾期利息高的待还款项的优先度高于未与征信体系相关联且每日逾期利息低的待还款项的优先度。示例性的,待还款项1是与征信体系关联的待还款项,其每日逾期利息为2元;待还款项2也是与征信体系关系的待还款项,期每期逾期利息为1元;待还款项3未与征信体系关联,其每日逾期利息为2元;待还款项4也未与征信体系关联,其每日逾期利息为3元,则在优先度队列为:待还款项1的优先度>待还款项2的优先度>待还款项3的优先度>待还款项4的优先度。
实施例三:
如图3所示,在本实施例中,实施例一中的步骤S104具体包括:
步骤S301:设置当次扣除操作对应的还款数额为扣除失败的待还款项的最低还款数额的1/2。
在具体应用中,待还款项所属的账户的余额小于扣除失败的待还款项的最低还款数额,为了最大限度地利用所属的账户的余额进行还款,将当次扣除操作对应的还款数额设置为上次扣除失败的待还款项的最低还款数额的1/2。
步骤S302:判断所述还款数额是否小于所述预设金额阈值。
在具体应用中,为了避免无意义的扣除操作(扣除的还款数额过小),先判断设置的还款数额是否小于预设金额阈值。需要说明的是,上述预设金额阈值是指为了避免与意义的扣除操作而预先设置的金额(例如0.1元)。
步骤S303:若所述还款数额小于所述预设金额阈值,则结束自动还款进程。
在具体应用中,当次扣除操作对应的还款数额小于该预设金额阈值,则说明待还款项所属的账户的余额小于该预设金额阈值的两倍,此时再进行扣除操作已经没有意义,此时结束自动还款进程。
步骤S304:若所述还款数额不小于所述预设金额阈值,则按照所述还款数额进行扣除操作,并将下次扣除操作对应的还款数额设置为当次扣除操作对应的还款数额的1/2,并在所述下次扣除操作对应的还款数额不小于所述预设金额阈值的情况下再次进行扣除操作,直至所述还款数额小于所述预设金额阈值,结束自动还款进程。
在具体应用中,由于还款数额不小于预设金额阈值,因此,向待还款项所属的账户发出扣除还款数额的扣款请求,为了最大限度的利用所属的账户的余额进行还款,将下次扣除操作对应的还款数额设置为当次扣除操作对应的还款数额的1/2(即待还款项的最低还款数额的1/4),并再次判断该还款数额是否小于预设金额阈值,在该还款数额不小于预设金额阈值的情况下再次进行扣除操作。直至还款数额小于预设金额阈值,此时说明待还款项所属的账户的余额小于该预设金额阈值的两倍,此时再进行扣除操作已经没有意义,因此结束自动还款进程。
在具体应用中,无论当次扣除操作是否成功,都将下次扣除操作对应的还款数额设置为当次扣除操作对应的还款数额的1/2。若当次扣除操作成功,则说明当次扣除操作之前,所属账户的余额小于该待还款项的最低还款数额且大于或等于该待还款项的最低还款数额的一半。此时再次通过二分法确定下次扣除操作对应的还款数额,即下次扣除操作对应的还款数额为当次扣除操作对应的还款数额的一半(为该待还款项的最低还款数额的1/4),并向所属的账户重新发出扣除还款数额的扣款请求。若当次扣除操作失败,则说明当次扣除操作之前,所述账户的余额小于该待还款项的最低还款数额的一半,此时同样再次通过二分法确定下次扣除操作对应的还款数额,即下次扣除操作对应的还款数额为当次扣除操作对应的还款数额的一半(为该待还款项的最低还款数额的1/4),并向所属的账户重新发出扣除还款数额的扣款请求。
实施例四:
如图4所示,区别与实施例三,在本实施例中,实施例一中的步骤S104具体包括:
步骤S401:根据历史还款记录预测得到预估账户余额。
在具体应用中,根据所属的账户的历史还款记录可以对该账户的账户余额进行预估,通过获取该账户前N个月的自动还款记录,预测该账户每个月的账户余额,将预测得到的每个月的账户余额求取平均数,将该平均数作为预估账户余额,其中N为大于1的整数。需要说明的是,当N的取值越大,预估账户余额越精准。还需要说明的是,为了更精准的预测所属账户的余额,可以将获取到的前N个月的自动还款记录中的异常点进行剔除,根据剔除异常点后的还款记录进行预测。其中,异常点与其他月份的还款记录存在明显差异的某一月份的还款记录,如还款过多或过少。步骤S402:设置当次扣除操作对应的还款数额为所述预估账户余额。
在具体应用中,待还款项所属的账户的余额小于扣除失败的待还款项的最低还款数额,为了最大限度地利用所属的账户的余额进行还款,将当次扣除操作对应的还款数额设置为预估账户余额。
步骤S403:判断所述还款数额是否小于所述预设金额阈值。
在具体应用中,为了避免无意义的扣除操作(扣除的还款数额过小),先判断设置的还款数额是否小于预设金额阈值。需要说明的是,上述预设金额阈值是指为了避免与意义的扣除操作而预先设置的金额(例如0.1元)。
步骤S404:若所述还款数额小于所述预设金额阈值,则结束自动还款进程。
在具体应用中,当次扣除操作对应的还款数额小于该预设金额阈值,则说明待还款项所属的账户的余额小于该预设金额阈值的两倍,此时再进行扣除操作已经没有意义,此时结束自动还款进程。步骤S405:若所述还款数额不小于所述预设金额阈值,则按照所述还款数额进行扣除操作,并将下次扣除操作对应的还款数额设置为当次扣除操作对应的还款数额的1/2,并在所述下次扣除操作对应的还款数额不小于所述预设金额阈值的情况下再次进行扣除操作,直至所述还款数额小于所述预设金额阈值,结束自动还款进程。
在具体应用中,由于还款数额不小于预设金额阈值,因此,向待还款项所属的账户发出扣除还款数额的扣款请求,为了最大限度的利用所属的账户的余额进行还款,将下次扣除操作对应的还款数额设置为当次扣除操作对应的还款数额的1/2(即预估账户余额的1/4),并再次判断该还款数额是否小于预设金额阈值,在该还款数额不小于预设金额阈值的情况下再次进行扣除操作。直至还款数额小于预设金额阈值,此时说明待还款项所属的账户的余额小于该预设金额阈值的两倍,此时再进行扣除操作已经没有意义,因此结束自动还款进程。
在具体应用中,无论当次扣除操作是否成功,都将下次扣除操作对应的还款数额设置为当次扣除操作对应的还款数额的1/2。若当次扣除操作成功,则说明当次扣除操作之前,所属账户的余额大于或等于预估账户余额。此时通过二分法确定下次扣除操作对应的还款数额,即下次扣除操作对应的还款数额为当次扣除操作对应的还款数额的一半(为该预估账户余额的1/2),并向所属的账户重新发出扣除还款数额的扣款请求。若当次扣除操作失败,则说明当次扣除操作之前,所述账户的余额小于该预估账户余额,此时同样再次通过二分法确定下次扣除操作对应的还款数额,即下次扣除操作对应的还款数额为当次扣除操作对应的还款数额的一半(为该预估账户余额的1/2),并向所属的账户重新发出扣除还款数额的扣款请求。
实施例五:
如图5所示,本实施例提供一种自动还款***100,用于执行实施例一中的方法步骤,其包括:优先度确定模块101、读取模块102、最低还款数额扣除模块103以及二分法扣除模块104。
优先度确定模块101用于根据待还款项与征信体系的关联度及所述待还款项的每日逾期利息,确定各个所述待还款项的优先度。
读取模块102用于读取各个所述待还款项的最低还款数额。
最低还款数额扣除模块103用于根据所述还款优先度,在所述待还款项所属的账户中依次扣除各个所述待还款项对应的所述最低还款数额,并在每一次扣除操作执行后检测本次扣除操作是否成功还款数额。
二分法扣除模块104用于若检测到当次扣除操作失败,则采用二分法重新确定当次扣除操作对应的还款数额并再次进行扣除操作,直至所述还款数额小于预设金额阈值,结束自动还款进程。
在一个实施例中,上述自动还款***还包括:报告生成模块。
报告生成模块用于在所述自动还款进程结束后,生成还款情况报告并发送至用户端,其中,所述还款情况报告包括未成功扣除最低还款数额的账户信息。
需要说明的是,本申请实施例提供的自动还款***,由于与本申请图1所示方法实施例基于同一构思,其带来的技术效果与本申请图1所示方法实施例相同,具体内容可参见本申请图1所示方法实施例中的叙述,此处不再赘述。
实施例六:
如图6所示,在本实施例中,实施例五中的优先度确定模块101包括用于执行图2所对应的实施例中的方法步骤的结构,其包括:关联判断单元201、第一排序单元202以及第二排序单元203。
关联判断单元201用于依次判断各个所述待还款项是否与征信体系相关联。
第一排序单元202用于若所述待还款项与征信体系相关联,则在优先度队列中将所述待还款项置于队首,并按照每日逾期利息的高低将与征信体系相关联的所述待还款项进行优先度排序。
第二排序单元203用于若所述待还款项未与征信体系相关联,则在优先度队列中将所述待还款项置于队尾,并按照每日逾期利息的高低将未与征信体系相关联的所述待还款项进行优先度排序。
实施例七:
如图7所示,在本实施例中,实施例五中的二分法扣除模块104包括用于执行图3所对应的实施例中的方法步骤的结构,其包括:金额设置单元301、判断单元302、结束单元303以及二分法扣除单元304。
金额设置单元301用于设置当次扣除操作对应的还款数额为扣除失败的待还款项的最低还款数额的1/2。
判断单元302用于判断所述还款数额是否小于所述预设金额阈值。
结束单元303用于若所述还款数额小于所述预设金额阈值,则结束自动还款进程。
二分法扣除单元304用于若所述还款数额不小于所述预设金额阈值,则按照所述还款数额进行扣除操作,并将下次扣除操作对应的还款数额设置为当次扣除操作对应的还款数额的1/2,并在所述下次扣除操作对应的还款数额不小于所述预设金额阈值的情况下再次进行扣除操作,直至所述还款数额小于所述预设金额阈值,结束自动还款进程。
实施例八:
如图8所示,在本实施例中,实施例五中的二分法扣除模块104包括用于执行图4所对应的实施例中的方法步骤的结构,其包括:预估单元401、金额设置单元402、判断单元403、结束单元404以及二分法扣款单元405。
预估单元401用于根据历史还款记录预测得到预估账户余额。
金额设置单元402用于设置当次扣除操作对应的还款数额为所述预估账户余额。
判断单元403用于判断所述还款数额是否小于所述预设金额阈值。
结束单元404用于若所述还款数额小于所述预设金额阈值,则结束自动还款进程。
二分法扣款单元405用于若所述还款数额不小于所述预设金额阈值,则按照所述还款数额进行扣除操作,并将下次扣除操作对应的还款数额设置为当次扣除操作对应的还款数额的1/2,并在所述下次扣除操作对应的还款数额不小于所述预设金额阈值的情况下再次进行扣除操作,直至所述还款数额小于所述预设金额阈值,结束自动还款进程。
实施例九:
图9是本申请实施例九提供的终端设备的示意图。如图9所示,该实施例的终端设备9包括:处理器90、存储器91以及存储在所述存储器91中并可在所述处理器90上运行的计算机可读指令92,例如程序。所述处理器90执行所述计算机可读指令92时实现上述各个自动还款方法实施例中的步骤,例如图1所示的步骤S101至S104。或者,所述处理器90执行所述计算机可读指令92时实现上述***实施例中各模块/单元的功能,例如图5所示模块101至104的功能。
示例性的,所述计算机可读指令92可以被分割成一个或多个模块/单元,所述一个或者多个模块/单元被存储在所述存储器91中,并由所述处理器90执行,以完成本申请。所述一个或多个模块/单元可以是能够完成特定功能的一系列计算机可读指令指令段,该指令段用于描述所述计算机可读指令92在所述终端设备9中的执行过程。例如,所述计算机可读指令92可以被分割成优先度确定模块、读取模块、最低还款数额扣除模块以及二分法扣除模块,各模块具体功能如上所述。
所述终端设备9可以是桌上型计算机、笔记本、掌上电脑及云端管理服务器等计算设备。所述终端设备可包括,但不仅限于,处理器90、存储器91。本领域技术人员可以理解,图9仅仅是终端设备9的示例,并不构成对终端设备9的限定,可以包括比图示更多或更少的部件,或者组合某些部件,或者不同的部件,例如所述终端设备还可以包括输入输出设备、网络接入设备、总线等。
所称处理器90可以是中央处理单元(Central Processing Unit,CPU),还可以是其他通用处理器、数字信号处理器 (Digital Signal Processor,DSP)、专用集成电路 (Application Specific Integrated Circuit,ASIC)、现成可编程门阵列 (Field-Programmable Gate Array,FPGA) 或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件等。通用处理器可以是微处理器或者该处理器也可以是任何常规的处理器等。
所述存储器91可以是所述终端设备9的内部存储单元,例如终端设备9的硬盘或内存。所述存储器91也可以是所述终端设备9的外部存储设备,例如所述终端设备9上配备的插接式硬盘,智能存储卡(Smart Media Card, SMC),安全数字(Secure Digital, SD)卡,闪存卡(Flash Card)等。进一步地,所述存储器91还可以既包括所述终端设备9的内部存储单元也包括外部存储设备。所述存储器91用于存储所述计算机可读指令以及所述终端设备所需的其他程序和数据。所述存储器91还可以用于暂时地存储已经输出或者将要输出的数据。
本领域普通技术人员可以意识到,结合本文中所公开的实施例描述的各示例的单元及算法步骤,能够以电子硬件、或者计算机软件和电子硬件的结合来实现。这些功能究竟以硬件还是软件方式来执行,取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能,但是这种实现不应认为超出本申请的范围。
另外,在本申请各个实施例中的各功能单元可以集成在一个处理单元中,也可以是各个单元单独物理存在,也可以两个或两个以上单元集成在一个单元中。上述集成的单元既可以采用硬件的形式实现,也可以采用软件功能单元的形式实现。
以上所述实施例仅用以说明本申请的技术方案,而非对其限制;尽管参照前述实施例对本申请进行了详细的说明,本领域的普通技术人员应当理解:其依然可以对前述各实施例所记载的技术方案进行修改,或者对其中部分技术特征进行等同替换;而这些修改或者替换,并不使相应技术方案的本质脱离本申请各实施例技术方案的精神和范围,均应包含在本申请的保护范围之内。

Claims (20)

  1. 一种自动还款方法,其特征在于,包括:
    根据待还款项与征信体系的关联度及所述待还款项的每日逾期利息,确定各个所述待还款项的优先度;
    读取各个所述待还款项的最低还款数额;
    根据所述还款优先度,在所述待还款项所属的账户中依次扣除各个所述待还款项对应的所述最低还款数额,并在每一次扣除操作执行后检测本次扣除操作是否成功;
    若检测到当次扣除操作失败,则采用二分法重新确定当次扣除操作对应的还款数额并再次进行扣除操作,直至所述还款数额小于预设金额阈值,结束自动还款进程。
  2. 根据权利要求1所述的自动还款方法,其特征在于,所述根据待还款项与征信体系的关联度及所述待还款项的每日逾期利息,对所有所述待还款项进行还款优先度排序,包括:
    依次判断各个所述待还款项是否与征信体系相关联;
    若所述待还款项与征信体系相关联,则在优先度队列中将所述待还款项置于队首,并按照每日逾期利息的高低将与征信体系相关联的所述待还款项进行优先度排序;
    若所述待还款项未与征信体系相关联,则在优先度队列中将所述待还款项置于队尾,并按照每日逾期利息的高低将未与征信体系相关联的所述待还款项进行优先度排序。
  3. 根据权利要求1所述的自动还款方法,其特征在于,所述采用二分法重新确定当次扣除操作对应的还款数额并再次进行扣除操作,直至所述还款数额小于预设金额阈值,结束自动还款进程,包括:
    设置当次扣除操作对应的还款数额为扣除失败的待还款项的最低还款数额的1/2;
    判断所述还款数额是否小于所述预设金额阈值;
    若所述还款数额小于所述预设金额阈值,则结束自动还款进程;
    若所述还款数额不小于所述预设金额阈值,则按照所述还款数额进行扣除操作,并将下次扣除操作对应的还款数额设置为当次扣除操作对应的还款数额的1/2,并在所述下次扣除操作对应的还款数额不小于所述预设金额阈值的情况下再次进行扣除操作,直至所述还款数额小于所述预设金额阈值,结束自动还款进程。
  4. 根据权利要求1所述的自动还款方法,其特征在于,所述采用二分法重新确定当次扣除操作对应的还款数额并再次进行扣除操作,直至所述还款数额小于预设金额阈值,结束自动还款进程,包括:
    根据历史还款记录预测得到预估账户余额;
    设置当次扣除操作对应的还款数额为所述预估账户余额;
    判断所述还款数额是否小于所述预设金额阈值;
    若所述还款数额小于所述预设金额阈值,则结束自动还款进程;
    若所述还款数额不小于所述预设金额阈值,则按照所述还款数额进行扣除操作,并将下次扣除操作对应的还款数额设置为当次扣除操作对应的还款数额的1/2,并在所述下次扣除操作对应的还款数额不小于所述预设金额阈值的情况下再次进行扣除操作,直至所述还款数额小于所述预设金额阈值,结束自动还款进程。
  5. 根据权利要求1所述的自动还款方法,其特征在于,还包括:
    在所述自动还款进程结束后,生成还款情况报告并发送至用户端,其中,所述还款情况报告包括未成功扣除最低还款数额的账户信息。
  6. 一种自动还款***,其特征在于,包括:
    优先度确定模块,用于根据待还款项与征信体系的关联度及所述待还款项的每日逾期利息,确定各个所述待还款项的优先度;
    读取模块,用于读取各个所述待还款项的最低还款数额;
    最低还款数额扣除模块,用于根据所述还款优先度,在所述待还款项所属的账户中依次扣除各个所述待还款项对应的所述最低还款数额,并在每一次扣除操作执行后检测本次扣除操作是否成功还款数额;
    二分法扣除模块,用于若检测到当次扣除操作失败,则采用二分法重新确定当次扣除操作对应的还款数额并再次进行扣除操作,直至所述还款数额小于预设金额阈值,结束自动还款进程。
  7. 根据权利要求6所述的自动还款***,其特征在于,所述优先度确定模块包括:
    关联判断单元,用于依次判断各个所述待还款项是否与征信体系相关联;
    第一排序单元,用于若所述待还款项与征信体系相关联,则在优先度队列中将所述待还款项置于队首,并按照每日逾期利息的高低将与征信体系相关联的所述待还款项进行优先度排序;
    第二排序单元,用于若所述待还款项未与征信体系相关联,则在优先度队列中将所述待还款项置于队尾,并按照每日逾期利息的高低将未与征信体系相关联的所述待还款项进行优先度排序。
  8. 根据权利要求6所述的自动还款***,其特征在于,所述二分法扣除模块包括:
    金额设置单元,用于设置当次扣除操作对应的还款数额为扣除失败的待还款项的最低还款数额的1/2;
    判断单元,用于判断所述还款数额是否小于所述预设金额阈值;
    结束单元,用于若所述还款数额小于所述预设金额阈值,则结束自动还款进程;
    二分法扣除单元,用于若所述还款数额不小于所述预设金额阈值,则按照所述还款数额进行扣除操作,并将下次扣除操作对应的还款数额设置为当次扣除操作对应的还款数额的1/2,并在所述下次扣除操作对应的还款数额不小于所述预设金额阈值的情况下再次进行扣除操作,直至所述还款数额小于所述预设金额阈值,结束自动还款进程。
  9. 根据权利要求6所述自动还款***,其特征在于,所述二分法扣除模块,包括:
    预估单元,用于根据历史还款记录预测得到预估账户余额;
    金额设置单元,用于设置当次扣除操作对应的还款数额为所述预估账户余额;
    判断单元,用于判断所述还款数额是否小于所述预设金额阈值;
    结束单元,用于若所述还款数额小于所述预设金额阈值,则结束自动还款进程;
    二分法扣款单元,用于若所述还款数额不小于所述预设金额阈值,则按照所述还款数额进行扣除操作,并将下次扣除操作对应的还款数额设置为当次扣除操作对应的还款数额的1/2,并在所述下次扣除操作对应的还款数额不小于所述预设金额阈值的情况下再次进行扣除操作,直至所述还款数额小于所述预设金额阈值,结束自动还款进程。
  10. 根据权利要求6所述的自动还款***,其特征在于,还包括:
    报告生成模块,用于在所述自动还款进程结束后,生成还款情况报告并发送至用户端,其中,所述还款情况报告包括未成功扣除最低还款数额的账户信息。
  11. 一种终端设备,包括存储器、处理器以及存储在所述存储器中并可在所述处理器上运行的计算机可读指令,其特征在于,所述处理器执行所述计算机可读指令时实现如下步骤:
    根据待还款项与征信体系的关联度及所述待还款项的每日逾期利息,确定各个所述待还款项的优先度;
    读取各个所述待还款项的最低还款数额;
    根据所述还款优先度,在所述待还款项所属的账户中依次扣除各个所述待还款项对应的所述最低还款数额,并在每一次扣除操作执行后检测本次扣除操作是否成功;
    若检测到当次扣除操作失败,则采用二分法重新确定当次扣除操作对应的还款数额并再次进行扣除操作,直至所述还款数额小于预设金额阈值,结束自动还款进程。
  12. 根据权利要求11所述的终端设备,其特征在于,所述根据待还款项与征信体系的关联度及所述待还款项的每日逾期利息,对所有所述待还款项进行还款优先度排序,包括:
    依次判断各个所述待还款项是否与征信体系相关联;
    若所述待还款项与征信体系相关联,则在优先度队列中将所述待还款项置于队首,并按照每日逾期利息的高低将与征信体系相关联的所述待还款项进行优先度排序;
    若所述待还款项未与征信体系相关联,则在优先度队列中将所述待还款项置于队尾,并按照每日逾期利息的高低将未与征信体系相关联的所述待还款项进行优先度排序。
  13. 根据权利要求11所述的终端设备,其特征在于,所述采用二分法重新确定当次扣除操作对应的还款数额并再次进行扣除操作,直至所述还款数额小于预设金额阈值,结束自动还款进程,包括:
    设置当次扣除操作对应的还款数额为扣除失败的待还款项的最低还款数额的1/2;
    判断所述还款数额是否小于所述预设金额阈值;
    若所述还款数额小于所述预设金额阈值,则结束自动还款进程;
    若所述还款数额不小于所述预设金额阈值,则按照所述还款数额进行扣除操作,并将下次扣除操作对应的还款数额设置为当次扣除操作对应的还款数额的1/2,并在所述下次扣除操作对应的还款数额不小于所述预设金额阈值的情况下再次进行扣除操作,直至所述还款数额小于所述预设金额阈值,结束自动还款进程。
  14. 根据权利要求11所述的终端设备,其特征在于,所述采用二分法重新确定当次扣除操作对应的还款数额并再次进行扣除操作,直至所述还款数额小于预设金额阈值,结束自动还款进程,包括:
    根据历史还款记录预测得到预估账户余额;
    设置当次扣除操作对应的还款数额为所述预估账户余额;
    判断所述还款数额是否小于所述预设金额阈值;
    若所述还款数额小于所述预设金额阈值,则结束自动还款进程;
    若所述还款数额不小于所述预设金额阈值,则按照所述还款数额进行扣除操作,并将下次扣除操作对应的还款数额设置为当次扣除操作对应的还款数额的1/2,并在所述下次扣除操作对应的还款数额不小于所述预设金额阈值的情况下再次进行扣除操作,直至所述还款数额小于所述预设金额阈值,结束自动还款进程。
  15. 根据权利要求11所述的终端设备,其特征在于,所述处理器执行所述计算机可读指令时还实现如下步骤:
    在所述自动还款进程结束后,生成还款情况报告并发送至用户端,其中,所述还款情况报告包括未成功扣除最低还款数额的账户信息。
  16. 一种计算机可读存储介质,所述计算机可读存储介质存储有计算机可读指令,其特征在于,所述计算机可读指令被处理器执行时实现如下步骤:
    根据待还款项与征信体系的关联度及所述待还款项的每日逾期利息,确定各个所述待还款项的优先度;
    读取各个所述待还款项的最低还款数额;
    根据所述还款优先度,在所述待还款项所属的账户中依次扣除各个所述待还款项对应的所述最低还款数额,并在每一次扣除操作执行后检测本次扣除操作是否成功;
    若检测到当次扣除操作失败,则采用二分法重新确定当次扣除操作对应的还款数额并再次进行扣除操作,直至所述还款数额小于预设金额阈值,结束自动还款进程。
  17. 根据权利要求16所述的计算机可读存储介质,其特征在于,所述根据待还款项与征信体系的关联度及所述待还款项的每日逾期利息,对所有所述待还款项进行还款优先度排序,包括:
    依次判断各个所述待还款项是否与征信体系相关联;
    若所述待还款项与征信体系相关联,则在优先度队列中将所述待还款项置于队首,并按照每日逾期利息的高低将与征信体系相关联的所述待还款项进行优先度排序;
    若所述待还款项未与征信体系相关联,则在优先度队列中将所述待还款项置于队尾,并按照每日逾期利息的高低将未与征信体系相关联的所述待还款项进行优先度排序。
  18. 根据权利要求16所述的计算机可读存储介质,其特征在于,所述采用二分法重新确定当次扣除操作对应的还款数额并再次进行扣除操作,直至所述还款数额小于预设金额阈值,结束自动还款进程,包括:
    设置当次扣除操作对应的还款数额为扣除失败的待还款项的最低还款数额的1/2;
    判断所述还款数额是否小于所述预设金额阈值;
    若所述还款数额小于所述预设金额阈值,则结束自动还款进程;
    若所述还款数额不小于所述预设金额阈值,则按照所述还款数额进行扣除操作,并将下次扣除操作对应的还款数额设置为当次扣除操作对应的还款数额的1/2,并在所述下次扣除操作对应的还款数额不小于所述预设金额阈值的情况下再次进行扣除操作,直至所述还款数额小于所述预设金额阈值,结束自动还款进程。
  19. 根据权利要求16所述的计算机可读存储介质,其特征在于,所述采用二分法重新确定当次扣除操作对应的还款数额并再次进行扣除操作,直至所述还款数额小于预设金额阈值,结束自动还款进程,包括:
    根据历史还款记录预测得到预估账户余额;
    设置当次扣除操作对应的还款数额为所述预估账户余额;
    判断所述还款数额是否小于所述预设金额阈值;
    若所述还款数额小于所述预设金额阈值,则结束自动还款进程;
    若所述还款数额不小于所述预设金额阈值,则按照所述还款数额进行扣除操作,并将下次扣除操作对应的还款数额设置为当次扣除操作对应的还款数额的1/2,并在所述下次扣除操作对应的还款数额不小于所述预设金额阈值的情况下再次进行扣除操作,直至所述还款数额小于所述预设金额阈值,结束自动还款进程。
  20. 根据权利要求16所述的计算机可读存储介质,其特征在于,所述计算机可读指令被处理器执行时还实现如下步骤:
    在所述自动还款进程结束后,生成还款情况报告并发送至用户端,其中,所述还款情况报告包括未成功扣除最低还款数额的账户信息。
PCT/CN2018/097529 2018-04-09 2018-07-27 一种自动还款方法、***及终端设备 WO2019196257A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201810309702.6 2018-04-09
CN201810309702.6A CN108711047B (zh) 2018-04-09 2018-04-09 一种自动还款方法、***及终端设备

Publications (1)

Publication Number Publication Date
WO2019196257A1 true WO2019196257A1 (zh) 2019-10-17

Family

ID=63867132

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2018/097529 WO2019196257A1 (zh) 2018-04-09 2018-07-27 一种自动还款方法、***及终端设备

Country Status (2)

Country Link
CN (1) CN108711047B (zh)
WO (1) WO2019196257A1 (zh)

Families Citing this family (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109816367A (zh) * 2019-01-04 2019-05-28 平安科技(深圳)有限公司 交易处理方法、终端设备及计算机存储介质
CN110322339B (zh) * 2019-05-22 2023-06-30 平安银行股份有限公司 虚拟资源管理方法、装置、计算机***及可读存储介质
CN110969427A (zh) * 2019-12-06 2020-04-07 优比付(杭州)科技有限公司 一种基于***的分期支付方法
CN111429261A (zh) * 2020-03-19 2020-07-17 交通银行股份有限公司 基于交易的贷记卡计息方法、***、终端设备和存储介质
CN111160891A (zh) * 2020-04-08 2020-05-15 优比付(杭州)科技有限公司 一种余款催收方法及催收***
CN111833031A (zh) * 2020-06-28 2020-10-27 深圳市融壹买信息科技有限公司 一种扣款处理方法、装置、终端设备及存储介质
CN113971559A (zh) * 2021-10-28 2022-01-25 中国银行股份有限公司 一种还款处理方法及***
CN116862668B (zh) * 2023-09-05 2023-11-24 杭州度言软件有限公司 一种提升催收效率的智能催收方法

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104361487A (zh) * 2014-10-29 2015-02-18 中国建设银行股份有限公司 ***跨行自动还款的方法及装置
CN105205716A (zh) * 2015-10-28 2015-12-30 平安科技(深圳)有限公司 ***还款方法和装置
CN105894264A (zh) * 2016-03-31 2016-08-24 宇龙计算机通信科技(深圳)有限公司 基于信贷付款方式的付款方法、付款装置和终端

Family Cites Families (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101140683A (zh) * 2007-10-23 2008-03-12 中国工商银行股份有限公司 一种用于实现提前还款的约转账户处理***和方法
CN106952156A (zh) * 2017-03-08 2017-07-14 中国银行股份有限公司 一种分期还款计划的生成方法及装置

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104361487A (zh) * 2014-10-29 2015-02-18 中国建设银行股份有限公司 ***跨行自动还款的方法及装置
CN105205716A (zh) * 2015-10-28 2015-12-30 平安科技(深圳)有限公司 ***还款方法和装置
CN105894264A (zh) * 2016-03-31 2016-08-24 宇龙计算机通信科技(深圳)有限公司 基于信贷付款方式的付款方法、付款装置和终端

Also Published As

Publication number Publication date
CN108711047A (zh) 2018-10-26
CN108711047B (zh) 2023-04-18

Similar Documents

Publication Publication Date Title
WO2019196257A1 (zh) 一种自动还款方法、***及终端设备
WO2021213250A1 (zh) 安全业务交易
US8392328B2 (en) Methods and apparatus for funding transactions using debit cards issued by one institution and funds from accounts at other institutions
CN106384281A (zh) 保单贷款处理方法和装置
CN110020936B (zh) 基于区块链的资产管理方法及装置、电子设备
US11042930B1 (en) Insufficient funds predictor
CN109285069B (zh) 资源转移方法、装置及服务器
CN109146148B (zh) 一种余额预测偏差原因的确定方法及装置
WO2018107597A1 (zh) 数据处理的方法、装置及资金管理服务器
CN109034990B (zh) 记账方法、装置及电子设备
CN110188990A (zh) 一种资源请求和资金请求分流方法、装置及设备
US20130013506A1 (en) Variable Service Fee For Overdraft Protection
CN111192138A (zh) 交易数据的计息处理方法、装置和设备
CN111008895A (zh) 一种互联网金融的还款方法、装置、设备及存储介质
CN108694588B (zh) 虚拟资源请求方法及终端设备
CN112016914B (zh) 资源管控、资金管控方法、装置和设备
CN112734561A (zh) 用于票据***的处理方法和装置
US20100312675A1 (en) Systems and Methods for Reporting Chargebacks
WO2021198764A1 (en) Transaction lifecycle monitoring
US11276065B2 (en) Transaction lifecycle monitoring
US8566241B2 (en) Deposit pending check clearance
CN114282921A (zh) 预付卡处理方法、装置、计算机设备以及存储介质
CN114444120A (zh) 一种基于区块链的融资方法、装置、电子设备和存储介质
CN113989001A (zh) 虚拟资产结算方法、装置、电子设备以及存储介质
CN110046976B (zh) 对账方法和装置、服务器

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 18914611

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

32PN Ep: public notification in the ep bulletin as address of the adressee cannot be established

Free format text: NOTING OF LOSS OF RIGHTS PURSUANT TO RULE 112(1) EPC (EPO FORM 1205A DATED 21/01/2021)

122 Ep: pct application non-entry in european phase

Ref document number: 18914611

Country of ref document: EP

Kind code of ref document: A1