How to receive USD payments from international clients

An American client wants to pay your invoice in dollars. A marketplace offers a USD payout. Another overseas business wants to send USD from a bank outside the United States.

These payments share a currency, but they may need different receiving instructions.

Receiving USD internationally starts with matching the sender’s transfer method to a compatible receiving route. A U.S. account number is not a promise that every dollar payment can reach it. Nor does receiving dollars tell you what it will cost to turn them into the currency you eventually spend.

This guide explains the choices for freelancers, agencies, and sellers: local USD receiving details, ACH, domestic wires, FedNow, international bank transfers, and the next step from receipt to payout.

Separate the payer’s location from the payment route

A business outside the United States can have access to a service that sends a local USD payment. A U.S. business can also use an intermediary or an international bank-transfer workflow.

The sender’s postal address therefore does not identify the rail. Ask which method their finance team or marketplace will actually use.

For a fictional designer based outside the U.S., two clients could need different arrangements. Client A can send an ACH credit from its U.S. business bank. Client B needs international wire instructions from a bank in another country. Local receiving details approved for Client A’s payment may not accept Client B’s route.

Resolve this before sharing account information. The practical question is “Can these details accept the transfer you will send?” rather than “Can you pay in dollars?”

Understand the main USD routes

Route	What to understand	What to confirm with the provider
ACH credit	A U.S. bank-transfer route with business-day processing	Whether the details accept incoming ACH credits and the intended payer
U.S. domestic wire	A bank wire within the U.S. payment infrastructure	Correct wire instructions, processing window, and charges
FedNow	Instant-payment infrastructure for participating institutions	Whether both the institution and the particular service support this payment
International bank transfer	A cross-border arrangement that can involve Swift messaging and intermediary banks	Explicit international receiving instructions and any intermediary requirements

Nacha distinguishes scheduled and same-day ACH processing. The Federal Reserve separately operates Fedwire Funds and FedNow; these are different services with different operating models. Their existence does not imply that every receiving product offers access to them. Nacha’s ACH overview, Fedwire Funds Service, and FedNow.

For a detailed comparison of the first two routes, read ACH versus wire transfers.

Also distinguish ACH credits from ACH debits. A receiving product accepting client credits does not necessarily let you collect authorised debits or pay subscriptions from those details.

What are local USD receiving details?

A bank or payment service may provide instructions that allow eligible payers to send supported local dollar transfers. Those instructions can include an account-holder name, routing number, account number, account type, bank information, and a required reference.

The product behind the details varies. It may be a bank account, a payment-service arrangement, or an identifier used to allocate payments within a broader account structure. The visual appearance of the number does not answer that question.

Check who provides the account service, what incoming payments are allowed, and what protections and withdrawal conditions apply. A virtual account identifier does not automatically create a full-service U.S. bank account or permission to use credit, debit, or card features.

The name on the instructions matters too. Use the displayed beneficiary name. If it differs from your trading name, explain the legitimate relationship to the payer rather than changing the instruction yourself.

Check whether the intended payer is allowed

Receiving your own money and collecting a client’s payment are different use cases. A service may apply different rules to first-party funding, business-client payments, payroll, marketplace payouts, and personal transfers.

Before announcing a new USD payment method, confirm your actual payer types. For a freelancer, that might be registered businesses paying invoices. For an agency, it might include several contracting entities. For a seller, it might be a particular marketplace’s settlement entity.

A broad product label such as “international account” does not resolve these permissions. Ask the provider to confirm the full example: your customer type and country, the payer type and country, the currency, the route, and the purpose.

If the product cannot support that combination, choose another permitted route. Do not describe a client payment as self-funding to make it appear eligible.

Prepare the correct instructions for the client

Obtain the current instructions from the receiving institution or service. Keep the fields together and identify the transfer method explicitly.

For a supported local USD route, the handover might require:

• The exact beneficiary name.
• The account and routing identifiers for that route.
• The account type, if specified.
• USD as the sending currency.
• The permitted method, such as ACH credit or domestic wire.
• A required memo or reference, where one is issued.
• Additional bank or beneficiary information requested by the instructions.

Do not assume ACH and wire routing details are interchangeable. Do not add a Swift code found online to local-only instructions. If the payer’s form demands information you were not given, ask whether they selected the wrong method or need a different receiving route.

Our international bank-details template helps turn the verified instructions into a clear message.

Receiving USD from a marketplace is a separate compatibility check

A marketplace choosing to display earnings in USD does not guarantee that it can pay your chosen USD receiving details.

Check the platform’s payout-country rules, account ownership requirements, permitted receiving institutions, currency, and transfer method. Then check the receiving provider’s rules for payments from that platform. Both sides need to accept the arrangement.

A common operational mistake is entering new details immediately before a large scheduled payout. If the marketplace reviews the change, a delay can begin before the payment reaches the banking system.

Allow time for verification, keep records of the previous payout destination, and check how the platform handles payouts already in progress. Our marketplace payout guide separates order revenue, available balances, and money actually sent to your bank.

Plan what happens after the dollars arrive

Your next step might be to retain a supported USD balance, convert to another currency, pay an approved recipient, or request a payout. Only count options the actual service provides to your account.

If your expenses are in a local currency, compare the complete path to that destination. A low receiving fee can be outweighed by a later conversion margin or payout charge. Conversely, an explicit collection charge may accompany a better net conversion result.

Use a fictional USD 2,500 receipt to illustrate the sequence. Assume a USD 5 receiving charge, then a conversion rate of 0.90 EUR per USD and a EUR 3 bank-payout charge:

Step	Illustrative result
Receipt	USD 2,500
After receiving charge	USD 2,495
After conversion	EUR 2,245.50
After payout charge	EUR 2,242.50

These are teaching figures, not an Ostro quote or current exchange rate. The point is to calculate in the order the charges occur and compare the final amount, not just the original invoice.

Decide who carries exchange-rate risk

If you invoice in USD while your expenses are in another currency, a change in the exchange rate can affect your local-currency revenue between quoting and conversion.

Agree the invoice currency and quote-validity period in advance. If you need a particular net local amount, build the commercial price around realistic costs rather than assuming that the client’s USD transfer will always convert into the same result.

Holding dollars can postpone a conversion; it does not eliminate the eventual currency exposure. Whether holding is available, suitable, or subject to particular requirements depends on your service and circumstances.

For a pricing worksheet with margin examples, see pricing freelance work in foreign currencies.

Track the transfer with the right evidence

When a client says “paid,” first establish whether the payment was approved internally, submitted to its bank, or actually processed.

Request the date, amount, currency, beneficiary details used, method, and available tracking identifier. ACH investigations can use a trace number. Fedwire messages have their own identifiers. A bank’s tracking reference is different from your invoice number.

Nacha advises people with questions about individual ACH payments to contact their financial institution rather than the association, which does not process individual customer enquiries. Nacha: Consumer FAQs.

Your receiving provider can inspect the incoming side once the relevant evidence is available. Keep the invoice open until you can reconcile it with an actual receipt or otherwise explain its settlement.

Common USD payment problems

Problem	What to check
Client sent an international wire to local-only details	The submitted rail and whether those details accept it
The beneficiary name differs from the invoice brand	The issued name, supplier record, and documented relationship
The transfer arrived short	Sent amount, fee allocation, intermediary handling, and any conversion
An ACH credit is being confused with a debit	Who initiated the transfer and what the product permits
A marketplace rejects the account	Payout country, ownership, institution type, and verification rules
The payment is visible but unavailable	Current status and any required review or payout conditions

Investigate the original transfer before asking for another one. A duplicate payment adds a second reconciliation problem without correcting the first.

Where Ostro fits

Ostro’s USD receiving and payout options are subject to activation, eligibility, compliance review, route support, and licensed financial partner availability. Account details in your name are available only where supported and approved. Use the instructions and options shown in your workspace; a rail discussed in this educational guide is not a guarantee that it is enabled for your account. How Ostro works explains the product workflow.

Frequently asked questions

Do I need to live in the United States to receive USD?

Not in every arrangement. Banks and payment services have different rules for non-resident customers and businesses. Verify your eligibility and the product’s permitted payment uses rather than assuming that a USD account number establishes residency or universal access.

Can I receive every dollar payment with the same details?

No. The rail, sender, currency, purpose, and provider rules must match. Local ACH or wire instructions do not automatically support international Swift-routed payments.

Is FedNow available to every USD recipient?

No. Institution participation and the particular service’s implementation both matter. Confirm the exact receiving or payout route instead of selecting it based only on the currency.

Can I receive USD and withdraw another currency?

Some services support that combination. Check the conversion quote, destination, fees, verification, and timing for the complete route. Receiving currency coverage and payout currency coverage are separate capabilities.

Start with one real payer and one intended final destination. Once that journey is confirmed, you can document it and repeat it with other eligible payments using the same approved process.