base

It's not a trick. What you receive as shipping or taxes on google shopping are not the final ones, google doesn't have your full address, neither doesn't have info from the merchant for all taxes (depends on the country) and shipping applied to the product to all possible locations.

The page needs some code examples. It's just marketing talk, needs to be more oriented to it's audience.

Akismet is a paid service and their apis are tailored for comments. An advantage with comments is that you can just mark as spam if some contents have dubious links or keywords.

An issue you have in many forms (e.g.: login form) is that there is limited data to decide if it's a real user or a bot.

That's what most big e-commerce websites already do. From the moment you have a login the content is personalised to you.

It's amazing the impact this had on the stock value of the company: +25% at the moment.

Depending on the app might not have better performance. The reason is that a host with more connections might not be using more resources than one with less connections. The busy connections might be waiting for a reply from an external service.

There a lot of ways to reduce, just some ideias: turn on 3dsecure authentication whenever available. Check user location vs card location. Validate cvc code and postal code. Check for user activity and user signals (user agent, screen size etc) on the website, and other methods.

Would be interesting to study if there is a correlation between layoffs and remote work and employee churn. It's easier to layoff people if you don't have a connection with them.

Better to correct the title. It's 10% of 7000.

With online payments I had a different experience. Tried to pay in a store that had coinbase payments with a binance account. So many issues:

- The QR code to pay didn't work with the binance app

- Had to find a way to copy the hash tag of the account from desktop to mobile to pay (luckily if you have a macbook pro and iphone this is easy)

- Initially chose the incorrect network for payments on binance so the transfer didn't go through. Had to read online which network to select.

With a card payment is normally just putting the cards details and in a few cases do an additional authentication.

They workout the issues like everyone else, and at a certain size the issue is minimized as you are either in several whitelists or human moderators recognise your domain.

Most of those services also let clients setup their own domain name, so a ban is a more of a inconvenience to deal, than business critical like in OP case.

I don't have a specific solution for you, but I also run a domain with some thousands of subdomains and is always a fight to not be banned from Google, Meta, internet operators etc. Sometimes is enough one bad actor under one of your subdomains to have a full ban on the whole domain.

What I suggest is for your and your clients to contact Meta through the Business Center support. Their support for paying clients is much better. I would also recommend you become a Meta Business Partner if Facebook/Instagram is important for your SaaS.