Attestation · every movement of money carries provable facts
A receipt anyone can verify — no login, no trust required
Every completed conversion issues an attestation receipt: amounts, fee waterfall, locked rate, on-chain transaction hash — and a content hash over the canonical record. Your bank, your auditor, your counterparty’s compliance system (human or AI) can check it independently.
Sample receipt (redacted)
Receipt · rcp_SAMPLE0001
sha256 · bfae0683f3b3c311070e27d035db6463bcd41a4fa0e791ee417a78b8cd9fc63a
{
"receipt_id": "rcp_SAMPLE0001",
"order_id": "ord_SAMPLE0001",
"initial_amount": {
"currency": "AUD",
"minor": 100000000,
"decimal": "10000.00"
},
"fees": [
{
"label": "conversion",
"amount": {
"currency": "AUD",
"minor": 3000000,
"decimal": "300.00"
}
}
],
"final_amount": {
"currency": "USDT",
"minor": 6320500000,
"decimal": "6320.50"
},
"rate": "1.5349",
"destination_tx_hash": "0x3f8a29c41e77b2SAMPLE",
"issued_at": "2026-07-01T03:24:07Z"
}The content hash is computed over the canonical JSON (right). Change one digit anywhere and the hash no longer matches — that is the whole point.
Verify it yourself
Pre-filled with the sample above. Edit any character of the hash and watch it fail.
Verify a receipt — no login
This box checks against our sandbox verification endpoint and currently recognises the published sample receipt only. Production receipts issue with the production API (spec-first — see developers).
For banks and auditors
Behind every receipt sits an evidence pack: KYC snapshot, order, deposit record with payer-name match result, approval trail and release confirmation — assembled per transaction, exportable on request. Our target for a bank-inquiry response is 30 minutes from request to pack. Scope and current build status are labelled honestly on platform and legal.