Accepting Card Payments with Square

If your business already runs on Square — a reader at the studio, payouts you’re used to, reporting your accountant likes — you don’t have to switch rails to use Spatiko. Square connects as a second card processor alongside Stripe: clients pay by card through your Square account, and everything downstream in Spatiko — payment status, the download gate, invoices — behaves identically.

Online payments need a paid plan — see the pricing page.

Connecting Square

Connect from your integrations: you’re handed to Square to sign in and approve the link, then back to Spatiko. The settings dialog shows three things:

• Connection — Connected, or Location needed until the next step is done.
• Merchant — the Square business the connection is linked to.
• Location — which Square location takes the payments.

Choosing a location

Card payments run through one Square location. If your account has several, Spatiko asks you to pick; only active locations with card processing enabled — and matching your business currency — can be used. You can change the location later; payments already in flight finish on the location they started on.

Once a location is saved, Square is ready to take card payments.

One active card processor

This page owns one rule the rest of the guides lean on: you can keep both Stripe and Square connected, but exactly one collects new card payments at a time.

Connecting a second processor never hijacks your checkout — it comes up paused, and whichever processor was already charging stays active. When you’re ready to switch, go to Settings → Payments and pick the active processor from the Card processor tiles; the chooser appears once two processors are connected.

Switching is clean because paused doesn’t mean dead:

• New charges go through the active processor.
• Payments already in flight finish on the processor they started on.
• Refunds keep routing through the processor that took the original payment.
• Payouts land in each processor’s own account.

That last point is also why you shouldn’t disconnect a processor just to switch — disconnecting Square blocks in-app refunds for past Square payments until you reconnect. Pause it from the processor switcher instead.

Payouts and the Square dashboard

Spatiko creates the charges; Square settles the money. Your balance pays out to your bank on Square’s schedule — Square advertises next-business-day payouts as its standard — and payout timing, history, and bank details all live in your Square dashboard, not in Spatiko.

What’s different from Stripe

Day to day, almost nothing — clients pay by card where they always would, statuses update, refunds issue from the order. The differences worth knowing:

• Wallets and extra methods — the express-checkout row (Apple Pay, Google Pay, Link, PayPal) and add-on methods like Klarna are part of the Stripe checkout. Square checkout is card payments.
• Location model — Square ties processing to a business location; Stripe doesn’t have an equivalent step.

If both are connected, pick whichever should take new charges and leave the other paused — you can switch back any time.

Go deeper

• Accepting online payments with Stripe — the other card processor, with one-tap wallets and extra payment methods.
• Getting paid — how payments work — where online card payments sit in the wider money flow.
• Refunding a client — refunds route through the processor that took the payment, paused or not.
• How connecting an integration works — what happens when you click Connect, and how to disconnect later.
• Pay-to-download — the gate opens on payment regardless of which processor collected it.