URC field should allow for spaces

[zbruhnke]

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*"

[mfdeveloper508]

Hello @zbruhnke I review spec document and sure URC field is mandatory filed Do you have any spec document to show URC is omit field?

[zbruhnke]

yes I do - I have provided these to @atonks2 and @adamdecaf

[atonks2]

Thanks @zbruhnke. I just shared them with @mfdeveloper508 in case he was operating off outdated docs.

For convenience though, here's what the spec says about URC:

User Request Correlation (URC): The sending DI may use this field to correlate the message sent to the Fedwire Funds Service with the response received from the Fedwire Funds Service. The contents of this field will be returned in the Fedwire Funds Service acknowledgment for the message. Spaces are permitted.

To me, that makes it sound like URC should be considered optional.

[atonks2]

@zbruhnke This should be resolved now. Would you mind grabbing the latest master and confirming that this issue is resolved for you?