Wikipedia

SWIFT

(Redirected from MT103)
For other uses, see Swift (disambiguation).

The Society for Worldwide Interbank Financial Telecommunication (Swift), legally S.W.I.F.T. SC, is a cooperative established in 1973 in Belgium (French: Société Coopérative) and owned by the banks and other member firms that use its service. SWIFT provides the main messaging network through which international payments are initiated.[2] It also sells software and services to financial institutions, mostly for use on its proprietary "SWIFTNet", and assigns ISO 9362 Business Identifier Codes (BICs), popularly known as "Swift codes".

S.W.I.F.T. SC
Company typeCooperative society[1]
IndustryTelecommunications
Founded3 May 1973; 51 years ago (1973-05-03)
HeadquartersLa Hulpe, Belgium
50°44′04″N 4°28′43″E / 50.73444°N 4.47861°E / 50.73444; 4.47861
Key people
  • Javier Perez-Tasso (CEO)
  • Graeme Munro (Board Chair)
ProductsFinancial telecommunication
Revenue1,024,000,000 Euro (2023) Edit this on Wikidata
Number of employees
>3,000
Websitewww.swift.com Edit this at Wikidata

As of 2018, around half of all high-value cross-border payments worldwide used the Swift network,[3] and in 2015, Swift linked more than 11,000 financial institutions in over 200 countries and territories, who were exchanging an average of over 32 million messages per day (compared to an average of 2.4 million daily messages in 1995).[4]

Swift is headquartered in La Hulpe near Brussels. It hosts an annual conference, called Sibos, specifically aimed at the financial services industry.

History

edit

Before SWIFT's establishment, international financial transactions were communicated over Telex, a public system involving manual writing and reading of messages.[5] SWIFT was set up out of fear of what might happen if a single private and fully American entity controlled global financial flows – which before was First National City Bank (FNCB) of New York – later Citibank. In response to FNCB's protocol, FNCB's competitors in the US and Europe pushed an alternative "messaging system that could replace the public providers and speed up the payment process".[6]

SWIFT was founded in Brussels on 3 May 1973. Individuals who played a key role in its creation included bankers Jan Kraa (at AMRO Bank) and François Dentz (at the Banque de l'Union Parisienne) as well as Carl Reuterskiöld and Bessel Kok, who became respectively its first two chairmen and chief executives.[2]: 14-16  It was initially supported by 239 banks in 15 countries. It soon started to establish common standards for financial transactions and a shared data processing system and worldwide communications network designed by Logica and developed by the Burroughs Corporation.[7] Fundamental operating procedures and rules for liability were established in 1975, and the first message was ceremonially sent by Prince Albert of Belgium on 9 May 1977.[2]: 19 

SWIFT's first non-European operations centre was inaugurated by Governor John N. Dalton of Virginia in 1979.[8] In 1989 SWIFT completed a monumental new head office building in La Hulpe, designed by Ricardo Bofill Taller de Arquitectura.[9]

Ownership and governance

edit

SWIFT's shareholding structure is adjusted every three years in proportion to volumes of activity incurred by the members, ensuring that the most active members get the most voice irrespective of geography; additional rules are aimed at ensuring some geographical diversity within the board of directors. The 25 directors are elected by the shareholders, on three-year terms with the renewal of one-third of the board every year; all directors are member representatives.[2]: 30-31 

As of May 2024, the members directly represented on the board of directors were JPMorgan Chase (chair), Lloyds Bank (deputy chair), Bank of China, BNP Paribas, BPCE, Citi, Clearstream, Commerzbank, Commonwealth Bank of Australia, Deutsche Bank, Euroclear, FirstRand, HSBC, ING, Intesa Sanpaolo, KBC, MUFG, NatWest, Nordea, Royal Bank of Canada, Santander, SEB, UBS (2 representatives following the acquisition of Credit Suisse), as well as the Association of Banks in Singapore.[10]

Operations

edit
 
SWIFT logo before 2023

Swift acts as a carrier of the "messages containing the payment instructions between financial institutions involved in a transaction".[2]: 35 [11] However, the organisation does not manage accounts on behalf of individuals or financial institutions, and it does not hold funds from third parties.[2]: 1-2  It also does not perform clearing or settlement functions.[2]: 1-2, 35 [11] After payment has been initiated, it must be settled through a payment system, such as TARGET2 in Europe.[2]: 36  In the context of cross-border transactions, this step often takes place through correspondent banking accounts that financial institutions have with each other.[2]: 35 

SWIFT means several things in the financial world:

  1. a secure network for transmitting messages between financial institutions;
  2. a set of syntax standards for financial messages (for transmission over SWIFTNet or any other network)
  3. a set of connection software and services allowing financial institutions to transmit messages over SWIFT network.

Under 3 above, SWIFT provides turn-key solutions for members, consisting of linkage clients to facilitate connectivity to the SWIFT network and CBTs or "computer-based terminals" which members use to manage the delivery and receipt of their messages. Some of the more well-known interfaces and CBTs provided to their members are:

  • SWIFTNet Link (SNL) software which is installed on the SWIFT customer's site and opens a connection to SWIFTNet. Other applications can only communicate with SWIFTNet through the SNL.
  • Alliance Gateway (SAG) software with interfaces (e.g., RAHA = Remote Access Host Adapter), allowing other software products to use the SNL to connect to SWIFTNet
  • Alliance WebStation (SAB) desktop interface for SWIFT Alliance Gateway with several usage options:
    1. administrative access to the SAG
    2. direct connection SWIFTNet by the SAG, to administrate SWIFT Certificates
    3. so-called Browse connection to SWIFTNet (also by SAG) to use additional services, for example, Target2
  • Alliance Access (SAA) and Alliance Messaging Hub (AMH) are the main messaging software applications by SWIFT, which allow message creation for FIN messages, routing and monitoring for FIN and MX messages. The main interfaces are FTA (files transfer automated, not FTP) and MQSA, a WebSphere MQ interface.
  • The Alliance Workstation (SAW) is the desktop software for administration, monitoring and FIN message creation. Since Alliance Access is not yet capable of creating MX messages, Alliance Messenger (SAM) has to be used for this purpose.
  • Alliance Web Platform (SWP) as new thin-client desktop interface provided as an alternative to the existing Alliance WebStation, Alliance Workstation (soon)[when?] and Alliance Messenger.
  • Alliance Integrator is built on Oracle's Java Caps which enables customer's back-office applications to connect to Alliance Access or Alliance Entry.
  • Alliance Lite2 is a secure and reliable, cloud-based way to connect to the SWIFT network which is a light version of Alliance Access specifically targeting customers with low volume of traffic.

Services

edit

There are four key areas that SWIFT services fall under in the financial marketplace: securities, treasury & derivatives, trade services, and payments & cash management.

Swift Ref, the global payment reference data utility, is SWIFT's unique reference data service. Swift Ref sources data directly from data originators, including central banks, code issuers and banks making it easy for issuers and originators to maintain data regularly and thoroughly. SWIFTRef constantly validates and cross-checks data across the different data sets.[13]

Operations centres

edit

The SWIFT secure messaging network is run from three data centres, located in the United States, the Netherlands, and Switzerland. These centres share information in near real-time. In case of a failure in one of the data centres, another is able to handle the traffic of the complete network. SWIFT uses submarine communications cables to transmit its data.[14]

Shortly after opening its third data centre in Switzerland in 2009,[15] SWIFT introduced a new distributed architecture with two messaging zones, European and Trans-Atlantic, so data from European SWIFT members no longer mirrored the U.S. data centre.[16] European zone messages are stored in the Netherlands and in part of the Swiss operating centre; Trans-Atlantic zone messages are stored in the United States and in another part of the Swiss operating centre that is segregated from the European zone messages. Countries outside of Europe were by default allocated to the Trans-Atlantic zone but could choose to have their messages stored in the European zone.

Data centres
SN SWIFT data centres Type
1 Zoeterwoude, Netherlands OPC (Operating Centre)
2 Culpeper, Virginia, United States OPC (Operating Centre)
3 Diessenhofen, Switzerland[17] OPC (Operating Centre)
4 Hong Kong Command and control

SWIFTNet network

edit

SWIFT moved to its current IP network infrastructure, known as SWIFTNet, from 2001 to 2005,[18] providing a total replacement of the previous X.25 infrastructure. The process involved the development of new protocols that facilitate efficient messaging, using existing and new message standards. The adopted technology chosen to develop the protocols was XML, which now provides a wrapper around all messages legacy or contemporary. The communication protocols can be broken down into:

SWIFT provides a centralized store-and-forward mechanism, with some transaction management. For bank A to send a message to bank B with a copy or authorization involving institution C, it formats the message according to standards and securely sends it to SWIFT. SWIFT guarantees its secure and reliable delivery to B after the appropriate action by C. SWIFT guarantees are based primarily on high redundancy of hardware, software, and people.

During 2007 and 2008, the entire SWIFT network migrated its infrastructure to a new protocol called SWIFTNet Phase 2. The main difference between Phase 2 and the former arrangement is that Phase 2 requires banks connecting to the network to use a Relationship Management Application (RMA) instead of the former bilateral key exchange (BKE) system. According to SWIFT's public information database on the subject, RMA software should eventually prove more secure and easier to keep up-to-date; however, converting to the RMA system meant that thousands of banks around the world had to update their international payment systems to comply with the new standards. RMA completely replaced BKE on 1 January 2009.

Standards

edit

SWIFT has become the industry standard for syntax in financial messages. Messages formatted to SWIFT standards can be read and processed by many well-known financial processing systems, whether or not the message travelled over the SWIFT network. SWIFT cooperates with international organizations to define standards for message format and content. SWIFT is also a registration authority (RA) for the following ISO standards:[19]

  • ISO 9362: 1994 Banking – Banking telecommunication messages – Bank identifier codes
  • ISO 10383: 2003 Securities and related financial instruments – Codes for exchanges and market identification (MIC)
  • ISO 13616: 2003 IBAN Registry
  • ISO 15022: 1999 Securities – Scheme for messages (Data Field Dictionary) (replaces ISO 7775)
  • ISO 20022-1: 2004 and ISO 20022-2:2007 Financial services – Universal Financial Industry message scheme

In RFC 3615 urn:swift: was defined as Uniform Resource Names (URNs) for SWIFT FIN.[20]

Supervision

edit

SWIFT is not a payment system and thus neither regulated nor supervised as such, but is nevertheless deemed to be systemically important and thus under the "oversight" of public authorities. In 1998, the so-called Group of Ten central banks (those of Belgium, Canada, France, Germany, Italy, Japan, the Netherlands, Sweden, Switzerland, the United Kingdom, the Federal Reserve Board and the Federal Reserve Bank of New York for the U.S. and the European Central Bank) started acting as joint overseers, with the National Bank of Belgium (NBB) in a lead role. The oversight focuses primarily on systemic risk, confidentiality, infrastructure security, and business continuity.[2]: 43  It is formalized in bilateral documents between the NBB and SWIFT on the one hand, and between the NBB and each of the other G10 central banks on the other hand.[21] In 2018, the International Monetary Fund has recommended that "the National Bank of Belgium should consider enhancing oversight with additional regulatory and supervisory powers."[22]

In 2012, this framework was complemented by a "SWIFT Oversight Forum" including additional central banks. As of 2024, in addition to the G10 central banks, the SWIFT Oversight Forum included the national central banks of Argentina, Australia, Brazil, China, Hong Kong, India, Indonesia, Korea, Mexico, Russia, Saudi Arabia, Singapore, South Africa, Spain, and Turkey. According to SWIFT, the Oversight Forum "provides a forum for the G-10 central banks to share information on Swift oversight activities with a wider group of central banks."[23]

Alternatives

edit

Purported alternatives to the SWIFT system include:[citation needed]

  1. CIPS: sponsored by China, for RMB-related deals. 1467 financial institutions in 111 countries and regions have connected to the system. The actual business covers more than 4,200 banking institutions in 182 countries and regions around the world.[24][25][26]
  2. SFMS: sponsored by India
  3. SPFS: developed by the Russian Federation[27]
  • Former. INSTEX: sponsored by the European Union, limited to non-USD transactions for trade with Iran, largely unused and ineffective.[28][29]Liquidated in March 2023.

Leadership

edit

Chair

edit
  • Johannes Kraa (AMRO Bank, Dutch), 1973-1974
  • François Dentz (Crédit du Nord, French), 1974-1976
  • Helmer Hasselblad (Swedish), 1976-1984
  • W. Robert Moore (Chemical Bank, American), 1984-1989
  • Richard Fröhlich (Austrian), 1989-1992
  • Eric C. Chilton (Barclays, British), 1992-1996
  • Jean-Marie Weydert (Société Générale, French), 1996-2000
  • Jaap Kamp (ABN AMRO, Dutch), 2000-2006
  • Yawar Shah (JPMorgan then Citi, American), 2006-2022[2]: 16 
  • Mark Buitenhek (ING, Dutch), acting 2022-2023
  • Graeme Munro (JPMorgan, British), since 2023[30]

Chief Executive Officer

edit
  • Carl Reuterskiöld, 1973-1983
  • Bessel Kok, 1983-1991
  • Jacques Cerveau (interim CEO), 1991
  • Leonard (Lennie) Schrank, 1992-2007
  • Lazaro Campos, 2007-2012
  • Gottfried Leibbrandt, 2012-2019[2]: 17 
  • Javier Pérez-Tasso, since 2019[31]

Controversy

edit

Inefficiency

edit

Swift has been criticised for inefficiency. In 2018, the London-based Financial Times noted that transfers frequently "pass through multiple banks before reaching their final destination, making them time-consuming, costly and lacking transparency on how much money will arrive at the other end".[3] Swift has since introduced an improved service called "Global Payments Innovation" (GPI), claiming it was adopted by 165 banks and was completing half its payments within 30 minutes.[3] The new standard which included Swift Go was supposed to be utilised in receiving and transferring low-value international payments. One of the significant changes was the transaction amount, which would not differ from start to end. However, as of 2023, uptake was mixed. For instance, Alisherov Eraj, Alif Bank Treasury Department Swift Transfers & Banking Relationship Expert in the Republic of Tajikistan, describes that the leading cause for the late Swift Go adoption in Tajikistan was the Core Banking System itself. To connect to Swift Go, he adds, banking system interfaces needed to be upgraded and integrated with their software to be fully compatible; this hindered many banks from adopting the technology earlier.

U.S. government surveillance

edit

A series of articles published on 23 June 2006 in The New York Times, The Wall Street Journal, and the Los Angeles Times revealed a program, named the Terrorist Finance Tracking Program, which the US Treasury Department, Central Intelligence Agency (CIA), and other United States governmental agencies initiated after the 11 September attacks to gain access to the SWIFT transaction database.[32]

After the publication of these articles, SWIFT quickly came under pressure for compromising the data privacy of its customers by allowing governments to gain access to sensitive personal information. In September 2006, the Belgian government declared that these SWIFT dealings with American governmental authorities were a breach of Belgian and European privacy laws.[citation needed]

In response, and to satisfy members' concerns about privacy, SWIFT began a process of improving its architecture by implementing a distributed architecture with a two-zone model for storing messages (see § Operations centres).

Concurrently, the European Union negotiated an agreement with the United States government to permit the transfer of intra-EU SWIFT transaction information to the United States under certain circumstances. Because of concerns about its potential contents, the European Parliament adopted a position statement in September 2009, demanding to see the full text of the agreement and asking that it be fully compliant with EU privacy legislation, with oversight mechanisms emplaced to ensure that all data requests were handled appropriately.[33] An interim agreement was signed without European Parliamentary approval by the European Council on 30 November 2009,[34] the day before the Lisbon Treaty—which would have prohibited such an agreement from being signed under the terms of the codecision procedure—formally came into effect. While the interim agreement was scheduled to come into effect on 1 January 2010, the text of the agreement was classified as "EU Restricted" until translations could be provided in all EU languages and published on 25 January 2010.

On 11 February 2010, the European Parliament decided to reject the interim agreement between the EU and the US by 378 to 196 votes.[35][36] One week earlier, the parliament's civil liberties committee had already rejected the deal, citing legal reservations.[37]

In March 2011, it was reported that two mechanisms of data protection had failed: EUROPOL released a report complaining that requests for information from the US had been too vague (making it impossible to make judgments on validity)[38] and that the guaranteed right for European citizens to know whether their information had been accessed by US authorities had not been put into practice.[38]

Der Spiegel reported in September 2013 that the National Security Agency (NSA) widely monitors banking transactions via SWIFT, as well as credit card transactions.[39] The NSA intercepted and retained data from the SWIFT network used by thousands of banks to securely send transaction information. SWIFT was named as a "target", according to documents leaked by Edward Snowden. The documents revealed that the NSA spied on SWIFT using a variety of methods, including reading "SWIFT printer traffic from numerous banks".[39] In April 2017, a group known as the Shadow Brokers released files allegedly from the NSA which indicate that the agency monitored financial transactions made through SWIFT.[40][41]

SWIFT and sanctions

edit

Iran

edit

In January 2012, the advocacy group United Against Nuclear Iran (UANI) implemented a campaign calling on SWIFT to end all relations with Iran's banking system, including the Central Bank of Iran. UANI asserted that Iran's membership in SWIFT violated US and EU financial sanctions against Iran as well as SWIFT's own corporate rules.[42]

Consequently, in February 2012, the U.S. Senate Banking Committee unanimously approved sanctions against SWIFT aimed at pressuring it to terminate its ties with blacklisted Iranian banks. Expelling Iranian banks from SWIFT would potentially deny Iran access to billions of dollars in revenue using SWIFT but not from using IVTS. Mark Wallace, president of UANI, praised the Senate Banking Committee.[43]

Initially SWIFT denied that it was acting illegally,[43] but later[when?] said that "it is working with U.S. and European governments to address their concerns that its financial services are being used by Iran to avoid sanctions and conduct illicit business".[44] Targeted banks would be—amongst others—Saderat Bank of Iran, Bank Mellat, Post Bank of Iran and Sepah Bank.[45] On 17 March 2012, following an agreement two days earlier between all 27 member states of the Council of the European Union and the Council's subsequent ruling, SWIFT disconnected all Iranian banks that had been identified as institutions in breach of current EU sanctions from its international network and warned that even more Iranian financial institutions could be disconnected from the network.

In February 2016, most Iranian banks reconnected to the network following the lift of sanctions due to the Joint Comprehensive Plan of Action.[46]

Israel

edit

In 2014, SWIFT rejected calls from pro-Palestinian activists to revoke Israeli banks' access to its network owing to the Israeli occupation of Palestinian territory.[47]

Russia and Belarus

edit
See also: SWIFT ban against Russian banks

Similarly, in August 2014 the UK planned to press the EU to block Russian use of SWIFT as a sanction due to Russian military intervention in Ukraine.[48] However, SWIFT refused to do so.[49] SPFS, a Russian alternative to SWIFT, was developed by the Central Bank of Russia as a backup measure.[50]

During the prelude to the 2022 Russian invasion of Ukraine, the United States developed preliminary possible sanctions against Russia, but excluded banning Russia from SWIFT.[51] Following the 2022 Russian invasion of Ukraine, the foreign ministers of the Baltic states Lithuania, Latvia, and Estonia called for Russia to be cut off from SWIFT. However, other EU member states were reluctant, both because European lenders held most of the nearly $30 billion in foreign banks' exposure to Russia and because Russia had developed the SPFS alternative.[52] The European Union, United Kingdom, Canada, and the United States finally agreed to remove a few Russian banks from the SWIFT messaging system in response to the 2022 Russian invasion of Ukraine; the governments of France, Germany, Italy and Japan individually released statements alongside the EU.[53][11]

On 20 March 2023, the Russian Federation banned the use of SWIFT.[54][55]

The European Union issued the first set of sanctions against Belarus - the first was introduced on 27 February 2022, which banned certain categories of Belarusian items in the EU, including timber, steel, mineral fuels and tobacco.[56] After the Lithuanian prime minister proposed disconnecting Belarus from SWIFT,[57] the European Union, which does not recognise Lukashenko as the legitimate President of Belarus, started to plan an extension of the sanctions already issued against Russian entities and top officials to its ally.[58]

Security

edit
See also: Bangladesh Bank robbery

In 2016 an $81 million theft from the Bangladesh central bank via its account at the New York Federal Reserve Bank was traced to hacker penetration of SWIFT's Alliance Access software, according to a New York Times report. It was not the first such attempt, the society acknowledged, and the security of the transfer system was undergoing new examination accordingly.[59] Soon after the reports of the theft from the Bangladesh central bank, a second, apparently related, attack was reported to have occurred at a commercial bank in Vietnam.[60][61]

Both attacks involved malware written to both issue unauthorized SWIFT messages and to conceal that the messages had been sent. After the malware sent the SWIFT messages that stole the funds, it deleted the database record of the transfers and then took further steps to prevent confirmation messages from revealing the theft. In the Bangladeshi case, the confirmation messages would have appeared on a paper report; the malware altered the paper reports when they were sent to the printer. In the second case, the bank used a PDF report; the malware altered the PDF viewer to hide the transfers.[60]

In May 2016, Banco del Austro (BDA) in Ecuador sued Wells Fargo after Wells Fargo honoured $12 million in fund transfer requests that had been placed by thieves.[61] In this case, the thieves sent SWIFT messages that resembled recently cancelled transfer requests from BDA, with slightly altered amounts; the reports do not detail how the thieves gained access to send the SWIFT messages. BDA asserts that Wells Fargo should have detected the suspicious SWIFT messages, which were placed outside of normal BDA working hours and were of an unusual size. Wells Fargo claims that BDA is responsible for the loss, as the thieves gained access to the legitimate SWIFT credentials of a BDA employee and sent fully authenticated SWIFT messages.[61]

In the first half of 2016, an anonymous Ukrainian bank and others—even "dozens" that are not being made public—were variously reported to have been "compromised" through the SWIFT network and to have lost money.[62]

In March 2022, Swiss newspaper Neue Zürcher Zeitung reported about the increased security precautions by the State Police of Thurgau at the SWIFT data centre in Diessenhofen. After most of the Russian banks had been excluded from the private payment system, the risk of sabotage was considered higher. Inhabitants of the town described the large complex as a "fortress" or "prison" where frequent security checks of the fenced property are conducted.[63]

See also

edit

References

edit
  1. ^ "CBE Public Search". kbopub.economie.fgov.be. FPS Economy, SMEs, Self-Employed and Energy. Retrieved 27 February 2022.
  2. ^ a b c d e f g h i j k l Scott, Susan V.; Zachariadis, Markos (2014). The Society for Worldwide Interbank Financial Telecommunication (Swift) : cooperative governance for network innovation, standards, and community. New York, NY: Routledge. pp. 1, 35. doi:10.4324/9781315849324. ISBN 978-1-317-90952-1. OCLC 862930816.
  3. ^ a b c Arnold, Martin (6 June 2018). "Ripple and Swift slug it out over cross-border payments". Financial Times. Archived from the original on 27 September 2019. Retrieved 28 October 2019.
  4. ^ "Swift Company Information". SWIFT. 9 March 2010. Archived from the original on 22 December 2008. Retrieved 7 December 2016.
  5. ^ Annex 1: The History and Detailed Functioning of SWIFT. ECahiers de l'Institut. Graduate Institute Publications. 6 September 2011. ISBN 9782940415731.
  6. ^ Farrell, Henry; Newman, Abraham L. (July 2019). "Weaponized Interdependence: How Global Economic Networks Shape State Coercion". International Security. 44 (1): 42–79. doi:10.1162/isec_a_00351. ISSN 0162-2889. S2CID 198952367.
  7. ^ "Logica history". Archived from the original on 20 October 2011. Retrieved 8 February 2012.
  8. ^ "Carl Reuterskiöld". SWIFT. March 2006. Archived from the original on 24 January 2012. Retrieved 7 September 2012.
  9. ^ Serena Vergano, ed. (2009). Ricardo Bofill Taller de Arquitectura: Architecture in the era of local culture and international experience. RBTA. p. 130.
  10. ^ "The Swift Board of Directors". SWIFT.
  11. ^ a b c Kowsmann, Patricia; Talley, Ian (26 February 2022). "What Is Swift and Why Is It Being Used to Sanction Russia?". The Wall Street Journal. Retrieved 27 February 2022.
  12. ^ a b "Accord". 26 November 2015. Archived from the original on 26 August 2016. Retrieved 15 August 2016.
  13. ^ "Value-Added Alliances". Surecomp. Archived from the original on 28 March 2018.
  14. ^ Sechrist, Michael (23 March 2010). "Cyberspace in Deep Water: Protecting Undersea Communication Cables By Creating an International Public-Private Partnership" (PDF). Belfer Center for Science and International Affairs. Archived (PDF) from the original on 12 March 2018. For example, the Society for Worldwide Interbank Financial Telecommunication (SWIFT), which describes itself as "the global provider of secure financial messaging services", uses undersea fiber-optic communications cables to transmit financial data between 208 countries
  15. ^ "SWIFT: SIBOS issues" (PDF). SWIFT. 16 September 2008. Archived from the original (PDF) on 7 November 2015. p. 12.
  16. ^ "Distributed architecture". SWIFT. 6 June 2008. Archived from the original on 17 August 2013. Retrieved 31 August 2013.
  17. ^ Multiple sources:
  18. ^ "SWIFT History". SWIFT. Archived from the original on 26 December 2012. Retrieved 11 January 2009.
  19. ^ "ISO – Maintenance agencies and registration authorities". ISO.
  20. ^ "RFC 3615 – A Uniform Resource Name (URN) Namespace for SWIFT Fin (RFC3615)". faqs.org.
  21. ^ The oversight of SWIFT: Objectives, scope and structure (PDF), European Central Bank, December 2005
  22. ^ Javier Hamann & Eija Holttinen (8 August 2018), Belgium Encouraged to Continue Strengthening Oversight of Critical Payments Node, International Monetary Fund
  23. ^ "Swift oversight". SWIFT.
  24. ^ "Exclusive - China's payments system scaled back; trade deals only: sources". Reuters. 13 July 2015.
  25. ^ "Factbox: What is China's onshore yuan clearing and settlement system CIPS?". Reuters. 28 February 2022. Retrieved 4 March 2022.
  26. ^ "CIPS Participants Announcement No. 88". www.cips.com.cn. Retrieved 18 September 2023.
  27. ^ "Перечень пользователей СПФС Банка России | Банк России". www.cbr.ru.
  28. ^ "Iran blames EU on INSTEX ineffectiveness". Tehran Times. 18 January 2021.
  29. ^ "No transaction has been done through INSTEX: Iranian diplomat". Tehran Times. 4 March 2020.
  30. ^ "Swift Board names new Chair and Deputy Chair, completing leadership transition". 30 March 2023.
  31. ^ "Javier Pérez-Tasso". SWIFT. Archived from the original on 15 November 2019. Retrieved 15 November 2019.
  32. ^ Brand, Constant (28 September 2005). "Belgian PM: Data Transfer Broke Rules". The Washington Post. Retrieved 23 May 2010.
  33. ^ "European Parliament resolution of 17 September 2009 on the SWIFT Agreement". European Parliament. 17 September 2009.
  34. ^ "European Parliament to vote on interim agreement at February session". European Parliament. 21 January 2010.
  35. ^ Brand, Constant (11 February 2010). "Parliament rejects bank transfer data deal". European Voice.
  36. ^ "Euro MPs block bank data deal with US". BBC News. 11 February 2010.
  37. ^ "European parliament rejects SWIFT deal for sharing bank data with US". DW. Reuters. 11 February 2010.
  38. ^ a b Schult, Christoph (16 March 2011). "Brussels Eyes a Halt to SWIFT Data Agreement". Der Spiegel.
  39. ^ a b "'Follow the Money': NSA Spies on International Payments". Der Spiegel. 15 September 2013. Retrieved 18 September 2013.
  40. ^ Baldwin, Clare (15 April 2017). "Hackers release files indicating NSA monitored global bank transfers". Reuters. Retrieved 15 April 2017.
  41. ^ Lawler, Richard (15 April 2017). "Shadow Brokers release also suggests NSA spied on bank transactions". Engadget. Retrieved 15 April 2017.
  42. ^ Gladstone, Rick (31 January 2012). "Iran Praises Nuclear Talks with Team from U.N." The New York Times. Retrieved 4 February 2012.
  43. ^ a b Gladstone, Rick (3 February 2012). "Senate Panel Approves Potentially Toughest Penalty Yet Against Iran's Wallet". The New York Times. Retrieved 4 February 2012.
  44. ^ Solomon, Jay; & Adam Entous (4 February 2012). "Banking Hub Adds to Pressure on Iran". The Wall Street Journal. Retrieved 4 February 2012.
  45. ^ "Banking's SWIFT says ready to block Iran transactions". Reuters. 17 February 2012. Retrieved 17 February 2012.
  46. ^ Torchia, Andrew (17 February 2016). "Iranian banks reconnected to SWIFT network after four-year hiatus". Reuters. Retrieved 21 April 2016.
  47. ^ International banking giant refuses to cut off Israel, despite boycott calls. Haaretz. 7 October 2014.
  48. ^ Hutton, Robert; Ian Wishart (29 August 2014). "U.K. Wants EU to Block Russia From SWIFT Banking Network". Bloomberg News. Retrieved 31 August 2014.
  49. ^ "SWIFT Sanctions Statement". swift.com (Press release).
  50. ^ Turak, Natasha (23 May 2018). "Russia's central bank governor touts Moscow alternative to SWIFT transfer system as protection from US sanctions". CNBC. Retrieved 4 October 2018.
  51. ^ Shalal, Andrea (11 February 2022). "SWIFT off Russia sanctions list, state banks likely target -U.S., EU officials". Reuters. Retrieved 14 February 2022.
  52. ^ "EU unlikely to cut Russia off SWIFT for now, sources say". Reuters. 24 February 2022. Retrieved 24 February 2022.
  53. ^ "Joint Statement on further restrictive economic measures". ec.europa.eu. 26 February 2022. Retrieved 26 February 2022.
  54. ^ "New financial messaging rules for Russia approved | Bank of Russia". Central Bank of Russia. Archived from the original on 12 August 2023.
  55. ^ Adeela Naureen; Waqar K Kauravi (6 May 2023). "De-dollarisation and emerging global order". The Express Tribune.
  56. ^ Martin, Jessica (27 February 2022). "EU extends Russia sanctions to airspace, media, Belarus". Euractiv. Archived from the original on 1 March 2022. Retrieved 1 March 2022.
  57. ^ @nexta_tv (27 February 2022). "Lithuanian Prime Minister proposed to disconnect Belarus from SWIFT" (Tweet) – via Twitter.
  58. ^ "EU to impose new sanctions on Belarus this week -EU official". Reuters. 28 February 2022. Archived from the original on 2 March 2022. Retrieved 1 March 2022.
  59. ^ Corkery, Michael, "Hackers’ $81 Million Sneak Attack on World Banking", The New York Times, 30 April 2016. Retrieved 1 May 2016.
  60. ^ a b Corkery, Michael (12 May 2016). "Once Again, Thieves Enter Swift Financial Network and Steal". The New York Times. Retrieved 13 May 2016.
  61. ^ a b c Bergin, Tom; Layne, Nathan (20 May 2016). "Special Report: Cyber thieves exploit banks' faith in SWIFT transfer network". Reuters. Retrieved 24 May 2016.
  62. ^ Metzger, Max (28 June 2016). "SWIFT robbers swoop on Ukrainian bank". SC Magazine UK. Retrieved 29 June 2016.
  63. ^ Gyr, Marcel (1 March 2022). "Das Swift-Rechenzentrum in der Schweiz wird polizeilich geschützt – wegen der Gefahr von Sabotage" (in German) NZZ.com. Retrieved 2 March 2022.

Further reading

edit
edit
Retrieved from "https://en.wikipedia.org/w/index.php?title=SWIFT&oldid=1257956279"