DistribPaymentMethod (FIX tag 477)

intFIX 4.4

DistribPaymentMethod (tag 477) is an int field defined in FIX 4.4. 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
Messages: 1
Valid values: 12

What the specification says

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

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

A real message using tag 477

RegistrationInstructions · FIX 4.4

Tag	Field	Wire value	Meaning
8	BeginString	FIX.4.4
9	BodyLength	111
35	MsgType	o	Registration Instructions
49	SenderCompID	BOARTEAM
56	TargetCompID	COUNTERPARTY
34	MsgSeqNum	2
52	SendingTime	20240101-12:00:00.000
513	RegistID	EXAMPLE
514	RegistTransType	0	New
508	RegistRefID	EXAMPLE
510	NoDistribInsts2 entries	2	repeating group
477	DistribPaymentMethod	1	CREST
477	DistribPaymentMethod	1	CREST
10	CheckSum	017

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.

Value	Meaning	Symbolic name
1	CREST	CREST
2	NSCC	NSCC
3	Euroclear	EUROCLEAR
4	Clearstream	CLEARSTREAM
5	Cheque	CHEQUE
6	Telegraphic Transfer	TELEGRAPHIC_TRANSFER
7	FedWire	FEDWIRE
8	Direct Credit (BECS, BACS)	DIRECT_CREDIT
9	ACH Credit	ACH_CREDIT
10	BPAY	BPAY
11	High Value Clearing System (HVACS)	HIGH_VALUE_CLEARING_SYSTEM
12	Reinvest in fund	REINVEST_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.

Message	MsgType	Requiredness	Where in the message
RegistrationInstructions	o	Conditional	inside 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;

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

Try the decoder Source on GitHub