OPERATIONS — 10 MIN READ
Correspondent Node Onboarding Checklist
Correspondent and Global Server Banking node onboarding checklist: identity, Protocol 101.1/201.3 controls, MT 103 mapping, testing gates, and node-access CTA.
|
Purpose: institutional node readiness—not a banking license
This checklist helps correspondent banks, payment institutions, and infrastructure teams prepare a Global Server Banking node evaluation: identity, messaging, ledger controls, and external settlement wiring. Completing items does not create a licensed bank relationship, Visa affiliation, or guaranteed corridor access.
Use alongside Protocol 101.1 vs 201.3, Protocol 101.1 mTLS identity, and cross-border settlement. When ready for discovery, continue to node access.
1) Institutional identity, legal, and due-diligence gates
Confirm the legal entity requesting node evaluation, authorized contacts, and whether the use case is sandbox architecture discovery or a later production discussion under separate agreements. Keep KYC / CDD evidence workflows distinct from technical certificate issuance.
- Legal entity name, jurisdiction, and registration identifiers documented
- Authorized technical and compliance contacts named with escalation paths
- Intended corridors/currencies described at capability level (no customer PII in tickets)
- Sanctions / AML program ownership identified for production paths
- Clear statement that evaluation ≠ licensed deposit-taking or card acquiring
2) Protocol 101.1 / IP-to-IP messaging readiness
Protocol 101.1 readiness means mutual identity and deterministic message handling before any credit instruction is trusted.
Deep dive: Protocol 101.1 mTLS node identity and IP-to-IP / S2S messaging.
| Control | Ready when | Evidence example |
|---|---|---|
| Mutual TLS | Client and server certs map to registered node IDs | Cert schedule + SAN/institution mapping |
| Trust store | Rotation/dual-running window defined | Runbook with overlap dates |
| Idempotency | Stable keys on create/retry paths | Fixture showing duplicate suppress |
| Status vocabulary | ACK / reject / timeout / ambiguous separated | Published code dictionary |
| Replay protection | Nonce/timestamp windows enforced | Negative test for replay |
3) Protocol 201.3 ledger and reconciliation readiness
Protocol 201.3 readiness means reservation/commit semantics and break detection—not marketing “instant settlement” claims. See posting vs settlement.
- Available vs book balance rules documented
- Atomic double-entry journal identifiers defined
- Compensating journal policy (no silent history rewrite)
- Outbox/event publication only after durable commit
- Nostro / external statement reconciliation owners assigned
4) External rails: MT 103 / pacs.008 and correspondents
If an external leg is in scope, confirm translator ownership, agent-chain tests, and screening-before-egress. Use the MT 103 to pacs.008 field mapping cheat sheet as a scorecard input.
- Correspondent or scheme path identified per currency
- MT/MX coexistence fixtures prepared for sample payments
- Charge bearer and remittance truncation tests completed
- Investigation / recall ownership mapped to queues
5) Sandbox test gates before production talk
Gate production discussions on observed evidence: failed-handshake logging without leaking customer data, duplicate submission suppression, reservation timeout behavior, and reconciliation of intentional breaks.
| Gate | Pass criteria | Fail signal |
|---|---|---|
| Identity | Unauthorized cert rejected | Peer accepted on IP allowlist alone |
| Messaging | Duplicate key does not double-instruct | Two accepts for one economic intent |
| Ledger | Commit then event; compensate on abort | Posted event before durable journal |
| Mapping | MT and MX fixtures retain party hash | Screened name differs from egress name |
| Ops | Correlation IDs span 101 and 201 records | Investigations rely on screenshots only |
Request node access when the checklist is substantially complete
When identity contacts, protocol controls, and test fixtures are prepared, submit an institutional evaluation request through node access. Bring sanitized architecture diagrams and non-production sample payloads—never live customer secrets in the inquiry form.
Related services: global server banking core, Protocol 101 & IP-to-IP / S2S frameworks, and cross-border settlement & MT 103 architecture. Specs: Global Server Protocol. Hosting: Cloud Global Server.
FURTHER CLARITY
Frequently asked questions
Does finishing this checklist grant production node connectivity?
No. The checklist prepares evaluation quality. Production connectivity requires separate institutional agreements, controls evidence, and authorized rail arrangements.
Is node access the same as opening a bank account?
No. Node access here means architecture discovery and sandbox evaluation framing for Global Server Banking reference models—not a licensed deposit account.
Do I need both Protocol 101.1 and 201.3 for onboarding?
Most institutional designs need messaging (101.1) and ledger execution (201.3) plus an external settlement path. Scope can be staged, but status vocabularies must stay separated.
Where do I submit the evaluation request?
Use the node access request flow at /node-access with authorized contacts and sanitized technical materials.
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.