What Stripe sends — and what ReviewNudger requires
The integration starts from a specific provider event, then resolves only the payment and customer facts listed here.
Accepted provider event
payment_intent.succeeded
ReviewNudger listens for a successful PaymentIntent on the connected Stripe account. It proceeds only when amount_received is present and a customer can be resolved from the payment facts.
A received amount
The PaymentIntent must include amount_received. A success event without a usable amount fails visibly instead of creating an incomplete request.
A reachable customer
ReviewNudger checks the attached Stripe Customer first, then the latest charge's billing details, then the receipt email. At least one usable email address or phone number is required.
A usable sending route
The location must have automation enabled, and the customer must pass cooldown, do-not-contact, and channel opt-out checks.
See the connection and its latest event
The connected-apps view shows whether Stripe is connected, whether ReviewNudger has received an event, and whether that event was processed or needs attention.
Illustrative product walkthrough using fictional Summit Plumbing data — not a customer case study.
From paid event to request, every step stays visible
The request journey records the trigger, initial delivery, follow-ups, stops, and outcomes in one timeline.
- 1Connect your Stripe account to ReviewNudger with a secure OAuth authorization. You never paste API keys, and you can revoke access from Stripe at any time.
- 2When a payment succeeds in Stripe, ReviewNudger receives the event, matches or creates the customer from the billing details, and applies your sending rules. It can then send one neutral Google review request by SMS or email.
- 3Every send is tracked: you can see delivery status, opt-outs, and whether the customer clicked through to your Google review page, all from one dashboard.
Illustrative product walkthrough using fictional Summit Plumbing data — not a customer case study.
What happens when the clean path is not available
Skipped and failed events are recorded with a reason. Nothing silently guesses a customer or sends around an opt-out.
Retries collapse onto one journey
Provider retries and repeated updates reuse the same provider payment identity. They cannot create a second ReviewNudger review-request journey.
Missing facts fail visibly
ReviewNudger requires the provider's amount and customer contact facts. If either is missing, the incoming event records the failure and no customer is guessed.
Sending rules can suppress the request
Disabled automation, an active cooldown, do-not-contact state, or an opt-out on the usable channel suppresses the request with a visible reason.
Refunds do not create or rewind journeys
Refund and reversal events do not create another request. They also do not automatically cancel a journey that already exists; an operator can cancel a queued request or stop later follow-ups.
Contact resolution has a fixed order
Customer contact details win over latest-charge billing details. The charge receipt email is the final email-only fallback; ReviewNudger does not invent or merge unidentified customers.
A later refund is not a second trigger
Refund and reversal events do not create another request and do not automatically cancel an already-created journey. An operator can cancel a queued request or stop its later follow-ups.
Email can carry the first request while SMS waits
A newly registered SMS number must be approved before it can send customer messages. ReviewNudger never sends from a number that is still pending.
Use email when it is allowed and usable
If the customer has email, the location has email enabled, and the required business address is configured, email carries the initial request while SMS is under carrier review.
Otherwise, keep the event recoverable
If no usable email route exists, the event is visibly suppressed as sms_not_ready. After SMS approval, an operator can recover it from recent events instead of asking the provider to send it again.
Connect Stripe and prove the trigger end to end
Have these provider and ReviewNudger details ready before you connect.
Before you start
- A Stripe account and permission to approve the secure OAuth connection.
- Customer email or phone captured on the Stripe Customer or payment details.
- A completed ReviewNudger location with its Google review destination and sending channels configured.
- 1Start a ReviewNudger trial and finish the short signup.
- 2Choose Stripe as your payment trigger and approve the OAuth connection.
- 3Take a real payment in Stripe to confirm the trigger end to end.
- 4Done. Each successful payment can now start one automatic review request under your sending rules.
Stripe integration questions
Do I need a Zapier account to connect Stripe?
No. The Stripe integration is native: you connect it directly inside ReviewNudger, with no middleware account, no per-task automation fees, and no field mapping to maintain.
What exactly triggers a review request?
Each time a payment succeeds in Stripe, ReviewNudger records the event and evaluates it against your per-location send delay, cooldown, contact, and channel rules. One matching event can create one review-request journey by SMS or email.
Can a retry or duplicate webhook double-text a customer?
No. Every incoming event is deduplicated before any message is sent, and each event can create at most one review request. Provider retries and replays collapse onto the same request instead of sending twice.
What about customers who opt out?
SMS recipients can reply STOP at any time and email recipients can unsubscribe. Opt-outs are recorded per customer and honored across every future Stripe-triggered event.
Where does ReviewNudger get Stripe contact details?
ReviewNudger checks the attached Stripe Customer first, then the latest charge's billing details, and finally the receipt email. The event needs at least one usable email address or phone number; otherwise it fails visibly without guessing a customer.
Questions before you start? Email support@reviewnudger.com and a human will answer.