Browser Extension
Why is the extension needed for some things?
A blockchain cannot directly check a Cash App or Wise payment, and screenshots can be edited. Some fiat orders need a verified payment record before funds can be released.
The uSwap extension finds the payment in your browser session and prepares it for verification. Sign in on the payment platform itself. Never paste your password into a chat or the bridge.
It is needed when the order asks for browser-based payment or account verification. Ordinary crypto swaps do not need it. Some on-ramp orders also offer mobile verification through PeerAuth.
From payment to verification
| Step | What happens |
|---|---|
| 1. Pay | You complete the transfer in the payment app using the order's instructions. |
| 2. Select | The verification flow finds the payment record. You select the transaction for this order. |
| 3. Verify | The verification system checks the platform record against the order's requirements. |
| 4. Continue | An accepted result lets the order proceed. Any remaining swap or delivery steps still have to complete. |
Verification can check the amount, currency, recipient, time, and transaction ID. The fields depend on the payment method.
How do zero-knowledge proofs fit in?
A zero-knowledge proof can prove something about private data without revealing all of it. For example, it can prove that a qualifying payment happened without exposing the full account history.
zkTLS applies this idea to HTTPS website data. It lets verification check that payment information came from the platform.
The current browser payment flow uses TEE-backed verification through Peer. A TEE is an isolated execution environment. The extension encrypts payment-session material for the verification service, which checks the record and returns an attested result.
This has different trust assumptions from a zero-knowledge proof. “Proof” in an order's interface does not mean every verification step is a zero-knowledge circuit.
What stays private?
Verification is designed to share the details needed to check a payment, not your whole browsing session or account history. The payment is not anonymous:
- Your payment platform still knows your account and transaction.
- The other party sees the details normally visible for that transfer.
- The verification result includes the fields required by the method. The TEE flow also processes encrypted session material in the verification environment.
Only approve verification for the account, platform, and action you intend. Never share a wallet seed phrase, login code, or private bridge link with someone claiming to help.
Install and use it
- Open uswap.net/extension and follow the current installation instructions.
- Return to the same order and choose the extension verification option.
- Approve the connection, sign in on the payment platform if needed, and select the matching transaction.
- Wait for the verification result on the order.
If the app reports an outdated or unavailable extension, update it and reload the order. If a payment is not listed, check the account, platform, and transaction status before trying again. Retrying verification does not require paying again.
For the underlying capture and attestation design, see Peer's extension architecture.