Process Byteforms refund requests in Stripe
Give refund requests a clear path from the form to the Stripe transaction they concern.
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 get buried between form responses, internal review, and the Stripe dashboard.
- Keep refund requests connected to their payment context.
- Reduce the chance that an approved request is forgotten.
- Use your instruction to define when a request is ready for processing.
Setup
Build it in a few focused steps.
- 1Connect Byteforms and Stripe once in the Notis portal.
- 2Create an automation in Automations, or tell Notis the outcome in plain language from any channel.
- 3In one instruction, ask Notis to create a Stripe refund for qualifying requests that include a valid charge or payment intent identifier and refund amount where needed.
- 4Pick the webhook trigger and choose where run reports go.
- 5Test with one real example and verify the refund details in Stripe.
Questions about this workflow
Can the form request a partial refund?
Yes. Ask Notis to use the requested amount when it is present and valid. A full refund can be requested without an amount, depending on the Stripe action inputs.
What payment information is needed?
The refund must target a Stripe charge or payment intent. The form submission needs to identify the relevant transaction, or your instruction must describe a reliable way to retrieve it.
Can the automation include a human approval step?
Describe the approval signal in your instruction and ensure it is present in the Byteforms submission before asking Notis to create a refund.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Byteforms to Stripe. A trigger fires from one place; an action lands in another.
Byteforms 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.
Byteforms 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.