Aeion Commerce + Square
A payments gateway for online storefronts, with card-not-present processing via Square's Web Payments SDK. Aeion's Bridge integration adds generic local hardware (receipt printer, cash drawer, barcode scanner) for a physical point-of-sale screen, sharing the same product catalog and inventory records as the online store.
When Square Wins
Square's sweet spot is omnichannel retail + food + service businesses:
Setup
- Create a Square account at
https://squareup.com/signup
Online (Card-Not-Present) Flow
Square Web Payments SDK for tokenization, same pattern as Stripe.js.
In-Person Flow via Bridge
Aeion's Bridge integration is a local-hardware bridge for a physical POS screen — it drives a receipt printer, cash drawer, and barcode scanner, and can read a generic magstripe card swipe over HID for display purposes (masked to the last 4 digits; raw track data never leaves the till). Bridge itself isn't a Square Terminal / Reader integration — there's no dedicated Square card-present hardware flow wired up today, so an in-person card charge still needs to go through Square's own certified terminal/reader hardware and app, or through Square's Web Payments SDK on a POS-facing browser tab, separate from Bridge's printer/drawer/scanner functions.
Unified Inventory + Customer + Order
Square's killer feature is the in-person + online unification. With Aeion:
Common Gotchas
- Sandbox vs Production tokens — completely separate; sandbox tokens don't work against production endpoints. Set the provider's Mode field carefully.
FAQ
Stripe has more developer-focused APIs, broader feature set (Radar, Billing, etc.). Square's online API is fine but less feature-rich. The reason to use Square online is unification with in-person.
Yes — same Aeion deployment can enable both. Online via Stripe, in-person via Square. Each order tracks which gateway handled the payment.
Not currently — Aeion's subscription engine only orchestrates Stripe, PayPal, Razorpay, GoCardless, Mollie, and Paystack as subscription providers today. For recurring billing, use one of those instead.
Aeion's `stores` records are storefront/theme configuration, not physical-location records, and there's no built-in mapping from an Aeion store to a specific Square Location ID today — a single enabled Square provider carries one Location ID. True multi-location Square reporting still happens in Square's own dashboard.
Square Gift Cards API works for in-person; for unified online + in-person gift cards, Aeion's native gift card system is better (works across all 20 payment providers).
If you need restaurant-specific features (kitchen display, course timing, etc.), Square for Restaurants is Square's own product for that. Aeion's Dining module lists Square POS as an integration category and has its own Bridge-dispatched card-charge flow for table-side payments, but it doesn't currently call Square's Restaurant-specific API.