How a freelancer in Syria records a Sham Cash deposit before starting
The deposit is a row: amount, wallet, transaction ID, and the job in one sentence. No ID, no start. A photo in the chat is not a payment.
A designer in Latakia started the logo because the client said "I sent it on Sham Cash." Two days later the transfer belonged to someone else with the same first name, or it was half the agreed sum because "the rest is after delivery" and that was never written down. The work was done. The argument was about the debt, not the color.
A freelancer who gets transfers does not need a store. They need one row before they open the design file or the repo.
The row before the file
Tell the client the amount, your account, and the deadline. They transfer. They send the transaction ID in the chat. You open Sham Cash, or Syriatel Cash if that is their wallet, and you check that the ID and the amount are on your account and were not already written against another job. Then you write a row: client name, the job in one sentence, the amount, the ID, the date. Then you open the file.
If the ID is missing, the reply is one sentence: "Send the ID from the transfer details." Do not start "just this once." That once is next week's pattern.
What the customer should send is the same key as in after a Syriatel Cash transfer. Sham Cash uses it too. If the deposits get dense and matching them by eye eats the evening, the account link is the Sham Cash API. Ten clients a month can still match by eye. Fifty payments cannot.
The second half after delivery
The second payment is a second row, not an edit of the first. "The remaining 40" disappears when the client does the math from memory. Write the second amount on the day you agree, before the design, in a message both of you can scroll back to. Hand over the open files after that row exists, or hand over a watermarked preview if you agreed the preview comes first. Do not send the source and then chase the transfer.
If a deposit has to be returned, the Arabic note I use is Sham Cash refunds and disputes. Say it before they transfer, in one line: the deposit is kept if they cancel after you opened the file, and returned if they cancel before that. A line written early is shorter than a fight a week later.
Your account, not a middleman's
The transfer lands on an account in your name. A person who "will pass you the money" puts a third party between the transaction ID and the job. If the amounts grow, that person becomes the ledger. I do not stand between a freelancer and their client on the payment. If you later want a page that lists the work and records the deposit, the page writes the same row. It does not change who owns the account.
Frequently asked questions
The client wants to pay Syriatel Cash and I only published Sham Cash.
Either you accept the second wallet and record it on the row, or you refuse before the work starts. Quiet acceptance, then "I couldn't" after the design, is a dispute waiting to happen.
The client is abroad and pays some other way.
Same row: amount, reference, date. The wallet name is a field, not an excuse to skip the rule.
Do I need a bot to get paid?
No. The table and the transaction ID are enough until the volume grows. A bot helps when the client already talks to you on Telegram and you want the ID requested inside the chat instead of in a manual message every time.