Caliza · Schema

TravelRuleProofResponse

A wallet ownership proof for a self-hosted wallet recipient. The microtransfer instruction fields are present only while a PENDING microtransfer test awaits its on-chain deposit.

CompanyFintechPaymentsCross-Border PaymentsStablecoinsRemittancesForeign ExchangeVirtual AccountsPayoutsKYCLatin America

Properties

Name Type Description
id string
recipientId string
walletAddress string The wallet address the proof covers.
chain string The blockchain of the wallet address (for example `ETH` or `TRON`).
method string How the proof was produced.
status string Lifecycle status of the proof. PENDING applies only to microtransfer tests awaiting their deposit; EXPIRED means the validity window has passed; INVALIDATED means the recipient's Travel Rule data chan
verifiedAt string
expiresAt string For a VERIFIED proof, when it expires. For a PENDING microtransfer test, the deadline for the test deposit to arrive.
expectedAmount number Microtransfer tests only — the exact amount to send from the wallet being proven.
expectedCurrency string Microtransfer tests only — the currency of the test transfer.
destinationAddress string Microtransfer tests only — the address to send the test transfer to (the beneficiary's own Caliza wallet; the test amount is credited to the beneficiary's balance).
View JSON Schema on GitHub

JSON Schema

caliza-travel-rule-proof-response-schema.json Raw ↑
{
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "$id": "https://raw.githubusercontent.com/api-evangelist/caliza/main/json-schema/caliza-travel-rule-proof-response-schema.json",
  "title": "TravelRuleProofResponse",
  "description": "A wallet ownership proof for a self-hosted wallet recipient. The microtransfer instruction fields are present only while a PENDING microtransfer test awaits its on-chain deposit.",
  "x-generated": "2026-10-14",
  "x-method": "derived",
  "x-generator": "derive-json-schema.py",
  "x-source": "openapi/caliza-api-documentation-reference-openapi.yml#/components/schemas/TravelRuleProofResponse",
  "type": "object",
  "properties": {
    "id": {
      "type": "string"
    },
    "recipientId": {
      "type": "string"
    },
    "walletAddress": {
      "type": "string",
      "description": "The wallet address the proof covers."
    },
    "chain": {
      "type": "string",
      "description": "The blockchain of the wallet address (for example `ETH` or `TRON`)."
    },
    "method": {
      "type": "string",
      "description": "How the proof was produced.",
      "enum": [
        "SIGNATURE",
        "MICROTRANSFER"
      ]
    },
    "status": {
      "type": "string",
      "description": "Lifecycle status of the proof. PENDING applies only to microtransfer tests awaiting their deposit; EXPIRED means the validity window has passed; INVALIDATED means the recipient's Travel Rule data changed after the proof was collected.",
      "enum": [
        "PENDING",
        "VERIFIED",
        "EXPIRED",
        "INVALIDATED"
      ]
    },
    "verifiedAt": {
      "type": "string",
      "format": "date-time"
    },
    "expiresAt": {
      "type": "string",
      "format": "date-time",
      "description": "For a VERIFIED proof, when it expires. For a PENDING microtransfer test, the deadline for the test deposit to arrive."
    },
    "expectedAmount": {
      "type": "number",
      "description": "Microtransfer tests only — the exact amount to send from the wallet being proven."
    },
    "expectedCurrency": {
      "type": "string",
      "description": "Microtransfer tests only — the currency of the test transfer."
    },
    "destinationAddress": {
      "type": "string",
      "description": "Microtransfer tests only — the address to send the test transfer to (the beneficiary's own Caliza wallet; the test amount is credited to the beneficiary's balance)."
    }
  }
}

Work with this as data

Every JSON Schema here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for schemas

4 MCP tools reach this
  • find_json_schemasBrowse and filter every JSON Schema in the catalog.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This JSON Schema
curl "https://apis.io/api/v1/json-schemas/caliza-travel-rule-proof-response"
All schemas
curl "https://apis.io/api/v1/json-schemas?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

A second provider on the same verified email joins the account you already have.