Payment proof
Rail, asset, amount, payee, nonce, expiry, transaction/signature, and payment binding where supported.
Wisely EnterprisesAgent-payment infrastructure
Receipts and proof
A receipt should say what was requested, what was paid, what was fulfilled, what proof exists, and whether reconciliation confirmed it.
Rail, asset, amount, payee, nonce, expiry, transaction/signature, and payment binding where supported.
Resource, method, payload hash, output summary, result hash, provider request id, and idempotency key.
Confirmed, failed, missing, replay-blocked, refund/credit queue, reconciliation drift, and payout packet state.
External trust: public proof endpoints are intentionally safe to read. Private logs, secrets, customer payloads, and sensitive settlement internals stay out of public artifacts.