Signed receipts and audit.
Autonomous payments need a record you can check, not a record you have to trust. Every SwapEazi settlement returns a receipt carrying a signed audit record. It proves what authority was exercised, for whom, and for what purpose, and anyone with the public key can verify it offline.
The audit trail is cryptographic, not a dashboard promise
A dashboard tells you what a server chose to display. A signed record tells you what actually happened, and lets you prove it later without asking anyone. Each receipt embeds an audit record signed with an ed25519 key, plus the public key to verify it. The signature covers the decision, so a receipt cannot be edited after the fact without breaking it.
The record binds the identities involved into one chain of custody: the principal's KYC reference, the agent, the exact mandate, the beneficiary, and the payout order. A mandateHash ties the receipt back to the precise signed mandate that authorised it, so a receipt and its mandate always agree.
A settlement receipt
Verify the audit record against auditPublicKey. The chain block is the answer to the question a dispute really asks: which authority was exercised, and for whom.
Observability and disputes, answered by proof
This is what a control plane usually sells as two separate dashboards. Here they are one artefact. Observability is the signed record of every settlement. Disputes are resolved by pointing at that record: it names the purpose the payout was declared for, the beneficiary it reached, and the mandate that permitted it.
The simulated field is always present and always surfaced. It states plainly whether the payout was a real-funds settlement or a sandbox run, and it stays true until the licensed payout integrator is live in production. A receipt never pretends to be more than it is.