The trailing digits of the CFX account the wire moved through, as the
notification quotes them — 454 from "Credited to account ending with
454". Three digits in every message seen so far, never a full number, so
this identifies an account only in combination with the bank.
Null when the notification carries no account line at all, which is
ordinary rather than exceptional: Burling omits it on every debit. It is
therefore NOT part of the irreducible date/amount/IMAD set in
parseCommonFields — a missing suffix must never make an otherwise
good wire email unparseable.
amount
amount:number
date
date:string
exchangeRate
exchangeRate:string|null
foreignExchangeContract
foreignExchangeContract:string|null
imad
imad:string
method
method:"SWIFT"|"FEDWIRE"
omad
omad:string|null
originatingFI
originatingFI:string|null
originatorAddress
originatorAddress:string|null
originatorInfo
originatorInfo:string|null
senderName
senderName:string|null
sendingFI
sendingFI:{code:string;name:string}|null
tradeDate
tradeDate:string|null
type
type:"CREDIT"|"DEBIT"
wireNumber
wireNumber:string|null
The bank's wire sequence number, or null when the notification carries no
usable one. Fiserv emits a literal * placeholder on some wires, so this
cannot be relied on as a key — imad is the stable identifier.
The trailing digits of the CFX account the wire moved through, as the notification quotes them —
454from "Credited to account ending with 454". Three digits in every message seen so far, never a full number, so this identifies an account only in combination with the bank.Null when the notification carries no account line at all, which is ordinary rather than exceptional: Burling omits it on every debit. It is therefore NOT part of the irreducible date/amount/IMAD set in parseCommonFields — a missing suffix must never make an otherwise good wire email unparseable.