TWI894095B - Virtual currency transaction abnormality control system and virtual currency transaction abnormality control method - Google Patents

Abstract

A virtual currency transaction anomaly management system includes a storage unit and a processing unit. The processing unit is electrically connected to the storage unit. The processing unit receives a transaction request related to a transaction by a user. For each of multiple transaction anomaly conditions, the processing unit determines whether the transaction meets the anomaly condition. If the processing unit determines that the transaction meets the anomaly condition, the processing unit executes an anomaly handling procedure corresponding to the anomaly condition. This prevents fraud or money laundering.

Description

Virtual currency transaction abnormality control system and virtual currency transaction abnormality control method

The present invention relates to a control system, and more particularly to a system for controlling abnormal conditions in virtual currency transactions.

Virtual currency trading has become increasingly popular in recent years. Because it involves the conversion of real currencies, many fraudulent and other illegal groups exploit virtual currency transactions to conduct fraudulent activities or launder funds. For virtual currency exchanges, preventing these illegal activities is currently a critical issue.

Therefore, the purpose of the present invention is to provide a virtual currency transaction abnormality management system.

Another object of the present invention is to provide a method for controlling abnormal transactions in virtual currency.

Therefore, the virtual currency transaction abnormality control system of the present invention includes a storage unit and a processing unit. The processing unit is electrically connected to the storage unit.

The processing unit receives a transaction request related to a transaction of a user.

For each of a plurality of transaction exception conditions, the processing unit determines whether the transaction meets the transaction exception condition.

When the processing unit determines that the transaction meets the transaction exception condition, the processing unit executes a transaction exception handling procedure corresponding to the transaction exception condition.

In some implementations, the processing unit determines whether user data of the user meets one of a plurality of high-risk conditions.

When the processing unit determines that user data of the user meets one of the high-risk conditions, the processing unit adds a high-risk tag to the user data.

When the processing unit determines that user data of the user does not meet one of the high-risk conditions, the processing unit adds a low-risk tag to the user data.

The abnormal transaction conditions are divided into a plurality of high-risk user abnormal transaction conditions, a plurality of low-risk user abnormal transaction conditions and at least one all-user abnormal transaction condition. After the processing unit receives the transaction request related to the transaction of the user, the processing unit determines whether the user data of the user includes the high-risk tag or the low-risk tag. When the processing unit determines that the user When the user data of the user includes the high-risk tag, the processing unit determines whether the transaction meets the high-risk user transaction anomaly conditions and the all-user transaction anomaly conditions. When the processing unit determines that the user data of the user includes the low-risk tag, the processing unit determines whether the transaction meets the low-risk user transaction anomaly conditions and the all-user transaction anomaly conditions.

In some implementations, when the processing unit determines whether the transaction meets one of the transaction exception conditions, the processing unit determines whether a user age of the user is less than or equal to a one-year age threshold, a user occupation of the user is unemployed or a student, a transaction type of the transaction request is a deposit, and the transaction amount is greater than or equal to a first amount threshold.

In some implementations, when the processing unit determines whether the transaction meets one of the transaction abnormality conditions, the processing unit determines whether a user title of the user is a responsible person and whether the total number of transactions and the total amount of transactions conducted by the user in a recent first time period for exchanging virtual currency for real currency or between different virtual currencies are greater than or equal to a transaction number threshold and a second amount threshold, respectively.

In some implementations, when the processing unit determines whether the transaction meets one of the transaction abnormality conditions, the processing unit determines whether a transaction type of the transaction request is deposit and a source address of the transaction request meets one of a plurality of suspicious addresses.

In some implementations, when the processing unit determines whether the transaction meets one of the transaction abnormality conditions, the processing unit determines whether the total amount of deposits or cash deposits and the total amount of withdrawals or cash withdrawals by the user in a recent second time period are greater than or equal to a third amount threshold and a fourth amount threshold, respectively.

When the processing unit determines whether the transaction meets one of the transaction abnormality conditions, the processing unit determines whether the total amount of gold or currency deposited by the user in that month is greater than a predetermined multiple of the user's monthly income.

In some implementations, the processing unit receives a login request.

For each of a plurality of login exception conditions, the processing unit determines whether the login request meets the login exception condition.

When the processing unit determines that the login request meets the login exception condition, the processing unit executes a login exception handling procedure corresponding to the login exception condition.

In some implementations, when the processing unit determines whether the login request meets one of the login exception conditions, the processing unit determines whether a login IP address of the login request belongs to one of a plurality of high-risk regions.

In some implementations, when the processing unit determines whether the login request meets one of the login exception conditions, the processing unit determines whether the number of different accounts used by a login network coordination address of the login request to log into the virtual currency transaction exception control system within a recent third time period is greater than or equal to a first account quantity threshold.

In some implementations, when the processing unit determines whether the login request meets one of the login exception conditions, the processing unit determines whether the number of different accounts used by a login device identification code of the login request to log into the virtual currency transaction exception management system within a recent fourth time period is greater than or equal to a second account number threshold.

The present invention provides a method for managing virtual currency transaction anomalies, implemented using a virtual currency transaction anomaly management system. The system comprises a storage unit and a processing unit. The method includes: the processing unit receiving a transaction request related to a transaction by a user; for each of a plurality of transaction anomaly conditions, the processing unit determining whether the transaction meets the transaction anomaly condition; and, if the processing unit determines that the transaction meets the transaction anomaly condition, executing a transaction anomaly handling procedure corresponding to the transaction anomaly condition.

The effect of the present invention is that: for each of the transaction abnormality conditions, the processing unit determines whether the transaction meets the transaction abnormality condition, and when it is determined that the transaction meets the transaction abnormality condition, the transaction abnormality handling procedure corresponding to the transaction abnormality condition is executed, thereby preventing illegal activities such as fraud or money laundering by monitoring the abnormal status of transaction behavior. Furthermore, for each of a plurality of abnormal login conditions, the processing unit determines whether the login request satisfies the abnormal login condition, and executes the abnormal login handling procedure corresponding to the abnormal login condition when the login request is determined to satisfy the abnormal login condition, thereby preventing illegal activities such as fraud or money laundering by monitoring abnormal login behavior.

Before the present invention is described in detail, it should be noted that similar elements are denoted by the same reference numerals in the following description.

Before the present invention is described in detail, it should be noted that, unless otherwise specified, the term "electrically connected" as used in this patent specification is used to describe the "coupled" relationship between computer hardware (e.g., electronic systems, devices, apparatuses, units, components), and generally refers to "wired electrical connections" achieved by physically connecting multiple computer hardware components to each other through conductive/semiconductor materials, as well as "radio connections" achieved by wireless data transmission using wireless communication technologies (such as, but not limited to, wireless networks, Bluetooth, and electromagnetic induction). On the other hand, unless otherwise specified, the "electrical connection" described in this patent specification also generally refers to a "direct electrical connection" achieved by directly coupling multiple computer hardware components to each other, and an "indirect electrical connection" achieved by indirectly coupling multiple computer hardware components through other computer hardware components.

Before the present invention is described in detail, it should be noted that the "unit" described in this patent specification represents computer hardware rather than software. For example, "processing unit" is used to represent computer hardware with data processing capabilities.

Referring to FIG. 1 , a first embodiment of a virtual currency transaction anomaly control system 100 of the present invention includes a storage unit 1 and a processing unit 2. The processing unit 2 is electrically connected to the storage unit 1. The virtual currency transaction anomaly control system 100 is implemented, for example, by cooperating with one or more servers or hosts.

1 and 2 , the following describes the steps of executing a login abnormality control procedure in the virtual currency transaction abnormality control system 100. First, as shown in step S01 , the processing unit 2 receives a login request.

Next, in steps S02-S07, for each of the multiple login exception conditions, the processing unit 2 determines whether the login request meets the login exception condition (steps S02, S04, and S06). When the processing unit 2 determines that the login request meets the login exception condition, the processing unit 2 executes a login exception handling procedure corresponding to the login exception condition (steps S03, S05, and S07). When the processing unit 2 determines that the transaction does not meet the login exception conditions, the processing unit 2 allows the login request (step S08). When executing the login abnormality handling procedure, the processing unit 2 may perform one or more of the following actions: rejecting the login request, canceling some or all permissions of the user's account, adding a related abnormality tag to the user's account, or issuing an internal abnormality notification.

The following details how the processing unit 2 determines whether the transaction meets the login exception condition in steps S02, S04, and S06. In step S02, the processing unit 2 determines whether the login request's login URL belongs to one of multiple high-risk regions. This prevents users from high-risk regions from logging in.

In step S04, the processing unit 2 determines whether the number of different accounts used by the login network address of the login request to log into the virtual currency transaction abnormality control system 100 within a recent third time period (e.g., 24 hours) is greater than or equal to a first account quantity threshold (e.g., 10 accounts). This prevents the use of dummy accounts for money laundering.

In step S06, the processing unit 2 determines whether the number of different accounts used by the login device identification code in the login request to log into the virtual currency transaction abnormality control system 100 within a recent fourth time period (e.g., 24 hours) is greater than or equal to a second account quantity threshold (e.g., 10 accounts). This prevents the use of dummy accounts for money laundering.

It should be noted that the order in which steps S02, S04, and S06 are performed is not limited to this embodiment.

1 and 3 , the following describes the steps of executing a transaction abnormality control procedure in the virtual currency transaction abnormality control system 100. First, as shown in step S11 , the processing unit 2 receives a transaction request related to a transaction by a user.

Next, in steps S12-S21, for each of a plurality of transaction exception conditions, the processing unit 2 determines whether the transaction meets the transaction exception condition (steps S12, S14, S16, S18, and S20). When the processing unit 2 determines that the transaction meets the transaction exception condition, the processing unit 2 executes a transaction exception handling procedure corresponding to the transaction exception condition (steps S13, S15, S17, S19, and S21). When the processing unit 2 determines that the transaction does not meet the transaction exception conditions, the processing unit 2 executes a transaction procedure corresponding to the transaction request (step S22). When executing the transaction abnormality handling procedure, the processing unit 2 may perform one or more of the following actions, such as rejecting the transaction or sending it for manual review, canceling some or all permissions of the user's account, adding a relevant abnormality tag to the user's account, or issuing an internal abnormality notification.

The following details how processing unit 2 determines whether a transaction meets the abnormal transaction conditions in steps S12, S14, S16, S18, and S20. In step S12, processing unit 2 determines whether the user's age is less than or equal to a one-year age threshold (e.g., 20 years old), their occupation is unemployed or a student, the transaction type is a deposit (i.e., depositing real currency), and the transaction amount is greater than or equal to a first threshold amount (e.g., NT$1 million). This prevents younger users from being misled by fraud rings and losing money or becoming "dummy accounts" for money laundering.

In step S14, when the processing unit 2 determines whether the transaction meets the transaction abnormality condition, the processing unit 2 determines whether the user's user title is "responsible person" and whether the total number of transactions and the total amount of transactions conducted by the user in a recent first time period (e.g., 7 days) between virtual currency and real currency, or between different virtual currencies, are greater than or equal to a transaction number threshold (e.g., 50 transactions) and a second amount threshold (e.g., NT$10 million). This prevents shell companies from laundering funds through these transactions.

In step S16, the processing unit 2 determines whether a transaction type of the transaction request is an inflow (i.e., receiving virtual currency from another address) and whether a source address of the transaction request matches one of multiple suspicious addresses. This prevents money laundering.

In step S18, the processing unit 2 determines whether the total amount of deposits or cash deposits and withdrawals (i.e., withdrawals of real currency) or cash withdrawals (i.e., transfers of virtual currency to other addresses) by the user within a recent second time period (e.g., 24 hours) is greater than or equal to a third threshold (e.g., NT$5 million) and a fourth threshold (e.g., NT$5 million), respectively. This prevents money laundering. For example, if within 24 hours the user deposits NT$5 million and withdraws NT$5 million, or deposits NT$5 million and withdraws NT$5 million, or deposits NT$5 million and withdraws NT$5 million, or deposits NT$5 million and withdraws NT$5 million, or deposits NT$5 million and withdraws NT$5 million, the judgment will be yes in step S08.

In step S20, the processing unit 2 determines whether the total amount of cash or currency deposited by the user in that month is greater than a predetermined multiple (e.g., 8 times) of the user's monthly income. This prevents money laundering.

It should be noted that the order in which steps S12, S14, S16, S18, and S20 are performed is not limited to this embodiment.

In another embodiment, the transaction exception conditions vary for users with different risk levels, as detailed below. Periodically, the processing unit 2 determines whether the user's user data meets one of multiple high-risk conditions. For example, the processing unit 2 determines whether the user's user data has been unemployed for more than one year continuously, whether the number of days the user has been a member is less than 60 days, whether the user data contains more than one transaction warning record, whether the user's age in the user data is under 20 years old, whether the user's age in the user data is over 70 years old, whether the user's occupation in the user data is one of multiple specific industries, whether the purpose of opening an account in the user data is one of multiple specific purposes, and whether the user's name appears in at least one negative news message.

When the processing unit 2 determines that the user data of the user meets one of the high-risk conditions, the processing unit 2 adds a high-risk tag to the user data. When the processing unit 2 determines that the user data of the user does not meet one of the high-risk conditions, the processing unit 2 adds a low-risk tag to the user data.

Such abnormal transaction conditions are categorized as multiple abnormal transaction conditions involving high-risk users, multiple abnormal transaction conditions involving low-risk users, and at least one abnormal transaction condition involving all users.

After the processing unit 2 receives the transaction request related to the transaction of the user, the processing unit 2 determines whether the user data of the user includes the high-risk tag or the low-risk tag.

When the processing unit 2 determines that the user data of the user includes the high-risk tag, the processing unit 2 determines whether the transaction meets the high-risk user transaction abnormality conditions and the all-user transaction abnormality conditions.

When the processing unit 2 determines that the user data of the user includes the low-risk tag, the processing unit 2 determines whether the transaction meets the low-risk user transaction abnormality conditions and the all-user transaction abnormality conditions.

In this implementation, the abnormal transaction conditions for high-risk users are stricter than those for low-risk users, and the abnormal transaction conditions for low-risk users are looser than those for high-risk users. For example, when the processing unit 2 determines whether the transaction meets one of the abnormal transaction conditions for high-risk users, the processing unit 2 determines whether the total amount of deposits or coins deposited by the user in the last 24 hours is The total amount of deposits and withdrawals is greater than or equal to NT$5 million and NT$5 million respectively. When the processing unit 2 determines whether the transaction meets one of the low-risk user transaction abnormality conditions, the processing unit 2 determines whether the total amount of deposits and withdrawals of the user in the last 24 hours is greater than or equal to NT$10 million and NT$10 million respectively (the higher the amount, the more relaxed the conditions).

In summary, the virtual currency transaction abnormality control system 100 of the present invention prevents fraud or money laundering by monitoring abnormalities in transaction behavior. Furthermore, for each of the multiple abnormal login conditions, the processing unit 2 determines whether the login request meets the abnormal login condition, and executes the abnormal login handling procedure corresponding to the abnormal login condition when the login request is determined to meet the abnormal login condition. Thus, by monitoring abnormal login behavior, fraud or money laundering can be prevented, thereby effectively achieving the purpose of the present invention.

However, the above description is merely an example of the present invention and should not be used to limit the scope of the present invention. All simple equivalent changes and modifications made according to the scope of the patent application and the content of the patent specification of the present invention are still within the scope of the present patent.

100: Virtual Currency Transaction Abnormal Control System 1: Storage Unit 2: Processing Unit S01-S08: Steps S11-S22: Steps

Other features and functions of the present invention are clearly illustrated in the accompanying drawings, including: Figure 1 is a schematic diagram illustrating the hardware connections of an embodiment of the present invention; Figure 2 is a flow chart illustrating a login anomaly control procedure of the embodiment; and Figure 3 is another flow chart illustrating a transaction anomaly control procedure of the embodiment.

S11~S22: Steps

Claims (18)

A virtual currency transaction anomaly control system includes: a storage unit; and a processing unit electrically connected to the storage unit; the processing unit receives a login request; for each of a plurality of login anomaly conditions, the processing unit determines whether the login request meets the login anomaly condition; when the processing unit determines that the login request meets the login anomaly condition, the processing unit executes a login anomaly processing procedure corresponding to the login anomaly condition; wherein, when the processing unit determines whether the login request meets one of the login anomaly conditions, the processing unit determines whether the login request meets the login anomaly condition. The processing unit determines whether the number of different accounts used by a login device identification code of the login request to log into the virtual currency transaction abnormality control system within a recent fourth time period is greater than or equal to a second account number threshold value; the processing unit receives a transaction request related to a transaction by a user; for each of a plurality of transaction abnormality conditions, the processing unit determines whether the transaction meets the transaction abnormality condition; when the processing unit determines that the transaction meets the transaction abnormality condition, the processing unit executes a transaction abnormality handling procedure corresponding to the transaction abnormality condition. The virtual currency transaction anomaly control system as described in claim 1, wherein the processing unit determines whether a user data of the user meets one of a plurality of high-risk conditions; when the processing unit determines that the user data of the user meets one of the high-risk conditions, the processing unit adds a high-risk tag to the user data; when the processing unit determines that the user data of the user does not meet one of the high-risk conditions, the processing unit adds a low-risk tag to the user data; wherein the transaction anomaly conditions are divided into a plurality of high-risk user transaction anomaly conditions, a plurality of low-risk user transaction anomaly conditions, and At least one all-user transaction exception condition. After the processing unit receives the transaction request related to the transaction by the user, the processing unit determines whether the user data of the user includes the high-risk tag or the low-risk tag. When the processing unit determines that the user data of the user includes the high-risk tag, the processing unit determines whether the transaction meets the high-risk user transaction exception condition and the all-user transaction exception condition. When the processing unit determines that the user data of the user includes the low-risk tag, the processing unit determines whether the transaction meets the low-risk user transaction exception condition and the all-user transaction exception condition. The virtual currency transaction anomaly control system as described in claim 1, wherein, when the processing unit determines whether the transaction meets one of the transaction anomaly conditions, the processing unit determines whether a user's age is less than or equal to a one-year age threshold, a user's occupation is unemployed or a student, a transaction type of the transaction request is a deposit, and the transaction amount is greater than or equal to a first amount threshold. The virtual currency transaction anomaly control system as described in claim 1, wherein, when the processing unit determines whether the transaction meets one of the transaction anomaly conditions, the processing unit determines whether a user's user title is a responsible person and whether the total number of transactions and the total transaction amount of the user's exchanges between virtual currency and real currency or between different virtual currencies in a recent first time period are greater than or equal to a transaction number threshold value and a second amount threshold value, respectively. The virtual currency transaction anomaly control system as described in claim 1, wherein, when the processing unit determines whether the transaction meets one of the transaction anomaly conditions, the processing unit determines whether a transaction type of the transaction request is a deposit and a source address of the transaction request meets one of multiple suspicious addresses. The virtual currency transaction anomaly control system as described in claim 1, wherein, when the processing unit determines whether the transaction meets one of the transaction anomaly conditions, the processing unit determines whether the total amount of deposits or cash inflows and the total amount of withdrawals or cash outflows by the user in a most recent second time period are greater than or equal to a third amount threshold and a fourth amount threshold, respectively. The virtual currency transaction anomaly control system as described in claim 1, wherein, when the processing unit determines whether the transaction meets one of the transaction anomaly conditions, the processing unit determines whether the total amount of gold or cryptocurrency deposited by the user in that month is greater than a predetermined multiple of the user's monthly income. The virtual currency transaction anomaly control system as described in claim 1, wherein, when the processing unit determines whether the login request meets one of the login anomaly conditions, the processing unit determines whether a login network collaboration location address of the login request belongs to one of multiple high-risk regions. The virtual currency transaction anomaly control system as described in claim 1, wherein, when the processing unit determines whether the login request meets one of the login anomaly conditions, the processing unit determines whether the number of different accounts used by a login network coordination address of the login request to log into the virtual currency transaction anomaly control system within a recent third time period is greater than or equal to a first account quantity threshold. A method for managing virtual currency transaction anomalies is implemented by a virtual currency transaction anomaly management system. The virtual currency transaction anomaly management system includes a storage unit and a processing unit. The method includes: the processing unit receiving a login request; for each of a plurality of login anomaly conditions, the processing unit determining whether the login request meets the login anomaly condition; when the processing unit determines that the login request meets the login anomaly condition, the processing unit executing a login anomaly handling procedure corresponding to the login anomaly condition; wherein, when the processing unit determines whether the login request meets one of the login anomaly conditions, the processing unit executes a login anomaly handling procedure corresponding to the login anomaly condition; When an abnormality condition is met, the processing unit determines whether the number of different accounts used by a login device identification code in the login request to log into the virtual currency transaction abnormality control system within a recent fourth time period is greater than or equal to a second account quantity threshold; the processing unit receives a transaction request related to a transaction by a user; for each of a plurality of transaction abnormality conditions, the processing unit determines whether the transaction meets the transaction abnormality condition; and when the processing unit determines that the transaction meets the transaction abnormality condition, the processing unit executes a transaction abnormality handling procedure corresponding to the transaction abnormality condition. The method for controlling abnormal transactions of virtual currency as described in claim 10, wherein the processing unit determines whether user data of the user meets one of a plurality of high-risk conditions; when the processing unit determines that the user data of the user meets one of the high-risk conditions, the processing unit adds a high-risk tag to the user data; when the processing unit determines that the user data of the user does not meet one of the high-risk conditions, the processing unit adds a low-risk tag to the user data; wherein the abnormal transaction conditions are divided into a plurality of high-risk user transaction abnormal conditions, a plurality of low-risk user transaction abnormal conditions, and a plurality of high-risk user transaction abnormal conditions. and at least one all-user transaction anomaly condition. After the processing unit receives the transaction request related to the transaction of the user, the processing unit determines whether the user data of the user includes the high-risk tag or the low-risk tag. When the processing unit determines that the user data of the user includes the high-risk tag, the processing unit determines whether the transaction meets the high-risk user transaction anomaly conditions and the all-user transaction anomaly conditions. When the processing unit determines that the user data of the user includes the low-risk tag, the processing unit determines whether the transaction meets the low-risk user transaction anomaly conditions and the all-user transaction anomaly conditions. The method for controlling abnormal transactions of virtual currency as described in claim 10, wherein, when the processing unit determines whether the transaction meets one of the transaction abnormality conditions, the processing unit determines whether a user age of the user is less than or equal to a one-year age threshold, a user occupation of the user is unemployed or a student, a transaction type of the transaction request is a deposit, and the transaction amount is greater than or equal to a first amount threshold. As described in claim 10, the method for controlling virtual currency transactions as anomalies, wherein, when the processing unit determines whether the transaction meets one of the transaction anomaly conditions, the processing unit determines whether a user title of the user is a responsible person and whether the total number of transactions and the total amount of transactions conducted by the user in a recent first time period for exchanging virtual currency for real currency or between different virtual currencies are greater than or equal to a transaction number threshold value and a second amount threshold value, respectively. The method for controlling virtual currency transaction anomalies as described in claim 10, wherein, when the processing unit determines whether the transaction meets one of the transaction anomaly conditions, the processing unit determines whether a transaction type of the transaction request is a deposit and a source address of the transaction request meets one of multiple suspicious addresses. As described in claim 10, the method for controlling virtual currency transactions as anomaly, wherein, when the processing unit determines whether the transaction meets one of the transaction anomaly conditions, the processing unit determines whether the total amount of deposits or cash inflows and the total amount of withdrawals or cash outflows by the user in a most recent second time period are greater than or equal to a third amount threshold and a fourth amount threshold, respectively. The method for controlling virtual currency transactions as described in claim 10, wherein, when the processing unit determines whether the transaction meets one of the transaction abnormality conditions, the processing unit determines whether the total amount of gold or cryptocurrency deposited by the user in that month is greater than a predetermined multiple of the user's monthly income. The method for controlling virtual currency transaction anomalies as described in claim 10, wherein, when the processing unit determines whether the login request meets one of the login anomaly conditions, the processing unit determines whether a login network collaboration location address of the login request belongs to one of multiple high-risk areas. The method for controlling virtual currency transaction anomalies as described in claim 10, wherein, when the processing unit determines whether the login request meets one of the login anomaly conditions, the processing unit determines whether the number of different accounts used by a login network coordination address of the login request to log into the virtual currency transaction anomaly control system within a recent third time period is greater than or equal to a first account quantity threshold.