Handle Bonsai refund requests with Stripe
Bring the client request and payment record together so an authorized refund can be processed with fewer lookup steps.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Action
Create Refund
Creates a full or partial refund in stripe, targeting either a specific charge id or a payment intent id.
Why this helps
Refund requests can stall while someone searches for the right Stripe payment and checks what the client asked for.
- Reduce time spent locating the related payment.
- Preserve the requested refund scope when it is clear.
- Flag ambiguous or unmatched requests for a person to review.
Setup
Build it in a few focused steps.
- 1Connect Bonsai and Stripe once in the Notis portal.
- 2Create an automation in Automations, New Automation, and give it a clear name.
- 3In one instruction, ask Notis to match the Bonsai refund request to available Stripe payment data and create a refund only when the payment and authorization are clear.
- 4Choose a webhook trigger and select where run reports should go.
- 5Test with one real, authorized refund example and verify the Stripe refund details.
Questions about this workflow
Can this workflow decide on its own whether a refund is appropriate?
No. The instruction should require clear authorization in the request or supplied context. Unclear cases should be reported for review.
Can it process partial refunds?
The Stripe refund action supports full or partial refunds. The requested amount must be clear from the available information or supplied by the user.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Bonsai to Stripe. A trigger fires from one place; an action lands in another.
Bonsai 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.
Bonsai 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.