MandateShield Payment Authority Agent

Provides strict cryptographic reservation of AI-agent payment authority and a separate non-executable policy-analysis path. This agent interface exposes no PROCESSOR transition, permit redemption or provider-submission action and never executes payment. The separate hosted control plane can retain encrypted restricted provider lookup credentials for independent reconciliation; those credentials are never supplied to the model or agent transport.

Skills

• Project Agent Payment Fields
  Map documented AP2 terminal closed-payment fields, x402 v2 PAYMENT-REQUIRED fields, or an explicitly profiled MPP Payment charge challenge into a deterministic purchase envelope. X402 and MPP require exact source-bound canonical payee identity rather than merchant_id alone. Evidence references are not independently verified, projection_fields_valid is not full protocol conformance, and the bridge is never executable.
  AP2x402 v2MPPpayment protocol adapterpurchase envelope
• Verify Cryptographic Payment Authority
  Fail-closed production verification 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 and Visa TAP chain/trust-store processing remains external. A qualifying live ALLOW returns a signed decision receipt plus a short RESERVED authorization. It never executes payment and exposes no PROCESSOR transition, redemption or reporting action. Every account created at or after 2026-07-26T12:01:24.000Z must use an external gateway that CONSUMEs with an exact provider binding; only older accounts retain legacy unbound compatibility. Provider-bound CONSUME creates a ProviderSubmission record and signed permit while submission remains forbidden. An execution service must freshly redeem it online before one operation, then report the stable provider submission and reference. The caller report or webhook is only a hint; configured Stripe API or canonical x402 chain verification must independently confirm a terminal outcome before autonomous COMMIT or RELEASE. Offline verification never grants, and provider adoption is not claimed.
  cryptographic authorizationsigned mandateSD-JWTRFC 9421AP2TAPdecision receiptaccount-pinned keyone-time challengecumulative budget reservationprocessor handoffprovider-bound execution permitatomic online redemptionprovider reconciliationindependent provider evidencesigned execution receipt
• Analyze AI Payment Policy
  Analyze a normalized purchase envelope against supplied policy facts. Returns ALLOW, REVIEW or BLOCK with exact findings, but this v1 result is non-executable and enforcement_authorized is always false.
  agentic commerceAI paymentspayment authorizationAP2UCPTAPx402ACP

How to call

https://mandateshield.com/a2a

Listed in

Directories this entry was found in.