OOneLink PayPitch
Universal Accounts TrackArbitrum · Road to Open House LondonMagic Labs

Give a research agent a card.
Not your wallet.

Give a deterministic research workflow 2 USDC for paid tools. It buys two market feeds, produces an ETH risk brief, and an unexpected premium request is stopped by the signed 0.10 USDC per-tool limit.

Underneath that legible story, OneLink Pay is the safety layer for the payments your apps and agents make: Particle handles chain-abstracted value movement while an on-chain mandate enforces limits and public receipts make settlement verifiable.

Agents can pay now. Nothing stops them overspending.

Software agents can already pay for anything over HTTP (x402). But a buggy or hijacked workflow can drain the wallet — and consumers feel it. The rails are here; the trust isn’t.

The trust gap we close

The agent economy isn’t short of rails — it’s short of trust. Independent research, not our numbers:

~3 in 4 are uncomfortable letting an AI pay autonomously — even with limits set in advance.

Forrester · external research · 2026-06

Only 13.9% would trust an AI agent to complete a purchase on their behalf.

Ecommpay / The Paypers · external research · 2026-06

~2 in 3 will try agentic shopping — but demand human approval before the buy.

Commerce + PayPal · external research · 2026-06

Distrust is rising, not falling: a majority (55%) are now uncomfortable letting AI agents make purchases — a reversal from the comfortable majority a year earlier.

Riskified · external research · 2026-04

Everyone is building rails. The blocker is trust. That is the layer we are.

One mandate. Enforced on-chain. Can’t overspend.

  1. Sign one mandate

    An EIP-712 PaymentMandate — per-charge, daily and total caps, expiry, one merchant, revocable. Read in plain English, not a blind hash.

  2. SpendPolicy enforces it on-chain

    A contract checks every charge. Over-cap, off-merchant, or post-revoke charges revert at zero gas — there is no server you have to trust.

  3. Every payment leaves a proof

    A public receipt links the settlement and the on-chain InvoicePaid attestation — re-checkable by anyone, no account.

Built on Particle Universal Accounts in EIP-7702 mode + Magic walletless login: one balance across chains, cross-chain settlement with no manual bridge, and zero-gas onboarding (the one-time delegation is relayer-sponsored) — bounding x402 agent payments, non-custodial on your own EOA.

The 90 seconds a judge sees

  1. 1

    Walletless, gasless login

    Google or email via Magic — no seed phrase, no extension, no gas — into a Particle Universal Account in EIP-7702 mode; the first-time delegation is relayer-sponsored.

  2. 2

    Read the card, not a hash

    A plain-English mandate: $0.10 / charge, $2 / day, one merchant, expires today, revocable. The EIP-712 hash sits behind a disclosure.

  3. 3

    Run one useful research task

    The deterministic workflow buys a 0.05 USDC market snapshot and a 0.08 USDC sentiment feed through the x402 pattern.

  4. 4

    Brief ready; overreach blocked

    The useful ETH brief appears first. Then an unnecessary 0.20 USDC premium export exceeds the cap and is refused before settlement.

  5. 5

    Cross-chain, no manual bridge

    A merchant is paid on Arbitrum with USDC sourced from Base in one operation — the user never bridges or picks a chain.

  6. 6

    Proof, then revoke

    Open the public proof receipt — anyone re-checks it on a block explorer. One click revokes the mandate.

How OneLink is different

Other tools move money between people. OneLink makes the payments your apps and agents send safe — non-custodial, on-chain enforcement on your own account, with a publicly verifiable proof.

PlayerWhere OneLink differs
Visa Intelligent Commerce + OpenAISame pre-authorization idea, but on-chain and non-custodial, on your own account.
Coinbase Agentic WalletsWallet-agnostic — the limit lives on your own EIP-7702 account, chain-abstracted.
AWS Bedrock AgentCore PaymentsNon-custodial and on your own on-chain account — the limit is a public contract anyone can re-check, with a proof receipt per payment.
MetaMask Smart Accounts · ERC-7715 session keysWe don't reinvent the primitive — we package it as a legible, revocable payments mandate with a public proof receipt, on your own EIP-7702 account.
Circle / CatenaNon-custodial — you hold the keys; we enforce, we don't custody.
Google AP2Same intent, enforced on-chain at your account — a promise becomes a guarantee.
x402 (Coinbase)We bound x402 spend with the mandate (live).
Consumer crypto wallets (send-money apps)Not another wallet: we make app & agent payments safe — an on-chain limit they can't exceed + a proof anyone can verify.
Other rails (cards · bank · PSP)directionalThe same mandate is designed to front them too — one on-chain guardrail across rails.

“Built” rows are live today and map to our honest-claim ledger. The “directional” row is a design direction, not a shipped integration.

Proven, not promised

Live today

  • Permission Firewall — SpendPolicy enforces per-charge / daily / total caps + expiry + single-merchant + revoke, live on Base + Arbitrum. Over-cap reverts at zero gas. 22 contract tests pass.
  • Cross-chain settlement via Particle Universal Account (EIP-7702) — merchant paid on Arbitrum, USDC sourced from Base, one operation, no manual bridge. Proven live on-chain.
  • Research agent expense card — two paid inputs produce a useful brief through the x402 pattern; the unexpected premium export is bounded by the mandate and refused before settlement.
  • Public proof receipts — ReceiptEmitter anchors an InvoicePaid attestation after server-side verification of the on-chain USDC transfer; re-verifiable by anyone.
  • Zero-gas onboarding — the one-time per-chain EIP-7702 delegation is submitted by our relayer (relayer pays); a first-time payer needs no native gas. Proven live on Arbitrum (the delegation tx is sent by the relayer, not the payer).
  • Self-custody — the limit lives on your own EOA (same address), not a custodial or MPC wallet; export your key via Magic's own reveal (OneLink never sees it) or revert the delegation anytime.

What we don’t claim

  • x402 is the pattern (our onelink-mandate scheme), not the Coinbase facilitator.
  • The agent is an unattended deterministic loop — not an LLM. No AI reasoning is claimed.
  • No general gas paymaster — only the one-time 7702 delegation is sponsored (relayer-paid); the settlement fee is paid in USDC.
  • Prod runs the pinned stable Particle SDK (2.0.3) — real 7702 + cross-chain, live-verified.

Every public claim maps to an on-chain proof — the full ledger is at /trust.

Integrate in one call

No contracts to deploy, no SDK. Send users to a hosted link, or bound an agent’s x402 spend with a signed mandate — two paths a builder ships today.

Hosted pay link

One POST from your backend, then redirect the customer. Cross-chain USDC, settled on your chain.

POST /api/payment-links
  x-admin-create-token: $TOKEN
  { merchantAddress, amount, token,
    destinationChainId }
→ { checkoutUrl: ".../pay/<id>" }

Agent on x402

GET → 402 → pay within the signed mandate → retry with proof → 200. The firewall caps every call on-chain.

GET  /api/x402/<resource>   → 402 + terms
POST /api/mandates/charge   → { txHash }
     (reverts on-chain if over-cap)
GET  /api/x402/<resource>
     X-PAYMENT: <proof>     → 200 + data

Who it’s for: AI-agent frameworks that need a hard spend ceiling, usage/subscription billing that wants a revocable capped mandate, and API providers pricing per call over x402. Full guide: docs/integrate.md.

See it for yourself

Everything here runs live — no slideware. The buttons run on our funded demo account; the replay and receipt need no wallet at all.

OOneLink Pay

Particle Universal Accounts + EIP-7702 · Magic walletless login · Arbitrum settlement.