01 / Merchant reconciliation desk
Two ledgers.
One clear account.
Pair what you charged with what you delivered. Find the exceptions. Keep the evidence.
Payment records 0
Paste JSON or inspect source
Your payments belong here.
Import a JSON array from your billing system.
Files stay in this browser. Up to 10,000 records.
Follow the request
Delivery logs 0
Paste CSV or inspect source
Every delivery leaves a trace.
Import a CSV with request references and status.
Quoted cells and multiline fields are supported.
02 / A precise account
Show the gap.
Keep the context.
One merchant dataset per session. Request IDs are compared as trimmed, case-sensitive strings. A matching reference links records; it does not prove that a payment or delivery happened.
Exact amounts, separate currencies
Decimal strings are converted to integer units at 18 decimal places. No floating-point arithmetic, rounding or exchange-rate conversion. Up to 18 fractional digits are accepted; this is input precision, not a claim about any token's on-chain decimals.
Charges and refunds are independent
Net per currency = charges − refunds. Repeated records remain in totals until you correct the source. Multiple charges for one request and currency are review signals, not confirmed billing errors.
Evidence before claims
Imported JSON is unverified. Signature checking and recovery requests need external services. Your local review and exports work without an account, token or wallet.
03 / Portable service access
A shared receipt index, by design.
Receipt Otter Access is a proposed application token for batch services, cross-merchant receipt indexing and team difference reports. A portable entitlement could let independent tools recognize service access and report contributions. These network services and their token necessity remain to be validated. No token has been issued; local reconciliation requires none.