Tag number, field name, MsgType, message or component name, or a value such as 39=1 or OrdStatus=2. Search runs in your browser.
Username <553>
- Tag
553- Type
- String
- FIXML name
Username- Pedigree
- Added FIX 4.3
- Versions
- FIX Latest ✓ · FIX 4.4 ✓ · Not in FIX 4.2
This page shows Username <553> as defined in FIX 4.4. For the current standard, see tag 553 Username in FIX Latest.
Username <553> in plain English
Summary by The MidPoint News, based on the description in the Orchestra file (quoted in full below).
Username carries the user ID or username, for example on the Logon message or a UserRequest.
Where it is used
Logon (35=A), UserRequest (35=BE), UserResponse (35=BF) .
In all, 3 messages in FIX 4.4 can carry it. Full list.
Example message
8=FIX.4.4|9=99|35=A|49=BUYSIDE|56=SELLSIDE|34=1|52=20261116-08:30:00.000|98=0|108=30|141=Y|553=user01|554=example|10=080 Illustrative example, not real orders or market data. A Logon (35=A) in FIX 4.4, shown with BeginString FIX.4.4. Instrument identifiers (such as AAPL, ISIN US0378331005, ESZ6, XNAS, XCME) are real public codes used for illustration. Order and execution IDs, accounts, prices, quantities and times are made up. Fields are separated by | here; on the wire the separator is the SOH character (ASCII 1). BodyLength (9) and CheckSum (10) are calculated for this example. Every tag and value in it is checked against the FIX 4.4 dictionary, but it is not a complete specification of the message.
Description (from the Orchestra file)
Userid or username.
Used in
Messages (3)
| Message | MsgType | Presence |
|---|---|---|
| Logon | A | Optional |
| UserRequest | BE | Required |
| UserResponse | BF | Required |