Track parsed refund requests against Stripe refunds
Make refund follow-up easier with a scheduled report comparing parsed requests with Stripe refund records.
Trigger
Recurring schedule
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
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
A refund request can be acknowledged in a message but still lack a clear follow-up trail in Stripe.
- Keep refund follow-up visible in a recurring report.
- Identify requests without an apparent Stripe refund record.
- Reduce the chance of losing track of refund requests.
Setup
Build it in a few focused steps.
- 1Connect Airparser and Stripe once in the Notis portal.
- 2Create an automation in Automations, New Automation, and give it a clear name.
- 3Tell Notis to compare available parsed refund requests with Stripe refunds and report likely matches and unresolved cases.
- 4Pick a recurring schedule and choose where run reports should go.
- 5Test with one request whose Stripe refund status you can verify.
Questions about this workflow
Does listing a refund prove the original request was handled correctly?
It shows refund records returned by Stripe. The report can identify likely matches, but request details still determine whether the outcome is correct.
Can it create a refund for every unmatched request?
This workflow is for review and reporting. Unmatched requests should be checked before any refund is created.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Airparser to Stripe. A trigger fires from one place; an action lands in another.
Airparser 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.
Airparser 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.