Format/Technical Documentation and MyStandards^® Frequently Asked Questions

Format Documentation

1. Where can I find information on the format specifications for the Fedwire^® Funds Service ISO^® 20022 implementation?

   You can obtain the following information on the Fedwire Funds Service page under “Fedwire Funds Service Release 2025” on the MyStandards^® 2 website: Usage Guidelines — Fedwire Funds Service Release 2025 (Off-site)

   • ISO 20022 usage/implementation guidelines (individual ISO 20022 messages that are in scope and customized for the Fedwire Funds Service)
   • ISO 20022 Implementation Guide
   • MyStandards Readiness Portal Guide
   • MyStandards Readiness Portal Test Script
   • DIT2 Test Script
   • Production Saturday Test Script
   • Fedwire Funds Service ISO 20022 Testing Attestation Form
   • Fedwire Funds Service ISO 20022 Quick Reference Guide

   
   

   You can also find the following information on the Fedwire Funds Service ISO 20022 Implementation Center.

   • Educational opportunities (webinars, drop-in sessions & workshops)
   • On the Wire newsletter
   • Testing requirements and key milestones
   • Industry preparedness checklist
   • Industry readiness dashboard
   • Vendor information
   • Frequently asked questions

   
   
   
2. What version of the ISO 20022 messages are used by the Fedwire Funds Service?

   The Fedwire Funds Service implemented the versions of the ISO 20022 messages that were available in 2019 for all messages except the following:

   • The pacs.004 (payment return) message aligns to version 10 of this message, which was published in 2020.
   • The camt.110 (investigation request) and camt.111 (investigation response) messages were the first release of those messages published in 2023.

   
   
   

   The specific version numbers for each message are listed in Section 1 of the Fedwire Funds Service ISO 20022 Implementation Guide.

3. Why does the Fedwire Funds Service use versions of the business application header (head.001) and return message (pacs.004) that are different than the versions of those messages in the Cross-border Payments Reporting Plus (CBPR+) guidelines?

   The business application header (BAH) is a point-to-point message, so use of a different version for messages exchanged across the Fedwire Funds Service does not cause any interoperability issues. We are using version 3 of the business application header (head.001.001.03) instead of version 2, which is used by the CBPR+ guidelines, because version 2 does not allow you to include a complete copy of the original BAH in the Related component that is used for message retrievals.

   The Fedwire Funds Service is using version 10 of the return message (pacs.004.001.10) instead of version 9, which is used by the CBPR+ guidelines because the Return Chain component identifying all persons/entities and agents involved in the return payment in version 9 does not cater for inclusion of account identifiers that may be needed for return payments sent across the Fedwire Funds Service to be complete and fully transparent.

4. What ISO 20022 messages are in scope for the Fedwire Funds Service? Are they all required?

   Please review the following documents that provide information on the Fedwire Funds Service ISO 20022 message portfolio:

   • Mandatory vs Optional ISO 20022 messages section of the Fedwire Funds Service ISO 20022 Quick Reference Guide
   • ISO 20022 usage/implementation guidelines
   • ISO 20022 Implementation Guide
   • MyStandards Readiness Portal Guide

   
   
   
5. Is there a document to compare the ISO 20022 messages to the former Fedwire Application Interface Manual (FAIM) format?

   See the Appendix of the Fedwire Funds Service ISO 20022 Implementation Guide on MyStandards. This topic was discussed during the ISO 20022 Introduction and Overview webinar on February 1, 2023 (Off-site).

6. Is there any documentation to explain how to generate a UETR?

   The Fedwire Funds Service requires you to include a Unique End-To-End Reference (UETR) that conforms to the Universally Unique Identifier (UUID) version 4 standard as described in IETC RFC 4122. The format pattern for the UETR is defined in the Fedwire Funds Service ISO 20022 usage guidelines on MyStandards. While we will validate that the UETR conforms to the correct pattern, we will not validate the uniqueness of the UETR.

Technical Guide and Business Application Header

1. How do we get a copy of the Technical Guide and the proprietary XSD files?

   Only EUACs and authorized contacts can request access to download the Fedwire Funds Service ISO 20022 Technical Guide and proprietary XSD files from a private page on the MyStandards website. Please review the instructions to request access (PDF) to the Technical Documentation Release 2025 private page.

2. Do ISO 20022 messages for the Fedwire Funds Service include a Business Application Header and a message envelope?

   All ISO 20022 messages require a message envelope, Business Application Header and the ISO 20022 business message. These requirements are specified in the Fedwire Funds Service ISO 20022 Technical Guide.

3. Do ISO 20022 messages need to be digitally signed?

   We do not require ISO 20022 messages to be digitally signed for the Fedwire Funds Service.

4. Can you explain the correct use of the From Member Identification and To Member Identification elements in the Business Application Header (BAH)?

   The table below provides information to help FedLine Direct connection owners properly format the BAH for all messages sent to the Fedwire Funds Service. The same rules apply to messages imported/uploaded using the import feature of the FedPayments^® Manager – Funds application.

   Message Sent By	From Member ID Element	To Member ID Element
   Fedwire Funds Service Customer	Must be the routing number of the Fedwire Funds Service customer that owns the FedLine Direct connection	Must always be the Fedwire Funds Service routing number (i.e., 021151080)
   Fedwire Funds Service Customer Using a Service Provider	Must be the Electronic Transfer Identifier (ETI) of the service provider that owns the FedLine Direct connection

5. When a Fedwire Sender sends a message to the Fedwire Funds Service, what value should be included in the "To" element of the Business Application Header?

   You should always include the Fedwire Funds Service routing number (i.e., 021151080) in element To/FIId/FinInstnld/ClrSysMmbld/Mmbld of the business application header for all messages you send to the Fedwire Funds Service.

6. What is the XML namespace prefix and is it required for ISO 20022 messages that we send to the Fedwire Funds Service?

   Namespaces act like a unique prefix and allow the same name elements and attributes from different schemas to coexist in a single XML message. For instance, the element <PstlAdr> exists in a number of ISO 20022 messages, but by attaching a namespace prefix that identifies a specific message, you can differentiate which element is in use.

   The requirements for the namespace prefix are as follows. Additionally, the requirements are further described in the Fedwire Funds Service ISO 20022 Technical Guide, which also includes samples.

   • The Fedwire Funds Service accepts ISO 20022 messages with or without namespace prefixes.
   • Messages sent by the Fedwire Funds Service do not use a namespace prefix in the Message Envelope and BAH, but please note the following:
     • For acknowledgements, the Fedwire Funds Service does not use a namespace prefix in the ISO 20022 Business Message.
     • For advices and retrieved messages, the Fedwire Funds Service passes along the original ISO 20022 Business Message sent by the Fedwire Sender with or without namespace prefix.

   
    
7. What is the XML declaration? Is it required for ISO 20022 messages that we send to the Fedwire Funds Service?

   The XML declaration specifies the XML version and the character set that is used for the Fedwire Funds Service ISO 20022 messages. This is optional, but when used, it must appear in the first line of the XML message as shown below:

   <?xml version=”1.0” encoding=”utf-8”?>

   • The Fedwire Funds Service accepts ISO 20022 messages with or without the XML declaration sent by Fedwire Senders.
   • All ISO 20022 messages sent by the Fedwire Funds Service always include the XML declaration.

   
    
8. What is the maximum size for Fedwire Funds Service ISO 20022 messages?

   The Fedwire Funds Service message specifications restrict use of the global ISO 20022 messages to reflect the nature of electronic payments, the Fedwire Funds Service ISO 20022 implementation scope and system requirements. While these restrictions already significantly reduce the risk of messages that could potentially be lengthy, messages sent by Fedwire Funds Service participants to the Fedwire Funds Service must not exceed 25,000 characters. Messages delivered by the Fedwire Funds Service (excluding the Account Reporting messages) to Fedwire Funds Service participants will not exceed 27,000 characters. The Message Envelope and ISO 20022 payload (this includes the Business Application Header and ISO 20022 Business Message) are included in this overall character limit.

9. Is an error code glossary available?

   The Error Code Glossary is included as an appendix in the Fedwire Funds Service ISO 20022 Technical Guide. Please refer to the table below to understand how we deliver error codes with descriptions.

   Error Type	Definition	ISO 20022 message sent by the Fedwire Funds Service	Description
   Technical Error (error codes begin with “T”)	Errors related to XML schema (e.g., character length) or errors related to rules in the Fedwire Funds Service ISO 20022 usage guidelines (e.g., postal address rules)	admi.002	Provides one error code with description at a time
   Business Error (error codes begin with “E,” “F, ” “H” or “I”)	Errors related to Fedwire Funds Service business edits (e.g., valid Fedwire Sender or Fedwire Receiver)	admi.002 (only for camt.029/pacs.028/ pain.014/admi.006/ camt.060/admi.004/ camt.110/camt.111)	Provides one error code with description at a time
   		pacs.002 (only for pacs.008/pacs.009/pacs.004)	Provide all error codes with descriptions
   		camt.029 (only for camt.056)
   		pain.014 (only for pain.013)

10. How should we handle the “FedwireFundsTechnicalHeader” element within the Fedwire Funds Service proprietary schemas (i.e., XSD files)?

    The optional FedwireFundsTechnicalHeader element within the Fedwire Funds Service proprietary schemas (i.e., XSD files) is a placeholder for future use by the Fedwire Funds Service and should not be used by Fedwire Funds Service customers.

MyStandards Questions

1. How do I set up access on MyStandards?

   The use of MyStandards is free and does not require SWIFT^® membership, but users will need a valid swift.com login ID and password to access the MyStandards platform. See MyStandards access instructions (PDF).

2. How do I use the features (e.g., compare button) in MyStandards?

   The MyStandards webinar (Off-site, Video) presented on March 8, 2023, provides a detailed overview of the MyStandards platform, including how to navigate the platform and use its features.

Top of Page