ReferencePage (FIX tag 1448)

StringFIX 5.0 SP2

ReferencePage (tag 1448) is a String field defined in FIX 5.0 SP2. It appears in 7 message types, always optionally.

At a glance

Tag: 1448
Name: ReferencePage
Datatype: String
Dialects: FIX 5.0 SP2
Messages: 7

What the specification says

Identifies the reference "page" from the rate source. For FX, the reference page to the spot rate to be used for the reference FX spot rate. When RateSource(1446) = 3 (ISDA Settlement Rate Option) this contains the value from the scheme that reflects the terms of the Annex A to the ISDA 1998 FX and Currency Option Definitions. See: https://fpml.org/coding-scheme/settlement-rate-option

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

A real message using tag 1448

ExecutionReport · FIX 5.0 SP2

Tag	Field	Wire value	Meaning
8	BeginString	FIXT.1.1
9	BodyLength	170
35	MsgType	8	ExecutionReport
49	SenderCompID	BOARTEAM
56	TargetCompID	COUNTERPARTY
34	MsgSeqNum	2
52	SendingTime	20240101-12:00:00.000
37	OrderID	ORD-10042
17	ExecID	EXEC-88117
150	ExecType	0	New
39	OrdStatus	0	New
54	Side	1	Buy
151	LeavesQty	0
14	CumQty	1000000
1445	NoRateSources2 entries	2	repeating group
1446	RateSource	0	Bloomberg
1448	ReferencePage	EXAMPLE
1446	RateSource	0	Bloomberg
1448	ReferencePage	EXAMPLE
10	CheckSum	130

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 1448 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
AllocationInstruction	J	Optional	inside the RateSource component
AllocationReport	AS	Optional	inside the RateSource component
ExecutionReport	8	Optional	inside the RateSource component
MarketDataIncrementalRefresh	X	Optional	inside MDIncGrp › RateSource
MarketDataSnapshotFullRefresh	W	Optional	inside MDFullGrp › RateSource
Quote	S	Optional	inside the RateSource component
QuoteRequest	R	Optional	inside QuotReqGrp › RateSource

Wire format

Free-form text. Any byte except the SOH separator is legal, so values are not trimmed or case-folded on the wire. @boarteam/fix keeps the value as a string; format rules are checked by validate(), which reports validate/invalid-value rather than throwing.

Read tag 1448 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);const field = message.fields[1448];field?.name;   // "ReferencePage"field?.raw;    // the verbatim wire stringfield?.value;  // coerced to a string

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