EDGE ENGINE SUB-2MS DETERMINISTIC V8 EXECUTION • ZERO DATA RETENTION • EXPLORE API SPECS →
ISO 17442 Legal Entity Identifier <1ms Edge Edge Compute

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.

Latency: <1ms Edge Availability: 99.99% Standard: GLEIF / SWIFT Relationship Matrix In-Memory Execution
Interactive Edge Workbench

⚡ 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.

32KB Demo Cap 60 req/min Burst <2ms V8 Compute Zero Data Retention
input.txt 0 B
output.json demo-ready
Status: Ready
{
  "status": "Click RUN VALIDATION to execute on the Cloudflare edge..."
}
Sandbox Quota: Free Tier (50 reqs/mo) • Production keys from $29/mo Get Free Sandbox Key →
Need 512KB+ Payloads, High-Throughput & 99.9% Production SLA?
Direct API keys include pooled monthly quotas, zero cold-starts, and HIPAA BAA eligibility on the Mega tier.
Get Production API Key →
LLM / MCP
Prompt-Ready Specification for AI Agents llms.txt
Structured format rules and schemas optimized for LLM coding agents and Model Context Protocol tooling.
Raw .md
Official Standard & Validation Protocol Authority: Global Legal Entity Identifier Foundation (GLEIF) ↗

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.

Latency
<1ms Edge
Standard
GLEIF / SWIFT Relationship Matrix
Version
Max Payload
512 KB
Privacy
In-Memory (0 bytes stored)

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 NameBIC / SWIFTLEI CodeCountry
Deutsche Bank AGDBEUMM21XXX7LTWFZYICNSX8D621K86Germany
BNP Paribas SABNPAFRPPXXXROM0U67LCH70SCY05V10France
JPMorgan Chase Bank, N.A.CHASUS33XXX7H6GLXDRUGQFU57RNE97United States

Parsed JSON Response Model

The edge microservice transforms input payloads into strongly-typed hierarchical JSON envelopes with sub-5ms latency:

HTTP 200 JSON Response Envelope
{
  "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

Why is BIC to LEI mapping required in banking?

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:

Complementary Enterprise APIs

Seamlessly orchestrate data pipelines across adjacent financial, regulatory, and supply-chain protocols:

All Global LEI & Corporate Tax ID Validator API Formats & Specifications (4) Directory Index ↓
LEI Number Format Rules & ISO 17442 Check Digit Validator SWIFT BIC to GLEIF LEI Mapping Standard & Cross-Referencing ISO 20275 Entity Legal Form (ELF) Code Directory & Resolver GLEIF Level 2 Relationship Data (Who Owns Whom) Model