CCelo PayGrid

Documentation

Security model

This document describes current controls and limitations. It does not claim banking compliance, SOC 2, ISO certification, insurance or regulatory approval.

Current controls

Treasury Safe

Protocol fees are configured to route to the Celo Mainnet Safe 0xc0C019DCeCE7a3a235Ab520F394A57c132F90cD6.

Remote MCP write auth

Read-only MCP tools are public. Write tools require Authorization: Bearer <PAYGRID_MCP_API_KEY>.

ERC-8004 signed backend requests

The MCP signs protected backend requests with an agent key. The backend verifies the signed request before treating it as agent-authenticated.

paygrid:erc8004:<agentId>:<address>:<METHOD>:<path>:<timestamp>:<nonce>

Rate limits and CORS

Backend routes apply rate limiting. Production backend CORS allows configured frontend origins only.

Onchain settlement

Payment status is anchored by Celo Mainnet contract events and indexed into Supabase.

Trust boundaries

BoundaryCurrent protection
Public users to backendvalidation, CORS, rate limits
External agents to MCP write toolsAPI key
MCP to backendERC-8004 signed headers
Backend to contractsbackend wallet
Funds settlementCelo Mainnet contracts
Payment statusonchain event indexing

Current limitations

  • No per-agent scoped API keys yet.
  • No per-agent daily spend limits yet.
  • No token allowlists or merchant allowlists yet.
  • No autonomous swap execution.
  • No advanced human approval policies.
  • No enterprise reconciliation controls.

Planned hardening

  1. Per-agent API keys.
  2. Key hashing and rotation.
  3. Scopes for MCP write tools.
  4. Rate limits per external agent.
  5. Daily request and spend limits.
  6. Token allowlists.
  7. Human confirmation thresholds for higher-risk actions.
  8. Audit logs for agent write operations.