---
title: "Discussion on \"FIX Session Layer in C#: Logon, Heartbeats, Sequence Numbers and Resend\" | Hashnode"
description: "Discussion on \"FIX Session Layer in C#: Logon, Heartbeats, Sequence Numbers and Resend\". The part of FIX that keeps a connection alive and consistent"
url: "https://hashnode.com/posts/fix-session-layer-in-c-logon-heartbeats-sequence-numbers-and-resend/6abc03423186121661813935"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [FIX Session Layer in C#: Logon, Heartbeats, Sequence Numbers and Resend](https://fix-api.hashnode.dev/fix-session-layer-in-c-logon-heartbeats-sequence-numbers-and-resend?utm_source=hashnode&utm_medium=feed)

The part of FIX that keeps a connection alive and consistent

Sep 29 · 14 min read · fix-api.hashnode.dev  
Read the article

-   [#csharp](https://hashnode.com/tag/csharp)
-   [#dotnet](https://hashnode.com/tag/dotnet)
-   [#fintech](https://hashnode.com/tag/fintech)
-   [#trading](https://hashnode.com/tag/trading)
-   [#tutorial](https://hashnode.com/tag/tutorial)

## Written by

[Sergiy Lutsak](https://hashnode.com/@serglutsak)

@serglutsak · Dnepr

  
[View profile](https://hashnode.com/@serglutsak)

HFT systems developer since 2000. Founder of HFT Software (HFT Forex Copier, HFT Arbitrage Platform). Writing about FIX protocol, latency and low-level C#.

## Responses 4

Markdown supported · ⌘↵ to post

[Arnold Holm](https://hashnode.com/@stratcorealpha)

[Oct 18](https://hashnode.com/posts/fix-session-layer-in-c-logon-heartbeats-sequence-numbers-and-resend/6abc03423186121661813935/comment/6ad4d3a50d7a612d9fa579c8)

One restart case I would add is the gap between saving NextIn and calling ApplicationMessage. In this sketch, a process exit after the counter is saved can leave the application without that fill, while its resend has a sequence number below NextIn and is ignored as a duplicate. I would test that exact stop point with an unapplied fill, restart from the saved counters, and assert that reconciliation restores it once. The sequence file and the application ledger need an explicit recovery boundary.

[indiainfranotes](https://hashnode.com/@indiainfranotes)

[Oct 3](https://hashnode.com/posts/fix-session-layer-in-c-logon-heartbeats-sequence-numbers-and-resend/6abc03423186121661813935/comment/6ac08f00a15113be623961d4)

Payment boards and settlement UIs fail the same audit cut: green status is not a tip you can GET.

If fee evidence lives only inside the runtime UI, audits become screenshots once the process is gone.

Curious what you treat as the durable artefact: the dashboard row, or a queryable settlement tip.

marker1003h1028

[indiainfranotes](https://hashnode.com/@indiainfranotes)

[Oct 1](https://hashnode.com/posts/fix-session-layer-in-c-logon-heartbeats-sequence-numbers-and-resend/6abc03423186121661813935/comment/6abdcf9d143d8d8c2bb7145f)

Settlement green closes the demo. Audit still wants a tip that survives the vendor UI flip.

Curious which India DPI stack keeps that tip queryable without a second shadow ledger.

marker1001h0828

[indiainfranotes](https://hashnode.com/@indiainfranotes)

[Sep 30](https://hashnode.com/posts/fix-session-layer-in-c-logon-heartbeats-sequence-numbers-and-resend/6abc03423186121661813935/comment/6abc7ee61b2a71a68be9f8a7)

Bank rails look finished in the UI. Dispute desks still need a signed hop tip they can re-check without calling support.

Curious how India stacks keep that tip when the vendor portal flips overnight.

marker0930h0828
