Stripe & Shopify
Look up Stripe payments, customers and subscriptions, issue refunds and review disputes.
OpenClaw
online
What you can do with Stripe
These are examples - your agent can use any of the tools you allow.
Reconcile Shopify Orders With Stripe
Match Shopify orders and refunds against Stripe charges and refunds to surface discrepancies.
Investigate Failed Shopify Payments
Combine Shopify order details with Stripe failure data to explain failed payments and next steps.
Monitor Payment Disputes And Chargebacks
Match open Stripe disputes to Shopify orders and assemble evidence checklists with deadlines.
Detect Refund Reconciliation Problems
Compare Shopify refunds with Stripe refunds to catch amount, status, or timing differences early.
Browse all use cases and example prompts
Reconcile Shopify Orders With Stripe
Match Shopify orders and refunds against Stripe charges and refunds to surface discrepancies.
Example prompt: Reconcile my Shopify orders and refunds against available Stripe payment records for the date range I specify. Match records using reliable identifiers first, followed by customer references, amount, currency, timestamps, and metadata where appropriate. Prepare a report containing the Shopify order number and payment status, matching Stripe charge or PaymentIntent reference, transaction amount and currency, Shopify refund amount and corresponding Stripe refund records when available, potentially unmatched or inconsistent records, and recommended investigation steps. Account for partial refunds, multiple transactions, and processing delays. Do not assume that similar amounts alone prove two records are related. Clearly distinguish confirmed matches from possible matches. Do not create refunds, modify payment records, or mark orders as paid. Ask for approval before taking any corrective action.
Investigate Failed Shopify Payments
Combine Shopify order details with Stripe failure data to explain failed payments and next steps.
Example prompt: Investigate Shopify orders with failed, pending, or otherwise concerning payment statuses. Search available Stripe PaymentIntents, charges, and payment attempt records for matching transactions. For each case, provide the Shopify order number and current payment status, the matching Stripe transaction reference if confirmed, available failure information, whether the payment requires customer action, further investigation, or no action, and a suggested next step for the support or finance team. Do not infer a specific decline reason when Stripe does not provide one. Do not treat a failed attempt as proof that every subsequent attempt failed. Do not retry charges, create new payment requests, or change Shopify order status without explicit approval.
Monitor Payment Disputes And Chargebacks
Match open Stripe disputes to Shopify orders and assemble evidence checklists with deadlines.
Example prompt: Review open Stripe disputes and match them with the relevant Shopify orders wherever reliable references are available. For each dispute, summarize the Stripe dispute reference, amount, currency, and status, the matching Shopify order and purchased products, available fulfillment and delivery evidence from connected integrations, relevant refund history, dispute deadlines and evidence requirements when available, and recommended evidence to gather next. Distinguish retrieved facts from suggested evidence. Do not claim an order was delivered unless the available records support that statement. Prepare an evidence checklist for each case. Do not submit evidence, accept a dispute, close a dispute, or issue a refund without my explicit approval.
Detect Refund Reconciliation Problems
Compare Shopify refunds with Stripe refunds to catch amount, status, or timing differences early.
Example prompt: Review Shopify refunds for the specified period and compare them with available Stripe refund records. Identify Shopify refunds with no confidently matched Stripe refund, Stripe refunds without a confidently matched Shopify refund, differences between recorded refund amounts or currencies, partial refunds that need additional reconciliation, and refunds whose current status may require follow-up. Include order references, transaction IDs, timestamps, amounts, and supporting evidence where available. Do not assume that every discrepancy is an error. Consider processing delays, multiple refunds, and differences in record timing. Prepare a prioritized report for finance. Do not create additional refunds or modify existing records without approval.
Alert Teams About Payment Failures
Use Stripe failure triggers with Shopify matching and Slack alerts for fast team response.
Example prompt: Design a workflow for Stripe payment failure events. When a relevant failure event occurs, retrieve the available Stripe payment and failure details. Attempt to match the transaction with a Shopify order using reliable identifiers. Include the order number, amount, currency, payment status, and failure details when available. Search relevant Slack discussions for existing context if Slack is connected. Prepare a concise alert for the designated finance or support channel. Include only information needed to investigate the issue. Avoid sharing full card details or unnecessary customer personal information. Do not automatically retry the payment, create another charge, or mark an order as paid. If the order cannot be confidently matched, label it as unmatched. Ask me to confirm the channel and workflow behavior before enabling notifications.
Analyze Shopify Sales Against Stripe Payouts
Compare Shopify sales with Stripe transactions, fees, and payouts to explain revenue differences.
Example prompt: Compare Shopify sales and refund records with available Stripe balance transactions, fees where exposed, and payout information for the period I specify. Prepare a reconciliation summary showing Shopify gross sales and recorded refunds, matched Stripe payment transactions, available Stripe fees and adjustments, payout amounts and payout statuses, timing differences and potential unmatched transactions, and remaining unexplained differences. Use consistent currencies and date ranges. Distinguish order revenue from payment volume, Stripe balance movements, and bank payouts. Do not assume that payout totals equal Shopify sales for the same day. Account for processing timing, fees, refunds, and other available adjustments. Identify missing data and recommend next checks. Do not modify financial records or initiate transfers.
Investigate Suspicious Shopify Transactions
Prioritize orders flagged by Stripe disputes, fraud warnings, and reviews for manual checks.
Example prompt: Review Shopify orders alongside available Stripe disputes, early fraud warnings, open reviews, and related payment records. Identify transactions that have explicit risk signals or inconsistencies requiring further investigation. For each case, include the Shopify order reference and available order details, the matching Stripe transaction and its current status, the specific risk signal returned by Stripe, relevant refund, dispute, or review information, and recommended verification steps. Do not invent fraud scores or classify a customer as fraudulent based solely on order value, location, or a failed payment. Clearly distinguish a warning from a confirmed fraudulent transaction. Prepare a review queue. Do not cancel orders, block customers, capture payments, or issue refunds without my approval.
Manage Stripe Subscriptions For Customers
Combine Shopify customer context with Stripe subscription, invoice, and payment status.
Example prompt: Review the subscription-related customer issues I specify using Shopify customer and order information alongside available Stripe subscription and invoice records. Identify active, trialing, past-due, or canceled Stripe subscriptions, upcoming invoice information where available, failed invoice payment attempts, relevant Shopify orders or customers when confidently matched, and potential customer access or billing issues. Do not assume that every Shopify customer has a Stripe subscription or that every Stripe subscription belongs to a Shopify order. Explain how each match was established. Recommend appropriate follow-up for billing or support. Do not cancel, resume, or modify subscriptions, change discounts, or send payment requests without explicit approval.
Compare Discounts With Payment Outcomes
Relate Shopify discounts to Stripe payments, refunds, and transaction values where data supports it.
Example prompt: Analyze Shopify orders and available discount information alongside matched Stripe payment records for the period I specify. Compare performance across discount codes or campaign groups where the data supports reliable attribution. Include order counts and sales totals, discount amounts recorded in Shopify, matched Stripe payment totals and refund activity, payment failure rates if the available data supports the calculation, differences across promotion groups, and data limitations plus recommended experiments. Do not assume a Stripe transaction contains the Shopify discount code unless it is explicitly recorded or reliably linked. Do not infer profit without product costs, payment fees, and other necessary data. Summarize the findings and recommend tests. Do not create promotion codes, change prices, or modify payment settings without approval.
Build A Daily Payment Operations Briefing
One prioritized daily report from Shopify orders and Stripe payments, refunds, disputes, and payouts.
Example prompt: Prepare a daily payment operations briefing using Shopify order and refund data alongside available Stripe payment records. Include failed or incomplete payment attempts, Shopify orders with potentially inconsistent payment status, refunds requiring reconciliation, new or updated disputes, invoice payment failures if applicable, payout issues and relevant balance movements, unmatched transactions, and recommended investigations. Include transaction references, amounts, currencies, timestamps, and source status where available. Avoid duplicate alerts for the same underlying issue. Prioritize cases by urgency and financial impact, but do not invent a risk score. Clearly separate verified discrepancies from possible ones. If Slack is connected, draft a concise briefing for the finance channel. Ask for approval before posting. If recurring delivery is required, confirm the schedule and destination before configuring it.
Works well with
What Stripe can do
426 toolsShowing 1-10 of 426
STRIPE_CREATE_PRODUCTCreates a new product in Stripe, encoding the request as `application/x-www-form-urlencoded` by flattening nested structuresSTRIPE_CREATE_PRICECreates a new Stripe Price for a product, defining its charges (one-time or recurring) and billing scheme; requires either an existing `product` ID orSTRIPE_CREATE_PREVIEW_INVOICETool to preview an upcoming invoice without creating itSTRIPE_COLLECT_TERMINAL_READER_PAYMENT_METHODTool to initiate payment method collection on a Stripe Terminal ReaderSTRIPE_CREATE_PLANTool to create a recurring billing plan with flexible pricing configurationSTRIPE_ACCEPT_QUOTETool to accept a quote in StripeSTRIPE_ACTIVATE_BILLING_ALERTReactivates a billing alert, allowing it to trigger againSTRIPE_ADD_INVOICE_LINESTool to add multiple line items to a draft Stripe invoiceSTRIPE_ADVANCE_TEST_CLOCKAdvance a test clock to a future timestampSTRIPE_APPLY_CUSTOMER_BALANCEManually reconciles remaining amount for a customer_balance PaymentIntent by applying funds from customer's cash balance
Triggers
STRIPE_CUSTOMER_SUBSCRIPTION_TRIAL_WILL_ENDOccurs three days before a subscription's trial period is scheduled to end, or immediately when a trial is ended early (for example, with `trial_end=nSTRIPE_CUSTOMER_SUBSCRIPTION_UPDATEDOccurs whenever a subscription changes (e.g., switching from one plan to another, or changing the status from trial to active)STRIPE_CUSTOMER_UPDATEDOccurs whenever any property of a customer changesSTRIPE_INVOICE_CREATEDOccurs whenever a new invoice is createdSTRIPE_INVOICE_FINALIZEDOccurs whenever a draft invoice is finalized and updated to be an open invoiceSTRIPE_INVOICEITEM_CREATEDOccurs whenever an invoice item is createdSTRIPE_INVOICE_PAIDOccurs whenever an invoice payment attempt succeeds or an invoice is marked as paid out-of-bandSTRIPE_INVOICE_PAYMENT_FAILEDOccurs whenever an invoice payment attempt fails, due to either a declined payment, including soft decline, or to the lack of a stored payment methodSTRIPE_INVOICE_PAYMENT_SUCCEEDEDOccurs whenever an invoice payment attempt succeedsSTRIPE_CHARGE_SUCCEEDEDOccurs whenever a charge is successfulSTRIPE_CHECKOUT_SESSION_ASYNC_PAYMENT_FAILEDOccurs when a payment intent using a delayed payment method failsSTRIPE_CHECKOUT_SESSION_ASYNC_PAYMENT_SUCCEEDEDOccurs when a payment intent using a delayed payment method finally succeedsSTRIPE_CHECKOUT_SESSION_COMPLETEDOccurs when a Checkout Session has been successfully completedSTRIPE_CHECKOUT_SESSION_EXPIREDOccurs when a Checkout Session is expiredSTRIPE_CUSTOMER_CREATEDOccurs whenever a new customer is createdSTRIPE_CUSTOMER_DELETEDOccurs whenever a customer is deletedSTRIPE_CUSTOMER_SUBSCRIPTION_CREATEDOccurs whenever a customer is signed up for a new planSTRIPE_CUSTOMER_SUBSCRIPTION_DELETEDOccurs whenever a customer's subscription endsSTRIPE_CHARGE_CAPTUREDOccurs whenever a previously uncaptured charge is capturedSTRIPE_CHARGE_DISPUTE_CLOSEDOccurs when a dispute is closed and the dispute status changes to `lost`, `warning_closed`, or `won`STRIPE_CHARGE_DISPUTE_CREATEDOccurs whenever a customer disputes a charge with their bankSTRIPE_CHARGE_DISPUTE_UPDATEDOccurs when the dispute is updated (usually with evidence)STRIPE_CHARGE_FAILEDOccurs whenever a failed charge attempt occursSTRIPE_CHARGE_REFUNDEDOccurs whenever a charge is refunded, including partial refundsSTRIPE_CHARGE_REFUND_UPDATEDOccurs whenever a refund is updated on selected payment methodsSTRIPE_INVOICE_UPCOMINGOccurs X number of days before a subscription is scheduled to create an invoice that is automatically charged-where X is determined by your subscriptiSTRIPE_INVOICE_VOIDEDOccurs whenever an invoice is voidedSTRIPE_PAYMENT_INTENT_CANCELEDOccurs when a PaymentIntent is canceledSTRIPE_PAYMENT_INTENT_CREATEDOccurs when a new PaymentIntent is createdSTRIPE_PAYMENT_INTENT_PAYMENT_FAILEDOccurs when a PaymentIntent has failed the attempt to create a payment method or a paymentSTRIPE_PAYMENT_INTENT_REQUIRES_ACTIONOccurs when a PaymentIntent transitions to requires_action stateSTRIPE_PAYMENT_INTENT_SUCCEEDEDOccurs when a PaymentIntent has successfully completed paymentSTRIPE_PAYMENT_LINK_CREATEDOccurs when a payment link is createdSTRIPE_PAYOUT_FAILEDOccurs whenever a payout attempt failsSTRIPE_PAYOUT_PAIDOccurs whenever a payout is *expected* to be available in the destination accountSTRIPE_PRICE_CREATEDOccurs whenever a price is createdSTRIPE_PRICE_UPDATEDOccurs whenever a price is updatedSTRIPE_PRODUCT_CREATEDOccurs whenever a product is createdSTRIPE_PRODUCT_UPDATEDOccurs whenever a product is updatedSTRIPE_REFUND_CREATEDOccurs whenever a refund is created
Connect Stripe
Agiexa is preparing for public launch in November 2026. These steps describe the connection flow; join the waitlist for access updates. OpenClaw and Hermes use Agiexa plugins. Other agent connections are coming soon via MCP.
- 1Install Agiexa on your store
- 2Connect Stripe - one sign-in, no passwords shared
- 3Choose what your agent can do
Before connecting, read about agent permissions and MCP connections for Shopify.
Questions
How do I connect Stripe?
What can my agent do in Stripe?
Will it act without asking me?
How do I disconnect Stripe?
Related integrations
Ready when you are.
I'm Interested