PAYMNTS sits between AI agents and payment rails — verifying mandates, scoring risk, screening sanctions, and writing the audit trail for every agent-initiated transaction. Before the money moves, not after the incident.

Six independent systems, one verdict — so no single failure lets an agent run wild.
Every transaction must cite a live, signed mandate: amount cap, merchant scope, expiry. Violations hard-decline in strict mode — not "warned", declined.
Mandate compliance, sanctions proximity, behavioral anomaly, merchant risk, and velocity exposure — including cross-agent collusion patterns — fused into one score with evidence attached.
Counterparties screened by name, alias, and graph proximity before approval.
Each agent builds a normal-behavior profile over time — anomalies surface as scored deviations, not guesses.
Suspicious Activity Reports generated from real evidence: facts, scores, graph paths, audit trail.
Every decision carries its evidence chain — who mandated, what scored, why it cleared. Auditors query the trail directly.
Agents verify mandates and check risk natively in their own flow; your team reviews escalations in the console.
Compliance overrides beat weighted scores — sanctions hits always stop the money.
Every check, verdict, and override streamed live — you see system health before your customers feel it.
Merchant, trusted-agent, and issuer public keys governed in one registry — registered, rotated, and revoked under human-admin control with full audit. Unknown trust material escalates; it never silently verifies.
Every scored transaction exports a signed evidence bundle — mandate, authorization, risk verdict, screening, provenance, and the hash-chained audit trail — verifiable offline and rendered as a document issuers review.
Agent gets a graph identity bound to an owner. The owner signs a mandate: amount cap, merchant scope, expiry — Ed25519-signed, tenant-isolated.
Via ACP, Agent Pay, VIC, or AP2, the event normalizes into our pipeline — mandate check, sanctions screen, behavioral analysis, velocity check.
Approve, escalate, or decline — with scored evidence and a 7-year audit trail. Regulators get provenance, not a shrug.
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.
PSP routers and checkout platforms score agent traffic before choosing a rail — clean agents take the fast path, risky ones get stepped up.
Agent-provisioned cards bound to a mandate — spend cap, merchant scope, and expiry enforced per-authorization, not just per program.
Agent-initiated sweeps, transfers, and reconciliation — every movement scoped to a signed mandate with an audit trail regulators can read.
Agents driving wallet operations get screened beyond policy scope — counterparty graph proximity catches what allowlists can't.
Agent buyers purchasing on behalf of users — mandate-verified orders with evidence that settles "who authorized this" disputes instantly.
Risk engines built for human telemetry get the missing agent signals — mandate compliance, behavioral deviation, counterparty context — as a feed.
The sandbox runs the full assurance engine on instant rails: request an account, mint an API key, and get a real approve / escalate / decline decision in under a minute.
Request sandbox access (or register directly on self-serve deployments), then click the verification link we email you — verified email is required for keys.
Badge in, open API Keys in the console, and mint a starter key — the secret is shown once, stored only as a hash, revocable instantly.
Call /risk/fast-check with your key — a real decision with
evidence, typically under 200 ms. Declines never touch the rail; then
watch it in the console's audit feed.
Same scoped, rate-limited assurance engine behind every door: REST for services, MCP for agents, OpenAPI for typed SDKs. Request a sandbox account, verify your email, mint an API key in the console, and score a payment in under a minute.
# decide before the rail sees it — fast-check
curl -X POST "https://paymnts.ai/api/v1/pymnts/risk/fast-check?tenant_id=YOUR_TENANT&project_id=YOUR_PROJECT" \
-H "x-api-key: YOUR_KEY" \
-H "content-type: application/json" \
-d '{
"tx_id": "tx_9f2", "agent_id": "checkout-bot",
"mandate_id": "mnd_1",
"amount": "129.99", "currency": "USD",
"merchant_category": "retail", "protocol": "fednow"
}'
Scoped by tenant + project. Every response carries
X-RateLimit-* headers for your tier.
// 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
# 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.
We never hold funds, never see your customers' payment credentials, and never participate in the rail ourselves — the sponsor bank executes our verdicts (release, hold, accept, reject); funds move only between your accounts there, never through a Paymnts account. Everything else is engineered to survive their audit.
API keys are stored as SHA-256 hashes, TTL-enforced, and revoked instantly — the full secret exists only at mint time.
Every decision, key issuance, override, and settlement lands in a SHA-256 hash-chained governance ledger, enforced at the database — tampering is detectable, not just prevented.
Webhook deliveries verified by HMAC-SHA256 signature and made idempotent — retries never double-settle or double-decide.
Every query is tenant + project scoped — cross-tenant access returns 403, never silently falls back.
If scoring or screening fails, the payment declines or escalates — there is no silent-approve path.
Secure headers on every response, per-key rate tiers, login lockout, TOTP MFA for console sign-in, and hash-only session tokens.
Every mandate is cryptographically bound to its owner — forged or replayed scopes decline at verification, not at the incident.
High-value rail releases require a second admin's approval — a risk-approved transaction still can't clear on one signature alone.
A SOC 2 Security-TSC evidence bundle (CC6.1–CC8.1) generated from live data — the artifact your TPRM review or Type II auditor maps directly.
Agent rotation, shared-owner bursts, and merchant fan-in are scored as signals — one clean agent can't launder a ring's volume.
Every deployable ships a deterministic SBOM and dependency audit, anchored into the same governance ledger as your decisions.
RFC 9116 security.txt and a safe-harbor
disclosure page — report privately via
/ui/security.
Rate limits scale with your tier — every tier gets the full assurance engine, the difference is throughput and retention.
Badge in and put every transaction under the radar sweep.
Badge in →