Square

What Is Square?

Square is Block's payments, point-of-sale (POS), and online-checkout platform, a unified ecosystem that lets businesses accept payments in person, online, and on the go. Launched in 2009 by Jack Dorsey and Jim McKelvey with its iconic small card reader, Square set out to make card acceptance effortless for small businesses that traditional processors had largely ignored. It has since grown into a comprehensive commerce platform spanning hardware, software, online stores, and business tooling, all operated under Block, Inc.

Square is one of the most recognized names in payments, especially among small and mid-size businesses, restaurants, retailers, and service providers. Its hallmark is an integrated experience: the same Square account can power a card reader at a market stall, a full POS system in a restaurant, an online store, and invoicing, with payments, reporting, and customer data unified across all of them. For developers and online merchants specifically, Square offers the Web Payments SDK, a JavaScript toolkit for accepting payments on websites.

This breadth is what distinguishes Square from a pure online payment gateway. Many processors focus on one channel, but Square's value proposition is omnichannel commerce: a coffee shop can take a tap payment at the counter, sell beans through a Square Online store, send a catering invoice, and see all of it, sales, inventory, customers, in one dashboard. The payments are just the connective tissue of a much larger commerce operating system aimed at running the whole business.

Square is not a browser extension you install yourself. In the online context it is a payments platform that merchants integrate into their websites, either through Square's hosted checkout and online store products or through the Web Payments SDK for custom integrations. The card data and processing are handled on Square's PCI-compliant infrastructure. From the outside, a website using Square's online payments reveals itself through the Web Payments SDK script, Square-hosted payment fields, and the domains its checkout communicates with.

It helps to understand who Square is for. The platform targets small and mid-size businesses that want an all-in-one commerce solution with minimal setup and transparent, predictable pricing, rather than enterprises assembling a bespoke payments stack. Where a developer-first processor optimizes for deep API flexibility, Square optimizes for an integrated, out-of-the-box experience across in-person and online sales. That positioning shapes its products, from plug-and-play hardware to a website builder, and explains why Square is so prevalent among independent retailers and restaurants.

How Square Works

Square's foundation is a payments engine that processes card and digital-wallet transactions across channels, in person via Square hardware and software, and online via Square's checkout products and the Web Payments SDK. The same account and processing infrastructure underpins every channel, so funds, fees, and reporting are consistent whether a sale happens at a counter or on a website.

For online payments specifically, the Web Payments SDK is the key technology. It is a JavaScript library a merchant adds to their site that renders secure, Square-hosted payment fields, card number, expiry, CVV, often as iframes, so sensitive card data goes directly to Square rather than touching the merchant's servers. This tokenization keeps the merchant's PCI-DSS scope low. The SDK also supports digital wallets like Apple Pay and Google Pay and methods such as Cash App Pay, reflecting Square's place within Block alongside Cash App. The merchant's backend then uses Square's APIs to create the payment from the tokenized card and confirm the charge.

Beyond raw payments, Square layers on a full commerce suite. Square Point of Sale runs on phones, tablets, and Square's dedicated hardware (Square Reader, Square Stand, Square Register, Square Terminal). Square Online is a website and online-store builder with built-in checkout. Square Invoices, Square Appointments, Square for Restaurants, and Square Retail tailor the platform to specific business types. Square Dashboard unifies sales, inventory, customers, and analytics, and Square Capital offers financing. Digital wallets and Cash App Pay extend the consumer payment options.

When an online payment flows through the system, the Web Payments SDK tokenizes the card in the browser, the merchant's server creates a payment with that token via Square's API, Square runs risk and fraud checks, processes the transaction through the card networks, and settles funds to the merchant on Square's schedule, recording everything in the unified dashboard. Webhooks notify the merchant's systems of events like completed payments and refunds, keeping order management synchronized.

A useful way to picture the online experience is to follow one website checkout end to end. A shopper on a Square-powered store enters their card into fields that are actually Square-hosted iframes; the Web Payments SDK tokenizes the details so the store never sees the raw card number. The store's backend sends that token to Square's API to create the payment, Square authorizes it through the card networks, and the shopper sees a confirmation. The same dashboard the merchant uses for in-person sales now shows this online order too, with funds settling alongside their counter transactions, the omnichannel unification that defines Square.

How to Tell if a Website Uses Square

Square's online payments leave several reliable fingerprints. Because StackOptic analyzes a URL from the server side, it looks at the same signals you can check manually with browser tools, View Source, or a detection extension.

The Web Payments SDK script. The strongest signal is the Web Payments SDK loaded from Square's domain, such as web.squarecdn.com (for example a script like https://web.squarecdn.com/v1/square.js). A reference to the Square Web Payments SDK on a checkout page is strong evidence of a Square integration.

Square-hosted payment fields. The card-entry fields rendered by the SDK are Square-hosted iframes rather than native inputs, keeping card data off the merchant's site. Inspecting the checkout form and finding Square-hosted iframes is a recognizable tell.

Square domains and CDNs. Online checkout communicates with Square endpoints, and assets load from squarecdn.com and related domains. Network requests to square and squareup.com / squarecdn.com domains during checkout are a strong secondary signal.

The Square JavaScript global. When the Web Payments SDK loads, it exposes a Square object on the page's JavaScript window. Finding a Square global in the DevTools Console confirms the integration.

Square Online storefront signatures. Sites built with Square Online frequently carry recognizable markup, asset paths, and sometimes a checkout hosted on Square's online-store infrastructure, which can include squareup.com checkout links or Square Online platform fingerprints.

Method	What to do	What Square reveals
View Source	"View Page Source" on the checkout page	A Web Payments SDK script from web.squarecdn.com
Browser DevTools	Open the Network tab during checkout	Requests to squarecdn.com / squareup.com and hosted card iframes
DevTools Console	Type window.Square after the SDK loads	The Square object confirms the integration
Wappalyzer	Run the extension on the live page	Identifies "Square" under payment processors
BuiltWith	Look up the domain	Current and historical Square detection plus the broader stack

A quick command-line check is curl -s https://example.com | grep -i "squarecdn\|web.squarecdn", ideally run against the checkout page where the SDK loads. For a broader walkthrough, see our guides on how to find out what payment processor a website uses and how to find out what technology a website uses. Reading the response headers can add confirming context, as covered in how to read a website's HTTP headers.

It is worth noting how these signals behave on real sites. The Web Payments SDK typically loads on the checkout or payment page rather than the homepage, so scanning the front page alone often misses it; checking the cart or checkout page is far more reliable. The SDK script and the Square global are the most dependable tells because the secure tokenization genuinely depends on them. Some merchants use Square Online's fully hosted store or hosted checkout links, in which case the payment step may redirect to a squareup.com domain rather than embedding the SDK directly, shifting the clearest signal to those hosted URLs. Because a business can use Square for in-person sales while processing its website through a different provider, online detection specifically depends on finding the web-payments signals rather than assuming Square everywhere. Combining multiple signals, a script reference, a network request, and the JavaScript global, makes the conclusion very reliable, and server-side analysis helps by reading the unmodified HTML without browser interference.

Key Features

• Omnichannel payments. Accept cards and digital wallets in person, online, and via invoices from one unified account.
• Web Payments SDK. A JavaScript toolkit for embedding secure, Square-hosted payment fields on websites with low PCI scope.
• Digital wallets and Cash App Pay. Built-in support for Apple Pay, Google Pay, and Cash App Pay within the Block ecosystem.
• Integrated POS and hardware. Square Reader, Stand, Register, and Terminal paired with Square Point of Sale software.
• Square Online store builder. A website and ecommerce builder with native checkout for non-developers.
• Unified dashboard. Sales, inventory, customers, and analytics across all channels in one place.
• Business tooling. Invoices, Appointments, restaurant and retail editions, and Square Capital financing.

Pros and Cons

Pros

• A genuinely integrated omnichannel platform: in-person, online, and invoicing share one account and dashboard.
• Transparent, predictable pricing and easy setup that suit small and mid-size businesses.
• Secure tokenized online payments via the Web Payments SDK keep PCI scope low.
• Strong hardware and software ecosystem for retail, restaurants, and services.

Cons

• Less deep API flexibility for highly custom, developer-first online integrations than some specialist gateways.
• Flat-rate pricing can be less economical than negotiated interchange-plus rates at high volume.
• Geared toward small and mid-size businesses rather than large-enterprise payment needs.
• Tightly integrated ecosystem can create some lock-in across hardware and software.

Square vs Alternatives

Square competes with other payment and commerce platforms across both online and in-person channels. The table below clarifies where it fits.

Platform	Strength	Channel focus	Best for
Square	Integrated omnichannel commerce	In-person and online	Small and mid-size businesses, retail, restaurants
Stripe	Developer-first online payments	Online (with in-person via Terminal)	Developers and online-first businesses
PayPal	Consumer trust and global wallets	Online (with in-person tools)	International checkout and conversion
Shopify Payments	Native to the Shopify platform	Online and Shopify POS	Shopify merchants wanting native checkout
Clover	POS-focused hardware and software	In-person (with online add-ons)	Restaurants and retail prioritizing POS

If you suspect a different processor, the same detection techniques apply; compare Square's integrated approach with a developer-first gateway like Stripe to see the contrast between an all-in-one commerce platform and a pure online payments API. For turning detection signals into qualified pipeline, see what is technographics: using tech-stack data to qualify leads.

Use Cases

Square is most at home for small and mid-size businesses that sell across both physical and online channels. Restaurants and cafes use Square for Restaurants for in-house ordering and a Square Online store for pickup and delivery, with payments and menus unified. Retailers use Square Retail for in-store POS and inventory plus an online store, so stock and sales stay synchronized across channels.

It also serves service providers using Square Appointments and Invoices to book and bill clients, market and pop-up sellers using a Square Reader with a phone, and online-first merchants embedding the Web Payments SDK into a custom checkout. For market and competitive research, detecting Square indicates a small or mid-size business that values an integrated, easy-to-run commerce platform, often a retailer, restaurant, or service provider, which is useful context for vendors and analysts.

Consider a few concrete scenarios. A boutique might run its physical shop on a Square Register, sell online through Square Online, and use the unified dashboard to manage inventory across both, never reconciling two separate systems. A restaurant might take counter and table payments on Square hardware while accepting online orders through a Square-powered site, with Cash App Pay and Apple Pay available at checkout. A web developer building a custom storefront for a client might integrate the Web Payments SDK directly to keep the design fully bespoke while offloading card security to Square.

From a sales-intelligence perspective, spotting Square on a domain is a meaningful data point. It strongly suggests a small or mid-size business, frequently in retail, food, or services, that prefers an integrated commerce solution over a stitched-together stack. For vendors selling to SMBs, point-of-sale add-ons, marketing tools, business services, that profile is a valuable qualifying signal. Identifying Square adoption automatically across many sites, rather than inspecting each checkout by hand, is exactly the kind of insight a technology-detection scan delivers in seconds.

Frequently Asked Questions

What is the Square Web Payments SDK?

The Web Payments SDK is Square's JavaScript toolkit for accepting payments on websites. A merchant embeds it to render secure, Square-hosted payment fields, typically as iframes for card number, expiry, and CVV, so sensitive card data goes directly to Square rather than the merchant's servers. The SDK also supports digital wallets like Apple Pay and Google Pay and Cash App Pay. Detecting a script from web.squarecdn.com and a Square JavaScript global is the clearest sign a site uses it.

How do I tell for free if a website uses Square online payments?

Yes, you can confirm it at no cost. Check the checkout page rather than the homepage: view the source for a Web Payments SDK script from web.squarecdn.com, open DevTools and watch for network requests to squarecdn.com or squareup.com, and type window.Square in the Console after the page loads. Free tools like Wappalyzer and BuiltWith also identify Square, and a curl -s URL | grep squarecdn command against the checkout page works from any terminal.

Is Square the same as Block and Cash App?

Square is the payments and commerce platform operated by Block, Inc., the parent company that also owns Cash App, the consumer payments app. They are distinct products under the same corporate umbrella. The connection shows up at checkout through Cash App Pay, a payment option Square supports that lets Cash App users pay directly. So while Square (merchant commerce) and Cash App (consumer app) are different products, Block's ownership of both is why Cash App Pay appears within Square's payment options.

Does Square reduce PCI compliance burden for online stores?

Yes. The Web Payments SDK renders card fields as Square-hosted iframes and tokenizes the card details in the browser, so the raw card data goes directly to Square and never passes through the merchant's servers. This keeps the merchant's PCI-DSS scope significantly lower than handling card data directly. Merchants still have responsibilities, such as securing API credentials and verifying payments server-side, but Square handles the heaviest compliance burden around storing and transmitting card data.

Can a business use Square in stores but a different processor online?

Yes. Square's channels are integrated but not mutually exclusive, a business can run its physical locations on Square hardware while processing its website through a separate online gateway, or vice versa. This is why detecting Square specifically for online payments depends on finding the web-payments signals (the SDK script, Square-hosted card fields, and Square domains on the checkout page) rather than assuming a business that uses Square in person also uses it online. Server-side analysis of the actual checkout page is the reliable way to confirm online usage.

Want to identify Square and the full stack behind any site in seconds? Run any URL through StackOptic at https://stackoptic.com.