Match the right transaction
Use your backend to associate a customer with an order or payment reference. An email address alone is not proof of ownership.
Integrations Square
SquarePlanned
SquarePlannedResolve the question behind the payment.
Plan your Square integration with Message. Design a read-only Square support workflow around a verified transaction. Keep payment controls with the people who are authorized to use them.
Native connector planned. No native Square connector is currently listed in Message settings. This guide describes a custom implementation, not an installed payment integration.
Payments
What we’re planning to connect.
- 01Square
- 02Your verified lookup
- 03Authorized support
Return only what helps
Prepare a narrow response with status, date and a reference. Avoid sending full payment records into chat or AI knowledge.
Keep money movement separate
An agent can review a payment question while refunds, charges and disputes remain in the provider’s authorized workflow.
The right context
Be precise about what connects.
Define the data, permissions and destination before putting the workflow in front of customers.
Lookup context
A custom service must verify ownership before returning transaction status.
Private data
Payment details are not reusable public knowledge and should not be bulk indexed.
Money movement
No native Square refunds, charges or subscription edits are provided by this page.
Prepare for the connection
Define your first workflow.
- 01
Define the lookup
Decide which transaction status fields your support team needs and how your system proves customer ownership.
- 02
Implement a narrow service
Use the provider API behind your server. Do not put payment credentials in a widget or knowledge article.
- 03
Validate before connecting
Test a correct identity, mismatched identity and missing transaction. Confirm the Message integration approach with your developer.