Settlement Receipt API - Cryptographic Verification

Overview

Every settled transaction on JIL Sovereign produces a cryptographic receipt - a tamper-proof record signed by the validating nodes. Receipts serve as the canonical proof that a settlement occurred, who participated, what amount moved, and which compliance attestations were applied.

Receipts are independently verifiable by any party without needing access to the JIL network. An external auditor, regulator, or counterparty can verify a receipt using only the public Sovereign Compliance Network (SCN) validator keys and the receipt data itself.

Retrieve a Receipt

GET /v1/receipt/{tx_id}

Response

{
  "receipt_id": "rcpt_8e2b1a3f",
  "tx_hash": "0xabc123def456789abcdef0123456789abcdef0123456789abcdef0123456789a",
  "amount": 1000,
  "currency": "USD",
  "corridor": "US-BR",
  "from_wallet": "0x7Bcff27567cfE3e67020a0d771a445178756aBa2",
  "to_wallet": "0x84fF5974c8C00F5B323965d925478A244E7d504F",
  "compliance_attestation": {
    "kyc_verified": true,
    "aml_cleared": true,
    "jurisdiction_approved": true,
    "risk_score": 0.12
  },
  "validator_signatures": [
    {
      "SCN validator": "SCN validator-us",
      "signature": "ed25519:3a7b9c1d2e4f5a6b...",
      "signed_at": "2026-03-27T14:30:44Z"
    },
    {
      "SCN validator": "SCN validator-de",
      "signature": "ed25519:8f2e1a3b4c5d6e7f...",
      "signed_at": "2026-03-27T14:30:44Z"
    }
  ],
  "receipt_hash": "sha256:e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855",
  "receipt_signature": "ed25519:9a8b7c6d5e4f3a2b1c0d9e8f7a6b5c4d3e2f1a0b...",
  "settled_at": "2026-03-27T14:30:45Z"
}

Receipt Hash Computation

Hash Formula receipt_hash = SHA-256( tx_id + amount + currency + corridor + timestamp )

The receipt hash is computed deterministically from the core transaction fields. This hash is then signed by validating nodes using Ed25519 to produce the receipt signature. Any party can recompute the hash from the receipt data and verify the signature against the SCN validator public keys.

Verification

GET /v1/receipt/{tx_id}/verify

Verification Response

{
  "receipt_id": "rcpt_8e2b1a3f",
  "valid": true,
  "hash_verified": true,
  "signatures_verified": 2,
  "signatures_required": 1,
  "validator_keys_used": [
    "SCN validator-us:ed25519:pk_a1b2c3d4...",
    "SCN validator-de:ed25519:pk_e5f6a7b8..."
  ],
  "verified_at": "2026-03-27T14:35:00Z"
}

The verification endpoint recomputes the receipt hash, validates each Ed25519 signature against the known SCN validator public keys, and confirms the receipt has not been tampered with. This process requires no authentication - anyone with the tx_id can verify the receipt.

API Endpoints

Method	Endpoint	Description
`GET`	`/v1/receipt/{tx_id}`	Retrieve the full receipt for a transaction
`GET`	`/v1/receipt/{tx_id}/verify`	Verify a receipt cryptographically
`GET`	`/v1/receipt/batch`	Retrieve receipts for multiple transactions

Use Cases

Audit Trail Provide auditors with cryptographic proof of every settlement, including compliance attestations and SCN validator signatures

Regulatory Reporting Generate verifiable reports for regulators with receipts that can be independently validated without platform access

Counterparty Verification Share receipts with counterparties as proof of payment - they verify independently using public SCN validator keys

Dispute Resolution In case of disputes, receipts provide a tamper-proof record of what occurred, signed by independent SCN validators