PAYMNTS — Assurance for the Agent Economy

CAPABILITIES

Trust, engineered in layers

Six independent systems, one verdict — so no single failure lets an agent run wild.

deterministic

Mandate verification

Every transaction must cite a live, signed mandate: amount cap, merchant scope, expiry. Violations hard-decline in strict mode — not "warned", declined.

5-factor fusion

Real-time risk scoring

Mandate compliance, sanctions proximity, behavioral anomaly, merchant risk, and velocity exposure — fused into one score with evidence attached.

OFAC·UN·EU·FATF

Sanctions shield

Counterparties screened by name, alias, and graph proximity before approval.

per-agent memory

Behavioral baselines

Each agent builds a normal-behavior profile over time — anomalies surface as scored deviations, not guesses.

compliance

SAR autopilot

Suspicious Activity Reports generated from real evidence: facts, scores, graph paths, audit trail.

audit-ready

Provenance graph

Every decision carries its evidence chain — who mandated, what scored, why it cleared. Auditors query the trail directly.

agents + teams

Agent-first API

Agents verify mandates and check risk natively in their own flow; your team reviews escalations in the console.

strict mode

Hard-decline policy

Compliance overrides beat weighted scores — sanctions hits always stop the money.

always-on

Live health

Every check, verdict, and override streamed live — you see system health before your customers feel it.

HOW IT WORKS

Three beats. Zero blind spots.

Agent registers → human signs

Agent gets a graph identity bound to an owner. The owner signs a mandate: amount cap, merchant scope, expiry — cryptographically bound, tenant-isolated.

Agent attempts a transaction

Via ACP, Agent Pay, VIC, or AP2, the event normalizes into our pipeline — mandate check, sanctions screen, behavioral analysis, velocity check.

Verdict + permanent record

Approve, escalate, or decline — with scored evidence and a 7-year audit trail. Regulators get provenance, not a shrug.

WHO IT'S FOR

Every rail agents will spend on

Wherever an AI agent can initiate a payment, there's a compliance question someone will ask. These are the teams who'll hear it first.

Payment orchestration

PSP routers and checkout platforms score agent traffic before choosing a rail — clean agents take the fast path, risky ones get stepped up.

Orchestrators · gateways · checkout platforms

Card issuing & wallets

Agent-provisioned cards bound to a mandate — spend cap, merchant scope, and expiry enforced per-authorization, not just per program.

Card issuers · agent wallets · spend platforms

Banks & treasury

Agent-initiated sweeps, transfers, and reconciliation — every movement scoped to a signed mandate with an audit trail regulators can read.

Bank innovation teams · treasury · corporate banking

Custody & digital assets

Agents driving wallet operations get screened beyond policy scope — counterparty graph proximity catches what allowlists can't.

MPC custodians · exchanges · institutional wallets

Marketplaces & commerce

Agent buyers purchasing on behalf of users — mandate-verified orders with evidence that settles "who authorized this" disputes instantly.

Marketplaces · e-commerce · procurement agents

Fraud & identity platforms

Risk engines built for human telemetry get the missing agent signals — mandate compliance, behavioral deviation, counterparty context — as a feed.

Fraud vendors · identity platforms · risk consortia

CONNECT

Three ways in — pick your weapon

Same scoped, rate-limited assurance engine behind every door: REST for services, MCP for agents, OpenAPI for typed SDKs.

🔌 REST API

Drop it in any service

# score a transaction before it settles
curl -X POST "https://YOUR-HOST/api/v1/pymnts/risk/score?tenant_id=tenant_acme&project_id=project_payments" \
  -H "x-api-key: YOUR_KEY" \
  -H "content-type: application/json" \
  -d '{
    "tx_id": "tx_9f2", "agent_id": "checkout-bot",
    "amount": "129.99", "currency": "USD",
    "merchant_id": "acme-store", "protocol": "acp"
  }'

Scoped by tenant + project. Every response carries X-RateLimit-* headers for your tier.

🤖 MCP server

Native tools for agents

// claude_desktop_config.json / any MCP client
{
  "mcpServers": {
    "paymnts": {
      "url": "https://YOUR-HOST:8121/mcp",
      "headers": { "x-api-key": "YOUR_KEY" }
    }
  }
}

verify_mandate · score_risk · check_sanctions · log_transaction · query_agent_history · check_merchant

📦 SDK

Typed clients, generated

# generate a typed SDK from the live spec
pip install openapi-python-client
openapi-python-client generate \
  --url https://YOUR-HOST/openapi.json

The spec is the contract — always in sync with the deployed routes, never hand-drifted.

PRICING

Tiered for your traffic

Rate limits scale with your tier — every tier gets the full assurance engine, the difference is throughput and retention.

STARTER

Pilot

Core mandate verification + risk scoring
Sanctions screening (OFAC-format)
Community support

GROWTH

Production

Everything in Pilot, plus behavioral baselines
Protocol adapters (ACP · Agent Pay · VIC · AP2)
SAR generation + compliance exports

ENTERPRISE

Regulated

Everything in Production, plus custom limits
Dedicated infra + air-gap deployment
Audit-grade retention + SLA

Your agents want to
spend money.
We watch them do it.