---
name: safegate-commerceproof-verify
description: Get an independent verdict on evidence of a Base USDC payment. Use when you hold a Base transaction hash, or a SafeGate CommerceProof, and need it checked against the chain through two independent RPC providers before you rely on it. Paid 0.05 USDC per call over x402, charged only on a VERIFIED verdict. Does not verify delivery of goods or services.
---

# SafeGate CommerceProof verification

## When to use this

Use it when you hold evidence that a payment happened and you need that evidence
checked by something other than the party who gave it to you. Typical moments:

- A counterparty sends you a transaction hash and says "paid". You want the chain
  to agree before you ship, release, or record it.
- You hold a SafeGate CommerceProof and need its signer, screening and on-chain
  legs checked together.
- You are reconciling and need a verdict you can cite, with its scope written
  down.

## When NOT to use this

- **You need proof of delivery.** SafeGate does not verify that anything was
  delivered. `commerce_verified` is always `false`. No input changes that.
- **You need a signed attestation.** This deployment does not sign. Its
  `signing_capability` is `NONE_BY_DESIGN` and its assurance ceiling is
  `OBSERVED`.
- **You need sanctions screening on a bare transaction hash.** The `payment`
  input performs none. Use the `proof` input for the screened path.
- **You just want to read a transaction.** A public block explorer is free. Pay
  SafeGate when you need the independence, the agreement requirement, and a
  verdict with a written scope.

## How to call it

### Step 1. Discover the price for free

```http
POST /api/commerceproof/verify-paid HTTP/1.1
Host: pay.safegatelabs.xyz
Content-Type: application/json

{}
```

You get `402`. The body and the `PAYMENT-REQUIRED` header carry the same object,
so price and payee cannot drift between them. Read `accepts[0]` for the payment
requirements and `extensions.bazaar` for the input shapes.

### Step 2. Choose your input

Send **exactly one**.

**You only have a transaction hash:**

```json
{ "payment": { "transaction_hash": "0x7d10...4b7c" } }
```

**You have a full CommerceProof:**

```json
{ "proof": { "...": "a SafeGate CommerceProof object" } }
```

Both in one body returns `400 AMBIGUOUS_INPUT`. Neither returns
`400 PROOF_REQUIRED`. SafeGate does not guess.

### Step 3. Pay and call

```http
POST /api/commerceproof/verify-paid HTTP/1.1
Host: pay.safegatelabs.xyz
Content-Type: application/json
PAYMENT-SIGNATURE: <x402 v2 authorization>

{ "payment": { "transaction_hash": "0x..." } }
```

| Field | Value |
|---|---|
| Scheme / network | `exact` on `eip155:8453` (Base mainnet) |
| Asset | USDC `0x833589fcd6edb6e08f4c7c32d4f71b54bda02913` |
| Amount | `50000` base units (0.05 USDC) |
| Pay to | `0x367f1b3d8ca90d1e087481a9a40d585bf3451a03` (facilitator treasury) |
| Facilitator | `https://x402-agent-pay.com/facilitator` |

Use `PAYMENT-SIGNATURE`. The legacy `X-PAYMENT` still works alone but is ignored
whenever `PAYMENT-SIGNATURE` is present.

### Step 4. Read the verdict, not the status code

A `200` means a verdict was produced. It does not mean the evidence held up.

```json
{
  "verdict": "VERIFIED",
  "ok": true,
  "charged": true,
  "payment_status": "CHARGED",
  "commerce_verified": false,
  "independently_verified": true,
  "independent_rpc_count": 2
}
```

Branch on `verdict`:

- **`VERIFIED`** — two or more independent RPC providers agreed field by field.
  You were charged. Act on it.
- **`FAILED`** — the chain contradicts the evidence. You were not charged. Do not
  retry with the same input; the answer will not change.
- **`INDETERMINATE`** — SafeGate could not establish the fact. You were not
  charged. Retrying later can help, because the usual causes are transient: only
  one provider answered, the providers disagreed, or all were unreachable. Read
  `verdict_reason` before deciding.

Then read these before you rely on anything:

- `verdict_scope` — exactly what the verdict covers. Nothing outside it is asserted.
- `not_verified` — the facts this response explicitly does **not** establish.
- `sanctions_screening` — on the `payment` input, `NOT_PERFORMED_IN_THIS_EVIDENCE_TYPE`.
- `multiple_transfers` — if true, the transaction moved USDC more than once and
  **all** transfers are in `payment.usdc_transfers`. Pick the one you meant; do
  not assume the first.

## Charging rules worth trusting

Settlement is attempted only on `VERIFIED`. `FAILED` and `INDETERMINATE` never
reach settlement, so a wrong or unprovable claim costs you nothing.

If `payment_status` comes back `UNKNOWN`, the settlement state could not be
established. SafeGate attempts **no** automatic second charge; recovery is
durable and handled on the next call. Do not fire a retry loop hoping to force a
result: you may be charged once for work already done.

A malformed `transaction_hash` is rejected **before** any RPC call is made.
Nothing is spent on a typo.

## Limits

Four quota dimensions, enforced together, lowest wins: 60 per wallet-minute, 500
per wallet-day, 500 per IP-day, 1000 global per day. Counted on
payment-authorized calls, not only on `VERIFIED` verdicts. Bodies over 1048576
bytes are rejected. Quota fails closed.

## Try before you pay

```http
POST /api/commerceproof/verify-free HTTP/1.1
Host: verify.safegatelabs.xyz
Content-Type: application/json
```

No payment header, no x402. Use it to learn the response shape before spending.

## References

- OpenAPI 3.1: https://pay.safegatelabs.xyz/openapi.json
- Plain summary: https://pay.safegatelabs.xyz/llms.txt
- Health and configuration: https://pay.safegatelabs.xyz/api/health
- Signer key registry: https://pay.safegatelabs.xyz/.well-known/safegate-keys.json

Operated by Nurexen Labs — https://safegatelabs.xyz

Last updated: 2026-11-20
