Privacy
Peer verifies only the payment details needed to settle an order, and keeps your personal data off-chain.
How verification stays private
Before you verify a payment, the Peer app or the PeerAuth extension checks the attestation of Peer's verification enclave, an AWS Nitro Enclave, and encrypts your payment-platform login session to it. The enclave reads the matching payment from the platform over HTTPS, checks it against the order (amount, currency, recipient and time) and signs an attestation. Sellers and Peer operators can't read your encrypted session.
Only the attestation goes on-chain. Your name, account details, balances and other transactions don't.
Who sees what
| Data | Who can see it |
|---|---|
| Your payment-platform login session | Only the verification enclave, in memory. Sellers and Peer operators can't |
| The payment record used for verification | The verification enclave |
| Payment details listed for you to select | The Peer page or integrator you approved in the extension |
| Your payment name or handle | Your counterparty, as with any payment, and Peer services. Never posted on-chain |
| Your wallet address, order amounts, rate and currency | Public, like any on-chain transaction |
What this means in practice
- Sellers see your payment like any payment they receive. They never see your balance or other transactions.
- Buyers see only the payee details a seller chose to publish.
- The protocol has no identity checks; your identity stays with your payment platform.
- On-chain observers see amounts, wallet addresses, rates, and hashed payment-method and currency IDs that map to known platforms. Seller payment handles are stored only as hashes.
For the technical detail, see Buyer TEE Verification.