DistribPaymentMethod (FIX tag 477)

intFIX 4.4FIX 5.0 SP2

DistribPaymentMethod (tag 477) is an int field defined in FIX 4.4 and FIX 5.0 SP2. It appears in 1 message type, always optionally. It is an enumerated field with 12 defined values.

At a glance

Tag
477
Name
DistribPaymentMethod
Datatype
int
Dialects
FIX 4.4 and FIX 5.0 SP2
Messages
1
Valid values
12

What the specification says

FIX 4.4

A code identifying the payment method for a (fractional) distribution. 13 through 998 are reserved for future use Values above 000 are available for use by private agreement among counterparties

FIX 5.0 SP2

Identifies the payment method for a (fractional) distribution. Used for CIV.

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

A real message using tag 477

RegistrationInstructions · FIX 4.4
TagFieldWire valueMeaning
8BeginStringFIX.4.4
9BodyLength111
35MsgTypeoRegistration Instructions
49SenderCompIDBOARTEAM
56TargetCompIDCOUNTERPARTY
34MsgSeqNum2
52SendingTime20240101-12:00:00.000
513RegistIDEXAMPLE
514RegistTransType0New
508RegistRefIDEXAMPLE
510NoDistribInsts2 entries2repeating group
477DistribPaymentMethod1CREST
477DistribPaymentMethod1CREST
10CheckSum017
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
1CRESTCREST
2NSCCNSCC
3EuroclearEUROCLEAR
4ClearstreamCLEARSTREAM
5ChequeCHEQUE
6Telegraphic TransferTELEGRAPHIC_TRANSFER
7FedWireFEDWIRE / FED_WIRE
8Direct Credit (BECS, BACS)DIRECT_CREDIT
9ACH CreditACH_CREDIT
10BPAYBPAY
11High Value Clearing System (HVACS)HIGH_VALUE_CLEARING_SYSTEM / HIGH_VALUE_CLEARING_SYSTEM_HVACS
12Reinvest in fundREINVEST_IN_FUND

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

MessageMsgTypeFIX 4.4FIX 5.0 SP2Where in the message
RegistrationInstructionsoConditionalOptionalinside the RgstDistInstGrp component

Wire format

A whole number, optionally signed. Leading zeros are legal on the wire and are preserved in the raw value. @boarteam/fix parses the value as a number and reports parse/invalid-int when it does not lex as one; the raw string is kept either way.

Read tag 477 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 distribPaymentMethod = message.fields[477]?.raw;// e.g. "1" — CREST// The dictionary also carries the labels:const label = fix.dictionary  .fieldByTag(477)  ?.enumValues?.find((e) => e.value === distribPaymentMethod)  ?.description;

Other int 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