If the collection code is used for remote collection, it will face the problem of risk control, because the collection code itself can only be used for face-to-face payment, and there are restrictions on remote places, high frequency, and large amounts. If the merchant's aggregation code is subject to risk control, it will lead to the failure of collection or the freezing of funds, affecting normal operations.
So, what should I do if remote collection is always controlled by risk?
As a leading merchant who operates a number of brands to aggregate collection codes, coupled with many years of industry experience, the solutions we give are as follows:
Try to use remote collection tools - receipts and small programsThese two tools can reduce the probability of remote risk control in terms of design principles. Pay by clicking on a link or by identifying ** to go to a web page. In this way, the payment platform will not consider it to be an abnormal transaction, but a normal transaction of the platform's purchase. Therefore, the use of receipts and mini programs can effectively avoid the problem of risk control. At present, there are many aggregation codes on the market that support payment slips and small programs, such as Fubei, Bill Pay, and Leshu.
2. If there are indeed many remote payments, handle several different aggregate collection codes, and use it instead. Different aggregate collection codes have different service providers and payment channels, if the merchant has multiple aggregate collection codes, you can spread the risk and reduce the probability of being controlled by risk.
3. If the amount is relatively large, the above two methods do not workIt is recommended to apply for H5 Dynamic LinkAlthough the cost of this method is higher, it is resistant to risk control. Relatively stable