Update Stripe payment intents from Byteforms requests
Give payment correction requests a direct path to the Stripe intent they refer to.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Action
Update Payment Intent
Updates a stripe paymentintent with new values for specified parameters; note that if `currency` is updated, `amount` might also be required, and certain updates (e.g., to `payment method`) can necessitate re-confirmation by the customer.
Why this helps
Payment correction details can get stranded in a form while the corresponding Stripe intent remains unchanged.
- Reduce handoffs for clearly specified payment corrections.
- Keep the request linked to the Stripe payment intent.
- Report invalid or incomplete requests for review.
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 update only the specified fields on the identified Stripe payment intent when the request meets your criteria.
- 4Pick the webhook trigger and choose where run reports go.
- 5Test with one real request and verify the resulting payment intent details in Stripe.
Questions about this workflow
What should the request identify?
Include the Stripe payment intent ID and the exact changes requested. Some updates may require additional information, such as an amount when changing currency.
Can this change a payment method?
The update action supports payment intent updates, but some changes may require customer reconfirmation. State the intended outcome clearly and review the resulting intent.
Can this confirm or charge the payment?
This workflow updates an existing payment intent. Confirming it is a separate action and may require a return URL for redirect-based payment methods.
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.