Our system implements high-risk payment masking by setting up two separate websites A ➡️ B:

• Website A: You use this site to sell high-risk products (such as IPTV, replica goods, adult videos, etc.);

• Website B: Your created “white site,” selling legal, low-risk products (such as T-shirts, household items, services, etc.).

How does the payment process get masked?

When your customer buys a high-risk product on Website A (e.g., IPTV subscription, $49.99), the system does not directly submit that order to the payment gateway. Instead:

Order Reconstruction:
The Cloak system regenerates an order on Website B with the same amount for a “legal product” (e.g., T-shirt, $49.99).

Payment Submission Masking:
The actual paid order is submitted through Website B;
The payment gateway receives information showing: legal product + legitimate website.

How to bypass payment gateway review?

Payment gateways typically use “risk control crawlers” to visit the order source site to determine if merchants engage in high-risk transactions. We use a complete set of identification and intervention mechanisms to ensure the risk control system always sees the white site content:

Risk Control Identification Technologies

• IP / ASN Detection
  We have the most comprehensive risk control IP database in the payment industry to identify crawlers from major payment gateways, banks, and anti-fraud systems.

• User-Agent Analysis
  Accurately identifies all kinds of non-human visits, including crawlers, API tests, automated detection tools, etc.

• Behavior Pattern Recognition
  Determines if visitors are real users or bots by analyzing click speed, mouse movement, and visit paths.

• Referer / Header Analysis
  Filters all abnormal request headers to further confirm visitor identity.

Intelligent Redirection Mechanism

Once identified as a risk control crawler, the system automatically redirects it to the white page content on Website B;
The risk control system ultimately sees a standard, legitimate shopping site showing low-risk product pages.

Unique Rotating Payment Feature:

You can add multiple payment accounts from the same gateway—for example, if you have 10 PayPal accounts, you can add all of them to our Cloak system.
You can set specific rules, such as: each PayPal account is allowed to process \$1,000 per day. When the first account reaches that limit, the next order will be processed by the second PayPal account. Likewise, when the second account hits \$1,000, the next order goes to the third account, and so on.

The benefit of this is: we all know that brand-new payment accounts are not trusted by payment gateways. For instance, if you register a new PayPal account—even for a legal business—processing a high volume of orders right away may lead PayPal to flag your account as high-risk or fraudulent, resulting in suspension.

The goal of rotating payments is to distribute the total transaction volume across multiple accounts, which significantly reduces the risk for each individual account.

Masking Effect

The payment gateway sees: a clean, legitimate domain + compliant product orders + normal user behavior.
Real customers still purchase the high-risk products they want. However, customers cannot detect that the orders are actually submitted by another website.