The mechanics of cloaking..

mweeku

Newbie
Joined
May 7, 2025
Messages
14
Reaction score
2
Afternoon all

Please note: I am not looking to purchase solutions - the last thread I read was closed because it started to turn into a sales thread. Please don't do that here.

Anyway, I in the process of setting up something online and I need to accept payments for a high risk business. I am investigating cloaking.

I'll start with a general question...I read somewhere not to bother with cloaking as Str1pe & others have a way of seeing where the traffic comes from on the way into their screen to make payment, how is this even possible? I can only think their JS SDK is picking up the referrer on the first visit into legit site from risky site?

I also see a mechanism where you have 2 sites under your let's call them site Risk and site Safe. Is the theory with this that you get the traffic into your Risk site and when it comes to payment pass them through to your Safe site to take payment....and any callbacks from the payment SDK go to Safe site. Once the payment etc is all complete you can then safely redirect them back to site Risk.

Now I am assuming at this point that site Safe will have some products for sale that can be purchased by just logging site Safe and going to checkout. This way, the site passes scrutiny by Stripe.

But aside from all of this..... can stripe still discover the source of the traffic?

The other option I was thinking of was to build a kind of professional services style site / or some kind of subscription site (as cloak) which would often use payment links in email.... then when somebody buys my product on site Risk I just email them a payment link to complete the transaction, which will start a new flow originating from the users mailbox.

What do you think?
 
Back
Top