Every payment managed and evidenced · Release Record v1

Every payment managed and evidenced, in an open format anyone can verify.

SwapEazi manages cross-border payments and waits for your approval, and every figure is evidenced. Every payment it manages ends in a Release Record: who approved it, on what evidence, and proof the record has not been touched since. An auditor, a board or a counterparty can verify it without taking our word for it.

What it saves

An audit sample that closes in minutes, not weeks.

A finance team that pays suppliers, staff or partners abroad spends days each audit rebuilding why each large payment went the way it did: emails, screenshots, a rate someone saw. Every payment SwapEazi manages ends in a Release Record, written at the moment of release, so the evidence exists before anyone asks for it. The auditor verifies the record itself, not a story about it.

What a record proves

Four facts, each one provable.

What was decided
The amount and currency, your own payment reference, the policy and version it was held to, whether an independent view of the route was in hand and valid, and the outcome: met, miss, exception or not material.
Who released it, and when
A named person, a system or an agent, with the time of release and the time the record was written. An agent release above its limit shows who signed it off.
That nothing changed since
A SHA-256 hash over everything the record states. Change one character and the hash no longer matches.
Where it sits in your history
Each record carries the hash of the one before it, so a record cannot be removed, reordered or slipped in without breaking the chain. A signature with our published key proves we issued it.
Why an auditor can trust it

Verification needs no account and no trust in us.

The format, the hash and the signature are published. The public key is at /api/v1/attestations/keys. With the record, the key and twenty lines of code from the spec, an auditor verifies it on their own machine with no network at all. A payment released without an independent view is still recorded, as a miss: the record shows the gap instead of hiding it. SwapEazi never holds or moves money; the record is the evidence of a payment SwapEazi managed, your team approved and your own bank, provider or wallet carried out.

Verify a record

Paste one in. Every test is named.

The box holds a synthetic two-record sample. Verify it, then change the amount and verify again to see the hash and the chain catch the change. Schema, hash, chain link and signature each come back pass, fail, not verified or not signed. Nothing you paste is kept.

For developers, platforms and agents

Ask for it by name.

Release Record schema
/schemas/release-record-v1.json
Rate Receipt schema
/schemas/rate-receipt-v1.json: each figure behind a route assessment, what was read and when.
Verifier
POST /api/v1/releases/verify with { record }, { records: [...] } or { record, chain: [...] }. No key.
MCP tool
verify_release_record, keyless, on https://swapeazi.io/api/mcp.
Versioning
The version is in the schema URL. v1 is fixed; any change to a field or to what the hash covers is a new version, and v1 records keep verifying.