Check whether a payment already has a refund
See the refund history next to a payment incident before deciding on the next customer support step.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Action
List Refunds
Lists stripe refunds, sorted by creation date descending (newest first), with optional filtering by charge or payment intent and pagination support.
Why this helps
Without refund history at hand, teams risk repeating work or giving a customer an incomplete update.
- Check refunds against the payment identifier present in the alert.
- Reduce uncertainty during billing support follow-up.
- Keep the result attached to the incident report.
Setup
Build it in a few focused steps.
- 1Connect Bugsnag and Stripe once in the Notis portal.
- 2Create an automation named Payment Refund History Check.
- 3Tell Notis to list refunds for the charge ID or payment intent ID explicitly present in the alert, and report if neither is available.
- 4Pick the Notis webhook trigger and choose where run reports should go.
- 5Test with one real payment incident that has known refund history.
Questions about this workflow
Will this create a refund?
No. It only lists refunds associated with the supplied payment identifier.
What if an alert includes both a charge and payment intent ID?
Tell Notis which identifier to use according to your incident convention, and have it report the identifier used.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Bugsnag to Stripe. A trigger fires from one place; an action lands in another.
Bugsnag triggers
Stripe actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Cancel subscription
Cancels a customer's active stripe subscription at the end of the current billing period, with options to invoice immediately for metered usage and prorate charges for unused time.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Confirm payment intent
Confirms a stripe paymentintent to finalize a payment; a `return url` is necessary if the payment method requires customer redirection.
Create Customer
Creates a new customer in stripe, required for creating charges or subscriptions; an email is highly recommended for customer communications.
Create an invoice
Creates a new draft stripe invoice for a customer; use to revise an existing invoice, bill for a specific subscription (which must belong to the customer), or apply detailed customizations.
Create payment intent
Creates a stripe paymentintent to initiate and process a customer's payment; using `application fee amount` for a connected account requires the `stripe-account` header.
Create a price
Creates a new stripe price for a product, defining its charges (one-time or recurring) and billing scheme; requires either an existing `product` id or `product data`.
Create product
Creates a new product in stripe, encoding the request as `application/x-www-form-urlencoded` by flattening nested structures.
Create Refund
Creates a full or partial refund in stripe, targeting either a specific charge id or a payment intent id.
Connect any two apps with Notis in the middle.
Bugsnag and Stripe, or any other combination from 1,000+ integrations.
When this happens · Trigger
Do this · Action
Save your first hour today.
7-day trial of any paid plan, with 20$ of usage included.
No card. Works with personal or business Stripe.