Square is the default nervous system for small vendors at markets, fairs, and night markets. Coordinators rarely get a single market-wide Square feed because each vendor owns their own Square identity—that is the real architectural constraint.
MoneyLayer treats Square as a first-class connected lane when vendors opt in, and falls back to structured self-report plus evidence for everyone else. This page is the compatibility truth table, not a sales claim.
Connected where possible. Structured self-report where it isn't. Every number carries freshness, coverage, and provenance.
At-a-glance matrix
| Capability | Connected | Self-report |
|---|---|---|
| Vendor-owned Square totals (event window)Depends on vendor connection + correct item/time attribution. | Partial | Square screenshot or CSV export |
| Cash / Venmo / Zelle | No | Structured fields + optional image |
| Tips handling | Partial | Define gross with tips in your market policy. |
Setup
Organizer-side
- Publish gross definition and event window (especially for late closes).
- Invite vendors on Square through the pilot onboarding flow (consent-based).
- Track coverage: connected vs self-report vs missing.
- Review exceptions before publishing stall fees or revenue share.
Vendor-side
- Read the market policy once.
- Connect Square if you opt in; otherwise use the structured submission link.
- If you revise a number, add a one-line reason (disputes drop sharply).
What data we pull
- When connected: structured totals aligned to your published event window (implementation varies by pilot configuration).
- When not connected: whatever the vendor submits, with timestamps and attachments.
What we cannot do with this POS
- MoneyLayer cannot see a vendor’s Square data without their consent path.
- Square will not magically unify independent merchant accounts into one coordinator-owned report.
- Refunds that post after your settlement window still need a policy call.
FAQ
Does MoneyLayer replace Square?
No. Square remains the POS; MoneyLayer is a sidecar reconciliation layer for coordinators.
Can coordinators force access?
No ethical product should. The workflow is consent-based plus structured fallbacks.