What exactly triggers the Square integration?
Square payment.updated with payment status COMPLETED.
Square direct integration
Send Google review follow-up after a completed Square payment.
Queue a fair Google review request only after Square reports that the customer payment is complete. This is a signed provider webhook with explicit setup and testing, not a one-click marketplace install.
Square sellers that collect customer email addresses and want a review request handoff after a completed payment, without another front-desk entry step.
Exact accepted Square trigger
Square must confirm a completed payment
ReviewsRelay accepts payment.updated only when the payment status is COMPLETED and a linked customer passes email preference checks. A completed payment may be a deposit or prepayment: use a completed-appointment bridge if you charge before the visit.
Square direct uses a private signed webhook. It is not a one-click Square App Marketplace install: someone with access to the Square Developer Dashboard must create the subscription and provide the minimum credentials shown in ReviewsRelay.
Required customer handoff
- A stable Square payment event ID
- A customer name
- A customer email address resolved from the linked Square customer
- The completed payment timestamp
Automatically ignored
- Payments that are not COMPLETED
- Duplicate event IDs
- Customers without a usable email address
- Provider-level email opt-outs
- Customers contacted within the previous 90 days
Provider-specific setup
Connect Square, prove one event, then enable live intake
- Create your private link
Create an inactive ReviewsRelay link first. No keys are needed and customer intake stays paused.
- Register the webhook in your provider
Paste the private ReviewsRelay Square URL into your Square webhook subscription. Subscribe to payment.updated and customer.updated. Only COMPLETED payments with a linked customer can add requests; customer email opt-outs stop queued follow-ups. Keep native webhook payloads unchanged so signatures can be verified.
- Save the required credentials
Open the saved Square subscription to copy its signature key. Save that key and a customer-read access token in ReviewsRelay; both are required to verify customer identity and email preferences.
- Verify a completed event while paused
Send a completed event using your own contact and customer record, then select Check test. Confirm the earliest send time before enabling intake. ReviewsRelay verifies the signature, customer lookup and eligibility without creating a request or contacting anyone.
- Enable customer intake
After the test passes, enable intake explicitly. New eligible events enter the queue; sending follows your request settings. Keep cancellations and opt-out events subscribed when intake is paused.
Go-live checks
Confirm the provider evidence, customer data, and duplicate behavior
- The delivery type is payment.updated
- The payment status is COMPLETED
- The signature matches the exact notification URL and body
- The customer has a usable name and email
- Repeating the same payment does not create a second queue item
Operational controls
- Signed webhook verification is required
- A customer-read access token is required for identity and email opt-out checks
- Sandbox events use Square sandbox APIs
- The connection can be tested, paused, rotated, or disconnected in ReviewsRelay
Square Webhooks documentation is the official provider source for the webhook contract.
- Compare all connection pathsDirect providers, Zapier, Make, secure webhooks, CSV, and manual entry
- Preview the downstream workflowSee what happens after an eligible customer reaches ReviewsRelay
Practical outcomes
- Trigger from a completed payment
- Resolve the Square customer safely
- Keep non-completed payments out
- Test in sandbox before production
Workflow
- Create your private link
- Register the webhook in your provider
- Save the required credentials
- Verify a completed event while paused
- Enable customer intake
Safety guardrails
- Signed webhook verification before payload processing
- Payments that are not COMPLETED
- Duplicate event IDs
- Customers without a usable email address
- Provider-level email opt-outs
Frequently asked questions
What customer data does ReviewsRelay need from Square?
A stable Square payment event ID. A customer name. A customer email address resolved from the linked Square customer. The completed payment timestamp.
Which Square events are ignored?
Payments that are not COMPLETED. Duplicate event IDs. Customers without a usable email address. Provider-level email opt-outs. Customers contacted within the previous 90 days.
Is the Square connection a one-click install?
Square direct uses a private signed webhook. It is not a one-click Square App Marketplace install: someone with access to the Square Developer Dashboard must create the subscription and provide the minimum credentials shown in ReviewsRelay.
Can I test the Square connection before enabling it?
Yes. Use contact details you control and verify these checks: The delivery type is payment.updated; The payment status is COMPLETED; The signature matches the exact notification URL and body; The customer has a usable name and email; Repeating the same payment does not create a second queue item.
Does ReviewsRelay need my Square password?
No. ReviewsRelay never asks for your Square sign-in password. The direct connection uses a private signed webhook and the minimum configured credentials needed for customer lookup.
Related review automation pages
- IntegrationsReview request automation
- VagaroVagaro Google review request automation
- MindbodyMindbody Google review request automation
- SafetySafe Google review automation
- Free toolsFree Google review tools
- Profile auditGoogle Business Profile audit tool