Field notes from money-movement operations

Guide 01

What a cross-border payment actually costs

A wire that "costs $40" rarely costs $40. Cross-border payments bill in three layers, and only the first one appears on the fee schedule:

Layer 1: the fee you see

Outgoing wire fees run $25–$50 for typical business accounts, per payment. Pay 30 suppliers individually and you've bought 30 of them, even inside one country group.

Layer 2: the intermediaries' cut

Correspondent banks along the route take $10–$30 — frequently deducted from the recipient. Your supplier receives an amount short of what you sent, with a cryptic deduction line. You paid in full; they got less; the money went to plumbing you can't see.

Layer 3: the FX spread, which dwarfs both

Banks monetize conversion through the rate, not the fee. A 2.5% margin — common for "standard" corporate FX — on a $100,000 payment is $2,500, invisible unless you benchmark against mid-market. Most companies never do, because the bank doesn't show the benchmark.

What actually reduces the stack

• Local rails over wires: SEPA/ACH/PIX cost a fraction of a wire and settle same-day. Route by destination, not by habit.
• Consolidation: fewer, larger payments per counterparty cut the fixed-fee layer.
• Benchmarked FX: require the rate to be stated against mid-market before you confirm. "Bank rate" is not a rate.
• Stablecoin where the counterparty accepts it: network fees of cents to dollars replace layers 1 and 2 entirely; the FX layer disappears if you're settling in dollars anyway.

Astro Breeze quotes every conversion against mid-market before confirmation and locks the rate at execution — the layer-3 surprise is the first thing we removed. Compare on the rails page.

Guide 02

Choosing a settlement network

"Should we pay on-chain?" is the wrong first question. The right ones: where is the receiver, what can they off-ramp cheaply, and how big is the payment? A decision table we use internally:

• Domestic instant rail exists (SEPA, PIX, SPEI, RTP...): use it. Instant, near-free, universally accepted. On-chain adds nothing here.
• Cross-border into a strong local rail: convert in your base currency, pay through the local rail. This is the Astro Breeze default: convert once at a quoted rate, then it's a domestic payment.
• Counterparty wants dollars on-chain: USDC on Polygon or Base for most corridors; USDT on Tron where that's the local liquidity standard (large parts of Southeast Asia and LatAm).
• No good local rail, USD-agnostic counterparty: on-chain. Minutes and cents beat a three-day, $70, 2.5% wire every time.
• Regulated counterparty requiring bank credit: SWIFT with full reference fields, priced and timed up front.

Two rules that prevent most on-chain incidents

Address allowlists with a cool-down. New destination addresses should never receive money the day they're added. A 24-hour window turns a fat-fingered or compromised address into an inconvenience instead of a loss.

The receiver confirms the network, not just the address. The same string of characters can be valid on several networks with very different outcomes. "USDT, Tron" is a complete instruction; a bare 0x address is not.

Network fees move with conditions; Astro Breeze shows the exact fee and locked rate before every transfer confirms.

Guide 03

A treasury policy for stablecoin wallets

Most on-chain losses aren't market losses — they're control failures: an address typed wrong, an approval given in a chat message, a key held by the one person on vacation. Five controls, in order of how much grief they prevent:

• 1. Address allowlists. Outbound transfers only to pre-approved destinations, with a 24-hour cool-down on new entries. This single control prevents the majority of catastrophic errors.
• 2. Maker–checker above a threshold. Transfers above, say, $10,000 need a second approver who isn't the initiator. Keep the threshold low enough to matter and high enough to not flag every routine payment.
• 3. Velocity limits. Per-wallet and per-entity caps on daily outflow. When credentials leak, velocity limits are what turns a potential catastrophe into a bounded incident.
• 4. Segregated wallets by purpose. Collection float, operational payouts and treasury reserves in separate wallets — so a compromise of one flow can't touch the others.
• 5. An audit trail you actually export. Every action with who/what/when, shipped to your data warehouse. If it only lives in the wallet UI, it doesn't exist for your auditor.

Astro Breeze operational wallets implement all five as platform policy — configured to your thresholds, enforced by the system, exported to your warehouse. Read more on the wallets page.

Guide 04

Stablecoin revenue to fiat balance: a worked flow

A marketplace collects 400,000 USDT a month from buyers and pays 23 suppliers in EUR and BRL. Here's the whole month on Astro Breeze, with the numbers on the table:

• Collect: buyers send USDT to per-entity wallets on Ethereum, Tron and Polygon. Deposits credit 24/7 after network confirmations, matched to orders by reference.
• Convert (policy, not vibes): an auto-rule converts 50% to USD on deposit at the quoted rate; the rest stays on-chain for the counterparties who want it. The rule exists so treasury doesn't watch charts.
• Pay out: 14 EU suppliers by SEPA (same day), 9 BR suppliers by PIX (instant, BRL converted at quoted rate). On-chain suppliers receive USDT directly, allowlisted.
• Reconcile: one journal covers deposits, conversions, payouts and fees — reference fields carried end-to-end. It imports into the ledger; nobody rebuilds the month from exchange statements.

The cost of the month: quoted conversion spreads (typically 0.3–0.7% over mid-market on volume bands), local rails included in the plan, on-chain fees at cost. The same month over wires: 23 wire fees, unknown intermediary deductions, and an FX spread discovered on invoices.

Figures are illustrative of a typical mid-size flow. Your corridor sheet will have exact pricing — request one.