Experimental test credits. Requests never authorize payment. Matching signatures remain Pending Sync; no funds or settlement service are connected.
ECHO PAY · NEARBY / SIGNED EXCHANGE
Echo Nearby
Internet optional.
Two signatures. One agreement.
The receiver signs a request. The payer reviews its terms and signs an intent tied to that exact request.
Local verification
Awaiting a checkPending Sync
Run a check below. No current verification is displayed.
The Twin reflects your local check. You choose what to sign. A valid signature does not prove identity, funds or settlement.
How the signed handoff travels
- Agree on the receiver. Confirm full keys separately. In the signed exchange, the receiver creates a request and keeps its ID.
- Review and sign. The payer checks the amount, receiver and expiry, then explicitly authorizes the exact intent.
- Carry the same bytes. Use QR, an exported file or copied packet. A third carrier can pass it onward; the packet is readable.
- Check and retain. The receiver verifies locally and keeps an exported copy. Pending Sync remains pending; there is no settlement connection.
Prepare both devices before disconnecting. Scanning never approves an action. Open the two-device guide →
YOUR ECHO / TEMPORARY TEST KEY
Your temporary test key
Each person uses a separate device or browser profile. Hiding or reloading this page discards the signing key. Export your signed request before reloading.
No key created.
01 / RECEIVER
Create a signed request
No request prepared.
Signed request · no payment authorization
Keep the exported request and its ID. Anyone carrying this packet can read its terms.
02 / PAYER
Verify, then decide
A signature authenticates a key. Confirm the receiver through a channel you trust; a scanned name or address alone does not establish identity.
No request checked.
No authorization prepared.
Pending Sync
03 / RECEIVER OR INDEPENDENT VERIFIER
Verify before accepting
Check the instruction, not a promise of payment. Verification below does not accept funds or acknowledge delivery.
Use your original request and separately retained request ID. Matching never proves payment, delivery, proximity or one-time use.
No match checked.
Instruction checked · Pending Sync
Still unknown: available funds, current revocation, spending on other devices, delivery and settlement. Your device clock is not trusted network time. A signing key is not proof of a person's identity.
Technical comparison details
Watch the signature hold
After a successful comparison, test a changed amount on a separate copy of the intent. Your matched original remains unchanged.
Retained authorizations
This browser retains up to 32 signed responses and their requests. Retrying the same request with the same payer key returns the existing response. This local convenience does not prevent spending or reuse elsewhere. Export what you need to keep.