Skip to Content

Industry Vocabulary Reference

Agentic Payments & Stablecoins

Comprehensive enumeration library for the Agentic Payments & Stablecoins vertical. Covers every subdomain where agentic AI is actively deployed in payment workflows as of July 2026: AP2 mandate chain governance (Google Agent Payments Protocol v0.2), x402 HTTP-native stablecoin payments (Coinbase), stablecoin asset and issuer compliance (GENIUS Act, EU MiCA), agentic commerce provider classification, fiat instant rail governance (FedNow, RTP, SEPA Instant), and payment regulatory regime tagging. Designed for use as OTel span attributes in an agentic AI SDK and as policy vocabulary in an OPA Rego GRC portal. The AP2 mandate chain (OpenPaymentMandate → PaymentMandate → PaymentReceipt) is the primary governance model; browser-commerce agents and stablecoin treasury transfers are the highest-risk modalities requiring the most rigorous evidence capture.

v2026.07.0129 enum categories2.3 schema8 subdomains13 standards

Back to industry coverage library

This page shows selected examples and categories. Download the JSON for the complete vocabulary, including every field, permitted value, and policy pattern in this catalog.

Download vocabulary JSONOpen industry SDK quickstartStart free for 60 days 

How to use this reference

  1. Start with the core file if you need the cross-industry governance baseline.
  2. Choose an industry file for its workflow fields and permitted values.
  3. Match the OTel attributes to the policy paths your rules use, then verify the recorded fields in a test session.

Catalog context

As of July 2026, agentic AI is deployed across all major payment rails as an initiator, delegator, and governance certifier of transactions. Google AP2 (Agent Payments Protocol v0.2) provides a structured mandate chain (OpenPaymentMandate → PaymentMandate → PaymentReceipt) encoded as SD-JWT verifiable credentials, enabling AI agents to make payments within clearly defined constraints with full auditability. Mastercard has integrated AP2 across its $9T+ annual network volume to support agentic commerce. Coinbase x402 enables HTTP-native micropayments with 75M+ monthly transactions across Base, Polygon, Arbitrum, World Chain, Solana, and Ethereum, allowing AI agents to pay for API access and digital services in a single HTTP round-trip. Browser-commerce agents (OpenAI ChatGPT agent mode, Anthropic computer-use) bypass structured payment APIs and execute checkout flows autonomously, a governance gap that Veriproof fills with session-wrapping and mandate verification. The GENIUS Act (Pub. L. 119-27, signed July 18, 2025) established the first US federal framework for payment stablecoins, requiring 1:1 reserves in cash and T-bills and federal licensing for issuers above $10B AUM. EU MiCA (Regulation 2023/1114, full enforcement 2026) requires CASPs and stablecoin issuers to hold national competent authority authorization and appear in the ESMA Interim Register. FedNow and RTP carry ISO 20022 pacs.008 instruction reference requirements for all AI-initiated real-time payments. Veriproof captures evidence at each mandate step, validates constraints via OPA policy, anchors to Solana, and issues W3C VC Payment Mandate certificates, providing the governance certification layer that AP2 merchants, acquirers, and regulators require.

Vocabulary file

  • Download filename: 14_vertical_agentic_payments_and_stablecoins.json
  • Kind: vertical

OTel namespaces

agentic_payments

Referenced standards

These references explain the catalog's context. A listed standard does not establish that a configured application meets its requirements.

  • Google AP2 v0.2, Agent Payments Protocol (mandate chain SD-JWT wire format, W3C VC issuance)
  • Coinbase x402, HTTP-native stablecoin micropayment protocol (PAYMENT-REQUIRED / PAYMENT-SIGNATURE / PAYMENT-RESPONSE headers)
  • GENIUS Act (Pub. L. 119-27, signed July 18, 2025), First US federal payment stablecoin framework; §4 reserve requirements and licensing thresholds
  • EU MiCA (Regulation 2023/1114), Markets in Crypto-Assets Regulation; ART/EMT token classification; CASP authorization; full enforcement 2026
  • ISO 20022, Universal financial industry message scheme (pacs, pain, camt families for FedNow/RTP/SEPA Instant)
  • FedNow, Federal Reserve real-time payment service ISO 20022 profile; launched July 2023
  • W3C Verifiable Credentials Data Model 2.0, AP2 mandates as SD-JWT verifiable credentials; Veriproof issues Payment Mandate VDC
  • IETF SD-JWT (draft-ietf-oauth-selective-disclosure-jwt), Selective disclosure JWT wire format for AP2 mandate chain
  • PCI DSS v4.0, Payment Card Industry Data Security Standard; Requirement 10 (audit logging), Requirement 6.3 (approved software)
  • FATF Recommendations (updated 2023), AML/CFT; Recommendation 15 (new technologies / virtual assets); applies globally
  • EU AI Act (Regulation 2024/1689), Transparency and high-risk classification for AI payment systems
  • EU DORA (Regulation 2022/2554), Digital Operational Resilience Act; applies to PSPs and CASPs operating in the EU
  • BSA / FinCEN, Bank Secrecy Act SAR and transaction monitoring obligations for AI-initiated stablecoin payments

Source references

Subdomains

SubdomainCategoriesSample attributes
AP2 Mandate Chain5agentic_payments.mandate.type, agentic_payments.mandate.status, agentic_payments.mandate.modality
x402 HTTP Payment Events4agentic_payments.x402.payment_event_type, agentic_payments.x402.network, agentic_payments.x402.facilitator_id
Stablecoin Asset & Issuer4agentic_payments.stablecoin.asset, agentic_payments.stablecoin.network, agentic_payments.stablecoin.issuer_compliance_status
Agentic Commerce Providers2agentic_payments.provider.id, agentic_payments.provider.agent_presence_signal
Fiat Instant Rail2agentic_payments.rail.type, agentic_payments.rail.iso20022_message_family
Payment Regulatory Regime1agentic_payments.regulatory.regime
HTTP 402 Protocol & MPP5agentic_payments.http402.protocol, agentic_payments.http402.challenge_phase, agentic_payments.mpp.session_authorization_mode
Pay Skills Registry & Gateway6agentic_payments.registry.discovery_source, agentic_payments.registry.provider_status, agentic_payments.gateway.routing_type

Control ideas

These patterns describe possible controls, not active rules. Confirm applicability, implement the control, and test its effect on the application.

Require a purchase mandate before an agent pays

Stop a delegated payment when the session lacks its required prior open mandate record. Keep the mandate reference with the policy decision for review.

Regulatory basis: Application-defined mandate-record control, informed by AP2's delegated checkout and payment flows.

Ap2 payment mandate must include agent presence signal

Require that all closed AP2 Payment Mandates and Checkout Mandates explicitly declare an agent presence signal. not_declared is a compliance gap under AP2 v0.2 (agentPresence claim) and EU AI Act Article 50 AI transparency disclosure obligations. Without an explicit presence signal, the mandate chain cannot be audited or certified.

Regulatory basis: Google AP2 v0.2 PaymentMandate agentPresence claim; EU AI Act Article 50 AI transparency disclosure obligation; PCI DSS v4.0 Requirement 10.2 audit trail completeness

Enforce before the action

Pass the request and your business action to this function. The core SDK checks policy before the action runs and again before its result is released. A deny or review decision means the action never runs.

import { Veriproof } from '@veriproof/sdk-core';
import type { GovernedResult, IndustryFact, JsonValue } from '@veriproof/sdk-core';

const veriproof = Veriproof.fromEnv();

export async function runProtectedAction<TInput extends JsonValue, TValue>(
  request: TInput,
  action: (input: TInput, signal: AbortSignal) => Promise<TValue>,
): Promise<GovernedResult<TValue, TInput>> {
  // Catalog values for this vertical. Replace them with facts from the current workflow.
  const industry: IndustryFact[] = [
    { attribute: "agentic_payments.mandate.type", policyInput: "agentic_payments_mandate_type", value: "open_payment" },
    { attribute: "agentic_payments.mandate.status", policyInput: "agentic_payments_mandate_status", value: "pending" },
    { attribute: "agentic_payments.mandate.modality", policyInput: "agentic_payments_mandate_modality", value: "human_present" },
  ];

  // Policy runs before action() and again before the result is released.
  // A deny or review decision means action() never runs.
  return veriproof.govern(
    "agentic.payments.and.stablecoins.evaluate",
    request,
    ({ input, signal }) => action(input, signal),
    { industry },
  );
}
  • Replace the sample values with facts from the current workflow. Rules read them under input.snapshot.industry.
  • Test both permitted and blocked actions. Confirm that a blocked action never reaches your business function.
  • Only completed, completed_with_warning, and transformed results carry a released value.

For review decisions, follow the Human Review guide to configure continuation. Observe remains available when you need to record activity without enforcing a decision.

Set up the Agentic Payments & Stablecoins example. See the API reference for TypeScript, Python, or .NET.

Start your Developer evaluation

Try a simulator to see a governed decision in context. To connect your own workflow, verify your work email and start Developer free for 60 days. You can also review the relevant controls with our team.

Live demo → Start free for 60 days → Request coverage workshop → 

Selected vocabulary categories

AP2MandateType

Classification of the AP2 mandate type in the payment chain. Maps to VCT (VC Type) claim values in the AP2 SD-JWT wire format. Open mandates define spending constraints for subsequent transactions; closed mandates record a specific committed transaction; receipts confirm settlement by the payee or merchant.

Workflow area: AP2 Mandate Chain

OTel attribute
agentic_payments.mandate.type
Permitted values
  • open_payment
  • open_checkout
  • payment
  • checkout
  • payment_receipt
  • checkout_receipt

AP2MandateStatus

Lifecycle status of an AP2 mandate as tracked by Veriproof. constraint_violated is set by the OPA policy evaluation engine when the PaymentMandate violates the OpenPaymentMandate constraints (amount range or allowed payees). Once constraint_violated is set, a SessionDirective(Block) is emitted and anchoring is suppressed.

Workflow area: AP2 Mandate Chain

OTel attribute
agentic_payments.mandate.status
Permitted values
  • pending
  • active
  • completed
  • constraint_violated
  • disputed
  • expired

AP2TransactionModality

Classification of the agent-payment scenario modality. Maps to AP2 scenario paths. Critical for OPA policy routing: human_not_present and delegated_task require a prior open mandate in the session chain (policy ap2_intent_mandate_required_before_agentic_purchase); browser_agent_checkout requires an explicit intent mandate or human confirmation event (policy browser_agent_checkout_requires_intent_mandate_or_explicit_confirmation); treasury_transfer requires KYC/KYB evidence (policy stablecoin_payout_recipient_must_pass_kyc_kyb).

Workflow area: AP2 Mandate Chain

OTel attribute
agentic_payments.mandate.modality
Permitted values
  • human_present
  • human_not_present
  • delegated_task
  • subscription
  • browser_agent_checkout
  • treasury_transfer

AP2ChainDepth

Number of tilde-delimited (~~) SD-JWT disclosure sets in the AP2 wire format mandate chain, representing the count of delegation hops from the originating OpenPaymentMandate to the current step. Depth 1 = OpenPaymentMandate only. Depth 2 = Intent + PaymentMandate or CheckoutMandate (standard two-party flow). Depth 3+ = multi-agent delegation with intermediary agents. Chain depth ≥ 6 should trigger heightened governance review.

Workflow area: AP2 Mandate Chain

OTel attribute
agentic_payments.mandate.chain_depth
Permitted values
  • 1
  • 2
  • 3
  • 4
  • 5
  • 6+

AP2ReceiptReferencePresent

Boolean flag indicating whether the sha256(closed_leaf_jwt) receipt reference has been computed, stored in session.otel_attributes, and submitted to Solana for anchoring. Set to true by the Veriproof AP2 adapter after successful attest-and-close. When false on a completed mandate session, indicates an incomplete anchoring pipeline requiring investigation.

Workflow area: AP2 Mandate Chain

OTel attribute
agentic_payments.mandate.receipt_reference_present
Permitted values
  • true
  • false

X402PaymentEventType

The x402 HTTP protocol payment event type captured by Veriproof at each step of the 11-step x402 payment flow. Veriproof observes x402 headers as a side-effect observer without modifying the payment flow; each event type triggers evidence capture in the active session and OPA policy evaluation. Events map directly to the x402 HTTP header interactions.

Workflow area: x402 HTTP Payment Events

OTel attribute
agentic_payments.x402.payment_event_type
Permitted values
  • payment_required
  • payment_signature_submitted
  • facilitator_verified
  • settlement_initiated
  • settlement_confirmed
  • payment_failed
  • payment_rejected_402

X402Network

The blockchain network used for x402 on-chain stablecoin settlement. Coinbase CDP Facilitator supports Base, Polygon, Arbitrum, World Chain, Solana, and Ethereum as of May 2026. Different networks carry different transaction finality characteristics, gas cost models, and regulatory jurisdictions. Network selection is specified in the PAYMENT-REQUIRED header's paymentRequirements.network field.

Workflow area: x402 HTTP Payment Events

OTel attribute
agentic_payments.x402.network
Permitted values
  • base
  • polygon
  • arbitrum
  • world_chain
  • solana
  • ethereum

X402FacilitatorId

The x402 facilitator identifier extracted from the payment scheme in the PAYMENT-REQUIRED header. Typically the Coinbase CDP Facilitator URL (cdp.coinbase.com) or a custom facilitator URL registered by the tenant. OPA policy x402_facilitator_must_be_in_tenant_allowlist validates this value against the tenant's approved facilitator list before certifying any x402 payment session.

Workflow area: x402 HTTP Payment Events

OTel attribute
agentic_payments.x402.facilitator_id
Permitted values
  • cdp.coinbase.com

X402AttestationType

Optional governance attestation requirements specified by the seller in the x402 PAYMENT-REQUIRED header's extra field. Sellers may require buyers to present evidence of KYC identity verification, geographic authorization, or age verification as a condition of payment acceptance. Veriproof captures the attestation type to enforce OPA governance policies and verify the buyer's session contains the required evidence.

Workflow area: x402 HTTP Payment Events

OTel attribute
agentic_payments.x402.attestation_type
Permitted values
  • none
  • kyc_verified
  • geographic_restriction
  • age_verified

StablecoinAsset

The stablecoin asset used in an agentic payment transaction. Issuers and regulatory compliance status differ significantly across assets; governance policies are applied per-asset. GENIUS Act and MiCA compliance obligations depend on the issuer, the asset type, and the regulatory regime tags applied to the session.

Workflow area: Stablecoin Asset & Issuer

OTel attribute
agentic_payments.stablecoin.asset
Permitted values
  • usdc
  • usdb
  • usdp
  • usdg
  • eurc
  • pyusd
  • usdt

StablecoinNetwork

The blockchain network on which the stablecoin payment is settled. Network determines transaction finality time, gas cost, and the applicable regulatory jurisdiction for on-chain record-keeping. Veriproof captures the network to ensure evidence packs correctly reference the on-chain transaction location and allow regulators to independently verify settlement.

Workflow area: Stablecoin Asset & Issuer

OTel attribute
agentic_payments.stablecoin.network
First 8 permitted values
  • ethereum
  • base
  • solana
  • polygon
  • arbitrum
  • optimism
  • avalanche_c_chain
  • stellar

StablecoinIssuerComplianceStatus

The regulatory licensing and registration status of the stablecoin issuer at the time the payment session is created. Veriproof evaluates this status against the applicable payment regulatory regime tags (genius_act, eu_mica) to enforce OPA compliance policies. genius_act_stablecoin_issuer_must_be_licensed_or_registered fires when the regime includes genius_act and the status is not genius_act_federally_licensed or genius_act_state_licensed. mica_casp_must_have_eu_authorization fires when the regime includes eu_mica and the status is not mica_art_registered or mica_emt_registered.

Workflow area: Stablecoin Asset & Issuer

OTel attribute
agentic_payments.stablecoin.issuer_compliance_status
Permitted values
  • genius_act_federally_licensed
  • genius_act_state_licensed
  • mica_art_registered
  • mica_emt_registered
  • pending_registration
  • unregulated

This page uses the vocabulary JSON distributed with the documentation. Check its version when comparing it with an installed SDK.

Download the vocabulary JSON for offline review or automated comparisons.

Use the SDK reference for configuration and supported APIs. Keep vocabulary selection separate from the compliance team's assessment of applicable requirements.

Last updated on