Where Verify is needed
| Flow | Why it needs Verify |
|---|---|
| Wise technical route | Legacy Wisetag registration exists, but Wise's current policy prohibits receiving P2P crypto-sale payments. |
| PayPal seller deposits | One-time PayPal.me registration; confirm that PayPal has preapproved the activity first. |
| Supported proof capture | Payment-provider metadata capture where the browser session is part of the proof path. |
| Other payment methods | Venmo, Cash App, Revolut, Zelle, Monzo, and Chime do not need this registration step. |
What the extension is
- A Chrome Manifest V3 extension for approved origins including usdctofiat.xyz and peerlytics.xyz.
- A stateless metadata bridge exposed as window.peer to the web app.
- A setup tool for extension-gated payment methods before creating meaningful seller liquidity.
- A narrow browser boundary for supported TEE/proof capture flows.
What it is not
- Not a wallet and not a place where USDC is held.
- Not a sidepanel, dashboard, proof history, or settings product.
- Not a generic payment-app scraper for arbitrary websites.
- Not required for every USDCtoFiat payment method.
Privacy boundary
Verify keeps capture sessions in tab-scoped memory and clears them after the provider tab closes, the metadata is returned, or the page is removed. It is designed around approved origins and does not add a saved extension account.
The extension helps the app prove or register the specific payment-app detail needed for a route. It does not publish your full payment-app history onchain, and it does not change the non-custodial contract path: your wallet still signs, and Base contracts still hold and release USDC.
