JPMorgan Kinexys
JPMorgan's permissioned blockchain for institutional payments — formerly Onyx/JPM Coin.
CTR (USD 10,000+)TRAVEL-RULE (USD 3,000+)ENHANCED-DUE-DILIGENCE (USD 50,000+)
Step 1 · Originating Institution (Kinexys Member)Policy-Enforced
A JPMorgan corporate banking client logging into their treasury management system — the institution has been pre-vetted at onboarding.
The originating institution initiates a payment on Kinexys. Every Kinexys member has completed JPMorgan's institutional KYB — bank-grade due diligence, legal entity verification, beneficial ownership disclosure. L4+L5 lit: identity and authorization are policy-enforced. The compliance center of gravity is here: the network itself is permissioned, so joining IS the compliance gate. D9 (prudential) applies because Kinexys members are regulated financial institutions.
Step 2 · Kinexys Compliance & RoutingCode-Enforced
An internal bank compliance desk reviewing a large-value transfer — the payment is screened under JPMorgan's own compliance framework before execution.
Kinexys runs internal compliance checks: sanctions screening, AML pattern detection, and Travel Rule data exchange between member institutions. Because the network is permissioned, both counterparties are known entities with full KYB on file. L3 Execution lit — screening runs at the network layer, code-enforced by Kinexys smart contracts. The compliance overhead is lower than public chains because identity is pre-established.
Step 3 · JPM Coin Transfer (On-Ledger)Code-Enforced
An intraday repo or Fedwire transfer between banks — value moves on a trusted, permissioned ledger with immediate finality.
JPM Coin (bank deposit token) transfers on the Kinexys ledger from originating to beneficiary institution. L1+L2+L3 lit — the full stack below the enforcement line processes the transfer. Because Kinexys is a permissioned ledger operated by JPMorgan, consensus is achieved among known validators. No public mempool, no MEV risk, no bridge — the transfer is internal to JPMorgan's infrastructure.
Step 4 · Beneficiary Institution ReceiptPolicy-Enforced
The beneficiary bank's treasury account showing the credit — the payment has arrived on the institutional ledger.
The beneficiary institution receives JPM Coin. L4+L5 lit on the receiving side. The institution can hold JPM Coin, redeem to fiat, or use it as collateral within the Kinexys ecosystem. Because both parties are JPMorgan clients, the settlement is a book transfer on JPMorgan's ledger — no external settlement risk.
Step 5 · Settlement Finality & ReportingPolicy-Enforced
The bank's internal ledger posting — final, reconciled, and reported to regulators.
Settlement is final on the Kinexys ledger. Both institutions hold matching records. JPMorgan provides the regulatory reporting infrastructure — the permissioned network means every transaction is fully attributed to identified institutions. L5 Application lit only. This is the cleanest compliance story on the wholesale rail: every participant is a regulated bank, every transaction is fully traceable, and the network operator is JPMorgan.
Resolved 5 steps across 1 chain(s). 3 threshold(s) triggered. Frameworks: Bank Secrecy Act, GENIUS Act, OFAC Sanctions Program, FATF Recommendation 16 (Travel Rule), Common Reporting Standard / FATCA.
VASP Compliance Engine
Entity classification, jurisdiction mapping, Travel Rule compliance, nested services detection, governance, and monitoring.