MandateShield AI Payment Evidence

com.mandateshield/payment-authority

Analyzes delegated AI payment authority and exposes supported Stripe/x402 evidence contracts.

Yes, your AI can use this right now.Answered a live MCP handshake in 1200 ms with no sign-in needed and exposes 3 tools.

Connect it

Settings → Connectors → Add custom connector
URL: https://mandateshield.com/api/mcp

3 tools, verified live

Pulled straight from the server with tools/list on 2026-10-17.
check_ai_payment_authority

Use before an AI agent buys, subscribes, transfers value, calls a metered API, or accesses a paid resource when the user wants a payment-authority check. Analyze whether the proposed purchase fits supplied policy facts. This v1 entry check is non-executable and always returns enforcement_authorized=false; use the strict cryptographic tool for a production gate. Never send payment credentials or pr

normalize_agent_payment_protocolread-only

Use when an agent encounters an AP2 terminal closed-payment projection, x402 v2 PAYMENT-REQUIRED offer, or explicitly profiled MPP Payment challenge and needs the supported fields projected before an authority check. Map those documented fields into a deterministic MandateShield purchase envelope. X402 requires source-matched network+payTo identity and MPP requires source-matched HTTPS service-ori

verify_cryptographic_payment_authority

Use only for a production pre-payment authority gate after the caller has a registered mandate, pinned issuer key, fresh challenge, VERIFY-scoped key, exact final purchase and supported signed evidence. Fail closed for JWS, an AP2-shaped closed-payment SD-JWT projection with RFC 9901 KB-JWT, or normalized TAP-shaped RFC 9421-style evidence. Full AP2 checkout/delegate-chain and Visa TAP structured-

Alternatives in Finance & Payments

Compare →
Try “Notion”, “Stripe”, “create invoice”, “browser”