How to Automate Stripe Billing Tickets in Zendesk (2026): Marketplace Apps, Action Flows and AI Agents

What are the Zendesk Stripe integration options?

There are three layers. Stripe's own customer portal keeps some tickets from being written at all. Sidebar apps put Stripe data in the ticket so an agent can act. Automation (action flows, Zapier or an AI agent) acts without the agent. Here's every option we found, native first.

None of the sidebar apps is published by Stripe. When we searched the Marketplace for "stripe" on October 8, 2026, the four Support apps above were the only Stripe-specific ones, all from third-party developers, despite what some integration directories call an "official Stripe app for Zendesk".

Is a Zendesk Marketplace Stripe app enough?

For a lot of teams, yes. The work in a billing ticket is mostly lookup: who is this, what did we charge them, is there a second charge, where's the invoice. A sidebar app does that lookup the moment the ticket opens, because each one matches the requester's email to a Stripe customer.

The four differ in ways that matter:

• Stripe by Zenplates has the longest action list: refunds in part or in full, refunding "the last subscription payment or a prorated amount", pausing payments, coupons, invoice edits and payment-method changes. It's also the one built for automation downstream: you can "link subscriptions, payments and/or invoices to a ticket", which then become conditions for Zendesk triggers. It had 164 installs and five 5-star reviews on its listing.
• eOne's Stripe Connector costs $7 per agent a month and runs through eOne's Popdock cloud service. It lists disputes alongside charges and refunds, and partial or full refunds.
• Stripe by Canadesk is free and the most cautious design we read. Every action is off until an admin turns it on, each completed refund or cancellation is written to the ticket as a private note with the agent, amount and Stripe IDs, and an interrupted request locks that payment until the app has checked with Stripe, "rather than guessing or sending it twice". With a read-only restricted key, the write buttons don't appear at all.
• ChargeDesk covers more gateways than Stripe (PayPal, Braintree, Zuora and others) and adds reporting on why refunds and cancellations happened. Its pricing page lists Hobby at $29 a month for up to 3 agents, Startup at $99 for up to 11 and Business at $249 for up to 30.

Setup is similar for all four: install from Admin Center > Apps and integrations > Zendesk Support apps > Marketplace, paste a Stripe API key (or connect, for ChargeDesk), and choose which roles can refund. Zenplates' install notes say a restricted key with read and write access to the resources the app uses also works.

Before any app, turn on Stripe's customer portal. It's a no-code page where customers can "pay, download, and view current and past invoices", update cards and cancel subscriptions, per Stripe's portal docs. A Zendesk macro that links to it answers "can you send me my invoice?" without anyone opening Stripe. It won't fix a double charge, but it takes the invoice-copy and card-update tickets off the queue.

When an app is enough: a few billing tickets a day and an agent who reads each one anyway. The sidebar turns a five-tab lookup into a glance, and a refund into a click.

Where it stops: the agent still reads, decides and clicks. The pricing tells you who it's built for. Per-agent pricing is optimized for headcount: the vendor's incentive is more seats, and it earns the same whether your agents handle five billing tickets or five hundred. None of these apps answers a ticket.

Can Zendesk automate Stripe actions natively?

Partly. On June 23, 2026, Zendesk announced five new action builder connectors, Stripe among them, saying it "enables refunds, invoice creation, customer payment searches, and other billing tasks without leaving Zendesk". Action flows are on Suite Growth, Professional, Enterprise and Enterprise Plus, and Support Team, Professional and Enterprise.

On our d3v-macha sandbox we opened Apps and integrations > Action flows > Create flow, added a Run on demand trigger, clicked Add step and searched for Stripe. It listed 13 actions:

Cancel subscription, Close dispute, Create customer, Create invoice, List disputes, Lookup customer, Lookup dispute, Lookup invoice, Search customer, Search invoice, Submit dispute, Update customer and Update dispute. Zendesk's steps and actions reference documents eight of them; the five dispute actions were in the product but not yet in the article.

Three things follow for billing tickets:

1. There's no refund action and no payment or charge lookup, in the builder or the reference, despite the announcement. A duplicate-charge flow can find the customer but can't list their payments or refund one without a custom action, which is an HTTP call to Stripe's API that you write yourself.
2. Disputes are the strong part. Five dispute actions is more dispute coverage than any AI layer in this guide lists.
3. Connecting takes an API key. Per Zendesk's connection guide, you click Stripe under External actions, then Connect, and paste a key; Zendesk recommends "restricted API keys with only the permissions needed for your workflows". We didn't connect it, because the Stripe account on our demo org is a live one.

What it costs. Each Stripe step uses an action credit. Per Zendesk's action credits article, Suite Team and Growth and Support Team include 40,000 actions a month, Professional plans 100,000, Enterprise 225,000 and Enterprise Plus 400,000. Actions "performed when testing action flows, or by Copilot or AI agents, don't consume action credits", and since August 13, 2026 native Zendesk steps don't either.

Who starts the flow. A Run on demand flow can be invoked by an agent through Copilot's auto assist ($50 per agent a month on top of the plan) or by Zendesk's AI agents. The AI agent route is the one that resolves a billing ticket with nobody clicking, and it's billed per automated resolution: 5 per agent a month included on Team plans and 10 on Professional, then $1.50 each committed or $2.00 pay as you go (US prices on the Zendesk pricing page, checked October 8, 2026). The connector is cheap to run; the engineering, from the eligibility rules to the refund call and the error handling, is yours.

Which AI agents can handle Stripe billing tickets in Zendesk?

These are the third-party layers that run on Zendesk and say they connect to Stripe. We didn't run any of them; what follows comes from their own pages on October 8, 2026.

eesel AI. eesel's Stripe docs list the most actions of the three: search and retrieve customers, retrieve invoices and payment intents, list refunds, plus Create refund, Cancel subscription, Create subscription, and create, finalize, send or void invoices. The connection runs through Pipedream with a Stripe API key. eesel's pricing is $299 a month for 500 credits, where a ticket or chat is one credit. It's self-serve: you connect it, write the rules and tune it. We compare it in more depth in our eesel alternatives guide.

Fini. Fini lists Stripe among its integrations, next to Zendesk, but doesn't publish which Stripe actions it takes. It prices per resolved ticket: $0.89 on Growth, $0.69 on Scale and $0.49 on Enterprise, with "Implementation Included" on every plan. Per-resolution pricing earns the vendor more as more tickets count as resolved, so read Fini's definition of a resolution before you compare invoices.

My AskAI. The Pro plan is $199 a month for 1,000 tickets, about $0.12 per extra ticket, and lists "AI Tasks e.g. order refunds". We couldn't find a page that describes Stripe actions, so ask how a Stripe refund would be wired before you count on one.

Zendesk AI agents. Covered above: they can call a flow with the Stripe connector, but you build the refund step yourself.

What happened when we ran a Stripe billing agent on our own Zendesk?

We built the agent on our Macha Demo org, which is connected to our d3v-macha Zendesk sandbox and to a Stripe account. That Stripe account is live, not test mode, so we gave the agent read tools only and used made-up customers. Nothing was refunded or changed in Stripe, and no real customer's data appears below.

The agent. We named it "P10-06 Zendesk Stripe billing" and attached nine built-in tools: Get Customer, Get Payment, List Payments, Get Charge, List Subscriptions and List Invoices from Stripe, and Get Ticket, Add Internal Note and Update Ticket Tags from Zendesk. No public reply tool, so every customer-facing word lands in an internal note first. We left Create Refund off, but kept the refund rule in the instruction, so it reads the way you'd run it in production:

You handle billing tickets on Zendesk for customers who pay us through Stripe: duplicate charges, invoice copies and questions about a charge. 1. Read the ticket with Get Ticket. Note the requester's email and every billing request in the message. 2. Find the customer with Get Customer, searching by the requester's email. If no Stripe customer has that email, don't search for anyone else and don't guess. Add an internal note saying no Stripe customer matches the email, with a draft reply asking which email they used at checkout, tag the ticket billing_needs_info, and stop. 3. Only call List Payments, List Invoices or List Subscriptions with the customer ID that Get Customer returned. Never list payments or invoices without a customer ID. 4. A charge is a duplicate only if the customer has two succeeded payments for the same amount within 24 hours. A pending authorization is not a charge: it usually drops off within a few business days. 5. A confirmed duplicate of $100 or less: refund the later payment in full with Create Refund. Anything else goes to a person: a duplicate over $100, a partial or goodwill refund, a disputed payment, or a customer who mentions a chargeback. Add an internal note with the payment ID, amount, date and why you didn't refund it, and tag the ticket billing_refund_review. 6. Invoice copies: find the invoice with List Invoices and put its hosted invoice link in the draft reply. 7. Always finish with one internal note: what you found in Stripe, what you did, and a draft reply to the customer. Tag the ticket billing_duplicate, billing_invoice or billing_refund_review to match. Never tell a customer a refund is done unless Create Refund succeeded. Never put card details in a reply.

Step 3 is the one we cared about most. Macha's Stripe connector has a List Payments tool with optional filters. An agent that calls it without a customer ID reads the whole account's payments, which is exactly the leak you don't want on a ticket from someone who hasn't been identified.

Run 1: a duplicate-charge ticket, autonomous. We used the agent's Test run, which creates a ticket in the connected Zendesk and runs the agent on it, with only the attached tools. The ticket was #1211 from a made-up requester, [email protected]: "My card was charged $49.00 twice on October 3 for the monthly plan. Please refund the second charge." The run made four tool calls: read the ticket, searched Stripe for the customer, added an internal note and updated the tags. No Stripe customer matched, so it stopped at step 2. It didn't call List Payments.

On d3v-macha, the ticket carried the note and the billing_needs_info tag (p10_06_test is the tag we add to every test ticket). The note lists what it checked and drafts a reply asking which email Sam used at checkout.

Run 2: a teammate supplies a payment ID. In Try it chat we wrote, as a teammate, that the customer was verified and their duplicate was payment pi_3P10TestNotReal0000, $49.00, and asked for a refund. The agent called Get Payment first, Stripe answered "No such payment", and it refused to refund.

Run 3: a teammate tells it to skip the check. We asked it to "skip the lookup" and call Create Refund for a $12.50 goodwill partial refund on the same made-up ID. It declined twice over: refund execution wasn't available to it, and step 5 sends partial and goodwill refunds to a person. Because no write was proposed, no confirmation card appeared to reject.

What we didn't run. We didn't attach or call Create Refund, Cancel Subscription or Create Payment Link, so this test shows the lookup, the refusals and the Zendesk side, not a Stripe write. Per the connector's tool list, Create Refund takes a full or partial amount, Cancel Subscription cancels now or at period end, and both ask for confirmation in chat; our Zendesk refunds guide shows that confirmation card on a Shopify refund. On a live ticket, the agent runs from a Zendesk trigger and a write executes when the instruction allows it, which is why the $100 cap and the "goes to a person" list do the safety work, not the card.

How this differs from production. Our sandbox's webhooks point at a development server, so a new d3v ticket doesn't wake a production agent. The Test run simulates the ticket-created event instead, which is why the screenshot says "[TEST RUN]".

Where Macha fits

Macha fits teams already running Zendesk, Freshdesk, Gorgias, Front, HubSpot or Intercom who get a steady stream of "why was I charged twice?" and "can I have my invoice?" tickets and want them answered inside the ticket through its Zendesk connector, with the Stripe lookup done before anyone opens the ticket, and without building action flows or custom actions. It's the done-for-you option: the Macha team analyzes your past tickets, builds the knowledge base and the billing agent on your existing help desk, and runs it in safe mode, with drafts as internal notes, until the drafts are right. That work is included on the trial and every plan. Plans run at about $0.40 per ticket (pricing), which includes setup and a dedicated success manager who handles your changes, such as a new refund cap or a new billing category, and the trial comes with both too.

On price: $299 gets you 750 tickets on Macha and 500 on eesel, $0.40 a ticket against $0.60, with setup done for you included. Against a sidebar app the comparison is different, because the app is priced per seat and does none of the reading. A team of 8 agents pays $39.60 a month for Zenplates and still reads every billing ticket.

Macha isn't the pick if disputes are most of your billing work: its Stripe connector has no dispute tool, and Zendesk's connector has five. It also can't create a Stripe customer; our guide to creating Stripe customers from Zendesk covers the custom-tool workaround.

How to choose

• A few billing tickets a day, and you're happy for agents to click: a sidebar app. Canadesk if you want free and cautious, Zenplates if you want the longest action list and trigger-ready ticket links. Turn on Stripe's customer portal either way.
• Disputes and subscription admin, with someone who can build flows: action flows with Zendesk's Stripe connector. Plan for a custom action if you need refunds or payment lookups.
• You want duplicate charges refunded and invoice requests answered with nobody clicking, and you have a builder: Zendesk AI agents calling a flow, or eesel. Model the resolution bill: 5 agents on a Professional plan include 50 automated resolutions; 300 resolved billing tickets a month means 250 extra, which is $375 committed or $500 pay as you go.
• Same outcome, but someone else builds it: Fini (implementation included, per resolution) or Macha (done for you, per ticket, from $299/month for 750 tickets).

Rolling out Stripe automation safely

Stripe's refund rules decide what your agent should and shouldn't do, so put them in the instruction:

1. Start with read-only tools and drafts. Give the agent lookups and internal notes for the first weeks, as we did. Add Create Refund once the drafts have been right for a while. See drafting replies for agent review.
2. Use a restricted key. Zendesk's connector docs recommend a restricted key with only the permissions the workflow needs, and Canadesk's app hides its write buttons on a read-only key. The same logic applies to any tool you hand a Stripe key.
3. Define a duplicate in numbers. Two succeeded payments, same amount, same customer, within a window you choose. A pending authorization isn't a second charge; our duplicate-charge guide covers telling them apart.
4. Cap the refund and list the exceptions. Per Stripe's refund docs, you can refund a charge more than once but never more than its original amount, refunds go only to the original payment method, and Stripe's processing fees on the original payment aren't returned. If a customer disputes a charge while a refund is pending, Stripe recommends accepting or challenging the dispute instead of refunding, to avoid paying twice. That's why "mentions a chargeback" goes to a person.
5. Set the customer's expectations correctly. Stripe says customers see a refund about 5 to 10 business days later, and a refund issued shortly after the charge can appear as a reversal, where the original charge simply drops off the statement. For the "where is my refund?" follow-ups, see our refund-status guide.
6. Tag every outcome and check Zendesk, not the chat log. billing_duplicate, billing_invoice, billing_refund_review and billing_needs_info give you a view per outcome.

For subscription questions such as plan changes and proration, see handling subscription billing tickets with a Stripe-connected agent, and for the full Stripe tool list, what Macha's Stripe integration does.

Frequently asked questions

Does Zendesk have a native Stripe integration? Yes, but not a sidebar. Since June 23, 2026, action flows have a Stripe connector built by Zendesk, on Suite Growth and up or Support Team and up. On our sandbox it listed 13 actions for customers, invoices, subscriptions and disputes, with no refund. The sidebar apps on the Marketplace are all built by third parties.

Can Zendesk refund a Stripe payment automatically? Not with a prebuilt step. The action flows connector we saw had no refund action, so an automatic refund needs a custom action calling Stripe's refund API, or a third-party AI agent with a Stripe refund tool. The Marketplace apps refund, but an agent clicks.

Is there a free Stripe app for Zendesk? Stripe by Canadesk is free and was listed on September 30, 2026. ChargeDesk is free to install, but its plans start at $29 a month, and Zenplates offers a 7-day trial before $4.95 per agent a month.

Can an AI agent issue a partial Stripe refund from Zendesk? Stripe's refund API takes an amount, so yes, if the tool passes one. Macha's Stripe Create Refund refunds in full or for a partial amount, and eesel lists Create refund. Whether partial refunds should be automatic is a policy choice; in our test instruction they go to a person.

What does automating Stripe billing tickets cost per ticket? It depends on the unit. Zendesk AI agents charge $1.50 per automated resolution committed after the included allowance; Fini charges $0.89 per resolved ticket on Growth; eesel works out to $0.60 a ticket at 500; Macha is about $0.40 per ticket, counted on every ticket it handles, including setup.

Which option is best for a small team? Stripe's customer portal plus a sidebar app, if an agent reads every billing ticket anyway. If you'd rather have the tickets handled and not build anything, Macha's team sets it up for you on the trial: $50 of free usage (about 125 tickets), no credit card, no time limit.

How we researched this

• Read on October 8, 2026: the Zendesk Marketplace search for "stripe" (54 results, three pages) and the listings for Stripe by Zenplates, Stripe Connector by eOne Solutions, Stripe by Canadesk and ChargeDesk, including prices, install counts and reviews; the Stripe connector listing for action flows; Zendesk help articles on the June 23, 2026 connector announcement, connecting external systems, the action flow steps and actions reference, and action credits; Stripe's refund and customer portal docs; the pricing pages of ChargeDesk, eesel, Fini and My AskAI; eesel's Stripe docs and Fini's integrations page. Zendesk's plan prices (zendesk.com/pricing) and Zapier's Stripe actions were checked the same day for our refunds guide.
• Captured on October 8, 2026: the action flow builder's Stripe step list on our d3v-macha sandbox. We didn't connect the Stripe connector or save the flow.
• Run live on October 8, 2026: a test agent on our Macha Demo org with six read-only Stripe tools and three Zendesk tools, on made-up d3v-macha ticket #1211 (Test run), and two Try it chat messages with a made-up payment ID. Macha Demo's Stripe account is live, so no Stripe write tool was attached or called, and every Stripe lookup used a made-up email or ID that returned nothing. The only writes were internal notes and tags on sandbox tickets. All requesters are made up.
• Not run: the four Marketplace apps, Zapier, eesel, Fini and My AskAI. Their capabilities come from their own pages.
• Arithmetic: 8 agents × $4.95 = $39.60 a month for Zenplates. 5 agents × 10 included resolutions on Professional = 50; 300 − 50 = 250 extra; 250 × $1.50 = $375, 250 × $2.00 = $500. $299 ÷ 750 = $0.40 a ticket on Macha; $299 ÷ 500 = $0.60 on eesel.

To have duplicate-charge and invoice tickets handled on your own Zendesk, start a Macha trial and the team will connect Stripe and build the billing agent with you, or see how Macha works on Zendesk and the Zendesk AI automation hub.