Update a payment intent after reviewing an order change
Bring order change research into the payment follow-up and update only the intent details you have approved.
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
Order changes can leave a payment intent out of date while the team searches for the right details and context.
- Review order change details before changing payment intent data.
- Update only the fields your instruction authorizes.
- Flag updates that may require customer reconfirmation.
Setup
Build it in a few focused steps.
- 1Connect Bright Data MCP and Stripe once in Notis.
- 2Create an automation in the portal or tell Notis what to do in plain language.
- 3In one instruction, identify the payment intent, the order change to verify, and the exact fields and conditions for an update.
- 4Choose a webhook trigger and select where run reports should go.
- 5Test with one real example and inspect the resulting payment intent.
Questions about this workflow
Could an update require the customer to confirm again?
Yes. Some changes, such as changing the payment method, can require customer re-confirmation. The workflow should report that possibility.
Can it update the payment amount?
The action supports specified updates. If currency changes, amount might also be required. State the intended values and conditions explicitly.
What if the order change is unclear?
Instruct Notis to stop and report uncertainty rather than update the payment intent.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Bright Data MCP to Stripe. A trigger fires from one place; an action lands in another.
Bright Data MCP 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.
Bright Data MCP 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.