The Payment Integrity Network
JIL Sovereign runs a 111-check Verdict Engine across 15 signal categories on every transaction in under 2 seconds, covering Fraud, Waste, Error, and Abuse (FWEA), and proves every outcome after settlement. The only unified FWEA coverage engine in production - deployed with 14-of-20 BFT consensus, post-quantum cryptography, and cryptographic proof of every verdict.
The Payment Integrity Network. 111 checks. 15 categories. FWEA coverage. Under 2-second latency.
JIL Sovereign is The Payment Integrity Network - the infrastructure layer that verifies every institutional payment before it executes and proves every outcome after it settles. At the core is the JIL Verdict Engine: a real-time attestation pipeline that runs 111 independent checks across 15 signal categories on every transaction and returns a structured verdict - Allow, Review, or Block - in under 2 seconds, with a cryptographically signed record written immediately to a distributed ledger.
Unlike single-point fraud tools, policy engines, or after-the-fact audit platforms, JIL delivers unified coverage of Fraud, Waste, Error, and Abuse (FWEA) - the four categories of loss that together consume 3 to 8 percent of annual payment volume at most institutions. The same engine operates across fiat rails (ACH, wire, FedNow, RTP, SWIFT), cross-border corridors, digital asset settlement, healthcare payments, and government disbursements.
JIL preserves institutional custody (MPC 2-of-3), enforces 14-of-20 BFT consensus across 13 jurisdictions, and runs on a post-quantum cryptographic foundation (CRYSTALS-Dilithium and CRYSTALS-Kyber). Every verdict produces two inseparable outputs: the decision your system acts on, and the immutable blockchain-anchored evidence that proves what was evaluated and when. JIL does not move money, custody funds, or replace any financial intermediary.
In addition to real-time pre-settlement attestation, JIL operates the Investigation Engine - a retroactive identity integrity product that reconstructs the identity state of every payee at the exact date of each historical payment. For any institution with months or years of payment history, the Investigation Engine runs 28 identity dimensions across the full payment dataset and returns date-anchored, cryptographically sealed findings suitable for federal investigative referral, False Claims Act proceedings, and recovery litigation. The engine processes 100 million records in 10 to 20 minutes and is starting at 5 basis points per record, with scope, check depth, and volume priced per engagement. See JIL Retroactive Identity Integrity Audit.
Every institution loses 3 to 8 percent of annual payment volume to Fraud, Waste, Error, and Abuse. Most never measure it systematically.
FWEA losses are distributed across four silos that no single vendor covers. Institutions run fraud tools, policy engines, duplicate-detection scripts, and after-the-fact audits in isolation - and the gap between them is where the 3-8 percent leakage lives. JIL is the infrastructure layer that closes this gap.
Fraud (0.5 to 2.5 percent of volume) - BEC, synthetic identity, account takeover, vendor impersonation, pig butchering, deepfake voice authorization, authorized push payment scams.
Waste (2 to 6 percent) - duplicate payments, overpayments, invoice inflation, stale instructions, payments to ineligible or deceased recipients, fee leakage, expired contract terms.
Error (0.3 to 1.2 percent) - wrong account, wrong currency, wrong amount, misrouted reference data, data-entry mistakes, system mismatches.
Abuse (0.2 to 1.0 percent) - policy workarounds, split transactions to avoid thresholds, ghost counterparties, kickback schemes, conflicts of interest, expense policy abuse.
Combined exposure: 3 to 8 percent of annual payment volume.
Measured exposure across five institutional verticals
The following figures represent documented, published improper payment and fraud exposure across the five institutional markets JIL addresses. Every dollar in this table flowed through a system that verified the format of the payment instruction - not whether the recipient was legitimate, eligible, or alive on the date the payment was made.
| Vertical | Annual Exposure | Source |
|---|---|---|
| Non-Medical Insurance (P&C / Auto / Life / WC) | $221.5B | Coalition Against Insurance Fraud 2024 |
| Credit Card / Payments | $145.6B | Mastercard / Nilson Report 2024 |
| Medical Insurance / CMS | $87.1B | CMS HHS Agency Financial Report FY2024 |
| Government Entitlements (SSI / SNAP / HUD / TANF / UI / VA) | $39.1B+ | GAO FY2024; SSA OIG; USDA FNS; HUD OIG; DOL OIG; HHS ACF; VA OIG |
| Banking (BEC / Wire / ACH / Check) | $30B+ | ABA; FinCEN 2024; FBI IC3 2023 |
| Total | $523B+ |
65 to 80 percent of this combined $523B+ exposure is directly attributable to the absence of a pre-settlement attestation gate. It is not sophisticated fraud that evades detection. It is structural vulnerability that no current system addresses before funds move.
Why existing infrastructure fails each vertical
Healthcare and Government Programs - pay first, audit later. 79% of Medicaid improper payments in FY2024 resulted from missing or insufficient documentation. The documentation gate does not exist before settlement.
Government Entitlements - no program verifies recipient eligibility in real time before each disbursement. The SSA paid an estimated $4.6 billion in benefits to deceased individuals over a recent multi-year period because death record matching runs on a batch lag, not at payment time.
Non-Medical Insurance - carriers release claim payments without pre-settlement verification that the contractor is credentialed, the claimant is eligible, or the payment instruction has not been redirected. 20% of all insurance claims filed in the US are estimated fraudulent.
Banking - legacy systems validate message format and routing codes, not cryptographic beneficiary integrity. A payment instruction in the correct SWIFT or ACH format with a valid account number will clear regardless of whether that account belongs to the intended recipient. This is the architectural gap BEC exploits every day.
Credit Card / Payments - 70% of chargebacks are estimated fraudulent misuse rather than legitimate consumer protection. The chargeback mechanism exists because settlement is reversible. Visa's own pilot found 54% of fraud had already passed through existing bank and PSP fraud systems before being caught.
The Investigation Engine addresses what has already left
For institutions with months or years of payment history, the question is not just "how do we prevent this going forward?" but "how much has already gone out that we can recover?"
JIL's Investigation Engine reconstructs the exact compliance and eligibility status of every payee on the exact date of every historical payment - and seals the finding with post-quantum cryptographic proof suitable for federal investigative referral, False Claims Act proceedings, and recovery litigation. 100 million records in 10 to 20 minutes.
This retroactive capability addresses the Investigation Engine's primary market: government entitlement programs and healthcare payers where years of improper payments have accumulated and the political and fiscal urgency for recovery is high.
JIL Sovereign: The Payment Integrity Network
111-check Verdict Engine and post-settlement proof infrastructure for tokenized assets, fiat payments, and cross-border corridors. Verify before execution, prove every outcome. Three settlement modes on a single protocol.
| Mode | Use Case | Speed | How It Works |
|---|---|---|---|
| Tokenized Asset | RWA-to-RWA, securities | T+0 (<5s) | Native on-chain atomic settlement. Single shared ledger eliminates reconciliation. |
| Fiat Settlement | Cross-border payments | <10s on-chain + rail | Transient Tokenization: mint, settle, burn. Fiat in/out via banking partners. |
Key Principles:
- Neutral infrastructure: JIL does not compete with banks or asset managers. We are the settlement coordination layer between their systems. Policy remains with participants; process enforcement is ours.
- DvP/PvP process enforcement: JIL enforces deterministic Delivery versus Payment and Payment versus Payment workflows. Both legs must be present and matched before final settlement.
- Attestation-based compliance: Banks attest to compliance status. JIL validates attestation signatures and enforces at protocol level. Banks remain obligated entities.
- Event emission, not reporting: JIL emits immutable event artifacts. Banks consume these for SAR/CTR/FATF filing. JIL does not file regulatory reports.
- Settlement premium: Internal protocol corridor classifications apply only to final settlement events. Routine custody transfers and internal movements incur no protocol fee. Base gas is burned 100%. Client engagement fees are negotiated separately; see jilsovereign.com/pricing (live settlement attestation at 35-90 bps per event, $1 minimum floor; retroactive validation starting at 5 bps per record).
- Token-optional: Banks can settle using fiat invoices. Holding JIL tokens provides fee discounts within the negotiated engagement range.
- Swiss legal framework: JIL Sovereign Technologies, Inc. (Wilmington, Delaware) with primary hub in Zurich, designed for FINMA supervision.
14-of-20 BFT consensus across 13 jurisdictions. 9,500 TPS per node.
No single jurisdiction, cloud provider, or political bloc can control enough validators to censor or unilaterally shut down the network.
1.5 seconds. Deterministic finality (not probabilistic). Once a block is confirmed, it is irreversible. 9,500 TPS sustained per node on medium-grade servers (benchmarked February 2026). Projected 15,000+ TPS per node on production hardware. With 20 nodes processing in parallel, aggregate network throughput reaches approximately 200,000 TPS. Exceeds DTCC/SWIFT peak processing requirements.
Zone Architecture
Three compliance zones enforced at the protocol level by validators, not smart contracts.
Protected Zone
Tokenized securities, institutional RWA settlement. SEC Reg D/S, MiFID II, MiCA, FINMA compliant.
- Full KYC/AML verification
- Accredited investor checks
- Hold period enforcement
- Transfer whitelist
Premium Zone
Stablecoins, fiat settlement, and payments. FinCEN and FIU reporting compliant.
- Sanctions screening
- Jurisdiction containment
- Travel rule evaluation
- Fiat settlement and RFQ venues
Cross-zone isolation is enforced at consensus: Protected zone assets cannot be moved to Unprotected to bypass compliance. Upgrades require full compliance onboarding.
Cross-Chain Bridge: Wrapper token bridge (wBTC-JIL, wETH-JIL, wUSDC-JIL) for cross-chain asset support with deposit-mint and unwrap-burn flows, secured by 14-of-20 validator consensus. Cryptographic finality receipts and evidence bundles are generated for every settlement event, providing audit-ready proof and dispute resolution artifacts.
Internal protocol corridor classifications. These designations govern validator throttle limits and risk tiers. Client engagement fees are negotiated separately - see jilsovereign.com/pricing.
| Corridor | Zone | Venue | Throttle | Use Case |
|---|---|---|---|---|
| protected | Protected | RFQ only | 3K/min | Institutional RWA settlement |
| fiat | Premium | Direct | 10K/min | Fiat-to-fiat cross-border settlement |
| default | Premium | RFQ | 6K/min | Standard operations |
Ledger Architecture Competitive Analysis
Database-level and architectural comparison of JIL Sovereign L1 against five leading blockchain networks. JIL's purpose-built hybrid data architecture is optimized for compliance, auditability, deterministic finality, and Human Flourishing accountability.
| Dimension | JIL Sovereign | XRP Ledger | XDC Network | Solana | BNB Chain | Polygon |
|---|---|---|---|---|---|---|
| Core DB Model | Hybrid multi-model (ledger + graph + columnar + doc + KV) | Hash tree (modified Merkle) over LevelDB | XDPoS over modified Ethereum MPT + LevelDB | AccountsDB (columnar KV) + Merkle tree | Geth fork: Merkle Patricia Trie + LevelDB | Plasma/PoS: Merkle checkpoints over LevelDB |
| Consensus | BFT (deterministic finality, 14-of-20 validators) | RPCA federated byzantine agreement | XDPoS 2.0 (HotStuff BFT) | PoS + PoH timestamps | Proof-of-Staked Authority (PoSA), 21 validators | PoS with Heimdall BFT checkpointing |
| Finality Type | Deterministic (instant, 1.5s) | Probabilistic (3-5s practical) | Deterministic (~2s) | Probabilistic (~400ms slots, optimistic) | Probabilistic (~3s) | Probabilistic (checkpoints every ~30 min) |
| Primary Use Case | Institutional asset settlement (DTCC equivalent) | Cross-border payments and liquidity bridging | Trade finance and RWA tokenization | High-throughput dApps, DeFi, NFTs | General purpose EVM-compatible DeFi | Ethereum L2 scaling for high-volume dApps |
| Smart Contracts | None - settlement protocol only (by design) | Hooks (limited, newly added) | EVM-compatible (full Solidity) | Sealevel parallel VM (Rust/C) | EVM-compatible (full Solidity) | EVM-compatible (full Solidity) |
| Native Compliance | Yes - 12 ZK compliance services at protocol layer | Partial (some KYC hooks) | Partial (XinFin compliance layer) | None native (app-layer only) | None native (app-layer only) | None native (app-layer only) |
| Document Storage | Native SDV, JRC-721 standard (on-chain doc layer) | None (off-chain only, IPFS pointers) | None (off-chain only) | None (off-chain only) | None (off-chain only) | None (off-chain only) |
| Human Flourishing Layer | 10% of JIL's profits allocated to Human Flourishing initiatives - anti-trafficking, financial inclusion, and economic empowerment. | None | None | None | None | None |
| Fee Structure | 90% JIL operations (validator infrastructure, attestation services, compliance stack, protocol development). 10% Human Flourishing (10% of profits). | Dynamic market-based (XRP burned) | Dynamic (gas market, lower than ETH) | Dynamic (gas market, very low) | Dynamic (gas market, low vs ETH) | Dynamic (gas market, MATIC fees) |
| Analytics Layer | Native columnar audit trail (no external indexer) | External (XRPL Data API, Bithomp) | External (XDC Explorer, The Graph) | External (Helius, The Graph, Bitquery) | External (BSCScan, The Graph) | External (Polygonscan, The Graph) |
| ZK Proof Services | 12 native ZK proof services at protocol layer | None | None | Light client ZK work (partial) | None | Polygon zkEVM (separate chain) |
| Validator Count | 20 (14-of-20 consensus, geo-distributed) | ~150 UNL validators (federated) | ~108 masternodes (XDPoS 2.0) | ~1,700 validators (permissionless) | 21 validators (PoSA, permissioned) | 100+ validators (PoS checkpointing) |
| Throughput | 9,500/node (200K+ aggregate) | ~1,500 TPS | ~2,000 TPS | ~65,000 TPS (theoretical) | ~2,200 TPS | ~7,000 TPS |
| Decentralization | Federated (institutional grade, by design) | Low (UNL federated trust model) | Moderate (masternode network) | High (permissionless PoS) | Low (21 validators, centralized) | Moderate (PoS with ETH checkpoints) |
| Target Market | Institutional finance, RWA, governments | Banks, payment providers, remittance | Trade finance, banks, SME cross-border | DeFi, NFTs, retail, high-freq apps | DeFi, GameFi, retail, BSC ecosystem | Ethereum dApps needing scale, gaming, DeFi |
Chain-by-Chain Analysis
XRP Ledger (XRPL)
XRPL uses the Ripple Protocol Consensus Algorithm (RPCA), a federated consensus model. Its database is a hash tree (SHAMap) over LevelDB - not a Merkle Patricia Trie like Ethereum. XRP is JIL's closest conceptual peer in intent - both target institutional payments and cross-border settlement - but XRPL lacks native compliance services, document storage, Human Flourishing allocation, and ZK proof infrastructure. XRP's fee model burns tokens rather than allocating revenue to validators, treasury, and Human Flourishing.
Key distinction: XRP is optimized for liquidity bridging. JIL is optimized for final settlement of tokenized assets with built-in compliance and audit trails.
XDC Network
XDC is a Geth fork using XDPoS 2.0 consensus (HotStuff BFT). Its database is Ethereum's Merkle Patricia Trie over LevelDB. XDC targets trade finance and RWA tokenization, making it a direct market competitor. It supports full EVM compatibility (Solidity smart contracts), which gives it a larger developer ecosystem but introduces arbitrary state bloat and smart contract risk that JIL deliberately avoids.
Key distinction: XDC accepts arbitrary smart contracts; JIL does not. Settlement-only operations make JIL more predictable and auditable for institutional use.
Solana
Solana uses AccountsDB - a purpose-built columnar KV store - with a Merkle tree for state root computation. Its signature innovation is Proof of History (PoH), a cryptographic clock that orders transactions before consensus. Solana's Sealevel parallel execution enables ~65,000 TPS theoretical throughput but introduces complexity that has caused multiple network outages. Its database model is the closest to JIL's columnar layer, but Solana is a general-purpose chain.
Key distinction: Solana optimizes for consumer throughput. Its probabilistic finality and network stability history are disqualifying for institutional settlement.
BNB Chain / Polygon
BNB Chain is a near-direct Geth fork using PoSA consensus with only 21 elected validators - one of the most centralized chains in this comparison. Its centralization and Binance ownership create regulatory and counterparty risk institutional settlement infrastructure cannot accept.
Polygon PoS is an Ethereum sidechain (not a true L2) using dual-layer architecture: Bor for block production and Heimdall for checkpointing to Ethereum. Finality is probabilistic at the transaction level, anchored to Ethereum at ~30 min checkpoint intervals. It is inherently dependent on Ethereum's security.
JIL's hybrid architecture is a deliberate design decision driven by institutional settlement requirements. Six layers work together: (1) Append-only ledger core - immutable, cryptographically chained settlement records satisfying audit and regulatory requirements. (2) Graph layer - multi-party settlement flows, cross-chain bridge routing, and validator peer relationships. (3) Columnar audit trail - fee allocation records (90% JIL operations / 10% Human Flourishing), Human Flourishing disbursements, and compliance event logs optimized for analytical queries without external indexers. (4) Native document store (SDV) - JRC-721 Lightweight Document Token Standard for on-chain document lifecycle management. (5) Key-value hot path - wallet balances, subscription tiers, and validator stake weights with sub-millisecond lookup. (6) 12 native ZK proof services - compliance verification, identity attestation, and privacy-preserving audit trails at the protocol layer. No competitor offers all six layers natively. "Hybrid" describes the architecture. The consensus mechanism is strictly Proof of Stake. Read the full architecture document →
The distributed ledger serves one purpose - creating an immutable, tamper-proof record of every verification event. It is the infrastructure for record integrity, not the product itself.
111 checks. 15 signal categories. FWEA coverage. Under 2-second verdict.
Every transaction submitted to JIL passes through the Verdict Engine before funds move. The engine runs 111 independent checks, organized into 15 signal categories, and produces a single cryptographically signed verdict: Allow, Review, or Block. Each check contributes a weighted score; the aggregate verdict is deterministic, reproducible, and anchored to the blockchain as immutable evidence.
JIL's Verdict Engine runs 111 checks across 15 signal categories. Every engagement is scoped to the subset relevant to the institution's payment type, corridor, and risk profile. A regional bank protecting against BEC wire fraud activates 6 checks. A Medicaid MCO protecting against improper provider payments activates 7. A P&C carrier containing post-disaster fraud rings activates 8. A state entitlement agency stopping payments to deceased and ineligible recipients activates 10.
The full engine is available. What runs against any given payment type is scoped at engagement time. The table below documents all 111 checks and their signal categories so institutions can identify which subset applies to their specific exposure.
| # | Category | Checks | Weight |
|---|---|---|---|
| 1 | Identity and Counterparty Integrity * | 7 (16 proposed) | 20% (25% proposed) |
| 2 | Payment Rail-Specific Fraud | 17 | 20% |
| 3 | Regulatory Compliance Flags | 11 | 15% |
| 4 | Transaction Behavior and Velocity | 7 | 15% |
| 5 | Settlement Instruction Integrity | 7 | 15% |
| 6 | Healthcare and Government Rails | 5 | 5% |
| 7 | Macro and Systemic Flags | 4 | 10% (8% proposed) |
| 8 | Cross-Jurisdiction Typology Correlation | 6 | 5% (4% proposed) |
| 9 | Emerging Threat Intelligence | 2 | 5% (3% proposed) |
| Total | 111 (69 FWEA + 42 WIE) | 100% | |
* Category 1 expanded from 7 to 16 checks with ID-008 through ID-016 (deceased, eligibility, license, employment, citizenship verification). The engine runs 111 checks across 15 categories. See BID Extended Identity Checks. The new checks address confirmed, quantified loss categories ($380B+ annually) rather than probabilistic emerging threats.
FWEA Framework - Unified Loss Coverage
The Verdict Engine is architected around the FWEA framework: every check is mapped to one or more of the four loss categories (Fraud, Waste, Error, Abuse). This ensures no loss pathway is orphaned between vendor silos. A typical institution running JIL gets coverage of 3 to 8 percent of annual payment volume that would otherwise disappear into the gap between fraud tools, policy engines, and audit functions.
- Fraud pillar (0.5 to 2.5%): identity checks, payment rail-specific fraud signals, adversarial ML detection, emerging threat intelligence.
- Waste pillar (2 to 6%): duplicate detection, overpayment pattern analysis, settlement instruction integrity, velocity anomalies.
- Error pillar (0.3 to 1.2%): beneficiary binding mismatch, account-to-name validation, currency and amount sanity checks, reference data validation.
- Abuse pillar (0.2 to 1.0%): split-transaction detection, threshold evasion, policy corridor enforcement, ghost-counterparty analysis, cross-jurisdiction typology correlation.
Extended Fraud Intelligence - 14 Advanced Checks
Within the 111-check Verdict Engine, 14 checks constitute the Extended Fraud Intelligence layer - advanced signals that target the highest-severity and fastest-evolving threats in institutional finance. These checks are distributed across categories but share a common architecture: specialized detectors, cryptographic evidence capture, and explainable-AI verdict rationale.
- Pig butchering and romance-investment scam detection
- AI voice deepfake authorization analysis
- Fraud-as-a-Service (FaaS) marketplace intelligence
- DPAN (Device Primary Account Number) tokenization abuse
- Magecart and payment skimmer correlation
- Zero-knowledge proof (ZKP) compliance attestation
- Real estate transaction laundering detection
- Trade-Based Money Laundering (TBML) indicators
- Bust-out fraud pattern recognition
- CBDC and digital currency flow analysis
- Consortium-wide shared intelligence signals
- Adversarial ML and model evasion detection
- Post-quantum TLS handshake validation
- Explainable AI (XAI) verdict rationale generation
Each check is versioned. Each verdict is signed. Each evidence bundle is hash-anchored to the JIL L1 ledger and co-signed by 14 of 20 validators. An auditor or regulator can replay any verdict, inspect the exact check versions and input data that produced it, and cryptographically confirm the result was not altered after the fact. See FWEA Framework and Extended Fraud Intelligence for full specifications.
Corridor Configurations by Vertical
Each institutional vertical has a pre-configured corridor that activates the relevant check subset. Corridors are configured at engagement time and enforce only the checks applicable to that payment type.
| Vertical | Corridor Name | Checks Activated | Primary Fraud Vectors Addressed |
|---|---|---|---|
| Healthcare / Medicare / Medicaid | healthcare-provider | 7 (categories 1, 6) | Unenrolled providers, documentation gaps, upcoding, cross-payer duplicates |
| Non-Medical Insurance | insurance-claims | 8 (categories 1, 5, 6, 7) | Ghost contractors, staged claims, surge anomalies, BEC on vendor payments |
| Banking / Wire / ACH | bank-payment | 6 (categories 1, 2, 5) | BEC account substitution, instruction interception, duplicate wires |
| Government Entitlements | entitlement-disbursement | 10 (categories 1, 3, 6, 7) | Deceased recipients, address fraud, cross-state duplicate enrollment, provider capacity |
| Legal / Asset Investigation | asset-investigation | 8 (WIE categories 10-15, category 1) | Hidden on-chain holdings, pre-proceeding asset movement, UBO concealment |
| Credit Card / Merchant | card-settlement | 7 (categories 2, 4, 5) | Chargeback abuse, CNP fraud, merchant impersonation, BEC on settlements |
| Cross-Border Treasury | cross-border | 9 (categories 1, 2, 3, 8) | Corridor sanctions, BEC, TBML, correspondent chain anomalies |
All corridor configurations are defined in the JIL Corridor Policy Registry. Custom corridors are available for institutions with non-standard payment profiles.
Retroactive identity integrity for institutional payment history.
The Verdict Engine addresses payments going forward. The Investigation Engine addresses payments that have already been made.
For any institution with a history of payments - CMS disbursements, insurance claim payouts, bank wire transfers, entitlement benefit payments - the Investigation Engine runs the same identity and eligibility verification against every historical record and returns a date-anchored, cryptographically sealed verdict on each one.
The key technical distinction: the Investigation Engine does not ask what the recipient's status is today. It reconstructs what the recipient's status actually was on the exact date each historical payment was made. A provider whose license was revoked in March 2023 but who continued receiving CMS reimbursements through December 2023 will appear in the findings as having been ineligible for each specific payment in that nine-month window - with the exact date, the exact check that failed, and the cryptographic proof sealed at processing time.
Technical specifications
- Processing capacity: 100 million records in 10 to 20 minutes
- Identity dimensions: 28 per record
- Lookback window: unlimited - engagements have run 4+ year histories
- Proof standard: CRYSTALS-Dilithium post-quantum signature on every finding; SHA-256 sealed verdict bundle; independently reproducible by any auditor or court
- Output format: structured evidence package per record, suitable for federal investigative referral, False Claims Act proceedings, and recovery litigation
The 28 identity dimensions
Death records (SSA DMF and state vital statistics), OIG exclusion (date-anchored), license revocation or expiration, SOS dissolution status, NPI and PECOS disenrollment, DUNS and UEI entity match, EIN and IRS TIN verification, business license active at payment date, bank account age and tenure, address classification (storefront / office / vacant / P.O. Box), address tenure, marriage and spousal benefit eligibility, voter registration cross-reference, citizenship and DHS SAVE eligibility, UBO deceased or excluded, capacity versus billing volume plausibility, geographic service area plausibility, SAM.gov debarment (date-anchored), cross-program enrollment status, household composition consistency, income and asset consistency, provider enrollment network cross-reference, digital asset holdings (undisclosed on-chain), DeFi position detection, corporate registry status (date-anchored), beneficial ownership graph, connected-party payment tracing, and rapid post-receipt asset movement detection.
Starting at 5 basis points per record. Scope, check depth, and volume priced per engagement. Revenue-share available: 10% of confirmed recovered funds, zero upfront cost.
Referral pathways by vertical
| Vertical | Investigation Output | Referral Pathway |
|---|---|---|
| Healthcare / CMS | Provider eligibility failures, documentation gaps | HHS OIG, CMS ZPIC, DOJ Civil (FCA) |
| Government Entitlements | Deceased recipients, cross-state duplicates, ineligible recipients | SSA OIG, HHS ACF, DOL OIG, State AG |
| Non-Medical Insurance | Ghost contractors, staged claim patterns, cross-carrier duplicates | State Insurance Fraud Bureaus, NICB, DOJ Civil |
| Banking / Wire | Historical BEC patterns, instruction anomalies, duplicate payments | FBI IC3, FinCEN SAR, internal recovery |
| Legal / Divorce / Litigation | Hidden assets, pre-proceeding transfers, UBO concealment | Court filing, expert witness, regulatory referral |
| Federal Vendors / Contracts | SAM-debarred vendors, EIN mismatches, dissolved entities | GSA IG, Agency IG, DOJ Civil |
Beneficiary verification at the verification layer. Before funds move.
Business Email Compromise causes over $2.7 billion in annual losses. Traditional payment rails verify routing and account numbers but never verify the identity of the actual recipient. JIL changes this.
Every settlement instruction submitted to JIL must include a cryptographic beneficiary binding. The binding is a SHA-256 hash computed from the beneficiary's LEI (or wallet identity), their account identifier, and the settlement instruction ID. This binding is created by the originating institution at instruction submission time, signed with the originator's Ed25519 API key, and is immutable - any change to the beneficiary after binding causes a hash mismatch and the settlement is rejected.
Gate 1 - Submission
Binding hash is computed from provided fields, verified against the binding signature, and stored. If the signature is invalid or the beneficiary is on a sanctions list, the instruction is rejected immediately.
Gate 2 - Compliance Check
During the COMPLIANCE_CHECK state, the stored binding is re-verified against settlement_parties data. If the beneficiary data has been tampered with, the settlement transitions to REJECTED with reason BENEFICIARY_BINDING_MISMATCH.
Gate 3 - Finality
The finality receipt includes the binding hash, verification timestamp, and a flag confirming the BEC check passed. This provides an immutable audit trail proving the correct beneficiary received the funds.
Attacker intercepts an invoice and changes the beneficiary account. Institution submits settlement instruction with the modified account. Gate 1: Binding hash computed from (LEI + modified account + instruction ID) does not match the pre-registered binding. Settlement is rejected with BENEFICIARY_BINDING_MISMATCH. Institution is alerted before any funds move.
BID - Beneficiary Identity Dispatch
BID is a standalone, monetized API product built on the beneficiary binding technology described above. Banks integrate BID to verify beneficiary identity before releasing funds - independent of whether they use JIL for full settlement. The end-to-end flow: the sending bank submits a verification request to JIL BID, which validates the beneficiary binding hash, confirms the Ed25519 signature, runs sanctions screening, and forwards the verified result to the receiving bank. The entire check completes in under 500ms. Pricing ranges from $0.12 to $0.50 per verification depending on tier (Starter, Pilot, Pro, Enterprise), making it accessible for banks of any size.
Exhaustive Identity Verification. BID performs five categories of identity checks, each backed by specialized vendor integrations: Phone verification (Twilio Lookup API - carrier identification, line type, subscriber name match, reachability), Email verification (DNS MX resolution, SMTP deliverability, disposable domain detection), Address verification (Smarty/SmartyStreets - USPS and international standardization, deliverability, residential/commercial classification, geocoding), Person verification (sanctions screening via OFAC SDN and internal lists, PEP status, adverse media), and Company verification (Middesk and OpenCorporates - business registration, officer identification, UBO discovery across 140+ jurisdictions). All person and company checks route through JIL's Compliance API for sanctions decisions and through the Analytics Integrations API for multi-provider blockchain risk scoring (Chainalysis KYT, Elliptic, TRM Labs - weighted composite scores). The architecture is fail-safe: when any upstream provider is unavailable, BID continues using JIL's internal heuristic engine with reduced confidence scores, ensuring verification never blocks settlement.
BID serves as the wedge product in JIL's go-to-market strategy - the first low-friction touchpoint that gets banks onto JIL infrastructure before full settlement adoption. A bank starts with BID for beneficiary verification on existing SWIFT flows, sees the speed and accuracy, then migrates settlement corridors to JIL over time. See the BID product page, BID API Specification, and Compliance Architecture for integration details.
Five Pillars of Settlement Integrity
Beneficiary binding (Pillar 1, above) is one of five settlement integrity pillars that JIL enforces simultaneously through a single protocol layer. The remaining four pillars complete the framework:
Pillar 2 - Policy Corridor Enforcement. Each settlement corridor (e.g., US-to-EU, APAC-to-MENA) can define automated compliance rules - jurisdiction-specific thresholds, sanctions screening, and escrow hold periods - enforced at the protocol level. This addresses the $4.3B in sanctions fines accumulated between 2015-2023 and the 33K daily SWIFT compliance alerts that currently require manual triage.
Pillar 3 - Deterministic Finality. Settlement achieves irreversible finality in under 5 seconds through 14-of-20 BFT validator consensus across 13 compliance zones. Unlike probabilistic finality (Bitcoin, Ethereum) or T+1/T+2 settlement windows (SWIFT, DTCC), JIL provides deterministic completion - once confirmed, settlement cannot be reversed or disputed.
Pillar 4 - Audit-Ready Receipts. Every settlement produces a portable finality receipt containing the beneficiary binding hash, compliance check results, validator signatures, and timestamp evidence. These receipts are independently verifiable and satisfy audit requirements without requesting additional documentation from counterparties - addressing the 42% KYC audit failure rate and over $10B in cumulative AML fines.
Pillar 5 - Neutral Integrity Layer. JIL operates as Swiss-anchored, self-custody infrastructure owned by no counterparty. It does not hold funds, take positions, or favor any participant. This structural neutrality unlocks the $14T currently locked in nostro/vostro accounts by providing a shared evidence layer that all parties trust without trusting each other.
These five pillars are protected by JIL's provisional patent portfolio covering MPC key splitting, ZK compliance, BPoH soulbound NFTs, autonomous AI management, self-healing contracts, and retroactive validation engine (historical payment file reconstruction with post-quantum cryptographic sealing). Enforcement infrastructure is deployed across 13 compliance zones with 190+ production microservices.
Transient Tokenization. Fiat in, fiat out. The verification layer is invisible.
A non-transferable, non-tradeable on-chain representation of fiat value that exists for < 30 seconds. Not a stablecoin. Not e-money. Not a stored-value instrument.
Fiat Received
From sending bank via banking partner API (FedNow, SEPA Instant, SWIFT gpi)
KYC/AML/Sanctions
Pre-check via compliance-api (< 200ms)
Transient Token Minted
To sender vault (< 2s block inclusion)
ZK-Compliance Proof
Generated (< 1s)
Atomic Transfer
On shared ledger with deterministic finality (< 5s)
Transient Token Burned
In same block
Event Artifact Emitted
Immutable regulatory audit trail
Fiat Released
To receiving bank via optimal rail
Steps 1-7 complete in under 2 seconds. Step 8 depends on the receiving bank's payment rail: FedNow (< 30s), SEPA Instant (< 10s), Faster Payments (< 2hrs), SWIFT gpi (1-2 days). JIL removes 80-90% of SWIFT's delay; the remaining time is the fiat last mile.
Regulatory positioning: Transient tokenization avoids classification as a stablecoin, e-money, or payment instrument. Token has no independent value and cannot exist outside the settlement window. It cannot be traded, transferred, approved, or held by any party. JIL never holds customer funds. Banking partners remain obligated entities for all regulatory compliance.
Message passing vs. shared ledger. The difference is structural.
| Dimension | SWIFT (Today) | JIL Sovereign |
|---|---|---|
| Architecture | Message-passing between siloed ledgers | Single shared ledger, atomic state changes |
| Intermediaries | 2-4 correspondent banks per transfer | Zero. Direct sender-to-receiver on one ledger |
| Settlement time | 1-5 business days | < 10 seconds on-chain + fiat rail |
| Cost | 25-50 bps ($15-50 per message + fees) | 25 bps flat |
| Reconciliation | Required at every hop. Manual. | None. Shared ledger = shared truth |
| Compliance | Each bank screens independently | Protocol-level ZK-compliance, one check |
| Finality | Reversible for days (recall risk) | Deterministic and irreversible at block confirmation |
| Nostro/Vostro | Pre-funded accounts at each correspondent | Pre-funded liquidity pools (more capital efficient) |
Tiered Verdict Engine pricing. Retroactive audit at 1 bps. Revenue-share optional.
JIL is priced per transaction verdict, not per dollar settled. Three real-time tiers scale from baseline fraud coverage to full FWEA stack. A retroactive audit product priced at 80 percent discount lets institutions run the Verdict Engine across historical payment volume to quantify existing FWEA exposure and recover losses.
| Tier | Price | Coverage | Target Client |
|---|---|---|---|
| Starter Real-Time | 5 bps / tx | Core Verdict Engine (111 checks, 15 categories) | Baseline FWEA coverage for all institutions |
| Pro Real-Time + Enrichment | 7 bps / tx | Verdict Engine + third-party enrichment + typology correlation | Mid-market banks, fintechs, treasury operations |
| Enterprise Full Stack | 12 bps / tx | Verdict Engine + enrichment + consortium intelligence + dedicated SentinelAI | Tier-1 banks, global asset managers, payment networks |
| Retroactive Audit | 1 bps / historical tx | Full 111-check engine replayed over historical payment volume (80% discount) | Institutions quantifying existing FWEA exposure |
| Retro + Real-Time Bundle | 0.5 bps retro + real-time tier | Historical audit plus ongoing real-time coverage | Institutions committing to long-term JIL deployment |
| Revenue-share option: 10 percent of recovered funds in lieu of, or in addition to, per-transaction pricing | |||
A regional bank with 50 million transactions per year runs a 4-year retroactive audit: 200 million historical transactions at 1 bps per transaction equals approximately 2 million dollars in audit cost. At a conservative 3 percent FWEA exposure rate, the Verdict Engine identifies roughly 60 million dollars in Fraud, Waste, Error, and Abuse findings. Typical recovery rates of 20 to 35 percent yield 12 to 21 million dollars in actual recovered funds - a 6x to 10x return on the audit spend, before any real-time coverage is added. See Retroactive Payment Audit for full methodology.
Legacy institutional settlement pricing: JIL also operates a separate settlement corridor product at 25 to 35 basis points per settlement event for tokenized asset settlement, cross-border fiat corridors, and cross-chain DvP / PvP operations. This is distinct from Verdict Engine pricing and applies only when JIL acts as the authoritative settlement record. 35 bps standard, 25 bps for volume corridors above 100 million dollars per month, 1 dollar minimum per settlement event.
Token-optional: Institutions can pay Verdict Engine and settlement fees by standard invoice (ACH, wire, or credit card), digital asset (ETH, USDC, USDT), or JIL token. Holding JIL tokens is an optional operational decision that provides additional fee discounts. Base gas is burned 100 percent. Treasury and Human Flourishing allocations are funded from the fixed 90/10 split (90% JIL operations / 10% Human Flourishing) on protocol-level fees.
0x9347efffa3e8985e0d35536b408cab48599971e8 (Sourcify verified)
JILTreasury contract deployed on Ethereum mainnet (0x84fF5974c8C00F5B323965d925478A244E7d504F - Sourcify verified) with 5 vaults: Validator Incentives (1B), Protocol Treasury (3B), Operations (2B), Ecosystem Fund (1B), and Strategic Reserve (0.5B). Total: 7.5B JIL managed under multi-vault governance.
Token migration contracts available for holders of deprecated token versions (v1 and v2). 1:1 swap ratio, deadline May 1, 2026. Both contracts verified on Sourcify.
No existing platform combines settlement speed, compliance, and fiat invisibility.
| Feature | JIL | SWIFT | Ripple/XRP | DTCC | Fireblocks |
|---|---|---|---|---|---|
| Settlement speed | < 5 seconds | 1-5 days | 3-5 seconds | T+2 | Chain-dep. |
| Finality | Deterministic | Reversible | Probabilistic | T+2 | Varies |
| Cost | 35-90 bps | 25-50 bps | < 1 bps | Varies | 10-50 bps |
| Fiat settlement | Yes (transient) | Yes (slow) | Yes (XRP bridge) | No | No |
| Compliance | Protocol-level | Per-bank | Per-bank | SRO rules | Policy engine |
| Neutrality | Swiss, neutral | Cooperative | US corp | US SRO | Custodial |
| Token required | No (optional) | No | Yes (XRP) | No | No |
| Crypto visible | Invisible for fiat | N/A | Visible (XRP) | N/A | Visible |
vs Ripple
Ripple requires banks to hold XRP as a bridge asset - a significant adoption barrier. JIL's transient tokenization is invisible to end users. Sender sends dollars, recipient gets dollars.
vs SWIFT
SWIFT passes messages between siloed ledgers. JIL provides a single shared ledger with atomic settlement. JIL removes the correspondent banking chain entirely.
vs Fireblocks
Fireblocks is custodial infrastructure (institutions give up keys). JIL is self-custody settlement (institutions keep keys, we settle).
Competitors address individual settlement problems - Ripple optimizes speed, SWIFT optimizes connectivity, Fireblocks optimizes custody. JIL addresses all five settlement integrity pillars simultaneously: beneficiary binding, policy corridor enforcement, deterministic finality, audit-ready receipts, and neutral infrastructure. This is protected by 48 patent claims (10 independent + 38 dependent) across the full stack. View the Settlement Integrity Framework →
Post-quantum cryptography. MPC custody. 5.2M+ certified tests.
Cryptographic Foundation
MPC 2-of-3 threshold signing for self-custody. Post-quantum cryptography migration path via pq-epoch-registry. 14-of-20 BFT consensus with geopolitical distribution across 13 jurisdictions. Zero-knowledge compliance proofs for privacy-preserving verification.
Operational Security
Modular compliance engines: Identity, Sanctions, Accredited Investor, Travel Rule, Jurisdiction Containment, Hold Periods, Transfer Whitelists. Regulator read-only audit APIs with jurisdiction filtering. Court order enforcement via multi-party authorization.
SentinelAI Fleet Inspector
Real-time validator monitoring, threat scoring, and automated remediation across all mainnet validators. Continuous health assessment and anomaly detection.
Test Coverage
5.2M+ certified tests across 190+ microservices. External audit pre-mainnet. Permissioned contracts (only JIL services can call). Emergency pause capability.
Retail products operate on a separate site.
Retail and consumer products (wallet, ramps, and related tooling) operate at getjil.com with their own pricing and commercial strategy. They are not prerequisites for institutional integration and are excluded from this whitepaper.
From pre-sale to network effects. Built, deployed, and operating.
| Timeline | Milestone | Details |
|---|---|---|
| Q1 2026 | Pre-sale + Development | Token pre-sale at $0.09. Complete fiat settlement module development. Banking partner outreach. |
| May 1, 2026 | Settlement Protocol Live | JIL mainnet with tokenized asset settlement, Verdict Engine, Vault. Fiat settlement on testnet. |
| Q3 2026 | Fiat Settlement Live | First banking partner live on mainnet for fiat settlement. FedNow + SEPA Instant integration. |
| Q4 2026 | Scale | 10 banking partners, $100B/month volume. FINMA license application. Additional rail integrations. |
| 2027 | Network Effects | 25+ banks. Cross-institutional settlement becomes standard. Series B optional. |
$40M raise. $1.2T+ addressable market. Network effects create the moat.
Competitive Moat: Network effects. Once 3-5 institutions settle on JIL, every counterparty needs access. This is the DTCC dynamic.
Human Flourishing: 10% of JIL's profits are allocated to Human Flourishing - not a tax on clients. JIL earns through infrastructure, not donations.
The Payment Integrity Network. 111 checks. 15 categories. FWEA coverage in under 2 seconds.
JIL Sovereign is the only unified FWEA coverage engine in production - closing the 3 to 8 percent payment volume gap that single-point fraud tools, policy engines, and after-the-fact audits leave behind. Operational today with 190+ microservices deployed, 10 mainnet validators across 13 jurisdictions, 48 patent claims pending, and cryptographic proof of every verdict.