OpenAI ChatGPT Wallet: secure payments for AI agents
OpenAI launches ChatGPT Wallet with Visa, Mastercard, and Amex to enable autonomous AI agent payments using delegated cryptographic tokens and FIDO2.

The launch of OpenAI ChatGPT Wallet for payments executed by AI agents resolves one of the most persistent security bottlenecks in autonomous commerce: enabling an algorithmic assistant to settle a real-world financial transaction without exposing plaintext banking credentials or surrendering the cardholder's cryptographic control. Engineered in technical partnership with Visa, Mastercard, and American Express, the infrastructure replaces legacy Primary Account Number (PAN) storage with scoped, delegated payment tokens signed inside local biometric hardware enclaves under the FIDO2 and WebAuthn standards.
Until now, granting purchasing authority to an autonomous agent presented an unacceptable security trade-off for retail and corporate banking institutions. Whenever a user supplied card details or session cookies within the model's context window, any indirect prompt injection encountered while scraping an external merchant catalog could hijack funds or trigger unauthorized charges. Under the ChatGPT Wallet architecture, the neural model never views or manipulates financial secrets; it operates strictly as an orchestrator requesting a single-use payment cryptogram governed by deterministic mathematical constraints.
Cryptographic delegation architecture and EMV network tokenization
At the core of ChatGPT Wallet lies a convergence of EMV payment network tokenization specifications and public-key cryptographic assertions. When a user instructs an AI agent to book a corporate flight or procure server hardware under specific price thresholds, the client application invokes the host device's native WebAuthn API to request a biometric signature inside its dedicated hardware security module (Secure Enclave on iOS/macOS or TPM-backed Keystore on Android and Windows).
This hardware operation generates a Scoped Payment Mandate signed with an ECDSA P-256 private key that never leaves the physical silicon of the user's endpoint. The signed mandate is transmitted to the tokenized vault operated by Visa, Mastercard, or American Express, which issues a restricted delegated payment token. Security engineers auditing financial gateways can inspect the structure of these signed assertions using a JWT decoder to verify spending ceiling claims (max_amount), currency bindings (currency), target merchant identifiers (merchant_id), and strict validity windows (exp).
An artificial intelligence agent must never hold implicit financial authority; every autonomous transaction must be anchored by a deterministic cryptographic mandate whose validity is enforced by the banking network outside the model's cognitive reach.
Integrating the latest FIDO CTAP 2.2 biometric authentication specification enables this delegation signature to incorporate cryptographic Transaction Confirmation Extensions. Consequently, the device's trusted hardware display presents the exact spending limit being authorized before the biometric sensor releases the private key signature, eliminating any discrepancy between what the conversational UI displays and what is cryptographically signed at the silicon layer.
Comparing legacy web checkout with ChatGPT Wallet agent delegation
To understand how this architecture neutralizes transactional fraud and identity spoofing across automated workflows, security architects should contrast the three digital payment paradigms currently operating in the industry.
| Security attribute | Browser saved card / Autofill | Standard digital wallet (Apple/Google Pay) | ChatGPT Wallet (AI agent delegation) |
|---|---|---|---|
| Raw PAN card exposure | High (actual card digits often sent to merchant) | Zero (uses static device-bound DPAN token) | Zero (uses ephemeral mandate-specific token) |
| Spending limit binding | None (merchant can submit arbitrary charge amounts) | Bound to exact cart total at the instant of click | Capped by cryptographic ceiling, merchant, and TTL |
| Prompt injection resilience | Vulnerable if an agent parses malicious DOM forms | Not applicable to asynchronous agent execution | High (card network rejects charges outside mandate) |
| Identity verification | Static CVV code and SMS/App 3D-Secure challenge | Instant local biometrics at checkout moment | FIDO2/WebAuthn hardware signature with pre-delegation |
| Cryptographic revocation | Requires canceling and reissuing physical plastic card | Deleting the device token inside the wallet app | Instant revocation by mandate ID without card impact |
This design directly counters the threat vectors exposed following the recent disclosure of an authentication vulnerability in AI agents, where adversaries hijacked delegated sessions lacking cryptographic token binding to the transport layer. Within ChatGPT Wallet, every payment cryptogram requires Demonstrating Proof-of-Possession (DPoP) bound directly to the mutually authenticated TLS certificate of the authorized execution node.
Technical structure of a WebAuthn-signed payment mandate
Once the autonomous agent locates the requested product or service within the cardholder's specified parameters and initiates checkout, it transmits the delegated token alongside the cryptographic proof of the original mandate to the merchant's payment gateway. The payment processor validates the signature chain against the public key registered with the issuing card network before settling funds.
Below is an illustration of a signed transactional mandate payload operating under the ChatGPT Wallet delegation protocol:
{
"mandate_header": {
"alg": "ES256",
"typ": "application/agent-payment-mandate+jwt",
"kid": "fido2-hw-enclave-99481a0c-3b2e"
},
"mandate_claims": {
"iss": "urn:openai:wallet:delegator:user-7829104",
"sub": "urn:openai:agent:procurement-runner-v4",
"aud": "https://network.tokenized-payments.visa.com/v2/authorize",
"iat": 1795111200,
"exp": 1795114800,
"transaction_constraints": {
"max_amount_minor_units": 45000,
"currency": "EUR",
"allowed_mcc": ["3000", "4511", "5732"],
"merchant_domain_hash": "sha256-8f9d2c4b1e0a7f6c5d4e3b2a1908f7e6d5c4b3a2",
"single_use_cryptogram": true
},
"fido2_assertion": {
"authenticator_data": "SZYN5YgOjGh0NBcPZHZgW4_krrmihjLHmVzzuoMdl2NBAAAACQ",
"user_verified_biometric": true,
"hardware_backed_key": true
}
}
}
If a merchant gateway attempted to process a charge for 450.01 EUR (45001 minor units), or if the Merchant Category Code (allowed_mcc) failed to match airlines or technology equipment providers, the card network's authorization engine deterministically declines the transaction in under twelve milliseconds, completely independent of the AI model's reasoning layer.
Security recommendations for deploying autonomous enterprise procurement
Enterprises planning to enable automated purchasing via corporate AI agents should enforce supplemental governance and financial auditing controls:
- Tiered budget policies and multi-signature approval: configure strict policy thresholds where minor operational purchases execute via single-user mandates, whereas high-value procurement requires concurrent FIDO2 hardware signatures from two authorized financial officers.
- Isolation of API integration credentials: ensure secret keys connecting corporate ERP platforms with tokenization gateways are generated using a maximum-entropy password generator and stored inside HSM appliances compliant with the cloud governance and encryption directive.
- Merchant allowlisting via TLS certificate pinning: restrict agent purchasing mandates exclusively to merchant domains verified by their SHA-256 cryptographic certificate fingerprint, blocking payments across cloned storefronts or dynamically generated phishing portals.
- Immutable auditing of agent decision traces: record the user's initial prompt, the merchant's signed offer response, and the resulting EMV cryptogram hash inside an append-only ledger, streamlining forensic reconciliation during chargeback disputes.
The foundation of machine-to-machine transactional commerce
The unveiling of ChatGPT Wallet alongside Visa, Mastercard, and American Express establishes the cryptographic bedrock for agentic commerce. By strictly decoupling the probabilistic reasoning layer of large language models from the deterministic authorization layer of global banking rails, the payment industry ensures autonomous purchasing aligns with the most rigorous fraud prevention and international regulatory compliance frameworks.
For e-commerce platform engineers and banking security architects, the architectural shift is profound. Payment gateways will no longer interact solely with human-operated web browsers in real time; they must now validate autonomous agents presenting hardware-signed cryptographic mandates, where the cardholder's FIDO2 biometric signature remains the irreplaceable root of trust for every financial movement.


