Integrations · Payments

Connect Square to Well

Name: Square entities in Well
Creator: Well

Read Square card payments, invoices, refunds, tips, and payouts into Well through the Square MCP server. Each payout is broken back into the payments it carries.

Connect SquareSee what Well does

What Well pulls from Square

Square feeds order, payout, customer into Well as a source. The connection is read-only; disconnect at any time from your workspace settings to revoke Square’s access.

From Square	In Well	Relation
Order	Invoice	Becomes
Payout	Bank deposit	Settles into
Customer	Company	Enriches
Refund	Credit note	Becomes

Sync mode: MCP hybrid
Refresh: live + reconciliation reads
Direction: Square → Well

9 triggers from Square.

When a Square card payment is captured
Captures successful card-present and card-not-present payments with currency, fees, and customer linkage.
Trigger·Transaction
When a Square invoice is paid
Detects paid Square invoices with line items, applied discounts, and tax breakdown.
Trigger·Invoice
When a Square refund is issued
Captures partial and full refunds with the originating payment id.
Trigger·Transaction
When a customer is created in Square
Pulls new customer records with name, email, and stored payment methods.
Trigger·Company
When a Square payout is sent to your bank
Detects the moment Square dispatches a payout batch toward your bank account.
Trigger·Transaction
When a Square dispute is opened
Captures chargebacks with the contested payment and reason code.
Trigger·Transaction
When a Square payment includes a tip
Pulls the tip amount off the payment so it can be routed separately.
Trigger·Transaction
When a Square order is completed
Captures the completed Square order with its line items, taxes, and the payment that settled it.
Trigger·Invoice
When a Square customer is updated
Detects changes to a Square customer's name, email, or stored payment method and refreshes the company record.
Trigger·Company

What Well does with your Square connection

Connect

Connect Square over OAuth (MCP DCR): Well registers a client through Square's OAuth Dynamic Client Registration and you approve on Square's side, so the password never reaches Well; Well holds only a scoped token it can refresh.

Sync

Well brings order, payout, and customer in from Square on live events backed by periodic reconciliation reads. The first sync backfills history in the background and the connection stays live after.

Enrich

Well resolves each Square entity into invoice, bank deposit, and company, assigns categories, and links every record to an audit trail across the rest of your connected tools.

Available

Your data from Square lands in the workspace as invoice, bank deposit, and company you can search, chart, and automate.

Questions Square unlocks

Ask in plain language. Well answers from your connected Square connection, resolved against the rest of your stack.

Ask Well

Ask anything about your Square connection

Summarise this month

What needs attention?

Find unmatched records

Ask about your Square connection…

Connect Square in three steps

01
Connect Square over its MCP server
Choose Square in Well's Connections panel and start the connect step. Well reads the Square MCP server's OAuth metadata at mcp.squareup.com, registers through Dynamic Client Registration, and sends you to Square's authorise screen for the read scopes. Approve there and the connection is live without a credential leaving Square.
- AuthOAuth (MCP DCR)
- DiscoveryMCP .well-known
- MCP servermcp.squareup.com/sse
02
Map your entities
Well reads orders, payouts, customers, and refunds and maps them through its data-views layer: orders become invoices, payouts settle into bank deposits, and the link between a paid invoice and the payment that cleared it comes across with them.
- Mappingpreconfigured by Well
03
Use the data
Use it to reconcile a day's takings against the deposit, table refunds by sale, or ask an agent about your effective processing fees. Square is the point-of-sale system of record; Well keeps a read-only, queryable copy beside your other tools.
- First syncstarts as soon as connect completes

The handshake completes in about a minute. Recent sales are read on connect; earlier history fills in afterwards in the background.

How Square stays secure with Well

The Square connection runs over its MCP server at mcp.squareup.com, with OAuth Dynamic Client Registration handling the credential exchange so no Square secret is stored in Well. Scope is limited to the orders, payouts, and customers Square exposes, and tokens renew on Square's side. Reads only: Well never refunds, captures, or edits a Square transaction.

OAuth (MCP DCR)Encrypted at restGDPR compliant

Read the full privacy and security policy

Scopes Well requestsmcp.squareup.com/sse

Read Square records
Resources the Square MCP server exposes, scoped by your OAuth approval.
granted
Resolve order, payout, customer, and refund across your stack
Match identifiers in Square against the same entities your other connected tools expose, so each record carries cross-tool context.
granted
Modify or delete Square records
Not granted; Square is read-only in Well. Write-back is opt-in per connector when a write surface exists.
refused
Store Square passwords or session cookies
Authentication runs through OAuth (MCP DCR) tokens we never see.
refused

Disconnect any time from Well settings or Square’s admin panel.

Frequently asked questions about Square and Well

From Well's Connections panel, find Square and start connecting. Well reads the Square MCP server's OAuth metadata at mcp.squareup.com, registers itself through Dynamic Client Registration, and hands you to Square's own authorise screen for the read scopes. Approve there, return to Well, and the connection is live without a credential ever leaving Square.

Orders, payouts, customers, and refunds arrive as workspace records. An order becomes the invoice it represents, a payout settles into the bank deposit it lands as, a customer enriches the matching company, and a refund turns into a credit note against the original sale. The link between a paid invoice and the payment that settled it comes across too, so the takings tie out to the document.

Square batches a day of card payments into one payout, net of fees and refunds. Well reads the payout together with the individual payments inside it, so when that single deposit shows up in your connected bank account, the breakdown of what it contains is already attached. The deposit matches the day's sales without a manual tie-out, and any refund in the batch is already credited to the sale it reverses.

Each Square payment keeps its fee and any tip alongside the gross amount, so the difference between what a customer paid and what reached your account is visible on the record itself. Questions about your effective Square processing rate, or about tips owed for a period, answer from the workspace because the components were never flattened into a single net figure.

Well reads payments, payouts, and refunds through the Square MCP connection and folds new ones into the workspace as they clear, while the first connect backfills earlier sales in the background. Square stays the point-of-sale system of record; Well keeps a queryable copy so a day's takings sit beside the invoices, deposits, and customers in the rest of your workspace.

Disconnect Square from Well's Connections panel and Well immediately stops reading the Square MCP server and releases its token. Square is read-only in Well, so no posted record needs reversing. The payments, payouts, and customers already brought in stay in your workspace for reporting; Support can purge them if a compliance step requires it.