SAFEGATE
Back to SafeGate

Controlled Testnet Pilot Hub

One trust layer. Multiple payment rails. Verifiable outcomes.

SafeGate does not process payments. It verifies what happened after payment, prevents conflicting transaction reuse, creates receipt and evidence, and unlocks wallet-bound delivery.

chain-agnostic Payment-rail neutral Real-device EVM pilot PASS Base Mainnet verified
Base Mainnet USDC

Verified commerce outcome

SafeGate verifies what happened after a real Base Mainnet USDC payment: intended-request binding, durable replay-safe consumption, merchant fulfillment, evidence and portable proof.

  1. Review the live public commerce verifier.
  2. Inspect the deterministic commerce outcome contract.
  3. Confirm deployment proof bound to the reviewed public commit.
Open Live Commerce Verifier View Deployment Proof
AI Agent Commerce

Commerce Outcome API

An AI agent can prove that payment moved. SafeGate lets the agent verify whether the intended commerce actually completed through a read-only, deterministic post-payment verification API.

  1. Did payment happen?
  2. Was it bound to the intended request?
  3. Was fulfillment completed and evidence created?
Open Commerce Outcome API View Public Verifier Source
Legacy / Test Paths

Earlier controlled engineering demos

Pi Testnet and Base Sepolia are retained as earlier SafeGate engineering paths. They document the progression toward the current Base Mainnet commerce-verification model.

  1. Review the earlier Pi Testnet payment path.
  2. Review the earlier Base Sepolia EVM verification path.
  3. No new payment or wallet action is required for historical review.
View Pi Testnet Path View Base Sepolia Path

Reviewer route

  1. Read the SafeGate boundary: verification and delivery, not payment custody.
  2. Start with the verified Base Mainnet commerce outcome and live Commerce Outcome API.
  3. Complete the controlled flow in the required wallet browser.
  4. Inspect the verified outcome, receipt, evidence and delivery state.