Keep verified user locations in Stripe
When a verified location arrives, update the corresponding Stripe customer record with the details you provide.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Action
Update Customer
Updates an existing stripe customer, identified by customer id, with only the provided details; unspecified fields remain unchanged.
Why this helps
Verified location information can sit in one system while billing records remain outdated.
- Move verified location details into customer records.
- Reduce manual copying after location checks.
- Keep billing records aligned with supplied user information.
Setup
Build it in a few focused steps.
- 1Connect Addresszen and Stripe once in the Notis portal.
- 2Create an automation and give it a clear name.
- 3Tell Notis to verify the submitted user location and update the corresponding Stripe customer with provided address details only after a successful check.
- 4Choose a webhook trigger and select where run reports should go.
- 5Test with one real verified location and customer record.
Questions about this workflow
How should the matching Stripe customer be identified?
Include a valid Stripe customer ID or another reliable identifier that Notis can use to find the correct record.
Will the workflow sync fields other than the address?
Tell Notis exactly which provided customer details to update. Unspecified fields remain unchanged.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Addresszen to Stripe. A trigger fires from one place; an action lands in another.
Addresszen 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.
Addresszen 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.