Product

AgentPay

PayAccept turns agent payments into controlled, auditable commerce. Bind every payment to intent, policy, service delivery and settlement evidence, starting with x402 and designed for emerging agent-payment protocols.

Private beta — currently onboarding design partners.

Apply for private beta View walkthrough

Why PayAccept exists

Payment protocols prove settlement.
Businesses require authorization.
Finance requires evidence.

PayAccept connects those worlds.

Lifecycle

Authorize → Bind → Prove → Reconcile

Evidence and policy engines power AgentPay underneath — they are not separate peer products.

Authorize

Evaluate delegated payment authority against policy before a payment is accepted.

Bind

Attach the payment to a specific request, agent, and service so settlement cannot drift.

Prove

Record verification, delivery, and receipt evidence alongside the payment path.

Reconcile

Reconstruct what was requested, authorized, paid, and delivered for finance and ops.

Simulated walkthrough

See a controlled payment path end to end

This is a website simulation for evaluation — not a live sandbox and not connected to production payments.

Interactive product walkthrough

Available on website

Simulated walkthrough for illustration. Not connected to a live payment sandbox.

Stage 1 of 8

Request

The request is bound to a fictional request identifier before any payment is accepted.

request_id: req_demo_01HZY8Y5K6
service: market-data.snapshot
agent: research-agent
amount: 2.50 USDC

Interactive product walkthrough

Simulated walkthrough for illustration. Not connected to a live payment sandbox.

1. Request
An agent requests a protected service.
2. 402 challenge
The service returns the payment terms.
3. Authorization policy
A policy evaluates delegated payment authority.
4. Payment verification
The payment is verified and bound to the request.
5. Service delivery
The merchant returns the requested service result.
6. Signed receipt
A signed receipt captures the payment and delivery evidence.
7. Webhook events
The lifecycle emits distinct, replayable event names.
8. Reconciliation record
Finance and operations receive a complete lifecycle record.

Sample lifecycle payload

{
  "request_id": "req_demo_01HZY8Y5K6",
  "policy_id": "pol_demo_01HZY8ZD5Q",
  "payment_id": "pay_demo_01HZY91Q2M",
  "events": [
    "payment.verified",
    "service.delivered",
    "receipt.created"
  ]
}

Architecture

Control plane beside the settlement path

Policy, binding, and evidence sit alongside protocol settlement — with clear data boundaries between chain, PayAccept, and merchant systems.

Expand diagram

Transaction path

Agent / Client

PayAccept Policy Gateway

Protocol Adapter(x402)RoadmapAP2 / ACP

Facilitator / Payment Processor

Merchant Service

Parallel evidence plane

Policy decisions, verification results, and delivery events are captured alongside the payment path.

Evidence, Receipt & Reconciliation Store

On-chain

Settlement reference and network transaction data.

PayAccept

Policy decisions, request binding, receipts, events, and reconciliation records.

Merchant

Service payloads and business data, unless explicitly supplied as evidence.

Longer-term control-plane research is documented separately as SEEF. AgentPay does not claim to ship that full design in private beta.

Who it is for

Built for paid machine-to-machine services

Best suited to API providers, AI platforms and MCP operators preparing paid machine-to-machine services.

API providers

Charge for machine-readable endpoints with request-bound receipts.

AI platforms

Give agents spend authority that finance and security can review.

MCP operators

Meter tool calls and agent-to-agent services with policy controls.

FAQ

Common questions

No. PAYT is an optional ecosystem asset and is not required to use PayAccept or participate in the private beta.

PayAccept is designed around non-custodial payment flows. Your payment processor or facilitator handles settlement according to its own terms and configuration.

PayAccept starts with x402. AP2 and ACP are roadmap integrations and are not currently available.

No. The interactive walkthrough is a simulated website experience and is not connected to a live payment sandbox.

Apply for private beta access and tell us about your API, AI platform, or MCP service. We are onboarding selected design partners.

Apply for private beta Explore developers