To give or not to give access to a client in git?

Question

git

We develop web and mobile applications. Usually we work according to the scheme - 33% prepayment, after the end of the project we take the rest of the money and give the application with all the sources.
During operation, the client always has access to the test server and to Fabric/Testflight/etc.
But now we are faced with a client who really wants to have constant access to git from the first days of the project development.
I understand that there is a fear that the sources will be leaked on the last day of the project and the remaining money will not be paid to us.
Do you give access to working repositories to clients? If so, how do you negotiate?

Answer 1

I give readonly access to turnips only if the client is verified or in case of full prepayment. In other cases, I do not give in mind the reasons you described.
If you work in stages with a separate payment for each stage, then you can do this: start a separate branch and give access to it. And merge a new code into it after payment. It turns out that the client fixed, say, a personal account - they merged it into this thread. And so for each iteration.
Full access, I would beware of giving.

Answer 2

But now we are faced with a client who really wants to have constant access to git from the first days of the project development.

Negotiate 100% advance payment.

Answer 3

No.
But if you really want to, let him pay in stages, for each major commit.

Answer 4

if you have a payment trust issue, then it is logical to suggest that the client give the client full access to the git and ask for more upfront payment or full upfront payment.