SWIFT BIC to GLEIF LEI Mapping Standard & Cross-Referencing
Cross-reference financial institution SWIFT BIC codes with GLEIF Legal Entity Identifiers for regulatory transaction reporting. This specification documents the exact field layout, checksum rules, and validation behavior so your integration matches ISO 17442 Legal Entity Identifier without reading the source standard.
⚡ Live SWIFT BIC to GLEIF LEI Mapping Standard & Cross-Referencing Interactive Workbench
Test real-time validation and schema parsing for SWIFT BIC to GLEIF LEI Mapping Standard & Cross-Referencing directly in your browser. Runs in sub-5ms with zero setup.
{
"status": "Click RUN VALIDATION to execute on the Cloudflare edge..."
}
Quick Summary: Cross-reference financial institution SWIFT BIC codes with GLEIF Legal Entity Identifiers for regulatory transaction reporting. Validates strictly against ISO 17442 Legal Entity Identifier with sub-5ms in-memory response times.
Specification & Structural Breakdown
Technical Summary: Validates strictly against ISO 17442 Legal Entity Identifier. Payloads are parsed in memory and return clean, typed JSON in milliseconds with zero data logged.
The SWIFT-to-LEI relationship mapping connects transaction message BICs directly to legal counterparty entities under MiFID II and Dodd-Frank mandates.
| Institution Name | BIC / SWIFT | LEI Code | Country |
|---|---|---|---|
| Deutsche Bank AG | DBEUMM21XXX | 7LTWFZYICNSX8D621K86 | Germany |
| BNP Paribas SA | BNPAFRPPXXX | ROM0U67LCH70SCY05V10 | France |
| JPMorgan Chase Bank, N.A. | CHASUS33XXX | 7H6GLXDRUGQFU57RNE97 | United States |
Parsed JSON Response Model
The edge microservice transforms input payloads into strongly-typed hierarchical JSON envelopes with sub-5ms latency:
{
"bic": "DBEUMM21XXX",
"lei": "7LTWFZYICNSX8D621K86",
"legalName": "Deutsche Bank AG"
}
Copy-Paste Integration Code (6 Languages)
Integrate SWIFT BIC to GLEIF LEI Mapping Standard & Cross-Referencing directly into your production application with native, zero-dependency code snippets in cURL, Node.js, Python, Go, C#, and a ready-to-paste Claude prompt. Get a free API key → (no credit card required):
curl --request POST \
--url "https://api.stanzaapi.com/lei-validator/api/v1/lei/validate" \
--header "Content-Type: application/json" \
--header "x-api-key: YOUR_API_KEY" \
--data '{
"lei": "5493006MHB84DD0ZWV18"
}'const response = await fetch("https://api.stanzaapi.com/lei-validator/api/v1/lei/validate", {
method: "POST",
headers: {
"Content-Type": "application/json",
"x-api-key": process.env.API_KEY || "YOUR_API_KEY"
},
body: JSON.stringify({
"lei": "5493006MHB84DD0ZWV18"
})
});
const data = await response.json();
console.log(data);import requests
import json
url = "https://api.stanzaapi.com/lei-validator/api/v1/lei/validate"
headers = {
"Content-Type": "application/json",
"x-api-key": "YOUR_API_KEY"
}
payload = {
"lei": "5493006MHB84DD0ZWV18"
}
response = requests.post(url, json=payload, headers=headers)
print(response.json())package main
import (
"bytes"
"fmt"
"io"
"net/http"
"os"
)
func main() {
url := "https://api.stanzaapi.com/lei-validator/api/v1/lei/validate"
payload := []byte(`{"lei":"5493006MHB84DD0ZWV18"}`)
req, _ := http.NewRequest("POST", url, bytes.NewBuffer(payload))
req.Header.Add("Content-Type", "application/json")
req.Header.Add("x-api-key", os.Getenv("API_KEY"))
res, err := http.DefaultClient.Do(req)
if err != nil {
panic(err)
}
defer res.Body.Close()
body, _ := io.ReadAll(res.Body)
fmt.Println(string(body))
}using System;
using System.Net.Http;
using System.Text;
using System.Threading.Tasks;
class Program
{
static async Task Main()
{
using var client = new HttpClient();
client.DefaultRequestHeaders.Add("x-api-key", Environment.GetEnvironmentVariable("API_KEY") ?? "YOUR_API_KEY");
var json = @"{""lei"":""5493006MHB84DD0ZWV18""}";
var payload = new StringContent(json, Encoding.UTF8, "application/json");
var response = await client.PostAsync("https://api.stanzaapi.com/lei-validator/api/v1/lei/validate", payload);
var content = await response.Content.ReadAsStringAsync();
Console.WriteLine(content);
}
}Integrate the StanzaAPI lei-validator micro-API.
Endpoint: POST https://api.stanzaapi.com/lei-validator/api/v1/lei/validate
Auth header: x-api-key: YOUR_API_KEY
Content-Type: application/json
Request body:
{
"lei": "5493006MHB84DD0ZWV18"
}
Rules:
- Send the request with a 2-second timeout.
- Parse the standard envelope { success, data, meta: { latency_ms, version } }.
- On failure, read { success: false, error, code } and branch on the code.
- Do not retry 4xx responses; surface the error code to the caller.
- Treat invalid-but-well-formed payloads as HTTP 200 with data.valid === false.Frequently Asked Questions & Technical Notes
MiFIR/EMIR regulatory reporting requires financial institutions to report transaction counterparties using LEIs rather than BICs.
Related Global LEI & Corporate Tax ID Validator API Formats
Explore sibling specifications and standards in the same developer cluster:
LEI Number Format Rules & ISO 17442 Check Digit Validator
Verify 20-character ISO 17442 LEI check digits, LOU prefix allocations, and entity identifiers in sub-1ms pure edge compute.
View Format →ISO 20275 Entity Legal Form (ELF) Code Directory & Resolver
Resolve 4-character ISO 20275 ELF codes into standardized corporate entity types across 160+ jurisdictions.
View Format →GLEIF Level 2 Relationship Data (Who Owns Whom) Model
Model corporate family trees, ultimate beneficial owners, and direct/ultimate accounting consolidation parents using GLEIF Level 2 data.
View Format →Complementary Enterprise APIs
Seamlessly orchestrate data pipelines across adjacent financial, regulatory, and supply-chain protocols:
SWIFT & ISO 13616 IBAN Validator →
Verify international bank accounts and counterparty integrity in global payments.
European VIES VAT Validator →
Validate corporate VAT registration across EU member states and the UK.
ISO 20022 Financial Messaging →
Enrich pacs.008 payment instructions with authenticated LEI counterparty verification.