Square Card Validation Guide: SDK, Terminal, and Keyed Entry

Square card validation is the set of checks Square runs before a payment goes to the issuer for authorization. The top pick for most online sellers is Square's Web Payments SDK because it validates the card number format, requires the CVV, supports billing address checks, and returns a token instead of raw card data. The criteria used here are card number validation, CVV collection, address verification support, tokenization, and PCI scope.

square card verification utility

Square Web Payments SDK

The Web Payments SDK is Square's browser-based payment form. It checks the card number as the buyer types, flags a failed Luhn check, and requires a CVV for card-not-present payments. Billing address fields can be passed for address verification. The SDK sends card data to Square and returns a payment token to your site.

square card test utility

• Pros: card number and CVV validation happen before authorization, tokenization keeps raw card data out of your server, and the hosted fields reduce PCI scope.
• Cons: you must customize the form to collect billing address for address verification, and the token flow adds a step to your checkout code.

Use the Web Payments SDK for online checkout, subscriptions, and any payment page where the buyer types card details.

more on this topic

Square Terminal and Square Reader

Square Terminal and Square Reader read the card at the point of sale. The card number still goes through a validation check, and the terminal prompts for a CVV when the card supports it. Address verification is not part of a standard card-present flow.

square card verification utility

• Pros: the card data stays in the device, the checkout is fast, and the risk of manual entry errors drops.
• Cons: you cannot use these devices for a remote online payment, and address verification is not available for card-present transactions.

Use a Square Terminal or Reader for in-person sales, counter service, and mobile stands.

Keyed entry with CVV and address verification

Keyed entry is the fallback for phone orders and invoices. Square supports manual card entry with a CVV field, and you can pass the billing address so the issuer can run an address verification check. Keyed transactions usually cost more and carry higher chargeback risk.

• Pros: works when the buyer cannot use a payment form or a terminal, and it supports CVV and address verification fields.
• Cons: higher risk of typos, higher processing cost, and weaker fraud signals than a tokenized online form.

Use keyed entry for phone orders, wholesale invoices, and exceptions, not as the default checkout.

Checks to confirm in any setup

• Card number passes a Luhn check and matches the expected length for the brand.
• CVV is collected at the time of the payment and is never stored after authorization.
• Billing address is passed for address verification on card-not-present payments.
• Raw card data is tokenized, and your servers never receive the full card number.