CN117312342A

CN117312342A - Repayment data processing method, repayment data processing device, repayment data processing equipment and storage medium

Info

Publication number: CN117312342A
Application number: CN202311266588.0A
Authority: CN
Inventors: 李瑞英; 吕雄; 殷钊
Original assignee: China Construction Bank Corp; CCB Finetech Co Ltd
Current assignee: China Construction Bank Corp; CCB Finetech Co Ltd
Priority date: 2023-09-27
Filing date: 2023-09-27
Publication date: 2023-12-29

Abstract

The application provides a repayment data processing method, device, equipment and storage medium, and belongs to the technical field of data processing and big data. The method comprises the following steps: determining first batch transfer state information of an online static database and second batch transfer state information of an online dynamic database in response to receiving payment information sent by a user terminal, wherein the payment information comprises payment amount and user identification; determining the payment undelivered amount and the payment total corresponding to the user identifier according to the user identifier, the first batch transfer state information, the second batch transfer state information and the payment amount; in response to receiving a repayment information inquiry request sent by a user terminal, reading a target repayment undelivered amount and a target repayment total corresponding to the user identifier; and sending the target repayment amount and the target repayment total amount to the user terminal. The method solves the problem that the current user can obtain the wrong query result when querying the repayment data.

Description

Repayment data processing method, repayment data processing device, repayment data processing equipment and storage medium

Technical Field

The present disclosure relates to the field of data processing and big data technologies, and in particular, to a repayment data processing method, device, equipment and storage medium.

Background

During the use of the credit card by the user, a repayment operation may be required, and the user may also typically view the change in the amount after repayment after the repayment operation.

Currently, in the prior art, the payment amount is usually recorded in a database, and in order to increase the response speed, the database is usually divided into two databases, one database changes data in real time during user transaction, and the other database synchronizes data in time.

However, the inventors found that at least the following technical problems exist in the prior art: when the current user inquires repayment data, an incorrect inquiry result can be obtained.

Disclosure of Invention

The application provides a repayment data processing method, device, equipment and storage medium, which are used for solving the problem that a user obtains an error query result when querying repayment data.

In a first aspect, the present application provides a payment data processing method, including: determining first batch transfer state information of an online static database and second batch transfer state information of an online dynamic database in response to receiving payment information sent by a user terminal, wherein the payment information comprises payment amount and user identification; determining the payment undelivered amount and the payment total corresponding to the user identifier according to the user identifier, the first batch transfer state information, the second batch transfer state information and the payment amount; in response to receiving a repayment information inquiry request sent by a user terminal, reading a target repayment undelivered amount and a target repayment total corresponding to the user identifier; and sending the target repayment amount and the target repayment total amount to the user terminal.

In one possible implementation manner, determining the payoff amount and the payoff total amount corresponding to the user identifier according to the user identifier, the first lot transfer state information, the second lot transfer state information and the payoff amount includes: if the first batch transfer state information and the second batch transfer state information are completed, reading the current repayment amount corresponding to the user identifier in the online static database; generating a repayment unread amount corresponding to the user identifier according to the repayment amount; and adding the current repayment amount and the repayment undelivered amount to obtain the repayment total corresponding to the user identifier.

In one possible implementation manner, determining the payoff amount and the payoff total amount corresponding to the user identifier according to the user identifier, the first lot transfer state information, the second lot transfer state information and the payoff amount includes: if the first transfer state information is completed and the second transfer state information is not completed, acquiring the current repayment amount corresponding to the user identifier, the current day repayment unded amount, an online transaction log and a clearing file, wherein the online transaction log comprises at least one transaction information, and the transaction information comprises the historical repayment amount; adding the repayment amount and the existing day repayment undelivered amount to obtain a new day repayment undelivered amount corresponding to the user identifier; determining transaction information which belongs to an online transaction log and does not belong to a clearing file as target transaction information; adding the historical payment amounts in each target transaction information to obtain a historical payment undelivered amount corresponding to the user identifier; adding the current repayment amount, the new current day repayment undelivered amount and the historical repayment undelivered amount corresponding to the user identifier to obtain the repayment total corresponding to the user identifier; and adding the new payment undelivered amount on the same day and the historical payment undelivered amount to obtain the payment undelivered amount corresponding to the user identifier.

In one possible implementation manner, determining the payoff amount and the payoff total amount corresponding to the user identifier according to the user identifier, the first lot transfer state information, the second lot transfer state information and the payoff amount includes: if the second transfer state information is completed and the first transfer state information is incomplete, acquiring an online transaction log and a clearing file corresponding to the user identifier, wherein the online transaction log comprises at least one transaction information, the transaction information comprises a historical repayment amount, and the transaction information corresponds to transaction time; if any transaction information belongs to an online transaction log and does not belong to a clearing file, and the corresponding transaction time is after the preset daily cut time and before the preset batch transfer completion time, determining any transaction information as target transaction information; adding the historical repayment amounts in the target transaction information to obtain target repayment amounts; reading the current repayment amount corresponding to the user identifier in the online static database; generating a payment undelivered amount on the same day according to the payment amount; adding the target payment amount and the current day payment undelivered amount to obtain the payment undelivered amount corresponding to the user identifier; and adding the payment undelivered amount and the current payment amount to obtain the total payment amount corresponding to the user identifier.

In one possible implementation manner, determining the payoff amount and the payoff total amount corresponding to the user identifier according to the user identifier, the first lot transfer state information, the second lot transfer state information and the payoff amount includes: if the first transfer state information and the second transfer state information are incomplete, the current repayment amount corresponding to the user identification in the online static database and the repayment unread amount corresponding to the user identification in the online dynamic database are read; and adding the current repayment amount and the repayment undelivered amount to obtain the repayment total.

In one possible implementation manner, after receiving the payment information sent by the user terminal, the method further includes: acquiring the receiving time of repayment information; periodically acquiring the current time and a clearing file; calculating the time difference of the current time and the receiving time; if the time difference is larger than a preset time difference threshold and the repayment information is not contained in each clearing file, removing the repayment amount from the repayment undelivered amount to obtain a target repayment undelivered amount; generating prompt information according to the receiving time, the target payment undelivered amount and the payment amount; and sending the prompt information to the user terminal.

In a second aspect, the present application provides a payment data processing apparatus comprising: the information determining module is used for determining the first batch transfer information of the online static database and the second batch transfer state information of the online dynamic database in response to receiving the repayment information sent by the user terminal, wherein the repayment information comprises repayment amount and user identification; the numerical value determining module is used for determining the repayment unread amount and the repayment total amount corresponding to the user identifier according to the user identifier, the first batch transfer information, the second batch transfer state information and the repayment amount; the data reading module is used for responding to a received repayment information inquiry request sent by the user terminal and reading a target repayment undelivered amount and a target repayment total corresponding to the user identifier; and the data transmitting module is used for transmitting the target repayment amount and the target repayment total amount to the user terminal.

In a third aspect, the present application provides an electronic device, comprising: a processor, a memory communicatively coupled to the processor; the memory stores computer-executable instructions; the processor executes computer-executable instructions stored in the memory to cause the processor to perform the payment data processing method as described in the first aspect.

In a fourth aspect, the present application provides a computer readable storage medium having stored therein computer executable instructions which when executed by a processor are for carrying out the payment data processing method as described in the first aspect.

In a fifth aspect, the present application provides a computer program product comprising a computer program which, when executed by a processor, implements a repayment data processing method as described in the first aspect.

According to the repayment data processing method, device, equipment and storage medium, after repayment information placed by a user terminal is received, batch transfer state information of an online static database and an online dynamic database is determined, the repayment undelivered amount and the repayment total amount corresponding to a user identifier are determined by the user identifier, the two batch transfer state information and the repayment amount, and after a repayment information inquiry request sent by the user terminal is received, the repayment undelivered amount and the repayment total amount are sent to the user terminal.

Drawings

The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the application and together with the description, serve to explain the principles of the application.

Fig. 1 is an application scenario schematic diagram of a repayment data processing method provided in an embodiment of the present application;

FIG. 2 is a schematic flow chart of a payment data processing method according to an embodiment of the present application;

FIG. 3 is a schematic diagram of a scenario in which both online static databases and online dynamic databases provided in the embodiments of the present application are completed in batch;

FIG. 4 is a schematic diagram of a scenario when online static database wholesale transfer is completed and data processing is not performed according to an embodiment of the present disclosure;

fig. 5 is a schematic diagram of a scenario after the online static database wholesale conversion is completed and data processing is performed according to the embodiment of the present application;

FIG. 6 is a schematic diagram of a scenario in which online dynamic database wholesale transfer is completed and data processing is not performed according to an embodiment of the present application;

fig. 7 is a schematic diagram of a scenario after the online dynamic database wholesale connection is completed and data processing is performed according to the embodiment of the present application;

FIG. 8 is a schematic structural diagram of a payment data processing apparatus according to an embodiment of the present application;

fig. 9 is a schematic structural diagram of an electronic device according to an embodiment of the present application.

Specific embodiments thereof have been shown by way of example in the drawings and will herein be described in more detail. These drawings and the written description are not intended to limit the scope of the inventive concepts in any way, but to illustrate the concepts of the present application to those skilled in the art by reference to specific embodiments.

Detailed Description

Reference will now be made in detail to exemplary embodiments, examples of which are illustrated in the accompanying drawings. When the following description refers to the accompanying drawings, the same numbers in different drawings refer to the same or similar elements, unless otherwise indicated. The implementations described in the following exemplary examples are not representative of all implementations consistent with the present application. Rather, they are merely examples of apparatus and methods consistent with some aspects of the present application as detailed in the accompanying claims.

The terms referred to in this application are explained first:

and (5) online: a credit card system for processing daily transactions, comprising inquiry of credit card information, deduction of amount and the like.

Batch size: a credit card system specifically posting a customer account, which will do the actual posting based on the online transaction log and peripheral clearing.

Batch transfer: and synchronizing the operation of the online database after the batch accounting results are checked in.

The repayment is not achieved: the clearing file is not delivered, only the payoff amount of the online transaction.

The payment amount is consumed at the current period: the clearing file has been sent and the customer bill has been credited for the payment amount on a daily basis.

Clearing a file: i.e. the posting documents, the batch will actually posting according to the clearing documents.

Day cutting: trade day/business day switch. The system is mainly related to business days of the system, and is different from natural days, the batch system transmits online log records at certain time points every day, and the rest transaction logs of the current day are taken into the transaction of the next business day along with the daily cut of the next day.

Online static database: mainly to save static attributes corresponding to credit cards. The static attributes do not dynamically change with each transaction, such as the customer's permanent credit and billing.

Online dynamic database: mainly to save business activity related information of clients. Each transaction affects the available credit of the customer, such as consumption and repayment.

In the using process of the credit card, various transaction data can be generated, after the user pays, the bank needs to record the payed amount, usually an online database is used for real-time recording, and a batch database is used for data synchronization (batch transfer) at fixed time, so that the operation of the double information system is realized. The credit card dual information system's line authorization and clearing posting are not performed simultaneously. Authorization is performed at the time point of transaction occurrence, is the judgment result of the issuer on whether the client is allowed to conduct transaction, and clearing is the final confirmation of the transaction result, is the basis for merchant transaction and is also the basis for generating a bill for the client. The data synchronization process between the dual systems also needs to ensure the consistency and correctness of the data. For a transaction, when a cardholder completes a consumption on a market terminal or completes a withdrawal on a cash dispenser, the background system responds to the transaction in real time and deducts the available amount of the customer, but the transaction does not involve specific account entry processing at this time, and a clearing account entry process exists in transactions such as card consumption and cash withdrawal, and the accounting is mainly completed in batch processing at night. But if the user queries the data during the data synchronization (during the batch transfer), it may cause errors in the query results.

Aiming at the technical problems, the inventor provides the following technical conception that batch transfer state information is added in an online static database and an online dynamic database in an online database respectively and used for recording whether batch transfer is completed or not, and for different batch transfer state information, the correct payment undelivered amount and the correct payment total amount corresponding to the user identification are determined by adopting different data and sent to the user terminal.

The method and the device are applied to scenes of repayment data processing. It should be noted that, the user information (including but not limited to user equipment information, user personal information, etc.) and the data (including but not limited to data for analysis, stored data, presented data, etc.) referred to in the present application are information and data authorized by the user or fully authorized by each party, and the collection, use and processing of the related data need to comply with the related laws and regulations and standards, and provide corresponding operation entries for the user to select authorization or rejection.

Fig. 1 is an application scenario schematic diagram of a repayment data processing method provided in an embodiment of the present application. As in fig. 1, in this scenario, it includes: server 101, user terminal 102, online static database 1031, online dynamic database 1032, batch database 1033.

In a specific implementation process, the server 101 may be implemented by using a server with more powerful processing capability and higher security or a cluster formed by multiple servers, and if possible, a computer with more powerful computing capability, a notebook computer, or the like may be used instead.

The user terminal 102 may include a computer, a server, a tablet, a mobile phone, a palm top (Personal Digital Assistant, PDA), a notebook, etc., which may perform data input.

The online static database 1031, online dynamic database 1032, and batch database 1033 may comprise a single database or may be a combination of databases. For example: one or more of Oracle (Oracle) database, mySQL (relational database management system), DRDS (Distribute Relational Database Service, distributed relational database) database, ES (elastic search) database, and the like, to which the present application is not limited in particular. The connection between the server 101 and the user terminal 102 may be a wired connection or a wireless connection.

The server 101 is configured to receive payment information sent by the user terminal, obtain a first transfer state information of the online static database and a second transfer state information of the online dynamic database, determine a payment undelivered amount and a payment total amount corresponding to the user identifier according to the user identifier, the first transfer state information, the second transfer state information and the payment amount, and send the payment undelived amount and the payment total amount to the user terminal.

Batch database 1033 may be journaled, batch synchronized, etc. with online dynamic database 1032 and batch database 1033.

In one possible implementation, the functionality of server 101 may also be replaced with a batch database.

It will be appreciated that the structure illustrated in the embodiments of the present application does not constitute a specific limitation on the method of processing the payment data. In other possible embodiments of the present application, the architecture may include more or fewer components than those illustrated, or some components may be combined, some components may be separated, or different component arrangements may be specifically determined according to the actual application scenario, and the present application is not limited herein. The components shown in fig. 1 may be implemented in hardware, software, or a combination of software and hardware.

The following describes the technical solutions of the present application and how the technical solutions of the present application solve the above technical problems in detail with specific embodiments. The following embodiments may be combined with each other, and the same or similar concepts or processes may not be described in detail in some embodiments. Embodiments of the present application will be described below with reference to the accompanying drawings.

Fig. 2 is a flow chart of a payment data processing method according to an embodiment of the present application. The execution subject of the embodiment of the present application may be the server 101 in fig. 1, or may be a computer and/or a mobile phone, which is not particularly limited in this embodiment. As shown in fig. 2, the method includes:

S201: and determining the first batch transfer state information of the online static database and the second batch transfer state information of the online dynamic database in response to receiving the repayment information sent by the user terminal, wherein the repayment information comprises repayment amount and user identification.

In this step, the repayment information may be in a format of a message, a data packet, or the like, and the first batch of transfer state information of the online static database may be determined by reading a specific field from a preset position in the online static database to obtain the first batch of transfer state information; the online static database can also send the batch transfer completion information to the server after the batch transfer is completed, if the server receives the batch transfer completion information within the preset time, the first batch transfer state information is determined to be completed, otherwise, the first batch transfer state information is determined to be incomplete. The second lot of transfer state information is determined in the same manner.

Wherein, "first" and "second" are used for distinguishing different lot-to-lot status information, and have no sequential meaning.

S202: and determining the payment undelivered amount and the payment total corresponding to the user identifier according to the user identifier, the first batch transfer state information, the second batch transfer state information and the payment amount.

In this step, the payment amount and/or the total amount of paid money may be calculated from the payment amount in combination with the corresponding value according to the contents of the first transfer state information and the second transfer state information.

Wherein the undelivered amount of money indicates an amount that has been paid, but has not completed the clearing process.

S203: and in response to receiving a repayment information inquiry request sent by the user terminal, reading a target repayment undelivered amount and a target repayment total corresponding to the user identifier.

In this step, the payment information inquiry request may also include a user identifier, and the payment information inquiry request may also be sent in a packet, a data packet, or other format. Reading the target payoff amount and the target payoff amount can be searching a file containing a user identifier at a preset position to obtain the target payoff amount and the target payoff amount, or reading data at a position corresponding to the user identifier to obtain the target payoff amount and the target payoff amount,

s204: and sending the target repayment amount and the target repayment total amount to the user terminal.

In this step, the target payment undelivered amount and the target payment sum may be written into a data packet or a message, and the data packet or the message may be sent to the user terminal.

As can be seen from the description of the above embodiments, in the embodiments of the present application, after receiving the payment information sent by the user terminal, the batch transfer state information of the online static database and the online dynamic database is determined, and the payment undelivered amount and the payment total amount corresponding to the user identifier are determined by the user identifier, the two batch transfer state information and the payment amount, and after receiving the payment information inquiry request sent by the user terminal, the payment undelivered amount and the payment total amount are sent to the user terminal.

Fig. 3 is a schematic diagram of a scenario in which both an online static database and an online dynamic database provided in an embodiment of the present application are completed in batch. As shown in FIG. 3, after both databases are in batch transfer, the online static database contains the correct current payment amount and the online dynamic database contains the correct payment amount.

In a possible implementation manner, in the step S202, the determining the payoff amount and the payoff total corresponding to the user identifier according to the user identifier, the first lot transfer state information, the second lot transfer state information, and the payoff amount includes:

s202A1: if the first and second transfer state information are completed, the current repayment amount corresponding to the user identification in the online static database is read.

In this step, the lot transfer status information may be replaced with numbers or letters, e.g., 0 for incomplete and 1 for complete; 00 represents incomplete and 01 represents complete. The current payment amount can be obtained by searching the corresponding relation between the user identifier and the current payment amount in the online static database, or by including a field or table of the user identifier in the online static database.

The corresponding relation between the user identification and the payment amount in the current period can be stored in a form and key value peer-to-peer format.

S202A2: and generating a repayment undelivered amount corresponding to the user identification according to the repayment amount.

In this step, the current payment amount may be obtained by adding all payment amounts corresponding to the user identifier after the completion of the wholesale transfer.

All repayment amounts corresponding to the user identifications can be obtained by searching corresponding files or tables in the user identifications in the online dynamic database.

S202A3: and adding the current repayment amount and the repayment undelivered amount to obtain the repayment total corresponding to the user identifier.

In this step, for example, the amount of payment in the current period is 3000, the amount of payment is 10000, and the total amount of payment is 13000; for another example, if the current payment amount is 20000 and the payment undelivered amount is 100000, the total amount of payment is 120000.

As can be seen from the description of the above embodiments, in the embodiment of the present application, under the condition that both of the batch transfer status information is completed, the current payment amount corresponding to the user identifier in the online static library is read, the payment amount corresponding to the user identifier is generated from the payment amount, the sum of the current payment amount and the payment amount is calculated, the total payment amount corresponding to the user identifier is obtained, and the more accurate effect of obtaining the total payment amount and the payment amount is achieved.

Fig. 4 is a schematic diagram of a scenario when online static database wholesale transfer is completed and data processing is not performed according to an embodiment of the present application. As shown in FIG. 4, the online dynamic database does not complete the lot transfer, the amount of the paid-up in the online dynamic database is not the latest amount, and direct calculation may cause data calculation errors. At this time, because the batch transfer of the static library is completed, the payment undelivered amount of the last business day corresponding to the user identifier can be obtained, and meanwhile, a field can be newly added for the payment undelivered after the date cutting and stored in the online static database, so that the complete payment undelivered of the client can be obtained.

Fig. 5 is a schematic diagram of a scenario after the online static database wholesale connection is completed and data processing is performed according to the embodiment of the present application. As shown in fig. 5, the newly added field is still called a payoff amount, but is stored in the online static database, and meanwhile, the payoff amount field in the online dynamic database is newly added in the day.

S202B1: if the first transfer state information is completed and the second transfer state information is not completed, the current repayment amount corresponding to the user identifier, the current day repayment unded amount, an online transaction log and a clearing file are obtained, wherein the online transaction log comprises at least one transaction information, and the transaction information comprises the historical repayment amount.

In this step, the manner of obtaining the payment amount in the present period may be similar to that of step S202A1, and will not be described here again. The existing day-to-day payoff amount may be obtained by accumulating all payoff amounts after day-cutting before the above step S201. The online transaction log corresponding to the user identifier may be obtained by searching the online transaction log whose name contains the user identifier. The manner of reading the clearing file is similar to the manner of reading the online transaction log and will not be described in detail herein.

S202B2: and adding the repayment amount and the existing day repayment undelivered amount to obtain a new day repayment undelivered amount corresponding to the user identifier.

In this step, for example, the repayment amount is 2000, the existing repayment amount on the same day is 4000, and the new repayment amount on the same day is 6000; for example, if the payment amount is 1000, the existing payment amount on the same day is 3000, and the new payment amount on the same day is 4000.

S202B3: and determining transaction information which belongs to the online transaction log and does not belong to the clearing file as target transaction information.

In this step, for example, the transaction information B belongs to an online transaction log and does not belong to a clearing file, the transaction information B is determined as target transaction information. For another example, the online transaction log includes transaction information A, B, C, D and the clearing file includes transaction information A, B, C, then transaction information D is the target transaction information.

S202B4: and adding the historical payment amounts in the target transaction information to obtain the historical payment undelivered amounts corresponding to the user identifiers.

In this step, for example, there are currently 5 pieces of target transaction information, and the historical payment amounts included in the current transaction information are 1000, 2000, 1000, 4000, respectively, and then the corresponding historical payment undelivered amount of the user identifier is 9000. For another example, when there is 3 pieces of target transaction information currently, and the historical repayment amounts included in the 3 pieces of target transaction information are 2000, 1000 and 4000 respectively, the historical repayment amount corresponding to the user identifier is 7000.

S202B5: and adding the current payment amount, the new current day payment undelivered amount and the historical payment undelivered amount corresponding to the user identification to obtain the total payment amount corresponding to the user identification.

In this step, for example, the current payment amount, the new payment amount on the current day and the historical payment amount are 10000, 3000 and 6000 respectively, and the sum of the payments corresponding to the user identifier is 19000; for another example, if the current payment amount, the new payment amount on the same day, and the historical payment amount are 7000, 2300, and 4000, respectively, the total payment amount corresponding to the user identifier is 13300.

S202B6: and adding the new payment undelivered amount on the same day and the historical payment undelivered amount to obtain the payment undelivered amount corresponding to the user identifier.

In this step, for example, the current day of the payment is 20000, the historical payment is 15000, and the payment corresponding to the user identifier is 35000; for another example, when the daily payoff amount is 2300 and the historical payoff amount is 1700, the payoff amount corresponding to the user identifier is 4000.

As can be seen from the description of the above embodiments, in the embodiments of the present application, when the batch transfer state information of the online static database is completed and the batch transfer state information of the online dynamic database is incomplete, the current payment amount corresponding to the user identifier, the current day payment undelivered amount, the online transaction log, and the clearing file are obtained, and a new current day payment undelived amount is calculated from the payment amount and the current day payment undelived amount, the historical transaction amounts which are included in the online transaction log but not included in the clearing file are accumulated to obtain the historical payment undelived amount, the new current day payment undelived amount and the historical payment undelived amount are added to obtain the payment undelived amount corresponding to the user identifier, and the current day payment undelived amount, the new current day payment undelived amount and the historical payment undelived amount are added to obtain the total amount corresponding to the user identifier.

Fig. 6 is a schematic diagram of a scenario in which online dynamic database wholesale transfer is completed and data processing is not performed according to an embodiment of the present application. As shown in FIG. 6, the online static database does not complete the lot transfer at this time. The paid-up amount in the online dynamic library indicates the real paid-up amount of the user, and the current paid-up amount of the online static library does not contain the paid-up amount of the last business day because the batch transfer is not completed, and at the moment, the online dynamic library can be newly added with a field to store the paid-up amount before the day cut.

Fig. 7 is a schematic diagram of a scenario after the online dynamic database wholesale connection is completed and data processing is performed according to the embodiment of the present application. As shown in fig. 7, a new target payment amount field is added to the online dynamic library to indicate the amount of payment paid on the last business day.

S202C1: if the second transfer state information is completed and the first transfer state information is incomplete, acquiring an online transaction log and a clearing file corresponding to the user identifier, wherein the online transaction log comprises at least one transaction information, the transaction information comprises a historical repayment amount, and the transaction information corresponds to transaction time.

The transaction time corresponding to the transaction information may be the time recorded when the transaction is generated, similar to the above step S202B 1.

S202C2: if any transaction information belongs to the online transaction log and does not belong to the clearing file, and the corresponding transaction time is after the preset date cut time and before the preset batch transfer completion time, determining any transaction information as target transaction information.

In this step. The preset date and time and the preset batch transfer completion time may be preset by a worker.

For example, when the current preset date and time is 19 points, the preset batch transfer completion time is 24 points, the generation time of the transaction information a in the online transaction log is 21 points, and the transaction information a is not in the clearing file, the transaction information a is determined as the target transaction information. For another example, the current preset date cut time is 0 point, the preset batch transfer completion time is 3 points, the generation time of the transaction information B in the online transaction log is 2 points, and the transaction information B is determined as the target transaction information if the transaction information B is not in the clearing file.

S202C3: and adding the historical repayment amounts in the target transaction information to obtain target repayment amounts.

In this step, for example, there are currently 4 pieces of target transaction information, and the historical repayment amounts included are 2000, 3000, 1000, 4000, respectively, and the target repayment amount is 10000. For another example, when there are 2 items of target transaction information currently, and the historical repayment amount included is 1000 and 5000 respectively, the target repayment amount is 6000.

S202C4: and reading the current repayment amount corresponding to the user identifier in the online static database.

In this step, the current payment amount may be pre-stored in the online static database, and may be obtained by searching a file corresponding to the user identifier in the online static database, or may be obtained by searching a correspondence between the user identifier in the online static database and the current payment amount.

The corresponding relation between the user identification and the current repayment amount can be stored in a form and key value peer-to-peer format.

S202C5: and generating a payment undelivered amount on the same day according to the payment amount.

In this step, the payment amount may be directly determined as the payment undelivered amount on the same day; the new current day payoff amount may be obtained by adding the payoff amount to the current day payoff amount, and the current day payoff amount may be obtained by adding the payoff amounts obtained after the completion of the transfer of the lot before the step S201.

S202C6: and adding the target payment amount and the current day payment undelivered amount to obtain the payment undelivered amount corresponding to the user identifier.

For example, if the target payment amount is 4000 and the payment undelivered amount on the same day is 1000, the payment undelivered amount corresponding to the user identification is 5000. For another example, the target payment amount is 1000, and the payment undelivered amount on the same day is 5000, and the payment undelivered amount corresponding to the user identification is 6000.

S202C7: and adding the payment undelivered amount and the current payment amount to obtain the total payment amount corresponding to the user identifier.

In this step, for example, the payment amount is 4000, the current payment amount is 6000, and the sum of the paid payments corresponding to the user identifier is 10000. For another example, if the payment sum is 7000 and the current payment sum is 4000, the sum of the paid-out amount corresponding to the user identification is 11000.

As can be seen from the description of the above embodiments, in the embodiments of the present application, when the batch transfer information of the online dynamic database is completed and the batch transfer information of the online static database is incomplete, the online transaction log and the clearing file corresponding to the user identifier are obtained, the transaction information in the online transaction log and the clearing file is compared, the target transaction information which belongs to the online transaction log and does not belong to the clearing file and is located after the preset day-to-day time and before the preset batch transfer completion time corresponding to the transaction time is found, the historical payoff amount in the target transaction information is added to obtain the target payoff amount, the target payoff amount is added to the current day payoff amount generated according to the payoff amount, the payoff amount corresponding to the user identifier is obtained, and the payoff amount in the online static database is added to obtain the total payoff amount, so that the payoff amount and the total payoff amount of the user are accurately calculated when the online dynamic database completes the batch transfer and the online static database is not completed.

S202D1: if the first and second transfer state information are incomplete, the current repayment amount corresponding to the user identification in the online static database and the repayment unread amount corresponding to the user identification in the online dynamic database are read.

In this step, the current payment amount may be obtained by searching for a corresponding relationship between the preset user identifier and the current payment amount in the online static database. The current repayment amount can be obtained by searching the corresponding relation between the preset user identification and the repayment undelivered amount in the online dynamic database.

Wherein, each corresponding relation can be stored in a form and a key value peer-to-peer format.

S202D2: and adding the current repayment amount and the repayment undelivered amount to obtain the repayment total.

This step is similar to step S202C7 described above, and will not be described again here.

As can be seen from the description of the above embodiments, in the embodiments of the present application, the amount of the current payment and the amount of the payment not yet reached are directly read under the condition that the online static database and the online dynamic database are not completed in batch transfer, and the total amount of the payment is calculated, so that the calculation is directly performed by adopting self-consistent data, and the data processing time is reduced.

In a possible implementation manner, after receiving the payment information sent by the user terminal in step S201, the method further includes:

s210: and acquiring the receiving time of the repayment information.

In this step, the time stamp may be acquired when the payment information is received, and the time of receipt of the payment information may be obtained.

S211: and periodically acquiring the current time and the clearing file.

In this step, the period may be 1 minute, 10 minutes, 1 hour, 1 day, or the like, and may be a value set in advance by a worker. The current time may be obtained by obtaining a time stamp. The clearing file may be read from a preset path.

S212: and calculating the time difference between the current time and the receiving time.

In this step, the time difference may be obtained by subtracting the reception time from the current time.

S213: if the time difference is larger than a preset time difference threshold and the clearing files do not contain repayment information, removing the repayment amount from the repayment undelivered amount to obtain the target repayment undelivered amount.

In this step, the preset time difference threshold may be preset by a worker. Whether the clearing file contains the repayment information can be determined by searching the number or the identification of the repayment information in the clearing file, if the number or the identification of the repayment information can be searched, the repayment information is not contained in the clearing file, and if the repayment information cannot be searched. Removing the payoff amount from the payoff amount may be subtracting the payoff amount from the payoff amount to obtain a target payoff amount.

For example, the time difference corresponding to the payment information a is 1 hour after 5 days, the preset time difference threshold is 5 days, the payment information is not contained in each clearing file, the payment sum is 10000, the payment sum is 2000, and the calculated target payment sum is 8000. For another example, the time difference corresponding to the repayment information B is 4 days and 10 hours, the preset time difference threshold is 4 days, the repayment information is not contained in each clearing file, the repayment undelivered amount is 21000, the repayment amount is 1000, and the calculated target repayment undelivered amount is 20000.

S214: and generating prompt information according to the receiving time, the target payment undelivered amount and the payment amount.

In this step, the receiving time, the target payment undelivered amount and the payment amount may be written into a preset prompt message template to obtain the prompt message.

Specifically, the receiving time, the target payment undelivered amount and the payment amount are written into corresponding positions in the prompt information template to obtain the prompt information.

S215: and sending the prompt information to the user terminal.

In this step, the prompt information may be written into a packet or a data packet, and the packet data packet is sent to the user terminal.

As can be seen from the description of the above embodiment, in the embodiment of the present application, by recording the receiving time of the payment information, periodically acquiring the current time and the clearing file, calculating the time difference from the received payment information to the current time, removing the payment amount in the payment undelivered amount when the time difference is greater than the preset time difference threshold and the clearing file has no payment information, obtaining the target payment undelivered amount, generating the prompt information according to the receiving time, the target payment undelivered amount and the payment amount, and sending the prompt information to the user terminal, so as to achieve the effects of removing the payment amount which is not cleared for a long time, updating the payment undelivered amount, increasing the accuracy of the payment undelivered amount, and prompting the user after the removal.

Fig. 8 is a schematic structural diagram of a payment data processing apparatus according to an embodiment of the present application. As shown in fig. 8, the payment data processing apparatus 800 includes: an information determining module 801, a numerical value determining module 802, a data reading module 803 and a data transmitting module 804.

The information determining module 801 is configured to determine, in response to receiving payment information sent by the user terminal, first batch transfer information of the online static database and second batch transfer status information of the online dynamic database, where the payment information includes a payment amount and a user identifier.

The value determining module 802 is configured to determine a payment unread amount and a total payment amount corresponding to the user identifier according to the user identifier, the first transfer information, the second transfer state information, and the payment amount.

The data reading module 803 is configured to read, in response to receiving a payment information query request sent by the user terminal, a target payment undelivered amount and a target total amount that are corresponding to the user identifier.

The data sending module 804 is configured to send the target payment undelivered amount and the target total amount of paid to the user terminal.

The device provided in this embodiment may be used to implement the technical solution of the foregoing method embodiment, and its implementation principle and technical effects are similar, and this embodiment will not be described herein again.

In one possible implementation, the value determining module 802 is configured to: if the first and second transfer state information are completed, the current repayment amount corresponding to the user identification in the online static database is read. And generating a repayment undelivered amount corresponding to the user identification according to the repayment amount. And adding the current repayment amount and the repayment undelivered amount to obtain the repayment total corresponding to the user identifier.

In one possible implementation, the value determining module 802 is configured to: if the first transfer state information is completed and the second transfer state information is not completed, the current repayment amount corresponding to the user identifier, the current day repayment unded amount, an online transaction log and a clearing file are obtained, wherein the online transaction log comprises at least one transaction information, and the transaction information comprises the historical repayment amount. And adding the repayment amount and the existing day repayment undelivered amount to obtain a new day repayment undelivered amount corresponding to the user identifier. And determining transaction information which belongs to the online transaction log and does not belong to the clearing file as target transaction information. And adding the historical payment amounts in the target transaction information to obtain the historical payment undelivered amounts corresponding to the user identifiers. And adding the current payment amount, the new current day payment undelivered amount and the historical payment undelivered amount corresponding to the user identification to obtain the total payment amount corresponding to the user identification. And adding the new payment undelivered amount on the same day and the historical payment undelivered amount to obtain the payment undelivered amount corresponding to the user identifier.

In one possible implementation, the value determining module 802 is configured to: if the second transfer state information is completed and the first transfer state information is incomplete, acquiring an online transaction log and a clearing file corresponding to the user identifier, wherein the online transaction log comprises at least one transaction information, the transaction information comprises a historical repayment amount, and the transaction information corresponds to transaction time. If any transaction information belongs to the online transaction log and does not belong to the clearing file, and the corresponding transaction time is after the preset date cut time and before the preset batch transfer completion time, determining any transaction information as target transaction information. And adding the historical repayment amounts in the target transaction information to obtain target repayment amounts. And reading the current repayment amount corresponding to the user identifier in the online static database. And generating a payment undelivered amount on the same day according to the payment amount. And adding the target payment amount and the current day payment undelivered amount to obtain the payment undelivered amount corresponding to the user identifier. And adding the payment undelivered amount and the current payment amount to obtain the total payment amount corresponding to the user identifier.

In one possible implementation, the value determining module 802 is configured to: if the first and second transfer state information are incomplete, the current repayment amount corresponding to the user identification in the online static database and the repayment unread amount corresponding to the user identification in the online dynamic database are read. And adding the current repayment amount and the repayment undelivered amount to obtain the repayment total.

In one possible implementation, the payment data processing apparatus 800 further includes: information prompt module 805.

And the information prompt module 805 is configured to obtain a receiving time of the payment information. And periodically acquiring the current time and the clearing file. And calculating the time difference between the current time and the receiving time. If the time difference is larger than a preset time difference threshold and the clearing files do not contain repayment information, removing the repayment amount from the repayment undelivered amount to obtain the target repayment undelivered amount. And generating prompt information according to the receiving time, the target payment undelivered amount and the payment amount. And sending the prompt information to the user terminal.

In order to achieve the above embodiments, the present application further provides an electronic device.

Referring to fig. 9, a schematic structural diagram of an electronic device 900 suitable for implementing embodiments of the present application is shown, where the electronic device 900 may be a terminal device or a server. The terminal device may include, but is not limited to, a mobile terminal such as a mobile phone, a notebook computer, a digital broadcast receiver, a personal digital assistant (Personal Digital Assistant, PDA for short), a tablet (Portable Android Device, PAD for short), a portable multimedia player (Portable Media Player, PMP for short), an in-vehicle terminal (e.g., an in-vehicle navigation terminal), and the like, and a fixed terminal such as a digital TV, a desktop computer, and the like. The electronic device shown in fig. 9 is only an example, and should not impose any limitation on the functions and scope of use of the embodiments of the present application.

As shown in fig. 9, the electronic device 900 may include a processor (e.g., a central processing unit, a graphics processor, etc.) 901, and a Memory 902 communicatively connected to the processor, which may perform various appropriate actions and processes according to a program stored in the Memory 902, a computer-executed instruction, or a program loaded from a storage 908 into a random access Memory (Random Access Memory, abbreviated as RAM) 903, implementing the payback data processing method in any of the above embodiments, where the Memory may be a Read Only Memory (ROM). In the RAM903, various programs and data necessary for the operation of the electronic device 900 are also stored. The processing device 901, the memory 902, and the RAM903 are connected to each other by a bus 904. An input/output (I/O) interface 905 is also connected to the bus 904.

In general, the following devices may be connected to the I/O interface 905: input devices 906 including, for example, a touch screen, touchpad, keyboard, mouse, camera, microphone, accelerometer, gyroscope, and the like; an output device 907 including, for example, a liquid crystal display (Liquid Crystal Display, LCD for short), a speaker, a vibrator, and the like; storage 908 including, for example, magnetic tape, hard disk, etc.; and a communication device 909. The communication means 909 may allow the electronic device 900 to communicate wirelessly or by wire with other devices to exchange data. While fig. 9 shows an electronic device 900 having various means, it is to be understood that not all illustrated means are required to be implemented or provided. More or fewer devices may be implemented or provided instead.

In particular, according to embodiments of the present application, the processes described above with reference to flowcharts may be implemented as computer software programs. For example, embodiments of the present application include a computer program product comprising a computer program embodied on a computer readable storage medium, the computer program comprising program code for performing the method shown in the flowcharts. In such an embodiment, the computer program may be downloaded and installed from a network via communication device 909, or installed from storage device 908, or installed from memory 902. When executed by the processing device 901, the computer program performs the functions defined above in the method of the embodiment of the present application.

It should be noted that the computer readable storage medium described in the present application may be a computer readable signal medium or a computer storage medium, or any combination of the two. The computer readable storage medium can be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or a combination of any of the foregoing. More specific examples of the computer-readable storage medium may include, but are not limited to: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the context of this document, a computer readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device. In the present application, however, a computer-readable signal medium may include a data signal that propagates in baseband or as part of a carrier wave, with the computer-readable program code embodied therein. Such a propagated data signal may take any of a variety of forms, including, but not limited to, electro-magnetic, optical, or any suitable combination of the foregoing. A computer readable signal medium may also be any computer readable storage medium that is not a computer readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device. Program code embodied on a computer readable storage medium may be transmitted using any appropriate medium, including but not limited to: electrical wires, fiber optic cables, RF (radio frequency), and the like, or any suitable combination of the foregoing.

The computer-readable storage medium may be contained in the electronic device; or may exist alone without being incorporated into the electronic device.

The computer-readable storage medium carries one or more programs which, when executed by the electronic device, cause the electronic device to perform the methods shown in the above-described embodiments.

Computer program code for carrying out operations of the present application may be written in one or more programming languages, including an object oriented programming language such as Java, smalltalk, C ++ and conventional procedural programming languages, such as the "C" programming language or similar programming languages. The program code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the case of a remote computer, the remote computer may be connected to the user's computer through any kind of network, including a local area network (Local Area Network, LAN for short) or a wide area network (Wide Area Network, WAN for short), or it may be connected to an external computer (e.g., connected via the internet using an internet service provider).

The flowcharts and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various embodiments of the present application. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams and/or flowchart illustration, and combinations of blocks in the block diagrams and/or flowchart illustration, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.

The modules involved in the embodiments described in the present application may be implemented by software, or may be implemented by hardware. The name of the unit does not in some case define the module itself, and for example, the information determination module may also be described as a "payment information determination module".

The functions described above herein may be performed, at least in part, by one or more hardware logic components. For example, without limitation, exemplary types of hardware logic components that may be used include: a Field Programmable Gate Array (FPGA), an Application Specific Integrated Circuit (ASIC), an Application Specific Standard Product (ASSP), a system on a chip (SOC), a Complex Programmable Logic Device (CPLD), and the like.

The present application further provides a computer readable storage medium, in which computer executable instructions are stored, when a processor executes the computer executable instructions, the technical scheme of the repayment data processing method in any of the foregoing embodiments is implemented, and the implementation principle and the beneficial effects are similar to those of the repayment data processing method, and may be referred to the implementation principle and the beneficial effects of the repayment data processing method, which are not described herein again.

In the context of this application, a machine-readable medium may be a tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device. The machine-readable medium may be a machine-readable signal medium or a machine-readable storage medium. The machine-readable medium may include, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing. More specific examples of a machine-readable storage medium would include an electrical connection based on one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.

The present application further provides a computer program product, including a computer program, where when the computer program is executed by a processor, the implementation principle and the beneficial effects of the repayment data processing method in any of the foregoing embodiments are similar to those of the repayment data processing method, and may be referred to the implementation principle and the beneficial effects of the repayment data processing method, and will not be described herein.

The foregoing description is only of the preferred embodiments of the present application and is presented as a description of the principles of the technology being utilized. It will be appreciated by persons skilled in the art that the scope of the disclosure referred to in this application is not limited to the specific combinations of features described above, but it is intended to cover other embodiments in which any combination of features described above or equivalents thereof is possible without departing from the spirit of the disclosure. Such as the above-described features and technical features having similar functions (but not limited to) disclosed in the present application are replaced with each other.

Other embodiments of the present application will be apparent to those skilled in the art from consideration of the specification and practice of the invention disclosed herein. This application is intended to cover any variations, uses, or adaptations of the application following, in general, the principles of the application and including such departures from the present disclosure as come within known or customary practice within the art to which the application pertains. It is intended that the specification and examples be considered as exemplary only, with a true scope and spirit of the application being indicated by the following claims.

It is to be understood that the present application is not limited to the precise arrangements and instrumentalities shown in the drawings, which have been described above, and that various modifications and changes may be effected without departing from the scope thereof. The scope of the application is limited only by the appended claims.

Claims

1. A payment data processing method, comprising:

determining first batch transfer state information of an online static database and second batch transfer state information of an online dynamic database in response to receiving payment information sent by a user terminal, wherein the payment information comprises payment amount and user identification;

determining a repayment unread amount and a repayment total amount corresponding to the user identifier according to the user identifier, the first batch transfer state information, the second batch transfer state information and the repayment amount;

responding to a received repayment information inquiry request sent by the user terminal, and reading a target repayment undelivered amount and a target repayment total corresponding to the user identifier;

and sending the target repayment amount and the target repayment total amount to the user terminal.

2. The method of claim 1, wherein the determining the payoff amount and the payoff total corresponding to the user identifier based on the user identifier, the first transfer state information, the second transfer state information, and the payoff amount comprises:

If the first transfer state information and the second transfer state information are completed, reading the current repayment amount corresponding to the user identifier in the online static database;

generating a repayment unread amount corresponding to the user identifier according to the repayment amount;

and adding the current repayment amount and the repayment undelivered amount to obtain the repayment total corresponding to the user identifier.

3. The method of claim 1, wherein the determining the payoff amount and the payoff total corresponding to the user identifier based on the user identifier, the first transfer state information, the second transfer state information, and the payoff amount comprises:

if the first transfer state information is completed and the second transfer state information is not completed, acquiring the current repayment amount, the current day repayment undelivered amount, an online transaction log and a clearing file corresponding to the user identifier, wherein the online transaction log comprises at least one transaction information, and the transaction information comprises a historical repayment amount;

adding the repayment amount and the existing day repayment undelivered amount to obtain a new day repayment undelivered amount corresponding to the user identifier;

Determining transaction information which belongs to an online transaction log and does not belong to the clearing file as target transaction information;

adding the historical repayment amounts in each target transaction information to obtain the historical repayment undelivered amounts corresponding to the user identifiers;

adding the current repayment amount, the new current day repayment undelivered amount and the historical repayment undelivered amount corresponding to the user identifier to obtain a repayment total corresponding to the user identifier;

and adding the new current day of the undelivered amount of the repayment and the historical undelivered amount of the repayment to obtain the undelivered amount of the repayment corresponding to the user identifier.

4. The method of claim 1, wherein the determining the payoff amount and the payoff total corresponding to the user identifier based on the user identifier, the first transfer state information, the second transfer state information, and the payoff amount comprises:

if the second transfer state information is completed and the first transfer state information is incomplete, acquiring an online transaction log and a clearing file corresponding to the user identifier, wherein the online transaction log comprises at least one transaction information, the transaction information comprises a historical repayment amount, and the transaction information corresponds to transaction time;

If any transaction information belongs to the online transaction log and does not belong to the clearing file, and the corresponding transaction time is after the preset date cutting time and before the preset batch transfer completion time, determining the any transaction information as target transaction information;

adding the historical repayment amounts in the target transaction information to obtain target repayment amounts;

reading the current repayment amount corresponding to the user identifier in the online static database;

generating a payment undelivered amount on the same day according to the payment amount;

adding the target repayment amount and the current day repayment undelivered amount to obtain a repayment undelivered amount corresponding to the user identifier;

and adding the payment undelivered amount and the payment amount in the current period to obtain the total payment amount corresponding to the user identifier.

5. The method of claim 1, wherein the determining the payoff amount and the payoff total corresponding to the user identifier based on the user identifier, the first transfer state information, the second transfer state information, and the payoff amount comprises:

if the first transfer state information and the second transfer state information are incomplete, reading the current repayment amount corresponding to the user identifier in the online static database and the repayment unread amount corresponding to the user identifier in the online dynamic database;

And adding the current repayment amount and the repayment undelivered amount to obtain the repayment total.

6. The method according to any one of claims 1 to 5, further comprising, after said receiving payment information sent by the user terminal:

acquiring the receiving time of the repayment information;

periodically acquiring the current time and a clearing file;

calculating the time difference of the current time and the receiving time;

if the time difference is larger than a preset time difference threshold and the repayment information is not contained in each clearing file, removing the repayment amount from the repayment undelivered amount to obtain a target repayment undelivered amount;

generating prompt information according to the receiving time, the target payment undelivered amount and the payment amount;

and sending the prompt information to the user terminal.

7. A payment data processing apparatus, comprising:

the information determining module is used for determining the first batch transfer information of the online static database and the second batch transfer state information of the online dynamic database in response to receiving the repayment information sent by the user terminal, wherein the repayment information comprises repayment amount and user identification;

The numerical value determining module is used for determining the repayment unread amount and the repayment total amount corresponding to the user identifier according to the user identifier, the first batch transfer information, the second batch transfer state information and the repayment amount;

the data reading module is used for responding to the received repayment information inquiry request sent by the user terminal and reading the target repayment undelivered amount and the target repayment total corresponding to the user identifier;

and the data sending module is used for sending the target repayment undelivered amount and the target repayment total amount to the user terminal.

8. An electronic device, comprising: a processor, and a memory communicatively coupled to the processor;

the memory stores computer-executable instructions;

the processor executing computer-executable instructions stored in the memory causes the processor to perform the payment data processing method of any one of claims 1 to 6.

9. A computer readable storage medium having stored therein computer executable instructions which when executed by a processor are for carrying out the payment data processing method of any one of claims 1 to 6.

10. A computer program product comprising a computer program which, when executed by a processor, implements the repayment data processing method of any one of claims 1 to 6.