Hi there,
I’m currently trying to use a cloaking approach because my website sells NSFW content, which is not authorized by Stripe.
I’ve created a second “mirror” website that is compliant with Stripe. It uses the same domain name as the NSFW site but with a different extension (.dev). This mirror site only presents a boilerplate, Stripe-compliant template.
The intended flow is:
Users pay on the NSFW website → they are redirected to the Stripe Checkout hosted on the mirror website → then redirected back to the NSFW website.
However, I assume this method will not work in the long run, as Stripe will likely detect that the .dev website is only a mirror.
Is there any guidance on a cleaner and “safer” approach (even though I know it’s never truly safe), considering that I’m using Xano as a backend (a no-code backend platform)?
Thanks and have a wonderful day
I’m currently trying to use a cloaking approach because my website sells NSFW content, which is not authorized by Stripe.
I’ve created a second “mirror” website that is compliant with Stripe. It uses the same domain name as the NSFW site but with a different extension (.dev). This mirror site only presents a boilerplate, Stripe-compliant template.
The intended flow is:
Users pay on the NSFW website → they are redirected to the Stripe Checkout hosted on the mirror website → then redirected back to the NSFW website.
However, I assume this method will not work in the long run, as Stripe will likely detect that the .dev website is only a mirror.
Is there any guidance on a cleaner and “safer” approach (even though I know it’s never truly safe), considering that I’m using Xano as a backend (a no-code backend platform)?
Thanks and have a wonderful day