Product / Money Passport APIjilsovereign.com/docs/money-passport
On This Page
01 AccreditedID 02 ProofOfFunds 03 SourceOfFunds 04 IncomeVerify 05 How It Works 06 Developer Experience 07 What You Get 08 Pricing and Access 09 Sandbox and POC
Developer API

Money Passport API

Four endpoints. One API key. Verified identity, accredited status, proof of funds, source of funds, and income verification, each returning a cryptographically sealed attestation. Developer-first, parametized, court-ready on every call.

Traditional KYC and AML checks produce a checkbox. Money Passport produces evidence. Each API call returns a structured attestation sealed to CourtChain™: who was verified, what was checked, what the result was, and the cryptographic proof that the result has not been altered. The same evidentiary standard JIL applies to billion-dollar settlement flows, available as a REST call.
4
Endpoints
REST
API-first
CREB™
Per attestation
3
Pricing tiers
01AccreditedID

Verify accredited investor status against SEC criteria. The API ingests identity and financial data, validates against regulatory thresholds, and returns a sealed attestation confirming accredited status. The attestation is re-verifiable by the issuer, the fund, or the regulator without re-collecting the investor's documents. Designed for Reg D offerings, fund subscriptions, and tokenized securities issuance.

02ProofOfFunds

Verify that a counterparty holds sufficient funds to complete a transaction. The API validates account balances, liquidity positions, or asset holdings against a specified threshold and returns a sealed attestation. No raw financial data is exposed to the requesting party. The attestation proves sufficiency without disclosing the actual balance. Built for real estate closings, M&A escrow, and institutional onboarding.

03SourceOfFunds

Trace and attest the origin of funds for AML and regulatory compliance. The API maps the provenance chain of a specified amount, validates against sanctions lists and known typologies, and returns a sealed attestation of source legitimacy. Designed for correspondent banking, cross-border treasury, and high-value transaction onboarding where source-of-funds documentation is a regulatory requirement.

04IncomeVerify

Verify income claims against authoritative data sources. The API validates stated income against employer records, tax filings, or payroll data and returns a sealed attestation confirming or flagging the claim. No underlying records are transmitted to the requesting party. Built for lending underwriting, tenant screening, benefits eligibility, and immigration visa processing (H-1B wage verification, EB-5 investment threshold).

05How it works
4 endpoints · selective disclosure · one API key
Money Passport API - Selective Disclosure with Sealed Attestation Four endpoints (AccreditedID, ProofOfFunds, SourceOfFunds, IncomeVerify) route through a single Money Passport hub. Authoritative source data enters the hub but never reaches the caller. Only the sealed CREB™ attestation is returned across the selective-disclosure boundary. Caller endpoints (1 key) Money Passport hub · selective disclosure Caller output AccreditedID POST /api/accreditedid Reg D · fund subscriptions ProofOfFunds POST /api/proofoffunds Real estate · M&A escrow SourceOfFunds POST /api/sourceoffunds AML · correspondent banking IncomeVerify POST /api/incomeverify Lending · H-1B · EB-5 Money Passport hub Authoritative-source verification + sealed attestation Authoritative sources (raw, never returned) SEC accred. Plaid + bank OFAC / SDN IRS + payroll CLEAR / TLO FINRA SEC EDGAR FATF typologies Selective disclosure Verdict Engine validates and signs Only the result + CourtChain™ ref crosses the boundary FRE 902(14) self-authenticating · raw evidence stays inside CREB™ returned to the calling app { "result": "verified", "verdict": "PASS", "courtchain_ref": "0x...", "fre_902_14": true, "raw_data": null, "hash": "0x7a3f9c..." } Re-verifiable by any party CourtChain™ seal · 4 endpoints · 1 API key · zero raw-data leak
i
API call with parameters
ii
Verdict Engine validates
iii
Attestation sealed to CourtChain™
iv
CREB™ returned to caller

Every endpoint follows the same pattern: the caller submits a structured request with the subject's consent, the Verdict Engine validates against authoritative sources, the attestation is sealed to CourtChain™, and the caller receives a CREB™ containing the verdict, the evidence hash, and the CourtChain™ reference. The CREB™ is self-authenticating under FRE 902(14). The caller never receives raw underlying data, only the attested result.

06Developer experience
  • REST API. Standard JSON request/response. OpenAPI 3.0 spec published. SDKs for Python, Node, Go, and Java.
  • Parametized pricing. Three tiers: Pilot (free sandbox, synthetic data), Production (per-call pricing), Enterprise (volume commitment).
  • Sandbox available now. Instant API key at testnet.jilsovereign.com. Synthetic data. Full endpoint coverage. No KYC required for sandbox.
  • Webhook notifications. Async results delivered via webhook for long-running validations. Idempotent request IDs on every call.
07What you get
  • Sealed attestation per call. Every API response includes a CREB™ sealed to CourtChain™. Re-verifiable by any party with the reference.
  • Selective disclosure. The subject's raw data never reaches the caller. The attestation proves the claim without exposing the evidence.
  • Court-ready evidence. FRE 902(14) self-authenticating. Designed for regulatory submission, litigation hold, and audit response.
  • 15+ year retention. Attestations persist on CourtChain™. The caller can re-verify years after the original call.
08Pricing and access
SandboxFree. Instant API key at testnet.jilsovereign.com. Synthetic data. Full endpoint coverage. No commitment.
ProductionPer-call pricing. Volume tiers available. Flat fee per attestation. No percentage of transaction value.
EnterpriseAnnual volume commitment with dedicated support, custom SLAs, and priority Verdict Engine processing.
DocumentationOpenAPI 3.0 spec, SDK libraries, integration guides, and sample CREB™ packages at jilsovereign.com/docs.

Start building in the sandbox today.

Instant API key, synthetic data, full endpoint coverage. Production keys available after KYC. No NDA required for sandbox access.

Sandboxtestnet.jilsovereign.comDocsjilsovereign.com/docsPOC Requestjilsovereign.com/connect