Data processing method and device, equipment, storage medium and program product
By obtaining and prioritizing repayment accounts, users can complete repayment of multiple repayment accounts at one time, simplifying the operation process and improving the success rate, solving the problems of cumbersome repayment and failure risks of users.
Patent Information
- Application Number
- CN202411372583.0
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-09-29
- Publication Date
- 2025-01-07
AI Technical Summary
When a user makes a repayment, there are multiple repayment accounts, which leads to cumbersome repayment operations, and may lead to excessive amounts of user repayment amounts transferred to the specified account, increasing the risk of repayment failure.
By obtaining the target parameters of each repayment account, determining priority, and dividing the repayment amount into sub-amounts, the repayment of all repayment accounts is achieved in one go, simplifying the repayment operation process, and the basis of making an appointment for repayment It can avoid transferring too much amount in the specified account and improve the repayment success rate.
It realizes that all repayment accounts can be completed without multiple operations by users, improves user experience, and guarantees the repayment success rate through appointment repayment, avoiding the failure of repayment.
Smart Images
Figure CN119273338A_ABST
Abstract
Description
Technical Field
[0001] The present application belongs to the field of big data processing technology, and in particular, relates to a data processing method, device, equipment, storage medium and program product. Background Art
[0002] With the change of people's consumption concepts and the diversification of purchasing methods, more and more users are purchasing items by advance consumption, which involves repayment.
[0003] In the exemplary technology, the user transfers the amount to the repayment account to make the repayment. However, the user may have multiple repayment accounts, and the user needs to transfer the repayment amount to the repayment account one by one, which makes the user's repayment operation more complicated. Summary of the invention
[0004] The embodiments of the present application provide a data processing method, apparatus, device, storage medium and program product for solving the problem that user repayment operations are relatively complicated.
[0005] In a first aspect, an embodiment of the present application provides a data processing method, including:
[0006] Receiving a repayment request and obtaining a customer ID of a repayment user associated with the repayment request;
[0007] In response to the scheduled repayment information associated with the customer identifier, determining the repayment amount of the repaying user in the designated account associated with the customer identifier;
[0008] Obtaining target parameters of each repayment account associated with the customer identifier, and determining the priority of the corresponding repayment account according to the target parameters, wherein the target parameters include the remaining balance and the number of overdue days;
[0009] According to the priority of each repayment account, the repayment amount is divided into sub-amounts corresponding to each repayment account;
[0010] Each of the sub-amounts is transferred to a corresponding repayment account, and the target parameters of each of the repayment accounts are updated.
[0011] In some possible implementations, the step of determining the repayment amount of the repayment user in the designated account associated with the customer identifier includes:
[0012] In response to detecting that the designated account associated with the customer identifier receives the repayment amount transferred by the repayment user, setting a first locking identifier for the customer identifier, and controlling a first process associated with the first locking identifier to determine the repayment amount of the repayment user in the designated account associated with the customer identifier;
[0013] The transferring of each sub-amount to the corresponding repayment account includes:
[0014] Setting a second locking mark for each of the repayment accounts;
[0015] Controlling the second process associated with the second locking identifier to transfer each of the sub-amounts to a corresponding repayment account;
[0016] The first locking mark of the customer mark is released, and the second locking mark of each of the repayment accounts is released.
[0017] In some possible implementations, after the step of obtaining the customer identifier of the repayment user associated with the repayment request, the step further includes:
[0018] Obtaining the reservation request information of the client identifier in the reservation information table;
[0019] In response to the status of the reservation request information being a valid status, determining the customer identifier associated with the reservation repayment information.
[0020] Some possible implementations also include:
[0021] In response to the reservation information table not including the reservation request information or the reservation request information being in an invalid state, determining whether the customer identifier is associated with binding information of a financial card;
[0022] In response to the customer identification being associated with the binding information, determining that the customer identification is associated with scheduled repayment information.
[0023] In some possible implementations, before the step of receiving the repayment request, the step further includes:
[0024] Receiving a scheduled repayment request sent by a terminal device associated with the repayment user;
[0025] In the reservation information table, the reservation request information corresponding to the customer identification is configured, and the state of the reservation request information is set to a valid state.
[0026] In some possible implementations, after the step of setting the status of the reservation request information to a valid status, the method further includes:
[0027] receiving a reservation cancellation request sent by the terminal device;
[0028] The state of the reservation request information is set from a valid state to an invalid state.
[0029] In some possible implementations, after the step of transferring each of the sub-amounts to the corresponding repayment account, the method further includes:
[0030] Determine a refund amount based on the repayment amount and each of the sub-amounts;
[0031] The refund amount is transferred to the target account, where the target account is the account from which the repayment amount is transferred to the designated account.
[0032] In a second aspect, an embodiment of the present application provides a data processing device, including:
[0033] A receiving module, used to receive a repayment request and obtain a customer identifier of a repayment user associated with the repayment request;
[0034] a determination module, configured to determine, in response to the scheduled repayment information associated with the customer identifier, a repayment amount of the repaying user in a designated account associated with the customer identifier;
[0035] An acquisition module, used to acquire target parameters of each repayment account associated with the customer identifier, and determine the priority of the corresponding repayment account according to the target parameters, wherein the target parameters include the remaining balance and the number of overdue days;
[0036] A division module, used for dividing the repayment amount into sub-amounts corresponding to each repayment account according to the priority of each repayment account;
[0037] The transfer module is used to transfer each of the sub-amounts to a corresponding repayment account and update the target parameters of each repayment account.
[0038] In a third aspect, an embodiment of the present application provides a data processing device, comprising: a processor and a memory storing computer program instructions; when the processor executes the computer program instructions, the data processing method as described above is implemented.
[0039] In a fourth aspect, an embodiment of the present application provides a computer-readable storage medium, characterized in that computer program instructions are stored on the computer-readable storage medium, and when the computer program instructions are executed by a processor, the data processing method as described above is implemented.
[0040] In a fifth aspect, an embodiment of the present application provides a computer program product. When instructions in the computer program product are executed by a processor of an electronic device, the electronic device is enabled to perform the data processing method as described above.
[0041] The data processing method, apparatus, device, storage medium and program product of the embodiments of the present application receive a repayment request and obtain a customer identification of a repayment user associated with the repayment request, when the customer identification is associated with the scheduled repayment information, determine the repayment amount of the repayment user in a designated account associated with the customer identification, obtain the target parameters of each repayment account associated with the customer identification, determine the priority of the repayment account through the target parameters, and then divide the repayment amount into sub-amounts corresponding to multiple repayment accounts based on the priority of each repayment account, transfer each sub-amount to the corresponding repayment account, and then update the target parameters of each repayment account. In the present application, the priority of the repayment account is determined by the target parameters of each repayment account, and the repayment amount remaining in the designated account is then split into sub-amounts of the repayment account according to the priority of each repayment account, so that the repayment of all repayment accounts can be completed at one time, without the need for users to perform multiple repayment operations, thereby simplifying the repayment operation process and improving the user experience; in addition, the user's repayment is implemented on the basis of scheduled repayment. Based on the appointment method, it can avoid the transfer of too many users' repayment amounts into the designated account, thereby avoiding the situation where the repayment amounts of too many users exist in the designated account and causing repayment failures. That is, based on scheduled repayment, the user's repayment success rate can be guaranteed, and the user does not need to perform repeated repayment operations, further improving the user experience. BRIEF DESCRIPTION OF THE DRAWINGS
[0042] In order to more clearly illustrate the technical solution of the embodiments of the present application, the following is a brief introduction to the drawings required for use in the embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without any creative work.
[0043] Figure 1 It is a schematic diagram of the scenario involved in the data processing method of this application;
[0044] Figure 2 It is a flowchart of the first embodiment of the data processing method of the present application;
[0045] Figure 3 It is a flowchart of the second embodiment of the data processing method of the present application;
[0046] Figure 4 It is a flowchart of the third embodiment of the data processing method of the present application;
[0047] Figure 5 is a flowchart of the fourth embodiment of the data processing method of the present application;
[0048] Figure 6 It is a functional module schematic diagram of the data processing device of the present application;
[0049] Figure 7 It is a structural diagram of the data processing device of this application. DETAILED DESCRIPTION
[0050] The features and exemplary embodiments of various aspects of the present application will be described in detail below. In order to make the purpose, technical solutions and advantages of the present application clearer, the present application will be further described in detail below in conjunction with the accompanying drawings and specific embodiments. It should be understood that the specific embodiments described herein are only intended to explain the present application, rather than to limit the present application. For those skilled in the art, the present application can be implemented without the need for some of these specific details. The following description of the embodiments is only to provide a better understanding of the present application by illustrating the examples of the present application.
[0051] It should be noted that, in this article, relational terms such as first and second, etc. are only used to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Moreover, the terms "include", "comprise" or any other variants thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, the elements defined by the statement "include..." do not exclude the presence of other identical elements in the process, method, article or device including the elements.
[0052] It should be noted that the acquisition, storage, use and processing of data in the embodiments of the present application are in compliance with the relevant provisions of national laws and regulations.
[0053] It should be noted that in the embodiments of the present application, certain software, components, models and other existing solutions in the industry may be mentioned, and they should be regarded as exemplary. Their purpose is only to illustrate the feasibility of implementing the technical solution of the present application, but it does not mean that the applicant has or will necessarily use the solution.
[0054] With the change of people's consumption concept and the diversification of the way of purchasing goods, more and more users adopt the way of advance consumption to purchase goods, and advance consumption involves repayment. In the exemplary technology, the user transfers the amount to the repayment account to repay.
[0055] The inventor of the present application discovered that a user may have multiple repayment accounts, and the user needs to transfer the repayment amount to the repayment account one by one, which makes the user's repayment operation more cumbersome.
[0056] The inventor of the present application therefore came up with the idea of determining the priority of the repayment account by the target parameters of each repayment account, and then splitting the repayment amount remaining in the designated account into sub-amounts of the repayment account by the priority of each repayment account, so as to complete the repayment of all repayment accounts at one time without the need for the user to perform multiple repayment operations, thereby simplifying the repayment operation process and improving the user experience; in addition, the user's repayment is implemented on the basis of scheduled repayment, and the appointment-based method can avoid the transfer of too many users' repayment amounts into the designated account, thereby avoiding the situation where the repayment amounts of too many users exist in the designated account and causing repayment failures, that is, the user's repayment success rate can be guaranteed based on scheduled repayment, and the user does not need to perform repeated repayment operations, further improving the user experience.
[0057] Reference Figure 1 , Figure 1 This is a schematic diagram of the scenario of the data processing method of this application. Figure 1 The data processing device 100 receives a repayment request sent by a terminal device 300 associated with a repayment user 200, and the data processing device 100 obtains a customer identifier associated with the repayment user 200. When the customer identifier is associated with the scheduled repayment information, the data processing device 100 determines the repayment amount of the repayment user in the designated account 110 associated with the customer identifier. The data processing device 100 obtains the target parameters of each repayment account 120 associated with the customer identifier, determines the priority of each repayment account 120 based on the target parameters, and divides the repayment amount into sub-amounts of each repayment account 120 according to the priority, and then transfers each sub-amount to the corresponding repayment account 120, and updates the target parameters such as the remaining amount and overdue days of the repayment account 120.
[0058] The following combination Figure 1 , the data processing method of this application is described in detail.
[0059] Reference Figure 2 , Figure 2 FIG. 1 is a flow chart of a first embodiment of a data processing method of the present application. The data processing method includes:
[0060] Step S201, receiving a repayment request, and obtaining a customer identifier of a repayment user associated with the repayment request.
[0061] In this embodiment, the execution subject is a data processing device. For the convenience of description, the term "device" is used to refer to the data processing device. The device can be a server or any terminal device with a repayment function.
[0062] The repayment user sends a repayment request to the device through the terminal device, and the repayment request carries the device identification of the terminal device. The device stores relevant information of the repayment user, including the device identification of the terminal device and the customer identification associated with the device identification. The device identification is, for example, the model or serial number of the terminal device, and the customer identification refers to the unique identification used by the repayment user for repayment. The customer identification is a unique number or letter, or a combination of numbers and letters. The customer identification can be set by the device based on the basic information of the repayment user, such as telephone information or identity information.
[0063] After obtaining the repayment request, the device parses the repayment request, obtains the device identification of the terminal device, and then obtains the customer identification associated with the device identification.
[0064] Step S202, in response to the scheduled repayment information associated with the customer identifier, determining the repayment amount of the repaying user in the designated account associated with the customer identifier.
[0065] Before making a repayment, the repaying user needs to make a repayment reservation. After the repaying user makes a repayment reservation, the device will set the scheduled repayment information associated with the customer ID. In this regard, after the device obtains the customer ID, it detects whether the customer ID is associated with the scheduled repayment information. If the customer ID is associated with the scheduled repayment information, the device can accept the repayment request, and the device sends information containing the designated account to the terminal device, so that the repaying user transfers the repayment amount to the designated account through the terminal device.
[0066] After the repaying user transfers the repayment amount to the designated account, the designated account sends information to the device, which includes the repayment amount and the customer ID. Based on the information, the device can determine the repayment amount of the repaying user in the designated account associated with the customer ID.
[0067] Step S203, obtaining target parameters of each repayment account associated with the customer identifier, and determining the priority of the corresponding repayment account according to the target parameters, wherein the target parameters include the remaining balance and the number of overdue days.
[0068] After the device determines the repayment amount, since the repaying user has multiple repayment accounts, the device needs to generate a repayment plan to complete the repayment amount required for each repayment account at one time. The repayment account refers to the account where the repaying user withdraws the amount of advance consumption. The repaying user needs to transfer the repayment amount to the repayment account to complete the repayment of the amount of advance consumption.
[0069] Specifically, the device stores various repayment accounts of repayment users. The repayment accounts can be added by users in the device. The device associates and stores customer identifiers with various repayment accounts. The device obtains target parameters for each repayment account. The target parameters include the remaining balance and the number of overdue days. The remaining balance refers to the amount of money that the repayment user can withdraw from the repayment account, and the repayment account has an upper limit. The upper limit minus the remaining balance is the amount that the repayment user needs to repay. The number of overdue days refers to the time difference between the current date and the repayment date set for the repayment account. For example, if the number of overdue days is -7 days, it means that there are 7 days left until the repayment deadline for the repayment account; if the overdue day is 7 days, it means that the repayment account is overdue for 7 days.
[0070] After obtaining the target parameters, the device determines the priority of each repayment account based on the target parameters.
[0071] In one example, the device first determines the weights corresponding to the overdue days and the amount of repayment required of the repayment account, determines the value corresponding to the overdue days based on the overdue days, performs weighted calculation on the value of the overdue days, the amount of repayment required, the weight corresponding to the overdue days, and the weight of the amount of repayment required to obtain a repayment score, and the device sorts each repayment account in descending order of the repayment score of each repayment account, and the priority of the repayment account in the front ranking is set to be greater than the priority of the repayment account after the sorting disaster. It should be noted that the smaller the overdue days, the larger the value corresponding to the overdue days. For example, the value corresponding to the overdue days of -14 days is greater than the value corresponding to the expected days of -7, and the weight when the overdue days is a negative number is set to be greater than the weight when the expected days are non-negative. The sum of the weight of the overdue days and the weight corresponding to the amount of repayment required is 1.
[0072] In another example, the target parameter also includes the repayment record of the repayment account. The device obtains the repayment amount and repayment time of the user in the repayment account from the repayment record, and determines the repayment rule of the user based on each repayment amount and repayment time. For example, the user repays one quarter of the required repayment in the first half of each month and repays the remaining amount in the middle of each month. The device sets the priority according to the repayment rule. Specifically, the repayment rule involves time and repayment ratio. The earlier the time, the smaller the score corresponding to the time. The product between the score and the repayment ratio is used as the repayment score, or the product of the score, the value corresponding to the overdue days and the repayment ratio is used as the repayment score, or the product of the score, the value corresponding to the overdue days, the weight and the repayment ratio is used as the repayment score. The device sets the priority of each repayment account based on the repayment score of each repayment account, that is, sorts each repayment account in descending order of the repayment score of each repayment account, and the priority of the repayment account ranked first is set to be greater than the priority of the repayment account ranked after the disaster.
[0073] Step S204: Divide the repayment amount into sub-amounts corresponding to each repayment account according to the priority of each repayment account.
[0074] After determining the priority of each repayment account, the device divides the repayment amount into sub-amounts corresponding to each repayment account based on the priority. And the higher the priority of the repayment account, the device first divides the repayment amount required for the repayment account from the repayment amount, and the divided amount is defined as the sub-amount of the repayment account. Exemplarily, the priority of repayment account A is higher than that of repayment account B, and the priority of repayment account B is higher than that of repayment account C. The repayment amount required for repayment account A is 800, the repayment amount required for repayment account B is 900, and the repayment amount required for repayment account C is 700. The repayment amount is 2500, then the repayment account A is allocated a sub-amount of 800, and then the repayment account B is allocated an amount of 900, and finally the repayment account C is allocated a sub-amount of 800.
[0075] Step S205: transfer each sub-amount to the corresponding repayment account, and update the target parameters of each repayment account.
[0076] After the device obtains the sub-amounts of each repayment account, it sends a repayment instruction to the designated account, and the designated account parses the repayment instruction to obtain the sub-amounts of each repayment account. The repayment account then transfers each sub-amount to the corresponding repayment account to complete the repayment. In addition, after the repayment is completed, the repayment account can directly send a reminder message of the repayment completion to the terminal device, or send a reminder message of the repayment completion to the terminal device through the device.
[0077] In this embodiment, a repayment request is received, and a customer identification of a repayment user associated with the repayment request is obtained; when the customer identification is associated with scheduled repayment information, the repayment amount of the repayment user in a designated account associated with the customer identification is determined; the target parameters of each repayment account associated with the customer identification are obtained; the priority of the repayment account is determined through the target parameters; the repayment amount is divided into sub-amounts corresponding to multiple repayment accounts based on the priority of each repayment account; each sub-amount is transferred to a corresponding repayment account; and the target parameters of each repayment account are updated. In this embodiment, the priority of the repayment account is determined by the target parameters of each repayment account, and the repayment amount remaining in the designated account is then split into sub-amounts of the repayment account according to the priority of each repayment account, so that the repayment of all repayment accounts is completed at one time, without the need for the user to perform multiple repayment operations, thereby simplifying the repayment operation process and improving the user experience; in addition, the user's repayment is implemented on the basis of scheduled repayment. Based on the appointment method, it is possible to avoid the transfer of too many users' repayment amounts into the designated account, thereby avoiding the situation where the repayment amounts of too many users exist in the designated account and causing repayment failures. That is, based on scheduled repayment, the user's repayment success rate can be guaranteed, and the user does not need to perform repeated repayment operations, further improving the user experience.
[0078] In one embodiment, after detecting the scheduled repayment information associated with the customer identification, the device detects whether the repaying user transfers the repayment into the designated account. If it is detected that the designated account associated with the customer identification receives the designated amount transferred by the repaying user, the device sets a first locking mark for the customer identification. The function of the first locking mark is to indicate that there is a process executing the repayment of the repaying user corresponding to the customer identification, and no other process is required to interfere with the repayment of this repaying user. The first locking mark can be associated with an idle process, which is defined as the first process. The device controls the first process to determine the repayment amount of the repaying user in the designated account associated with the customer identification.
[0079] After the device determines the sub-amount of each repayment account, a second lock mark is set for each repayment account. The second lock mark is used to indicate that a process is repaying the repayment account and other processes are required to repay the repayment account. The second lock mark can be associated with an idle process as the second process. The device controls the second process to transfer each sub-amount to the corresponding repayment account.
[0080] After completing the repayment of each repayment account, the device releases the first lock mark of the customer ID and releases the second lock mark of the repayment account. It should be noted that the first lock mark and the second lock mark have a certain time limit. For example, the time limit of the first lock mark set for the customer ID is 5 minutes. After 5 minutes, if the first process still fails to successfully detect that the designated ID has a repayment amount transferred by the repayment user, the repayment fails, and the device sends a reminder message of repayment failure to the terminal device; the second lock mark can be set for 3 minutes. If it exceeds 3 minutes, the second process has not transferred all the sub-amounts to the corresponding repayment account, the device outputs a reminder message of repayment failure, and the reminder message is used to indicate the repayment failure reminder message of the repayment account that has not transferred the sub-amount.
[0081] In this embodiment, a lock mark is set for the customer ID and the repayment account to prevent other processes from interfering with the repayment, avoid the situation where too many processes execute repayments and cause repayment failures, thereby improving the repayment success rate and reducing the number of repeated repayments by users, thereby improving the user experience.
[0082] Reference Figure 3 , Figure 3 This is a flow chart of the second embodiment of the data processing method of the present application. Based on the first embodiment, after step S201, it further includes:
[0083] Step S301, obtaining the reservation request information of the client identifier in the reservation information table.
[0084] Step S302: in response to the status of the reservation request information being valid, determining the customer identifier associated with the reservation repayment information.
[0085] In this embodiment, the repaying user needs to make an appointment for repayment in the device. If the appointment is successful, the device will add the appointment request information associated with the customer identifier in the appointment information table.
[0086] In this regard, after obtaining the customer identification, the device determines whether the customer identification contains associated reservation request information in the reservation information. When the customer identification has associated reservation request information in the reservation information table, it can be determined that the repayment user has made a scheduled repayment. The device then determines the status of the reservation request information. If the status of the reservation request information is valid, the repayment user has successfully made the scheduled repayment, and the repayment can be made for the repayment user, that is, the device determines that the customer identification is associated with the scheduled repayment information.
[0087] When the reservation information table does not contain the reservation request information or the status of the reservation request information is invalid, it can be determined that the user has no reservation or the reservation has failed. For example, if the reservation information table does not contain the reservation request information, the user has not made a reservation; if the status of the reservation request information is invalid. It can be determined that the user's reservation has failed. In this case, if the repayment user has bound a financial card, the device can respond to the repayment request to carry out the repayment user's request. In this regard, when the reservation information table does not contain the reservation request information or the status of the reservation request information is invalid, the device determines whether the customer identification is associated with the binding information of the financial card. If the customer identification is associated with the binding information, it can be determined that the repayment user has bound the financial card to the designated account and is in a long-term reservation repayment state. The device can determine that the customer identification is associated with the reservation repayment information, that is, it can respond to the repayment user's repayment request.
[0088] It should be noted that when the reservation information table does not contain reservation request information or the status of the reservation request information is invalid, and the repayment user has not bound a bank card, and the repayment account has the repayment amount of the repayment user, the repayment amount will be used as the refund amount, and the refund amount will be transferred to the target account. The target account refers to the account from which the repayment amount is transferred to the designated account.
[0089] In this embodiment, the device obtains the reservation request information of the customer identifier in the reservation information table. If the status of the reservation request information is valid, it is determined that the customer identifier is associated with the reservation repayment information, and the device can respond to the repayment request, so that users who have not made reservation repayments cannot make repayments, avoiding the device from having to process too many users' repayment requests, ensuring the stable operation of the device, and thus ensuring that the repayment users who have made reservation repayments can successfully repay.
[0090] Reference Figure 4 , Figure 4 This is a flowchart of the third embodiment of the data processing method of the present application. Based on the second embodiment, before step S201, it also includes:
[0091] Step S401: receiving a scheduled repayment request sent by a terminal device associated with a repayment user.
[0092] Step S402: In the reservation information table, the reservation request information corresponding to the customer identifier is configured, and the state of the reservation request information is set to a valid state.
[0093] In this embodiment, the repaying user needs to make a repayment reservation before repaying. The repaying user sends a repayment reservation request to the device based on the terminal device, that is, the device receives the repayment reservation request sent by the terminal device associated with the repaying user.
[0094] After receiving the scheduled repayment request, the device parses the scheduled repayment request to obtain the device identification of the terminal device, then obtains the customer identification associated with the device identification, configures the scheduled request information corresponding to the customer identification in the scheduled information table, and sets the status of the scheduled request information to a valid status.
[0095] Further, the repaying user can cancel the repayment reservation. After the state of the reservation request information is set to the valid state, if the device receives a reservation cancellation request sent by the terminal device, the state of the reservation request information is changed from the valid state to the invalid state in the reservation information table.
[0096] The reservation information table includes reservation request information in a valid state and invalid reservation request information. The device can count the number of reservation requests for each user. If the number of reservation requests is greater than the preset number, it can be determined that the user may be abusing the reservation repayment function. The device outputs a prompt message to the terminal device to prompt that the remaining cancellation number of the reservation repayment is less than the target number, so that the repaying user will carefully cancel the reservation repayment.
[0097] In this embodiment, the device receives a scheduled repayment request sent by a terminal device associated with the repayment user, and configures the reservation request information corresponding to the customer identifier in the reservation information table based on the scheduled repayment request, and sets the status of the reservation request information to a valid status, thereby ensuring that the device helps the repayment user to repay in advance of the scheduled repayment by the repayment user.
[0098] Reference Figure 5 , Figure 5 This is a flowchart of a fourth embodiment of the data processing method of the present application, based on any one of the first to third embodiments, after step S205, further comprising:
[0099] Step S501, determine the refund amount according to the repayment amount and each sub-amount.
[0100] Step S502, the refund amount is transferred to the target account, and the target account is the account from which the repayment amount is transferred to the designated account.
[0101] In this embodiment, after the repayment is completed, there may be a refund. Specifically, the device determines the refund amount based on the repayment amount and each sub-amount. Specifically, the sum of each sub-amount is calculated first, and the refund amount is obtained by subtracting the sum of each sub-amount from the repayment amount.
[0102] The device transfers the refund amount to the target account, which is the account from which the repayment amount is transferred to the designated account.
[0103] Furthermore, a refund timer task is initiated every few minutes to query the records in the refund registration table according to the registration date and status. During the traversal process, if the refund information in the initial state is queried, the refund record status is changed to "processing", and a transfer transaction is initiated to transfer the refund amount in the specified account to the target account. The refund registration table and refund transaction details table are updated according to the returned results.
[0104] If refund information in an unknown state is found during the traversal process, or if no confirmed return result information is obtained after calling the transfer transaction, it is necessary to actively call the query transaction status transaction to determine whether the refund is successful.
[0105] In addition, after the daily transfer repayment is completed, a day-end reconciliation is required. First, three tables need to be synchronized: account details, refund transaction details, and repayment transaction details. Account details refer to the table of transfers in and out of the repayment account. First, you need to scan the three tables to confirm that all transactions are in the intermediate state of "unknown" or "processing", otherwise you need to query the transaction results to ensure that the transaction is in the result state of "success" or "failure". After the three detailed tables are scanned, start the reconciliation. Make sure that each record in the account details is the sum of the repayment amount and the refund amount. After the reconciliation is completed, output the reconciliation file and list.
[0106] In this embodiment, if there is a refund amount, the device will return the refund amount, thereby ensuring that the repaying user will not pay more than the amount, thereby improving the user experience.
[0107] See also Figure 6 , the data processing device 600 provided in the embodiment of the present application, the data processing device 600 includes:
[0108] The receiving module 610 is used to receive a repayment request and obtain a customer identifier of a repayment user associated with the repayment request;
[0109] A determination module 620, for determining the repayment amount of the repaying user in the designated account associated with the customer identifier in response to the scheduled repayment information associated with the customer identifier;
[0110] The acquisition module 630 is used to acquire the target parameters of each repayment account associated with the customer identifier, and determine the priority of the corresponding repayment account according to the target parameters, wherein the target parameters include the remaining balance and the number of overdue days;
[0111] A division module 640, for dividing the repayment amount into sub-amounts corresponding to each repayment account according to the priority of each repayment account;
[0112] The transfer module 650 is used to transfer each sub-amount to a corresponding repayment account and update the target parameters of each repayment account.
[0113] In one embodiment, the data processing device 600 is specifically configured to:
[0114] In response to detecting that the designated account associated with the customer identifier receives the repayment amount transferred by the repayment user, a first locking identifier is set for the customer identifier, and a first process associated with the first locking identifier is controlled to determine the repayment amount of the repayment user in the designated account associated with the customer identifier;
[0115] Transfer each sub-amount to the corresponding repayment account including:
[0116] Setting a second locking mark for each repayment account;
[0117] Controlling the second process associated with the second locking identifier to transfer each sub-amount to a corresponding repayment account;
[0118] The first locking mark of the customer mark is released, and the second locking mark of each repayment account is released.
[0119] In one embodiment, the data processing device 600 is specifically configured to:
[0120] Get the reservation request information of the customer ID in the reservation information table;
[0121] In response to the status of the reservation request information being a valid status, determining the customer identifier associated with the reservation repayment information.
[0122] In one embodiment, the data processing device 600 is specifically configured to:
[0123] In response to the reservation information table not including the reservation request information or the reservation request information being in an invalid state, determining whether the customer identification is associated with the binding information of the financial card;
[0124] In response to the customer identification-associated binding information, the customer identification-associated scheduled repayment information is determined.
[0125] In one embodiment, the data processing device 600 is specifically configured to:
[0126] Receiving a scheduled repayment request sent by a terminal device associated with the repayment user;
[0127] In the appointment information table, configure the appointment request information corresponding to the customer ID, and set the status of the appointment request information to a valid status.
[0128] In one embodiment, the data processing device 600 is specifically configured to:
[0129] Receiving a reservation cancellation request sent by a terminal device;
[0130] Set the status of the reservation request information from valid to invalid.
[0131] In one embodiment, the data processing device 600 is specifically configured to:
[0132] Determine the refund amount based on the repayment amount and each sub-amount;
[0133] The refund amount is transferred to the target account, which is the account from which the repayment amount is transferred to the designated account.
[0134] Each module of the data processing device provided in the embodiment of the present application can realize Figures 2 to 5 Any embodiment provides the functions of each step of the data processing method and can achieve its corresponding technical effect. For the sake of concise description, it will not be repeated here.
[0135] Figure 7 A schematic diagram of the hardware structure of a data processing device provided in an embodiment of the present application is shown.
[0136] The data processing device may include a processor 701 and a memory 702 storing computer program instructions.
[0137] Specifically, the processor 701 may include a central processing unit (CPU), or an application specific integrated circuit (ASIC), or may be configured to implement one or more integrated circuits of the embodiments of the present application.
[0138] The memory 702 may include a large capacity memory for data or instructions. By way of example and not limitation, the memory 702 may include a hard disk drive (HDD), a floppy disk drive, a flash memory, an optical disk, a magneto-optical disk, a magnetic tape, or a universal serial bus (USB) drive or a combination of two or more of these. In appropriate cases, the memory 702 may include a removable or non-removable (or fixed) medium. In appropriate cases, the memory 702 may be inside or outside the integrated gateway disaster recovery device. In a specific embodiment, the memory 702 is a non-volatile solid-state memory.
[0139] In certain embodiments, the memory 702 may include a read-only memory (ROM), a random access memory (RAM), a magnetic disk storage media device, an optical storage media device, a flash memory device, an electrical, optical or other physical / tangible memory storage device. Thus, in general, the memory includes one or more tangible (non-transitory) computer-readable storage media (e.g., a memory device) encoded with software including computer-executable instructions, and when the software is executed (e.g., by one or more processors), it is operable to perform the operations described with reference to the method according to an aspect of the present disclosure.
[0140] The processor 701 implements any one of the authentication methods in the above embodiments by reading and executing computer program instructions stored in the memory 702 .
[0141] In one example, the data processing device may further include a communication interface 703 and a bus 710. Figure 7 As shown, the processor 701, the memory 702, and the communication interface 703 are connected via a bus 710 and communicate with each other.
[0142] The communication interface 703 is mainly used to implement communication between various modules, devices, units and / or equipment in the embodiments of the present application.
[0143] Bus 710 includes hardware, software or both, and the parts of online data flow billing equipment are coupled to each other. For example, but not limitation, bus may include accelerated graphics port (AGP) or other graphics bus, enhanced industrial standard architecture (EISA) bus, front-end bus (FSB), hypertransport (HT) interconnection, industrial standard architecture (ISA) bus, infinite bandwidth interconnection, low pin count (LPC) bus, memory bus, micro channel architecture (MCA) bus, peripheral component interconnection (PCI) bus, PCI-Express (PCI-X) bus, serial advanced technology attachment (SATA) bus, video electronics standard association local (VLB) bus or other suitable bus or two or more of these combinations. In appropriate cases, bus 710 may include one or more buses. Although the present application embodiment describes and shows a specific bus, the present application considers any suitable bus or interconnection.
[0144] The data processing method in the above embodiment can be implemented by providing a computer storage medium in the present application embodiment. The computer storage medium stores computer program instructions; when the computer program instructions are executed by a processor, any one of the data processing methods in the above embodiment is implemented.
[0145] An embodiment of the present application also provides a computer program product, including a computer program, which implements any one of the data processing methods in the above embodiments when the computer program is processed and executed.
[0146] It should also be noted that the exemplary embodiments mentioned in this application describe some methods or systems based on a series of steps or devices. However, this application is not limited to the order of the above steps, that is, the steps can be performed in the order mentioned in the embodiment, or in a different order from the embodiment, or several steps can be performed simultaneously.
[0147] Aspects of the present disclosure are described above with reference to the flowchart and / or block diagram of the method, device (system) and computer program product according to the embodiment of the present disclosure. It should be understood that each box in the flowchart and / or block diagram and the combination of each box in the flowchart and / or block diagram can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing device to produce a machine so that these instructions executed by the processor of the computer or other programmable data processing device enable the implementation of the function / action specified in one or more boxes of the flowchart and / or block diagram. Such a processor can be, but is not limited to, a general-purpose processor, a special-purpose processor, a special application processor, or a field programmable logic circuit. It can also be understood that each box in the block diagram and / or flowchart and the combination of boxes in the block diagram and / or flowchart can also be implemented by dedicated hardware that performs a specified function or action, or can be implemented by a combination of dedicated hardware and computer instructions.
[0148] The above are only specific implementation methods of the present application. Those skilled in the art can clearly understand that for the convenience and simplicity of description, the specific working processes of the systems, modules and units described above can refer to the corresponding processes in the aforementioned method embodiments, and will not be repeated here. It should be understood that the protection scope of the present application is not limited to this. Any technician familiar with the technical field can easily think of various equivalent modifications or replacements within the technical scope disclosed in this application, and these modifications or replacements should be included in the protection scope of this application.
Claims
1. A data processing method, characterized in that: include: Receiving a repayment request and obtaining a customer ID of a repayment user associated with the repayment request; In response to the scheduled repayment information associated with the customer identifier, determining the repayment amount of the repaying user in the designated account associated with the customer identifier; Obtaining target parameters of each repayment account associated with the customer identifier, and determining the priority of the corresponding repayment account according to the target parameters, wherein the target parameters include the remaining balance and the number of overdue days; According to the priority of each repayment account, the repayment amount is divided into sub-amounts corresponding to each repayment account; Each of the sub-amounts is transferred to a corresponding repayment account, and the target parameters of each of the repayment accounts are updated.
2. The data processing method according to claim 1, characterized in that: The step of determining the repayment amount of the repayment user in the designated account associated with the customer identifier comprises: In response to detecting that the designated account associated with the customer identifier receives the repayment amount transferred by the repayment user, setting a first locking identifier for the customer identifier, and controlling a first process associated with the first locking identifier to determine the repayment amount of the repayment user in the designated account associated with the customer identifier; The transferring of each sub-amount to the corresponding repayment account includes: Setting a second locking mark for each of the repayment accounts; Controlling the second process associated with the second locking identifier to transfer each of the sub-amounts to a corresponding repayment account; The first locking mark of the customer mark is released, and the second locking mark of each of the repayment accounts is released.
3. The data processing method according to claim 1, characterized in that: After the step of obtaining the customer identification of the repayment user associated with the repayment request, the method further includes: Obtaining the reservation request information of the client identifier in the reservation information table; In response to the status of the reservation request information being a valid status, determining the customer identifier associated with the reservation repayment information.
4. The data processing method according to claim 3, characterized in that: Also includes: In response to the reservation information table not including the reservation request information or the reservation request information being in an invalid state, determining whether the customer identifier is associated with binding information of a financial card; In response to the customer identification being associated with the binding information, determining that the customer identification is associated with scheduled repayment information.
5. The data processing method according to claim 3, characterized in that: Before the step of receiving the repayment request, the method further includes: Receiving a scheduled repayment request sent by a terminal device associated with the repayment user; In the reservation information table, the reservation request information corresponding to the customer identification is configured, and the state of the reservation request information is set to a valid state.
6. The data processing method according to claim 5, characterized in that: After the step of setting the status of the reservation request information to a valid status, the method further includes: receiving a reservation cancellation request sent by the terminal device; The state of the reservation request information is set from a valid state to an invalid state.
7. The data processing method according to any one of claims 1 to 6, characterized in that: After the step of transferring each of the sub-amounts to the corresponding repayment account, the method further includes: Determine a refund amount based on the repayment amount and each of the sub-amounts; The refund amount is transferred to the target account, where the target account is the account from which the repayment amount is transferred to the designated account.
8. A data processing device, characterized in that: include: A receiving module, used to receive a repayment request and obtain a customer identifier of a repayment user associated with the repayment request; a determination module, configured to determine, in response to the scheduled repayment information associated with the customer identifier, a repayment amount of the repaying user in a designated account associated with the customer identifier; An acquisition module, used to acquire target parameters of each repayment account associated with the customer identifier, and determine the priority of the corresponding repayment account according to the target parameters, wherein the target parameters include the remaining balance and the number of overdue days; A division module, used for dividing the repayment amount into sub-amounts corresponding to each repayment account according to the priority of each repayment account; The transfer module is used to transfer each of the sub-amounts to a corresponding repayment account and update the target parameters of each repayment account.
9. A data processing device, characterized in that: The device comprises: a processor and a memory storing computer program instructions; when the processor executes the computer program instructions, the data processing method according to any one of claims 1 to 7 is implemented.
10. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores computer program instructions, and when the computer program instructions are executed by a processor, the data processing method according to any one of claims 1 to 7 is implemented.
11. A computer program product, characterized in that When the instructions in the computer program product are executed by a processor of an electronic device, the electronic device is enabled to execute the data processing method as described in any one of claims 1 to 7.