Reconcile documented refund requests with Stripe
Give refund paperwork a regular follow-up by checking its payment references against refunds already recorded in Stripe.
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
Refund requests can be overlooked when teams cannot quickly tell whether Stripe already shows a refund.
- Spot requests that may need follow-up.
- Check refunds by charge or payment intent reference.
- Keep the review read-only and report exceptions.
Setup
Build it in a few focused steps.
- 1Connect Affinda and Stripe once in the Notis portal.
- 2Create an automation for scheduled refund reconciliation.
- 3Tell Notis to review processed refund requests, list Stripe refunds for each referenced charge or payment intent, and report requests with no matching refund.
- 4Choose a recurring schedule and a channel for run reports.
- 5Test with one request whose Stripe refund status you can verify.
Questions about this workflow
Does this issue a refund?
No. It lists existing refunds for comparison and reports the result.
What references are useful?
A charge ID or payment intent ID lets the workflow look for related refunds.
What if the request is missing a payment reference?
Ask Notis to flag it as needing manual review rather than searching with incomplete information.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Affinda to Stripe. A trigger fires from one place; an action lands in another.
Affinda 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.
Affinda 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.