When a Square card payment is captured
Captures successful card-present and card-not-present payments with currency, fees, and customer linkage.
Trigger·Transaction
Connect Square to 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.
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 invoice is paid
Detects paid Square invoices with line items, applied discounts, and tax breakdown.
Trigger·InvoiceWhen a Square refund is issued
Captures partial and full refunds with the originating payment id.
Trigger·TransactionWhen a customer is created in Square
Pulls new customer records with name, email, and stored payment methods.
Trigger·CompanyWhen a Square payout is sent to your bank
Detects the moment Square dispatches a payout batch toward your bank account.
Trigger·TransactionWhen a Square dispute is opened
Captures chargebacks with the contested payment and reason code.
Trigger·TransactionWhen a Square payment includes a tip
Pulls the tip amount off the payment so it can be routed separately.
Trigger·TransactionWhen a Square order is completed
Captures the completed Square order with its line items, taxes, and the payment that settled it.
Trigger·InvoiceWhen 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 through live reads, backed by a periodic reconciliation pass. 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…
27 agent skills run on Square.
Each one answers a question from live Square data. The required ones return nothing until a source like it is connected.
Needs a source like Square
Chase late invoices
Get a prioritized list of who to chase for payment, with their contact info and a message already drafted.
Rank clients by LTV
Rank your most valuable customers by lifetime value, over a year you name or their whole life.
Customer Dependency
See how much of your revenue rides on a few customers, and what a late or lost one does to your cash.
Company profile
Everything you know about one company, in one view.
Payment and invoice lookup
Find what payment settled an invoice, or catch every payment that never got one.
Missing receipts
Find the bills with no paperwork attached, before an auditor does.
Invoice Compliance
Know which invoices are missing a legal line before your customer or the tax office does.
Recurring revenue
See the monthly run-rate of live subscriptions, or an invoice average when no typed subscriptions are present.
Answers better with Square
Receivables aging
See which customers still owe you money: the unpaid and overdue invoices, how late each is, and the total.
Bills due
See what you owe and when, ordered by due date with a running total.
FX exposure
See how much of your cash and receivables sit outside your reporting currency.
Missing supplier invoices
See which suppliers owe you paperwork, in each of your files, for a month, a quarter or this week.
Missing invoice sweep
Walk the whole month-end sweep in one prompt.
Payables aging
See what you owe your suppliers, and how long each bill has been past due.
Board pack
The board numbers in one pass, each with its scope and its window stated.
Compose a board
The measures you name, arranged on one board that stores the question rather than the answer.
Revenue by customer
See how much each customer billed in a period, ranked by revenue, with the part you could not place named.
Supplier spend register
See what each supplier invoiced you over a year, ranked, with unplaced invoices counted.
Check bank and books
Compare your bank with your books, list the gaps, and re-run what missed rows.
VAT radar
See the VAT position your data suggests for a quarter, and which invoices to fix first.
Money back
Find money owed back to you: refunds, credit notes, VAT credits, double debits, then unpaid customer invoices.
Check contractor status
For each supplier that looks like a freelancer, read the purchase invoices, the payment rail and any contract Well holds, and state the facts a requalification question turns on, next to the papers your country expects you to keep.
Uses Square when it is there
Connects and checks Square
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 policyScopes Well requestsmcp.squareup.com/sse
- granted
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.
- refused
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.
Disconnect any time from Well settings or Square’s admin panel.
Frequently asked questions about Square and Well
What is the connect step for Square, start to finish?
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.
What does Well pull from a Square account?
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.
How does Well make a Square payout reconcile against my bank?
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.
Where do Square's per-transaction fees and tips show up?
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.
How does new Square activity reach Well after the first sync?
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.
What happens to Square records if I disconnect?
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.
Connect Square with
Ready-to-ship workflows that pair Square with another tool through Well.
Freshbooks
Reconcile Square sales, refunds, and customer activity insid…
Bill.com
Reconcile Square supplier-side activity inside Well, forward…
Melio
Route Square purchase activity into Melio for vendor payment…
Pennylane
Reconcile Square sales, refunds, and customer activity insid…
Xero
Reconcile Square sales, refunds, and customer activity insid…
QuickBooks
Reconcile Square sales, refunds, and customer activity insid…
Pairs well with Square
Popular pairs
More in Payments
Popular cross-category
Gmail
Connect Gmail to Well to collect and process invoices from your inbox.
QuickBooks
Connect QuickBooks to Well to sync accounting data and ledger records.
Xero
Connect Xero to Well to sync accounting data and ledger records.
Google Drive
Connect Google Drive to Well to import and export documents and invoices from your cloud storage.
Ready to connect Square?
Connect once. Every order, payout, customer from Square becomes searchable, queryable, and ready for your agents and tables. Disconnect any time.