Payments that never touch your server

Technology

Square Web Payments handles card entry in an iframe Square controls, hands back a single-use token, and keeps card data out of your application entirely. That is the whole reason to choose it: the compliance surface shrinks to almost nothing.

We build donation and checkout flows on it for organizations that need to take money online without taking on the risk of storing it.

Monogram logo

Why

Why we reach for Square Web Payments

  1. Card data never reaches you

    The card form runs in an iframe Square hosts. Your application receives a token, never a card number, which keeps the bulk of PCI scope on Square's side rather than yours.

  2. One integration, several payment methods

    Card, Apple Pay, Google Pay, and ACH come from the same SDK and the same tokenization flow, so adding a method is a front end change rather than a new integration.

  3. Right sized for nonprofits and smaller operators

    Not every organization needs a full commerce platform. When the requirement is a reliable, secure way to accept donations or a handful of products, this is less machinery to own.