Review Stripe refunds when a token transfer is reported
Gather refund records around a reported transfer and make uncertain matches clear for a quick human check.
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
Refund and transfer records can be reviewed in isolation, leaving teams to piece together the context manually.
- Starts a refund lookup from a reported token transfer.
- Collects Stripe refund records with the supplied payment context.
- Highlights uncertainty instead of asserting an unsupported match.
Setup
Build it in a few focused steps.
- 1Connect Bitquery and Stripe once in the Notis portal.
- 2Create an automation in Automations, New Automation, and name it.
- 3Tell Notis to retrieve Stripe refunds relevant to the payment context supplied with the Bitquery transfer request and summarize possible matches.
- 4Choose a webhook trigger and select where run reports should go.
- 5Test with one real transfer and refund example, checking that uncertain results are labeled.
Questions about this workflow
Does the transfer automatically identify a Stripe refund?
Not necessarily. A reliable link needs shared identifiers or other matching details in the webhook request or returned records.
Does this workflow issue refunds?
No. It retrieves refund records for review and does not create or change refunds.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Bitquery to Stripe. A trigger fires from one place; an action lands in another.
Bitquery 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.
Bitquery 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.