
You can receive a SWIFT transfer in Armenia through a bank that accepts the payment’s currency, origin and purpose. Give the sender your bank’s current receiving instructions, including any intermediary details. If you have an eligible US account supporting ACH, or a euro account supporting SEPA, a compatible payer may use that route instead. Your location in Armenia does not determine the receiving rail; the account and the sender’s payment method do.
A company in the United States wants to pay your invoice. You live in Yerevan and have a USD account at an Armenian bank. The company asks for a routing number so it can pay by ACH. You send the bank’s SWIFT code instead.
The currencies match, but the payment instructions do not.
This is where international payments become confusing. A dollar account can be in Armenia, the United States or another country. Each account can accept different transfer types. Understanding that distinction helps you avoid rejected payments, unnecessary conversions and repeated bank charges.
This guide is for people living, working or managing payments in Armenia, including foreign residents, contractors and individual entrepreneurs. It covers receiving and sending international bank payments, and how local US or European receiving details can change the client’s payment route.
Your client’s payment method matters as much as the currency.
If they want to pay by ACH or SEPA, check whether your walllet.com account gives you a compatible receiving option before sending bank details.

What is SWIFT and why do banks use it?
SWIFT is the Society for Worldwide Interbank Financial Telecommunication. Its network lets financial institutions exchange standardized financial messages, including payment instructions. The institutions handling the payment move and credit the funds. SWIFT itself does not hold your money or operate your personal account.
Banks use this common language to communicate across countries and currencies. Your bank can instruct another institution to pay a named beneficiary, identify the relevant accounts and communicate information needed to process the transfer.
A SWIFT payment to Armenia may follow this simplified route:
Sender → sending bank → correspondent bank → Armenian receiving bank → your account
Some payments take a shorter route. Others involve additional institutions. A correspondent bank provides banking services to another bank; an intermediary is the institution handling a particular payment between the sending and receiving banks.
SWIFT remains useful when the payer needs to send directly to an Armenian bank account, when the payment currency is outside the scope of a local alternative, or when the payer’s finance department supports international wires as its approved method.
The tradeoff is that the payment can involve several institutions with separate prices and processing requirements. A fee shown by the sending bank may cover only its part of the transfer.
Can Armenian banks receive international SWIFT transfers?
Yes. Armenian banks publish SWIFT services and currency-specific receiving instructions. Acceptance still depends on the receiving account, the originating bank, the currency and the transaction. An account being open does not establish that every incoming payment will be accepted.
For example, Evocabank describes its international SWIFT transfer service, while Inecobank publishes correspondent-bank instructions by currency.
Before a client pays, confirm four details with your Armenian bank:
Whether the account accepts the invoice currency without automatic conversion.
Whether the bank accepts payments from the sender’s country and institution.
Whether the account permits the payment’s purpose, such as salary, consulting income or a transfer of your own savings.
Whether supporting documents or specific references are required.
Explain the intended activity accurately. A recurring business payment can require a different account arrangement from a personal transfer. If you need to establish the account first, use the separate guide to opening a USD bank account in Armenia as a foreigner.
Does an Armenian USD account support ACH or SEPA?
Holding USD in an Armenian account does not make that account reachable through US domestic ACH. Holding EUR does not automatically make an Armenian account a SEPA destination.
ACH is a US payment network. A US client can send an ACH credit only through an arrangement that supports the relevant receiving details. An Armenian bank’s dollar correspondent relationship does not give each Armenian customer a personal US ACH account.

SEPA payment schemes concern euro payments between participating payment service providers. Armenia is absent from the European Payments Council’s published SEPA geographical scope, reviewed on 5 October 2026.
Someone living in Armenia may nevertheless qualify for a separate account with a provider in the SEPA area. That account’s eligibility and payment support determine whether it can receive SEPA. The person’s physical location does not turn the Armenian bank account into the European receiving account.
Payment arrangement | Route to confirm | What the account label does not prove |
|---|---|---|
USD account at an Armenian bank | USD international wire instructions | US domestic ACH support |
EUR account at an Armenian bank | EUR international wire instructions | SEPA participation |
Eligible US receiving account | ACH credit or another explicitly supported US rail | Acceptance of every payer or international wire |
Eligible euro receiving account in the SEPA area | SEPA Credit Transfer; instant support separately | Support for USD or every international payment |
Ask for the accepted payment method before asking for the account currency.
What is the difference between a SWIFT code, an IBAN and an account number?
A SWIFT/BIC identifies an institution or business party. An account number identifies the relevant account. An IBAN is a standardized international account identifier used by countries that have adopted an IBAN format.
A BIC has eight characters, with an optional three-character branch identifier. The presence of a BIC alone does not establish that a provider accepts every SWIFT payment. Swift’s BIC documentation also distinguishes connected and non-connected BICs.
Armenia is not listed in the Swift IBAN Registry, Release 103, September 2026. Use the Armenian account format your bank supplies. Never create an IBAN by adding an “AM” prefix.
A receiving instruction sheet can include an overseas correspondent account or IBAN. That identifier may belong to the Armenian bank’s account at the correspondent bank. It is not automatically your personal receiving account.
For instance, ARMECONOMBANK’s SWIFT instructions show overseas correspondent details alongside the Armenian bank’s information. Copying a correspondent IBAN into a form intended for your personal beneficiary account can misidentify the destination.

If the sender’s form requires an IBAN and has no account-number option, the sender should confirm with its bank how to enter your Armenian instructions. A mandatory field is a compatibility issue to resolve before sending money.
How do you receive a SWIFT transfer in Armenia?
Start with a receiving instruction sheet generated or confirmed by your bank for the exact currency. A public SWIFT code lookup is insufficient for a complete payment instruction.
1. Confirm the account and payment purpose
Tell the bank who will pay, from which country, in which currency and for what reason. For recurring income, describe the expected frequency and amounts. Confirm that your personal, individual entrepreneur or company account is suitable for that activity.
2. Obtain the complete beneficiary instructions
Depending on the route, the sender may need:
Your exact beneficiary name and address.
Your beneficiary account number.
The receiving bank’s name, address and SWIFT/BIC.
The intermediary bank’s information and correspondent account details, where required.
The amount, currency and a truthful payment purpose or reference.
Use the spelling and account structure shown by the bank. Do not substitute a card number for an account number.
3. Keep the intermediary and beneficiary fields separate
Inecobank’s USD instruction sheet names the Bank of New York Mellon as intermediary and separately identifies the beneficiary’s account. The sheet states that its full information is mandatory and that incomplete information may lead to rejection.
Inecobank’s EUR sheet names Commerzbank as intermediary. This illustrates why you should obtain the instructions for the invoice currency instead of reusing the dollar sheet for euros.
These are examples of published routing, not instructions to send money to a generic bank account. Obtain your own current beneficiary details.
4. Agree who pays the charges
Decide whether the invoice must arrive as a specific net amount. Ask the payer’s bank which charge options it supports and whether its quote includes intermediary and receiving-bank charges. Record the agreement before the transfer.
5. Send one clear payment instruction
Keep ACH, SEPA and SWIFT instructions separate. A finance team should not have to choose between several account numbers or infer which bank is the final beneficiary. The guide to bank details for an international payment explains the differences between instruction sets.
6. Retain the confirmation and reconcile the credit
Ask the sender to retain the bank’s transfer confirmation and reference. Once funds arrive, compare the currency and credited amount with the invoice. Check whether the balance is available for use and whether fees were charged separately.
A small first payment can expose a naming or routing problem before a larger invoice. It still has costs and does not guarantee that every later payment will pass the same checks.
A payment instruction you can adapt
Use this format only after replacing the fields with your bank’s verified information:
Payment method: International bank transfer via SWIFT
Invoice reference: [invoice number]
Amount and currency: [agreed amount and supported currency]
Beneficiary name: [exact name supplied by the bank]
Beneficiary address: [address supplied or confirmed by the bank]
Beneficiary account number: [your account number]
Beneficiary bank: [bank name and address]
Beneficiary bank SWIFT/BIC: [bank-confirmed code]
Intermediary bank: [include only if required]
Correspondent details: [copy exactly where required]
Payment purpose: [accurate description linked to the invoice or contract]
Charge arrangement: [agreed option supported by the sending bank]
Please confirm before changing the currency, route or beneficiary information.
Who pays SWIFT fees under OUR, SHA and BEN?
OUR, SHA and BEN describe how transfer charges are allocated. They do not specify a universal price, and not every bank or payment type offers every option.
Charge option | General allocation | What to confirm before payment |
|---|---|---|
OUR | Sender bears the relevant bank charges | Whether the quoted service delivers the agreed net amount |
SHA | Sender pays its own bank’s charges; beneficiary bears the applicable other-side charges | Which charges can reduce the recipient’s credit |
BEN | Beneficiary bears the transfer charges | How deductions affect the amount arriving |
These general meanings are reflected in HSBC’s explanation of charge codes. The bank’s available options and applicable rules still control the specific payment.
OUR deserves particular attention when an invoice must arrive in full. Standard OUR is not a universal guarantee against every deduction. Some banks distinguish it from a guaranteed-full-amount service.
For example, Evocabank lists a separate USD Guaranteed OUR option. Before choosing it, obtain the terms for the exact payment rather than assuming the acronym alone settles the issue.
If a payment arrives short, use the guide to intermediary bank deductions and short international wires to separate a sender fee, a deduction from the principal and an incoming-account charge.
How much does a SWIFT transfer in Armenia cost?
There is no single retail SWIFT fee for Armenia. Price the sender’s service, any intermediary deductions, the receiving account and any later conversion or withdrawal separately.
One current bank example shows why the details matter. Evocabank’s published transfer tariff, displaying an update of 1 October 2026 and checked on 5 October, lists:
Evocabank outgoing service | Published tariff |
|---|---|
Standard USD OUR, excluding Russia and Belarus | 0.15%; minimum AMD 7,000; maximum AMD 70,000 |
USD Guaranteed OUR | Applicable OUR fee plus AMD 10,000 |
USD BEN | AMD 5,000 |
These are outgoing tariffs, not a quote for receiving money at every Armenian bank. Currency, destination and special routing can change the applicable fee. Obtain a transaction-specific quote.
How to compare the full cost
Use the same invoice value and the same final destination for each option. Compare how much the payer spends and how much usable value reaches you. Include conversion and the next transfer if you need the money in an Armenian bank.

For illustration only, suppose a $2,000 payment incurs a $25 sender fee paid separately, an $18 intermediary deduction and a $7 receiving deduction. The payer spends $2,025 and the recipient receives $1,975. Total transfer charges are $50, or 2.5% of the invoice. Conversion into AMD would add another cost if required.
Those figures are hypothetical, not Armenian bank tariffs or walllet.com prices.
An alternative with a small incoming fee can still cost more after conversion and withdrawal. Conversely, a SWIFT route with a higher advertised sender fee can be competitive if it delivers the needed currency directly to your intended account.
Before you choose the cheapest-looking route, compare where your money actually ends up.
See which receiving options are available in walllet.com, then compare the incoming method, fees and what you can do with the money after it arrives.

How long does a SWIFT payment to Armenia take?
The bank’s quoted delivery window is more useful than a universal promise. Ask when the sender’s bank will release the payment and when the Armenian bank expects to make the money available.
Swift reports that 90% of payments on its network reach the end bank within an hour. That statistic concerns arrival at the bank. It does not promise that the customer can use the funds within an hour.
The receiving bank may need information before crediting or releasing the payment. Cutoff times, banking holidays and the currency’s processing calendar can also affect the route. Swift’s explanation of the last mile of a cross-border payment describes why delivery to a bank and availability to a customer can differ.
For Armenia, check the receiving bank’s business day as well as the sending country’s calendar. A payment submitted near the sender’s Friday cutoff may enter the route later than the client expects. The guide to international transfer business days explains how to count the relevant processing days.
Keep the stages separate: submitted, released by the sending bank, received by the destination bank, credited, and available. A message saying “sent” describes only one part of that sequence.
Why might an Armenian bank ask for an invoice or contract?
A bank may need to verify the transaction’s purpose, the source of funds or whether the activity fits the account. Araratbank’s SWIFT terms state that the bank may request additional documents and information for customer due diligence.
For a service payment, retain the contract or order, the invoice, the payer’s identity and the bank confirmation. The payer’s name, amount and reference should connect to the underlying work. If an agency or payroll provider pays on the client’s behalf, keep the document explaining that relationship.
For a transfer of savings, the relevant evidence may instead be a statement showing how you acquired and held the money. The documents should explain the actual transaction.
Ask the bank what is missing, how to submit it and whether a translation is required. A generic folder of unrelated paperwork can make the payment harder to understand.
Using a US or European receiving account does not remove identity checks, payer restrictions or transaction review. Nor does it decide how the income must be reported. Account permission, payment processing and tax treatment are separate matters.
What should you do if the SWIFT transfer is missing or returned?
Locate the payment before arranging another transfer. A duplicate payment can create a second fee and a second investigation.
Current information | Practical next action |
|---|---|
The sender has only an app screenshot | Obtain the bank-issued confirmation, release date and reference |
The sender’s bank confirms release | Request the UETR and the available payment-message details |
The Armenian bank has the payment but needs information | Submit the requested evidence through the bank’s official channel |
The Armenian bank cannot locate the payment | Give it the identifying details; have the sender request a trace |
The payment was returned | Obtain the reason and confirm the returned amount before resending |
Funds arrived in a smaller amount | Request a breakdown of deductions and check the charge instruction |
A Unique End-to-end Transaction Reference, or UETR, is a 36-character identifier used to trace a payment through the chain. Ask the sending bank to provide it and use the same reference in communication with both banks.
In 2026, request the bank’s available payment confirmation rather than insisting that every payment must have a native MT103. Swift’s cross-border payment instruction migration to ISO 20022 completed on 22 November 2025. A bank may provide pacs.008-related information or a customer-facing representation. Swift’s migration announcement confirms the transition.
Neither a reference nor a payment-message copy by itself proves that the funds are available in your account. For deeper investigation, use the guide to tracing a missing wire with a UETR or MT103.
If the case stalls, send the Armenian bank one consistent record: payer, beneficiary, amount, currency, release date, reference, payment purpose and prior case number. Request a written status and a clear explanation of what action is required. The missing-payment evidence pack provides a reusable structure.

How do you send a SWIFT transfer from Armenia?
Use your Armenian bank’s supported branch or digital channel and obtain the destination bank’s instructions from the recipient. A European destination does not automatically turn an outgoing Armenian bank payment into SEPA.
First verify the recipient’s name, account identifier, bank and any intermediary details. Select the supported currency and an accurate payment purpose. If you are paying an invoice, attach the documentation your bank requires and agree who pays the charges.
Before confirming, review the total debit, conversion rate if applicable, expected delivery window and charge option. Save the payment confirmation and reference after submission.
ARMECONOMBANK lists the information needed for a SWIFT order, including the sender’s account, currency, beneficiary information, intermediary details where applicable and payment details. Your bank’s exact form may differ.
If the recipient is using a fintech receiving account, verify that it accepts incoming SWIFT. ACH-only or SEPA-only instructions cannot be used as a substitute. This is particularly relevant to walllet.com: it does not offer SWIFT transfers, so a SWIFT payment should not be sent to its receiving details.
When can you get paid without SWIFT while living in Armenia?
You can avoid a SWIFT client payment when the payer can use a supported local or regional rail to a receiving account you are eligible to use. The strongest examples are a US ACH credit and a euro SEPA credit transfer.
A US client pays a US receiving account
Suppose you live in Yerevan and invoice a US company in USD. If you have eligible US receiving details that support incoming ACH credits and accept that company’s payment, the client may pay using ACH.
The client uses the ACH routing number and account number supplied for that route. Your address in Armenia does not require the client to send the money directly to an Armenian bank.
Nacha states that ACH credits can process on the same banking day, the following day or up to two business days, depending on scheduling. A provider can have its own availability and review process; network settlement timing is not a promise about when every app balance becomes usable.
A euro client pays a SEPA receiving account
If the payer can send EUR through SEPA and your eligible receiving account supports that payment, you may receive through SEPA Credit Transfer instead of an international wire to Armenia.
Use the provider’s exact beneficiary name, IBAN and reference instructions. Verify standard SEPA and SEPA Instant support separately. The EPC’s SEPA Instant scheme is designed for availability in less than ten seconds between participating providers; that does not establish that a particular app supports it.
The later transfer to Armenia is a separate decision
Receiving into a US or European account and moving the proceeds into an Armenian bank are two transactions.
The first can use ACH or SEPA. The second may require SWIFT, conversion into AMD or another supported payout method. Price and verify that second step before selecting the first.
Where does walllet.com fit into this payment route?
walllet.com is relevant when you want to receive through an eligible account route rather than ask the client to wire directly to Armenia. walllet.com does not offer SWIFT transfers. Its role must be evaluated through the incoming methods available for your account.
The walllet.com receiving-account page describes USD, EUR and GBP account details. The public site also explains that accounts and payments are provided through partners and that walllet.com is a financial technology company, not a bank.
For a supported local receiving route, the client can pay using the method shown in the app. If that route supports ACH for the US payment, or SEPA for the euro payment, the client’s incoming payment can avoid SWIFT.
Eligibility comes first. Being in Armenia does not by itself establish that you can open or use a particular walllet.com receiving account. Confirm your residence and nationality eligibility, payer rules, supported incoming rail, fees and limits before putting the details on an invoice. Also confirm how you can use or move the funds after receipt; an Armenian bank payout or AMD cash-out must not be assumed.
The walllet.com IBAN account guide explains the fields to verify and the distinction between the payment-account service and the crypto-wallet layer.
Check the receiving options available to your account in walllet.com, and use only the payment method shown for those details.
Which payment route fits your situation?
Choose based on the payer’s method and the account where you need the money to become usable.
Your situation | Route to investigate | Decisive check |
|---|---|---|
You need USD directly in your Armenian bank | Incoming USD SWIFT | Current beneficiary and intermediary instructions |
A US client can pay ACH and you have eligible US receiving details | ACH credit | Payer acceptance and the later route to usable money |
A client can pay EUR by SEPA and you have an eligible euro account | SEPA Credit Transfer | Receiving support and EUR terms |
A finance department only supports international wires | SWIFT-compatible receiving account | Avoid sending to local-only details |
You need money in AMD for local expenses | Compare complete routes ending in AMD | Conversion rate, payout availability and total deductions |
You are sending from an Armenian bank to an overseas account | Bank’s supported international transfer | Destination accepts the selected rail |
For a recurring payment, retain one dated instruction set per currency and route. When details change, tell the payer before the next invoice and confirm that its saved beneficiary record has been updated.
If your client does not need to pay directly into an Armenian bank, you may have another route.
Check the receiving methods available to your walllet.com account and use only the payment details and rails shown for your account.
See the receiving routes available to me
