SwapPoints (FIX tag 1069)

PriceOffsetFIX 5.0 SP2

SwapPoints (tag 1069) is a PriceOffset field defined in FIX 5.0 SP2. It appears in 2 message types, always optionally.

At a glance

Tag: 1069
Name: SwapPoints
Datatype: PriceOffset (float)
Dialects: FIX 5.0 SP2
Messages: 2

What the specification says

For FX Swap, this is used to express the differential between the far leg's bid/offer and the near leg's bid/offer. Value can be negative. Expressed in decimal form. For example, 61.99 points is expressed and sent as 0.006199

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

A real message using tag 1069

NewOrderMultileg · FIX 5.0 SP2

Tag	Field	Wire value	Meaning
8	BeginString	FIXT.1.1
9	BodyLength	143
35	MsgType	AB	NewOrderMultileg
49	SenderCompID	BOARTEAM
56	TargetCompID	COUNTERPARTY
34	MsgSeqNum	2
52	SendingTime	20240101-12:00:00.000
11	ClOrdID	ORD-10042
54	Side	1	Buy
1069	SwapPoints	0.00010
555	NoLegs1 entry	1	repeating group
600	LegSymbol	EXAMPLE
60	TransactTime	20240101-12:00:00.000
40	OrdType	1	Market
10	CheckSum	205

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 1069 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
MultilegOrderCancelReplace	AC	Optional	directly on the message body
NewOrderMultileg	AB	Optional	directly on the message body

Wire format

A signed decimal price delta. Negative values are legal and meaningful. @boarteam/fix parses the value as a number and reports parse/invalid-float when it does not lex as one; the raw string is kept so precision and trailing zeros are never lost.

Read tag 1069 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[1069];field?.name;   // "SwapPoints"field?.raw;    // the verbatim wire stringfield?.value;  // coerced to a number

Other PriceOffset 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-fix50sp2

Try the decoder Source on GitHub