[Bug]: x402 transactions marked as "deceptive request"

Nobody has claimed this yet.

### Describe the bug

Hey guys! I'm using x402 as a payment mechanism on my site to make it agent-friendly. I'm not doing anything deceptive, but I get warnings anyway. I didn't see this on my staging tests on the fuji testnet but I do see it here. It's going through PayAI to facilitate the transactions.

### Expected behavior

I want x402 transactions to be treated as payment requests only. You can still warn or let people know the risks, but it shouldn't scare users away.

### Screenshots/Recordings

### Steps to reproduce

On my site, go to https://attago.bid and sign up for the basic account.

If you don't want to do that, understandable, but you just need to make an x402 payment from the browser.

### Error messages or log output

```shell
See the screenshots. The payment DID go through just fine, I just had to bypass a lot of checks that will scare off users.
```

### Where was this bug found?

Live version (from official store)

### Version

13.18.1

### Build type

None

### Browser

Chrome

### Operating system

Windows

### Hardware wallet

_No response_

### Additional context

It surprised me when I pushed to production to go to a live network rather than a test network and it started firing these warnings.

### Severity

Gosh, I dunno, but it's going to be hard to get users to go past that error, so it impacts my payment scheme (which is legitimate).

Start by reproducing the x402 payment on attago.bid in Chrome with MetaMask 13.18.1 on the live network, then compare the behavior with the Fuji testnet flow. Use the screenshots and warning text to identify why the legitimate payment is classified as a deceptive request; done means x402 payments remain usable without that warning while appropriate risk notices are preserved.

Written by the indexing model from the issue text.