Credit card limiting method, device, computer program product and credit card system

Abstract

The invention provides a credit card quota limiting method and device, a computer program product and a credit card system, and the method comprises the steps: obtaining an accumulated amount record of a target user under the condition of receiving a transaction request of the target user, the accumulated amount record comprising a user unique identifier, an accumulated amount of the day and accumulated amounts of multiple months; analyzing the transaction request to obtain a current transaction amount; according to the current transaction amount and the accumulated amount record, calculating to obtain an accumulated amount of each limit period, wherein the limit period comprises a daily limit period, a monthly limit period, a half-year limit period and an annual limit period; and under the condition that the accumulated amount of the at least one limit period is greater than the limit of the corresponding limit period, the transaction request of the target user is rejected, and the problem of high delay of credit card limit calculation in the prior art is solved.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of quota control, in particular to a credit card quota method, device, computer program product and credit card system. BACKGROUND

[0002] In the financial transaction scene such as credit card, the bank needs to verify whether the user transaction exceeds the daily cumulative, monthly cumulative or annual cumulative quota in real time. The existing technology generally uses SQL aggregation query to statistically analyze the user historical transaction data in real time, but as the time span increases or the transaction volume of a single user increases (for example, the transaction records of all users reach one million), the SQL aggregation operation needs to scan a large amount of data, resulting in high calculation delay, system performance decline, and affecting the real-time transaction and user experience. SUMMARY

[0003] The main purpose of the present application is to provide a credit card quota method, device, computer program product and credit card system to at least solve the problem of high credit card quota calculation delay in the prior art.

[0004] In order to achieve the above-mentioned purpose, according to one aspect of the present application, a credit card quota method is provided, comprising: in the case of receiving a transaction request of a target user, acquiring a cumulative amount record of the target user, the cumulative amount record comprising a user unique identifier, a daily cumulative amount and a plurality of monthly cumulative amounts; analyzing the transaction request to obtain a current transaction amount; calculating the cumulative amount of each quota period according to the current transaction amount and the cumulative amount record, the quota period comprising a daily quota period, a monthly quota period, a semi-annual quota period and an annual quota period; in the case that the cumulative amount of at least one of the quota periods is greater than the quota of the corresponding quota period, rejecting the transaction request of the target user.

[0005] Optionally, calculating the cumulative amount of each quota period according to the current transaction amount and the cumulative amount record comprises: in the case that the quota period is the daily quota period, calculating the sum of the current transaction amount and the daily cumulative amount to obtain the cumulative amount of the daily quota period; in the case that the quota period is the monthly quota period, calculating the sum of the current transaction amount and the monthly cumulative amount of the month in which the day is to obtain the cumulative amount of the monthly quota period; in the case that the quota period is the semi-annual quota period, calculating the sum of the current transaction amount and all the monthly cumulative amounts within the semi-annual quota period to obtain the cumulative amount of the semi-annual quota period; in the case that the quota period is the annual quota period, calculating the sum of the current transaction amount and all the monthly cumulative amounts within the annual quota period to obtain the cumulative amount of the annual quota period.

[0006] Optionally, before obtaining the cumulative amount record of the target user, the method further comprises: obtaining a time of the latest valid financial transaction, the time of the latest valid financial transaction being a time of the latest valid credit card transaction; in a case where the time of the latest valid financial transaction is not on the current day, clearing the daily cumulative amount; in a case where the time of the latest valid financial transaction is not in the current month, clearing the monthly cumulative amount corresponding to the months after the month in which the time of the latest valid financial transaction is located.

[0007] Optionally, after calculating the cumulative amount of each limit period according to the current transaction amount and the cumulative amount record, the method further comprises: in a case where the cumulative amount of each limit period is less than or equal to the limit of the corresponding limit period, accumulating the current transaction amount to the daily cumulative amount and the monthly cumulative amount of the current month.

[0008] Optionally, calculating the cumulative amount of each limit period according to the current transaction amount and the cumulative amount record comprises: determining the sum of the current transaction amount and the daily cumulative amount as the cumulative amount of the daily limit period; determining the sum of the current transaction amount and the monthly cumulative amount of the current month as the cumulative amount of the monthly limit period; calculating the sum of the current transaction amount, the monthly cumulative amount of the current month, and the monthly cumulative amounts of the five months before the current month to obtain the cumulative amount of the half-year limit period; and calculating the sum of the current transaction amount, the monthly cumulative amount of the current month, and the monthly cumulative amounts of the eleven months before the current month to obtain the cumulative amount of the annual limit period.

[0009] Optionally, in a case where the cumulative amount of at least one limit period is greater than the limit of the corresponding limit period, rejecting the transaction request of the target user comprises: in a case where the daily cumulative amount is greater than the daily limit, rejecting the transaction request of the target user; in a case where the monthly cumulative amount of the current month is greater than the monthly limit, rejecting the transaction request of the target user; in a case where the cumulative amount of the half-year limit period is greater than the half-year limit, rejecting the transaction request of the target user; and in a case where the cumulative amount of the annual limit period is greater than the annual limit, rejecting the transaction request of the target user.

[0010] Optionally, before the cumulative amount record of the target user is acquired, the method further comprises: in the case that the target user successfully applies for a credit card, constructing a plurality of record indexes, the record indexes comprising the user unique identifier, the time of the last valid financial transaction, the daily cumulative amount, and the monthly cumulative amounts from January to December; and recording the user unique identifier of the target user, the time of the last valid financial transaction as null, the daily cumulative amount as 0, and the monthly cumulative amounts from January to December as 0 in the plurality of record indexes to obtain the cumulative amount record of the target user.

[0011] According to another aspect of the present application, a credit card limit device is provided, comprising: a first acquisition unit configured to acquire a cumulative amount record of a target user in the case that a transaction request of the target user is received, the cumulative amount record comprising a user unique identifier, a daily cumulative amount, and a plurality of monthly cumulative amounts; an analysis unit configured to analyze the transaction request to obtain a current transaction amount; a first calculation unit configured to calculate a cumulative amount of each limit period according to the current transaction amount and the cumulative amount record, the limit periods comprising a daily limit period, a monthly limit period, a semi-annual limit period, and an annual limit period; and a processing unit configured to reject the transaction request of the target user in the case that the cumulative amount of at least one of the limit periods is greater than the limit of the corresponding limit period.

[0012] According to still another aspect of the present application, a computer program product is provided, comprising a computer program configured to implement any of the methods described above when executed by a processor.

[0013] According to yet another aspect of the present application, a credit card system is provided, comprising one or more processors, a memory, and one or more programs, wherein the one or more programs are stored in the memory and configured to be executed by the one or more processors, and the one or more programs comprise instructions for implementing any of the methods described above.

[0014] According to the technical solutions of the present application, in the credit card limit method described above, the daily cumulative amount and the plurality of monthly cumulative amounts in the cumulative amount record of the target user and the current transaction amount are used to calculate the cumulative amounts of the daily limit period, the monthly limit period, the semi-annual limit period, and the annual limit period, which are compared with the limits of the corresponding limit periods, and the transaction request of the target user is rejected if it exceeds the corresponding limit, so that the limit is achieved without the need to scan a large amount of transaction data within the limit period, which greatly reduces the calculation amount and solves the problem of high delay in the credit card limit calculation in the prior art. BRIEF DESCRIPTION OF DRAWINGS

[0015] The accompanying drawings, which form a part of this application, are included to provide a further understanding of the application and are incorporated in and constitute a part of this application. The illustrations, together with the description, serve to explain the application, but are not intended to limit the application in any way.

[0016] Figure 1 A hardware structure block diagram of a mobile terminal for performing a credit card limit method according to an embodiment of the present application is shown;

[0017] Figure 2 A flowchart of a credit card limit method according to an embodiment of the present application is shown;

[0018] Figure 3 A flowchart of a monthly cumulative amount clearing method according to an embodiment of the present application is shown;

[0019] Figure 4 A flowchart of another credit card limit method according to an embodiment of the present application is shown;

[0020] Figure 5 A structure block diagram of a credit card limit device according to an embodiment of the present application is shown.

[0021] In the above drawings, the following reference numerals are used:

[0022] 102, processor; 104, memory; 106, transmission device; 108, input / output device. DETAILED DESCRIPTION

[0023] It should be noted that the embodiments and features of the embodiments in the present application can be combined with each other without conflict. The technical solutions in the embodiments of the present application will be described in detail below with reference to the accompanying drawings and in combination with the embodiments. Obviously, the described embodiments are only part of the embodiments of the present application, not all the embodiments. Based on the embodiments in the present application, all other embodiments obtained by those skilled in the art without creative labor should be within the scope of protection of the present application.

[0024] In order to enable those skilled in the art to better understand the present application, the technical solutions in the embodiments of the present application will be described in detail below with reference to the accompanying drawings. Obviously, the described embodiments are only part of the embodiments of the present application, not all the embodiments. Based on the embodiments in the present application, all other embodiments obtained by those skilled in the art without creative labor should be within the scope of protection of the present application.

[0025] It should be noted that the terms "first," "second," etc., in the specification, claims, and accompanying drawings of this application are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that such data can be interchanged where appropriate for the embodiments of this application described herein. Furthermore, the terms "comprising" and "having," and any variations thereof, are intended to cover non-exclusive inclusion; for example, a process, method, system, product, or apparatus that comprises a series of steps or units is not necessarily limited to those steps or units explicitly listed, but may include other steps or units not explicitly listed or inherent to such processes, methods, products, or apparatus.

[0026] For ease of description, the following explains some of the nouns or terms used in the embodiments of this application:

[0027] Financial transactions refer to business operations involving changes in funds, including but not limited to credit card spending, transfers, and payments.

[0028] Cumulative Financial Transaction Limit: This refers to the maximum cumulative amount of a user's current financial transactions within a specific time frame (such as day, month, or year), used for risk control and limit management.

[0029] SQL aggregation: A method in Structured Query Language (SCL) used to perform statistical calculations (such as summation and average) on multiple rows of data.

[0030] As described in the background section, the prior art suffers from high latency in calculating credit card limits. To address this issue, embodiments of this application provide a credit card limit method, apparatus, computer program product, and credit card system.

[0031] The technical solutions of the present invention will be clearly and completely described below with reference to the accompanying drawings in the embodiments of the present invention.

[0032] The methods and embodiments provided in this application can be executed on a mobile terminal, computer terminal, or similar computing device. Taking running on a mobile terminal as an example, Figure 1 This is a hardware structure block diagram of a mobile terminal for a credit card limit method according to an embodiment of the present invention. Figure 1 As shown, a mobile terminal may include one or more ( Figure 1 Only one is shown in the diagram. A processor 102 (which may include, but is not limited to, a microprocessor MCU or a programmable logic device FPGA, etc.) and a memory 104 for storing data are also shown. The mobile terminal may further include a transmission device 106 for communication functions and an input / output device 108. Those skilled in the art will understand that... Figure 1The illustrated structure is merely schematic and does not limit the structure of the mobile terminal described above. For example, the mobile terminal can further include more or less components than those shown, or have a different configuration or arrangement of the components. Figure 1 The illustrated structure is merely schematic and does not limit the structure of the mobile terminal described above. For example, the mobile terminal can further include more or less components than those shown, or have a different configuration or arrangement of the components. Figure 1 The illustrated structure is merely schematic and does not limit the structure of the mobile terminal described above. For example, the mobile terminal can further include more or less components than those shown, or have a different configuration or arrangement of the components.

[0033] The memory 104 can be used to store computer programs, such as software programs of application software and modules, such as the computer program corresponding to the credit card limit method in the embodiments of the present application. The processor 102 can execute various functional applications and data processing, i.e., implement the method described above, by running the computer programs stored in the memory 104. The memory 104 can include a high-speed random access memory, and can further include a non-volatile memory, such as one or more magnetic storage devices, flash memories, or other non-volatile solid-state memories. In some examples, the memory 104 can further include a memory remotely arranged with respect to the processor 102, and the remote memory can be connected to the mobile terminal through a network. Examples of the network include, but are not limited to, the Internet, an intranet, a local area network, a mobile communication network, and a combination thereof. The transmission device 106 is used to receive or send data via a network. The specific example of the network can include a wireless network provided by a communication provider of the mobile terminal. In one example, the transmission device 106 includes a network adapter (NIC), which can be connected to other network devices through a base station so as to communicate with the Internet. In one example, the transmission device 106 can be a radio frequency (RF) module, which is used to communicate with the Internet in a wireless manner.

[0034] In the embodiments, a credit card limit method running on a mobile terminal, a computer terminal or a similar computing device is provided. It should be noted that the steps shown in the flowchart of the accompanying drawings can be executed in a computer system such as a set of computer executable instructions, and although a logical order is shown in the flowchart, in some cases, the steps shown or described herein can be executed in an order different from that shown.

[0035] Figure 2 is a flowchart of the credit card limit method according to the embodiments of the present application. As shown in Figure 2 , the method includes the following steps:

[0036] In step S201, when a transaction request of a target user is received, a cumulative amount record of the target user is obtained, and the cumulative amount record includes a user unique identifier, a daily cumulative amount and a plurality of monthly cumulative amounts.

[0037] Specifically, a cumulative amount record of all credit card users is constructed, recording a user unique identifier for matching with a user unique identifier of a transaction request, recording a target user corresponding to a credit card triggering the transaction request, recording a daily cumulative amount to accumulate daily cumulative transaction amounts, and recording a plurality of monthly cumulative amounts to accumulate cumulative transaction amounts of a plurality of months.

[0038] In step S202, the current transaction amount is obtained by parsing the transaction request.

[0039] Specifically, the transaction request includes not only a user unique identifier but also other transaction information, at least including a current transaction amount, and the current transaction amount is obtained by parsing the transaction request.

[0040] In step S203, the cumulative amount of each limit period is calculated according to the current transaction amount and the cumulative amount record, and the limit period includes a daily limit period, a monthly limit period, a semi-annual limit period, and an annual limit period.

[0041] Specifically, the limit period includes a daily limit period, a monthly limit period, a semi-annual limit period, and an annual limit period, and the time period covered by the limit period as of the current date is determined, for example, the daily limit period covers the current day, the monthly limit period covers the current month, the semi-annual limit period covers the recent half year, and the annual limit period covers the recent year. Therefore, the cumulative amount of each limit period can be obtained by adding the cumulative amount record corresponding to the time period covered by each limit period and the current transaction amount.

[0042] In step S204, if the cumulative amount of at least one limit period is greater than the limit of the corresponding limit period, the transaction request of the target user is rejected.

[0043] Specifically, if the cumulative amount of at least one limit period is greater than the limit of the corresponding limit period, for example, the daily cumulative amount exceeds the daily limit or the monthly cumulative amount exceeds the monthly limit, the transaction request of the target user is rejected, thereby realizing the credit card limit.

[0044] Through the above embodiment, in the credit card limit method, the daily limit period, the monthly limit period, the semi-annual limit period, and the annual limit period can be calculated by the daily cumulative amount and the monthly cumulative amount in the cumulative amount record of the target user and the current transaction amount. By comparing the cumulative amount of each limit period with the limit of the corresponding limit period, if the cumulative amount exceeds the limit, the transaction request of the target user is rejected, thereby realizing the limit without scanning a large amount of transaction data within the limit period, greatly reducing the calculation amount, and solving the problem of high delay in calculating the credit card limit in the prior art.

[0045] In order to calculate the cumulative amount of each limit period, in an optional embodiment, the step S203 includes:

[0046] Step S2031, in the case where the limit period is the daily limit period, calculating the sum of the current transaction amount and the daily cumulative amount to obtain the cumulative amount of the daily limit period;

[0047] Step S2032, in the case where the limit period is the monthly limit period, calculating the sum of the current transaction amount and the monthly cumulative amount of the month in which the current transaction occurs to obtain the cumulative amount of the monthly limit period;

[0048] Step S2033, in the case where the limit period is the semi-annual limit period, calculating the sum of the current transaction amount and all the monthly cumulative amounts within the semi-annual limit period to obtain the cumulative amount of the semi-annual limit period;

[0049] Step S2034, in the case where the limit period is the annual limit period, calculating the sum of the current transaction amount and all the monthly cumulative amounts within the limit period to obtain the cumulative amount of the annual limit period.

[0050] In the above embodiments, the current transaction amount is accumulated to the daily cumulative amount to obtain the cumulative amount of the daily limit period, the current transaction amount is accumulated to the monthly cumulative amount of the current month to obtain the cumulative amount of the monthly limit period, the sum of the current transaction amount and the monthly cumulative amounts of the recent half year is calculated to obtain the cumulative amount of the semi-annual limit period, and the sum of the current transaction amount and the monthly cumulative amounts of the recent year is calculated to obtain the cumulative amount of the annual limit period.

[0051] In order to ensure the accuracy of the cumulative amount, in an optional embodiment, before obtaining the cumulative amount record of the target user, the method further comprises:

[0052] Step S301, obtaining the time of the most recent valid financial transaction, the time of the most recent valid financial transaction being the time of the most recent valid credit card transaction;

[0053] Step S302, in the case where the time of the most recent valid financial transaction is not on the current day, clearing the daily cumulative amount;

[0054] Step S303, in the case where the time of the most recent valid financial transaction is not in the current month, clearing the monthly cumulative amounts corresponding to the months after the month in which the time of the most recent valid financial transaction occurs.

[0055] In the above embodiment, the time of the latest valid financial transaction in the user cumulative amount table is obtained, and if the date corresponding to the current time is not the current date, the daily cumulative amount is cleared. The time of the latest valid financial transaction in the user cumulative amount table is obtained, the year and month corresponding to the latest valid financial transaction are obtained, and the month corresponding to the latest valid financial transaction and the current transaction is obtained. The month cumulative amount of the corresponding month is cleared, which prevents the transaction amount of an invalid transaction from being accumulated in the daily cumulative amount or the month cumulative amount, thereby ensuring the accuracy of the cumulative amount.

[0056] Specifically, as shown in Figure 3 the time of the latest valid financial transaction is obtained, and if the time of the latest valid financial transaction is more than one year away from the current date, i.e., currentYear>lastYear+1, for example, the time of the latest valid financial transaction is in 2023, and the current date is in 2025, or currentYear=lastYear+1 and currentMonth≥lastMonth, for example, the time of the latest valid financial transaction is in March 2024, and the current date is in March 2025, indicating that there is no valid transaction in the past year, then the month cumulative amounts from January to December are cleared. If the time of the latest valid financial transaction is not more than one year away from the current date, one case is currentYear=lastYear+1 and currentMonth<lastMonth, for example, the time of the latest valid financial transaction is in September 2024, and the current date is in March 2025, then the month cumulative amounts from January to March are cleared, and the month cumulative amounts from October to December are cleared. The time of the latest valid financial transaction is in December 2024, and the current date is in March 2025, then only the month cumulative amounts from January to March are cleared. Another case is currentYear=lastYear and currentMonth>lastMonth, for example, the time of the latest valid financial transaction is in March 2025, and the current date is in September 2025, then the month cumulative amounts from April to September are cleared. If it does not belong to these cases, then the month cumulative amounts from January to December will not change.

[0057] In order to complete a normal transaction, in an optional embodiment, after the cumulative amount of each limit period is calculated based on the current transaction amount and the cumulative amount record, the method further comprises:

[0058] Step S401, in the case where the cumulative amount of each limit period is less than or equal to the limit of the corresponding limit period, the current transaction amount is accumulated in the daily cumulative amount and the month cumulative amount of the current month.

[0059] In the above embodiments, if the cumulative amount of each of the above limit periods is less than or equal to the limit of the corresponding limit period, the limit control is not triggered, and the transaction can be normally processed. After the transaction is completed, the current transaction amount is accumulated into the daily cumulative amount and the monthly cumulative amount of the month.

[0060] For convenience of calculation, in an optional embodiment, the step S203 further includes:

[0061] In step S2034, the sum of the daily cumulative amount and the current transaction amount is determined as the cumulative amount of the daily limit period.

[0062] In step S2035, the sum of the monthly cumulative amount of the month and the current transaction amount is determined as the cumulative amount of the monthly limit period.

[0063] In step S2036, the sum of the current transaction amount, the monthly cumulative amount of the month, and the monthly cumulative amounts of the previous five months is calculated as the cumulative amount of the half-year limit period.

[0064] In step S2037, the sum of the current transaction amount, the monthly cumulative amount of the month, and the monthly cumulative amounts of the previous eleven months is calculated as the cumulative amount of the annual limit period.

[0065] In the above embodiments, the user cumulative amount table includes the monthly cumulative amounts of January to December. The sum of the current transaction amount and the daily cumulative amount is the cumulative amount of the daily limit period. The sum of the current transaction amount and the monthly cumulative amount of the month is the cumulative amount of the monthly limit period. For example, if the current date is March, the sum of the current transaction amount and the monthly cumulative amount of March is the cumulative amount of the monthly limit period. The sum of the current transaction amount, the monthly cumulative amount of the month, and the monthly cumulative amounts of the previous five months is calculated as the cumulative amount of the half-year limit period. For example, if the current date is March 2025, the sum of the current transaction amount, the monthly cumulative amounts of January to March, and the monthly cumulative amounts of October to December is calculated as the cumulative amount of the half-year limit period. The sum of the current transaction amount, the monthly cumulative amount of the month, and the monthly cumulative amounts of the previous eleven months is calculated as the cumulative amount of the annual limit period. For example, the sum of the current transaction amount and the monthly cumulative amounts of January to December is calculated as the cumulative amount of the half-year limit period. The calculation is simple and does not require scanning of a large amount of transaction data.

[0066] In order to implement the credit card limit, in an optional embodiment, the step S204 includes:

[0067] Step S2041, in the case that the daily cumulative amount is greater than the daily limit, the transaction request of the target user is rejected;

[0068] Step S2042, in the case that the monthly cumulative amount is greater than the monthly limit, the transaction request of the target user is rejected;

[0069] Step S2043, in the case that the cumulative amount of the semi-annual limit period is greater than the semi-annual limit, the transaction request of the target user is rejected;

[0070] Step S2044, in the case that the cumulative amount of the annual limit period is greater than the annual limit, the transaction request of the target user is rejected.

[0071] In the above embodiment, the daily cumulative amount, the monthly cumulative amount, the cumulative amount of the semi-annual limit period and the cumulative amount of the annual limit period cannot exceed the corresponding limit, otherwise the transaction request of the target user is rejected, thereby realizing the credit card limit control.

[0072] In order to facilitate inquiry, in an optional embodiment, before obtaining the cumulative amount record of the target user, the method further comprises:

[0073] Step S501, in the case that the target user successfully applies for a credit card, a plurality of record indexes are constructed, the record indexes comprising the user unique identifier, the latest valid financial transaction time, the daily cumulative amount and the monthly cumulative amount from January to December;

[0074] Step S502, in the plurality of record indexes, the user unique identifier of the target user, the latest valid financial transaction time, the daily cumulative amount and the monthly cumulative amount from January to December are recorded as 0, thereby obtaining the cumulative amount record of the target user.

[0075] In the above embodiment, the user cumulative amount table is shown in Table 1, and the core data table structure field mainly comprises: the user unique identifier, the latest valid financial transaction time (the transaction time corresponding to the transaction with the cumulative amount and success), the daily cumulative amount, the cumulative amount of each month from January to December. The daily and monthly cumulative amount records of the user are queried according to the user unique identifier.

[0076] Table 1

[0077]

[0078] In order to enable those skilled in the art to more clearly understand the technical solutions of the present application, the implementation process of the credit card limit method of the present application will be described in detail below in conjunction with specific embodiments.

[0079] This embodiment relates to a specific credit card limit method, as shown in Figure 4 comprising the following steps:

[0080] Step 1: Read the user cumulative amount table. As shown in Table 1, the core data table structure fields mainly include: user unique identifier, the latest valid financial transaction time (the transaction time corresponding to the cumulative amount and successful transaction), the daily cumulative amount, and the cumulative amount of each month from January to December. According to the user unique identifier, the daily and monthly cumulative amount records of the user are queried out.

[0081] Step 2: Perform data cleaning.

[0082] / / Pseudocode 1: Daily cumulative amount cleaning

[0083] if (last_valid_trade_time.date!= today's date) {

[0084] daily_accumulated = 0; / / Clear and re-calculate

[0085] }

[0086] 1) Daily cumulative amount cleaning. As shown in the above pseudocode, the latest valid financial transaction time in the user cumulative amount table is obtained. If the date corresponding to the current time is not the current date, the daily cumulative amount is cleared.

[0087] 2) Monthly cumulative amount cleaning. As shown in Figure 3 , the latest valid financial transaction time in the user cumulative amount table is obtained, and the corresponding year and month are obtained. At the same time, the month and year corresponding to the current date are obtained, and the cumulative amount of the corresponding month between the latest valid financial transaction and the current transaction is cleared. The specific months that need to be cleaned are shown in Figure 3 . The pseudocode for cleaning the monthly cumulative amount between startMonth and endMonth is as follows:

[0088] / / Pseudocode 2: Clean monthly cumulative amount between startMonth and endMonth

[0089] clear_month_amount(int startMonth, int endMonth) {

[0090] for(int m=startMonth; m<=endMonth; m++) {

[0091] set_month_amount(m, 0); / / Set the monthly cumulative amount value of a certain month to 0

[0092] }

[0093] }

[0094] Step 3: Perform the amount accumulation.

[0095] 1) Daily accumulated amount. Accumulate the current transaction amount to the daily accumulated amount, pseudo code as follows:

[0096] / / Pseudo code 3: Daily accumulated amount accumulation

[0097] daily_accumulated += current transaction amount; / / Daily accumulation

[0098] 2) Monthly accumulated amount. Accumulate the current transaction amount to the monthly accumulated amount of the current month, pseudo code as follows:

[0099] / / Pseudo code 4: Monthly accumulated amount accumulation

[0100] int current_month = CurrentTime.getMonth(); / / Get the current month

[0101] set_month_amount(current_month, get_month_amount(current_month) + current transaction amount);

[0102] 3) Half-year accumulated amount processing. There is no corresponding storage field for half-year accumulated amount, only need to dynamically accumulate the monthly accumulated amount of the past half year, pseudo code as follows:

[0103] / / Pseudo code 5: Half-year accumulated amount accumulation

[0104] get_half_year_amount(int month) {

[0105] half_year_amount = 0;

[0106] for (int i=0;i<6;i++) {

[0107] if (month == 0) {

[0108] month = 12;

[0109] }

[0110] half_year_amount = add(half_year_amount, get_month_amount(month));

[0111] month--;

[0112] }

[0113] }

[0114] 4)Yearly accumulated amount processing. There is no corresponding storage field for half-year accumulated amount, only the accumulated amount of twelve months needs to be accumulated, the pseudo code is as follows:

[0115] / / Pseudo code 6: Yearly accumulated amount accumulation

[0116] get_one_year_amount() {

[0117] one_year_amount = 0;

[0118] for (int month=1;month<=12;month++) {

[0119] one_year_amount = add(one_year_amount, get_month_amount(month));

[0120] }

[0121] }

[0122] Step 4: Compare the quota strategy, execute or reject the transaction. Compare the preset threshold, compare whether the user exceeds the quota.

[0123] / / Pseudo code 7: Compare the quota strategy, execute or reject the transaction.

[0124] IF daily_accumulated > daily quota THEN reject the transaction

[0125] IF half_year_sum > half-year quota THEN reject the transaction

[0126] IF year_sum > annual quota THEN reject the transaction

[0127] Step 5: Update the user accumulated amount table. After step 2, execute data cleaning, execute amount accumulation, if the transaction is successful, update the daily accumulated amount, the monthly accumulated amount, the month accumulated amount that needs to be updated after data cleaning, to the database in real time.

[0128] The embodiment of the present application further provides a credit card quota device. It should be noted that the credit card quota device of the embodiment of the present application can be used to execute the credit card quota method provided by the embodiment of the present application. The device is used to realize the above-mentioned embodiment and preferred embodiment, and the description has been made and will not be repeated. As used below, the term "module" can be a combination of software and / or hardware that realizes a predetermined function. Although the device described in the following embodiment is preferably realized in software, the realization of hardware or a combination of software and hardware is also possible and conceived.

[0129] The credit card quota device provided by the embodiment of the present application is introduced below.

[0130] Figure 5 is a schematic diagram of the credit card quota device according to the embodiment of the present application. As shown in Figure 5 , the device comprises:

[0131] The first acquisition unit 10 is configured to acquire the cumulative amount record of the target user in the case of receiving the transaction request of the target user, wherein the cumulative amount record comprises a user unique identifier, a daily cumulative amount and a plurality of monthly cumulative amounts.

[0132] The analysis unit 20 is configured to analyze the transaction request to obtain a current transaction amount.

[0133] The first calculation unit 30 is configured to calculate the cumulative amount of each quota period according to the current transaction amount and the cumulative amount record, wherein the quota period comprises a daily quota period, a monthly quota period, a semi-annual quota period and an annual quota period.

[0134] The processing unit 40 is configured to reject the transaction request of the target user in the case that the cumulative amount of at least one of the quota periods is greater than the quota of the corresponding quota period.

[0135] In the credit card quota device, the daily cumulative amount and the plurality of monthly cumulative amounts in the cumulative amount record of the target user and the current transaction amount are used to calculate the cumulative amount of the daily quota period, the monthly quota period, the semi-annual quota period and the annual quota period, and the cumulative amount is compared with the quota of the corresponding quota period. If the cumulative amount exceeds the quota, the transaction request of the target user is rejected, so that the quota is realized, a large amount of transaction data in the quota period does not need to be scanned, the calculation amount is greatly reduced, and the problem of high delay in the credit card quota calculation in the prior art is solved.

[0136] In order to calculate the cumulative amount of each quota period, in an optional embodiment, the first calculation unit comprises:

[0137] The first calculation module is configured to calculate the sum of the current transaction amount and the daily cumulative amount to obtain the cumulative amount of the daily limit period when the limit period is the daily limit period.

[0138] The second calculation module is configured to calculate the sum of the current transaction amount and the monthly cumulative amount of the month in which the current transaction is made to obtain the cumulative amount of the monthly limit period when the limit period is the monthly limit period.

[0139] The third calculation module is configured to calculate the sum of the current transaction amount and all the monthly cumulative amounts in the half-year limit period to obtain the cumulative amount of the half-year limit period when the limit period is the half-year limit period.

[0140] The fourth calculation module is configured to calculate the sum of the current transaction amount and all the monthly cumulative amounts in the limit period to obtain the cumulative amount of the annual limit period when the limit period is the annual limit period.

[0141] In the embodiments, the current transaction amount is accumulated to the daily cumulative amount to obtain the cumulative amount of the daily limit period, the current transaction amount is accumulated to the monthly cumulative amount of the current month to obtain the cumulative amount of the monthly limit period, the sum of the current transaction amount and the monthly cumulative amounts in the recent half year is calculated to obtain the cumulative amount of the half-year limit period, and the sum of the current transaction amount and the monthly cumulative amounts in the recent year is calculated to obtain the cumulative amount of the annual limit period.

[0142] To ensure the accuracy of the cumulative amount, in an optional embodiment, the device further comprises:

[0143] The second acquisition unit is configured to acquire the time of the most recent valid financial transaction before acquiring the cumulative amount record of the target user, the time of the most recent valid financial transaction being the time of the most recent valid credit card transaction.

[0144] The first zeroing unit is configured to zero the daily cumulative amount when the time of the most recent valid financial transaction is not in the current day.

[0145] The second zeroing unit is configured to zero the monthly cumulative amounts corresponding to the months after the month in which the time of the most recent valid financial transaction is located when the time of the most recent valid financial transaction is not in the current month.

[0146] In the above embodiment, the time of the latest valid financial transaction in the user cumulative amount table is obtained, and if the date corresponding to the current time is not the current date, the daily cumulative amount is cleared. The time of the latest valid financial transaction in the user cumulative amount table is obtained, the year and month corresponding to the latest valid financial transaction are obtained, and the month corresponding to the latest valid financial transaction and the current transaction is obtained. The month cumulative amount of the corresponding month is cleared, which prevents the transaction amount of an invalid transaction from being accumulated in the daily cumulative amount or the month cumulative amount, thereby ensuring the accuracy of the cumulative amount.

[0147] Specifically, as shown in Figure 3 the time of the latest valid financial transaction is obtained, and if the time of the latest valid financial transaction is more than one year away from the current date, i.e., currentYear>lastYear+1, for example, the time of the latest valid financial transaction is in 2023, and the current date is in 2025, or currentYear=lastYear+1 and currentMonth≥lastMonth, for example, the time of the latest valid financial transaction is in March 2024, and the current date is in March 2025, indicating that there is no valid transaction in the past year, then the month cumulative amounts from January to December are cleared. If the time of the latest valid financial transaction is not more than one year away from the current date, one case is currentYear=lastYear+1 and currentMonth<lastMonth, for example, the time of the latest valid financial transaction is in September 2024, and the current date is in March 2025, then the month cumulative amounts from January to March are cleared, and the month cumulative amounts from October to December are cleared. The time of the latest valid financial transaction is in December 2024, and the current date is in March 2025, then only the month cumulative amounts from January to March are cleared. Another case is currentYear=lastYear and currentMonth>lastMonth, for example, the time of the latest valid financial transaction is in March 2025, and the current date is in September 2025, then the month cumulative amounts from April to September are cleared.

[0148] To complete a normal transaction, in an optional embodiment, the above device further comprises:

[0149] The accumulation unit is configured to, after calculating the cumulative amount of each limit period according to the current transaction amount and the cumulative amount record, if the cumulative amount of each limit period is less than or equal to the limit of the corresponding limit period, accumulate the current transaction amount to the daily cumulative amount and the month cumulative amount of the current month.

[0150] In the above embodiment, if the cumulative amount of each of the above limit periods is less than or equal to the limit of the corresponding limit period, the limit control is not triggered, and the transaction can be normally processed. After the transaction is completed, the current transaction amount is accumulated to the daily cumulative amount and the monthly cumulative amount of the month.

[0151] To facilitate calculation, in an optional embodiment, the first calculation unit further comprises:

[0152] The first determination unit is configured to determine the sum of the daily cumulative amount and the current transaction amount as the cumulative amount of the daily limit period.

[0153] The second determination unit is configured to determine the sum of the monthly cumulative amount of the month and the current transaction amount as the cumulative amount of the monthly limit period.

[0154] The second calculation unit is configured to calculate the sum of the current transaction amount, the monthly cumulative amount of the month, and the monthly cumulative amounts of the five months before the month to obtain the cumulative amount of the half-year limit period.

[0155] The third calculation unit is configured to calculate the sum of the current transaction amount, the monthly cumulative amount of the month, and the monthly cumulative amounts of the eleven months before the month to obtain the cumulative amount of the annual limit period.

[0156] In the above embodiment, the user cumulative amount table comprises the monthly cumulative amounts of January to December. The sum of the current transaction amount and the daily cumulative amount is the cumulative amount of the daily limit period, and the sum of the current transaction amount and the monthly cumulative amount of the month is the cumulative amount of the monthly limit period. For example, if the current date is March, the sum of the current transaction amount and the monthly cumulative amount of March is the cumulative amount of the monthly limit period. The sum of the current transaction amount, the monthly cumulative amount of the month, and the monthly cumulative amounts of the five months before the month is calculated to obtain the cumulative amount of the half-year limit period. For example, if the current date is March 2025, the sum of the current transaction amount, the monthly cumulative amounts of January to March, and the monthly cumulative amounts of October to December is calculated to obtain the cumulative amount of the half-year limit period. The sum of the current transaction amount, the monthly cumulative amount of the month, and the monthly cumulative amounts of the eleven months before the month is calculated to obtain the cumulative amount of the annual limit period. For example, the sum of the current transaction amount and the monthly cumulative amounts of January to December is calculated to obtain the cumulative amount of the half-year limit period. The calculation is simple and does not require scanning of a large amount of transaction data.

[0157] To implement the credit card limit, in an optional embodiment, the processing unit comprises:

[0158] The first processing module is configured to reject the transaction request of the target user when the daily cumulative amount is greater than the daily limit;

[0159] The second processing module is configured to reject the transaction request of the target user when the monthly cumulative amount is greater than the monthly limit.

[0160] The third processing module is configured to reject the transaction request of the target user when the cumulative amount of the semi-annual limit period is greater than the semi-annual limit.

[0161] The fourth processing module is configured to reject the transaction request of the target user when the cumulative amount of the annual limit period is greater than the annual limit.

[0162] In the above embodiments, the daily cumulative amount, the monthly cumulative amount, the cumulative amount of the semi-annual limit period, and the cumulative amount of the annual limit period cannot exceed the corresponding limits, otherwise the transaction request of the target user is rejected, thereby achieving credit card limit control.

[0163] For easy query, in an optional embodiment, the device further comprises:

[0164] The construction unit is configured to, before obtaining the cumulative amount record of the target user, construct a plurality of record indexes when the target user successfully applies for a credit card, the record indexes comprising the user unique identifier, the time of the last valid financial transaction, the daily cumulative amount, and the monthly cumulative amount from January to December.

[0165] The record unit is configured to record, in the plurality of record indexes, the user unique identifier of the target user, the time of the last valid financial transaction as empty, the daily cumulative amount as 0, and the monthly cumulative amount from January to December as 0 to obtain the cumulative amount record of the target user.

[0166] In the above embodiments, the user cumulative amount table is shown in Table 1, and the core data table structure field mainly comprises: the user unique identifier, the time of the last valid financial transaction (the transaction time corresponding to the cumulative amount of the transaction that is successful), the daily cumulative amount, and the cumulative amount of each month from January to December. The daily and monthly cumulative amount records of the user are queried according to the user unique identifier.

[0167] The credit card limit device comprises a processor and a memory, and the first obtaining unit, the parsing unit, the first calculating unit, and the processing unit are all stored in the memory as program units, and the corresponding functions are realized by the processor executing the program units stored in the memory. The modules are all located in the same processor; or, the modules are located in different processors in any combination.

[0168] The processor comprises a core, and the core is used to call corresponding program units in the memory.

[0169] The memory can comprise a non-permanent memory in a computer readable medium, a random access memory (RAM) and / or a non-volatile memory such as a read-only memory (ROM) or a flash memory (flash RAM), and the memory comprises at least one memory chip.

[0170] The embodiment of the present application provides a computer readable storage medium, and the computer readable storage medium comprises a stored program.

[0171] Specifically, the credit card limit method comprises:

[0172] In step S201, when a transaction request of a target user is received, a cumulative amount record of the target user is acquired, and the cumulative amount record comprises a user unique identifier, a daily cumulative amount and a plurality of monthly cumulative amounts.

[0173] In step S202, the transaction request is parsed to obtain a current transaction amount.

[0174] In step S203, a cumulative amount of each limit period is calculated according to the current transaction amount and the cumulative amount record, and the limit period comprises a daily limit period, a monthly limit period, a semi-annual limit period and an annual limit period.

[0175] In step S204, when the cumulative amount of at least one limit period is greater than a limit of the corresponding limit period, the transaction request of the target user is rejected.

[0176] The embodiment of the present application provides a processor, and the processor is used to run a program.

[0177] Specifically, the credit card limit method comprises:

[0178] In step S201, when a transaction request of a target user is received, a cumulative amount record of the target user is acquired, and the cumulative amount record comprises a user unique identifier, a daily cumulative amount and a plurality of monthly cumulative amounts.

[0179] In step S202, the transaction request is parsed to obtain a current transaction amount.

[0180] Step S203, calculating the cumulative amount of each limit period according to the current transaction amount and the cumulative amount record, wherein the limit period includes a daily limit period, a monthly limit period, a semi-annual limit period and an annual limit period.

[0181] Step S204, rejecting the transaction request of the target user in the case that the cumulative amount of at least one limit period is greater than the limit of the corresponding limit period.

[0182] The credit card system provided by the embodiment of the present application comprises a processor, a memory, and a program stored in the memory and executable on the processor, and the processor implements at least the following steps when executing the program:

[0183] Step S201, obtaining the cumulative amount record of the target user in the case that the transaction request of the target user is received, wherein the cumulative amount record comprises a user unique identifier, a daily cumulative amount and a plurality of monthly cumulative amounts.

[0184] Step S202, parsing the transaction request to obtain a current transaction amount.

[0185] Step S203, calculating the cumulative amount of each limit period according to the current transaction amount and the cumulative amount record, wherein the limit period includes a daily limit period, a monthly limit period, a semi-annual limit period and an annual limit period.

[0186] Step S204, rejecting the transaction request of the target user in the case that the cumulative amount of at least one limit period is greater than the limit of the corresponding limit period.

[0187] The present application also provides a computer program product adapted to execute the program initialized with at least the following method steps when executed on a data processing device:

[0188] Step S201, obtaining the cumulative amount record of the target user in the case that the transaction request of the target user is received, wherein the cumulative amount record comprises a user unique identifier, a daily cumulative amount and a plurality of monthly cumulative amounts.

[0189] Step S202, parsing the transaction request to obtain a current transaction amount.

[0190] Step S203, calculating the cumulative amount of each limit period according to the current transaction amount and the cumulative amount record, wherein the limit period includes a daily limit period, a monthly limit period, a semi-annual limit period and an annual limit period.

[0191] Step S204, rejecting the transaction request of the target user in the case that the cumulative amount of at least one limit period is greater than the limit of the corresponding limit period.

[0192] It should be apparent to those skilled in the art that the modules or steps of the application described above can be implemented using general computing devices, which can be centralized on a single computing device or distributed across a network of multiple computing devices, which can be implemented using program code executable by a computing device, which can be stored in a storage device for execution by a computing device, and in some cases, the steps shown or described can be performed in a different order than shown, or can be implemented as separate integrated circuit modules, or as a single integrated circuit module, and thus the application is not limited to any particular combination of hardware and software.

[0193] Those skilled in the art will appreciate that embodiments of the application can be further implemented as a method, system, or computer program product. Accordingly, the application can be embodied in the form of an entirely hardware embodiment, an entirely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, the application can be embodied in the form of a computer program product on one or more computer readable storage media (including, but not limited to, disk memory, CD-ROMs, optical storage media, etc.) having computer usable program code embodied thereon.

[0194] The present application is described herein with reference to the drawings, which are described below. The application is described with reference to the flow diagrams and / or block diagrams of the methods, apparatus (systems), and computer program products according to embodiments of the application. It will be understood that each block of the flow diagrams and / or block diagrams, and combinations of blocks in the flow diagrams and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general purpose computer, special purpose computer, embedded processing device, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flow diagrams and / or block diagrams block or blocks. Figure 1 The flow diagrams and / or block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of apparatuses (systems), methods and computer program products according to various embodiments of the present application. In this regard, each flow diagram and / or block diagram can represent a method, a system, or a computer program product. In some embodiments, the flow diagrams and / or block diagrams can represent a computer program product that can be implemented by a computer or other programmable data processing apparatus. In some embodiments, the flow diagrams and / or block diagrams can represent a computer program product that can be implemented by a computer or other programmable data processing apparatus. Figure 1 The flow diagrams and / or block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of apparatuses (systems), methods and computer program products according to various embodiments of the present application. In this regard, each flow diagram and / or block diagram can represent a method, a system, or a computer program product. In some embodiments, the flow diagrams and / or block diagrams can represent a computer program product that can be implemented by a computer or other programmable data processing apparatus. In some embodiments, the flow diagrams and / or block diagrams can represent a computer program product that can be implemented by a computer or other programmable data processing apparatus. The flow diagrams and / or block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of apparatuses (systems), methods and computer program products according to various embodiments of the present application. In this regard, each flow diagram and / or block diagram can represent a method, a system, or a computer program product. In some embodiments, the flow diagrams and / or block diagrams can represent a computer program product that can be implemented by a computer or other programmable data processing apparatus. In some embodiments, the flow diagrams and / or block diagrams can represent a computer program product that can be implemented by a computer or other programmable data processing apparatus.

[0195] The flow diagrams and / or block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of apparatuses (systems), methods and computer program products according to various embodiments of the present application. In this regard, each flow diagram and / or block diagram can represent a method, a system, or a computer program product. In some embodiments, the flow diagrams and / or block diagrams can represent a computer program product that can be implemented by a computer or other programmable data processing apparatus. In some embodiments, the flow diagrams and / or block diagrams can represent a computer program product that can be implemented by a computer or other programmable data processing apparatus. Figure 1 The flow diagrams and / or block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of apparatuses (systems), methods and computer program products according to various embodiments of the present application. In this regard, each flow diagram and / or block diagram can represent a method, a system, or a computer program product. In some embodiments, the flow diagrams and / or block diagrams can represent a computer program product that can be implemented by a computer or other programmable data processing apparatus. In some embodiments, the flow diagrams and / or block diagrams can represent a computer program product that can be implemented by a computer or other programmable data processing apparatus. Figure 1 The flow diagrams and / or block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of apparatuses (systems), methods and computer program products according to various embodiments of the present application. In this regard, each flow diagram and / or block diagram can represent a method, a system, or a computer program product. In some embodiments, the flow diagrams and / or block diagrams can represent a computer program product that can be implemented by a computer or other programmable data processing apparatus. In some embodiments, the flow diagrams and / or block diagrams can represent a computer program product that can be implemented by a computer or other programmable data processing apparatus. The flow diagrams and / or block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of apparatuses (systems), methods and computer program products according to various embodiments of the present application. In this regard, each flow diagram and / or block diagram can represent a method, a system, or a computer program product. In some embodiments, the flow diagrams and / or block diagrams can represent a computer program product that can be implemented by a computer or other programmable data processing apparatus. In some embodiments, the flow diagrams and / or block diagrams can represent a computer program product that can be implemented by a computer or other programmable data processing apparatus.

[0196] These computer program instructions can also be loaded into a computer or other programmable data processing devices, so that a series of operational steps are performed on the computer or other programmable devices to generate a computer-implemented process, thus the instructions executed on the computer or other programmable devices provide a process for implementing the functions specified in the flowchart Figure 1 2one or more flows and / or blocks Figure 1 2one or more flows and / or blocks 2

[0197] 2In a typical configuration, a computing device includes one or more processors (CPUs), input / output interfaces, network interfaces, and memory. 2

[0198] 2The memory can include non-persistent memory and / or volatile memory, such as a random access memory (RAM) including a cache area for the temporary storage of data. The memory can also include non-volatile memory, such as read only memory (ROM), electrically programmable read only memory (EPROM), electrically erasable programmable read only memory (EEPROM), flash memory, or non-volatile random access memory (NVRAM). The memory can also inoperable with a database, data structures, program instructions, or other data. 2

[0199] 2Computer readable media includes permanent and non-permanent, removable and non-removable media that can be implemented by any method or technology for storing information. Information can be computer readable instructions, data structures, program modules or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read only memory (ROM), electrically erasable programmable read only memory (EEPROM), flash memory or other memory technology, compact disc read only memory (CD-ROM), digital versatile disc (DVD) or other optical storage, magnetic cassette, magnetic disk storage or other magnetic storage devices or any other non-transmission medium that can be used to store information that can be accessed by a computing device. According to the definition herein, computer readable media does not include transitory media, such as modulated data signals and carriers. 2

[0200] 2The technical features of the above-described embodiments can be combined in any manner. In order to make the description simple, all possible combinations of the technical features in the above-described embodiments are not described, however, as long as the combination of the technical features does not exist contradictory, it should be considered as the scope of the present specification. 2

[0201] 2It should also be noted that the terms "comprising", "comprises" or any other variations thereof are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but can include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element preceded by "comprises a" does not, without more constraints, foreclose the existence of additional identical elements in the process, method, article, or apparatus that comprises the element.

[0202] From the above description, it can be seen that the above-mentioned embodiments of the present application achieve the following technical effects:

[0203] 1) In the credit card limit method of the present application, the daily cumulative amount and the multiple monthly cumulative amounts in the cumulative amount record of the target user and the current transaction amount are used to calculate the cumulative amounts of the daily limit period, the monthly limit period, the semi-annual limit period, and the annual limit period, which are compared with the limits of the corresponding limit periods. If the limit is exceeded, the transaction request of the target user is rejected, thereby realizing the limit without the need to scan a large amount of transaction data within the limit period, greatly reducing the calculation amount and solving the problem of high delay in credit card limit calculation in the prior art.

[0204] 2) In the credit card limit device of the present application, the daily cumulative amount and the multiple monthly cumulative amounts in the cumulative amount record of the target user and the current transaction amount are used to calculate the cumulative amounts of the daily limit period, the monthly limit period, the semi-annual limit period, and the annual limit period, which are compared with the limits of the corresponding limit periods. If the limit is exceeded, the transaction request of the target user is rejected, thereby realizing the limit without the need to scan a large amount of transaction data within the limit period, greatly reducing the calculation amount and solving the problem of high delay in credit card limit calculation in the prior art.

[0205] The above only describes the preferred embodiments of the present application and is not intended to limit the present application. For those skilled in the art, the present application can have various modifications and changes. Any modification, equivalent replacement, improvement, etc. made within the spirit and principles of the present application shall be included in the protection scope of the present application.

Claims

1. A method for setting credit card limits, characterized in that, include: Upon receiving a transaction request from a target user, the system retrieves the target user's cumulative amount record, which includes the user's unique identifier, the cumulative amount for the day, and the cumulative amount for multiple months. The transaction request is parsed to obtain the current transaction amount; The cumulative amount for each limit period is calculated based on the current transaction amount and the cumulative amount record. The limit period includes daily limit period, monthly limit period, semi-annual limit period and annual limit period. If the cumulative amount in at least one of the limit periods exceeds the limit for the corresponding limit period, the transaction request of the target user is rejected.

2. The method according to claim 1, characterized in that, The cumulative amount for each limit period is calculated based on the current transaction amount and the cumulative amount record, including: When the limit period is the daily limit period, the sum of the current transaction amount and the cumulative amount for the day is calculated to obtain the cumulative amount for the daily limit period; When the limit period is the monthly limit period, the sum of the current transaction amount and the monthly cumulative amount of the current month is calculated to obtain the cumulative amount of the monthly limit period; When the limit period is the six-month limit period, the sum of the current transaction amount and all the monthly cumulative amounts within the six-month limit period is calculated to obtain the cumulative amount for the six-month limit period; If the limit period is an annual limit period, the sum of the current transaction amount and the cumulative monthly amount within the annual limit period is calculated to obtain the cumulative amount for the annual limit period.

3. The method according to claim 1, characterized in that, Before obtaining the target user's cumulative amount records, the method further includes: Obtain the time of the most recent valid financial transaction, which is the time of the most recent valid credit card transaction; If the most recent valid financial transaction was not made on the same day, the cumulative amount for that day will be cleared to zero. If the most recent valid financial transaction is not in the current month, the cumulative amount for the month following the month in which the most recent valid financial transaction occurred will be cleared to zero.

4. The method according to claim 1, characterized in that, After calculating the cumulative amount for each limit period based on the current transaction amount and the cumulative amount record, the method further includes: If the cumulative amount for each of the aforementioned limit periods is less than or equal to the limit for the corresponding limit period, the current transaction amount is added to the daily cumulative amount and the monthly cumulative amount for the current month.

5. The method according to claim 1, characterized in that, The cumulative amount for each limit period is calculated based on the current transaction amount and the cumulative amount record, including: The sum of the current transaction amount and the cumulative amount for the day is determined as the cumulative amount for the daily limit period; The sum of the current transaction amount and the monthly cumulative amount for the current month is determined as the cumulative amount for the monthly limit period; The cumulative amount for the six-month limit period is obtained by summing the current transaction amount, the monthly cumulative amount for the current month, and the monthly cumulative amounts for the previous five months. The cumulative amount for the annual limit period is obtained by summing the current transaction amount, the monthly cumulative amount for the current month, and the monthly cumulative amounts for the previous 11 months.

6. The method according to claim 5, characterized in that, If the cumulative amount in at least one of the specified limit periods exceeds the limit for the corresponding limit period, the transaction request of the target user is rejected, including: If the cumulative amount for the day exceeds the daily limit, the transaction request of the target user will be rejected. If the cumulative monthly amount exceeds the monthly limit, the target user's transaction request will be rejected. If the cumulative amount over the six-month limit period exceeds the six-month limit, the target user's transaction request will be rejected. If the cumulative amount over the annual limit period exceeds the annual limit, the target user's transaction request will be rejected.

7. The method according to any one of claims 1 to 6, characterized in that, Before obtaining the target user's cumulative amount records, the method further includes: If the target user successfully applies for a credit card, multiple record indicators are constructed, including the user's unique identifier, the time of the most recent valid financial transaction, the cumulative amount for the day, and the cumulative amount for the month from January to December; Among the various recorded indicators, the cumulative amount record of the target user is obtained by recording the target user's unique identifier, the time of the most recent valid financial transaction being empty, the daily cumulative amount being 0, and the monthly cumulative amount from January to December being 0.

8. A credit card limit setting device, characterized in that, include: The first acquisition unit is used to acquire the cumulative amount record of the target user upon receiving a transaction request from the target user. The cumulative amount record includes the user's unique identifier, the cumulative amount for the day, and the cumulative amount for multiple months. The parsing unit is used to parse the transaction request to obtain the current transaction amount; The first calculation unit is used to calculate the cumulative amount for each limit period based on the current transaction amount and the cumulative amount record. The limit period includes daily limit period, monthly limit period, semi-annual limit period and annual limit period. The processing unit is configured to reject the target user's transaction request if the cumulative amount in at least one of the limit periods exceeds the limit of the corresponding limit period.

9. A computer program product, comprising a computer program, characterized in that, When the computer program is executed by a processor, it implements the method described in any one of claims 1 to 7.

10. A credit card system, characterized in that, include: One or more processors, a memory, and one or more programs, wherein the one or more programs are stored in the memory and configured to be executed by the one or more processors, the one or more programs comprising methods for performing any one of claims 1 to 7.

Images