payment cloaking help

Elegante

Regular Member
Joined
Jul 6, 2015
Messages
429
Reaction score
153
What do they actually do? Do they just hide your products and website from payment providers like what you're selling and everything? Is that it?
And do other people charge a percentage based on that (like cloaking service providers)?
Because I don't understand what's so difficult about payment cloakers.
 
We're in this industry, so I can provide you some input based on experience.

The charge is mostly based on how fast the product is shipped with updates and mitigation and the dashboard and the features.

Payment cloaking let's a user complete every activity in a non-compliant site, when they checkout they reach a page on a secondary compliant site where they can see their order details and make the payment.

Once the payment succeeds, they are sent back to their old site.

All of this happens without leaking the name of the original site or the service in the source code.

The payment provider never sees the primary site.

There are additional features that include the ability to rotate the secondary site and payment gateways etc.

Ability to get notified when a particular payment gateway gets nuked or has high error rates.

And a lot of very specific things happening in the background for it to work.
 
We're in this industry, so I can provide you some input based on experience.

The charge is mostly based on how fast the product is shipped with updates and mitigation and the dashboard and the features.

Payment cloaking let's a user complete every activity in a non-compliant site, when they checkout they reach a page on a secondary compliant site where they can see their order details and make the payment.

Once the payment succeeds, they are sent back to their old site.

All of this happens without leaking the name of the original site or the service in the source code.

The payment provider never sees the primary site.

There are additional features that include the ability to rotate the secondary site and payment gateways etc.

Ability to get notified when a particular payment gateway gets nuked or has high error rates.

And a lot of very specific things happening in the background for it to work.
I saw that you said this part :
"when they checkout they reach a page on a secondary compliant site where they can see their order details and make the payment"
why cant we juts cloak the page tho then?
 
What do they actually do? Do they just hide your products and website from payment providers like what you're selling and everything? Is that it?
And do other people charge a percentage based on that (like cloaking service providers)?
Because I don't understand what's so difficult about payment cloakers.
payment cloakers go beyond just replacing content
they do more checks and spoof info
 
payment cloakers go beyond just replacing content
they do more checks and spoof info
can you give me more info like what checks do they go through i am only aware like they receive payment details, ordered item details
check the webhook has to be from the same domain .

I mean for a payment cloaker that works with alot of api calls then that's different obv they will have to spoof alot of stuff, so that it can imitate the same domain same webhook etc. or is there something else to it
 
you can buy stealth stripe accounts in markets in darketn

but why not just stick to lgeal stuff?
 
why cant we juts cloak the page tho then?

Because the Payment Gateway's checkout element loads on the page.

This means the payment gateway gets more than enough information to determine what page and what domain the payment is coming from.

This differentiates from traditional Ads cloaking because you're not just providing the PG with your site link to send traffic too, you're actually loading their SDK on the site.

Which is why you need a legitimate, compliant site. So when audited, everything comes green.
 
Because the Payment Gateway's checkout element loads on the page.

This means the payment gateway gets more than enough information to determine what page and what domain the payment is coming from.

This differentiates from traditional Ads cloaking because you're not just providing the PG with your site link to send traffic too, you're actually loading their SDK on the site.

Which is why you need a legitimate, compliant site. So when audited, everything comes green.
Well, we can just have a common DB for both the clean and non-clean sites and just map the products differently, only on the frontend while keeping the backend intact

Basically:
One is clean and compliant for Stripe and PayPal audits
One is cloaked and shown only to real users with blackhat offers but it still uses a clean DB so the products are legit and not shady, just mapped differently on the frontend
Both sites pull from the same backend so inventory, prices, and orders stay synced
On the blackhat site users just see different stuff on the frontend but the backend stays the same which is what Stripe usually accesses, since all payment gateway providers get product details directly from the backend or database

Each site handles fulfillment and logs independently but stays tied to the same account (differnet webhook - this is compliant)
 
What does overcomplicating the entire setup, the way you describe, actually gain?

Loading non-compliant offers for users brings the domain in question to the fore, and thereby the PG account associated with it in jeapordy.

Creating a compliant digital product site takes less than a day. It operates independently, can be easily rotated to use multiple stripe accounts to mitigate reporting from competitors and other takedowns or suspensions.

While the non-compliant site can continue to function normally and be promoted through organic means.
 
What does overcomplicating the entire setup, the way you describe, actually gain?

Loading non-compliant offers for users brings the domain in question to the fore, and thereby the PG account associated with it in jeapordy.

Creating a compliant digital product site takes less than a day. It operates independently, can be easily rotated to use multiple stripe accounts to mitigate reporting from competitors and other takedowns or suspensions.

While the non-compliant site can continue to function normally and be promoted through organic means.
isn't that the whole point of payment cloakers to sell non compliant products ?
and also of the cloakers to hide non compliant websites?

oh i get your point too now you are saying the non compliant site will open the stripe sdk and all that will lead to flaggint the domain?
but payment processor only check browser fingerpirnts and Checkout metadata
 
Last edited:
Cloaking isn't meant for illegal items although some use it like that. You can use it to select countries and to protect against fraud, among other ideas. There is no difference between payment cloaking or other cloaking, they're all the same.
 
Cloaking isn't meant for illegal items although some use it like that. You can use it to select countries and to protect against fraud, among other ideas. There is no difference between payment cloaking or other cloaking, they're all the same.
oh i see now, type shit
 
Yeah, payment cloaking hides the real product from payment providers and shows them a clean version. It involves things like IP filtering and bot detection, which makes it more complex and why some charge higher fees.
 
Payment cloaking typically involves product information obfuscation, transaction splitting and synchronization, payment gateway crawler detection and redirection, and multi-route processing — not just simply hiding products or the website. At muadata.com, we have been working in payment cloaking for many years and possess extensive experience specifically in payment-related cloaking.
 
Back
Top