Bind every payment to a verified counterparty.
Business Email Compromise and invoice redirection cost organizations $2.77 billion per year (FBI IC3). The root cause - payment instructions are not bound to verified identities. BID fixes this at the protocol layer.
or email contact@jilsovereign.com
How BID eliminates payment fraud
Four capabilities that close the identity gap at the instruction layer.
BID Record Directory
Every beneficiary registered with cryptographic identity binding - a hash of their verified KYC data, payment endpoints, and organizational metadata. BID records are immutable once confirmed and provide the anchor for all downstream verification.
Endpoint Governance
Payment endpoints versioned and tracked. Any change to an endpoint triggers an automatic hold window. The previous endpoint remains active until the change is explicitly approved through the configured workflow.
First-Payment Risk Scoring
Elevated risk score for new BID records or changed endpoints. This score factors in endpoint age, verification depth, organizational trust history, and counterparty relationship duration to flag high-risk first payments before release.
Approval Workflows
Configurable maker-checker workflows for BID record creation and endpoint changes. Organizations define approval chains, threshold triggers, and escalation paths. No single actor can modify a beneficiary identity binding unilaterally.
How it works
A BID record is the cryptographic anchor for every payment.
BID Record Structure
{
"bid_id": "bid_8f3a...c7d2",
"entity_hash": "sha256(kyc_provider + entity_ref)",
"endpoints": [
{
"type": "bank_account",
"hash": "sha256(routing + account)",
"version": 3,
"status": "active",
"verified": "2026-01-15T10:30:00Z"
}
],
"trust_score": 0.92,
"created": "2025-11-02T08:00:00Z",
"last_payment": "2026-02-20T14:22:00Z"
}
Endpoint Change Flow
Change Requested
Authorized user submits new endpoint. The request is logged with requestor identity, timestamp, and change details.
Hold Window Activated
Configurable hold period (default 48h). Previous endpoint remains active. All payments during the hold are flagged for review.
Approval and Activation
Maker-checker approval confirmed. New endpoint version activated. BID record trust score recalculated.
Privacy and compliance
BID does not store PII. It stores identity binding hashes that connect to regulated KYC providers. The directory contains cryptographic proofs of identity verification - not the identity data itself. All personal data remains with the licensed KYC provider under the applicable data protection regime.
Stop paying unverified counterparties.
Learn how the Beneficiary Identity Directory binds every payment to a verified identity - eliminating invoice redirection and first-payment fraud at the protocol layer.
or email contact@jilsovereign.com