ChatGPT Wallet: Give Your Agent a Purchasing Policy

Abstract tech illustration: ChatGPT Wallet: Give Your Agent a Purchasing Policy

▶ Watch the video version of this article

A purchasing agent can find the right item and still finish the wrong job. It might ship to an old address, accept a late delivery date, or leave accounting without a receipt. Before giving an agent a card, give it a narrower assignment: what it may prepare, what you must approve, and what evidence proves the order is complete.

What ChatGPT Wallet can do—and where it stops

ChatGPT Wallet lets eligible users approve purchases made through dots, OpenAI’s agents in ChatGPT. It is a payment capability for a specific workflow, not a general promise that an agent can complete your business’s purchasing, project tracking, and accounting handoffs.

OpenAI announced ChatGPT Wallet on November 13, 2026. According to its Wallet help documentation, access is rolling out gradually to eligible ChatGPT Pro users in the United States. Users must be at least 18, live in the United States, have a US billing address, and use an eligible US-issued card. Meeting those conditions does not mean the feature has appeared in your account yet.

The distinction between dots and other ChatGPT workflows matters. OpenAI says Wallet works in dot conversations, not in Chat, Work, or standalone Codex threads. Don’t design a business process around the assumption that a card added for Wallet will work wherever your team uses ChatGPT. The initial rollout also does not establish availability for ChatGPT Business or Enterprise.

The purchase flow has an important human boundary: before a Wallet purchase, the user reviews the details and approves with a security check such as Face ID or a fingerprint scan. After approval, Wallet uses a substitute payment credential linked to the selected card; the agent and merchant do not receive the actual card details. That protects card information, but it does not decide whether the item, supplier, delivery date, or client allocation is correct.

OpenAI’s documentation also distinguishes approval from order confirmation. If the result is unclear, approval alone is not proof that the merchant placed the order. For a small business, “I approved the payment” and “the supplies are ordered” must remain separate states until you have merchant confirmation.

Turn a repeat order into a purchasing brief

A useful purchasing brief defines one repeatable job tightly enough that the agent can prepare it and a person can spot a wrong proposal before paying. Start with an approved item and supplier, then specify the total-cost ceiling, destination, deadline, changes that require a stop, and the records needed afterward.

Here’s exactly how I’d frame an agency’s repeat print order. The project manager needs another run of approved event flyers. The request arrives in Gmail, but the project record holds the event deadline and client name. A message saying “sort out the printing” is not enough instruction for an agent that can reach checkout.

This is an illustrative business policy, not an OpenAI setting or a claim that Wallet enforces these fields:

task: Prepare a reorder; do not approve payment
project: Client event flyer
item:
  artwork: Use the approved file from the project record
  quantity: 500 copies
supplier: Existing approved print supplier
delivery:
  address: Saved office address from the project record
  required_by: Event delivery deadline in the project record
budget:
  maximum_total_usd: 150
  includes: [item, tax, fees, shipping]
stop_if:
  - Artwork, quantity, supplier, or address differs
  - Delivery cannot meet the required date
  - Final total exceeds the maximum
  - Checkout includes a recurring charge, deposit, or hold
  - Any required detail is missing or contradictory
approval:
  show_before_payment:
    - Final item and artwork
    - Quantity and supplier
    - Delivery address and date
    - Total or maximum price and any recurring terms
completion:
  - Save merchant order confirmation and receipt if provided
  - Record the order against the correct project
  - Notify the project manager with the order status

This YAML is an illustrative policy draft. Check which rule options are available in your account, and don’t assume Wallet automatically enforces every field listed here. OpenAI says dot users can set custom rules for certain actions involving what a dot may share, purchase, or access, but warns that dots can make mistakes even when following rules. Treat a written rule as guidance to test, not as a substitute for reviewing the checkout details.

Notice that the brief says prepare a reorder, not “buy whatever is needed.” The $150 figure is an example chosen for this fictional job, not a default spending limit. It includes tax, fees, and shipping because a base price alone cannot tell you whether the order fits the budget. OpenAI’s Wallet terms tell users to review the total or maximum price, including known taxes, fees, and shipping, and to check for recurring charges, deposits, and authorization holds.

For your first brief, choose something less ambiguous than a new supplier search: a repeat purchase with an approved specification and a known destination. If the request requires interpreting design feedback, negotiating substitutions, or resolving conflicting deadlines, keep that decision with a person.

Put approval at the point where the facts can still change

The approval boundary should sit immediately before payment, after the agent has assembled the actual checkout details. Approving a general instruction at the start of a task is not the same as reviewing the final cart, shipping choice, and amount you are about to authorize.

A purchasing workflow can change between the initial request and checkout. The usual paper stock may be unavailable. The supplier may offer a replacement that looks similar but does not match the approved flyer. A cheaper shipping option may arrive after the event. A last-minute email may change the delivery address. Each is a reason to stop and show the difference, not improvise.

For the print order, I’d ask for a short approval summary:

Check before payment What the approver needs to see
Item The approved artwork and print specification
Quantity The count in the final cart
Supplier The merchant receiving the order
Delivery Address, shipping method, and expected arrival
Cost Total or maximum price, including known extras
Payment terms Any recurring charge, deposit, or authorization hold
Project The client job that should receive the expense

This is a proposed review checklist, not a description of fields Wallet currently guarantees to display. If a detail is absent from the agent’s summary, inspect the merchant checkout before approving.

Pay particular attention to recurring terms. OpenAI’s help documentation notes that a merchant may charge again under an agreed recurring-payment plan. A one-time reorder brief should not quietly become permission for an ongoing service. Likewise, a changed delivery date is not a minor formatting difference when the materials are for an event.

Keep payment credentials out of the conversation. OpenAI’s Wallet terms direct users to enter card numbers, security codes, and verification codes in Wallet’s secure forms, not in ChatGPT messages. If you plan to use a business card, the same terms say your organization must permit you to store it with OpenAI for purchases. Wallet does not support adding debit or virtual cards at launch, according to OpenAI’s help documentation.

The useful rule is simple: the agent can gather facts and propose an order; the authorized person checks the final facts and approves the payment. Don’t describe that as unattended purchasing. OpenAI’s current documentation describes user review and approval for purchases.

Make “done” mean more than an approved charge

A purchase is complete for business operations only when its outcome is verified and its records are where the next person expects them. Wallet can participate in payment, but an accounting-ready order also needs merchant confirmation, an appropriate receipt, a project reference, and a clear status for the team.

Consider the sequence for the flyer order:

  1. Request captured: The project manager’s request is associated with the right client job.
  2. Proposal checked: The item, supplier, delivery details, and total match the purchasing brief.
  3. Payment approved: An authorized person reviews the final purchase details in Wallet.
  4. Order verified: The merchant confirms whether it accepted the order.
  5. Records filed: The confirmation and receipt, when available, are saved against the project.
  6. Team notified: The project manager receives the confirmed status and any unresolved issue.

Do not collapse steps three and four. OpenAI explicitly advises checking for merchant confirmation when the result of a purchase is unclear. If approval succeeds but confirmation is missing, report “approval completed; merchant order unconfirmed.” Do not report “ordered,” and do not immediately submit the cart again. First check the merchant account and confirmation messages so an uncertain result does not become a duplicate order.

The same precision helps when a later step fails. If the merchant confirms the order but the receipt cannot be saved to the client folder, the agent should say so. That is a filing failure, not a purchasing failure. Someone can then repair the record without placing another order.

This matters because the source of truth is spread across tools. Gmail may hold the request, a project tool the deadline, the merchant the order, and accounting the expense. A wallet does not by itself reconcile those systems. Define which record is authoritative for each field, and have the workflow surface conflicts instead of selecting whichever value it encountered last.

Plan the exception path as well. OpenAI’s Wallet terms direct users to the merchant for order problems, cancellations, returns, and refunds, and to the card issuer for card charges, billing errors, and unauthorized transactions. Your internal order record should retain enough information for a person to identify the merchant, project, and disputed transaction without searching through an agent conversation.

Test the policy without spending money

Run the workflow as a dry run before attaching a card or approving a live purchase. The test is whether it stops on a material mismatch, presents the right facts for approval, and reports incomplete handoffs accurately—not whether it can produce a convincing shopping summary.

Give it the approved flyer request and ask it to prepare the order without paying. Then change one condition at a time:

Dry-run input Expected behavior
Quote exceeds the example $150 total cap Stop; show the full total and request a new decision
Approved paper or artwork is unavailable Stop; describe the proposed substitution
Delivery arrives after the event deadline Stop; show the date conflict
Checkout contains a recurring charge Stop; identify the term before approval
Address in an email differs from the project record Stop; ask which address is authorized
Payment appears approved but no merchant confirmation is found Report the order as unconfirmed; do not retry blindly
Merchant confirms the order but receipt filing fails Report the order as confirmed and the filing step as incomplete

This is an acceptance test for your workflow. It does not assert that Wallet provides a native test mode, a vendor whitelist, or automatic budget enforcement. Confirm which controls are actually available in your account before relying on them.

The address-conflict test is especially valuable. An agent may encounter a legitimate last-minute change, an outdated message, or an instruction embedded in content it was only meant to read. A purchasing policy should name who can authorize a change and where that authorization must appear. “Use the latest address you find” is a poor rule when shipping mistakes cost money and time.

Keep the first live task narrow and supervised. Watch what the dot proposes, review the actual checkout, and verify the merchant’s result afterward. If the process only works when you silently correct the agent at every step, the brief or the surrounding workflow is not ready to run routinely.

Where bizflowai.io fits

I build practical AI automations for small teams. A workflow around payment should turn a request into a checkable proposal, use the project record, and clearly report incomplete steps. Wallet may handle an approved purchase inside an eligible dot conversation; the business still needs to define and verify what happens before and after it. That is the workflow to get working before treating a card as the solution.


Want more like this?

I’m Lazar Milićević, a senior engineer who builds AI automations for solopreneurs and small teams.

The purchasing brief and dry-run checks above are a starting point: adapt them to your own approval process and verify the controls available in your account before using a card.

Visit bizflowai.io.

Frequently asked questions

What is ChatGPT Wallet?

ChatGPT Wallet is a reported payment capability for OpenAI’s Dots agents platform, intended to let agents make purchases for users. The Verge reported its launch on November 13. The supplied report excerpt does not establish which merchants it supports or whether it provides spending controls, refund handling, or business accounting integrations.

Who can use ChatGPT Wallet at launch?

The reported rollout starts with ChatGPT Pro subscribers in the United States who are at least 18, have a US billing address, and use an eligible US-issued American Express, Chase, Mastercard, or Visa card. This describes the announced starting audience; it does not mean ChatGPT Wallet is available worldwide.

How do I prepare a business purchasing task for an AI agent?

Write a narrow purchasing brief for one repeat order. Specify the approved item and supplier, quantity, maximum total including tax and delivery, shipping address, and deadline. State which changes require human approval and what details you want to review before payment. Define completion too: save the confirmation and receipt, record the order against the project, and notify the responsible person.

Why does payment capability alone not complete a business purchasing task?

Payment is only one step. In the agency example, the request is in Gmail, the deadline is in a project tool, and accounting needs a receipt tied to the correct client job. A completed task also requires the right item and delivery details, plus a record of what happened. The supplied report does not establish that ChatGPT Wallet connects those systems.

How do I test an AI purchasing workflow before attaching a card?

Run the workflow without live payment against a written purchasing brief. Try an over-budget quote, an unavailable item, and a changed delivery date. Check whether it stops and asks for approval rather than improvising. Also check that it reports any incomplete step. Verify the product’s actual controls before attaching a card; these tests are proposed safeguards, not documented ChatGPT Wallet features.