The name Airtm US Virtual Account can lead to a simple but consequential misunderstanding: “US” describes part of the payment infrastructure, not a blanket eligibility statement for every US resident. A product can help someone receive a transfer from a US bank while following a different set of rules from the US-user payout experience. Read the product’s audience and the account’s available features before comparing instructions.
Airtm’s product explainer describes receiving US-bank payments through assigned banking details and says additional verification is required. It also lists product-specific location restrictions. That is a feature description, not proof that the feature is enabled for your account. US Virtual Account explainer.
Three uses of “US” that should not be merged
- US payer: the company or person sending money is based in the United States.
- US payment rail: the transfer uses banking infrastructure described by the product.
- US resident: the recipient’s residence places them in a particular eligibility and product context.
Write those three facts separately in your notes. If you are a US resident receiving a partner payout, begin with the US-specific payout map, not a virtual-account tutorial written for a recipient abroad. If you are comparing products for a non-US recipient, check that person’s actual eligibility rather than treating your own account as a proxy.
Ask what kind of transfer the sender can make
The product FAQ says the US Virtual Account accepts supported transfers from US bank accounts and does not support SWIFT. The detailed receiving page distinguishes ACH, wire and FedNow. A generic instruction to “send a bank transfer” therefore leaves important questions unanswered. Product FAQ; receiving-rail reference.
Before a payer acts, establish the exact product, transfer type and current receiving instructions. Do not copy bank details from a blog or another account. Do not use a marketing page as a substitute for the details generated by the authorized account. This publication does not provide recipient bank information or accept payments on anyone’s behalf.
How to handle apparently contradictory pages
A broad landing page is usually written to introduce a product; a product FAQ narrows the mechanics; an account screen shows what is currently offered to that account. If they disagree, preserve the question rather than choosing the most appealing version. Contact the provider with the specific product, residence and transfer type, without sending private credentials.
For example, a page promising a fast transfer does not settle whether the sender’s bank supports the relevant rail. Likewise, a general fee percentage does not settle whether a different country, transfer type or intermediary adds a charge. The cost worksheet deliberately leaves room for those dependencies.
The takeaway for a US reader
Product names are not eligibility decisions. Confirm the service available to your actual account, then check the entire route and the final destination. When a feature is absent or a support answer is unclear, leave the payment uninitiated until the gap is resolved. Correctly identifying the product is a more useful first step than learning a sequence of buttons that may not apply.