ONBOARDING — 8 MIN READ
LEI and BIC in Correspondent Onboarding
Onboard correspondent nodes with LEI and BIC evidence, certificate binding, and corridor tests before authorizing live Protocol 101.1 IP-to-IP traffic.
|
Identity before throughput
Correspondent onboarding fails when teams chase TPS before binding legal entity identity (LEI), BIC routing identity, and technical certificates into one registration record. Protocol 101.1 traffic should not start until that binding is tested.
globalserverbank is not a licensed bank, does not issue BICs or LEIs, and is not affiliated with Visa. See also correspondent node onboarding checklist.
Technical profiles: Global Server Protocol.
Bind LEI, BIC, and certificates
Store LEI status (including lapsed checks), BIC, permitted corridors, and mTLS certificate fingerprints together. Certificate SANs should map to the registered institution—not only to ephemeral cloud hostnames. Pair with message signing vs mTLS.
KYC/KYB evidence owners differ from platform engineers; keep workflows explicit under AML/KYC integration.
Corridor tests before go-live
Run negative tests: expired cert, wrong LEI, replay, cut-off reject. Host pre-prod nodes on cloud banking servers that mirror prod network controls.
CTAs
Start institutional evaluation at node access and S2S transfer frameworks. Specs: Global Server Protocol.
FURTHER CLARITY
Frequently asked questions
Is a BIC enough to go live on Protocol 101.1?
No. You also need legal-entity due diligence, technical identity, corridor contracts, and tested controls.
Who issues LEIs?
Accredited LEI issuers in the Global LEI System—not globalserverbank.
Is this Visa Global Server onboarding?
No. This is independent infrastructure intelligence with no Visa affiliation.
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.