Payment Processor Integration

Square-native.
Processor-agnostic.

Aisle FLO runs on Square. Stripe, Lightspeed, Moneris, and Chase all work via our sidecar model.

Square — deepest
Stripe
Lightspeed
Moneris
Chase Paymentech
Book an integration demo →
Where each processor fits

The right integration
for every merchant.

Sidecar

Stripe

Catalogue import via guided onboarding. Orders arrive in the GoFLO merchant dashboard. Stripe continues processing all in-store transactions untouched.

Sidecar + API sync

Lightspeed

API sync available for Lightspeed merchants. Menu/catalogue auto-syncs to GoFLO or FaveCart. In-store Lightspeed POS is completely untouched.

Sidecar

Moneris

Canada's most widely used processor. Moneris continues handling all card-present volume. Aisle FLO adds a delivery channel settled separately to your bank.

Enterprise sidecar

Chase Paymentech

Enterprise and chain merchants on Chase keep their full payment infrastructure. Aisle FLO adds last-mile delivery and white-label capabilities alongside it.

Capability Square (native) Stripe / Lightspeed Moneris / Chase
Payment processing✓ Square native✓ via sidecar✓ via sidecar
POS/KDS integration✓ Native — Orders APIMerchant dashboardMerchant dashboard
Catalogue sync✓ AutomaticLightspeed: API · Stripe: guided importGuided import
FavePoints loyalty✓ Square Customer Directory✓ FaveWallet✓ FaveWallet
New hardware requiredNoneNoneNone
Switching costZeroZeroZero
Canadian data residency✓ Always✓ Always✓ Always
Platform-agnostic onboarding

Three steps.
Any processor.

Aisle FLO works with what you have. Your in-store system stays exactly as it is. We add the delivery channel on top.

1

Sync your catalogue

Square and Lightspeed merchants sync automatically via API — your menu or inventory is live on GoFLO or FaveCart within one session. Stripe, Moneris, and Chase merchants use our guided catalogue import. No developer required.

2

List under your brand

Your menu or catalogue publishes on GoFLO, FaveCart, or both — under your banner. Square merchants receive orders natively in their existing POS and KDS. All other merchants receive orders via the GoFLO merchant dashboard in real time, with optional webhook notifications.

3

Settle to your bank

Aisle FLO settles your delivery-channel revenue directly to your bank account. Your in-store Lightspeed, Stripe, Moneris, or Chase setup is completely untouched. Two revenue streams. One operation. Zero switching cost.

GoFLO Order Flow — Square Merchant
📱
Customer orders on GoFLOTrue menu price + flat delivery fee
Square Orders API firesOrder appears in your existing POS/KDS instantly
👨‍🍳
Kitchen prepares orderMarks ready in Square — exactly like a native order
🔔
Webhook firesAisle FLO dispatches nearest available IBO driver
🚗
IBO picks up and deliversMerchant keeps ~95%. No new tablet. No new login.
💳
Settlement to your bankDelivery revenue settled separately — in-store untouched
Square — deepest integration

Already on Square?
You're already halfway in.

Aisle FLO was built Square-first. Every GoFLO and FaveCart delivery order is a native Square order — your kitchen, your KDS, your loyalty, your customer data. Nothing changes about how you run your business.

OAuth API

Secure merchant connect

Merchants connect their Square account to Aisle FLO securely in one click. We request only the scopes needed — Orders, Catalog, Customer Directory. No credential sharing.

Orders API + Webhooks

Native POS/KDS injection

GoFLO and FaveCart orders are created as Square DELIVERY orders via the Orders API. They appear in your Square POS and KDS instantly. Webhooks on order.fulfillment.updated trigger IBO dispatch.

Catalog API

Automatic menu sync

Your Square catalog is the source of truth. Add an item in Square — it appears on GoFLO automatically. Price changes, modifiers, and availability all stay in sync.

Customer Directory

FavePoints on your customer base

FavePoints loyalty ties to your Square Customer Directory. Delivery orders earn points for your customers — attributed to your location, not a generic Aisle FLO bucket.

Payments API

Square processes everything

All customer payments on GoFLO and FaveCart flow through Square at your standard processing rate. No new payment processor. No new merchant account. No new fees on top.

FaveWallet

Cross-platform wallet + loyalty

FaveWallet integrates with Square's payments infrastructure. Wallet loads, FavePoints redemptions, and Diamond fee passes all flow through the same Square-native layer.

Frequently asked questions

What if I don't
use Square?

Lightspeed

We're on Lightspeed. Do we need to switch?

No. Lightspeed is a strong Canadian-built POS and we integrate alongside it. Aisle FLO adds a dedicated delivery channel on top, settled separately. Your Lightspeed setup stays exactly as it is — hardware, contracts, staff workflow, all unchanged.

Stripe

We process payments through Stripe. Problem?

Not at all. Stripe handles what it handles today. When a customer orders through GoFLO or FaveCart, that transaction runs through Aisle FLO's Square-powered front-end independently. We settle your delivery revenue to your bank separately — clean, no overlap, no conflict.

Moneris

We're on Moneris. Is that supported?

Yes. Moneris is Canada's most widely used processor and we support it via sidecar onboarding. Moneris continues processing your in-store and card-present volume. Aisle FLO handles the delivery channel, settled separately. No switching, no disruption.

Chase Paymentech

We're a larger operation on Chase. Enterprise-ready?

Yes. Every Aisle FLO platform is white-label ready for enterprise retailers and restaurant groups. Chase continues processing your in-store volume. Aisle FLO handles last-mile delivery, IBO dispatch, loyalty, and the customer-facing experience under your own brand.

All processors

Will we eventually need to move to Square?

Square unlocks the deepest integration — native POS/KDS injection, catalog auto-sync, and FavePoints tied to your Square customer base. But it is never a requirement. Many merchants start on the sidecar model and migrate to Square when they see the operational benefit. The decision stays yours.

Data

Where does our customer data live?

All transaction, customer, and order data routes through Canadian infrastructure — Vercel's Montreal region for edge compute, Square Canada for payments. Your customer data does not cross into US jurisdiction or train a competitor's algorithm. Canadian data residency is a non-negotiable design constraint, not a marketing claim.