MESSAGING — 8 MIN READ
IP-to-IP Transaction Lifecycle: States and Evidence
IP-to-IP transaction lifecycle for banks: handshake, ACK, ledger reservation, scheme messaging, and settlement evidence without mixing delivery and finality.
|
Define IP-to-IP as a path, not a product
An IP-to-IP transaction is an institutional instruction path between authenticated endpoints over private or controlled IP connectivity. It is a messaging and control pattern—not a consumer app, not a card authorization, and not proof that money changed legal owners. In Global Server Banking architecture, IP-to-IP often rides Protocol 101.1 contracts with Protocol 201.3 ledger follow-through.
This lifecycle map complements S2S financial messaging and Protocol 101.1 rails. Independent intelligence only: not a licensed bank; not Visa-affiliated.
Lifecycle stages with distinct evidence
Stage 1 — Channel: mutual TLS (or equivalent) establishes peer identity. Stage 2 — Accept: schema, signature, entitlement, and idempotency checks return an acknowledgment. Stage 3 — Ledger: Protocol 201.3 reserves or posts. Stage 4 — Scheme: optional MT 103 / ISO 20022 egress on settlement rails. Stage 5 — Finality: confirmed only under governing system rules.
Each stage needs its own timestamped evidence object. Collapsing them into a single “success” boolean causes duplicate submissions and false customer notifications.
Timeouts, duplicates, and safe retries
After a timeout, retry with the same idempotency key and unchanged payload. Changing the amount under the same key must hard-fail. If the peer accepted but the client never saw the ACK, the safe path is status inquiry—not a new instruction—unless scheme rules provide an explicit cancel/replace procedure.
Link correlation IDs across the IP-to-IP ACK, Protocol 201 journal, and any MT 103 UETR/reference so operations can answer “where is it?” without treating screenshots as proof of funds.
Pillar pages and next reading
Deepen ledger semantics in Protocol 201.3 posting vs settlement. For wire egress, see MT 103 wire infrastructure. For the full stack view, read Global Server Banking architecture.
Service scopes: Protocol 101 & IP-to-IP frameworks and cross-border settlement & MT 103.
Before inviting a new peer into the lifecycle, complete the correspondent node onboarding checklist.
Lifecycle states should map cleanly to Global Server Protocol acceptance and status contracts. Hot-path gateways belong on low-latency cloud banking server infrastructure.
FURTHER CLARITY
Frequently asked questions
Is IP-to-IP the same as a blockchain transfer?
No. IP-to-IP here means authenticated institutional messaging between servers. Settlement still depends on accounts and authorized rails—not on a public chain by default.
Does IP-to-IP bypass SWIFT?
Not necessarily. IP-to-IP may initiate or coordinate instructions that still egress as MT 103 / ISO 20022 on correspondent or market infrastructures when those routes apply.
When can a customer be told funds are final?
Only when payment finality criteria under the relevant scheme and legal framework are met—not merely when an IP-to-IP ACK returns HTTP 200.
PRIMARY SOURCES & STANDARDS
References and citations
AN INFORMED NEXT STEP
Bring architectural discipline to your payment and ledger systems.
Start with your architecture, integration boundaries and operational requirements.