CN115482007A - Method, device, equipment and storage medium for processing transaction request - Google Patents

Method, device, equipment and storage medium for processing transaction request Download PDF

Info

Publication number
CN115482007A
CN115482007A CN202211201554.9A CN202211201554A CN115482007A CN 115482007 A CN115482007 A CN 115482007A CN 202211201554 A CN202211201554 A CN 202211201554A CN 115482007 A CN115482007 A CN 115482007A
Authority
CN
China
Prior art keywords
transaction
target
request
transaction request
type
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
CN202211201554.9A
Other languages
Chinese (zh)
Inventor
王一平
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Bank of China Ltd
Original Assignee
Bank of China Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Bank of China Ltd filed Critical Bank of China Ltd
Priority to CN202211201554.9A priority Critical patent/CN115482007A/en
Publication of CN115482007A publication Critical patent/CN115482007A/en
Pending legal-status Critical Current

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/38—Payment protocols; Details thereof
    • G06Q20/40—Authorisation, e.g. identification of payer or payee, verification of customer or shop credentials; Review and approval of payers, e.g. check credit lines or negative lists
    • G06Q20/405—Establishing or using transaction specific rules
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/38—Payment protocols; Details thereof
    • G06Q20/382—Payment protocols; Details thereof insuring higher security of transaction
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/38—Payment protocols; Details thereof
    • G06Q20/40—Authorisation, e.g. identification of payer or payee, verification of customer or shop credentials; Review and approval of payers, e.g. check credit lines or negative lists
    • G06Q20/401—Transaction verification
    • G06Q20/4016—Transaction verification involving fraud or risk level assessment in transaction processing

Landscapes

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

Abstract

The application discloses a transaction request processing method, a transaction request processing device, equipment and a storage medium, which can be applied to the field of Internet of things or the field of finance, and can be used for acquiring a transaction request carrying a transaction event of a user; determining a target transaction type to which the transaction event belongs from a plurality of preset transaction types according to the risk and the processing flow of the transaction event; determining the transaction request times corresponding to the transaction request according to the accumulated transaction times corresponding to the transaction type; and if the transaction request times exceed the target transaction upper limit times corresponding to the target transaction types, limiting the transaction requests. According to the method and the device, different target transaction request times can be determined according to different target transaction types, so that when the target transaction request times are too large or are attacked maliciously, the interference and influence of the maliciously attacking on normal users can be reduced, and the stability of the system is improved.

Description

Method, device, equipment and storage medium for processing transaction request
Technical Field
The present application relates to the field of information system technologies, and in particular, to a method, an apparatus, a device, and a storage medium for processing a transaction request.
Background
With the development of electronic informatization, the transaction request amount of financial services is increasing day by day, and people put higher requirements on the safety and stability of the system.
In the prior art, in order to control the transaction request amount, a transaction upper limit number is usually set, and when the transaction request number exceeds the set transaction upper limit number within a certain time, the transaction request sent by the user is limited, so that the user cannot continuously send the transaction request.
However, since all transaction requests share the uniform transaction upper limit times, when the transaction request times are too large or are attacked maliciously, the transaction request times can reach the transaction upper limit times quickly, so that normal users cannot access the system, and the system has the defect of poor stability.
Disclosure of Invention
Based on the above problems, the present application provides a method, an apparatus, a device and a storage medium for processing a transaction request.
The embodiment of the application discloses the following technical scheme:
the embodiment of the application provides a method for processing a transaction request, wherein different preset transaction types correspond to different transaction upper limit times, and the method comprises the following steps:
acquiring a transaction request of a user, wherein the transaction request carries a transaction event;
determining a target transaction type to which the transaction event belongs from a plurality of preset transaction types according to the risk and the processing flow of the transaction event;
determining the transaction request times corresponding to the transaction request according to the accumulated transaction times corresponding to the transaction type;
and if the transaction request times exceed the target transaction upper limit times corresponding to the target transaction types, limiting the transaction request.
Further, under the condition of the same preset transaction type, different preset transaction sources correspond to different transaction upper limit times, and the method further comprises the following steps:
determining a target transaction source corresponding to the transaction request from a plurality of preset transaction sources according to the transaction identifier of the transaction request;
if the transaction request frequency exceeds the target transaction upper limit frequency corresponding to the target transaction type, limiting the transaction request, including:
and if the transaction request times exceed the target transaction types and the target transaction upper limit times corresponding to the target transaction sources, limiting the transaction requests.
Further, the transaction identifier includes one or more of a user identification of the user, a mobile phone number of the user, a user access address and a user access terminal.
Further, under the condition of the same preset transaction type, different preset transaction period types correspond to different transaction upper limit times, and the method further comprises the following steps:
determining a target transaction time interval type corresponding to the transaction request from a plurality of preset transaction time interval types according to the transaction time interval of the transaction request;
if the transaction request times exceed the target transaction upper limit times corresponding to the target transaction types, limiting the transaction request, including:
and if the transaction request times exceed the target transaction upper limit times corresponding to the target transaction type and the target transaction time period type, limiting the transaction request.
Further, the plurality of preset transaction period types include peak transaction periods and low transaction periods; the target transaction type and the target transaction upper limit times corresponding to the transaction peak time period are larger than the target transaction type and the target transaction upper limit times corresponding to the transaction peak time period.
Further, after limiting the transaction request if the number of times of the transaction request exceeds the upper limit number of times of the target transaction corresponding to the target transaction type, the method includes:
prompting error information to the user corresponding to the transaction request; and the error reporting information is used for prompting the user to exceed the transaction upper limit times.
The embodiment of the present application further provides a device for processing a transaction request, where different preset transaction types correspond to different transaction upper limit times, and the device includes:
the device comprises an acquisition module, a first determination module, a second determination module and a limitation module;
the acquisition module is used for acquiring a transaction request of a user, wherein the transaction request carries a transaction event;
the first determining module is used for determining a target transaction type to which the transaction event belongs from a plurality of preset transaction types according to the risk and the processing flow of the transaction event;
the second determining module is used for determining the transaction request times corresponding to the transaction request according to the accumulated transaction times corresponding to the transaction type;
and the limiting module is used for limiting the transaction request if the transaction request times exceed the target transaction upper limit times corresponding to the target transaction type.
Further, under the condition of the same preset transaction type, different preset transaction sources correspond to different transaction upper limit times, and the device further comprises:
a third determination module;
the third determining module is configured to determine, according to the transaction identifier of the transaction request, a target transaction source corresponding to the transaction request from a plurality of preset transaction sources;
the restriction module is configured to:
and if the transaction request times exceed the target transaction types and the target transaction upper limit times corresponding to the target transaction sources, limiting the transaction requests.
Further, the transaction identifier includes one or more of a user identification of the user, a mobile phone number of the user, a user access address and a user access terminal.
Further, under the condition of the same preset transaction type, different preset transaction period types correspond to different transaction upper limit times, and the device further comprises:
a fourth determination module;
the fourth determining module is configured to determine, according to the transaction time period of the transaction request, a target transaction time period type corresponding to the transaction request from a plurality of preset transaction time period types;
the restriction module is configured to:
and if the transaction request times exceed the target transaction upper limit times corresponding to the target transaction type and the target transaction time period type, limiting the transaction request.
Further, the plurality of preset transaction period types include peak transaction periods and low transaction periods; and the target transaction type and the target transaction upper limit times corresponding to the transaction peak time period are greater than the target transaction type and the target transaction upper limit times corresponding to the transaction peak time period.
Further, the apparatus further comprises:
a prompt module;
the prompting module is used for prompting error reporting information to the user corresponding to the transaction request; and the error reporting information is used for prompting the user to exceed the transaction upper limit times.
An embodiment of the present application further provides a computer device, where the computer device includes a processor and a memory:
the memory is used for storing program codes and transmitting the program codes to the processor;
the processor is adapted to perform the steps of a method of transaction request processing as described above in accordance with instructions in the program code.
Embodiments of the present application also provide a computer-readable storage medium, on which a computer program is stored, and the computer program, when executed by a processor, implements the steps of a method for transaction request processing as described above.
Compared with the prior art, the method has the following beneficial effects:
the method comprises the steps of obtaining a transaction request of a user, determining a target transaction type to which the transaction event belongs from a plurality of preset transaction types according to the risk and the processing flow of the transaction event carried by the transaction request, determining the transaction request times corresponding to the transaction request according to the accumulated transaction times corresponding to the transaction types, and limiting the transaction request if the transaction request times exceed the target transaction upper limit times corresponding to the target transaction types. According to the method and the device, different transaction requests can be distinguished, the target transaction type to which the transaction event carried by the transaction request belongs is determined, and different target transaction request times are determined according to different target transaction types, so that when the target transaction request times are too large or the target transaction request is attacked maliciously, the transaction request which belongs to the same target transaction type as the transaction event carried by the transaction request is only limited, interference and influence of the maliciously attacking on normal users are reduced, and the stability of the system is improved.
Drawings
In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings needed to be used in the description of the embodiments or the prior art will be briefly introduced below, and it is obvious that the drawings in the following description are only some embodiments of the present application, and it is obvious for those skilled in the art that other drawings can be obtained according to the drawings without inventive exercise.
Fig. 1 is a schematic diagram of a system framework related to an application scenario in an embodiment of the present application;
FIG. 2 is a flow chart of a method for processing a transaction request according to an embodiment of the present application;
fig. 3 is a schematic structural diagram of a device for processing a transaction request according to an embodiment of the present application.
Detailed Description
As described above, how to improve the system stability is a technical problem to be solved by those skilled in the art.
The inventor finds that, in the prior art, by setting the transaction upper limit times, after the transaction request times exceed the set transaction upper limit times within a certain time, the transaction request sent by the user is limited, so that the user cannot continuously send the transaction request, and the control of the transaction request amount is realized. However, since all transaction requests share the same transaction upper limit number, when the transaction request number is too large or is attacked maliciously, the transaction request number can quickly reach the transaction upper limit number, so that normal users cannot access the system, and the system stability is poor.
According to the method and the device, different transaction requests can be distinguished, the target transaction type to which the transaction event carried by the transaction request belongs is determined, and different transaction request times are determined according to different target transaction types, so that when the transaction request times are too large or are attacked maliciously, the transaction requests which belong to the same target transaction type as the transaction event carried by the transaction request can be limited, interference and influence of the maliciously attacking on normal users are reduced, and the stability of the system is improved.
For example, one of the scenarios in the embodiment of the present application may be applied to the scenario shown in fig. 1. The scenario includes a transaction request storage device 101 and a transaction request processing device 102, which interact between the transaction request storage device 101 and the transaction request processing device 102.
The transaction request storage device 101 stores a transaction request of a user, wherein the transaction request carries a transaction event; the transaction request processing equipment 102 acquires a transaction request of a user, wherein the transaction request carries a transaction event; determining a target transaction type to which the transaction event belongs from a plurality of preset transaction types according to the risk and the processing flow of the transaction event; determining the transaction request times corresponding to the transaction request according to the accumulated transaction times corresponding to the transaction type; and if the transaction request times exceed the target transaction upper limit times corresponding to the target transaction types, limiting the transaction request.
First, in the application scenario described above, although the actions of the embodiment provided by the embodiment of the present application are described as being performed by the transaction request processing device 102; however, the embodiments of the present application are not limited in terms of the execution subject as long as the actions disclosed in the embodiments provided in the embodiments of the present application are executed.
Next, the above scenario is only one example of the scenario provided in the embodiment of the present application, and the embodiment of the present application is not limited to this scenario.
In order to make the technical solutions of the present application better understood, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are only a part of the embodiments of the present application, and not all of the embodiments. All other embodiments obtained by a person of ordinary skill in the art based on the embodiments in the present application without making any creative effort belong to the protection scope of the present application.
The embodiment of the present application provides a method for processing a transaction request, where different preset transaction types correspond to different transaction upper limit times, which may be specifically implemented through steps 201 to 204, and refer to fig. 2, which is a flowchart of a method for processing a transaction request provided in the embodiment of the present application.
Step 201: the method comprises the steps of obtaining a transaction request of a user, wherein the transaction request carries a transaction event.
Specifically, the transaction request of the user may include a query request, a download request, a request for accessing a database, and the like. And acquiring a transaction request carrying the transaction event, so as to be convenient for subsequently determining the target transaction type to which the transaction event belongs.
Step 202: and determining a target transaction type to which the transaction event belongs from a plurality of preset transaction types according to the risk and the processing flow of the transaction event.
In particular, different transaction events may correspond to different risks and processing flows, such as: compared with the transaction event carried by the request for accessing the database, the transaction event carried by the query request has lower risk and simpler processing flow. According to the risk and the processing flow of the transaction event, the target transaction type of the transaction event can be determined, and the transaction request frequency corresponding to the transaction request can be conveniently determined subsequently.
Step 203: and determining the transaction request times corresponding to the transaction request according to the accumulated transaction times corresponding to the transaction type.
Specifically, for example, if the accumulated transaction number corresponding to the transaction type has reached 10 times, after the transaction request of this time is obtained, the transaction request number corresponding to the transaction request may be determined to be 11 times. And after the transaction request times corresponding to the transaction requests are determined, the subsequent transaction requests are limited conveniently.
Step 204: and if the transaction request times exceed the target transaction upper limit times corresponding to the target transaction types, limiting the transaction requests.
Specifically, when the transaction request frequency exceeds the target transaction upper limit frequency corresponding to the target transaction type, the transaction request is limited, so that the user cannot continuously send the transaction request, and the transaction requests corresponding to the transaction events belonging to other target transaction types are not influenced by the limitation.
Further, under the condition of the same preset transaction type, different preset transaction sources correspond to different transaction upper limit times, and the method further includes step 301.
Step 301: and determining a target transaction source corresponding to the transaction request from a plurality of preset transaction sources according to the transaction identifier of the transaction request.
Specifically, the transaction identifier may include one or more of a user identity identifier of the user, a mobile phone number of the user, a user access address and a user access terminal. The user access terminal comprises a mobile terminal, a computer terminal, an applet and the like. And determining a target transaction source corresponding to the transaction request according to the transaction identifier, and further judging whether the target transaction source is a normal user or an abnormal user.
The above step 204 can be implemented by step 302.
Step 302: and if the transaction request times exceed the target transaction upper limit times corresponding to the target transaction type and the target transaction source, limiting the transaction request.
Specifically, for the target transaction type, the target transaction upper limit times corresponding to different target transaction sources may be different, and when the transaction request times exceed the target transaction upper limit times corresponding to the target transaction type and the target transaction source, the transaction request is limited.
Further, under the condition of the same preset transaction type, different preset transaction period types correspond to different upper limit transaction times, and the method further includes step 401.
Step 401: and determining a target transaction time interval type corresponding to the transaction request from a plurality of preset transaction time interval types according to the transaction time interval of the transaction request.
Specifically, the transaction request periods may differ, and the corresponding target transaction period types may differ.
Step 204 described above may be implemented by step 402.
And if the transaction request times exceed the target transaction upper limit times corresponding to the target transaction type and the target transaction time period type, limiting the transaction request.
Specifically, for the target transaction types, the target transaction upper limit times corresponding to different target transaction period types may be different, and when the transaction request times exceed the target transaction types and the target transaction upper limit times corresponding to the target transaction period types, the transaction request is limited.
Further, the plurality of preset transaction period types include a peak transaction period and a low transaction period; the target transaction type and the target transaction upper limit times corresponding to the transaction peak time period are larger than the target transaction type and the target transaction upper limit times corresponding to the transaction peak time period. For example, the night transaction request amount is small, the night can be set as a transaction peak time period, the corresponding target transaction upper limit times are small, the transaction request amount at working time of working day is large, the time period can be set as a transaction peak time period, and the corresponding target transaction upper limit times are high.
Further, after the step 204, a step 205 is further included.
Step 205: prompting error information to the user corresponding to the transaction request; and the error reporting information is used for prompting the user to exceed the transaction upper limit times.
Specifically, after the transaction request is limited, an error message may be prompted to the user corresponding to the transaction request, and the user is prompted to exceed the transaction upper limit number of times.
In summary, the method and the device can distinguish different transaction requests, determine the target transaction types to which the transaction events carried by the transaction requests belong, and determine different transaction request times aiming at different target transaction types, so that when the transaction request times are too large or are attacked maliciously, the transaction requests belonging to the same type of target transaction types as the transaction events carried by the transaction requests are only limited, thereby reducing the interference and influence of the maliciously attacking on normal users, and improving the stability of the system. Meanwhile, the target transaction upper limit times can be flexibly set according to different transaction time period types, and different target transaction sources can be distinguished and correspond to different target transaction upper limit times. Even if the malicious website attacks, the target transaction source is limited to be incapable of continuously accessing, and other users who normally access the target transaction source are not influenced and can be normally used.
Referring to fig. 3, which is a schematic structural diagram of a device for processing a transaction request according to an embodiment of the present application, a specific implementation manner of the device is consistent with the implementation manner and the achieved technical effect described in the embodiment of the foregoing method, and details of a part of the implementation manner are not repeated.
A device for processing transaction requests, wherein different preset transaction types correspond to different transaction upper limit times, comprises:
an acquisition module 1101, a first determination module 1102, a second determination module 1103 and a restriction module 1104;
the obtaining module 1101 is configured to obtain a transaction request of a user, where the transaction request carries a transaction event;
the first determining module 1102 is configured to determine, according to the risk and the processing flow of the transaction event, a target transaction type to which the transaction event belongs from a plurality of preset transaction types;
the second determining module 1103 is configured to determine, according to the accumulated transaction times corresponding to the transaction types, transaction request times corresponding to the transaction requests;
the limiting module 1104 is configured to limit the transaction request if the number of times of the transaction request exceeds the target upper limit number of times of the transaction corresponding to the target transaction type.
Further, under the condition of the same preset transaction type, different preset transaction sources correspond to different transaction upper limit times, and the device further comprises:
a third determination module;
the third determining module is configured to determine, according to the transaction identifier of the transaction request, a target transaction source corresponding to the transaction request from a plurality of preset transaction sources;
the restriction module is configured to:
and if the transaction request times exceed the target transaction upper limit times corresponding to the target transaction type and the target transaction source, limiting the transaction request.
Further, the transaction identifier includes one or more of a user identification of the user, a mobile phone number of the user, a user access address and a user access terminal.
Further, under the condition of the same preset transaction type, different preset transaction period types correspond to different transaction upper limit times, and the device further comprises:
a fourth determination module;
the fourth determining module is used for determining a target transaction period type corresponding to the transaction request from a plurality of preset transaction period types according to the transaction period of the transaction request;
the restriction module is configured to:
and if the transaction request times exceed the target transaction upper limit times corresponding to the target transaction type and the target transaction time period type, limiting the transaction request.
Further, the plurality of preset transaction period types include a peak transaction period and a low transaction period; and the target transaction type and the target transaction upper limit times corresponding to the transaction peak time period are greater than the target transaction type and the target transaction upper limit times corresponding to the transaction peak time period.
Further, the apparatus further comprises:
a prompt module;
the prompting module is used for prompting error reporting information to the user corresponding to the transaction request; and the error reporting information is used for prompting the user to exceed the transaction upper limit times.
In summary, the method and the device can distinguish different transaction requests, determine the target transaction type to which the transaction event carried by the transaction request belongs, and determine different transaction request times for different target transaction types, so that when the transaction request times are too large or are attacked maliciously, the transaction request belonging to the same target transaction type as the transaction event carried by the transaction request is limited, thereby reducing the interference and influence of the maliciously attack on normal users, and improving the stability of the system.
An embodiment of the present application further provides a computer device, where the computer device includes a processor and a memory:
the memory is used for storing program codes and transmitting the program codes to the processor;
the processor is adapted to perform the steps of a method of transaction request processing as described above according to instructions in the program code.
Embodiments of the present application further provide a computer-readable storage medium, on which a computer program is stored, where the computer program, when executed by a processor, implements the steps of a method for processing transaction requests as described above.
It should be noted that the method, the device, the equipment and the storage medium for processing the transaction request provided by the invention can be applied to the fields of artificial intelligence, block chaining, distribution, cloud computing, big data, internet of things, mobile internet, network security, chip, virtual reality, augmented reality, holography, quantum computing, quantum communication, quantum measurement, digital twin or finance. The above description is only an example, and does not limit the application fields of the method, apparatus, device and storage medium for processing transaction requests provided by the present invention.
It should be noted that, in this specification, each embodiment is described in a progressive manner, and the same and similar parts between the embodiments are referred to each other, and each embodiment focuses on differences from other embodiments. In particular, for the apparatus, device and storage medium embodiments, since they are substantially similar to the method embodiments, they are described in a relatively simple manner, and reference may be made to some descriptions of the method embodiments for relevant points. The above-described embodiments of the apparatus, device and storage medium are merely illustrative, and units described as separate components may or may not be physically separate, and components indicated as units may or may not be physical units, may be located in one place, or may be distributed on multiple network units. Some or all of the modules may be selected according to actual needs to achieve the purpose of the solution of the present embodiment. One of ordinary skill in the art can understand and implement without inventive effort.
The above description is only one specific embodiment of the present application, but the scope of the present application is not limited thereto, and any changes or substitutions that can be easily conceived by those skilled in the art within the technical scope of the present application should be covered by the scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.

Claims (10)

1. A method for processing transaction requests is characterized in that different preset transaction types correspond to different transaction upper limit times, and the method comprises the following steps:
acquiring a transaction request of a user, wherein the transaction request carries a transaction event;
determining a target transaction type to which the transaction event belongs from a plurality of preset transaction types according to the risk and the processing flow of the transaction event;
determining the transaction request times corresponding to the transaction request according to the accumulated transaction times corresponding to the transaction type;
and if the transaction request times exceed the target transaction upper limit times corresponding to the target transaction types, limiting the transaction request.
2. The method of claim 1, wherein different predefined transaction sources correspond to different upper transaction limits for the same predefined transaction type, the method further comprising:
determining a target transaction source corresponding to the transaction request from a plurality of preset transaction sources according to the transaction identifier of the transaction request;
if the transaction request times exceed the target transaction upper limit times corresponding to the target transaction types, limiting the transaction request, including:
and if the transaction request times exceed the target transaction upper limit times corresponding to the target transaction type and the target transaction source, limiting the transaction request.
3. The method of claim 2, wherein the transaction identification comprises one or more of a user identification of the user, a user cell phone number, a user access address, and a user access terminal.
4. The method of claim 1, wherein different preset transaction period types correspond to different upper transaction limits for the same preset transaction type, the method further comprising:
determining a target transaction period type corresponding to the transaction request from a plurality of preset transaction period types according to the transaction period of the transaction request;
if the transaction request frequency exceeds the target transaction upper limit frequency corresponding to the target transaction type, limiting the transaction request, including:
and if the transaction request times exceed the target transaction upper limit times corresponding to the target transaction type and the target transaction time period type, limiting the transaction request.
5. The method of claim 4, wherein the plurality of preset transaction period types include peak transaction periods and low transaction periods; the target transaction type and the target transaction upper limit times corresponding to the transaction peak time period are larger than the target transaction type and the target transaction upper limit times corresponding to the transaction peak time period.
6. The method according to any one of claims 1 to 5, wherein after the limiting the transaction request if the number of transaction requests exceeds the target upper transaction limit number corresponding to the target transaction type, the method comprises:
prompting error information to the user corresponding to the transaction request; and the error reporting information is used for prompting the user to exceed the transaction upper limit times.
7. A device for processing transaction requests, wherein different preset transaction types correspond to different transaction upper limit times, comprising:
the device comprises an acquisition module, a first determination module, a second determination module and a limiting module;
the acquisition module is used for acquiring a transaction request of a user, wherein the transaction request carries a transaction event;
the first determining module is used for determining a target transaction type to which the transaction event belongs from a plurality of preset transaction types according to the risk and the processing flow of the transaction event;
the second determining module is used for determining the transaction request times corresponding to the transaction request according to the accumulated transaction times corresponding to the transaction type;
and the limiting module is used for limiting the transaction request if the transaction request times exceed the target transaction upper limit times corresponding to the target transaction type.
8. The apparatus of claim 7, wherein different predetermined transaction sources correspond to different transaction upper limits for the same predetermined transaction type, the apparatus further comprising:
a third determining module;
the third determining module is configured to determine, according to the transaction identifier of the transaction request, a target transaction source corresponding to the transaction request from a plurality of preset transaction sources;
the restriction module is configured to:
and if the transaction request times exceed the target transaction upper limit times corresponding to the target transaction type and the target transaction source, limiting the transaction request.
9. A computer device, the computer device comprising a processor and a memory:
the memory is used for storing program codes and transmitting the program codes to the processor;
the processor is adapted to perform the steps of a method of transaction request processing according to any of claims 1-6 in accordance with instructions in the program code.
10. A computer-readable storage medium, having stored thereon a computer program which, when executed by a processor, carries out the steps of a method of transaction request processing according to any of claims 1-6.
CN202211201554.9A 2022-09-29 2022-09-29 Method, device, equipment and storage medium for processing transaction request Pending CN115482007A (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202211201554.9A CN115482007A (en) 2022-09-29 2022-09-29 Method, device, equipment and storage medium for processing transaction request

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202211201554.9A CN115482007A (en) 2022-09-29 2022-09-29 Method, device, equipment and storage medium for processing transaction request

Publications (1)

Publication Number Publication Date
CN115482007A true CN115482007A (en) 2022-12-16

Family

ID=84394427

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202211201554.9A Pending CN115482007A (en) 2022-09-29 2022-09-29 Method, device, equipment and storage medium for processing transaction request

Country Status (1)

Country Link
CN (1) CN115482007A (en)

Similar Documents

Publication Publication Date Title
CN108734028B (en) Data management method based on block chain, block chain link point and storage medium
CN107169499B (en) Risk identification method and device
CN111310196B (en) Risk identification method and device and electronic equipment
CN106878250B (en) Cross-application single-state login method and device
US10104112B2 (en) Rating threat submitter
WO2016118621A1 (en) Methods, apparatus, and systems for resource access permission management
CN109669718A (en) System permission configuration method, device, equipment and storage medium
CN113378193A (en) Privacy information access control method and device based on ontology reasoning
CN113672894B (en) Data processing method, device, equipment and storage medium for verification code request
CN113179266A (en) Service request processing method and device, electronic equipment and storage medium
GB2581105A (en) Page accessing method and system for terminal
CN112491930A (en) System risk dynamic monitoring method, system, computer equipment and storage medium
CN112651039A (en) Electric power data differentiation desensitization method and device fusing service scenes
CN106559386A (en) A kind of authentication method and device
CN111461730B (en) Wind control method, device and system and electronic equipment
CN110278241B (en) Registration request processing method and device
CN115482007A (en) Method, device, equipment and storage medium for processing transaction request
CN115879156A (en) Dynamic desensitization method, device, electronic equipment and storage medium
CN112583606B (en) Security verification method, server, terminal and storage medium
WO2022243956A1 (en) Method, mobile equipment, and system for vulnerability detection in a sim
CN113590352A (en) Data calling method, device, equipment and readable storage medium
CN114567678A (en) Resource calling method and device of cloud security service and electronic equipment
CN114006758B (en) Method, device and storage medium for managing equipment identification
CN116094847B (en) Honeypot identification method, honeypot identification device, computer equipment and storage medium
CN112822022B (en) Multi-signature address updating method and related device

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination