What were you trying to do?
Validate an AccountCreditedDrawdown (tag {5400})

What did you expect to see?
DrawdownCreditAccountNumber shouldn't allow any characters other than 0-9. This field is for 9 digit ABA routing numbers:

What did you see?
DrawdownCreditAccountNumber allows both numbers and letters.

How can we reproduce the problem?
See the unit test TestParseAccountCreditedDrawdownReaderParseError

We need to setup TravisCI deployment/releases for the HTTP server in this repository. It enables someone to just push a tag and have an image build.

See: https://docs.travis-ci.com/user/deployment/releases/ (or `travis setup releases) with our moov-bot credentials.

Update Wire Server Routes and use base ID()

Add CODE_OF_CONDUCT.md

What were you trying to do?
To deploy on OpenShift we need to use their base image. This allows a common setup for deployment, scanning, etc.

Also, publish the images to https://quay.io/, Red Hat’s image repository.

Wire Version: v0.9.0-rc1

What were you trying to do?
Parse a valid wire file in the format

{1100}30P N{1110}06071654XXXX{1120}20220607XXXXXXXXXXXXXXXXXXXXXXXXXX{1510}1000{1520}20220607XXXXXXXX000002{2000}000000009000{3100}021004543Test Bank*{3320}158545637*{3400}123456789Test XXXXXXXXXXXXX*{3600}CTP{3620}3*752E9D0D-99B8-4DF4-87F2-XXXXXXXXXXXX*{3700}BUSD0,00*USD10,00*{3710}USD100,00*{4200}DXXXXXXXXXXXXXXXX*Test Bank*line1*line2*line3*{4320}WW22060755582563*{5000}DXXXXXXXXXXX*line1*line2*line3*{5100}BXXXXXXXXXXX*Test Bank*line1*line2*{6000}FFC: XXXXX*XXXXXXXXXXX*

What did you expect to see?
I would expect this file to be successfully parsed

What did you see?
A validation error is thrown indicating that tag {5010} is mandatory.

How can we reproduce the problem?
Using the wire example posted above or any wire which is

• of Business Function code CTP
• Has tag {6000}
• Does not have tag {5010}

The crux of the issue seems to be around the following note on tag {6000} in the Fedwire Funds Service
Format Reference Guide doc, March 18, 2019. The note says

The wire library seems to interpret this note to indicate that if tag {6000} is present and the wire is a CTP, then tag {5010} is mandatory and validates accordingly.

Based on live wires we have been seeing as well as the rest of the format reference guide which requires either tag {5000} or {5010} to provide originator details for CTP, I believe this note on the reference guide is effectively trying to say

If tag {6000} is present and the business function code is not CTP, {4200} and {5000} are mandatory.
If tag {6000} is present and the business function code Is CTP, {4200} and ( either of {5000} or {5010} ) are mandatory.

Wire Version: Release v0.9.0-rc1

What were you trying to do?

Send a wire for $1200

What did you expect to see?

a wire for $1200

What did you see?

a wire for $12

How can we reproduce the problem?

with the name of the field not being clear it would be easy for someone to submit the wrong amount, I realize this is a nitpick so I added it to its own issue, its mostly just that consistency in naming would help here and this would be much more explicit

Add HTTP API

Wire Version: ``

What were you trying to do?

Make this file via the API

{1500}30        T {1510}1000{1520}20220128DOVTAL3C000001{2000}000000010000{3100}123456789DOVETAIL BANK US F*{3320}XX22012800000051*{3400}021000089CITIBANK NYC*{3600}CTP{3620}3*3AC4C307-0FFB-4028-BD8E-53D55BDB90E1*{3700}SUSD0,*{4200}D000100002*{5000}T000100011*DRESDEFFXXX*

What did you expect to see?

A properly formatted file that allows spaces in {1500}

What did you see?

{"error":"error reading file: line:1 record:SenderSupplied *wire.FieldError UserRequestCorrelation is a required field"}

How can we reproduce the problem?

Use the file above and try to create a file through the API

## Create Wire File From FAIM
# Creates a Wire File with the Moov Wire API
curl -X "POST" "https://MOOV_WIRE_URL/files/create" \
     -H 'Content-Type: text/plain' \
     -d "{1500}30        T {1510}1000{1520}20220128DOVTAL3C000001{2000}000000010000{3100}123456789DOVETAIL BANK US F*{3320}XX22012800000051*{3400}021000089CITIBANK NYC*{3600}CTP{3620}3*3AC4C307-0FFB-4028-BD8E-53D55BDB90E1*{3700}SUSD0,*{4200}D000100002*{5000}T000100011*DRESDEFFXXX*"

If {3610} is ANSI or S820, only the X12 Character Set* is permitted in Addenda Information element.

If {3610} is GXML, IXML, NARR, SWIF or UEDI, only the SWIFT MX ISO 20022 Character Set* is permitted in Addenda Information element.

• See latest version of the FAIM manual for specific characters included in character set.

This issue lists Renovate updates and detected dependencies. Read the Dependency Dashboard docs to learn more.

Awaiting Schedule

These updates are awaiting their schedule. Click on a checkbox to get an update now.

• chore(deps): update actions/cache action to v4
• chore(deps): update actions/checkout action to v4
• chore(deps): update actions/setup-go action to v5
• chore(deps): update github artifact actions to v4 (major) (actions/download-artifact, actions/upload-artifact)
• chore(deps): update github/codeql-action action to v3

Detected dependencies

• Check this box to trigger a request for Renovate to run again on this repository

Add validations for the FEDWIRE Message.

1. Mandatory tags

• Sender Supplied Information
• Type/Subtype
• Input Message Accountability Data (IMAD)
• Amount
• Sender DI
• Receiver DI
• Business Function Code

2. Business Function Codes

Business Function Code (3 characters)
BTR, CKS, CTP, CTR, DEP, DRB, DRC, DRW, FFR, FFS, SVC

Business Function Code Notes:
Each Fedwire Funds Service message originated must be assigned a valid business function code.
the business function code must be valid for the associated type/subtype code.

Some business function codes have specific information requirements and restrictions. Some field tags are only permitted for certain business function codes.

There is an error with this repository's Renovate configuration that needs to be fixed. As a precaution, Renovate will stop PRs until it is resolved.

Error type: undefined. Note: this is a nested preset so please contact the preset author if you are unable to fix it yourself.

Add Contributing.MD

I am new to GoLang. The following are the steps I had completed. I have set the Go in my environment and verified the same working fine.

Now when I change into the wire-master directory (cloned from GIT) and trying to build gives the following output. I would like to know if there is an instruction to build this wire project locally on windows and run it.

Wire Version: v0.6.2-dev

What were you trying to do?
So I am round trip testing a example wire file that I got out of the examples directory and when I receive them in the wire format I convert to json and store these in our database (not the wire server DB). I them grab the json representation of the wire and sent back through our wire processor and convert to fedwire format and all the tags are missing when using the FileFromJSON method

What did you expect to see?

{1500}30User ReqT ...

What did you see?

30User ReqT 
1600
20190410Source08000001
000001234567
121042882Wells Fargo NA    
231380104Citadel           
CKS   
Sender Reference
Previous Message Ident
D123456789                         FI Name                            Address One                        Address Two                        Address Three                      
D123456789                         FI Name                            Address One                        Address Two                        Address Three                      
31234                              Name                               Address One                        Address Two                        Address Three                      
Reference       
11234                              Name                               Address One                                                           Address Three                      
D123456789                         FI Name                            Address One                        Address Two                        Address Three                      
D123456789                         FI Name                            Address One                        Address Two                        Address Three                      
LineOne                            LineTwo                            LineThree                          LineFour                           
Line Six                                                                                                                                                                                           
Line Six                                                                                                                                                                                           
LTRLine One                  Line Two                         Line Three                       Line Four                        Line Five                        Line Six                         
Line One                      Line Two                         Line Three                       Line Four                        Line Five                        Line Six                         
TLXLine One                  Line Two                         Line Three                       Line Four                        Line Five                        Line Six                         
Line One                      Line Two                         Line Three                       Line Four                        Line Five                        Line Six                         
LTRLine One                  Line Two                         Line Three                       Line Four                        Line Five                        Line Six                         
CHECKAdditional Information        
Line One                           Line Two                           Line Three                         Line Four                          Line Five                          Line Six      

How can we reproduce the problem?

Call the /files/:fileID/contents end point with a valid json representation of a wire and you should get back:

30User ReqT 
1000
20190410Source08000001
000001234567
121042882Wells Fargo NA    
231380104Citadel           
BTR   
Sender Reference
Previous Message Ident
D123456789                         FI Name                            Address One                        Address Two                        Address Three                      
D123456789                         FI Name                            Address One                        Address Two                        Address Three                      
31234                              Name                               Address One                        Address Two                        Address Three                      
Reference       
11234                              Name                               Address One                                                           Address Three                      
D123456789                         FI Name                            Address One                        Address Two                        Address Three                      
D123456789                         FI Name                            Address One                        Address Two                        Address Three                      
LineOne                            LineTwo                            LineThree                          LineFour                           
Line Six                                                                                                                                                                                           
Line Six                                                                                                                                                                                           
LTRLine One                  Line Two                         Line Three                       Line Four                        Line Five                        Line Six                         
Line One                      Line Two                         Line Three                       Line Four                        Line Five                        Line Six                         
TLXLine One                  Line Two                         Line Three                       Line Four                        Line Five                        Line Six                         
Line One                      Line Two                         Line Three                       Line Four                        Line Five                        Line Six                         
LTRLine One                  Line Two                         Line Three                       Line Four                        Line Five                        Line Six                         
CHECKAdditional Information        
Line One                           Line Two                           Line Three                         Line Four                          Line Five                          Line Six                           

Wire Version: v0.8.0

What were you trying to do?
I was attempting to create a CustomerTransfer (CTR) without the InputMessageAccountabilityData (IMAD) field

What did you expect to see?
I expected to see the fedwire file contents without the IMAD field

What did you see?
An error is produced indicating the IMAD is a required field

How can we reproduce the problem?
Try to create a wire file without setting the InputMessageAccountabilityData field

Create example code for FEDWireMessage(s) which can be linked to from the README.md

I have installed the latest docker and then downloaded the docker image as below. Docker terminal shows the following output. However a curl or Google Chrome complains an empty response

Let me know what is going wrong....

With X9 and Wire being generated we should differentiate between ACH and the other formats and API docs.

See: moov-io/imagecashletter#42 (comment)

Wire Version: Release v0.9.0-rc1

What were you trying to do?

Process a wire file with Interface data at the beginning

What did you expect to see?

A successful processing of the wire file

What did you see?

{"error":"error reading file: line:1 record:SenderSupplied *wire.FieldError UserRequestCorrelation  is a required field"}

How can we reproduce the problem?

Use this to create a new wire file

FTI0811 XFT811  {1500}30        T {1510}1000{1520}20220128DOVTAL3C000001{2000}000000010000{3100}123456789DOVETAIL BANK US F*{3320}XX22012800000051*{3400}021000089CITIBANK NYC*{3600}CTP{3620}3*3AC4C307-0FFB-4028-BD8E-53D55BDB90E1*{3700}SUSD0,*{4200}D000100002*{5000}T000100011*DRESDEFFXXX*

## Create Wire File From FAIM
# Creates a Wire File with the Moov Wire API
curl -X "POST" "https://MOOV_WIRE_URL/files/create" \
     -H 'Content-Type: text/plain' \
     -d "FTI0811 XFT811  {1500}30        T {1510}1000{1520}20220128DOVTAL3C000001{2000}000000010000{3100}123456789DOVETAIL BANK US F*{3320}XX22012800000051*{3400}021000089CITIBANK NYC*{3600}CTP{3620}3*3AC4C307-0FFB-4028-BD8E-53D55BDB90E1*{3700}SUSD0,*{4200}D000100002*{5000}T000100011*DRESDEFFXXX*"

I think the best solution is to just strip out any characters before the first { because the Interface data is not useful for anything in 99.99% of use cases and this would also solve for other errors that sprung up for strange characters that ODFIs somehow magically add to wire files

It would be nice to have bidirectional conversion available in the browser demo, similar to https://oss.moov.io/ach/

Create openapi.yaml and go client for wires

Wire currently assumes fields are fixed-width, but the Fed also supports variable length elements. The Fedwire Funds reference doesn't say much about how variable length fields work, but IBM has some docs that explain more: https://www.ibm.com/docs/en/b2b-integrator/5.2?topic=higher-creating-fedwire-maps

We need to support a basic HTTP server for Wire files. To upload one (in JSON form), get its contents and validate. The OpenAPI docs exist, so let's copy from those and write the endpoints.

Wire Version: v0.9.0

What were you trying to do?
Generate a "variable-length" file via HTTP API.

What did you expect to see?
Support for "variable-length" file via HTTP API.

What did you see?
No support right now via HTTP API.
As per slack discussion the proposal is expose to a feature to generate "variable-length" file using /files/{fileId}/contents.

One proposal - have a query param type to choose between fixed and variable(can use better names).
Based on this value, appropriate writer can be used. i.e.

for fixed -> use what we have wire.NewWriter(w)
for variable -> use

wire.NewWriter(w, wire.VariableLengthFields(true), wire.NewlineCharacter(""))

** One other thing to take care is how the writer currently handles
{3600}BusinessFunctionCode - TransactionTypeCode. This field is optional as per spec and when not set in payload while creating(/files/create) the file, the decoder still adds the field with "". This happens because a string in Go cannot be nil. Any string field where the JSON key isn't present will end up as an empty string in Go.
This ends up adding * to this tag element for when we request file content i.e CTR* but should be just CTR here.
@atonks2 will investigate and address this after understanding its impact.

Party Identifier (35 characters)
Must be one of the following two formats:

1. /Account Number (slash followed by at least one valid non-space character: e.g., /123456)

2. Unique Identifier/ (4 character code followed by a slash and at least one valid non-space character: e.g., SOSE/123-456-789)
   ARNU/ Alien Registration Number
   CCPT/ Passport Number
   CUST/ Customer Identification Number DRLC/ Driver’s License Number EMPL/ Employer Number
   NIDN/ National Identify Number SOSE/ Social Security Number
   TXID/ Tax Identification Number
   Name (35 characters)
   Format: Must begin with Line Code 1 followed by a slash and at least one valid non-space character: e.g., 1/SMITH JOHN.
   Line 1 to 3 (35 characters each)
   Format: Each line, if present, must begin with one of the following Line Codes followed by a slash and at least one valid non-space character.
   1 Name
   2 Address
   3 Country and Town
   4 Date of Birth
   5 Place of Birth
   6 Customer Identification Number
   7 National Identity Number
   8 Additional Information For example:
   2/123 MAIN STREET
   3/US/NEW YORK, NY 10000
   7/111-22-3456

Wire Version: v0.8.0

What were you trying to do?
Generate a wire file in the "Fedwire extended format" (not sure of the terminology) for sharing with a banker's bank.

What do you expect to see?

A file generated by Moov looks similar to

{1500}30User ReqT {1510}1000 {1520}20220324WebBanki000001 {2000}000100000000 {3100}125109048Bank Name XXXXXXXX {3400}062000019An Souphorn {3600}CTR {4200}D000000219 An Souphorn {5000}D1001295 Christiane YWalker Address 1

Unlike a bank with a direct connection to the fed, which can use the file generated by the Moov wire library as is, for sharing the file with a banker's bank, a few changes are required with respect to delimiters. Each message starts with “YFT811 “, instead of fixed width, they are using variable width with asterisk (*) as the delimiter, and no new line characters are used in between and tags are present in the order of increasing numerical order.

A file that can be accepted by the Banker's Bank looks similar to

YFT811 {1500}303O004HE8P {1510}1000{1520}2022032400000000000001{2000}000000022200{3100}123456780Xxxxx Corresponden*{3400}021000021JPMCHASE*{3600}CTR{4100}F021000021*JPMC*123 Test st*Test*Test*{4200}D123455*Test Name*123 Test St*Town*MO*{5000}D123456*John Doe*123 Anywhere St*Anywhere*MO*{5100}D998877*Xxxx First Bank*158 Anywhere St*Anywhere*MO*{5200}F404123787*Xxxxxxx Bank*144 Anywhere St*Anywhere*MO*{6000}Test*{6500}Test*

Key differences:

1. ”YTF811 ” Static data; Marks the beginning of each wire

2. No new line character in the entire message structure (single line message)

3. A field delimiter (*) is used to terminate mandatory or optional variable length elements or optional fixed length elements. Mandatory fixed length elements do not require a delimiter. Mandatory elements always precede optional elements in a field tag. If an element is not present we must include asterisk. For e.g.

• {4200} is the beneficiary of the wire. The tag is broken up into 5 elements: (1) Account (2) Name (3) Address Line 1 (4) Address Line 2 (5) Address Line 3
• Each element is delimited by an asterisk. If the element is not present, you must include an asterisk. For example: {4200}D123456789*BeneficiaryName*AddressLine1*AddressLine2*AddressLine3* {4200}D123456789*BeneficiaryName*AddressLine1**AddressLine3 *{4200}D123456789*BeneficiaryName*AddressLine1*AddressLine2**

4. Three characters are defined as restricted special characters. They are: Asterisk (*), Left brace ({), and Right brace (}) The asterisk is used only as a delimiter, to terminate a mandatory or optional variable-length element or an optional fixed length element. The braces are used only as tag delimiters.

What did you want to see?

An optional field in the Moov wire library, say "useExtendedFormat" (not sure if I am using the right terminology) that allows toggling between the default format to the format described above

Add OPENAPI Routes

Support Phase 1 ISO20022 FEDWIRE Funds Service (FAIM 4.0.2)

https://www.youtube.com/watch?v=nA0w2M4OUdg&feature=youtu.be

Create types for reader and writer for reading and writing fed wire files

Add container builds for wire (review/see ach and ofac)

Wire Version: Release v0.9.0-rc1

What were you trying to do?

Send a wire

What did you expect to see?

No decimals in completed wire file

What did you see?

{2000}000000012.05

How can we reproduce the problem?

"amount": {
      "amount": "12.05"
    }

I'd recommend adding something like this to make sure it strips out anything that is not a digit

regexp.Compile("[\d]+")

Add Getting Started

Add tests for each fedWireMessage type to increase code coverage. With the new validation code coverage is currently at 56.5%. We should target 92% or > code coverage.

Charges  Details of Charges (‘B’ beneficiary or ‘S’ shared)   Senders Charges  (up to 4 occurrences of 15 characters each)   Format:  The first three characters must contain an alpha currency code (e.g., USD).  The remaining characters for the amount must begin with at least one numeric character (0-9) and only one decimal comma marker (e.g., $1,234.56 should be entered as USD1234,56 and $0.99 should be entered as USD0,99).

We need to support TLS in our HTTP server. This protects requests from inspection along the various network paths and routing. It's also required as part of several guidelines and audit requirements.

Add README.md

Wire Version: 0.7.2

What were you trying to do?
Replace a file's existing message using /FEDWireMessage, where the file ID does not exist.

What did you expect to see?
A 404 error response.

What did you see?
Empty reply from server.

How can we reproduce the problem?
curl -X POST -d "@fedWireMessage-FEDFundsSold.json" localhost:8088/files/invalid-id/FEDWireMessage -i

What were you trying to do?
Read in a fedWireMessage file containing invalid combinations of tags.

What did you expect to see?
Errors regarding the fedWireMessage.

What did you see?
Nothing.

I was looking at #36 but was unable to generate the client locally.

adam@Adams-MacBook-Pro:~/code/src/github.com/moov-io/wire
$ OPENAPI_GENERATOR_VERSION=4.0.1 ./openapi-generator generate -i openapi.yaml -g go -o ./client 
[main] WARN  o.o.c.ignore.CodegenIgnoreProcessor - Output directory does not exist, or is inaccessible. No file (.openapi-generator-ignore) will be evaluated.
[main] INFO  o.o.codegen.DefaultGenerator - OpenAPI Generator: go (client)
[main] INFO  o.o.codegen.DefaultGenerator - Generator 'go' is considered stable.
[main] WARN  o.o.codegen.utils.ModelUtils - Multiple schemas found in content, returning only the first one
[main] INFO  o.o.c.languages.AbstractGoCodegen - Environment variable GO_POST_PROCESS_FILE not defined so Go code may not be properly formatted. To define it, try `export GO_POST_PROCESS_FILE="/usr/local/bin/gofmt -w"` (Linux/Mac)
[main] INFO  o.o.c.languages.AbstractGoCodegen - NOTE: To enable file post-processing, 'enablePostProcessFile' must be set to `true` (--enable-post-process-file for CLI).
[main] INFO  o.o.codegen.DefaultGenerator - Model Files not generated since it's an alias to array (without property) and `generateAliasAsModel` is set to false (default)
Exception in thread "main" java.lang.RuntimeException: Could not process model 'MessageDisposition'.Please make sure that your schema is correct!
	at org.openapitools.codegen.DefaultGenerator.generateModels(DefaultGenerator.java:470)
	at org.openapitools.codegen.DefaultGenerator.generate(DefaultGenerator.java:919)
	at org.openapitools.codegen.cmd.Generate.run(Generate.java:396)
	at org.openapitools.codegen.OpenAPIGenerator.main(OpenAPIGenerator.java:60)
Caused by: java.lang.NullPointerException
	at org.openapitools.codegen.DefaultCodegen.updateCodegenPropertyEnum(DefaultCodegen.java:4137)
	at org.openapitools.codegen.DefaultCodegen.postProcessModelsEnum(DefaultCodegen.java:332)
	at org.openapitools.codegen.languages.AbstractGoCodegen.postProcessModels(AbstractGoCodegen.java:509)
	at org.openapitools.codegen.DefaultGenerator.processModels(DefaultGenerator.java:1195)
	at org.openapitools.codegen.DefaultGenerator.generateModels(DefaultGenerator.java:465)
	... 3 more

Most (all?) of the unit tests in Wire put their assertions inside conditional blocks. These tests trigger errors by deliberately crafting invalid tags and/or messages, but they pass if no error is returned. For example:

	if err := pn.Validate(); err != nil {
		if !base.Match(err, ErrValidTagForType) {
			t.Errorf("%T: %s", err, err)
		}
	}

The tests should be refactored to fail if no error is returned. The test above should be

	err := pn.Validate()

	if err == nil {
		t.Fatalf("an error was expected - wanted %T, %s", ErrValidTagForType, ErrValidTagForType)
	}
	if !base.Match(err, ErrValidTagForType) {
		t.Errorf("%T: %s", err, err)
	}

Better yet, the tests could be improved by using the testify package to assert or require test results:

	err := pn.Validate()
	
	require.NotNil(t, err)
	require.Contains(t, err.Error(), ErrValidTagForType.Error())

What were you trying to do?
I was trying to show file contents of a CTR transaction

What did you expect to see?
I expected to see my file contents

What did you see?
I saw an error requiring the the BeneficiaryIntermediaryFI field

How can we reproduce the problem?
Create a fedwire file with the following JSON:

{
    "id": "704943",
    "fedWireMessage": {
        "id": "704943",
        "messageDisposition": {
            "formatVersion": "30",
            "testProductionCode": "T"
        },
        "senderSupplied": {
            "formatVersion": "30",
            "userRequestCorrelation": "TESTDATA",
            "testProductionCode": "T",
            "messageDuplicationCode": " "
        },
        "typeSubType": {
            "typeCode": "10",
            "subTypeCode": "00"
        },
        "inputMessageAccountabilityData": {
            "inputCycleDate": "20180922",
            "inputSource": "XYZ ABC ",
            "inputSequenceNumber": "000001"
        },
        "amount": {
            "amount": "000000000250"
        },
        "senderDepositoryInstitution": {
            "senderABANumber": "000714895",
            "senderShortName": "Fake Institution"
        },
        "receiverDepositoryInstitution": {
            "receiverABANumber": "000738119",
            "receiverShortName": "Fake Institution"
        },
        "businessFunctionCode": {
            "businessFunctionCode": "CTR",
            "transactionTypeCode": "   "
        },
        "charges": {
            "chargeDetails": "B",
            "sendersChargesOne": "USD0",
            "sendersChargesTwo": "USD0",
            "sendersChargesThree": "USD0",
            "sendersChargesFour": "USD0"
        },
        "instructedAmount": {
            "currencyCode": "USD",
            "amount": "000000000250"
        },
        "exchangeRate": {
            "exchangeRate": "1.3624055125"
        },
        "beneficiary": {
            "personal": {
                "identificationCode": "T",
                "identifier": "755756",
                "name": "string",
                "address": {
                    "addressLineOne": "string",
                    "addressLineTwo": "string",
                    "addressLineThree": "string"
                }
            }
        },
        "originator": {
            "personal": {
                "identificationCode": "T",
                "identifier": "798260",
                "name": "string",
                "address": {
                    "addressLineOne": "string",
                    "addressLineTwo": "string",
                    "addressLineThree": "string"
                }
            }
        }
    }
}

So realistically - following the flow of this 2011 Fedwire Doc: http://citeseerx.ist.psu.edu/viewdoc/download?doi=10.1.1.445.7645&rep=rep1&type=pdf
Field {4000} (Beneficiary Intermediary FI) is not required in any case. If you look at page 15 of the doc, you'll see a flow of Business function codes, which fields are mandatory, and which fields are optional in a fedwire implementation.

Unless if you know of a better standard to be following: this is the implementation of Fedwire I'm using as a gold standard.

C:\Users\Owner\go\src\github.com\fzipp\gocyclo>gocyclo -over 45 C:\Users\Owner\go\src\github.com\moov-io\wire
114 wire (*Reader).parseLine C:\Users\Owner\go\src\github.com\moov-io\wire\reader.go:88:1
60 wire (*FedWireMessage).verify C:\Users\Owner\go\src\github.com\moov-io\wire\fedWireMessage.go:146:1

Add tag validation for each type

What were you trying to do?
Within the webui we can parse Wire files over to their JSON representation. We should expose file validation as well as a button.

Wire Version: v0.9.0

What were you trying to do?
Parse incoming wires in the Fedwire extended format

What did you expect to see?
Wires parsed successfully

What did you see?
Validation error message since tag {1500} is not present in incoming Fedwire extended format files

How can we reproduce the problem?
Parse a wire file with tag {1500}, ex

{1100}30P N{1110}06071654XXXX{1120}20220607XXXXXXXXXXXXXXXXXXXXXXXXXX{1510}1000{1520}20220607XXXXXXXX000002{2000}000000009000{3100}021004543Test Bank*{3320}158545637*{3400}123456789Test XXXXXXXXXXXXX*{3600}CTP{3620}3*752E9D0D-99B8-4DF4-87F2-XXXXXXXXXXXX*{3700}BUSD0,00*USD10,00*{3710}USD100,00*{4200}DXXXXXXXXXXXXXXXX*Test Bank*line1*line2*line3*{4320}WW22060755582563*{5000}DXXXXXXXXXXX*line1*line2*line3*{5100}BXXXXXXXXXXX*Test Bank*line1*line2*{6000}FFC: XXXXX*XXXXXXXXXXX*

Wire Version: v0.6.3-dev

This issue was reported by one of our Slack community members. Here's the thread for context: https://moov-io.slack.com/archives/CJV1WSCKF/p1605886718010000

What were you trying to do?
Parse a Fedwire file by calling the create file endpoint

What did you expect to see?
A successful API request/response

What did you see?
{"error":"error reading file: {1100} is an invalid tag"}

How can we reproduce the problem?
Call the create file endpoint with a file containing tags that fall under the "12. Information Appended by the Fedwire Funds Service" section of the format guide.