Docs · Setup

Wire a supplier via Stripe ACP

Skip the email round-trip and the browser sign-in wizard for suppliers that publish an Agentic Commerce Protocol endpoint. The bot drafts → you approve → bot calls the merchant's checkout API directly. Faster, no scraping, no brittle per-supplier login.

1

Confirm the supplier supports ACP

ACP is brand-new (Stripe + OpenAI launched it in 2026). Coverage today is heavy on consumer DTC; most B2B foodservice suppliers (Sysco, GFS, Restaurant Depot) aren't on the network yet. Suppliers that DO support it today:

  • Etsy storefronts (specialty roasters, small-batch dry goods)
  • Shopify storefronts that have opted into Stripe ACP
  • WooCommerce / BigCommerce / commercetools / Wix stores via Stripe's suite
  • A handful of large brands: Coach, Kate Spade, URBN, Revolve, Ashley Furniture

Ask the supplier directly whether they publish an ACP /checkout_sessions endpoint. If the answer is “huh?” — they're not on the network. Use email or website mode for now.

2

Get the supplier's ACP endpoint URL + (maybe) API key

From the supplier, you need:

  • Endpoint base URL — e.g. https://store.example.com/agentic-commerce. Our bot will POST to <endpoint>/checkout_sessions.
  • (Optional) Bearer API key — some merchants require one at onboarding; others accept anonymous calls and gate on the payment-delegation step instead.
3

Add the supplier with mode=STRIPE_ACP

On /suppliers, click + Add supplier. Use:

Ordering mode

STRIPE_ACP

Then paste the endpoint URL + (if you have one) the API key. Both are encrypted at rest.

4

Tell the bot to draft + approve

Same conversation as any supplier — the bot doesn't care about the dispatch mode at draft time:

  • “we need 2 cases of oat milk from <supplier>” → bot drafts a PO
  • You tap Approve
  • Bot POSTs to the merchant's ACP endpoint. The PO moves to SENT with an ACP CheckoutSession id stored on the row.
No email send, no browser script, no supplier sign-in.
5

(Pending) Stripe Link Agent Wallet payment delegation

ACP's checkout flow is two-step: create the session, then POST /complete with a payment token from the Stripe Link Agent Wallet to finalize.

Stripe Link Agent Wallet was announced at Sessions 2026 and is in private beta as of May 2026. Until you have credentials, the bot stops at step-1 (the session is open + ready_for_payment) and you complete the payment manually from the supplier's site OR the supplier sends an invoice. When Link Agent ships publicly, the bot does the second call automatically and the order moves straight to ACKNOWLEDGED.

← Back to Settings