How Online Clients Actually Pay You

There are three ways money reaches a freelancer, and they protect completely different things. Choosing between them under time pressure, with a client waiting on an answer, is how people end up chasing money they already earned.

Set one up before you need it, and put something small through it first.

Escrow, direct transfer and card processors, side by side

Platform escrow works like this: the client funds the job into the platform before you start, the platform holds it, and it is released when the work is accepted. What you are buying is the knowledge that the money exists — a bigger deal than it sounds, because the failure that actually bites is not a client refusing to pay, it is a client who never had it. What it costs is a fee and some independence: the platform's rules govern any dispute, and protection stops at the platform's edge.

Direct bank transfer is the opposite trade. Nothing sits between you and the client, nothing is deducted by a third party, and nothing protects you either. There is no dispute process at all. It suits a client who has already paid you before.

A card or invoice-link processor sits in the middle. The client pays by card through a page you send, you get a receipt trail, and they get the convenience that makes people pay today. The cost is a fee plus a genuine exposure: card payments can be reversed after the fact, which for one person with no company behind them is a real risk rather than a theoretical one.

Small operators end up running two rails: a platform for new clients, a direct one for the clients who have proven themselves.

What holds your money, for how long, and why

Money stops moving for reasons, and the reasons are boring. New accounts get reviewed. First payments to a new recipient get held while identity and address are verified. Some services release nothing until the balance passes a minimum they set. Bank transfers settle on banking days, so a Friday evening payment is a Monday or Tuesday arrival.

None of it is negotiable by you, but you can find out in advance. Before the first real job, put a small amount through the entire rail — into the account, out to your bank — and watch where it pauses. That single test teaches you more than any support page, and it lets you tell a client honestly when money will reach you.

Deposits and milestones are protection, not a favor

A deposit does two jobs. It confirms the client can actually pay, which you cannot learn any other way, and it moves part of the risk off the end of the job, where all of it otherwise sits.

Ask as a standard term rather than a special request. "I take a deposit to start and the balance on delivery" is a sentence, not a negotiation.

Split longer jobs by deliverable, not by calendar. Each milestone should be a thing that exists and can be looked at — the draft, the cleaned file, the first section — so there is no argument about whether it was reached. Milestones tied to time invite a debate about how the time was spent.

Hold the final handover. Show the work, let them review it, and release the source files, passwords, raw exports and publish access when the final payment has settled. Not sent. Settled. The document that requests each of those payments is the invoice, and sending your first freelance invoice covers what goes on it.

Being paid from another country

Cross-border payment adds four things: a currency conversion at a rate somebody else chooses, an intermediary bank that may take a cut nobody itemizes, extra verification because international payments to a new recipient attract it, and a question about who absorbs the cost.

Settle that last one in writing before you start. The sentence is: which currency am I invoiced and paid in, and who covers the conversion and transfer charges? Silence means you cover them, and you find out when the amount landing is smaller than the amount agreed.

There may also be forms. Some clients need a tax declaration before their finance system can pay a foreign supplier, and some countries withhold at source. Ask the client's finance contact what they need from you, and a local tax adviser or your national revenue service what applies to you.

Give complete details the first time: account name exactly as the bank holds it, the international codes, your address as registered. A rejected transfer restarts the wait.

The payment record you will need later

Keep one running list of money in: date received, who from, which job, which rail, the reference the payment carried, and the amount. A spreadsheet is enough. Start it at the first payment, because reconstructing it later from bank statements is a day you will not enjoy.

Keep the evidence with it: the payout confirmation, the remittance advice, the platform statement.

You will need this in three situations. Tax, in whatever form applies where you live. Chasing, because the first question is always what was agreed and what has arrived. And proof of income for a rental application, a phone contract or a loan, where self-employed people get asked for a history they never kept — building credit from nothing picks up that thread.

A separate account helps more than it costs, even if it is just a second free current account used only for client money.

Payment arrangements to refuse

Any arrangement where money leaves you first. A fee to release your earnings, a fee to unlock a higher payout tier, software bought from the client, paying for your own background check to the person hiring you. There is no version of client work where you fund the start.

Overpayment. The client sends more than agreed and asks you to return the difference, or forward it to a supplier. The original payment is the part that reverses later. Refuse the whole thing: return nothing, forward nothing, and say the payment must be corrected at source. This pattern and its relatives are set out in spotting a side hustle scam.

Being a link in somebody else's payment chain: receiving money for a third party, taking payment on behalf of another business, moving funds that are not yours through your personal account. Whatever the story, the consequences land on the account holder, and that is you.

And the small one: a client who insists on a rail that leaves no record, for a job with no written scope. If the money never arrives, what to do when a freelance client will not pay is the next step, and every option in it works better where there is a record.

Pick your rail this week, run a small payment through it end to end, and write the details somewhere you can copy them from when a client asks.