EncryptedNewPassword (FIX tag 1404)

dataFIX 5.0 SP2

EncryptedNewPassword (tag 1404) is a data field defined in FIX 5.0 SP2. It appears in 2 message types, always optionally. It is length-prefixed — tag 1403 carries the byte count, so the value may contain the SOH separator without breaking the message.

At a glance

Tag: 1404
Name: EncryptedNewPassword
Datatype: data
Dialects: FIX 5.0 SP2
Messages: 2
Length field: tag 1403

What the specification says

Encrypted new password - encrypted via the method specified in the field EncryptedPasswordMethod(1400)

Descriptions are quoted from the FIX Orchestra sources under the Apache 2.0 licence.

A real message using tag 1404

Logon · FIX 5.0 SP2

Tag	Field	Wire value	Meaning
8	BeginString	FIXT.1.1
9	BodyLength	101
35	MsgType	A	Logon Message
49	SenderCompID	BOARTEAM
56	TargetCompID	COUNTERPARTY
34	MsgSeqNum	2
52	SendingTime	20240101-12:00:00.000
98	EncryptMethod	0	None
108	HeartBtInt	1
1403	EncryptedNewPasswordLen	7
1404	EncryptedNewPassword	EXAMPLE
1137	DefaultApplVerID	9
10	CheckSum	176

Edit and decode it yourself

Shown with | separators for readability. On the wire FIX uses SOH (0x01), an invisible control byte — and because BodyLength and CheckSum are computed over the actual bytes, the two forms have different checksums. Both are valid and both decode here.

Open in the full decoder →

Generated from the FIX 5.0 SP2 dictionary and verified at build time: it parses and validates with no issues. Open the decoder to try your own message.

Where tag 1404 appears

Requiredness is a property of the message, not of the field: the same tag can be optional in one message and conditionally required in another.

Message	MsgType	Requiredness	Where in the message
Logon	A	Optional	directly on the message body
UserRequest	BE	Optional	directly on the message body

Wire format

Raw bytes, length-prefixed by a partner field. The value may legally contain the SOH separator, which is why the length matters. @boarteam/fix reads the partner length field first and takes exactly that many bytes, so an embedded separator does not truncate the value.

Read tag 1404 in TypeScript

decode.tsts

import { createFixEngine } from "@boarteam/fix";import { dictionary } from "@boarteam/fix-dict-fix50sp2";const fix = createFixEngine(dictionary);const { message, issues } = fix.parse(raw);// Length-prefixed: tag 1403 carries the byte count, so the// value may contain the SOH separator without breaking the message.const length = message.fields[1403]?.value;const encryptedNewPassword = message.fields[1404]?.raw;

Decode this in your own code

The same engine that produced the decoded example above is an Apache-2.0 npm package with zero runtime dependencies. It runs in Node and in the browser, and parse() returns problems as data instead of throwing.

npm i @boarteam/fix @boarteam/fix-dict-fix50sp2

Try the decoder Source on GitHub