How to protect yourself from a payment fraud?

Question

Freelance

Good afternoon, life teaches nothing and I find myself in a situation when I upload a site to a client before paying (there was an advance payment).
How can you protect yourself from a kidk in the case when the site is on the client's host, and the client is not a complete fool, but does not really want to pay?
There is an option грузить скрипты и стили со своего хостингаand in which case, just cut them down. But the client knows this chip.
There is простой скрипт бэкдора,, but it is easy to calculate, I do not have enough skills to write something difficult.
What are the options? because if you stupidly delete the site, then it can be restored from the hosting backup.
PS I am considering the option so far with the client in normal relations and I haveвсе доступы.

Answer 1

To protect yourself from such problems, you need to follow some rules.
1. Never give the source before payment. This also means that never work or upload to a customer's hosting without payment.
2. From the point above it follows - always work on your dev server. And show results too only on it. If the customer does not agree - goodbye. The only thing you can give away almost for free is CSS, and if it has time, then layout. But this is the way for not lazy throwers. The test server is always protected by basic auth
JS, do not forget to minify, and not just to a string, but with the reduction of variables, etc.
3. Work only in your Git repository
4. Work through the contract. Open IP. 90% of scammers will be eliminated at the mention of this kind of relationship
5. Use a safe deal. Although there are options to be thrown
PS Sometimes there are cases when a client has a lot of pictures, for this you can use nginx proxy;)

Answer 2

Work through a guarantor