Product features

Full-stack payment control, without custody

One governed surface for every collection, approval, refund, and agent-initiated transaction.

Transaction control centerLive monitoring
Volume monitored

$2.84M

Processed today

1,284

Approval rate

99.8%

Median decision

1.7s

24h+18.4%
Policy engine active 3 networks connected

Live transaction stream

UTC 03:33:20
GS-8842Base · USDC
12,480.00ClearedCleared
GS-8841Ethereum · USDT
4,260.50ScreeningReviewing
GS-8840Solana · USDC
8,940.00ClearedCleared
GS-8839Base · USDC
2,175.25ClearedCleared
Non-custodial
We never hold funds or touch private keys. Settlement stays on your rails.
Compliance by default
OFAC SDN screening, Travel Rule collection, and core policies that cannot be switched off.
Maker-Checker
Sensitive operations require a second approver, recorded end to end.
Full-chain reconciliation
Append-only double-entry ledger reconciles provider, chain, and book records.

Capabilities

Seven modules, one governed workflow

Operable by finance, scriptable by engineering.

OperationsFor operators

Daily overview & work queue

A single console for what settled, what broke, and what needs a human right now.

  • KPI dashboard: settlement volume, success rate, trend by period
  • Provider health at a glance, with degradation signals
  • Queue depth and backlog aging across processing stages
RevenueFor operators

Collections & customer management

Three ways to get paid, one customer record behind them.

  • Payment Link for ad-hoc and one-off collection
  • Invoice with due dates and structured line items
  • Pricing Page for productised, repeatable offers
ComplianceFor compliance officers

Compliance & secure approvals

Screening and dual control applied before value moves, not after.

  • OFAC SDN screening with automatic hold on match
  • Manual release or rejection with recorded reviewer rationale
  • Maker-Checker dual approval on sensitive operations
GovernanceFor finance leads

Post-sale & financial reconciliation

Refunds, disputes, and books that always tie back.

  • Full and partial refunds with policy-checked limits
  • Dispute handling: contest with evidence, or accept
  • Append-only double-entry ledger — no silent edits
AutomationFor developers

Advanced capabilities & customisation

Agent payments, white-label surfaces, and automated remediation.

  • Agent-Pay: x402 protocol, hosted sessions, metered per-use charging
  • Brand customisation: colours, logo, dark mode, company details
  • Automated tasks: overpayment refunds, expired-quote refunds, webhook retries
MeteringFor developers

Metering & rating

Every call counted once, priced at the list that was live that day.

  • Idempotency keys so a retried request is never double-charged
  • Fails open: if metering is unavailable your calls keep serving
  • Per-metric rating — tokens, requests, GPU minutes, seats
BalancesFor operators

Balances & replenishment

Pete watches the balance and asks for a top-up before service stops.

  • Two warning thresholds — percentage and runway in hours; first one wins
  • Top-up request drafted, branded as you, and chased on a schedule
  • Service pauses with a 402 at zero and resumes the moment funds land

Technical assurance

Built to be verified, not trusted blindly

Limited by design in what it can do with your funds.

Read-only by design
Chain and provider data is observed, never unilaterally moved.
No private keys
GoSeven never stores, generates, or transmits your private keys.
Sepolia testnet
Rehearse the full lifecycle in sandbox before touching mainnet.
Complete audit log
Every action, actor, and approval is retained and exportable.

How usage reaches us

Two ways in, same ledger

Send usage from your code, or let the gateway count it.

Your codePete SDKMetered ledger

SDK ingest

You call us after you serve the request.

  • A few lines in your handler — customer, metric, quantity
  • Idempotency key per event, so retries collapse into one
  • Batched and async: no added latency on your hot path
Your customerPete gatewayMetered ledger

Gateway proxy

Traffic passes through us and is counted on the way.

  • Point your customers at a Pete endpoint; no handler changes
  • Requests, tokens and duration metered automatically
  • Balance enforced at the edge — exhausted keys get a 402

Events you can build on

Seven webhooks, signed and replayable

Everything Pete does emits a signed, replayable event.

  1. usage.ingested

    Event accepted

  2. usage.rated

    Priced

  3. balance.low

    Threshold crossed

  4. balance.exhausted

    Service paused

  5. replenishment.settled

    Top-up settled

  6. invoice.issued

    Invoice published

  7. payment.reconciled

    Matched to usage

Questions

The things teams ask first

Pete is in limited release

A 30-minute call, then a sandbox running synthetic traffic through the whole loop, then one real customer. We take on a small number of teams at a time.

All rights reserved.