CancellationRights (FIX tag 480)

charFIX 4.4

CancellationRights (tag 480) is a char field defined in FIX 4.4. It appears in 8 message types, always optionally. It is an enumerated field with 4 defined values.

At a glance

Tag
480
Name
CancellationRights
Datatype
char
Dialects
FIX 4.4
Messages
8
Valid values
4

What the specification says

For CIV – A one character code identifying whether Cancellation rights/Cooling-off period applies

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

A real message using tag 480

NewOrderSingle · FIX 4.4
TagFieldWire valueMeaning
8BeginStringFIX.4.4
9BodyLength117
35MsgTypeDOrder – Single
49SenderCompIDBOARTEAM
56TargetCompIDCOUNTERPARTY
34MsgSeqNum2
52SendingTime20240101-12:00:00.000
11ClOrdIDORD-10042
54Side1Buy
60TransactTime20240101-12:00:00.000
40OrdType1Market
480CancellationRightsYYes
10CheckSum041
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 4.4 dictionary and verified at build time: it parses and validates with no issues. Open the decoder to try your own message.

Valid values

A value outside this list is not a parse error — the message still decodes — but validate() reports it as validate/value-not-in-enum.

ValueMeaningSymbolic name
YYesYES
NNo – execution onlyNO_EXECUTION_ONLY
MNo – waiver agreementNO_WAIVER_AGREEMENT
ONo – institutional.NO_INSTITUTIONAL

Where tag 480 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.

MessageMsgTypeRequirednessWhere in the message
CrossOrderCancelReplaceRequesttOptionaldirectly on the message body
ExecutionReport8Optionaldirectly on the message body
MultilegOrderCancelReplaceACOptionaldirectly on the message body
NewOrderCrosssOptionaldirectly on the message body
NewOrderListEOptionaldirectly on the message body
NewOrderMultilegABOptionaldirectly on the message body
NewOrderSingleDOptionaldirectly on the message body
OrderCancelReplaceRequestGOptionaldirectly on the message body

Wire format

A single character. Most char fields are enumerated, so the value is one of a fixed set rather than arbitrary text. @boarteam/fix keeps the value as a string and, for enumerated fields, reports validate/value-not-in-enum when it is not a defined value.

Read tag 480 in TypeScript

decode.tsts
import { createFixEngine } from "@boarteam/fix";import { dictionary } from "@boarteam/fix-dict-fix44";const fix = createFixEngine(dictionary);const { message, issues } = fix.parse(raw);const cancellationRights = message.fields[480]?.raw;// e.g. "Y" — Yes// The dictionary also carries the labels:const label = fix.dictionary  .fieldByTag(480)  ?.enumValues?.find((e) => e.value === cancellationRights)  ?.description;

Other char fields

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-fix44