Square

Square's Payments API is the developer surface of Block's Square ecosystem, exposing the same payment rails that power Square's point-of-sale hardware and seller tools. The core CreatePayment endpoint accepts a payment token (generated client-side by the Web Payments SDK or In-App Payments SDK), a card on file, or other sources, and supports an unusually broad set of methods: credit/debit cards, digital wallets (Apple Pay, Google Pay, Cash App Pay), ACH bank transfers, Afterpay/Clearpay BNPL, Square gift cards, cash, and external payments. It is complemented by a coherent family of REST APIs, Refunds, Disputes, Payouts, Orders, Catalog, Customers, Subscriptions, Terminal, and Cards, so a developer can build an end-to-end commerce stack rather than just a charge call. The platform's defining strength is the tight unification of online and in-person (omnichannel) payments under one account and one API, which is hard for pure online-only gateways to match.

Square is best suited to small and mid-market sellers, omnichannel retailers, restaurants, and SaaS/marketplace builders who want PCI-compliant tokenized inputs without standing up their own card vault. The developer experience is genuinely strong: official server SDKs for Node.js, Python, Java, PHP, Ruby, .NET, and Go, client SDKs for web/iOS/Android/React Native, a full-featured sandbox with deterministic test card values, OAuth for multi-merchant apps, and well-regarded reference docs. Pricing is simple and transparent, flat-rate, no monthly minimums or PCI fees on the free tier, at 2.6% + 15¢ in-person and 2.9% + 30¢ for online API payments, which is competitive for low-volume sellers but expensive at scale versus interchange-plus processors; volume above $250K/year qualifies for custom rates.

The most serious and consistently reported weakness is not technical but operational: Square's automated risk system periodically freezes accounts or withholds funds with little notice and slow, hard-to-escalate support, which is a real business-continuity risk for developers building a livelihood on the platform. Phone support is limited to the first 90 days, and the BBB logged over 900 complaints in the past year, many about holds. For a developer the calculus is a polished, omnichannel, well-documented API with excellent time-to-first-payment, weighed against flat-rate economics that erode at scale and underwriting/support practices that have burned merchants. It is an excellent default for SMB and omnichannel use cases and a riskier bet for high-volume or thin-margin operations.