# How a consultant collects a large project fee without a payment gateway A case study of a consultant navigating the real cost and risk of collecting a six-figure project fee without a payment gateway that takes a percentage, imposes limits, or reverses the payment. --- ## How a consultant collects a large project fee without a payment gateway Six figures. Delivered. Signed off. The client has approved every milestone, the final report is in their inbox, and the relationship is good. The only remaining question — the one that should be the simplest — is how the money gets from their account to yours. It is at precisely this moment, when everything else has gone right, that the infrastructure of professional payment shows its most embarrassing limitations. The wire might arrive short. The gateway might flag the amount. The card payment, collected and sitting in your account, might be reversed thirty days later when a client decides the scope was "unclear." The problem is not the client. The problem is the system every consultant defaults to — a system designed for retail transactions, not for professional services work worth five or six figures. This is the story of one such consultant, and what it actually costs to get paid. ## The Situation The consultant — call him M. — operates a two-person advisory practice. His firm does operational restructuring work for mid-market companies: process analysis, team structure, executive alignment. Engagements run between three and eight months. Fees are negotiated on a project basis, not hourly, and final invoices frequently land in the $80,000 to $150,000 range. M. has no payment infrastructure problem on small invoices. A $12,000 deposit clears a bank transfer in two days and no one thinks twice about it. But when the final invoice arrives — say, $95,000 on a completed engagement — the question of how to collect it becomes its own project. He has tried every available option. He has learned, at real cost, what each of them actually means at this scale. ## The Gateway Default — and What It Actually Costs The first instinct for most consultants entering the digital economy is to reach for a payment gateway. Stripe, PayPal, a platform-specific invoicing tool. The logic is clean: send a link, client pays, money arrives. Simple. Payment gateways typically include a per-transaction fee around 1.5% to 3.5% plus a small fixed charge, along with extra fees for chargebacks, cross-border payments, and currency conversion. On a $95,000 invoice, that is not a rounding error. Stripe, for example, charges 2.9% plus $0.30 in the US. At that rate, the gateway extracts roughly $2,755 from a single payment — for what, precisely? For routing a number between two bank accounts. The consultant did not negotiate this. The client did not see it. It simply left. That is the visible cost. The invisible one is more dangerous. The cardholder contacts their issuing bank to dispute a charge instead of asking for a refund directly. The bank assigns a reason code, reverses the funds, and notifies the payment processor. The money leaves your account — often before you even know a dispute exists. For M., this is not a theoretical scenario. Three months after completing a restructuring engagement, he received a chargeback notification on a $40,000 payment he had collected via gateway. The client — not acting in obvious bad faith, but facing internal pressure from a board that had not approved the engagement terms — told their bank the charge was unauthorized. Sometimes clients file chargebacks when they feel they've received inadequate work; other times the freelancer hasn't done anything wrong and the client is trying to get out of paying for the services they requested and received. The bank rules for you or the customer usually within 60 to 90 days. M. spent six weeks gathering email records, signed statements of work, and approval confirmations. He won the dispute. He also lost six weeks of operational focus, and the relationship with that client was irreparably damaged. Processors track your chargeback ratio, and too many disputes can result in your account being frozen or closed. For a practice collecting $400,000 a year in project fees, a frozen processor account is not an inconvenience. It is an existential risk. The gateway is, for high-value consulting work, the wrong tool entirely. It was designed for retail. It treats a $95,000 professional services invoice the same way it treats a $95 software subscription. The risk models are identical. The protections are not. ## The Wire Transfer Alternative — Friction, Float, and the Hidden Costs M. shifted his default to wire transfers after the chargeback experience. Wire transfers are bank-to-bank, carry no percentage fee, and — crucially — are not reversible through a consumer dispute mechanism once confirmed. For finality of payment, they are significantly more robust. But wire transfers at this scale introduce a different category of cost: friction, float, and the opacity of cross-border movement. A typical outgoing domestic wire runs $25 to $35, an outgoing international wire $35 to $50, and incoming wires about $15. Those flat fees are manageable. What is not manageable is what happens to the wire in transit. On international wires, two larger costs never appear as a line item: a markup baked into the exchange rate, and deductions taken by intermediary banks in the middle of the route. M. invoices some clients in euros. On a €90,000 wire, the wire fee is the smallest number. The FX margin, intermediary deductions, and receiving bank fees are where the real cost sits. Then there is the float. International wire transfers typically take two to five business days to settle. During that time, the sender's account has been debited but the beneficiary has not been credited. The money is in the banking system, moving through correspondent chains, sitting in processing queues, waiting for cut-off times and compliance reviews. For a two-person practice where cash flow is tightly managed, five days of float on $90,000 is not trivial. It means payroll decisions are made with incomplete information. It means the consultant is carrying operational risk on money that has technically already been paid. Each intermediary may deduct fees and introduce delays, which contributes to limited transparency in traditional international payments. When M.'s wire from a European client arrived €800 short of the invoiced amount, he had no clean way to explain it to his bookkeeper. Which leg of the chain took it? Which bank made the deduction? The answer required three phone calls and ultimately went unresolved. The wire is final, but it is not clean. And cleanliness — clear records, predictable amounts, confirmed timing — is what professional services work demands. ## The Multi-Party Problem M.'s practice is structured around collaboration. Not every engagement is billed by him alone. On his most recent restructuring project, the fee was split three ways: M. took 55%, a specialist brought in for the financial modelling work took 30%, and a project manager took 15%. This is a common arrangement in professional services. It is also, under conventional payment infrastructure, a nightmare. The client pays M. M. receives the full $95,000, less whatever the gateway extracted or the wire left in transit. He then owes the other two parties their shares. He calculates the splits. He initiates two additional transfers. He waits for confirmations. He reconciles the amounts against what was received versus what was invoiced. He manages the float for the specialist and the project manager, who are waiting on him. According to the 2025 Contractor Management Report, 85% of freelancers have their invoices paid late at least some of the time. More than 1 in 5 freelancers are paid late more than half the time — meaning late payment is their normal experience, not the exception. In this arrangement, M. has become the institution making his collaborators late. Not because he intends to, not because the money is not there, but because the infrastructure requires him to act as a redistribution hub: receive, calculate, re-send, confirm. Each step introduces delay, error risk, and the social cost of being the person who holds other people's money for even forty-eight hours. The specialist once sent a follow-up message asking if the transfer had been initiated. It was a polite message. The damage to the working relationship was disproportionate to the message's tone. ## Escrow Doesn't Solve It Either The natural response to the reversibility problem with cards and the opacity problem with wires is to propose an escrow arrangement. Hold the funds somewhere neutral, confirm delivery, release upon sign-off. Structured. Protected. Professional. In practice, at this scale and in this context, escrow creates a different set of problems. Traditional escrow services are slow to establish. They require account creation, identity verification, and — for amounts at this level — compliance review that can take days or weeks. For an engagement that closes on a Friday with a client who is ready to pay, introducing escrow adds friction that the client did not expect and may not accept. It changes the tone of the transaction from one of professional confidence to one of institutional suspicion. A 2025 Atradius survey found that roughly 1 in 4 B2B invoices in North America are paid late or disputed, with the average resolution taking 30 to 60 days. Escrow services also hold funds in accounts that M. does not control. If the service provider has their own compliance triggers, their own processing delays, or — in the worst case — their own operational problems, M.'s $95,000 becomes a support ticket. Escrow is the right concept. The execution, through legacy infrastructure, consistently falls short. ## What a Six-Figure Invoice Actually Needs By the time M. had cycled through these options across several engagements, the requirements had become clear. Not aspirational — concrete and operational. He needed payment to be **final**. Not provisionally received pending a dispute window. Not sitting in a gateway hold. Final the moment it confirms. He had delivered the work. The invoice was not a request — it was a record of completed obligation. He needed payment to be **complete**. The full invoiced amount, without a percentage extracted by an intermediary who performed no professional function on the engagement. US merchants paid approximately $187.2 billion in processing fees in 2024, up 8.7% year-over-year, while payment volume grew 5.8%. Those fees are not an abstraction. They are a tax on professional output — one that is non-negotiable, invisibly extracted, and entirely disconnected from the value of the work done. He needed payment to be **simultaneous**. Not a flow that arrived to him and then required him to redistribute. The splits were agreed before the engagement began. The contract defined them. The payment event should honour those terms automatically — not create a reconciliation exercise that he managed manually while two other professionals waited. He needed payment to be **legible**. Not a wire that arrived in an unexpected amount with no line-item explanation for the difference. A record of what was paid, to whom, in what amount, at what time. Something that served as a receipt, a confirmation, and an audit trail simultaneously. Payment gateway fees can significantly impact the profitability and cost structure of a business. Since every transaction incurs a cost, the choice of a payment gateway and the associated fees can make a substantial difference in net revenue. But the problem M. faced was not simply one of fee optimization. It was structural: the entire payment layer was designed for a different kind of commerce. ## The Cost, Itemised To make this concrete, run M.'s $95,000 invoice through each available channel. ### Gateway (card-based) Transaction percentages typically range from 1.5% to 2.9% depending on the provider and region. At 2.9%, that is $2,755 extracted immediately. If the client is cross-border, cross-border charges can reach up to 4.4% — adding another $1,415 on top of the base rate. Total cost on the payment event alone: potentially over $4,000. The work was worth $95,000. The gateway took the equivalent of two days of M.'s billing rate for routing a number. Then there is the chargeback window. Standard card networks allow disputes to be filed for 60 to 120 days after the transaction. For all of that window, the payment is not final. It is conditional. ### Domestic Wire Flat fee: $25 to $35. No percentage. No chargeback risk. But: settlement in 1–3 business days, no automatic split to collaborators, and reconciliation is entirely manual. For a straightforward single-party domestic invoice, this is the most efficient option available — and it still requires M. to initiate two additional payments to his collaborators within 48 hours. ### International Wire Wire fees run USD $10 to USD $50 per transfer at most traditional banks; FX margin: 1% to 3% above the real mid-market rate, baked into the quoted rate; intermediary deductions: each correspondent bank takes a cut from the principal. On a €90,000 invoice, the FX margin alone at 2% mid-rate markup represents €1,800 extracted invisibly. Settlement typically takes two to five business days, with some corridors and circumstances pushing that longer. The payment is final when it arrives — but when it arrives, and in what exact amount, is not fully within M.'s control. ### The Multi-Party Overhead Under any of the above: M. receives the funds, calculates the splits, initiates transfers to two collaborators, waits for confirmation, and reconciles. At a conservative estimate of two hours of administrative time, this process costs the practice roughly $600 to $1,000 in billed time per engagement — in addition to the transaction fees themselves. Most invoice disputes stem from unclear scope, missing documentation, or pricing misunderstandings. The manual redistribution process creates its own ambiguity: if a collaborator receives less than expected because of an undisclosed intermediary deduction on the incoming wire, who carries the shortfall? The question should not exist. The payment structure was agreed. The execution infrastructure made it uncertain. ## The Resolution The problem M. faced is not exotic. It is structural, and it affects every consultant working on high-value, multi-party engagements. The conventional payment layer was not designed for professional services — it was designed for consumer commerce, where the seller is a merchant with risk profiles appropriate to retail, where the transaction amounts are small enough that percentage fees are invisible, and where reversibility protects the buyer from a seller they cannot verify. None of that applies to a professional services engagement. The buyer has verified the consultant. The scope has been documented. The work has been delivered and signed off. The relationship is the opposite of anonymous retail: it is a contractual, documented professional arrangement. Shaka resolves this structurally. The deal creator defines the payment split before the invoice is sent — M.'s 55%, the specialist's 30%, the project manager's 15%. A payment link is generated. The client pays once. The smart contract distributes funds to every party simultaneously at the moment of confirmation. There is no redistribution. There is no float between receipt and dispersal. There is no calculation to perform and no transfer to initiate. Payment is final and irreversible the moment it confirms — not pending a dispute window, not subject to a processor's risk review. The contract executes the terms of the engagement. For M., this means the conversation about payment infrastructure is closed before the engagement begins. The split is part of the deal structure. The client pays once, cleanly. Everyone receives their share in the same transaction. There is nothing left to reconcile. ## Why This Matters Beyond One Consultant M.'s situation is a compression of a problem that operates across the entire professional services economy. 85% of freelancers have their invoices paid late at least some of the time, and just over 21% are paid late or not at all over half the time — making late payment their normal experience rather than the exception. But late payment is only one dimension of the problem. The deeper issue is that the payment event itself — the moment when money should simply move from one party to another in the amount agreed — is compromised by infrastructure that takes a percentage, imposes reversibility, creates float, and requires manual redistribution. Payment gateway fees can significantly impact the profitability and cost structure of a business, and since every transaction incurs a cost, the choice of payment infrastructure makes a substantial difference in net revenue. That is true at $10,000. It is acutely true at $100,000. And it is true in a way that compounds: a consultant collecting $500,000 a year in project fees through a standard gateway at 2.9% is voluntarily surrendering $14,500 annually to infrastructure that adds no professional value to their work. The question M. arrived at — after the chargeback, after the short wire, after the three-way redistribution exercise — was not which gateway to use. It was whether to use one at all. The answer, for high-value professional services work, is that the gateway model was never the right fit. The correct infrastructure treats the payment as a contract execution, not a retail transaction: defined splits, simultaneous distribution, irreversible confirmation, and a complete record. That is what professional payment looks like. It is what collecting a six-figure fee should have looked like from the beginning.