Tempo MPP Agent Mandate

Parse an MPP (Money Payment Protocol) session object, validate the spend cap and session terms, map the HTTP-402 flow to AP2 Intent→Cart→Payment, perform KYA agent identity check via did:key, model settlement cost, and emit a signed agent-payment mandate. The did:key identity of the agent signer is the marquee OCG v0.3 feature. Tempo: payments-first L1 incubated by Stripe + Paradigm, mainnet live March 2026. MPP spec: github.com/tempoxyz/mpp-specs. Client-side. Zero PII.

AP2 Export Chains: ART-01, ART-02, ART-04 did:key Identity MPP Session Tempo Stablecoin payment_mandate iso20022:pacs.008-subset

🔒 All inputs are processed locally in your browser. No data is transmitted. Do not enter real personal data — use synthetic or anonymised inputs only.

Agent identity

Agent DID (did:key format) Must be did:key method (z6Mk... prefix). Self-describing, registry-free agent identity. OCG v0.3 feature.

MPP session parameters

Merchant / API endpoint Merchant URL or metered API endpoint — CartMandate.merchant_id in AP2 mapping

Spend cap (USD) IntentMandate.ceiling_amount in AP2 mapping

Session duration

Payment rail

Stablecoin Applies when Tempo stablecoin rail is selected

Voucher cadence MPP off-chain signed voucher streaming frequency

Session summary

AP2 mandate mapping — MPP → AP2

KYA risk assessment

ISO 20022 pacs.008 settlement leg

Agent mandate

Next-chain links

→ ART-01 AP2 Mandate Validator → ART-02 Spend Policy Simulator → ART-04 KYA Identity Checker

Export the artifact then carry it into ART-01 to apply AP2 policy mandates, ART-02 for spend limit validation, or ART-04 for full KYA attestation.