What Square data does Well pull into Ramp?

Square streams card payments, invoices, refunds, customers, payouts, disputes, and inventory adjustments to Well over its MCP server. After Well resolves the counterparty and assigns a confidence score, the matched record posts to Ramp as draft bills via email-in at the @ap.ramp.com address, with invoice number, vendor, payment details, and line items pre-filled by Ramp's OCR, with the Square event ID preserved on the entry for audit.

Will every Square record post to Ramp automatically?

Not always. Within seconds of Square firing the event, Well scores the record on field completeness, counterparty strength, and policy fit. Above the 85% default auto-link threshold Well forwards the reconciled document to your Ramp email-in address and Ramp drafts the record from it for you to confirm. Between 55% and 85% the record waits in the review queue with the alternative matches ranked. Below the 55% default review threshold the record is refused and the candidate list kept so you can pin the right entry by hand.

What happens to historical Square data when I first connect to Ramp?

Square exposes the last two years through its API on a connected account. The window Well actually pulls is configurable from the integration settings page; each record is matched against your existing Ramp ledger, and re-running the backfill is safe because Well tracks the Square record IDs and updates existing Ramp entries instead of duplicating them.

Does Well handle multi-currency records between Square and Ramp?

Square carries the original transaction currency on every record, but Ramp ledgers in a single base; Well preserves the source currency, attaches the FX rate at the timestamp of the event, and the converted figure and the source amount both travel on the document Well forwards to Ramp, so both sides of the trade are visible when you post.

How does Well prevent duplicates when posting Square records to Ramp?

Square sends each event with a stable resource ID that Well tracks against the Ramp ledger. Webhook replays (which Square can issue for delivery retries) are recognised by ID and either skipped or used to update the existing Ramp entry. Distinct records that look similar are caught by Well before posting, with the candidates surfaced in the review queue when confidence is ambiguous.

How does Well authenticate with Square and Ramp?

Square's MCP server handles authorisation directly; Well receives an access token through Dynamic Client Registration and never sees raw user credentials. For the delivery side, Well forwards the reconciled document to your Ramp email-in address once it clears the matching threshold; Ramp creates the draft record from it and you confirm and post it. Well holds no write credential to Ramp. Tokens are encrypted at rest and in transit under TLS 1.3. Square and Ramp together cover multiple regions; Well's storage region is configured per workspace.

Square to Ramp

AvailableNative · SquareNative · Ramp

Connect Square to Ramp with Well

When the Square payout hits Ramp, Well already knows which charges it covers; the deposit lands with the gross-net-fee split pre-computed and the FX captured at settlement.

Connect both toolsView all integrations

Square

Source

The Square connection reads your Square account through the Square MCP server using OAuth.

Ramp

Target

The Ramp integration connects your corporate card and expense management platform to Well.

Why this pair

Connect Square to Ramp through Well so records flow without manual rework.

What Well does between Square and Ramp

One-way: Square into Well into Ramp
Sync mode: Real-time MCP push
Events arrive in seconds

Trigger from Square

7 events · pick one

Well engine·recipe·When a Square card payment is captured

Source

from payment · live webhook

Tessellate Design

via Square

Payment

When a Square card payment is captured

ch_1q5nk · 22 Apr 2026€1,284.00

Extract

6 fields read from Square

6 fields read

CustomerTessellate Design
Charge date22 Apr 2026
Charge amount€1,284.00
CurrencyEUR
Processing fee€37.24

Enrich

against your historical record graph

4 fields added

Customer recordTessellate Design
Domaintessellate.studio
Tax idGB432109876
Sales journalVE · 2026

Confidence97%

<55% refused55–85% review≥85% auto-posts

Post

reconcile as draft bills

Create a draft bill in Ramp Bill Pay

auto-posted

posted

TypeBill
VendorTessellate Design
Amount€1,284.00
LedgerVE · 2026
Source docattached
Confidence97%

audit linkto Ramp

Action in Ramp

1 compatible with this trigger

Create a draft bill in Ramp Bill Pay

Workflows Square and Ramp unlock together.

01Featured

Reconcile a card payout against the bank deposit

Square payouts are matched to the inbound Ramp deposit by amount, date, and currency. Once the deposit lands, the linked payout collapses onto the right bank line and the fee delta is split onto a separate Ramp record so the bank statement and the processor settlement agree to the cent.

Detect failed transfers before they hit the GL

When a Square payout is reversed (chargeback chain, NSF, fraud claim), Well watches the matching Ramp bank line for the reversal. The two events are paired in Well so the next reconciliation pass treats them as a single net-zero event rather than two competing entries.

Track multi-currency settlements

Square payouts in non-base currencies are converted at settlement and Well stores the FX rate alongside the Ramp deposit. The conversion delta is tagged for review so finance can compare the processor's FX against the bank's mid-market rate and challenge any divergence.

13 signals and actions across Square and Ramp

When a Square invoice is paid
Detects paid Square invoices with line items, applied discounts, and tax breakdown.
Trigger·Invoice
When a customer is created in Square
Pulls new customer records with name, email, and stored payment methods.
Trigger·Company
When a Square dispute is opened
Captures chargebacks with the contested payment and reason code.
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 card payment is captured
Captures successful card-present and card-not-present payments with currency, fees, and customer linkage.
Trigger·Transaction
When a Square refund is issued
Captures partial and full refunds with the originating payment id.
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 payout is sent to your bank
Detects the moment Square dispatches a payout batch toward your bank account.
Trigger·Transaction
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

Reference

Field mapping for Square → Ramp

8 fields across 2 record types, open to see the full table.

Transaction fields

5 fields flow from Square into Ramp.

Square field	Label		Ramp field	Label
payment.amount_money.amount	Payment amount	→	transaction.amount	Transaction amount
payment.amount_money.currency	Currency	→	transaction.currency_code	Currency
payment.created_at	Charge date	→	transaction.user_transaction_time	Transaction time
payment.note	Description	→	transaction.merchant_name	Merchant
payment.id	Charge id	→	transaction.id	Ramp transaction id

Invoice fields

3 fields flow from Square into Ramp.

Square field	Label		Ramp field	Label
invoice.invoice_number	Invoice number	→	matched_record.reference	Reference
invoice.total_money.currency	Currency	→	matched_record.currency	Currency
invoice.primary_recipient.customer_id	Customer	→	matched_record.id	Source id

Connect Square and Ramp in three steps.

1
Connect Square
Click Connect with Square; Square's MCP server registers a Well client automatically. Square's MCP server registers a read-scoped Well client through DCR; no credential paste, no shared secret.
- AuthOAuth 2.0
2
Map your accounts
Well discovers Square's card payments, invoices, refunds, customers, payouts, disputes, and inventory adjustments and the the Ramp Bill Pay drafts queue awaiting approval. Payouts are anchored to the matching bank deposit with the fee split into its own ledger line, so reconciliation shows gross revenue and processor fees separately.
- Auto-post above85% confidence
- Overridemanual anytime
3
Connect Ramp
Click Connect with Ramp; the Ramp MCP server registers a Well client automatically. Ramp's MCP server registers a write-scoped Well client through DCR; no credential paste, no shared secret.
- AuthOAuth 2.0
- First sync~30 min

How Square and Ramp stay secure with Well

Well connects to Square through its MCP server, which issues short-lived access tokens via Dynamic Client Registration. Well never holds a long-lived Square secret; the server refreshes its own tokens on each session. Well's storage region is configured per workspace regardless of where Square and Ramp host theirs.

MCP server authStorage region per workspaceGDPR-aligned

Scopes Well requestsmcp.squareup.com/sse

Read Square records
Scoped to card payments, invoices, refunds, customers, and related records. No access to anything else in your Square account.
granted
Deliver documents to your Ramp inbox
Well forwards the extracted document to your Ramp email-in address; Ramp reads draft bills via email-in at the @ap.ramp.com address, with invoice number, vendor, payment details, and related records from it and you review and post. No write credential to Ramp is requested.
granted
Modify or delete Square records
Not granted. Square is read-only on Well's side; the source of truth never moves.
refused
Read other workspaces' data
Encryption keys are per-workspace; another tenant's records are inaccessible by design.
refused

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

Frequently asked questions about Square and Ramp on Well

01What Square data does Well pull into Ramp?: Square streams card payments, invoices, refunds, customers, payouts, disputes, and inventory adjustments to Well over its MCP server. After Well resolves the counterparty and assigns a confidence score, the matched record posts to Ramp as draft bills via email-in at the @ap.ramp.com address, with invoice number, vendor, payment details, and line items pre-filled by Ramp's OCR, with the Square event ID preserved on the entry for audit.
02Will every Square record post to Ramp automatically?: Not always. Within seconds of Square firing the event, Well scores the record on field completeness, counterparty strength, and policy fit. Above the 85% default auto-link threshold Well forwards the reconciled document to your Ramp email-in address and Ramp drafts the record from it for you to confirm. Between 55% and 85% the record waits in the review queue with the alternative matches ranked. Below the 55% default review threshold the record is refused and the candidate list kept so you can pin the right entry by hand.
03What happens to historical Square data when I first connect to Ramp?: Square exposes the last two years through its API on a connected account. The window Well actually pulls is configurable from the integration settings page; each record is matched against your existing Ramp ledger, and re-running the backfill is safe because Well tracks the Square record IDs and updates existing Ramp entries instead of duplicating them.
04Does Well handle multi-currency records between Square and Ramp?: Square carries the original transaction currency on every record, but Ramp ledgers in a single base; Well preserves the source currency, attaches the FX rate at the timestamp of the event, and the converted figure and the source amount both travel on the document Well forwards to Ramp, so both sides of the trade are visible when you post.
05How does Well prevent duplicates when posting Square records to Ramp?: Square sends each event with a stable resource ID that Well tracks against the Ramp ledger. Webhook replays (which Square can issue for delivery retries) are recognised by ID and either skipped or used to update the existing Ramp entry. Distinct records that look similar are caught by Well before posting, with the candidates surfaced in the review queue when confidence is ambiguous.
06How does Well authenticate with Square and Ramp?: Square's MCP server handles authorisation directly; Well receives an access token through Dynamic Client Registration and never sees raw user credentials. For the delivery side, Well forwards the reconciled document to your Ramp email-in address once it clears the matching threshold; Ramp creates the draft record from it and you confirm and post it. Well holds no write credential to Ramp. Tokens are encrypted at rest and in transit under TLS 1.3. Square and Ramp together cover multiple regions; Well's storage region is configured per workspace.