Enable in-context shopping on AI agentsPrivate preview
Learn how to let your businesses sell their products on AI chat agents.
Private preview
If you’re interested in using agentic commerce to sell your businesses’ products through AI agents, including Instant Checkout in ChatGPT, or to manage transactions between buyers and businesses, join the waitlist.
Choosing your charge type
In the in-context shopping flow, Stripe creates an agentic checkout session for your platform. To create the session, Stripe needs to know which charge type you want to use. Stripe supports direct charges and destination charges with the on_ parameter.
In both charge types, the connected account acts as the seller.
Contact Stripe with the charge type you want, and Stripe updates that setting for your account.
Upload your product catalog data to Stripe
Prepare your product catalog
For each connected account, create a CSV file that conforms to the Stripe product catalog specification.
Upload the catalog data to Stripe
Upload catalog data for each connected account separately through the Stripe APIs. You can send updates every 15 minutes.
Use the sandbox to validate parsing, field mappings, and data quality before enabling live updates.
First, upload a connected account’s product catalog CSV using the Files API. A successful request returns a File object, which includes the id.
- Specify
data_asmanagement_ manual_ upload purpose. - Make sure the MIME type matches the file format. Acceptable formats include CSV and TSV, where each row represents one product or variant.
- The maximum file size is 200 MB.
curl https://files.stripe.com/v1/files \ -u: \ -H "Stripe-Account: {{CONNECTED_ACCOUNT_ID}}" \ -F purpose=data_management_manual_upload \ -F file="@/path/to/your/file.csv;type=text/csv"sk_test_BQokikJOvBiI2HlWgH4olfQ2
Then, use the Data Management API to create an ImportSet. This call starts catalog processing and makes the data available in the Dashboard. Include the following:
- The file
idreturned. - The preview header (for example,
Stripe-Version: 2025-09-30.).clover;udap_ beta=v1
curl https://api.stripe.com/v1/data_management/import_sets \ -H "Stripe-Version: 2025-09-30.clover;udap_beta=v1" \ -H "Stripe-Account: {{CONNECTED_ACCOUNT_ID}}" \ -u: \ -d file={{FILE_ID}} \ --data-urlencode standard_data_format="product_catalog_feed"sk_test_BQokikJOvBiI2HlWgH4olfQ2
Monitor feed status
Stripe validates and cleans the catalog data, indexes it, and converts it to a format for AI agents. Monitor indexing progress using the status field on the import set. The status can be pending, failed, succeeded, succeeded_, pending_, or archived.
curl https://api.stripe.com/v1/data_management/import_sets/{{IMPORT_SET_ID}} \ -u: \ -H "Stripe-Version: 2025-09-30.clover;udap_beta=v1" \ -H "Stripe-Account: {{CONNECTED_ACCOUNT_ID}}"sk_test_BQokikJOvBiI2HlWgH4olfQ2
The response includes the status and any errors:
{ "id": "impset_7MabcdZ8b617780e5145413", "object": "data_management.import_set", "created": 1643992696, "livemode": true, "result": { "errors": { "file": "file_234923sIENc", "row_count": 30 }, "rows_processed": 120, "successes": { "row_count": 90 } }, "status": "succeeded_with_errors" }
If your import status is succeeded_, you can download the error report:
- Find the
result.field in the response.errors. file - Use the Files API to retrieve the error file by its ID.
- The downloaded CSV contains your original data with a leading column named
stripe_that describes why each row failed.error_ message
curl https://files.stripe.com/v1/files/{{ERROR_FILE_ID}}/contents \ -u:sk_test_BQokikJOvBiI2HlWgH4olfQ2
The API returns a CSV file containing only the rows that failed, with a stripe_ column describing each error.
Configure taxes for your connected accounts
Use Stripe Tax for fully managed tax calculations, or implement a tax hook in your integration if you need custom tax logic or must integrate a third‑party tax provider.
Monitize transactions
By default, when you create an agentic checkout session, no application fee is applied.
Common mistake
You must add an application fee when your platform pays Stripe fees for a connected account. Without an application fee, you can lose money on each transaction.
Enable agents for your connected accounts
Stripe offers an embedded component to help onboard connected accounts to agentic commerce. When you’re ready for your connected accounts to sell on an AI chat agent, they must review the agent terms and enable the agent using this embedded component. Stripe sends the agent an approval request that the agent must accept. The component lets connected accounts manage which AI agents can sell their products, customize how their business appears across agent platforms, and pause or stop selling on an AI chat agent.
Private preview
We’re actively developing this embedded component. The code snippets are for illustrative purposes only and are subject to change.
The following code example shows how your platform can integrate with this embedded component. For details on how to embed dashboard functionality into your website, see Get started with Connect embedded components.
// server.js const stripe = require("stripe")(, { apiVersion: ${STRIPE_API_VERSION}} ); // POST /account_session_token const accountSession = await stripe.accountSessions.create({ account: '{{CONNECTED_ACCOUNT_ID}}', components: { agentic_commerce_settings: { enabled: true, }, }, }, { apiVersion: `${STRIPE_API_VERSION}; embedded_connect_beta=v2`, }); response.json({ accountSessionToken: accountSession.client_secret });'sk_test_BQokikJOvBiI2HlWgH4olfQ2'
// App.jsx import { ConnectAgenticCommerceSettings, ConnectComponentsProvider, } from "@stripe/react-connect-js"; import { loadConnectAndInitialize } from "@stripe/connect-js"; const AgenticCommerce = () => { const [stripeConnectInstance] = React.useState(() => { const fetchClientSecret = async () => { const response = await fetch('/account_session', { method: "POST" }); if (!response.ok) { const {error} = await response.json(); console.log('An error occurred: ', error); return undefined; } else { const {client_secret: clientSecret} = await response.json(); return clientSecret; } }; return loadConnectAndInitialize({ publishableKey: "pk_123", fetchClientSecret: fetchClientSecret, }) }); return ( <div> <ConnectComponentsProvider connectInstance={stripeConnectInstance}> <ConnectAgenticCommerceSettings /> </ConnectComponentsProvider> </div> ) }
Respond to purchases and fulfill orders
Listen to Stripe webhooks to monitor orders made on AI chat agents.
When an order is confirmed, Stripe emits webhook events that your server can handle to run fulfillment logic. Set up an endpoint on your server to accept, process, and acknowledge these events. See the webhooks guide for step-by-step instructions on integrating with and testing Stripe webhooks.
Stripe emits checkout. and payment_. If your fulfillment logic already handles these events, you don’t need additional integration changes. You can customize your fulfillment logic for in-context agentic selling (for example, by noting in your order confirmation email that the checkout occurred through an agent).
For details on setting up webhooks for connected accounts, see Connect webhooks.
const stripe = require('stripe')(process.env.STRIPE_SECRET_KEY); // Use the secret provided by Stripe CLI for local testing // or your webhook endpoint's secret const endpointSecret = 'whsec_...'; app.post('/webhook', (request, response) => { const sig = request.headers['stripe-signature']; let event; try { event = stripe.webhooks.constructEvent(request.body, sig, endpointSecret); } catch (err) { response.status(400).send(`Webhook Error: ${err.message}`); return; } if (event.type === 'checkout.session.completed') { const session = event.data.object; // For V1 webhooks event.account is the connected account const session = await stripe.checkout.sessions.retrieve( session.id, { expand: ["line_items.data.price.product", "line_items.data.price"], }, // If using direct charges, the checkout session is created on the connected account and the `stripeAccount` parameter must be passed. If using destination charges the checkout session is created on the platform account and `stripeAccount` parameter can be ignored. { stripeAccount: "{{CONNECTED_ACCOUNT_ID}}", }, ); // SKU id is available at session.line_items.data[number].price.external_reference fulfillCheckout(event.account, session); } response.status(200).send(); });
After you receive the webhook, retrieve all required fields with a single API call. To avoid multiple requests, expand sub-resources using the expand request parameter with the preview header Stripe-Version: 2025-12-15..
curl https://api.stripe.com/v1/checkout/sessions/{{SESSION_ID}}?expand[]=line_items.data.price.product&expand[]=line_items.data.taxes&expand[]=payment_intent.latest_charge \ -u: \ -H "Stripe-Version: 2025-12-15.preview" \ -H "Stripe-Account: {{CONNECTED_ACCOUNT_ID}}"sk_test_BQokikJOvBiI2HlWgH4olfQ2
See fields in the expanded Checkout Session, such as amount_, quantity, and SKU ID.
Checkout session field reference
| Order field | Available resource | API path |
|---|---|---|
| Order date | CheckoutSession. | CheckoutSessions. |
| Order quantity | CheckoutSessions | CheckoutSession. |
| SKU | CheckoutSessions | CheckoutSession. |
| Product description | CheckoutSessions | CheckoutSession. |
| Unit price | CheckoutSessions | CheckoutSession. |
| Tax amount | CheckoutSessions | CheckoutSession. |
| Tax type | CheckoutSessions | CheckoutSession. |
| Tax rate | CheckoutSessions | CheckoutSession. |
| ShippingAddress | CheckoutSessions | CheckoutSessions. |
| BillingAddress | CheckoutSessions. | CheckoutSessions. |
| Last4 | CheckoutSessions. | CheckoutSessions. |
| ExpMonth | CheckoutSessions. | CheckoutSessions. |
| ExpYear | CheckoutSessions. | CheckoutSessions. |
| CreditCardType | CheckoutSessions. | CheckoutSessions. |
| Final amount | CheckoutSessions | CheckoutSessions. |
| GTIN Private preview | CheckoutSessions | CheckoutSession. |
| MPN Private preview | CheckoutSessions | CheckoutSession. |
| Agent details Private preview | CheckoutSession. | CheckoutSessions. |
| OrderNo | CheckoutSession. | CheckoutSessions. |
Test your integration
You can test your integration directly from the Dashboard in a sandbox:
- Open the Trigger Agentic Purchase blueprint in Workbench
- Enter the connected account’s ID and a SKU ID
- Click Run to simulate a charge from an agent
OptionalManual capture
By default, Stripe captures payments immediately when a purchase completes. Contact Stripe to enable manual capture. After it’s enabled, call the capture method on the PaymentIntent returned in the webhook described in the previous section.
OptionalSet up an order approval hook
Before we confirm a payment, we check inventory based on your product catalog data and run fraud checks with Radar by default. To control whether we complete a purchase, configure an order approval hook. Before we complete checkout, we send an approval request to your service. You must approve or decline the request.
Stripe enforces a four-second timeout for your hook. If your hook doesn’t respond within this time, Stripe declines the payment.
To set up an order approval hook:
- Specify the endpoint on the Agentic Commerce settings page in the Dashboard.
- Enable Order approvals.
- Implement your logic at the endpoint and use the request and response formats below.
Request format
Stripe sends the following request to your endpoint:
{ type: "v1.delegated_checkout.finalize_checkout", id: string, livemode: boolean, // account ID context?: string, // request specific data data: { amount_subtotal?: number, amount_total?: number, billing_details?: { name?: string, address?: { line1?: string, line2?: string, city?: string, state?: string, postal_code?: string, country?: string } }, currency: string, email?: string, line_items_details: Array<{ id: string, unit_amount: number, quantity: number, name: string }>, payment_method_details?: { type: "card" | ..., card?: { brand: "amex" | "visa" | "master_card" | ..., country?: string, exp_month: number, exp_year: number, fingerprint?: string, funding: "credit" | "debit" | "prepaid" | "unknown", iin?: string, last4: string, wallet?: { type: "apple_pay" | "google_pay" | ... } } }, phone?: string, shipping_details?: { name?: string, address?: { line1?: string, line2?: string, city?: string, state?: string, postal_code?: string, country?: string }, }, total_details?: { amount_discount?: number, amount_shipping?: number, amount_tax?: number } } }
Response format
Your endpoint must return 200 HTTP responses with the following format:
{ manual_approval_details: { type: "approved" | "declined", declined?: { reason: string } } }
OptionalSet up a checkout customization hook
By default, Stripe calculates taxes and shipping options for your products based on the options defined in your product catalog.
To calculate taxes or shipping options and costs dynamically with your logic:
- Specify the endpoint on the Agentic Commerce settings page in the Dashboard.
- Enable Custom tax rates or Custom shipping options.
- Implement your logic at the endpoint and use the request and response formats below.
Request format
Stripe sends the following request to your endpoint:
{ type: "v1.delegated_checkout.customize_checkout", id: string, livemode: boolean, // Connected account ID context?: string, // Request specific data data: { // Used by the seller to determine whether they can set manual tax rates on line items automatic_tax: { enabled: boolean, }, currency: string, line_item_details?: Array<{ id: string, sku_id: string, unit_amount: number, amount_discount: number, amount_subtotal: number, amount_tax: number, amount_total: number, quantity: number, name: string, tax_rates: Array<{ rate: { id: string, display_name: string, percentage: number, inclusive: boolean, } // Amount of tax applied for this rate. amount: number }> }>, shipping_details?: { // Same as the shipping rate object described at https://docs.stripe.com/api/shipping_rates/object#shipping_rate_object shipping_rate?: { id: string, display_name?: string, metadata?: Map<string,string>, tax_code?: string , tax_behavior: 'unspecified' | 'included' | 'excluded', fixed_amount: { amount: number, currency: 'usd' | 'cad' | etc., currency_options.<currency>: { amount: number, tax_behavior: 'unspecified' | 'included' | 'excluded', } }, delivery_estimate?: { maximum: { unit: 'business_day' | 'day' | 'hour' | 'month' | 'year', value: number }, minimum: { unit: 'business_day' | 'day' | 'hour' | 'month' | 'year', value: number } } }, // Same as the shipping rate object described at https://docs.stripe.com/api/shipping_rates/object#shipping_rate_object shipping_rates?: Array<{ id: string, display_name?: string, metadata?: Map<string,string>, tax_code?: string, tax_behavior: 'unspecified' | 'included' | 'excluded', fixed_amount: { amount: number, currency: 'usd' | 'cad' | etc., currency_options.<currency>: { amount: number, tax_behavior: 'unspecified' | 'included' | 'excluded', } }, delivery_estimate?: { maximum: { unit: 'business_day' | 'day' | 'hour' | 'month' | 'year', value: number }, minimum: { unit: 'business_day' | 'day' | 'hour' | 'month' | 'year', value: number } } }, address?: { line1?: string, line2?: string, city?: string, state?: string, postal_code?: string, country?: string } }, amount_total?: number, amount_subtotal?: number, total_details?: { amount_discount?: number, amount_shipping?: number, amount_tax?: number } } }
Response format
Your endpoint must return a 200 HTTP response with the following format:
{ shipping_options?: Array<{ // ID of the shipping rate, or data provided to create the shipping rate. Only provide one; not both shipping_rate?: string, shipping_rate_data: { display_name?: string, fixed_amount: { amount: number, currency: 'usd' | 'cad' | etc., }, metadata?: Map<string,string>, tax_code?: string , tax_behavior?: 'unspecified' | 'included' | 'excluded', // Same as the shipping rate object described at https://docs.stripe.com/api/shipping_rates/create#create_shipping_rate-delivery_estimate delivery_estimate?: { maximum: { unit: 'business_day' | 'day' | 'hour' | 'month' | 'year', value: number }, minimum: { unit: 'business_day' | 'day' | 'hour' | 'month' | 'year', value: number } } }, }>, line_items?: Array<{ // Corresponding ID of the line item to update id: string, // List of tax rates to apply to this line item // Provide either `rate` or `rate_data` tax_rates: Array<{ // ID of a v1 tax rate rate?: string, // Or `rate_data`. // This will use an existing tax rate that matches the params or will create one if a matching rate does not exist rate_data?: { display_name: string, inclusive: boolean, // percentage out of 100 percentage: number, } }, }> }
OptionalTest your hooks
You can test your order approval or checkout customization hook by providing a publicly accessible endpoint that can accept hook requests with a POST method. Set up your endpoint function so that it:
- Handles
POSTrequests with a JSON payload - Returns a successful status code (
200)
For local development, use a tunneling tool such as ngrok to expose your local endpoint.
Example endpoint
This code snippet is an endpoint function configured to receive v1. requests and return a 200 responses.
require 'json' # Replace this endpoint secret with your unique endpoint secret key endpoint_secret = 'whsec_...'; # Using Sinatra post '/hooks' do payload = request.body.read # Check that you have configured webhook signing if endpoint_secret # Retrieve the event by verifying the signature using the raw body and the endpoint secret signature = request.env['HTTP_STRIPE_SIGNATURE']; begin Stripe::Webhook::Signature.verify_header( payload, signature, endpoint_secret ) rescue Stripe::SignatureVerificationError => e puts "Webhook signature verification failed. #{e.message}" status 400 end end # Handle the event payload = JSON.parse(payload) case payload["type"] when 'v1.delegated_checkout.finalize_checkout' # Check inventory and accept payment data = { manual_approval_details: { type: "approved" } } end status 200 body data.to_json end
OptionalHandle the agreement with agents
Private preview
This API is in private preview. Examples below are subject to change.
When a connected account onboards to an agent, Stripe creates an Agreement object between the seller and the agent. Stripe emits webhook events to the platform and the agent whenever the Agreement object’s status changes:
v2.: An Agreement was created between the seller and the agent.orchestrated_ commerce. agreement. created v2.: The seller has confirmed the Agreement.orchestrated_ commerce. agreement. partially_ confirmed v2.: The agent has confirmed the Agreement.orchestrated_ commerce. agreement. confirmed v2.: Either the seller or agent terminated the Agreement.orchestrated_ commerce. agreement. terminated
Listen for these events on your webhook endpoint to keep your platform’s state in sync (for example, updating UI, enabling or disabling agent access, or notifying sellers).
Fetch an Agreement
Retrieve an Agreement object using the Agreements API:
curl https://api.stripe.com/v2/orchestrated_commerce/agreements/{{AGREEMENT_ID}} \ -H "Authorization: Bearer {{API_KEY}}" \ -H "Stripe-Version: 2025-12-19-17.internal" \ -H "Stripe-Account: {{CONNECTED_ACCOUNT_ID}}"
OptionalSend incremental inventory updates
In addition to uploading your product catalog, you can send individual product inventory updates using the Inventory Feed API. Use the same upload process as catalog uploads, but set standard_ to inventory_:
# Step 1: Upload your CSV using the Files API curl https://files.stripe.com/v1/files \ -u: \ -H "Stripe-Account: {{CONNECTED_ACCOUNT_ID}}" \ -F purpose=data_management_manual_upload \ -F file="@/path/to/your/file.csv;type=text/csv" # Step 2: Create an ImportSet object curl https://api.stripe.com/v1/data_management/import_sets \ -H "Stripe-Version: ${STRIPE_API_VERSION};udap_beta=v1" \ -H "Stripe-Account: {{CONNECTED_ACCOUNT_ID}}" \ -usk_test_BQokikJOvBiI2HlWgH4olfQ2: \ -d file={{FILE_ID}} \ --data-urlencode standard_data_format="inventory_feed"sk_test_BQokikJOvBiI2HlWgH4olfQ2
OptionalHandle refunds and disputes
If you already use the PaymentIntents or Checkout Sessions API, your existing refunds and disputes integration doesn’t require changes for in-context agentic selling. PaymentIntents are still created for in-context agentic selling flows. As long as you associate the PaymentIntent ID with your order, your refunds and disputes integration continues to work.
After checkout succeeds, you can initiate a refund if a customer cancels the order from your website or through customer service. If you already use the Checkout Sessions or PaymentIntents API, your existing refund flow works without changes for in-context agentic selling.
Manage refunds and disputes without code in the Dashboard from the Transactions page.
To handle refunds programmatically, integrate with the Refunds API for post-checkout cancellation or refund requests.