CN117237108A - Transaction abnormity detection method and related device - Google Patents
Transaction abnormity detection method and related device Download PDFInfo
- Publication number
- CN117237108A CN117237108A CN202311197843.0A CN202311197843A CN117237108A CN 117237108 A CN117237108 A CN 117237108A CN 202311197843 A CN202311197843 A CN 202311197843A CN 117237108 A CN117237108 A CN 117237108A
- Authority
- CN
- China
- Prior art keywords
- transaction
- target transaction
- target
- legal
- business logic
- 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
Links
- 238000001514 detection method Methods 0.000 title claims abstract description 56
- 230000002159 abnormal effect Effects 0.000 claims abstract description 39
- 238000000034 method Methods 0.000 claims description 22
- 230000005856 abnormality Effects 0.000 claims description 19
- 238000004590 computer program Methods 0.000 claims description 4
- 238000012545 processing Methods 0.000 abstract description 10
- 230000000903 blocking effect Effects 0.000 description 4
- 238000010586 diagram Methods 0.000 description 4
- 230000002547 anomalous effect Effects 0.000 description 2
- 238000013459 approach Methods 0.000 description 2
- 230000009286 beneficial effect Effects 0.000 description 2
- 238000004891 communication Methods 0.000 description 1
- 238000012790 confirmation Methods 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 230000000750 progressive effect Effects 0.000 description 1
- 238000011160 research Methods 0.000 description 1
- 230000004044 response Effects 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
Landscapes
- Debugging And Monitoring (AREA)
Abstract
The application discloses a transaction anomaly detection method and a related device, which can be applied to the financial field or other fields and comprise the following steps: acquiring a target transaction to be executed, judging whether the target transaction is legal, executing first business logic corresponding to the target transaction if the target transaction is legal, sending a query request for querying key data required by the target transaction based on the first business logic, and executing second business logic corresponding to the target transaction if the key data is received; if the key data is not received after the preset times of inquiry requests are sent, a transaction exception message is sent, and the target transaction is ended. And judging whether the target transaction is legal or not through first transaction anomaly detection, sending a query request of key data under the condition that the target transaction is legal, and if the key data is received within preset query times, judging that the target transaction is abnormal, stopping the target transaction, and sending a new target transaction, thereby improving the processing efficiency of the transaction.
Description
Technical Field
The present application relates to the field of transaction detection technologies, and in particular, to a method and an apparatus for detecting transaction anomalies.
Background
At present, banks are involved in various transactions, and some transactions may involve the inquiry of asynchronous information, for example, a deposit transaction needs to inquire information such as deposit amount related to the deposit transaction, if the asynchronous information is not replied for a long time, the transaction needs to be reinitiated until the inquired asynchronous information is received, and the transaction is continuously executed. However, this approach may result in long waiting times for other transactions, resulting in blocking of the transaction, and reducing transaction processing efficiency.
Disclosure of Invention
Based on the above problems, the application provides a transaction anomaly detection method and a related device, which improve transaction processing efficiency.
The embodiment of the application discloses the following technical scheme:
in a first aspect, an embodiment of the present application provides a transaction anomaly detection method, including:
acquiring a target transaction to be executed;
judging whether the target transaction is legal or not;
if the target transaction is legal, executing a first business logic corresponding to the target transaction;
sending a query request based on the first business logic; the query request is a request for inquiring key data required by the target transaction;
if the key data is received, executing a second business logic corresponding to the target transaction;
if the key data is not received after the query request with preset times is sent, sending a transaction exception message; the transaction anomaly message indicates the target transaction anomaly.
Optionally, the determining whether the target transaction is legal includes:
judging whether an interface corresponding to the target transaction is legal or not;
and if the target transaction is legal, executing first business logic corresponding to the target transaction, wherein the first business logic comprises:
and if the interface corresponding to the target transaction is legal, executing first business logic corresponding to the target transaction.
Optionally, before determining whether the target transaction is legal, the method further comprises:
judging whether the target transaction and the historical abnormal transaction are associated or not; the historical abnormal transaction is a transaction corresponding to the historical transaction abnormal message before the target transaction is acquired;
ending the target transaction if the correlation exists between the target transaction and the historical abnormal transaction.
Optionally, the method further comprises:
and ending the target transaction if the target transaction is illegal.
Optionally, the method further comprises:
and if the key data is not received within the preset time, sending the transaction abnormal message.
In a second aspect, an embodiment of the present application provides a transaction anomaly detection device, including:
the acquisition module is used for acquiring the target transaction to be executed;
the first abnormality detection module is used for judging whether the target transaction is legal or not;
the first execution module is used for executing a first business logic corresponding to the target transaction if the target transaction is legal;
the query module is used for sending a query request based on the first business logic; the query request is a request for inquiring key data required by the target transaction;
the second execution module is used for executing second business logic corresponding to the target transaction if the key data is received;
the second abnormality detection module is used for sending a transaction abnormality message if the key data is not received after the query request with preset times is sent; the transaction anomaly message indicates the target transaction anomaly.
Optionally, the first abnormality detection module is specifically configured to:
judging whether an interface corresponding to the target transaction is legal or not;
the first execution module is specifically configured to:
and if the interface corresponding to the target transaction is legal, executing first business logic corresponding to the target transaction.
Optionally, before the first abnormality detection module, the apparatus further includes:
the third abnormality detection module is used for judging whether the association exists between the target transaction and the historical abnormal transaction; the historical abnormal transaction is a transaction corresponding to the historical transaction abnormal message before the target transaction is acquired;
and the execution ending module is used for ending the target transaction if the correlation exists between the target transaction and the historical abnormal transaction.
In a third aspect, an embodiment of the present application provides a computer apparatus, including: a memory, a processor, and a computer program stored on the memory and executable on the processor, the processor implementing the transaction anomaly detection method according to any one of the first aspects when the computer program is executed.
In a fourth aspect, an embodiment of the present application provides a computer-readable storage medium having stored therein instructions that, when executed on a terminal device, cause the terminal device to perform the transaction anomaly detection method according to any one of the first aspects.
Compared with the prior art, the application has the following beneficial effects:
according to the transaction anomaly detection method provided by the embodiment of the application, whether the target transaction is legal or not is judged by acquiring the target transaction to be executed, if the target transaction is legal, a first business logic corresponding to the target transaction is executed, a query request for querying key data required by the target transaction is sent based on the first business logic, and if the key data is received, a second business logic corresponding to the target transaction is executed; if the key data is not received after the preset times of inquiry requests are sent, a transaction exception message is sent, and the target transaction is ended. And judging whether the target transaction is legal or not through first transaction anomaly detection, sending a query request, namely sending a query request of key data based on first business logic under the condition that the target transaction is legal, and if the key data is received within preset query times, judging that the target transaction is anomalous, stopping the target transaction, and sending a new target transaction, thereby improving the processing efficiency of the transaction.
Drawings
In order to more clearly illustrate the embodiments of the application or the technical solutions of the prior art, the drawings which are used in the description of the embodiments or the prior art will be briefly described, it being obvious that the drawings in the description below are only some embodiments of the application, and that other drawings can be obtained according to these drawings without inventive faculty for a person skilled in the art.
FIG. 1 is a flowchart of a transaction anomaly detection method according to an embodiment of the present application;
FIG. 2 is a schematic diagram of a transaction anomaly detection method according to an embodiment of the present application;
fig. 3 is a schematic structural diagram of a transaction abnormality detection device according to an embodiment of the present application.
Detailed Description
As described above, in research on banking transactions, it is found that, at present, banks may involve various transactions, and some transactions may involve inquiry of asynchronous information, for example, a deposit transaction needs to inquire information such as a deposit amount related to the deposit transaction, and if the asynchronous information is not replied for a long time, the transaction needs to be reinitiated until the inquired asynchronous information is received, and the transaction is continuously executed. However, this approach may result in long waiting times for other transactions, resulting in blocking of the transaction, and reducing transaction processing efficiency.
In order to solve the above problems, an embodiment of the present application provides a transaction anomaly detection method. The method comprises the following steps: acquiring a target transaction to be executed, judging whether the target transaction is legal, executing first business logic corresponding to the target transaction if the target transaction is legal, sending a query request for querying key data required by the target transaction based on the first business logic, and executing second business logic corresponding to the target transaction if the key data is received; if the key data is not received after the preset times of inquiry requests are sent, a transaction exception message is sent, and the target transaction is ended.
In this way, through first transaction anomaly detection, whether the target transaction is legal or not is judged, under the condition that the target transaction is legal, a query request is sent based on the first business logic, namely, a query request of key data is sent, if the key data is received in the preset query times, the target transaction is considered to be abnormal, the target transaction is stopped, a new target transaction is sent, and the transaction processing efficiency is improved.
In order to make the present application better understood by those skilled in the art, the following description will clearly and completely describe the technical solutions in the embodiments of the present application with reference to the accompanying drawings, and it is apparent that the described embodiments are only some embodiments of the present application, not all embodiments. All other embodiments, which can be made by those skilled in the art based on the embodiments of the application without making any inventive effort, are intended to be within the scope of the application.
Referring to fig. 1, the flowchart of a transaction anomaly detection method provided by the embodiment of the present application, with reference to fig. 1, the transaction anomaly detection method provided by the embodiment of the present application may include:
s101: a target transaction to be executed is obtained.
The target transaction means a transaction to be performed, such as a deposit transaction, a balance inquiry transaction, etc., and is not particularly limited herein.
S102: and judging whether the target transaction is legal or not.
Before executing the target transaction, whether the target transaction is legal or not needs to be judged, if not, the transaction can be directly ended, and a new transaction is acquired.
In one possible implementation manner, step S102 may specifically include: and judging whether the interface corresponding to the target transaction is legal or not.
It should be understood that it may be specifically determined whether the interface corresponding to the target transaction is legal, for example, the interface is an interface of a third party application, and if the third party application is not authorized, the target transaction is illegal.
Correspondingly, when the interface corresponding to the target transaction is legal, executing first business logic corresponding to the target transaction.
S103: and if the target transaction is legal, executing first business logic corresponding to the target transaction.
It should be understood that, in the execution process of the target transaction, external data may need to be called for confirmation, for example, a withdrawal transaction may need to be performed, and the password system needs to obtain the password in response to the user, so in the embodiment of the present application, the business logic corresponding to the target transaction is divided into a first business logic and a second business logic, where the first business logic represents the logic corresponding to the business before the external data is called, and the second business logic represents the business logic corresponding to the business after the external data is obtained.
S104: and sending a query request based on the first business logic.
The inquiry request means a request for inquiring key data (referring to the aforementioned external data) required for the target transaction, for example, the key data required for the deposit transaction may be a user password, a business code of a business person, and the like.
S105: and if the key data is received, executing second business logic corresponding to the target transaction.
After sending the query request, there are two cases where the external application or module responds to the query request and returns the critical data, or does not return the critical data.
And when the key data is received, the second business logic corresponding to the target transaction can be normally executed, and the transaction is completed.
S106: and if the key data is not received after the query request with preset times is sent, sending a transaction abnormal message.
Wherein the transaction anomaly message indicates the target transaction anomaly.
It should be understood that if the key data is not received after the first query request, the query request may be resent, and the key data is not received after the preset number of times, the target transaction is considered to be abnormal, and a transaction abnormal message needs to be sent to a service person, and meanwhile, execution of the target transaction needs to be stopped so as to facilitate execution of other subsequent transactions.
According to the transaction anomaly detection method provided by the embodiment of the application, whether the target transaction is legal or not is judged by acquiring the target transaction to be executed, if the target transaction is legal, a first business logic corresponding to the target transaction is executed, a query request for querying key data required by the target transaction is sent based on the first business logic, and if the key data is received, a second business logic corresponding to the target transaction is executed; if the key data is not received after the preset times of inquiry requests are sent, a transaction exception message is sent, and the target transaction is ended. And judging whether the target transaction is legal or not through first transaction anomaly detection, sending a query request, namely sending a query request of key data based on first business logic under the condition that the target transaction is legal, and if the key data is received within preset query times, judging that the target transaction is anomalous, stopping the target transaction, and sending a new target transaction, thereby improving the processing efficiency of the transaction.
Based on the transaction anomaly query method provided in the foregoing embodiment, in a possible implementation manner, before step S102, the method further includes:
a1: and judging whether the target transaction and the historical abnormal transaction are associated or not.
The historical abnormal transaction is a transaction corresponding to the historical transaction abnormal message before the target transaction is acquired. The historical abnormal transaction is a transaction corresponding to the illegal judgment result represented in the last step S102, or a transaction corresponding to the transaction abnormal message represented in the step S106.
A2: ending the target transaction if the correlation exists between the target transaction and the historical abnormal transaction.
It should be understood that if the target transaction is associated with the historical abnormal transaction, the target transaction is considered to be abnormal, and the target transaction can be directly ended, so that the detection efficiency of the abnormal transaction is improved.
In one possible implementation, the method may further include: and ending the target transaction if the target transaction is illegal.
It should be understood that if the target transaction is illegal, the target transaction is considered to be abnormal, the target transaction can be ended, a new transaction can be acquired, transaction blocking is avoided, and transaction processing efficiency is improved.
In one possible implementation, the method may further include: and if the key data is not received within the preset time, sending the transaction abnormal message.
It should be understood that, in order to save memory resources, only one query request may be sent, if no key data is received within a preset time, the target transaction is considered to be abnormal, the target transaction may be ended, a new transaction is received, transaction blocking caused by multiple query requests is avoided, and transaction processing efficiency is improved.
Referring to fig. 2, the schematic diagram of a transaction anomaly detection method provided by an embodiment of the present application, with reference to fig. 2, the transaction anomaly detection flow may include:
step 1: the target transaction is initiated.
Step 2: the gateway judges whether the target transaction is legal or not and whether the target transaction needs to be ended or not.
Step 3: and (3) ending the interface corresponding to the target transaction, and returning failure.
Step 4: the end is not required and service logic a (referred to as the first service logic described above) is executed.
Step 5: external data (i.e., the aforementioned key data) is queried.
Step 6: whether the external data is returned by the query.
Step 7: if not, repeating the query according to the service repetition query times, and circularly querying; if the transaction is not returned within the preset times, the transaction is directly ended.
Step 8: there is a return to continue execution of business logic b (referring to the second business logic described above).
Step 9: the target transaction is ended.
Based on the transaction anomaly detection method provided by the foregoing embodiment, the embodiment of the present application further provides a transaction anomaly detection device, referring to fig. 3, which is a schematic structural diagram of the transaction anomaly detection device provided by the embodiment of the present application, and in combination with fig. 3, the transaction anomaly detection device 300 provided by the embodiment of the present application may include:
an acquiring module 301, configured to acquire a target transaction to be executed;
a first anomaly detection module 302, configured to determine whether the target transaction is legal;
a first execution module 303, configured to execute a first business logic corresponding to the target transaction if the target transaction is legal;
a query module 304, configured to send a query request based on the first service logic; the query request is a request for inquiring key data required by the target transaction;
a second execution module 305, configured to execute a second business logic corresponding to the target transaction if the key data is received;
a second anomaly detection module 306, configured to send a transaction anomaly message if the key data is not received after sending the query request for a preset number of times; the transaction anomaly message indicates the target transaction anomaly.
As an example, the first anomaly detection module 302 is specifically configured to:
judging whether an interface corresponding to the target transaction is legal or not;
the first execution module is specifically configured to:
and if the interface corresponding to the target transaction is legal, executing first business logic corresponding to the target transaction.
As an example, before the first anomaly detection module 302, the apparatus 300 further includes:
the third abnormality detection module is used for judging whether the association exists between the target transaction and the historical abnormal transaction; the historical abnormal transaction is a transaction corresponding to the historical transaction abnormal message before the target transaction is acquired;
and the execution ending module is used for ending the target transaction if the correlation exists between the target transaction and the historical abnormal transaction.
As an example, the apparatus 300 further comprises:
and the fourth abnormality detection module is used for ending the target transaction if the target transaction is illegal.
As an example, the apparatus 300 further comprises:
and the fifth abnormality detection module is used for sending the transaction abnormality message if the key data is not received within the preset time.
The transaction abnormality detection device provided by the embodiment of the application has the same beneficial effects as the transaction abnormality detection method provided by the embodiment, so that the description is omitted.
The embodiment of the application also provides corresponding equipment and a computer storage medium, which are used for realizing the scheme provided by the embodiment of the application.
The device comprises a memory and a processor, wherein the memory is used for storing instructions or codes, and the processor is used for executing the instructions or codes so as to enable the device to execute the transaction abnormality detection method according to any embodiment of the application.
The computer storage medium stores codes, and when the codes are executed, the equipment for executing the codes realizes the transaction abnormality detection method according to any embodiment of the application.
The transaction anomaly detection method and the related device can be used in the financial field or other fields, for example, can be used in banking transaction scenes in the financial field. Other fields are any field other than the financial field, for example, the transaction detection field. The foregoing is merely exemplary, and the application fields of the transaction anomaly detection method and the related device provided by the present application are not limited.
It should be noted that, in the present specification, each embodiment is described in a progressive manner, and identical and similar parts of each embodiment are all referred to each other, and each embodiment is mainly described in a different point from other embodiments. In particular, for the apparatus and device embodiments, since they are substantially similar to the method embodiments, the description is relatively simple, and reference is made to the description of the method embodiments for relevant points. The apparatus and device embodiments described above are merely illustrative, wherein elements illustrated as separate elements may or may not be physically separate, and elements presented as elements may or may not be physical elements, may be located in one place, or may be distributed over a plurality of network elements. Some or all of the modules may be selected according to actual needs to achieve the purpose of the solution of this embodiment. Those of ordinary skill in the art will understand and implement the present application without undue burden.
It should be noted that, the user information (including but not limited to user equipment information, user personal information, etc.) and the data (including but not limited to data for analysis, stored data, presented data, etc.) related to the present application are information and data authorized by the user or sufficiently authorized by each party, and the collection, use and processing of the related data need to comply with the related laws and regulations and standards of the related country and region.
The "first" and "second" in the names of "first", "second" (where present) and the like in the embodiments of the present application are used for name identification only, and do not represent the first and second in sequence.
From the above description of embodiments, it will be apparent to those skilled in the art that all or part of the steps of the above described example methods may be implemented in software plus general hardware platforms. Based on such understanding, the technical solution of the present application may be embodied in the form of a software product, which may be stored in a storage medium, such as a read-only memory (ROM)/RAM, a magnetic disk, an optical disk, etc., and includes several instructions for causing a computer device (which may be a personal computer, a server, or a network communication device such as a router) to perform the method according to the embodiments or some parts of the embodiments of the present application.
The foregoing 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 easily contemplated by those skilled in the art within the technical scope of the present application should be included in the scope of the present application. Therefore, the protection scope of the present application should be subject to the protection scope of the claims.
Claims (10)
1. A transaction anomaly detection method, the method comprising:
acquiring a target transaction to be executed;
judging whether the target transaction is legal or not;
if the target transaction is legal, executing a first business logic corresponding to the target transaction;
sending a query request based on the first business logic; the query request is a request for inquiring key data required by the target transaction;
if the key data is received, executing a second business logic corresponding to the target transaction;
if the key data is not received after the query request with preset times is sent, sending a transaction exception message; the transaction anomaly message indicates the target transaction anomaly.
2. The method of claim 1, wherein said determining whether the target transaction is legitimate comprises:
judging whether an interface corresponding to the target transaction is legal or not;
and if the target transaction is legal, executing first business logic corresponding to the target transaction, wherein the first business logic comprises:
and if the interface corresponding to the target transaction is legal, executing first business logic corresponding to the target transaction.
3. The method of claim 1, wherein prior to determining whether the target transaction is legitimate, the method further comprises:
judging whether the target transaction and the historical abnormal transaction are associated or not; the historical abnormal transaction is a transaction corresponding to the historical transaction abnormal message before the target transaction is acquired;
ending the target transaction if the correlation exists between the target transaction and the historical abnormal transaction.
4. The method according to claim 1, wherein the method further comprises:
and ending the target transaction if the target transaction is illegal.
5. The method according to claim 1, wherein the method further comprises:
and if the key data is not received within the preset time, sending the transaction abnormal message.
6. A transaction anomaly detection device, the device comprising:
the acquisition module is used for acquiring the target transaction to be executed;
the first abnormality detection module is used for judging whether the target transaction is legal or not;
the first execution module is used for executing a first business logic corresponding to the target transaction if the target transaction is legal;
the query module is used for sending a query request based on the first business logic; the query request is a request for inquiring key data required by the target transaction;
the second execution module is used for executing second business logic corresponding to the target transaction if the key data is received;
the second abnormality detection module is used for sending a transaction abnormality message if the key data is not received after the query request with preset times is sent; the transaction anomaly message indicates the target transaction anomaly.
7. The apparatus of claim 6, wherein the first anomaly detection module is specifically configured to:
judging whether an interface corresponding to the target transaction is legal or not;
the first execution module is specifically configured to:
and if the interface corresponding to the target transaction is legal, executing first business logic corresponding to the target transaction.
8. The apparatus of claim 6, wherein prior to the first anomaly detection module, the apparatus further comprises:
the third abnormality detection module is used for judging whether the association exists between the target transaction and the historical abnormal transaction; the historical abnormal transaction is a transaction corresponding to the historical transaction abnormal message before the target transaction is acquired;
and the execution ending module is used for ending the target transaction if the correlation exists between the target transaction and the historical abnormal transaction.
9. A computer device, comprising: a memory, a processor, and a computer program stored on the memory and executable on the processor, the processor implementing the transaction anomaly detection method of any one of claims 1-5 when the computer program is executed.
10. A computer readable storage medium having instructions stored therein which, when executed on a terminal device, cause the terminal device to perform the transaction anomaly detection method of any one of claims 1 to 5.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202311197843.0A CN117237108A (en) | 2023-09-15 | 2023-09-15 | Transaction abnormity detection method and related device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202311197843.0A CN117237108A (en) | 2023-09-15 | 2023-09-15 | Transaction abnormity detection method and related device |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN117237108A true CN117237108A (en) | 2023-12-15 |
Family
ID=89092494
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202311197843.0A Pending CN117237108A (en) | 2023-09-15 | 2023-09-15 | Transaction abnormity detection method and related device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN117237108A (en) |
-
2023
- 2023-09-15 CN CN202311197843.0A patent/CN117237108A/en active Pending
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN111030812A (en) | Token verification method, device, storage medium and server | |
| CN105207996A (en) | Account merging method and apparatus | |
| CN110222116B (en) | Control method and device for transaction data storage and storage medium | |
| CN110222085B (en) | Processing method and device for certificate storage data and storage medium | |
| CN110555769A (en) | Block chain transaction data processing method and device, computer equipment and storage medium | |
| JP6629973B2 (en) | Method and apparatus for recognizing a service request to change a mobile phone number | |
| CN114422139B (en) | API gateway request security verification method, device, electronic equipment and computer readable medium | |
| CN111679968A (en) | Interface calling abnormity detection method and device, computer equipment and storage medium | |
| CN107040497B (en) | Network account anti-theft method and device | |
| CN108650123B (en) | Fault information recording method, device, equipment and storage medium | |
| CN106612263B (en) | Method and equipment for processing application access request | |
| CN110738502A (en) | bill processing method and device and storage medium device | |
| US20220400384A1 (en) | Sim swap fraud detection | |
| CN111080302A (en) | Transaction risk identification method and device | |
| CN110889689A (en) | Transaction request processing method and device, electronic equipment and readable storage medium | |
| CN117237108A (en) | Transaction abnormity detection method and related device | |
| CN115018612A (en) | Business processing method and device based on bank counter | |
| CN111709803B (en) | Method and system for preventing unauthorized business handling | |
| CN102243738A (en) | Safety payment system and method | |
| CN115065510A (en) | Login method, device, system, electronic equipment and readable storage medium | |
| CN112819628A (en) | Detection method, device and system for preventing transaction from being replayed, electronic equipment and storage medium | |
| CN111901299A (en) | Application authentication method and device, electronic equipment and storage medium | |
| CN115001803B (en) | Mobile phone bank login method and device | |
| CN116720818B (en) | Warehouse processing method, device and computer equipment based on block chain | |
| CN112069488B (en) | Application login method in communication program and related device thereof |
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 |