Transaction risk control method and device

Abstract

The application relates to the technical field of risk control, and provides a transaction risk control method and device. The method comprises the following steps: acquiring channel risk control rules of a plurality of third-party payment channels bound by a merchant; generating platform risk control rules based on the channel risk control rules; the strictness of the platform risk control rules is greater than the strictness of the channel risk control rules; when detecting that a transaction behavior of the merchant triggers the platform risk control rules, switching a third-party payment channel corresponding to the transaction behavior to another third-party payment channel. The platform of the application sets platform risk control rules that are more strict than channel risk control rules, pre-controls the transaction behavior of the merchant, can maximally reduce the probability that the transaction behavior of the merchant triggers the channel risk control rules, and thus can maximally avoid the false risk control of the merchant account function when facing the occasional payment transaction change of the merchant.

Description

Technical Field

[0001] This application relates to the field of risk control technology, specifically to a transaction risk control method and apparatus. Background Technology

[0002] Software as a Service (SaaS) platforms provide merchants with a range of services, including operations management, marketing promotion, and data analysis. They also facilitate daily payment and collection for merchants by connecting to third-party payment platforms linked to their accounts.

[0003] Typically, payment risk control is implemented by third-party payment platforms according to their risk control rules. When a payment transaction triggers a risk control rule, the third-party payment platform will restrict or block the merchant's account functions, preventing the merchant from receiving and making payments normally on the platform.

[0004] However, merchants may experience occasional changes in their payment and receipt processes due to sudden changes in their business operations. When these occasional changes trigger risk control rules, they may lead to incorrect risk control of the merchant's account functions. Summary of the Invention

[0005] This application provides a transaction risk control method and apparatus to solve the technical problem that occasional changes in merchant payments trigger the risk control rules of third-party payment platforms, leading to erroneous risk control of merchant account functions.

[0006] In a first aspect, embodiments of this application provide a transaction risk control method, including: Obtain the channel risk control rules of multiple third-party payment channels linked to the merchant; Based on the channel risk control rules, platform risk control rules are generated; the platform risk control rules are more stringent than the channel risk control rules. When the platform detects that a merchant's transaction behavior triggers the platform's risk control rules, the third-party payment channel corresponding to the transaction behavior will be switched to another third-party payment channel.

[0007] In one embodiment, the channel risk control rules for any of the aforementioned third-party payment channels are obtained based on the following method: Directly obtain the publicly available channel risk control rules of the aforementioned third-party payment channels; and / or Based on the channel risk control model of the third-party payment and collection channel, the channel risk control rules of the third-party payment and collection channel are obtained.

[0008] In one embodiment, the channel risk control model is obtained based on the following method: Based on the historical transaction behavior of multiple merchants on the third-party payment channel and their trigger tags for the channel risk control rules, any classification model is trained to obtain the channel risk control model.

[0009] In one embodiment, switching the third-party payment channel corresponding to the transaction to another third-party payment channel includes: Receive the merchant's first appeal request regarding the transaction behavior triggering the platform's risk control rules; Verify the merchant's signature carried in the first appeal request; Upon successful verification, the merchant is shown an appeal form page. Based on the appeal details filled in by the merchant on the appeal form, a reassessment is made as to whether the transaction triggered the platform's risk control rules. Based on the result of the re-judgment, the merchant's third-party payment channels are processed.

[0010] In one embodiment, processing the merchant's third-party payment channels based on the result of the re-determination includes: If the result of the re-judgment is that the transaction behavior triggers the platform's risk control rules, then the merchant's current payment channel will remain the switched third-party payment channel. If the result of the reassessment is that the transaction behavior does not trigger the platform's risk control rules, then the merchant's current payment channel will be switched back to the original third-party payment channel.

[0011] In one embodiment, switching the third-party payment channel corresponding to the transaction to another third-party payment channel includes: Receive the merchant's second appeal request regarding the transaction behavior triggering the channel risk control rules; Verify the merchant's signature carried in the second appeal request; Upon successful verification, the merchant is shown an appeal form page. Based on the appeal details filled in by the merchant on the appeal form, a third appeal request is sent to the third-party payment channel corresponding to the transaction.

[0012] Secondly, embodiments of this application provide a transaction risk control device, comprising: The channel risk control rule acquisition module is used to: acquire the channel risk control rules of multiple third-party payment channels bound to a merchant; The platform risk control rule generation module is used to: generate platform risk control rules based on the channel risk control rules; the platform risk control rules are more stringent than the channel risk control rules. The platform risk control rule execution module is used to: when the platform detects that the merchant's transaction behavior triggers the platform risk control rule, switch the third-party payment channel corresponding to the transaction behavior to another third-party payment channel.

[0013] Thirdly, embodiments of this application provide an electronic device, including a processor and a memory storing a computer program, wherein the processor executes the program to implement the steps of the transaction risk control method described in the first aspect.

[0014] Fourthly, embodiments of this application provide a computer program product, including a computer program that, when executed by a processor, implements the steps of the transaction risk control method described in the first aspect.

[0015] Fifthly, embodiments of this application provide a non-transitory computer-readable storage medium, including a computer program, which, when executed by a processor, implements the steps of the transaction risk control method described in the first aspect.

[0016] The transaction risk control method and device provided in this application obtain the channel risk control rules of multiple third-party payment channels bound to a merchant, generate platform risk control rules based on the channel risk control rules, and the platform risk control rules are more stringent than the channel risk control rules. When a merchant's transaction behavior is detected to trigger the platform risk control rules, the third-party payment channel corresponding to the transaction behavior is switched to another third-party payment channel. In this application, the platform sets up a layer of risk control rules between merchants and third-party payment channels. Since the platform's risk control rules are stricter than the channel's risk control rules, it can proactively prevent transactions that might trigger channel risk control rules and switch the corresponding third-party payment channel for the transaction. On the one hand, since the channel risk control rules for each third-party payment channel are not exactly the same, the platform's risk control rules generated for each third-party payment channel are also not exactly the same. After switching, the transaction may not trigger new platform risk control rules, and therefore will not trigger new channel risk control rules either, greatly reducing the probability of the merchant's account being restricted or banned. On the other hand, since merchants can observe the switching of third-party payment channels during payment operations, they will also proactively realize that there may be problems with their transactions, and thus proactively adjust their transactions to avoid triggering platform risk control rules again, thereby simultaneously reducing the probability of triggering new channel risk control rules. The probability of the merchant's account being restricted or banned will also be greatly reduced. In summary, by setting stricter platform risk control rules than channel risk control rules, this application platform can pre-control merchant transaction behavior, thereby minimizing the probability of merchant transaction behavior triggering channel risk control rules. This also minimizes the risk of mis-control of merchant account functions when faced with occasional changes in merchant payment transactions. Attached Figure Description

[0017] To more clearly illustrate the technical solutions in this application or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0018] Figure 1 This is one of the flowcharts illustrating the transaction risk control method provided in the embodiments of this application; Figure 2 This is the second flowchart illustrating the transaction risk control method provided in the embodiments of this application; Figure 3 This is the third flowchart illustrating the transaction risk control method provided in the embodiments of this application; Figure 4 This is a schematic diagram of the transaction risk control device provided in the embodiments of this application; Figure 5 This is a schematic diagram of the structure of the electronic device provided in the embodiments of this application. Detailed Implementation

[0019] To make the objectives, technical solutions, and advantages of this application clearer, the technical solutions of this application will be clearly and completely described below with reference to the accompanying drawings of the embodiments. Obviously, the described embodiments are only some embodiments of this application, not all embodiments. Based on the embodiments of this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.

[0020] It should be noted that in the description of the embodiments of this application, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that includes a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitations, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes said element. The terms "upper," "lower," etc., indicating orientation or positional relationships based on the orientation or positional relationships shown in the accompanying drawings, are only for the convenience of describing this application and simplifying the description, and do not indicate or imply that the device or element referred to must have a specific orientation, or be constructed and operated in a specific orientation, and therefore should not be construed as a limitation of this application. Unless otherwise expressly specified and limited, the terms "installed," "connected," and "linked" should be interpreted broadly, for example, they can be fixed connections, detachable connections, or integral connections; they can be mechanical connections or electrical connections; they can be direct connections or indirect connections through an intermediate medium; and they can be internal connections between two elements. Those skilled in the art can understand the specific meaning of the above terms in this application according to the specific circumstances.

[0021] The terms "first," "second," etc., used in this application are used to distinguish similar objects and not to describe a specific order or sequence. It should be understood that such data can be interchanged where appropriate so that embodiments of this application can be implemented in orders other than those illustrated or described herein, and the objects distinguished by "first," "second," etc., are generally of the same class, without limiting the number of objects; for example, a first object can be one or more. Furthermore, "and / or" indicates at least one of the connected objects, and the character " / " generally indicates that the preceding and following objects have an "or" relationship.

[0022] Figure 1 This is one of the flowcharts illustrating the transaction risk control method provided in the embodiments of this application; see reference. Figure 1 This application provides a transaction risk control method, which may include: 101. Obtain the channel risk control rules for multiple third-party payment channels linked to the merchant; 102. Generate platform risk control rules based on channel risk control rules; The platform's risk control rules are more stringent than those of the channels. 103. When a merchant's transaction behavior is detected to trigger the platform's risk control rules, the third-party payment channel corresponding to the transaction behavior will be switched to another third-party payment channel.

[0023] In step 101, merchants can bind multiple third-party payment channels on the platform according to their actual needs, and can add or unbind channels at any time.

[0024] In step 102, the platform will generate corresponding platform risk control rules based on the channel risk control rules of each third-party payment channel bound to each merchant. That is, the channel risk control rules and the platform risk control rules are one-to-one.

[0025] In step 103, both the merchant's pre- and post-switching third-party payment channels are those bound to the platform. When confirming actual payment transactions, the merchant can change the third-party payment channel after the switch. That is, although the platform switches the merchant's third-party payment channel, the merchant retains the final decision on whether to use it as the new payment channel. If the merchant does not change the switched third-party payment channel, it will be used as the new payment channel, and the platform will re-check whether the merchant's transaction behavior triggers the platform's risk control rules corresponding to the new payment channel. If the merchant changes the switched third-party payment channel, it will be used as the new payment channel, and the platform will re-check whether the merchant's transaction behavior triggers the platform's risk control rules corresponding to the new payment channel.

[0026] The transaction risk control method provided in this embodiment obtains the channel risk control rules of multiple third-party payment channels bound to the merchant, generates platform risk control rules based on the channel risk control rules, and the platform risk control rules are more stringent than the channel risk control rules. When the merchant's transaction behavior is detected to trigger the platform risk control rules, the third-party payment channel corresponding to the transaction behavior is switched to another third-party payment channel. In this embodiment, the platform sets up a layer of risk control rules between the merchant and the third-party payment channels. Since the platform's risk control rules are stricter than the channel's risk control rules, it can proactively prevent transactions that might trigger channel risk control rules and switch the corresponding third-party payment channel for the transaction. On the one hand, since the channel risk control rules for each third-party payment channel are not exactly the same, the platform's risk control rules generated for each third-party payment channel are also not exactly the same. After switching, the transaction may not trigger new platform risk control rules, and therefore will not trigger new channel risk control rules either, greatly reducing the probability of the merchant's account being restricted or banned. On the other hand, since the merchant can observe the switching of third-party payment channels during payment operations, the merchant will also proactively realize that there may be problems with the transaction behavior, and thus proactively adjust their transaction behavior to avoid triggering the platform risk control rules again, thereby simultaneously reducing the probability of triggering new channel risk control rules. The probability of the merchant's account being restricted or banned will also be greatly reduced. In summary, this embodiment of the platform sets stricter platform risk control rules than the channel risk control rules to pre-control the risk of merchants' transaction behavior. This can minimize the probability of merchants' transaction behavior triggering the channel risk control rules, thereby minimizing the risk control errors of merchant account functions when faced with occasional changes in merchants' payment and receipt transactions.

[0027] In one embodiment, the channel risk control rules of any of the aforementioned third-party payment channels can be obtained in the following ways: Directly obtain publicly available channel risk control rules from third-party payment and collection channels; and / or Based on the channel risk control model of third-party payment channels, obtain the channel risk control rules of the third-party payment channels; wherein, the channel risk control model can be obtained based on the following methods: Based on the historical transaction behavior of multiple merchants on third-party payment channels and their trigger tags for channel risk control rules, a channel risk control model is obtained by training any classification model.

[0028] In this embodiment, some third-party payment channels disclose their own risk control rules, which can be obtained directly; some third-party payment channels do not disclose their own risk control rules, which can be obtained by learning the characteristics of merchants' historical transaction behavior on these third-party payment channels. It should be noted that these historical transaction behaviors can only be collected and used with the user's authorization.

[0029] In the process of acquiring channel risk control models, multiple merchants can be selected based on their historical transaction volume, total transaction amount, average transaction amount, and maximum single transaction amount on a third-party payment channel. These data, along with daily data on whether the merchants' daily transactions trigger the channel risk control rules of the third-party payment channel (i.e., whether their daily transactions result in account restrictions or bans), are used as a training set to train the classification model. This allows the model to accurately output the probability of each merchant triggering the channel risk control rules of the third-party payment channel based on their daily historical transaction volume, total transaction amount, average transaction amount, and maximum single transaction amount. This allows the acquisition of the channel risk control rules set by the third-party payment channel for merchants based on their transaction volume, total transaction amount, average transaction amount, and maximum single transaction amount.

[0030] Furthermore, assuming that the risk control rule of a certain third-party payment channel is that there are 5 consecutive transactions exceeding 1,000 yuan, then the platform risk control rule can be generated to be 4 consecutive transactions exceeding 1,000 yuan, thereby preventing the merchant's transaction behavior from triggering the channel's risk control rule in advance.

[0031] It should be noted that even if a third-party payment channel has publicly disclosed its own channel risk control rules, it is still possible to construct a channel risk control model for that third-party payment channel and obtain the channel risk control rules accordingly. By comparing and integrating the channel risk control rules obtained through the two methods, on the one hand, the channel risk control model obtained through the model can be corrected based on the channel's publicly disclosed channel risk control rules; on the other hand, potential channel risk control rules that have not been disclosed by the channel can be discovered, thereby ultimately obtaining complete and accurate channel risk control rules.

[0032] This embodiment obtains channel risk control rules through multiple means to ensure the availability of channel risk control rules, and can further compare and integrate these channel risk control rules to ensure the completeness and accuracy of the final channel risk control rules.

[0033] Figure 2 This is the second flowchart illustrating the transaction risk control method provided in the embodiments of this application; see also... Figure 2 In one embodiment, after switching the third-party payment channel corresponding to the transaction to another third-party payment channel, the following may be included: 201. Receive the first appeal request from merchants regarding transaction behavior that triggers the platform's risk control rules; 202. Verify the merchant's signature carried in the first appeal request; 203. Upon successful verification, display the appeal form to the merchant; 204. Based on the appeal details filled in by the merchant on the appeal form, a reassessment will be made as to whether the transaction triggered the platform's risk control rules; 205. If the result of the further judgment is that the transaction behavior triggers the platform's risk control rules, then the merchant's current payment and receipt channel will remain the switched third-party payment and receipt channel; 206. If the result of the further judgment is that the transaction behavior has not triggered the platform's risk control rules, then the merchant's current payment and collection channel will be switched back to the original third-party payment and collection channel.

[0034] Sometimes, a merchant's transaction behavior does not actually trigger the platform's risk control rules, but is incorrectly judged by the platform as having triggered them for various reasons. In response to this situation, this embodiment provides merchants with an appeal channel for triggering the platform's risk control rules. Through simple procedures such as merchant signature verification and appeal details collection, a reassessment of whether a merchant's transaction behavior has triggered the platform's risk control rules can be initiated. Merchants do not need to engage in cumbersome communication with the platform, thereby reducing their communication costs.

[0035] Figure 3 This is the third flowchart illustrating the transaction risk control method provided in this application embodiment; see also... Figure 3 In one embodiment, after switching the third-party payment channel corresponding to the transaction to another third-party payment channel, the following may be included: 301. Receive the merchant's second appeal request regarding the transaction behavior triggering the channel's risk control rules; 302. Verify the merchant's signature carried in the second appeal request; 303. Upon successful verification, display the appeal form to the merchant; 304. Based on the appeal details filled in by the merchant on the appeal form, send a third appeal request to the third-party payment channel corresponding to the transaction.

[0036] Since platform risk control rules are stricter than channel risk control rules, a merchant's transaction behavior should not trigger channel risk control rules if it does not trigger platform risk control rules. However, for various reasons, third-party payment channels may mistakenly judge that channel risk control rules have been triggered. To address this, this embodiment provides merchants with an appeal channel for triggering channel risk control rules. Through simple procedures such as merchant signature verification and appeal details collection, the process of appealing to third-party payment channels on behalf of the merchant can be initiated. In other words, it communicates with third-party payment channels on behalf of the merchant, eliminating the need for merchants to engage in cumbersome communication with third-party payment channels themselves, thereby reducing the merchant's communication costs.

[0037] The transaction risk control device provided in the embodiments of this application is described below. The transaction risk control device described below can be referred to in correspondence with the transaction risk control method described above.

[0038] Figure 4 This is a schematic diagram of the transaction risk control device provided in an embodiment of this application. (Refer to...) Figure 4 This application provides a transaction risk control device, which may include: The channel risk control rule acquisition module 401 is used to: acquire the channel risk control rules of multiple third-party payment channels bound to a merchant; The platform risk control rule generation module 402 is used to: generate platform risk control rules based on the channel risk control rules; the platform risk control rules are more stringent than the channel risk control rules. The platform risk control rule execution module 403 is used to: when the platform detects that the merchant's transaction behavior triggers the platform risk control rule, switch the third-party payment channel corresponding to the transaction behavior to another third-party payment channel.

[0039] The transaction risk control device provided in this embodiment obtains the channel risk control rules of multiple third-party payment channels bound to the merchant, generates platform risk control rules based on the channel risk control rules, and the platform risk control rules are more stringent than the channel risk control rules. When the merchant's transaction behavior is detected to trigger the platform risk control rules, the third-party payment channel corresponding to the transaction behavior is switched to another third-party payment channel. In this embodiment, the platform sets up a layer of risk control rules between the merchant and the third-party payment channels. Since the platform's risk control rules are stricter than the channel's risk control rules, it can proactively prevent transactions that might trigger channel risk control rules and switch the corresponding third-party payment channel for the transaction. On the one hand, since the channel risk control rules for each third-party payment channel are not exactly the same, the platform's risk control rules generated for each third-party payment channel are also not exactly the same. After switching, the transaction may not trigger new platform risk control rules, and therefore will not trigger new channel risk control rules either, greatly reducing the probability of the merchant's account being restricted or banned. On the other hand, since the merchant can observe the switching of third-party payment channels during payment operations, the merchant will also proactively realize that there may be problems with the transaction behavior, and thus proactively adjust their transaction behavior to avoid triggering the platform risk control rules again, thereby simultaneously reducing the probability of triggering new channel risk control rules. The probability of the merchant's account being restricted or banned will also be greatly reduced. In summary, this embodiment of the platform sets stricter platform risk control rules than the channel risk control rules to pre-control the risk of merchants' transaction behavior. This can minimize the probability of merchants' transaction behavior triggering the channel risk control rules, thereby minimizing the risk control errors of merchant account functions when faced with occasional changes in merchants' payment and receipt transactions.

[0040] In one embodiment, the channel risk control rule acquisition module 401 is specifically used for: Directly obtain the publicly available channel risk control rules of the aforementioned third-party payment channels; and / or Based on the channel risk control model of the third-party payment and collection channel, the channel risk control rules of the third-party payment and collection channel are obtained.

[0041] In one embodiment, a channel risk control model building module (not shown in the figure) is also included, for: Based on the historical transaction behavior of multiple merchants on the third-party payment channel and their trigger tags for the channel risk control rules, any classification model is trained to obtain the channel risk control model.

[0042] In one embodiment, a first appeal module (not shown in the figure) is further included for: Receive the merchant's first appeal request regarding the transaction behavior triggering the platform's risk control rules; Verify the merchant's signature carried in the first appeal request; Upon successful verification, the merchant is shown an appeal form page. Based on the appeal details filled in by the merchant on the appeal form, a reassessment is made as to whether the transaction triggered the platform's risk control rules. Based on the result of the re-judgment, the merchant's third-party payment channels are processed.

[0043] In one embodiment, the first appeal module is specifically used for If the result of the re-judgment is that the transaction behavior triggers the platform's risk control rules, then the merchant's current payment channel will remain the switched third-party payment channel. If the result of the reassessment is that the transaction behavior does not trigger the platform's risk control rules, then the merchant's current payment channel will be switched back to the original third-party payment channel.

[0044] In one embodiment, a second appeal module (not shown in the figure) is further included for: Receive the merchant's second appeal request regarding the transaction behavior triggering the channel risk control rules; Verify the merchant's signature carried in the second appeal request; Upon successful verification, the merchant is shown an appeal form page. Based on the appeal details filled in by the merchant on the appeal form, a third appeal request is sent to the third-party payment channel corresponding to the transaction.

[0045] Figure 5 is a schematic diagram of the structure of the electronic device provided in an embodiment of this application, as shown below. Figure 5As shown, the electronic device may include: a processor 510, a communication interface 520, a memory 530, and a communication bus 540, wherein the processor 510, the communication interface 520, and the memory 530 communicate with each other via the communication bus 540. The processor 510 can call the computer program in the memory 530 to execute the steps of the transaction risk control method, such as including: Obtain the channel risk control rules of multiple third-party payment channels linked to the merchant; Based on the channel risk control rules, platform risk control rules are generated; the platform risk control rules are more stringent than the channel risk control rules. When the platform detects that a merchant's transaction behavior triggers the platform's risk control rules, the third-party payment channel corresponding to the transaction behavior will be switched to another third-party payment channel.

[0046] Furthermore, the logical instructions in the aforementioned memory 530 can be implemented as software functional units and, when sold or used as independent products, can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or a portion of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0047] On the other hand, this application also provides a computer program product, which includes a computer program that can be stored on a non-transitory computer-readable storage medium. When the computer program is executed by a processor, the computer can perform the steps of the transaction risk control method provided in the above embodiments, such as: Obtain the channel risk control rules of multiple third-party payment channels linked to the merchant; Based on the channel risk control rules, platform risk control rules are generated; the platform risk control rules are more stringent than the channel risk control rules. When the platform detects that a merchant's transaction behavior triggers the platform's risk control rules, the third-party payment channel corresponding to the transaction behavior will be switched to another third-party payment channel.

[0048] On the other hand, embodiments of this application also provide a non-transitory computer-readable storage medium storing a computer program thereon, the computer program being used to cause a processor to execute the steps of the transaction risk control methods provided in the above embodiments, for example including: Obtain the channel risk control rules of multiple third-party payment channels linked to the merchant; Based on the channel risk control rules, platform risk control rules are generated; the platform risk control rules are more stringent than the channel risk control rules. When the platform detects that a merchant's transaction behavior triggers the platform's risk control rules, the third-party payment channel corresponding to the transaction behavior will be switched to another third-party payment channel.

[0049] The non-transitory computer-readable storage medium can be any available medium or data storage device that the processor can access, including but not limited to magnetic memory (e.g., floppy disk, hard disk, magnetic tape, magneto-optical disk (MO)), optical memory (e.g., CD, DVD, BD, HVD), and semiconductor memory (e.g., ROM, EPROM, EEPROM, non-volatile memory (NAND FLASH), solid-state drive (SSD)).

[0050] The device embodiments described above are merely illustrative. The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the modules can be selected to achieve the purpose of this embodiment according to actual needs. Those skilled in the art can understand and implement this without any creative effort.

[0051] Through the above description of the embodiments, those skilled in the art can clearly understand that each embodiment can be implemented by means of software plus necessary general-purpose hardware platforms, and of course, it can also be implemented by hardware. Based on this understanding, the above technical solutions, in essence or the part that contributes to the prior art, can be embodied in the form of a software product. This computer software product can be stored in a computer-readable storage medium, such as ROM / RAM, magnetic disk, optical disk, etc., and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute the methods described in the various embodiments or some parts of the embodiments.

[0052] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of this application, and are not intended to limit them. Although this application has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some of the technical features. Such modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the spirit and scope of the technical solutions of the embodiments of this application.

Claims

1. A transaction risk control method, characterized in that, include: Obtain the channel risk control rules of multiple third-party payment channels linked to the merchant; Based on the channel risk control rules, platform risk control rules are generated; the platform risk control rules are more stringent than the channel risk control rules. When the platform detects that a merchant's transaction behavior triggers the platform's risk control rules, the third-party payment channel corresponding to the transaction behavior will be switched to another third-party payment channel.

2. The transaction risk control method according to claim 1, characterized in that, The channel risk control rules for any of the aforementioned third-party payment channels are obtained based on the following methods: Directly obtain the publicly available channel risk control rules of the aforementioned third-party payment channels; and / or Based on the channel risk control model of the third-party payment and collection channel, the channel risk control rules of the third-party payment and collection channel are obtained.

3. The transaction risk control method according to claim 2, characterized in that, The channel risk control model is obtained based on the following method: Based on the historical transaction behavior of multiple merchants on the third-party payment channel and their trigger tags for the channel risk control rules, any classification model is trained to obtain the channel risk control model.

4. The transaction risk control method according to claim 1, characterized in that, After switching the third-party payment channel corresponding to the transaction to another third-party payment channel, the process includes: Receive the merchant's first appeal request regarding the transaction behavior triggering the platform's risk control rules; Verify the merchant's signature carried in the first appeal request; Upon successful verification, the merchant is shown an appeal form page. Based on the appeal details filled in by the merchant on the appeal form, a reassessment is made as to whether the transaction triggered the platform's risk control rules. Based on the result of the re-judgment, the merchant's third-party payment channels are processed.

5. The transaction risk control method according to claim 4, characterized in that, The processing of the merchant's third-party payment channels based on the result of the re-determination includes: If the result of the re-judgment is that the transaction behavior triggers the platform's risk control rules, then the merchant's current payment channel will remain the switched third-party payment channel. If the result of the reassessment is that the transaction behavior does not trigger the platform's risk control rules, then the merchant's current payment channel will be switched back to the original third-party payment channel.

6. The transaction risk control method according to claim 1, characterized in that, After switching the third-party payment channel corresponding to the transaction to another third-party payment channel, the process includes: Receive the merchant's second appeal request regarding the transaction behavior triggering the channel risk control rules; Verify the merchant's signature carried in the second appeal request; Upon successful verification, the merchant is shown an appeal form page. Based on the appeal details filled in by the merchant on the appeal form, a third appeal request is sent to the third-party payment channel corresponding to the transaction.

7. A transaction risk control device, characterized in that, include: The channel risk control rule acquisition module is used to: acquire the channel risk control rules of multiple third-party payment channels bound to a merchant; The platform risk control rule generation module is used to: generate platform risk control rules based on the channel risk control rules; the platform risk control rules are more stringent than the channel risk control rules. The platform risk control rule execution module is used to: when the platform detects that the merchant's transaction behavior triggers the platform risk control rule, switch the third-party payment channel corresponding to the transaction behavior to another third-party payment channel.

8. An electronic device comprising a processor and a memory storing a computer program, characterized in that, When the processor executes the computer program, it implements the steps of the transaction risk control method according to any one of claims 1 to 6.

9. A computer program product, comprising a computer program, characterized in that, When the computer program is executed by the processor, it implements the steps of the transaction risk control method according to any one of claims 1 to 6.

10. A non-transitory computer-readable storage medium having a computer program stored thereon, characterized in that, When the computer program is executed by the processor, it implements the steps of the transaction risk control method according to any one of claims 1 to 6.

Images