[anonym29]

The tricks are mostly proactive / strategic rather than reactive.

• Don't rely on platforms you have no control over in the first place. PayPal can close your PayPal account, but nobody can close your self-custody Bitcoin wallet. Self-ownership comes with some risks, but it negates some others. The solution is to use both (and others), which brings us to our next point -

• If you must use some platforms you have no control over, have functionality redundancies in place with other providers, to eliminate single points of failure. You can encourage customers to use alternative payment mechanisms by offering price incentives to lesser utilized mechanisms. Obviously you don't want to lose too much money, but there is a case to be made that getting 100% of your potential profit, but getting it from one payment provider is riskier than getting 90% of your potential profit, split across two payment providers. This works for ad buys too, rather than just receiving revenue.

As far as reactive techniques go, getting in contact with customer service and saying your account was hijacked because your computer got hacked and you had your password saved can be effective if there was a specific behavior/condition you are confident that caused the ban, which you are also confident you can avoid in the future. This excuse is particularly good because it offers an explanation not only for the behavior, but also for almost all of the metrics/identifiers that would be used to validate it was you - IP address, useragent, etc.

[simfree]

To add to this, using hidden points of escalation are one of the few ways you have for appealing bans or restrictions from platforms that you can't avoid.

Stripe

- Comment on one of the Stripe founders threads with your issue, email them too

- Make a well written HN post about your Stripe issue at the right time of day and share it with your friends

Google

- Have Googlers you know file an internal ticket on your behalf

- LinkedIn search Google employees and email them (first & last name @google.com iirc). Poke enough employees with a positively written ask for help and they might file a ticket

- If your domain gets flagged by Google Safe Browsing, remove all outdated DNS entries and drop all traffic from Google's ASN on remaining servers, then have them rescan your domain in Google Search Console Tools.

Note that Google silently proxies any users that click through the Safe Browsing warning in Chrome, so blocking their ASN will break this workaround for Chrome users

[oska]

Your first two points are great.

However your third point advocates lying, which many great moral/religious thinkers have explicitly warned against, and for good reason (it rots the soul).