Square, ready to run.
The Square integration runs the refunds and disputes your team keeps handling by hand. Floowed reads the payment, the order and the customer behind it, applies your rules, and acts where they allow it.
What it does.
What Floowed reads from Square
- Payments, and the orders behind them
- Customers, with their history assembled from payments and orders
- Refunds and disputes
- Catalog items, where a rule depends on what was sold
What it writes back
- A refund, where the rules allow one
- Customer custom attributes recording the outcome
- Dispute evidence, where the case is a chargeback
- The decision and its reasoning, wherever your team actually reads it
One Square limitation worth knowing up front. Orders made in the Square Point of Sale app cannot be updated through the API: Square only allows updates to orders created with the Orders API. So the decision is recorded against the customer and in the system your team works in, rather than on the point-of-sale order.
A refund request for a damaged delivery, from ticket to refund.
- Gather
A customer opens a ticket in Zendesk about a damaged delivery. Floowed opens a case and pulls the payment, the order and the customer's history from Square.
- Interpret
Floowed reads the customer's photos and the delivery record from ShipStation, and matches the damaged items to the order lines.
- Chase
If the photos are missing, the customer is asked through the ticket. The store manager is asked in Slack or the Floowed Dashboard whether the item can be resold.
- Decide
Your refund rules run in the deterministic policy engine: full refund, partial refund or replacement. A case that does not fit them goes to the customer service lead to decide.
- Act
Floowed refunds the payment in Square, records the outcome in a custom attribute on the customer and replies on the Zendesk ticket.
Used in the same case
The connection, in detail.
How it connects.
- 1
Connect Square
Using OAuth 2.0 authorization code flow (PKCE supported); access tokens expire after 30 days and are refreshed. Nothing migrates and nothing is replaced.
- 2
Build your operation
Describe it in Slack, Teams or the Floowed Dashboard. Floowed builds it and asks only what it can’t work out.
- 3
Let it run
Every case runs from request to outcome, the same way each time, with the reasons on record. Anything sensitive waits for a person.
Questions
Does Floowed integrate with Square?
Yes. The Square integration connects over OAuth 2.0 across payments, orders, customers, refunds and disputes.
How does the Square integration connect?
Through Square's OAuth 2.0 sign-in against your seller account, with only the permissions you approve. Access tokens last 30 days and are refreshed automatically.
What can Floowed do with Square data?
A refund is a decision: what was bought, what the customer has done before, and what your policy says. Floowed reads all of it, decides, and refunds the payment or responds to a dispute where the rules allow.
Do I need to build anything to use it?
No. Describe the operation in the Floowed Dashboard, Slack or Microsoft Teams, connect Square, and set your rules and the point at which a person still decides.
Is my Square data secure?
Permissions are approved at sign-in and can be revoked from Square at any time. Card details stay with Square; we work from the objects its API exposes. Every case keeps a full record of what was read, decided and written.
What does the Square integration cost?
Nothing extra. Integrations are included, and you pay for the work Floowed does on a case. Start free with $80 of credits, no card and no sales call.
Start with Square. Add the rest.
Free to try, no card, no sales call. Your first $80 of credits is on us.