Getting paid
Getting paid in United States: salary, freelance & remote work
Get paid while living in United States - salary rails, foreign employers, freelance invoices, stablecoin income, and ACH payout design. Includes mid-market FX vs boards, DCC refusal, ACH vs SWIFT, fee-stack anatomy, week-one calendar, and a Glide operating angle for United States.
On this page
Getting paid in the United States - or from abroad while living there - is where freelancers and remote employees keep or lose margin. This page owns receive architecture.
Receive path matrix
| Income type | Better pattern | Avoid |
|---|---|---|
| Local employer | Local USD account on domestic rails | Monthly SWIFT to a foreign retail account |
| Foreign employer | Multi-currency collection + scheduled local payout | Ad-hoc wires with random intermediaries |
| Freelance clients | Invoice with modern payout options + fee ownership | “Whatever your bank does” after the fact |
Local context
US employers prefer ACH to US accounts. Cross-border payroll into non-US accounts is a different product. Freelancers should avoid forcing clients through $45 wires when ACH-capable collection exists.
Rails you will hear:
- ACH is the US batch account-to-account network — cheap, not always instant (same-day ACH exists). Great for payroll-like flows; weak when you need guaranteed same-hour finality (that is closer to wires/RTP/FedNow).
- Fedwire-style gross settlement is for high-value US domestic urgency. It is not the default for everyday spend in United States.
- US real-time rails (RTP/FedNow) are expanding instant bank credit — coverage depends on both banks. Still not universal like Faster Payments in the UK.
- US real-time rails (RTP/FedNow) are expanding instant bank credit — coverage depends on both banks. Still not universal like Faster Payments in the UK.
Invoice mechanics
- State currency and exact receive method on the invoice
- Define who pays transfer fees
- Add terms that cover FX windows on late payers
- Reconcile receipts weekly with exportable statements
Stablecoin / crypto-native income
USDC-style collection can remove the long-haul wire - you still need a clean offramp into USD for rent and tax. Multisig matters once balances exceed coffee money.
Tax admin (high level)
Not tax advice. Living in United States may create home, host, or dual reporting duties. Keep tidy inbound/conversion records. Hire a cross-border-aware accountant before year-end.
Numbers that matter
| Metric | Planning band |
|---|---|
| Daily mid-range travel | USD 100–300 |
| Monthly mid living | USD 2,800–6,000 |
| Currency | US dollar (USD) |
| Primary rails | ACH, Fedwire, RTP, FedNow |
| Major banks (ATM brands) | Chase, Bank of America, Wells Fargo, Citi |
| Cash declaration baseline | Report currency and monetary instruments over USD 10,000 when entering or leaving the US (FinCEN). |
| Best months (general) | Varies widely by region — spring/fall for most cities |
Mid-market FX vs the board you are shown
The mid-market rate is the midpoint between buy and sell on wholesale markets — the number Google and major FX feeds show for USD. Airport desks, hotel cashiers, and many bank boards price far away from that midpoint. A “0% commission” offer in New York almost always hides the markup inside the rate.
Dynamic currency conversion (DCC) is the terminal prompt that offers to charge your home currency “for convenience.” In United States, refuse it: choose USD / local currency so your issuer converts near its published FX rules instead of the merchant’s padded rate.
| Surface | What you usually get | What to do |
|---|---|---|
| New York airport desk | Wide spread vs mid-market | Convert only emergency float |
| Hotel cashier | Convenience tax on USD | Pay room in local currency on card |
| Restaurant POS with DCC | Home-currency “helpful” prompt | Always select USD |
| Bank-branded ATM | Issuer FX + possible operator fee | Prefer Chase lobbies; cover PIN |
True-cost matrix (illustrative)
Ignore “$0 fee” headlines. For money into or inside United States, rank options by total funded to deliver a fixed USD outcome — including FX distance from mid-market, flat fees, intermediary lifting, and time risk.
| Path | Speed* | Hidden costs* | Best for |
|---|---|---|---|
| Local rail (ACH) | Minutes–same day | Needs local/multi-currency balance | Rent, salary, family once banked |
| Card spend in local currency | Instant auth | Issuer FX; DCC if you accept it | Tourist day-to-day in hubs |
| SWIFT / correspondent wire | 1–5 business days | Send fee + intermediary + FX markup | Only if beneficiary cannot receive local |
| Stablecoin leg + offramp | Minutes–hours | Network + conversion spread | Crypto-capable teams & freelancers |
| Airport cash convert | Immediate notes | Worst FX + theft surface | Emergency float only |
Domestic rails worth understanding
Inside United States, everyday bank value usually rides ACH and sibling domestic systems — not SWIFT. Tourists meet these rails indirectly (hotel deposits, local contractors). Residents and long-stay expats should treat them as the default once a local account exists.
- ACH is the US batch account-to-account network — cheap, not always instant (same-day ACH exists). Great for payroll-like flows; weak when you need guaranteed same-hour finality (that is closer to wires/RTP/FedNow).
- Fedwire-style gross settlement is for high-value US domestic urgency. It is not the default for everyday spend in United States.
- US real-time rails (RTP/FedNow) are expanding instant bank credit — coverage depends on both banks. Still not universal like Faster Payments in the UK.
- US real-time rails (RTP/FedNow) are expanding instant bank credit — coverage depends on both banks. Still not universal like Faster Payments in the UK.
Week-one money calendar
- Before you fly: enable issuer travel/security controls; order a backup card; save Chase ATM brands on a map around New York
- Landing day: skip full-budget airport FX; keep a tiny USD float if you already hold near-mid-market notes
- Day 1–2: test a small card purchase in USD; refuse DCC; confirm your backup card also works
- Day 3+: map where cash is still required (markets, tips, intercity desks) and refill only at bank lobby ATMs
- If staying 30+ days: start local-account checklist early — tourist KYC often fails at Chase
Fee stack anatomy (read this before any big transfer)
Every cross-border move into or out of United States is a stack of (1) FX distance from mid-market, (2) explicit send fees, (3) intermediary or network fees, and (4) time risk if the payment misses a payroll or rent cut-off. Marketing that highlights only one of the four is incomplete.
| Layer | What it is | How to pressure-test it |
|---|---|---|
| FX | Distance from mid-market USD | Ask for all-in funded amount for a fixed receive |
| Send fee | Flat or % charged by the sender product | Confirm whether fee is in send or receive currency |
| Intermediary / network | SWIFT lifting fees, ATM operator fees, chain gas | Ask who can debit intermediate banks |
| Time risk | Missed cut-offs, weekends, compliance holds | Plan 1–2 buffer days for rent-critical moves |
If a card freezes in United States
- Freeze the failed card in your issuer app; do not keep retrying and burning authorizations
- Switch to the backup card on a different network/issuer — test a small purchase first
- Withdraw a modest USD float from a Chase lobby ATM if cash is required
- Use a pre-arranged emergency top-up (partner, multi-currency balance, or stablecoin offramp) — not airport desks for large amounts
- If both cards fail, contact issuer travel support with merchant name + city; document every fee for dispute
Decision checklist before you commit
- Write the outcome first: “Recipient holds $X USD by date Y.”
- Quote at least two paths (local-rail fintech vs bank SWIFT vs card-funded cash) using the same outcome sentence
- Confirm the beneficiary can actually receive on ACH — if not, SWIFT may be forced
- Refuse DCC on every terminal; screenshot rate screens when amounts are large
- Document fees for expense reports and future disputes
What good looks like
- You can explain the mid-market USD rate vs the board in front of you
- You never accept DCC on POS or ATM prompts in United States
- Local outcomes ride ACH when the counterparty can receive them
- Emergency funding does not depend on a single card or airport cash
- Teams use approval controls (multisig) for treasury-scale balances
- You know which Chase (or peer) ATMs you will actually use in New York
Worked example (illustrative — not a live quote)
Suppose the recipient in United States must receive exactly $1,000 USD (rent slice, tuition installment, or family support). Fix that delivered amount first, then compare providers on what you must fund in your home currency.
| Provider pattern | What usually inflates cost |
|---|---|
| Bank SWIFT + desk FX | Flat wire fee + 1.5–4% FX vs mid-market + intermediary lifting fees |
| Fintech local-rail payout | Transparent fee + small FX spread — compare total funded |
| Airport cash then carry | Worst FX + theft risk — never for salary-scale amounts |
Frequently asked questions
How should freelancers get paid in United States?
Can my US employer ACH me in another country?
What local rail should salary use?
Is crypto salary legal?
How do I avoid bad FX in United States?
When should I use SWIFT into United States?
Written by
Glide Research
Payments research
Glide Research maps payment rails, FX corridors, and banking access so travellers, freelancers, and treasury teams can move money without legacy wire tax.
- Published
- Last reviewed
Glide · Borderless banking
Money for United States without the wire tax
Run payroll and cross-border payments from one account: hold USDC and 80+ currencies, convert close to the mid-market rate, and pay out on local rails instead of paying the wire tax. Solo, or with multisig for teams.
- Currencies
- 80+
- Spend anywhere
- Visa card
- Regulated legs run by
- Licensed partners