Stripe cloaking solution - am I missing something?

TomasMiller

Junior Member
Joined
Mar 5, 2023
Messages
125
Reaction score
53
I've been thinking while reading BWH topics about Stripe cloaking. Since many people want to use Stripe cloacking to use it on adult, gambling or similar sites.
As far as I see, the solution is simple, all you need to have is totally new website, new domain that sells some kind of virtual product, like a game or something, process all the payments on the new site and just use virtual coins if you need some kind of payments on real website. Use events to notify your original website about payment.

The only issue I see is when you redirect user to the new website which might be confusing for the user.

Am I missing something?
 
I've been thinking while reading BWH topics about Stripe cloaking. Since many people want to use Stripe cloacking to use it on adult, gambling or similar sites.
As far as I see, the solution is simple, all you need to have is totally new website, new domain that sells some kind of virtual product, like a game or something, process all the payments on the new site and just use virtual coins if you need some kind of payments on real website. Use events to notify your original website about payment.

The only issue I see is when you redirect user to the new website which might be confusing for the user.

Am I missing something?
Yeah, that’s basically how cloaking works run a clean front site while your main traffic/products live elsewhere. It buys time, but Stripe audits descriptors and user complaints, so it’s never permanent. I see it come up a lot in my line of work, usually as a short-term survival tactic before moving onto something more stable
 
I've been thinking while reading BWH topics about Stripe cloaking. Since many people want to use Stripe cloacking to use it on adult, gambling or similar sites.
As far as I see, the solution is simple, all you need to have is totally new website, new domain that sells some kind of virtual product, like a game or something, process all the payments on the new site and just use virtual coins if you need some kind of payments on real website. Use events to notify your original website about payment.

The only issue I see is when you redirect user to the new website which might be confusing for the user.

Am I missing something?
yeah that’s pretty much how most people do it—set up a clean front site stripe is okay with and then connect it back to the real project. the main problem is user experience, since sending people to another site can feel shady. plus, stripe is sharp at catching patterns, so if traffic looks off or there are too many disputes, they’ll flag it. it can work in the short run, but it’s not a stable long-term solution.
 
Back
Top