Update Jira Issues for Recurring Stripe Payment Failures
A customer's payment fails once—create a ticket. It fails again—update the ticket, don't duplicate it. Notis finds the existing issue and updates it, keeping your workflow clean.
Trigger
Payment Intent Failed Trigger
Triggered when a payment intent fails in Stripe
Action
Edit Issue
Updates an existing jira issue with field values and operations. supports direct field parameters (summary, description, assignee, priority, etc.) that are merged with the fields parameter. direct parameters take precedence.
Why this helps
A customer has recurring payment issues and you end up with multiple Jira tickets for the same problem. Notis clogs up and the real issue gets lost.
- One ticket per customer payment problem—no clutter, clear history
- See the full timeline of a customer's payment struggles in one place
- Reduce time spent managing duplicate tickets
Setup
Build it in a few focused steps.
- 1Connect Stripe and Jira to Notis.
- 2Tell Notis: 'When a payment fails in Stripe, search for an existing Jira issue for that customer. If found, update it with the new failure details. If not, create a new issue.'
- 3Notis will append the new failure to the issue's description or add a comment.
- 4Choose your notification channel.
- 5Test by failing a payment twice for the same customer and confirming the issue is updated, not duplicated.
Questions about this workflow
How does Notis know which issue belongs to which customer?
Notis uses the customer email or ID from Stripe to search Jira for an issue with that customer in the title or description.
What if we want to re-assign the issue after a certain number of failures?
Yes—tell Notis to escalate after 3 failures (e.g., 'after 3 failures, change priority to High and assign to premium support').
Can we close the issue if the payment eventually succeeds?
Yes—create a separate automation for successful payments that closes related failed payment issues.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Stripe to Jira. A trigger fires from one place; an action lands in another.
Stripe triggers
Jira actions
Charge Failed Trigger
Triggered when a direct charge fails in Stripe's legacy Charges API
Add Attachment
Uploads and attaches a file to a jira issue.
Checkout Session Completed Trigger
Triggered when a checkout session is completed in Stripe
Add Comment
Adds a comment using atlassian document format (adf) for rich text to an existing jira issue.
Invoice Payment Succeeded Trigger
Triggered when an invoice payment is successful in Stripe
Add Watcher to Issue
Adds a user to an issue's watcher list by account id.
Payment Intent Failed Trigger
Triggered when a payment intent fails in Stripe
Assign Issue
Assigns a jira issue to a user, default assignee, or unassigns; supports email/name lookup.
Product Created Trigger
Triggered when a product is created in Stripe
Bulk Create Issues
Creates multiple jira issues (up to 50 per call) with full feature support including markdown, assignee resolution, and priority handling.
Subscription Added Trigger
Triggered when a subscription is added in Stripe
Create Issue
Creates a new jira issue (e.g., bug, task, story) in a specified project.
Subscription Deleted Trigger
Triggered when a subscription is deleted in Stripe
Link Issues
Links two jira issues using a specified link type with optional comment.
Create Project
Creates a new jira project with required lead, template, and type configuration.
Connect any two apps with Notis in the middle.
Not just Stripe and Jira. Any combination from 1,000+ integrations.
When this happens · Trigger
Do this · Action
Save your first hour today.
7 days free trial with 20$ free usage included.
No card. Works with personal or business Jira.