Scenario
Audience
European contractors and small agencies with US clients
Goal
compare USD-to-EUR bank routes against stablecoin routes before choosing a payment instruction for the client
Best for
recipients who need a repeatable route and can keep clean invoice documentation
Payment scenario and route objective
Get paid from a US client in Europe is a use-case route guide for European contractors and small agencies with US clients. US-client payments into Europe sit between American payer expectations and European bank controls, so the route has to make sense to both sides of the transaction.
US clients may prefer ACH, wire, card or platform payout, while European recipients care about EUR settlement, FX spread and bank acceptance. The practical objective is to compare USD-to-EUR bank routes against stablecoin routes before choosing a payment instruction for the client, but the decision should be made through a live route result and a documentable payment story.
For this page, the preset starts with 1,000 USD, Card, Europe, and a USD into USDC ERC20 flow. Refresh the preset before each invoice cycle because US card, bank and aggregator availability can change by country and KYC result.
Routes worth testing live
The useful comparison is between speed, payer familiarity, recipient documentation and net receive after spread, not between provider brand names alone.
Keep at least two alternatives visible because a bank, fintech, card or stablecoin route can win for different reasons. The table below avoids fixed fee promises and uses the article as a route checklist rather than a static quote.
Before choosing a rail, confirm who appears as sender, which currency the contract names and whether the recipient can document the business purpose.
- US wire or platform payout to EUR bank account: The useful comparison is between speed, payer familiarity, recipient documentation and net receive after spread, not between provider brand names alone.
- USD card-funded USDC through an official ramp: Before choosing a rail, confirm who appears as sender, which currency the contract names and whether the recipient can document the business purpose.
- USD wallet balance to EUR SEPA then on-ramp: A route becomes fragile when a US payer sends a business payment through a consumer rail or when the recipient cannot connect the incoming amount to an invoice.
Test amounts
Run the same route at three sizes
These rows are calculation rules, not fabricated quotes. The live Route Finder fills in the real net amount when a provider returns a usable route.
| Amount | Calculation | Fee check | Decision use |
|---|---|---|---|
| 100 USD | 100 USD -> live USDC ERC20 net received | Card minimums, fixed fees and quote rounding can dominate this small test. | Use only when the convenience case is stronger than fixed-cost drag for European contractors and small agencies with US clients. |
| 1,000 USD | 1,000 USD -> live USDC ERC20 net received | Use this as the practical baseline for Europe: visible fees, spread and route confidence are easier to compare. | The best route is the one that gives the European recipient usable funds with fewer reconciliation questions. |
| 10,000 USD | 10,000 USD -> live USDC ERC20 net received | At larger size, a route becomes fragile when a us payer sends a business payment through a consumer rail or when the recipient cannot connect the incoming amount to an invoice. | Prefer the route with clearer limits, evidence and review path: Before choosing a rail, confirm who appears as sender, which currency the contract names and whether the recipient can document the business purpose. |
Route table
Compare route quality before checkout
Rows show what must be checked. Exact net receive, known fees and spread are generated from live route data, not from static page copy.
| Route | Provider | Net received | Known fee | Spread loss | KYC | Business use | Confidence |
|---|---|---|---|---|---|---|---|
| US wire or platform payout to EUR bank account | Wise | Live quote baseline for Europe | Card and provider fee lines must be visible | Benchmark after route check; The useful comparison is between speed, payer familiarity, recipient documentation and net receive after spread, not between provider brand names alone. | Business KYC likely | Potentially suitable after business review | Use as baseline |
| USD card-funded USDC through an official ramp | Payoneer | Compare against the second path | Card and provider fee lines must be visible | Benchmark after route check; The useful comparison is between speed, payer familiarity, recipient documentation and net receive after spread, not between provider brand names alone. | Business KYC likely | Potentially suitable after business review | Compare with live route |
| USD wallet balance to EUR SEPA then on-ramp | Revolut Business | Compare against the fallback path | Card and provider fee lines must be visible | Benchmark after route check; The useful comparison is between speed, payer familiarity, recipient documentation and net receive after spread, not between provider brand names alone. | Business KYC likely | Potentially suitable after business review | Fallback or edge-case route |
Find this route
Use this preset to compare available USD to USDC ERC20 routes for Europe with Card. Results are generated after you click Find route.
Want to change amount, payment method, country or network?
Open full Route Finder- Country
- Europe
- Pay
- USD
- Receive
- USDC
- Network
- ERC20
- Rail
- Card
- Amount
- 1,000 USD
How to calculate usable net receive
Run the route at 100, 1,000 and 10,000 units because the cost pattern changes with size. At small amounts, fixed fees can dominate; at mid-size, spread becomes easier to see; at larger size, limits and enhanced review may matter more than the headline rate.
For European contractors and small agencies with US clients, the useful number is the value that can actually be spent, booked or paid out after known provider fees, confirmed network costs, spread versus benchmark and any visible payout charge.
If a fee is not confirmed by the provider source, treat it as unknown rather than assuming it is zero. Keep quote timestamps, receipts and payment-purpose records with the route decision.
Compliance, KYC and bank-readiness
the cheapest visible route can still be worse after FX spread, intermediary bank charges or card issuer treatment. A route becomes fragile when a US payer sends a business payment through a consumer rail or when the recipient cannot connect the incoming amount to an invoice.
Route confidence should include source quality, freshness, route availability, provider status and whether the payment purpose can be documented for Europe.
Expect full KYC or business KYC when the route touches regulated providers, bank payouts, higher ticket sizes or business activity. Keep account ownership, source-of-funds and payment-purpose evidence ready before relying on the route.
- Document: Before choosing a rail, confirm who appears as sender, which currency the contract names and whether the recipient can document the business purpose.
- Watch: A route becomes fragile when a US payer sends a business payment through a consumer rail or when the recipient cannot connect the incoming amount to an invoice.
- Use cautiously: the sender requires chargeback protection, card acceptance or formal merchant acquiring rather than contractor payout
How to use the Route Finder block
Use the embedded Route Finder to refresh this exact scenario: PL, USD, USDC, ERC20, Card and 1,000 USD.
Refresh the preset before each invoice cycle because US card, bank and aggregator availability can change by country and KYC result. After results appear, compare the top route with the table rather than treating the article body as a locked quote.
If the live route returns no results, change one input at a time: amount, rail, country, asset or network. A no-route result is a useful availability signal, not a reason to fabricate a recommendation.
When not to use this route
Do not use this route when the sender requires chargeback protection, card acceptance or formal merchant acquiring rather than contractor payout. The best route is the one that gives the European recipient usable funds with fewer reconciliation questions.
Also avoid using the route to bypass country restrictions, sanctions controls, KYC, account-purpose limits or tax reporting duties. The product compares routes; it does not provide custody, exchange execution, brokerage, tax advice or legal advice.
FAQ
Is get paid from a us client in europe mainly a price decision?
The useful comparison is between speed, payer familiarity, recipient documentation and net receive after spread, not between provider brand names alone. The live Route Finder should be used before making a decision because amount, country, rail, KYC and provider source quality can change the result.
Why test 100, 1,000 and 10,000 USD?
The same provider can look different at each size. The best route is the one that gives the European recipient usable funds with fewer reconciliation questions. Small tests reveal fixed-cost drag, mid-size tests show spread more clearly, and larger tests expose limits or review friction.
Does the Card preset guarantee availability?
No. The preset only starts the comparison for Europe. Refresh the preset before each invoice cycle because US card, bank and aggregator availability can change by country and KYC result. Provider availability can change by account type, KYC result, rail, network and amount.
Can businesses use this USDC ERC20 route?
Only when the provider supports the business profile and the company can document the payment purpose. Before choosing a rail, confirm who appears as sender, which currency the contract names and whether the recipient can document the business purpose.
What is the main limitation of this use-case route guide?
US-to-Europe flows need a route that the client, provider and recipient bank can all understand. This is route intelligence and product education, not legal, tax, custody, exchange, brokerage or investment advice.