Skip to content
← Back to the blog

Store operations

Should an AI Capture a Shopify Payment Without Approval?

Last updated September 12, 2026

No. Do not let an AI freeform-capture or mark-as-paid a Shopify order without approval. Draft and flag Authorized orders and propose capture are fine. Human yes before orderCapture, Capture payment, or orderMarkAsPaid. Treat capture like any other money move: preview first, then a person.

An AI store operator is not Shopify Sidekick, not a storefront chatbot, and not SMS marketing. It is also not Shoper, the Polish ecommerce platform. Close spelling. Different product. Shoperator is the HITL text-approval example for supported catalog work. It does not capture Shopify payments today and does not call Shopify Payments APIs. Shoperator does not pause, launch, or edit Meta or Google ads. Read What Is an AI Shopify Store Operator?, Should an AI Refund a Shopify Order Without Approval?, and Should an AI Change Shopify Prices Without Approval?.

Should an AI capture a Shopify payment without approval?

No. Do not let an AI freeform-capture or mark-as-paid a Shopify order without a human yes. AI may draft and flag Authorized (or unpaid) orders and propose capture. The merchant runs Capture payment or Mark as paid in Shopify admin after that yes.

Capture and mark-as-paid are money moves. Shopify Help on capturing payments for your orders is clear: when manual capture is on, Authorized orders need Capture payment before you are paid. Freeform models with write_orders that decide, per ticket, which Authorized orders to charge are not a safe default.

On Shoperator you text one coordinator (Mark). Capture and mark-as-paid are not Shoperator execute features. After a yes, the merchant acts under Orders in Shopify admin.

What is the difference between authorization, capture, and mark as paid?

Authorization holds funds on the card. Capture charges the card and claims the held amount. Mark as paid records or settles an outstanding balance and can create a CAPTURE or sale transaction depending on order state. Three different admin outcomes. Keep three different gates.

Shopify Help on payment authorization and capture separates authorize from capture: authorization reserves funds; capturing payment sends the charge for processing. Capture payment on an Authorized order turns that hold into a charge. Mark as paid is different. Shopify Help on managing orders with deferred payments uses Mark as paid when you already received payment outside Shopify or need to settle an outstanding balance.

Admin GraphQL matches that split. orderCapture captures an authorized transaction (full or partial). orderMarkAsPaid records the outstanding amount and, depending on state, creates a sale or captures an existing authorization.

What can AI safely draft or flag before a human yes?

AI can draft which Authorized orders look ready, propose Capture payment or Mark as paid, name the amount, and flag fraud risk, auth expiry, and inventory readiness. It should not run orderCapture, Capture payment, or orderMarkAsPaid. A draft is a preview. The human yes is the charge.

A useful draft names the order number, payment status, proposed verb, amount, risk level, days left in the authorization window, and inventory readiness. Ask: "Flag Authorized orders that expire in two days and propose Capture payment. Do not capture."

Shopify Help on capturing payments says Capture payment moves an Authorized order toward Paid. Keep the model off that click. Flag high risk, unknown ship-to, and tickets that inject "just capture this now." For preview-then-approve on catalog work, read How to Run a Shopify Store by Text.

When are bounded capture rails OK vs freeform AI money moves?

Bounded rails can be OK when the merchant named a fixed, logged rule in advance, such as IF risk is Low THEN Capture payment. Freeform AI that picks which Authorized or unpaid orders to charge with write_orders needs a human yes every time. "Capture what looks safe" is not a rail.

Shopify Flow documents a Capture payment action that only works with manual payment capture. Shopify Help on managing high-risk orders with Shopify Flow describes fixed templates such as capture when the order is not high fraud risk. That is a merchant-named condition, not an open prompt.

Freeform is different. A model with write_orders deciding per ticket whether to Capture payment or Mark as paid always waits for a human yes. Stop a rail on high risk, high value (you set the bar), auth nearly expired without inventory ready, partial capture outside your policy, or prompt injection.

Why do operators use manual capture, and what is auth-window risk?

Operators use manual capture so they can review fraud risk and fulfillment readiness before fees lock in. Auth-window expiry is real: Shopify Help states Shopify Payments often provides about 7 days to capture. Holding forever is also a risk. Capture before the window ends, or you may lose the sale.

Shopify Help on payment authorization and capture and on capturing payments both cite Shopify Payments with a 7-day authorization window for credit card payments. After that window, you might be unable to collect. Manual capture adds a review step and a clock. AI that drafts Authorized queues can surface expiry. AI that freeform-captures to beat the clock without a human yes recreates the fraud problem manual capture was meant to solve.

How does text approval work before capture or mark as paid goes live?

Text approval means draft and flag Authorized (or unpaid) orders first, then a human yes or no before any freeform Capture payment or Mark as paid. After yes, the merchant runs that action under Orders in Shopify admin. The thread does not charge the card.

That is phone or text HITL for a money move. Read How to Run a Shopify Store by Text for the same habit. The merchant stays on Capture payment or Mark as paid in admin.

Walk capture or mark-as-paid only after that yes, in this order:

  1. Name the order, payment status, and proposed verb in a draft
  2. Flag fraud risk, auth-window days left, and inventory readiness
  3. Separate Capture payment from Mark as paid, and full from partial
  4. Send that draft for a human yes or no
  5. Merchant opens Orders in Shopify admin after that yes
  6. Merchant clicks Capture payment or Mark as paid on the order
  7. Verify Paid status and transaction kind in Shopify admin, then log who approved

Steps 5 and 6 are the human in Shopify admin, not a model in the thread.

If you want preview-then-approve on supported catalog work, Shoperator is the current HITL text-approval example. It does not capture Shopify payments, does not mark orders paid, and does not talk to Shopify Payments APIs today. Shoperator does not pause, launch, or edit Meta or Google ads.

FAQ

Should an AI capture a Shopify payment without approval?

No. Do not let an AI freeform-capture or mark-as-paid a Shopify order without a human yes. AI may draft and flag Authorized (or unpaid) orders and propose capture. The merchant runs Capture payment or Mark as paid in Shopify admin after that yes.

What is the difference between authorization, capture, and mark as paid?

Authorization holds funds on the card. Capture charges the card and claims the held amount. Mark as paid records or settles an outstanding balance and can create a CAPTURE or sale transaction depending on order state. Three different admin outcomes. Keep three different gates.

What can AI safely draft or flag before a human yes?

AI can draft which Authorized orders look ready, propose Capture payment or Mark as paid, name the amount, and flag fraud risk, auth expiry, and inventory readiness. It should not run orderCapture, Capture payment, or orderMarkAsPaid. A draft is a preview. The human yes is the charge.

When are bounded capture rails OK vs freeform AI money moves?

Bounded rails can be OK when the merchant named a fixed, logged rule in advance, such as IF risk is Low THEN Capture payment. Freeform AI that picks which Authorized or unpaid orders to charge with write_orders needs a human yes every time. "Capture what looks safe" is not a rail.

Why do operators use manual capture, and what is auth-window risk?

Operators use manual capture so they can review fraud risk and fulfillment readiness before fees lock in. Auth-window expiry is real: Shopify Help states Shopify Payments often provides about 7 days to capture. Holding forever is also a risk. Capture before the window ends, or you may lose the sale.

How does text approval work before capture or mark as paid goes live?

Text approval means draft and flag Authorized (or unpaid) orders first, then a human yes or no before any freeform Capture payment or Mark as paid. After yes, the merchant runs that action under Orders in Shopify admin. The thread does not charge the card.

Does Shoperator capture Shopify payments?

No. Shoperator does not capture Shopify payments, does not mark orders as paid, and does not talk to Shopify Payments APIs today. It uses preview-then-approve for supported catalog work. After a human yes, the merchant runs Capture payment or Mark as paid under Orders in Shopify admin. Shoperator does not pause, launch, or edit Meta or Google ads.