Apply payment intent corrections in Stripe
Handle payment intent corrections with a clear instruction and a report when Stripe may require customer reconfirmation.
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
Correcting transaction details across billing tools takes focus and can create customer friction if a change is missed.
- Reduce manual transaction edits
- Make reconfirmation risks visible
- Keep unclear corrections for review
Setup
Build it in a few focused steps.
- 1Connect Billsby and Stripe once in Notis.
- 2Create an automation and describe the allowed correction details and when to report instead of updating.
- 3Pick the webhook trigger and choose where run reports go.
- 4Test with one real correction request and inspect the Stripe intent.
Questions about this workflow
Can changing an intent require customer action?
Yes. Some updates, such as changing the payment method, can require the customer to confirm again.
What if the currency changes?
An amount may also be required when currency is updated. Include both values in the request or have Notis report it for review.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Billsby to Stripe. A trigger fires from one place; an action lands in another.
Billsby 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.
Billsby 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.