Skip to content
Notis

Log Custom Payment Events in Jira via Webhook

If you have a custom billing system alongside Stripe, events get lost in sync. Notis accepts webhook calls from your system and logs them as comments in Jira.

Trigger

Webhook received

Notis starts this workflow when an external tool or custom backend sends an HTTP request.

Action

Add Comment

Adds a comment using atlassian document format (adf) for rich text to an existing jira issue.

Why this helps

You use Stripe plus a legacy billing system or custom processor. Events sync imperfectly and you manually update Jira or accept inconsistent records.

  • All payment events (Stripe + custom systems) end up in one Jira issue
  • No manual copying or reconciliation—Notis captures everything automatically
  • Audit trail is complete and searchable in Jira

Setup

Build it in a few focused steps.

  • 1Connect Jira to Notis.
  • 2Tell Notis: 'Accept incoming webhooks from my billing system and add each event as a comment to the Revenue Tracking issue in Jira.'
  • 3Notis will provide you a webhook URL. Add it to your billing system's outgoing webhooks.
  • 4Test by sending a sample payment event from your system and confirming the comment appears in Jira.
  • 5Monitor the webhook logs in Notis to catch any delivery failures.

Questions about this workflow

What format should the webhook payload be in?

JSON is standard. Notis parses common payment fields (amount, date, customer, status). Tell us your payload format and we'll map it.

Can we filter which webhooks create issues vs. just comments?

Yes—tell Notis to create a new Jira issue for certain event types (e.g., refunds) and just comment on the main issue for routine payments.

What if the webhook fails to reach Jira?

Notis queues failed deliveries and retries. You'll see failed webhooks in the Notis dashboard and can manually replay them.

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

TriggerInstant

Add Attachment

Uploads and attaches a file to a jira issue.

ActionInstant

Checkout Session Completed Trigger

Triggered when a checkout session is completed in Stripe

TriggerInstant

Add Comment

Adds a comment using atlassian document format (adf) for rich text to an existing jira issue.

ActionInstant

Invoice Payment Succeeded Trigger

Triggered when an invoice payment is successful in Stripe

TriggerInstant

Add Watcher to Issue

Adds a user to an issue's watcher list by account id.

ActionInstant

Payment Intent Failed Trigger

Triggered when a payment intent fails in Stripe

TriggerInstant

Assign Issue

Assigns a jira issue to a user, default assignee, or unassigns; supports email/name lookup.

ActionInstant

Product Created Trigger

Triggered when a product is created in Stripe

TriggerInstant

Bulk Create Issues

Creates multiple jira issues (up to 50 per call) with full feature support including markdown, assignee resolution, and priority handling.

ActionInstant

Subscription Added Trigger

Triggered when a subscription is added in Stripe

TriggerInstant

Create Issue

Creates a new jira issue (e.g., bug, task, story) in a specified project.

ActionInstant

Subscription Deleted Trigger

Triggered when a subscription is deleted in Stripe

TriggerInstant

Link Issues

Links two jira issues using a specified link type with optional comment.

ActionInstant

Create Project

Creates a new jira project with required lead, template, and type configuration.

ActionInstant

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.