Developer APIs · Settlement Integrity
Portable Trust APIs for Money Movement.
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, parameterized, 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.
Business use
Build trust into the payment flow.
Money movement is fragmented across institutions, wallets, rails, and jurisdictions. Each participant repeats verification, loses context, and accepts unnecessary risk. JIL Money Passport APIs provide reusable trust signals that can move with the transaction - and the evidence that backs each signal travels along with it.
Four core APIs
What you can call from day one.
AccreditedID Issuer API
Verify and re-attest investor accreditation status under SEC Rule 506(c). Sealed attestation per investor, refreshable on demand.
ProofOfFunds Title / Escrow API
Verify proof of funds at the moment of bid, escrow opening, or wire instruction. Evidence sealed to the named transaction.
SourceOfFunds Exchange API
Trace source-of-funds for crypto and fiat deposits through a structured attestation. AML/CFT alignment.
IncomeVerify Lender API
Income verification with audit-grade evidence. Lender receives a structured attestation, not a checkbox.
Use cases
Where Money Passport lands.
Payment pre-clearance
Banks and fintechs pre-clear payments with reusable trust signals that survive across hops.
Wallet risk checks
Wallet platforms add identity, accreditation, and source-of-funds attestation as a deposit gate.
Account verification
Beneficial-owner and account-holder verification with sealed evidence at the moment of onboarding.
Beneficiary validation
Confirm beneficiary identity and account match before wire transfer, with audit-grade evidence.
Cross-border payment review
Travel Rule-aligned attestations and corridor-specific compliance checks at the API layer.
Government disbursement
Federal and state programs verify beneficiary eligibility and account routing before disbursement.
Technical deep dive
How the APIs work in practice.
- POST /v1/accreditedid
- POST /v1/proofoffunds
- POST /v1/sourceoffunds
- POST /v1/incomeverify
- GET /v1/attestation/{id}
- GET /v1/evidence/{id}
Signed request with subject identifiers and check scope. Response includes verdict, reason codes, attestation ID, evidence reference, cryptographic timestamp, and expiry. JSON over HTTPS.
Identity match, document review, KYB/KYC alignment, sanctions and PEP overlay, address and phone signal, beneficial-owner chain, and accreditation history.
Where the call relates to crypto movement, wallet typology, counterparty graph, and sanctions exposure can be included in the attestation context.
Every response includes an evidence reference. Pulling the evidence returns the CREB with documents, source citations, and cryptographic seal under FRE 902(13).
Subscribe to attestation lifecycle events: ready, expired, revoked, or recertified. Webhooks signed with shared secret.
API keys plus mTLS for production. Per-tenant isolation. Rate limits configurable per integration. Encryption in transit and at rest. Audit logging on every call.
What this is not
Scope, plainly.
- Not a bank account
- Not custody
- Not a payment rail by itself
- Not a legal opinion
- Not a guarantee of transaction approval
Add trust to your payment flow at the API layer.
Brief your developer or product lead. We will walk the four endpoints, the attestation response model, the evidence retrieval flow, and sandbox access.
Request developer access Request technical design