What are SWIFT payments and how do they work?

If you're managing cross-border vendor payments, sending payroll abroad, or investing in overseas markets, it helps to understand SWIFT's role and the costs your bank or provider quotes. SWIFT is a financial-messaging network used by more than 11,500 institutions in more than 200 countries and territories to exchange standardized financial messages. It does not itself move funds. SWIFT describes its network and role here.

What is SWIFT?

The SWIFT network is a messaging system that lets financial institutions exchange standardized information about financial transactions. It does not hold customer accounts or transfer funds.

SWIFT was founded in 1973 and began operations in 1977 to replace Telex-based financial messages with more standardized and secure communications.

Over time, SWIFT has introduced or expanded:

• Business Identifier Codes (BICs), commonly called SWIFT codes
• Standardized message formats, including MT formats and ISO 20022 MX formats
• Security controls and customer-security requirements
• Global Payments Innovation (GPI) services that can improve tracking and transparency when the participating banks support them

Standardized messages can reduce manual re-keying and make it easier for banks and businesses to reconcile cross-border payments. Actual speed and automation depend on the banks, payment route, and systems involved.

What are SWIFT payments?

SWIFT payments are international transfers in which banks use the SWIFT network to exchange payment instructions. The funds are settled by the banks, often through accounts they maintain with one another or with correspondent banks.

SWIFT's standardized messages help banks communicate payment details consistently. That can support reconciliation and automated workflows, but it does not eliminate the need for accurate recipient, currency, and compliance information.

Core components of a SWIFT payment can include:

• Standardized messaging: Banks use defined formats to communicate payment instructions. An MT103 has traditionally been used for single customer credit transfers, while ISO 20022 MX messages are now the standard for cross-border payment instructions on SWIFT's CBPR+ service.
• Global reach: The network connects more than 11,500 institutions in more than 200 countries and territories. Whether a specific recipient can receive a payment depends on its bank, currency, local rules, and the available payment route.
• Multi-currency processing: A cross-border payment may require currency conversion, which is priced by the bank or provider.
• Security infrastructure: SWIFT provides secure messaging; participating financial institutions remain responsible for their own controls, customer due diligence, and payment processing.
• Traceability: Banks may provide a payment reference and, for eligible gpi payments, tracking information. The degree of visibility depends on the participating institutions and route.
• Compliance data: Payment messages can carry originator, beneficiary, remittance, and regulatory information that banks use in their compliance processes.

What are SWIFT codes?

SWIFT codes, also called BICs (Business Identifier Codes), identify financial institutions in SWIFT messages. A BIC is either eight or 11 characters long. The optional final three characters identify a branch or other location; XXX generally denotes the primary office.

A SWIFT/BIC code has four parts:

1. Institution code (four characters): Identifies the institution, such as CHAS for JPMorgan Chase.
2. Country code (two characters): Identifies the country, such as US for the United States.
3. Location code (two characters): Identifies a location or other distinguishing element under the BIC standard.
4. Branch code (three characters, optional): Identifies a branch or XXX for the primary office.

When you send or receive a cross-border payment, your bank or provider may ask for a BIC and, where relevant, the recipient's international bank account number (IBAN). Requirements vary by destination, currency, and receiving bank.

For example, CHASUS33XXX breaks down as:

• CHAS: Institution code for JPMorgan Chase
• US: Country code for the United States
• 33: Location code
• XXX: Primary office

How do SWIFT payments work?

A SWIFT payment works by transmitting secure, standardized payment instructions between banks. The banks—not SWIFT—move and settle the funds, often through correspondent-banking relationships.

International banking commonly uses Nostro and Vostro accounts. The terms describe the same account from opposite perspectives:

• Nostro account: “Our account with you”—a bank's account held at another bank, often in that other bank's local currency.
• Vostro account: “Your account with us”—the same account from the bank that holds it.

For example, a U.S. bank may maintain a euro account with a German bank. That account is the U.S. bank's Nostro account and the German bank's Vostro account. These relationships help banks make international payments without maintaining branches in every country.

Here's how a SWIFT payment typically works:

• Instruction creation: Your bank or provider creates a payment instruction with the amount, currency, beneficiary, and required remittance or regulatory information.
• Message transmission: The sending bank exchanges the instruction with the receiving bank and, if needed, correspondent banks through SWIFT.
• Correspondent settlement: If the banks do not have a direct relationship, one or more correspondent banks may help settle the payment. The specific route is determined by the banks and available accounts; it is not chosen by the SWIFT network.
• Account crediting: After the receiving bank completes its checks and receives settlement, it credits the beneficiary according to its procedures.
• Confirmation and tracking: The sending bank or provider may provide a reference number and, where available, tracking updates.

Unlike domestic transfers such as ACH payments in the United States or SEPA credit transfers in Europe, cross-border payments may require correspondent banks, currency conversion, and additional compliance checks. These factors can affect timing and cost.

Common sources of delay include cut-off times, compliance review, missing or mismatched beneficiary details, currency conversion, public holidays, and intermediary banks.

When do you need to use SWIFT payments?

You may use SWIFT when a bank-to-bank payment crosses borders and the sending and receiving institutions use SWIFT for the chosen route. It is one option for paying overseas vendors, collecting funds from international customers, or moving money among international entities. It is not the only cross-border payment method.

Other common scenarios include:

• Paying foreign contractors or service providers
• Paying international employees or expatriate staff
• Paying dividends to international shareholders
• Settling cross-border merger and acquisition transactions

How to send a SWIFT payment

Sending a SWIFT payment follows the general process for an international wire transfer. Confirm the required details, fees, exchange rate, and approval requirements with your bank or provider before authorizing the payment.

1. Gather the recipient's details: You may need the beneficiary's full legal name, account number or IBAN, bank name, SWIFT/BIC code, address, and payment purpose. Exact requirements vary by destination and bank.
2. Initiate the payment with your bank or provider: Most business-banking platforms support international wires, though availability and setup requirements vary.
3. Enter the transfer details: Provide the recipient information, amount, currency, and available charge instruction. Banks commonly use OUR (sender pays), SHA (shared charges), or BEN (beneficiary pays), subject to the bank's and corridor's rules.
4. Review and authorize: Check the BIC, account number or IBAN, beneficiary name, payment purpose, fees, and exchange rate. Errors can cause delays, repair requests, or returned payments.
5. Track the transfer: Keep the bank's reference number. If the route supports gpi tracking, your bank may be able to provide status updates.

How you initiate and approve an international wire also depends on your organization:

• Small businesses: Online banking and owner or administrator approvals may be sufficient.
• Mid-size enterprises: Treasury systems, payment batches, and dual approvals are common.
• Large corporations: Enterprise resource planning (ERP) systems, treasury systems, multi-level approvals, and direct bank connections may be used.

If you regularly send international transfers, consider Ramp Bill Pay, which automates approvals and consolidates international wire transfers alongside domestic payments.

Fees and costs of SWIFT transactions

There is no universal price for a SWIFT payment. The sending bank, receiving bank, correspondent banks, and foreign-exchange provider may each set charges. Ask your bank or provider for a pre-payment quote that identifies the fee, exchange rate, charge instruction, and the amount the beneficiary is expected to receive.

Potential cost components include:

• A sending-bank or provider fee
• A receiving-bank fee, if applicable
• Correspondent or intermediary-bank deductions, if applicable
• Foreign-exchange spread or conversion fee

The charge instruction can affect who bears charges:

• OUR: The sender instructs that it will bear charges, though the final amount and treatment depend on the banks and route.
• SHA: The sender and beneficiary each bear the charges charged to them.
• BEN: Charges are deducted from the payment amount, where permitted.

To manage cost:

• Compare the total quote, including the exchange rate, rather than the stated transfer fee alone.
• Confirm whether the beneficiary must receive an exact amount.
• Use an account in the payment currency when that is operationally and economically appropriate.
• Review payment volume and pricing with your bank or provider if you make recurring international transfers.

Unexpected deductions can complicate reconciliation. Effective accounts receivable management includes matching the amount sent, the amount received, exchange-rate treatment, and any bank charges.

Benefits of SWIFT

SWIFT's global messaging reach, standardized formats, and security controls make it a common infrastructure component of cross-border bank payments.

1. Traceability: Banks can provide payment references, and eligible gpi payments may provide additional status information.
2. Operational consistency: Standardized messages can reduce manual re-keying and support automated payment and reconciliation workflows.
3. Structured information: Payment messages can carry originator, beneficiary, remittance, and regulatory information that helps institutions process and review transactions.

The operational benefit varies by the participating banks and a business's own systems. For example, standardized documentation may help manufacturing teams reconcile supplier payments, while structured remittance information can help healthcare organizations match payments to invoices.

Drawbacks of SWIFT

SWIFT-based payments can involve multiple institutions, currency conversion, and jurisdiction-specific checks. That can make timing, fee allocation, and end-to-end visibility less predictable than a domestic payment on a single rail.

Three common considerations are:

1. Variable timing: Cut-off times, holidays, compliance review, and correspondent banks can extend delivery time.
2. Route-dependent visibility: gpi can improve tracking, but the information available depends on the participating institutions and route.
3. Potentially higher total cost: Bank, intermediary, and foreign-exchange charges can make a cross-border payment more expensive than a domestic transfer.

For certain corridors, alternatives may offer faster delivery or a different cost structure. Multi-currency accounts can reduce the need to convert funds repeatedly, while payment providers may offer local-payment options in supported markets. Businesses expanding into new markets, such as those launching operations in Canada, can evaluate local payment rails alongside bank wires.

Domestic options such as SEPA credit transfers for euro payments in the SEPA area, and Fedwire Funds Service or CHIPS for domestic U.S. dollar wires, serve different purposes from SWIFT. Availability, delivery time, and fees depend on the payment type and participating financial institutions.

SWIFT payments vs. wire transfers

A wire transfer is a broad term for an electronic bank-to-bank payment. SWIFT is a messaging network that many institutions use to exchange instructions for cross-border wires. Domestic U.S. wires may use Fedwire Funds Service or CHIPS, while ACH and SEPA are separate payment schemes.

The right option depends on the currency, destination, delivery deadline, recipient-bank requirements, and total quoted cost.

SWIFT payments and compliance

Banks and payment providers have their own legal and regulatory obligations when processing international payments. SWIFT provides messaging infrastructure; it does not replace the compliance responsibilities of participating institutions or their customers.

Anti-money laundering and Know Your Customer requirements

Payment instructions can include originator, beneficiary, remittance, and regulatory information. Banks may use this information, along with their customer records and transaction-monitoring processes, to meet anti-money-laundering and counter-financial-crime obligations.

Your bank may request information or supporting documents for a payment, particularly when a recipient, payment purpose, or transaction pattern requires review. Requirements vary by institution, jurisdiction, and transaction.

Sanctions screening

Financial institutions screen payments under the sanctions laws and policies that apply to them. A SWIFT message is not itself a sanctions clearance, and it is inaccurate to assume that every message receives the same screening or that a payment will be blocked solely because it involves a country.

Before a high-value or higher-risk payment, verify the recipient and transaction with your compliance team and bank. For U.S. sanctions information, consult OFAC's Sanctions Programs and Country Information.

SWIFT Customer Security Programme

SWIFT's Customer Security Programme establishes security-control requirements and an annual attestation process for in-scope SWIFT users. Its controls address areas such as secure environments, access controls, and threat detection. SWIFT's Customer Security Programme explains the current framework.

For a business using a bank or payment provider, this is part of the provider's SWIFT environment; it does not eliminate the need for your own payment controls, such as verified beneficiary changes and approval workflows.

The future of SWIFT

SWIFT continues to develop its tracking, API, and data capabilities. The practical effect for a business depends on its bank, payment routes, and systems.

SWIFT's cross-border payment service has completed its migration to ISO 20022 messaging. The end of the MT/MX coexistence period for cross-border payments and reporting was November 2025. ISO 20022 can support more structured data, but better reconciliation still depends on how banks and businesses populate, pass through, and use that data. See SWIFT's ISO 20022 resources for the current migration information.

SWIFT gpi can provide improved tracking and fee transparency for eligible payments. Do not assume same-day delivery or full end-to-end visibility: both remain route- and participant-dependent.

SWIFT Go is a service for participating institutions that aims to make eligible low-value cross-border payments more predictable. It does not establish a universal dollar limit, fee, or delivery time; availability and terms depend on the participating institution and corridor. SWIFT Go provides the current service details.

Simplify SWIFT payment management with Ramp

If you're managing cross-border vendor payments, understanding how SWIFT works is key to ensuring funds arrive accurately and on time. But coordinating international wire transfers across multiple bank portals, chasing approvals over email, and manually reconciling payments in your accounting system eats into time you could spend on higher-value work.

Ramp Bill Pay lets you initiate international wire transfers in U.S. dollars through the SWIFT network, giving you control and transparency from a single platform. You can set up automated approval workflows so the right people sign off before a payment goes out, and every transaction syncs directly to your general ledger without manual data entry. Ramp's AP Agent also flags anomalies before payment, so your team isn't doing manual review on every invoice.

Bill Pay processes invoices 2.4x faster than legacy software, with 86% fewer clicks to process bills. Whether you're paying vendors in the U.S. or abroad, you get a single view of all your payables, domestic and international, in one place.

Try an interactive demo to see how Ramp simplifies international payment management.