PaymentMethod (FIX tag 492)

intFIX 4.4

PaymentMethod (tag 492) is an int field defined in FIX 4.4. It appears in 1 message type, always optionally. It is an enumerated field with 15 defined values.

At a glance

Tag: 492
Name: PaymentMethod
Datatype: int
Dialects: FIX 4.4
Messages: 1
Valid values: 15

What the specification says

A code identifying the Settlement payment method. 16 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 492

SettlementInstructions · FIX 4.4

Tag	Field	Wire value	Meaning
8	BeginString	FIX.4.4
9	BodyLength	148
35	MsgType	T	Settlement Instructions
49	SenderCompID	BOARTEAM
56	TargetCompID	COUNTERPARTY
34	MsgSeqNum	2
52	SendingTime	20240101-12:00:00.000
777	SettlInstMsgID	EXAMPLE
160	SettlInstMode	1	Standing Instructions Provided
60	TransactTime	20240101-12:00:00.000
778	NoSettlInst2 entries	2	repeating group
162	SettlInstID	EXAMPLE
492	PaymentMethod	1	CREST
162	SettlInstID	EXAMPLE
492	PaymentMethod	1	CREST
10	CheckSum	163

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	Debit Card	DEBIT_CARD
9	Direct Debit (BECS)	DIRECT_DEBIT
10	Direct Credit (BECS)	DIRECT_CREDIT
11	Credit Card	CREDIT_CARD
12	ACH Debit	ACH_DEBIT
13	ACH Credit	ACH_CREDIT
14	BPAY	BPAY
15	High Value Clearing System (HVACS)	HIGH_VALUE_CLEARING_SYSTEM

Where tag 492 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
SettlementInstructions	T	Optional	inside the SettlInstGrp 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 492 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 paymentMethod = message.fields[492]?.raw;// e.g. "1" — CREST// The dictionary also carries the labels:const label = fix.dictionary  .fieldByTag(492)  ?.enumValues?.find((e) => e.value === paymentMethod)  ?.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