# How a freelancer collects payment without a payment gateway How a freelancer can accept payment with just a link, no merchant account or gateway, and how the client completes it simply. --- ## How a freelancer collects payment without a payment gateway Most freelancers assume that getting paid professionally requires merchant infrastructure — a Stripe account, a PayPal business profile, a payment gateway bolted onto an invoice tool. That assumption is wrong, and it costs money. There is a set of collection paths that require none of that machinery: no merchant account, no per-transaction card fees, no platform sitting between you and your client's bank. This article covers each of those paths in full — what they are, when they work, when they fail, and how to set them up so your client can complete a payment without friction. ## Why the gateway-free question matters A payment gateway is a piece of infrastructure built to handle card transactions. It authorizes the card, routes the funds through a processor, and delivers them to your account — usually two to three business days later, minus a processing percentage and a fixed per-transaction fee. Stripe's online payment fee runs at 2.9% plus $0.30 per transaction. On a $5,000 invoice, that is $175.30 gone before the money lands. On a $15,000 project — not unusual for a senior developer, consultant, or creative director — the fee exceeds $435. Over a year of steady billing, that is a new laptop or two, handed to a payment processor for work it completed in milliseconds. Late payments are the single biggest financial threat to freelancers worldwide, and 85% of freelancers have their invoices paid late at least some of the time. The Freelancer's Union reports that unpaid freelancers are owed $6,000 on average, and 71% of freelancers have experienced a stalled payment at least once. Those numbers describe a profession where money moves slowly and unpredictably — which makes the choice of collection method a real business decision, not an administrative detail. The gateway-free alternatives fall into three distinct categories: traditional bank-to-bank transfers, peer-to-peer payment rails, and direct onchain transfers using stablecoins. Each has a different cost structure, a different client experience, and a different threshold where it works cleanly versus where it introduces friction. ## Bank transfers: the baseline The simplest gateway-free method is a direct bank transfer. You give your client your routing number and account number — or your IBAN and BIC if the payment crosses a border — and they initiate a transfer from their own bank. No third-party platform touches the transaction. No merchant account is required. Bank transfers are among the most secure and reliable payment methods, especially for recurring payments. Domestic transfers are usually free or come with minimal fees, and since payments go directly from one bank to another, there is no need to deal with third-party platforms. ### ACH for domestic US work ACH stands for Automated Clearing House. It is the electronic network that powers most bank-to-bank transfers within the United States and is commonly used for direct deposits, payroll, bill payments, and business-to-contractor payments. ACH transfers are typically free or very low-cost for the sender and are usually completed within one to three days. They require no SWIFT code or complex international banking details — just a routing number and account number. For a freelancer working with domestic clients — a strategist based in Chicago invoicing a Chicago-area company, a copywriter invoicing an agency with a US bank account — ACH is the most cost-effective collection method that exists. If both you and your client are in the US, ACH transfers are fast, secure, and low-cost. How it works: you give your bank account info to the client and the client pays with a transfer directly into your account. No platform fee. No percentage withheld. The only variable is timing: ACH settles in one to three business days, not instantly, which matters if you are working against a cash flow deadline. The limitation of ACH is geographic. For an ACH payment to work, both banks need to be on the ACH network. This means you will not be able to use ACH if the freelancer is outside the United States or uses a bank that is not on the ACH network. The moment your client is in another country, ACH disappears as an option. ### Wire transfers for larger or cross-border payments A wire transfer operates on international banking networks — primarily SWIFT — and can move money across borders between almost any two banks in the world. Wire transfers work similarly to ACH in that a transfer is submitted to a network that clears out transactions in batches. However, wire transfers use an international network of banks and financial institutions, which brings higher costs and longer processing times. International wire transfers typically cost $25–$50 from the sender's bank, with additional intermediary bank fees of $15–$30 per hop and receiving bank fees of $10–$25. A single payment to a freelancer in a different country can easily cost $75–$100 in combined fees. That cost structure is acceptable on a $20,000 engagement. It is punishing on a $1,500 invoice. Wire transfers occupy a specific niche: large, infrequent cross-border payments where the fixed fee is small relative to the invoice amount, and where both parties have traditional banking infrastructure. SWIFT transfers take three to five business days as a baseline, but the actual timeline depends on how many intermediary banks are involved, whether any compliance reviews are triggered along the way, and whether the transfer crosses a weekend or banking holiday. For a freelancer who needs to know when the money will land — and most do — that unpredictability is a real operational problem. ## Peer-to-peer rails: Zelle, Wise, and the middle ground Between a full payment gateway and a raw bank transfer, there is a set of platforms that route bank-to-bank payments without charging merchant account fees or card-processing percentages. These are worth separating from both gateways and from traditional bank wires because their cost structure and client experience are meaningfully different. ### Zelle for zero-fee domestic transfers Zelle is built into most major US bank apps and transfers money between enrolled bank accounts in minutes with no fee for either party. For paying domestic freelancers, direct bank deposit or Zelle are cost-effective options. If your client is at Bank of America, Chase, Wells Fargo, or any of the major US banks, they can send a Zelle payment directly from their banking app to your email address or phone number. Funds arrive within minutes, not days. For smaller invoices — a logo package at $800, a consulting session at $350 — Zelle is effectively free money movement. The constraints are real. Zelle imposes sending limits. Many bank accounts cap Zelle sends at $500 to $2,500 per day, and business accounts vary widely. If your invoice is $6,000, your client may need to split the payment across multiple days unless they have a business account with a higher limit. Confirm the limit before you invoice. Also confirm that your client's bank participates — Zelle enrollment is voluntary, and some smaller credit unions have not joined the network. ### Wise for international work at transparent cost Wise (formerly TransferWise) is not a payment gateway. It does not require a merchant account. It routes international payments through local banking rails in each country, which lets it avoid SWIFT fees and offer real mid-market exchange rates with a transparent, published margin. For paying international freelancers, Payoneer and Wise reduce currency conversion costs. For a freelancer in Berlin billing a client in Toronto, a Wise transfer is structurally simpler and cheaper than a bank wire while still being a gateway-free collection method from the perspective of merchant infrastructure. The client pays in their local currency. Wise converts at the live rate and deposits the agreed amount in the freelancer's Wise account or linked bank. No card processing. No merchant category code. No chargeback exposure. The practical setup: open a Wise account, get your local receiving details in the currencies your clients use (USD routing/account, EUR IBAN, GBP sort code), and include those details on your invoices. The client makes a bank transfer to what appears to be a local account in their country. The rise of virtual bank accounts has made it possible for freelancers globally to access payments without requiring local residency. These accounts provide routing and account numbers, and when you share them with your US clients or platforms, to them it appears as a regular domestic transfer. ## Stablecoins: the no-gateway path for digital-native clients The conversation about gateway-free payments has shifted materially with the adoption of stablecoins — dollar-pegged digital currencies that move on public blockchains in minutes, at near-zero cost, to any wallet address in the world. ### What a stablecoin actually is, for this purpose A stablecoin is a cryptocurrency designed to hold a fixed value relative to a reference currency — usually the US dollar. USDC, issued by Circle, is backed one-to-one by cash and short-term US Treasury assets, with publicly published monthly reserve attestations. USDT, issued by Tether, has the highest daily trading volume of any stablecoin and dominates payment flows in Asian and emerging-market contexts. Getting paid in USDC or USDT used to require both parties to be crypto-native. That has changed as stablecoins have become more useful for everyday money movement, especially for cross-border work, freelance payments, and dollar-denominated income. The operational basics are simple: your client sends a specified amount of USDC or USDT from their wallet to your wallet address. The transaction settles on-chain in minutes. You see the funds. The payment is final. ### Why it qualifies as gateway-free There is no merchant account here. No payment processor authorizes the transaction. No platform holds the funds in transit. All a recipient needs to receive crypto is a wallet — available as a free mobile app on iOS or Android, or as a desktop application. No bank account required, no SWIFT code, no approval process from a financial institution. The cost structure is radically different from card processing. If a client in Berlin pays $3,000 for a brand redesign, by the time PayPal takes its cut and converts EUR to USD, you receive $2,820. Wire transfers are worse — $25–$50 in bank fees, a 1–3% FX spread, and three to five business days before the money lands. A direct USDC transfer on a low-fee network costs under a dollar in network fees, regardless of the invoice amount. ### The mechanics of receiving a stablecoin payment Freelancers can receive USDT or USDC by agreeing on the stablecoin token, specifying an exact blockchain network, sharing a wallet address that supports that network, and requesting a small test payment before the full transfer. The network specification is critical and where most errors occur. USDT and USDC are not interchangeable. The token, the network, and the wallet address all have to match. The network is where most stablecoin payments go wrong. USDC on Ethereum, USDC on Base, USDC on Polygon, and USDC on Solana all use different technical standards. If a client sends USDC on Ethereum to an address you provided expecting Solana-based USDC, the funds go to the correct-looking address on the wrong chain and may be inaccessible. Always specify: "Please send USDC on [network name]" — and confirm with a test transaction for any new client. The entire process — from client sending to you holding local currency — typically takes fifteen to sixty minutes, compared to three to five business days with traditional methods. ### Which clients will pay this way The honest answer is: fewer than with bank transfer, but more than most freelancers expect. USDC is increasingly the preferred stablecoin in formal business payments, compliance-aware workflows, and any context touching US regulation. US tech startups, digital agencies, crypto-native companies, and remote-first businesses often hold stablecoin treasury balances and can pay out directly. The biggest barrier to getting paid in crypto is not technology — it is communication. Most clients are willing to pay in stablecoins once they understand the process is simpler than a wire transfer. Frame it around their benefit: paying in USDC skips the $30–$50 bank fee and settles in minutes. Finance teams respond to concrete numbers. Freelancers who position crypto as a mutual cost reduction — not a personal preference — report higher acceptance rates. ### Tax and recordkeeping Receiving a stablecoin payment is a taxable event in most jurisdictions. When you receive USDT or USDC for freelance work, the value in your local currency at that moment is your taxable income — whether or not you convert to fiat. Track every payment: date, amount in crypto, value in local currency, client name, and invoice reference. This is your audit trail. The blockchain provides a transaction hash that serves as immutable proof of payment — more auditable than a bank statement entry, in fact. ## When split payments land: multiple parties, one transaction Most freelance engagements are single-party — one freelancer collects the full invoice amount. But there is a growing class of work that involves splits: a design lead who brought in a developer, a consultant on a revenue-share arrangement, a creative director working alongside an editor. The traditional approach is sequential: the primary party receives the full amount and manually transfers the other party's share. This creates lag, creates liability for the primary party as a fund holder, and creates opacity. The cleaner path is to route the payment so all parties receive their share simultaneously, in one transaction. That is what Shaka is built for. A freelancer or small team closes a deal and creates a payment link that specifies each wallet address and its percentage. When the client pays, funds move directly to each recipient. There is no holding step, no manual transfer, no one waiting on someone else to send their share. ## Choosing between methods: the real decision tree The choice of gateway-free collection method is not an abstract preference — it follows a practical logic based on client location, invoice size, and client sophistication. For domestic US clients on invoices of any size, ACH is the primary recommendation. It costs nothing, it is familiar to corporate accounts payable departments, and it does not require the client to adopt any new platform. The only downside is settlement time: one to three business days. If you need same-day availability, Zelle works for smaller invoices with clients at major US banks. For international clients with invoices above $10,000, a wire transfer becomes acceptable because the fixed fee of $50–$100 is small relative to the invoice amount, and both parties understand wire mechanics. For invoices below that threshold, Wise is typically the better option — lower cost, faster settlement, and simpler to initiate on the client side. For international clients who are tech-forward or already crypto-literate, USDC or USDT on a low-fee network (Base, Polygon, Tron for USDT) is the cheapest and fastest available path. The client experience is a wallet transfer, not a bank login sequence. Every extra step between opening an invoice and completing payment increases the chance the client postpones. This is the operational argument for matching your collection method to your client's existing behavior — not your preference. A Fortune 500 accounts payable department will initiate an ACH transfer by uploading a remittance file. A startup founder will send a Zelle or a stablecoin transfer from their phone in two minutes. Know your client. ## The friction that causes late payment Most late freelance payments are not caused by clients refusing to pay. They happen because of structural problems in how invoices are sent, received, and processed. The most common cause is administrative friction. An invoice arrives in a client's inbox, sits unread for three days, gets buried under forty other emails, and by the time the client finds it again, the due date has passed. Every extra step between opening an invoice and completing payment increases the chance the client postpones. Accepting multiple payment methods — credit card, bank transfer, and payment links — and embedding the payment link directly in the invoice so the client can pay in one click reduces this friction significantly. Clients who have to manually set up a bank transfer or mail a check are statistically more likely to delay payment than those who click a link and enter a card number. The way to reconcile "gateway-free" with "low friction" is not to force the client through an unfamiliar process. It is to make your preferred no-gateway method feel as simple as clicking a link. For ACH and wire, that means your invoice contains the exact banking details in a clearly labeled box — nothing the client has to look up. For stablecoins, it means including a QR code for your wallet address alongside the chain specification. According to research, 61% of late payments result directly from invoice errors. This means most late payment is preventable simply by sending a complete, accurate invoice every time. ## What you still need to handle yourself Eliminating a payment gateway removes infrastructure, but it does not remove all payment-related work. Four things remain on your plate. **Proof of payment.** A gateway sends you a notification when a card clears. Without one, your confirmation comes from your bank (ACH and wire), your Zelle app, your Wise dashboard, or your blockchain explorer (stablecoins). Build the habit of checking confirmation before releasing final deliverables. **Reconciliation.** When a payment arrives without connecting to the invoice or project it belongs to, revenue leaks. Without a platform that auto-matches payment to invoice, you are manually doing that reconciliation. Use a naming convention — every transfer description should reference the invoice number — and enforce it on your clients. **Tax documentation.** For US-based freelancers collecting from domestic clients, collecting a W-9 before the first payment is required; for international clients, a W-8BEN. Regardless of payment method, always collect the appropriate tax forms before paying or being paid. Gateway platforms often prompt this. Without one, you are entirely responsible for collecting and retaining that documentation. **Currency risk.** If you invoice in USD but collect from clients who pay in EUR or GBP, the exchange rate between invoice date and payment date can move your effective rate by two to four percent. For small invoices, tolerable. For a $40,000 engagement, that is $800–$1,600. Either invoice in the client's currency and accept the FX exposure, or specify that USD amounts are due in USD regardless of conversion timing. ## The practical setup A freelancer who wants to collect without any payment gateway needs three things: a business bank account with a routing number and account number clearly identified, a Wise or equivalent multi-currency account if they work with international clients, and — for digital-native clients — a self-custody or exchange-based wallet capable of receiving USDC. The invoice itself should list payment options by method, with all necessary details inline. Not "bank transfer available on request" — that requires a follow-up. The routing number, account number, and bank name go on the invoice. The Wise IBAN or US receiving details go on the invoice. The wallet address and chain specification go on the invoice. The client opens the invoice once and has everything they need to pay immediately. That is the entire infrastructure. No merchant application. No approval from a payment processor. No PCI compliance questionnaire. No per-transaction fee withheld before money reaches your account. What it does require is that you understand which clients will default to which method, that you have confirmed your banking details are accurate before sending a single invoice, and that you track payment status yourself rather than relying on a platform to alert you. These are not burdens — they are the administrative cost of keeping 2–3% of every invoice that would otherwise flow to a payment processor. The freelancers who treat payment collection as an afterthought — defaulting to whatever platform is easiest to set up — end up paying for that convenience on every invoice, forever. The ones who understand the mechanics collect the same money faster and keep more of it. Bank rails, peer-to-peer platforms, and direct onchain transfers each have a natural home based on client location, invoice size, and client behavior. Matching method to context is not sophisticated treasury work — it is the basic professional practice of someone who takes their own business as seriously as they take their client's work.