Overview
SugarPay.io is an independent Square Reseller. We sell Square's payments products to merchants and build software on top of Square's public APIs to give them a clean, mobile-first experience over their Square account — branded invoicing, real-time analytics, and streamlined onboarding.
Square is the system of record. Your catalog, customers, orders, and payouts all live in your own Square account. SugarPay reads from and writes to Square through OAuth-authorized connections you control.
Connecting your Square account
- From SugarPay, choose Connect Square. You'll be redirected to Square to sign in (or create) your Square account.
- Square presents a consent screen listing the exact permissions SugarPay is requesting. You approve there — not in SugarPay.
- Square issues us a scoped access token tied to your account. We store it encrypted at rest and rotate refresh tokens on Square's schedule.
- Initial sync runs in the background — typically under a minute for a small catalog, longer for large multi-location operations.
What syncs
Two-way sync covers the core merchant objects:
| Object | Direction | Notes |
|---|---|---|
| Catalog (items, variations, modifiers) | Two-way | Square is canonical; SugarPay edits write back |
| Customers | Two-way | Email-deduped on first import |
| Orders | Read-only into SugarPay | Source of truth lives in Square |
| Invoices | Two-way | Branded templates from SugarPay; payment state from Square |
| Payouts | Read-only into SugarPay | For analytics; funds settle in Square |
| Locations | Read-only into SugarPay | Multi-location supported |
| Payment card data | Never touches SugarPay | See below |
Sync is event-driven via Square webhooks where available, with a periodic reconciliation sweep as a safety net. Conflicts on simultaneous edits resolve last-write-wins, with the original value preserved in the audit log.
Permissions & scopes
SugarPay requests only the OAuth scopes it needs. The exact list is shown on Square's consent screen at the time of connection. As of this writing, those are:
MERCHANT_PROFILE_READ— to detect your account, currency, and locationsITEMS_READ,ITEMS_WRITE— to mirror and update your catalogORDERS_READ— to power analytics and order historyCUSTOMERS_READ,CUSTOMERS_WRITE— to dedupe and enrich the customer listINVOICES_READ,INVOICES_WRITE— to send branded invoices via Square's railsPAYMENTS_READ— for payout analytics and reconciliation
We do not request payment-write scopes, employee-management scopes, or anything tied to settlement rails.
Payments & payouts
Card payments captured on your Square account are processed by Square (a Block, Inc. company). Funds settle directly to your linked Square bank account on Square's standard payout schedule. SugarPay never holds your money, touches the funds flow, or sits between you and Square's settlement.
For sellers on our Dual Pricing plan (powered by DuetPay), the cash-discount logic runs at the point of sale before the payment is captured; Square still settles each transaction.
Square processing rates
SugarPay does not mark up Square's processing rates. The Standard plan surfaces Square's rack rates as published — see squareup.com/pricing for the canonical list. Effective rates as of April 2026:
- In-person (tap, dip, swipe): 2.6% + 15¢
- Manually keyed / card on file: 3.5% + 15¢
- Online (eCommerce checkout): 2.9% + 30¢
- Invoices (paid online): 3.3% + 30¢
Square may adjust rates from time to time; we'll mirror Square's posted pricing without notice on our side. Custom plans may negotiate interchange-plus pricing — contact sales.
What we don't do
- We don't store, transmit, or process card data.Card capture happens in Square's PCI-validated environment (in-person hardware, Square Web Payments SDK, or Square-hosted invoice URLs). Card numbers, CVVs, and full PANs never reach SugarPay servers.
- We don't hold funds. All settlement is between you and Square. SugarPay is not a money transmitter or payment processor.
- We don't change your Square account's underlying terms. Square's seller agreement, fee schedule, payout schedule, and dispute rules apply unchanged.
- We don't share your data with anyone you haven't authorized. See our Privacy Policy.
Disconnecting & data retention
Disconnect SugarPay at any time — from Settings → Integrations → Disconnect Square, or directly from your Square dashboard. Once disconnected:
- Sync stops immediately. No further reads or writes occur.
- Your data remains in your Square account, untouched. SugarPay does not delete anything from Square on disconnect.
- We retain limited records on our side (invoice metadata, audit logs, billing history) for legal and tax requirements; everything else is purged within 90 days of account closure.
Troubleshooting
Connection expired / re-auth required
Square refresh tokens have a finite lifetime. If your connection lapses, SugarPay will prompt you to re-authorize on next sign-in — your data and settings are preserved.
Catalog item appears in Square but not in SugarPay
Initial sync is paginated and may take several minutes for large catalogs. Webhook delivery can also briefly lag during Square service incidents — the reconciliation sweep will catch any stragglers within an hour.
Two-location merchants seeing the wrong inventory
Confirm the location filter in your SugarPay dashboard matches the location whose inventory you intend to view. Catalog items are global; inventory is per-location.
An invoice paid in Square shows unpaid in SugarPay
Force a manual sync (Settings → Integrations → Re-sync now). If the discrepancy persists, contact support with the invoice ID — we'll trace the webhook delivery and reconcile.
Need help?
Real humans, based in Sherman, Illinois, who know Square inside out.
- Email: contact@sugarpay.io
- Phone: 217-960-8896
- Or visit our contact page for hours and social.
Independence notice:SugarPay.io is an independent Square Reseller and is not affiliated with, endorsed by, or sponsored by Block, Inc. or Square, Inc. "Square" is a trademark of Block, Inc. See our disclaimers.