# How to receive donations from abroad without the transfer eroding them

A practical guide for settlement agents, fund managers, and charitable administrators on how international donation flows lose value in transit — and how onchain routing changes the math.

---


There is a cruelty built into the plumbing of international generosity. A donor in Sydney decides to give $10,000 USD (approximately $15,200 AUD) to a foundation operating in North America. Their intent is clear, their funds are available, and their instruction is simple. Yet by the time that money arrives — three banking days later, filtered through two correspondent institutions and a currency-conversion desk — the foundation's finance officer looks at the incoming credit and finds something closer to $9,150 USD (approximately $13,900 AUD). Eight hundred and fifty dollars of a charitable gift have been silently converted into fees, FX spreads, and handling charges incurred along the route. Nobody sent an invoice. Nobody asked for authorization. The erosion just happened.

This is not an edge case. It is the ordinary, documented experience of organizations that depend on cross-border giving. Understanding exactly where that erosion occurs — and what professionals can do about it — is what this piece is for.

<figure class="keyfacts">
<div class="keyfacts-grid">
<div><b>$40,000</b><span>lost per year at 4% average erosion on $1 million USD of cross-border donations</span></div>
<div><b>$30,000</b><span>kept per year on that $1 million USD when 1% onchain cost replaces 4% erosion</span></div>
<div><b>$15,000</b><span>kept per year on $500,000 USD of international donations, same comparison</span></div>
</div>
<p class="fig-src">Worked examples from this article: 4% average erosion on traditional wires against 1% onchain cost.</p>
</figure>

## The anatomy of a cross-border donation loss

To understand the problem precisely, it helps to trace a wire from source to destination.

SWIFT is not itself a banking system — it does not hold accounts, process payments, or move funds directly. It is a secure messaging network that financial institutions use to exchange standardized information, letting banks coordinate these activities with each other. The actual movement of money depends on chains of correspondent banks that settle with one another, each one a potential point of cost extraction.

SWIFT transfer fees and currency conversion markups typically fall in these ranges:

| Cost | Typical range |
| --- | --- |
| Sending fee | $25–$50 USD |
| Receiving fee | $10–$20 USD |
| Each intermediary bank involved | $10–$30 USD |
| Currency conversion markup | 1–4% over the mid-market rate |

Now stack those figures. A donor's bank charges a $45 USD outgoing wire fee. An intermediary correspondent bank deducts $20 USD. The receiving institution charges up to $25 USD on the incoming side. And if any currency conversion occurs — even a momentary one, say from AUD to USD — the largest cost involved in carrying out SWIFT money transfers is often the exchange rates. Most main banks charge around 3 to 5% for exchanging funds to the recipient's currency. On a $10,000 USD gift, that spread alone represents $300–$500 USD before a single operational dollar has been spent by the receiving organization.

International transfers are sent between banks in different countries. They typically cost more and take longer because funds have to pass through more third parties, who may charge handling fees that are often passed along to the customer. International transfers also often involve taxes and currency conversions. And banks set their own exchange rates and may include a margin to cover costs and profit.

The charge structure is also deliberately opaque. The amount deducted can vary significantly depending on the bank's specific policies and the number of intermediary banks involved in the transfer. Organizations are generally recommended to contact their bank's wire department to understand their fee structure for international incoming wires, as these costs are not always captured in standard reporting.

In other words, neither the donor nor the recipient organization has reliable visibility into what the corridor will cost until the funds land — or fail to land in full.

## The SHA problem: when "shared" means the recipient pays

Professionals who work with international payment flows are familiar with the SHA instruction — the charge allocation code that tells every bank in the chain to deduct its own fees from the transfer amount rather than billing the sender separately.

The sending bank and any intermediary banks that handle the money along the way may charge their own fees. The receiving platform has no control over these extra charges. When a donor's bank defaults to SHA — which is common — intermediary banks will deduct their charges from the sending amount, so the recipient receives less money.

The alternative, OUR-instruction transfers, requires the sender to explicitly request that their bank absorb all correspondent charges. But most retail banking customers have never heard of this instruction, and most bank interfaces do not surface it prominently. The result is that charity administrators routinely receive wire credits for amounts that don't match any pledge agreement, grant letter, or donation confirmation, requiring manual reconciliation every time.

<aside class="callout">
<span class="callout-label">Charge instruction</span>
<h4>Ask for an "OUR" Swift transfer</h4>
<p>To make sure the full amount arrives, asking the bank to cover all transfer fees when setting up the wire, known as an "OUR" Swift transfer, is the reliable method.</p>
</aside>

Despite the name, SWIFT transfers are not always fast — they can take anywhere from one to five working days. Anywhere from a total of three to five banks will charge fees, and they add up. If money is converted into another currency, poor currency exchange rates represent an added expense.

For an organization relying on predictable cash flow — a nonprofit with program commitments, a fund manager disbursing to beneficiaries, a foundation coordinating grants — this is not merely inconvenient. It is a structural funding gap that emerges from the mechanics of the transfer itself.

## A concrete scenario: the three-party grant

Consider a foundation headquartered in New York that receives a $50,000 USD (approximately $76,000 AUD) international grant from a European donor and must distribute it across three designated programs: 60% to a domestic service program, 25% to an international field partner, and 15% to the foundation's general administration. This is a standard structure in charitable disbursement practice.

Under the conventional SWIFT wire model, the sequence looks like this:

<figure class="fig">
<figcaption><b>The conventional SWIFT wire sequence</b><span>Worked example: a $50,000 USD grant split 60% / 25% / 15%</span></figcaption>
<ol class="steps">
<li><b>Funds arrive</b>The foundation receives the wire. Sending an international wire transfer through a U.S. bank typically costs $35–$50 USD, plus potential intermediary and receiving fees. By the time the $50,000 USD gift lands, the amount might be $49,200 USD (approximately $74,800 AUD) after correspondent deductions.</li>
<li><b>Internal allocation</b>The foundation's finance team manually calculates the three shares, prepares three separate outgoing payment instructions, and routes them through accounts payable. Each instruction must be reviewed, approved, and executed independently.</li>
<li><b>Disbursement delays</b>Other providers often have to wait for client payments to clear or for donations to reach a minimum value before issuing disbursements, adding weeks of delay. The three receiving parties are told funds are "in process."</li>
<li><b>Reconciliation</b>The wire amounts received by each party may differ from the calculated shares because each subsequent transfer incurs its own fees. The administration receives 15% of a slightly eroded base, the field partner's international wire carries its own FX conversion cost, and the entire exercise requires multiple rounds of bookkeeping to close.</li>
</ol>
</figure>

The total cost in fees, staff time, and timing risk can easily consume 3–6% of the original gift, depending on the route. On a $50,000 USD grant, that is $1,500–$3,000 USD (approximately $2,280–$4,560 AUD) that never reaches the intended purpose.

## Why FX spread is the largest hidden cost

Fee line items, while irritating, are at least legible. The more insidious erosion comes from currency conversion spreads, which are embedded in exchange rates rather than disclosed as separate charges.

In 2025, the global average cost to send remittances remained above 6%. This is well above the G20's remittance target cost of 1%.

The implication for a foundation receiving $1 million USD (approximately $1.52 million AUD) annually in cross-border donations is stark: at 4% average erosion, $40,000 USD (approximately $60,800 AUD) per year disappears into the correspondent banking system — not into programs, not into administration, not into any purpose the donor intended.

This is the number that foundation boards, audit committees, and major donors rarely see presented clearly. It lives inside a line item called "bank charges" or gets netted out of gross receipts before it ever reaches a finance report. But it is real, and it compounds.

Settlement officers and fund administrators who work in this space understand the problem viscerally. They have built workarounds: pre-negotiated FX rates with primary banking relationships, OUR-instruction requirements in grant agreements, minimum wire thresholds to justify the fixed costs. These are professional adaptations to a broken rail. They reduce erosion but do not eliminate it, because the correspondent banking architecture itself is the source of the friction.

## The timing problem: when settlement uncertainty becomes operational risk

Beyond cost, the timing uncertainty of international transfers creates a second category of harm that is harder to quantify but just as damaging.

A settlement agent coordinating a multi-party closing, a fund administrator releasing grants on a quarterly cycle, or a legal professional holding funds on behalf of multiple beneficiaries all share one critical need: certainty. They need to know, at a specific moment, that the funds have arrived in full and that the credit is final. A bank creates a SWIFT message and routes it to the recipient's bank, typically settling in 1–5 business days. Delays also occur during compliance checks, currency conversions, or across time zones.

That window — one to five business days — is not a minor inconvenience. For a closing attorney coordinating title transfer, a one-day slip in fund receipt can cascade into rescheduled signings, extended rate locks, and material cost to all parties. For a foundation disbursing grants on a funding deadline, a delayed wire can mean a field partner misses payroll.

And even when the wire clears on day two, the professional receiving it faces a residual question: is this credit final? In the traditional correspondent banking model, a SWIFT message may be acknowledged in hours but only settles once correspondent banks clear it, often one to several business days later. The difference between message delivery and settlement finality is real, and it matters to anyone whose fiduciary obligation requires certainty before releasing downstream obligations.

## How onchain routing changes the arithmetic

The answer to this problem does not require abandoning the professionals who manage these transactions — quite the opposite. It requires giving them a better instrument for the routing work they are already doing.

Onchain payment rails, and specifically stablecoin-denominated transfers settled on Ethereum, offer a fundamentally different cost and timing structure.

Businesses can reduce cross-border payment costs by up to 80% using crypto and stablecoin rails. Traditional wire transfers cost 2–7% in fees including FX spreads and intermediary charges, while stablecoin payments typically cost 0.5–2%.

Stablecoins can meaningfully reduce total transaction costs by minimizing correspondent hops and automating foreign exchange and transaction settlement.

On the finality question, the difference is structural. Stablecoin payment settlement means value transfers can reach on-chain finality faster than SWIFT, ACH, or card flows in many cross-border scenarios, often in seconds to minutes rather than business days.

Where traditional settlement relies on institutional rules and operational procedures to establish finality, blockchains achieve it through cryptography and economic deterrence. On a proof-of-stake network like Ethereum, a transaction becomes technically final when it is incorporated into a validated block and subsequently confirmed. Although consensus finality can be formally probabilistic depending on the consensus mechanism used, the economic cost of reversing even a handful of confirmations makes rollback practically impossible.

For business settlement, irrevocability is worth more than message delivery, because it is the property that lets you release goods, fund an account, or pay a counterparty without holding your breath.

This is not theoretical. Stablecoin payments were estimated at $390 billion in 2025, with B2B volume growing 733% year-over-year. The infrastructure is production-grade, the stablecoin instruments are deep and liquid, and the settlement professionals who have moved onto this rail report a material improvement in their operational certainty.

## The split problem: one inbound, many recipients

The challenge of receiving a large international donation and distributing it to multiple parties is not only about the cost of the inbound wire. It is also about what happens after: the manual allocation, the multiple outgoing payments, the reconciliation burden, and the timing uncertainty that each additional disbursement step introduces.

Traditional practice handles this sequentially. The funds arrive. They are verified. The administrator calculates shares. Separate payment instructions are issued. Each one incurs its own processing time and potentially its own additional fees. The parties wait.

This is where shaka.deal introduces a specific mechanical advantage. Shaka.deal is an onchain payment router built on Ethereum. Its design is straightforward: one incoming payment, preset allocation shares, simultaneous payout to every party in the same transaction, with final settlement. The router moves the total amount. It distributes it instantly to every named party at their predetermined share. It does not hold funds at any point in the process — it routes.

For a settlement agent managing a charitable closing, a fund administrator distributing a grant across multiple program beneficiaries, or a foundation coordinating a pooled gift to several field organizations, the operational implication is significant. Instead of a multi-step disbursement sequence — each step carrying its own risk of delay, shortfall, or reconciliation error — the entire split happens in one onchain transaction. The shares are defined before the payment is made. The distribution is simultaneous. The record is permanent, public, and auditable on-chain.

Consider the three-party grant scenario revisited. The European donor sends USDC equivalent to $50,000 USD (approximately $76,000 AUD) to the foundation's onchain address. The foundation has configured shaka.deal with three recipient wallets and three share percentages. When the inbound transfer settles, the router executes — simultaneously, in one transaction, final:

| Recipient | Preset share | Amount routed |
| --- | --- | --- |
| Domestic program | 60% | $30,000 USD |
| Field partner | 25% | $12,500 USD |
| Administration | 15% | $7,500 USD |

No sequential wires. No additional FX conversion for the field partner payment. No three-day float between allocation and disbursement. No reconciliation discrepancy because every party received exactly their preset share of exactly what arrived.

The field partner's finance officer can confirm receipt within minutes. The foundation's audit trail is complete and machine-readable from the moment the transaction is broadcast. No spreadsheet reconstruction is needed.

## What the OTC desk and settlement agent do in this model

It is worth being explicit about the role of professionals in an onchain routing workflow, because the instinct — mistaken — is to assume that better payment technology means fewer professionals. That is not the Shaka model, and it is not how this works in practice.

Settlement agents, closing attorneys, OTC desks, and fund administrators are the parties who structure the deal, confirm the parties, document the shares, and ensure that the transaction complies with applicable legal and regulatory requirements. None of that changes when the settlement rail moves onchain. In fact, the professional's role becomes more valuable in one specific respect: because the shares must be configured before the transaction executes, the allocation logic must be precise and agreed in advance. That requires exactly the kind of professional coordination — term negotiation, documentation, counterparty verification — that these specialists provide.

The OTC desk that helps a high-net-worth donor convert a large position into stablecoin for a charitable transfer is not replaced by onchain routing — it is complemented. The closing attorney who confirms that all parties have agreed to their respective shares before configuring the router is doing the same work they have always done, with more certain execution at the end.

What changes is the settlement layer. The attorney does not need to track multiple wire confirmations. The fund administrator does not need to issue sequential disbursements. The compliance officer gets an immutable on-chain record of exactly when each party received exactly what share. The professional's judgment governs the setup; the router handles the execution.

## Practical considerations for international donation structures

For organizations that regularly receive significant donations from abroad, the transition to onchain routing is not a single switch. It is a deliberate workflow adjustment that requires coordination across a few practical dimensions.

**Stablecoin denomination:** The most common choice for cross-border charitable transfers is USDC, a dollar-denominated stablecoin issued by Circle and fully reserved by cash and short-duration US Treasuries. For most enterprise use cases, the stability and predictability of these dollar-pegged assets make them the best choice for international transfers. A payment sent in USDC arrives as USDC, with no exposure to the price swings that characterize volatile cryptocurrencies. This matters for charitable organizations with budget commitments denominated in USD, and it matters equally for Australian entities whose AUD-denominated operations need predictable conversion — the rate is negotiated once, at the point of donor off-ramp, rather than being extracted silently by every bank in the chain.

**Donor education:** The majority of international donors giving to a foundation or charitable fund will be individuals or corporations who are accustomed to wire transfer instructions. Moving them onto stablecoin rails requires clear, professional instructions from the receiving organization and, often, access to a reputable on-ramp service. This is a one-time onboarding step, and for major donors giving regularly, the cost savings over time — for both the donor and the recipient — provide a strong motivation.

**Off-ramp considerations:** An organization that receives USDC but needs to pay operational expenses in USD, AUD, or another fiat currency will need a banking partner or OTC relationship capable of converting stablecoins to local currency. The hard engineering problem for a cross-border payment operator is not the on-chain transfer. It is the stablecoin off-ramp: converting USDC into local fiat in the destination market, reconciling on-chain finality against banking-rail finality, and keeping the corridor compliant end to end. This is precisely where an OTC desk or a banking partner with stablecoin settlement capability provides essential value.

**Accounting and audit:** Onchain transactions produce a public, timestamped record of every movement. For a foundation's audit committee, this is materially better than reconstructing correspondent bank records from SWIFT message logs. The on-chain record shows the sender address, the amounts distributed to each recipient address, the timestamp, and the transaction hash — all of it permanent and independently verifiable.

## The erosion calculus over a year

Numbers bring this home. Take an organization that receives $500,000 USD (approximately $760,000 AUD) annually in international donations, spread across ten to fifteen inbound wires of varying sizes.

Under the current SWIFT model, applying a conservative 4% average erosion — combining sending fees, intermediary charges, receiving fees, and FX spread — part of every year's giving disappears into the correspondent banking system. Even near the midpoint of the two cost ranges — comparing 4% traditional erosion against 1% onchain cost — the organization retains most of that amount, as does one receiving $1 million USD (approximately $1.52 million AUD) in annual international donations:

| Annual international donations | Lost at 4% erosion | Retained at 1% onchain cost |
| --- | --- | --- |
| $500,000 USD | $20,000 USD (approximately $30,400 AUD) | $15,000 USD (approximately $22,800 AUD) |
| $1 million USD | $40,000 USD (approximately $60,800 AUD) | $30,000 USD (approximately $45,600 AUD) |

That differential is redirected each year from bank corridors into programmatic work. Add the staff time required to reconcile partial arrivals, re-request shortfalls from donors, and manage sequential disbursements to multiple program parties, and the operational cost of the SWIFT model climbs further.

A company processing $10 million annually in international payments could save hundreds of thousands of dollars by switching to blockchain-based settlement. For a charitable organization, that is not a cost optimization — it is mission-critical funding recovered.

## Certainty as a design principle

The case for onchain routing in international donation flows is ultimately a case for certainty. Donors want to know that their full gift arrives. Program staff want to know that their disbursements will land without shortfall. Settlement agents want a record that closes cleanly. Audit committees want documentation that does not require reconstruction from fragmentary bank records.

The traditional correspondent banking system was not designed with any of these needs as a priority. It was designed for institutional currency exchange and interbank liquidity management. Charitable organizations, fund administrators, and the professionals who serve them have been adapting to its limitations for decades, building workarounds on top of workarounds.

The split, instant, and final settlement that onchain payment routing provides — the spine of what shaka.deal does — is not a replacement for the professionals who structure these transactions. It is the settlement infrastructure those professionals deserve. One inbound amount. Preset shares. Simultaneous distribution to every party. Permanent record. No erosion in transit.

That is what a donation looks like when the rail works the way the donor intended.

*Shaka.deal is a non-custodial onchain payment router on Ethereum that routes and distributes incoming payments to multiple parties at preset shares, in a single transaction, with final settlement. Learn more at [shaka.deal](https://shaka.deal).*