In this article
The payment methods a freelancer can offer fall into ten families: a domestic bank transfer, an international wire, a multi-currency account with local account details, a card payment through an invoicing tool or processor, a digital wallet, a freelance marketplace's payment system, a direct debit, a cheque, a stablecoin payment to your own wallet, and an onchain payment router. No single one is best for every invoice: the criterion that separates them is who starts the payment, because a payment the client pushes from their own account is cheap and hard to take back, while a payment pulled from a card or an account is easier for the client and stays open to a reversal for weeks or months.
For most freelancers the answer is therefore a pair, not a single method: a pushed bank payment as the default, because it costs the least and settles for good, and one fallback chosen for the client in front of you. Which fallback depends on four things, and the rest of this article compares every family on them: how long until the money is usable, how the cost is charged, whether the client can reverse it, and which clients can actually use it.
Payment rules, fees and time limits vary by country, by bank and by provider. The rules quoted here come from the published sources named in each sentence, and every fee in the worked example is an illustrative assumption, not a quote. This is general information, not legal or tax advice.
Figures from the World Bank's Remittance Prices Worldwide report and the European Payments Council. The World Bank figure measures small personal transfers, not business invoices; it is discussed in the section on cost.
Which payment methods can a freelancer offer, and how do they compare?
A freelancer can offer ten families of payment method, and they differ most on three points a client never sees: the delay before the money is usable, the way the cost is charged, and the range of clients able to pay that way. The table below applies the same three criteria to each family; the right to reverse and the paperwork are compared in the next section.
| Method | Time until the money is usable | How the cost is charged | Which clients can use it |
|---|---|---|---|
| Domestic bank transfer | Seconds on an instant scheme; otherwise the same day to a few banking days | Usually nothing or a small flat fee | Any client with a bank account in your country |
| International wire | One to several banking days | Flat fees at each bank, plus an exchange-rate margin when currencies differ | Any client with a bank account, in almost any country |
| Multi-currency account with local details | As fast as a domestic transfer in the client's country, then a conversion | A percentage on conversion; receiving is often free | Clients in the countries where the account gives local details |
| Card through an invoicing tool or processor | A payout delay of a few days after the client pays | A percentage plus a flat fee per payment; more on foreign cards | Any client with a card, consumer or business |
| Digital wallet or online payment account | Balance visible at once; withdrawal to a bank takes longer | A percentage, plus a conversion margin across currencies | Clients who hold, or agree to open, the same kind of account |
| Freelance marketplace's payment system | After the marketplace's review or security period | A service fee as a percentage of the invoice | Clients who hire through that marketplace |
| Direct debit for retainers | A few banking days after each collection | A small percentage or flat fee per collection | Clients in the same debit scheme who sign a mandate |
| Cheque | Days to clear; longer if the bank places a hold | Usually nothing, apart from your time | Clients in countries where cheques are still in use |
| Stablecoin to your own wallet | Minutes once the transaction confirms | A network fee for the sender; a conversion cost if you move to a bank | Clients who already hold stablecoins |
| Onchain payment router | Minutes, for every party at the same moment | Set by the router; a conversion cost if you move to a bank | Clients able to pay onchain; useful when the invoice is shared |
The methods at the top of the table are bank-to-bank and cost little, but they ask the client to do the work of setting you up as a payee. The methods in the middle take that work away from the client and charge you a percentage for it.
Can the client reverse the payment, and what does each method ask of the client?
A client can reverse a card payment, a wallet payment and a direct debit through their own bank or provider, and cannot reverse a bank transfer, a wire or a confirmed onchain payment on their own. The methods that ask the least of the client are, with few exceptions, the ones that leave you exposed longest.
| Method | Can the client reverse it? | What the client must do | Record you keep |
|---|---|---|---|
| Domestic bank transfer | Not by request; only for error or fraud, through the banks | Add you as a payee, type your account details | Bank statement line with the client's reference |
| International wire | Not by request; recalls need your bank's cooperation | Enter international account details, often approve in two steps | Wire advice and statement line |
| Multi-currency account with local details | Same as a local transfer in the client's country | Pay a local account, as they would a domestic supplier | Statement in each currency, with conversion shown |
| Card through an invoicing tool or processor | Yes, by a dispute with the card issuer, for months | Click a pay button, enter a card | Processor report: gross, fee, payout |
| Digital wallet or online payment account | Yes, through the provider's dispute process or the card behind it | Log in and approve | Transaction history and fee statement |
| Freelance marketplace's payment system | Disputes run through the marketplace's own process | Fund the contract or milestone on the platform | Platform earnings report |
| Direct debit for retainers | Yes, under the scheme's refund rules | Sign a mandate once | Mandate, plus a collection report |
| Cheque | Yes, by a stop order, and it can fail on presentation | Write and post it | Deposit slip and a copy of the cheque |
| Stablecoin to your own wallet | No; some stablecoin issuers can freeze an address | Send to your address on the agreed network | Transaction record onchain, plus your own invoice |
| Onchain payment router | No; the same issuer freeze applies to some stablecoins | Pay once through a payment link | Onchain record of who was paid what |
The reversal windows are set by each system's rulebook. On a consumer SEPA direct debit, the European Payments Council states that the payer can ask for a refund during eight weeks without giving any justification, and up to 13 months for a debit that was not authorised; under the business-to-business version of the scheme, the payer is not entitled to a refund of an authorised transaction. In the United States, Nacha's operating rules give a bank two banking days to return a debit to a business account and 60 calendar days when a consumer reports a debit as unauthorised. Card disputes are governed by each card network's rules and typically stay open for several months.
For a freelancer, the practical meaning is short: with a card, a wallet or a direct debit, the money in your account after delivery stays conditional for the length of that window, and the amount at stake is the full invoice.
How fast does each payment method put usable money in your account?
The fastest methods are an instant bank transfer and a confirmed onchain payment, both usable within seconds or minutes; the slowest are a cheque and any method that holds your balance for review before releasing it. Speed has two parts: the time the client takes to start the payment, and the time the method takes to finish it.
The second part is the only one the method controls. On a domestic instant scheme it is close to zero: the European Payments Council states that a SEPA Instant Credit Transfer makes the funds available in less than ten seconds, 24 hours a day and on all calendar days of the year. Where the client's bank sends an ordinary transfer instead, the funds follow that country's clearing cycle, from the same day to a few banking days.
Card payments, digital wallets and marketplaces show a different pattern: the payment appears at once, and the money is yours to use later. A processor pays out on a schedule, a wallet balance needs a second step to reach your bank, and a marketplace releases earnings after its review period.
A cheque is slow at both ends: it travels by post, then the bank clears it, and funds shown as available can still be taken back if the cheque is later returned unpaid.
The first part, the time the client takes to start, is where the easy methods earn their fee: a client who can pay by card from the invoice often pays the same day, while a large company pays on its next payment run, whatever the method could do.
What does each payment method cost a freelancer?
A payment method costs a freelancer in one of three ways: a flat fee per payment, a percentage of the invoice, or a margin hidden in an exchange rate. Flat fees weigh on small invoices, percentages on large ones, and the exchange-rate margin appears on no fee line.
A flat fee is typical of bank rails: a wire may carry a sending fee, a deduction by an intermediary bank and a receiving fee at your bank. A percentage is typical of cards, wallets and marketplaces; it pays for the client's convenience and for the risk the provider carries, and it grows with the invoice without limit.
An exchange-rate margin applies whenever the client pays in one currency and you are paid in another. The provider that converts applies its own rate, and the gap between that rate and the mid-market rate is a cost that behaves like a percentage.
The most detailed public data on cross-border cost is the World Bank's Remittance Prices Worldwide data, with one caution: it measures small personal transfers, not business invoices. In its report for the first quarter of 2025, the global average cost of sending $200 was 6.49%, which is $12.98, and the average for sending $500 was 4.26%, which is $21.30. The same report recorded an average of 14.55% for banks against 5.04% for money transfer operators, and 4.85% for digital remittances against 7.16% for non-digital ones. Those averages are not a price for your invoice, but they show that the cost as a share falls as the amount rises, and that the kind of provider carrying the money changes the cost several times over.
Who pays is negotiable. On a wire, the sender chooses whether fees are shared or borne by one side, so state on the invoice that the amount is due net of bank charges. On a card, rules on passing the fee to the client as a surcharge vary by country and by card network, so check before adding one.
What does a freelancer net on a $2,000 domestic invoice and an $8,000 cross-border invoice?
On a $2,000 domestic invoice, a freelancer nets between $1,800.00 and $2,000.00 depending on the method, and on an $8,000 cross-border invoice between $7,200.00 and $7,960.00, under the illustrative fee assumptions set out below. The assumptions are invented to show how each cost structure behaves; your own bank's and provider's price lists are the only figures that count.
The worked example takes one freelancer and two invoices. The first, $2,000, goes to a client in the same country and currency. The second, $8,000, goes to a client abroad who pays in their own currency, and the freelancer wants the money in a home bank account.
| Method | Illustrative assumption | $2,000 domestic: fee, then net | $8,000 cross-border: fee |
|---|---|---|---|
| Bank transfer, or international wire | Domestic: no fee. Cross-border: $35 in flat bank fees plus a 2.5% exchange-rate margin | $0.00, net $2,000.00 | $235.00 |
| Multi-currency account with local details | Receiving free; 0.6% on conversion | $0.00, net $2,000.00 | $48.00 |
| Card through an invoicing tool | 2.9% plus $0.30; on a foreign card, 1.5% more plus 1% conversion | $58.30, net $1,941.70 | $432.30 |
| Digital wallet | 3.5% plus $0.50; cross-border, 1.5% more plus a 3% conversion margin | $70.50, net $1,929.50 | $640.50 |
| Freelance marketplace | 10% service fee on the invoice | $200.00, net $1,800.00 | $800.00 |
| Stablecoin to your own wallet | Received in full; 0.5% to convert and withdraw to a bank | $10.00, net $1,990.00 | $40.00 |
The domestic column shows why a bank transfer is the usual default at home: the card costs $58.30 for the same $2,000. The cross-border column changes the order, and the chart shows what is left of the $8,000 under each method.
Worked example with invented fee assumptions, not market prices. Not included: the cost of a reversal, the marketplace's value in finding the client, tax, and any change in the stablecoin's value before conversion.
Three readings matter more than the ranking. First, the gap between the wire and the multi-currency account, $187.00 on this invoice, comes almost entirely from the exchange-rate margin: where the conversion happens is the main cost decision on a cross-border invoice. Second, the percentage methods cost more abroad than at home because three percentages stack: the base rate, a cross-border surcharge and the conversion. Third, the marketplace's $800.00 is not a payment cost alone: a marketplace also finds the client, holds the client's funds before work starts and handles disputes, so the fair question is whether you would have had that client without it.
Where does each family of payment method stop?
Every family of payment method stops somewhere: bank rails stop at the client's willingness to set up a payee, percentage methods stop at invoice size, and onchain methods stop at the client's ability to pay that way.
- Domestic bank transfer. Does well: cost, finality, a clean statement line. Stops: at the border, and with clients who want to pay in one click. Suits most local invoices of any size.
- International wire. Does well: reach and large amounts. Stops: on small invoices, where flat fees weigh heavily, and on conversion, where the margin is rarely shown. Suits large invoices and finance teams that pay only by wire.
- Multi-currency account with local details. Does well: the client pays a local account, and you choose when to convert. Stops: at the countries and currencies the account covers, and at procurement systems that must match the account holder's name and country exactly. Suits repeat clients in major currencies.
- Card through an invoicing tool or processor. Does well: the least effort for the client, and reach to consumers. Stops: at the percentage on large invoices and at the dispute window. Suits small or urgent invoices and deposits.
- Digital wallet or online payment account. Does well: speed between two account holders. Stops: at conversion cost, withdrawal delays and larger companies that do not pay suppliers from a wallet. Suits small cross-border jobs for individuals and very small businesses.
- Freelance marketplace's payment system. Does well: the client's funds are committed before work starts, and a process exists for disagreements. Stops: at the service fee and the platform's rules. Suits client relationships found on the platform.
- Direct debit. Does well: a retainer collected on a fixed date without chasing. Stops: at one-off invoices, clients outside the scheme, and the refund right described earlier. Suits a monthly retainer with an established local client.
- Cheque. Does well: it needs no account details from you. Stops: at speed, at the risk of a returned cheque and at borders. Suits a client whose process leaves no alternative.
- Stablecoin to your own wallet. Does well: the same speed and cost at home and abroad, with no payer-side reversal. Stops: at clients who hold no stablecoins, at the conversion step if you need bank money, and at record-keeping, since the wallet issues no statement. Suits clients that already run their treasury onchain.
The tenth family answers a different question, and has its own section.
When does an onchain payment router fit, and when does it not?
An onchain payment router fits when one invoice is shared between several parties, such as a lead freelancer, a subcontractor and a referrer, and each must be paid their share from the client's single payment. It does not fit a solo invoice, where there is nothing to route.
Every other method in this article pays one recipient, who then makes onward transfers to collaborators. A payment router removes that second step: the client's one payment is divided at the moment it is made.
Shaka is one such router. Each party's share is set as a percentage of the deal, and each recipient can sign their share before the client pays, at no cost to them. The client pays once, through a payment link, and every party is paid at the same moment, in one transaction. Shaka routes the payment and never holds the funds. The destinations are fixed and signed before the payment, so the money cannot be redirected at the last minute. The payment is onchain and final, each party can see that the others were paid, and a payment record can be kept for the file. A deal has at most 20 recipients.
A short illustration: a $12,000 project shared 60% to the lead freelancer, 30% to a developer and 10% to the person who referred the client. With a bank transfer, the lead receives $12,000 and later sends $3,600 and $1,200 in two further payments. Through a router, the client's single payment arrives as $7,200, $3,600 and $1,200 at the same moment.
Where it does not fit: the client must be able to pay onchain, which rules out many local small businesses and most procurement departments. It is not an escrow service, so it does not hold a deposit pending approval of the work, and a final payment means any refund is a new payment agreed between the parties. For a solo invoice, a bank transfer or a direct stablecoin payment does the job with less setup.
How do you choose a default method and a fallback by client type?
Choose the default by cost and finality, and the fallback by what the client's own payment process allows: a bank transfer first for nearly every client, then the one alternative that removes that client's specific obstacle.
| Client type | Default | Fallback | Why |
|---|---|---|---|
| Local small business | Domestic bank transfer, instant where available | Card through the invoice | The owner pays personally; a card link gets a late invoice paid today |
| Large company with a procurement process | Bank transfer or wire to the account on your supplier form | None; fit their process | Their system pays registered bank details on a fixed run and little else |
| Client abroad | Multi-currency account with local details in their currency | International wire | Local details avoid wire fees; the wire covers countries the account does not |
| Client who wants to pay by card | Card through an invoicing tool | Bank transfer for larger invoices | Accept the fee on small amounts; set a ceiling above which you ask for a transfer |
| Startup that pays in stablecoin | Stablecoin to your own wallet | Bank transfer or wire | Agree the token and network in writing; keep a bank route in case their policy changes |
| Monthly retainer, local client | Direct debit | Standing order or scheduled transfer | Collection on a fixed date; the fallback puts the client in control if they prefer |
| Project shared with collaborators or a referrer | Bank transfer, then onward payments | An onchain payment router, if the client can pay onchain | One recipient is simplest; a router pays every share at once |
Two rules of thumb sit behind the table. Set a size ceiling for percentage methods: a card is a reasonable price for speed on a few hundred, and an expensive habit on tens of thousands. And for a large company, ask for the supplier onboarding form at the start of the engagement: their payment method is whatever that form says.
The invoice amount can override the client type: for a first invoice to an unknown client paying by card or wallet, a deposit by bank transfer before work starts limits the amount exposed to a reversal.
How should you state accepted payment methods on an invoice?
State accepted payment methods on the invoice as a short ordered list: the default method first with every detail needed to pay it, the fallback second with its condition, and the reference rule once. A client who has to write back to ask how to pay has already lost a day.
A payment section that covers the usual questions contains the following.
- The default, complete. For a bank transfer: account holder name exactly as on the account, the account identifiers used in the client's country, the bank's name, and the currency. For an international wire, add the international account and bank identifiers.
- The fallback, with its condition. Sample wording: "Card payment is available through the pay button on this invoice for amounts up to $1,500." Or: "Payment in a stablecoin is accepted by prior agreement; the token, network and address are confirmed in writing before each payment."
- Who bears charges. Sample wording: "The amount due is net of bank charges; please send with all fees paid by the sender."
- The reference. Sample wording: "Quote the invoice number as the payment reference." This is what lets you match the statement line to the invoice.
- A fixed-details notice. Sample wording: "Our bank details do not change by email. Please confirm any change request by phone on the number in our contract."
Keep the same payment section on the contract or statement of work, so the method is agreed before the first invoice. Keep the matching record too: a statement line with the invoice number for a bank payment, the provider's report of gross, fee and payout for a card, wallet or marketplace, and the invoice with the transaction reference for an onchain payment.