The February 23, 2011 article covered Square and its small card reader for a mobile device’s headphone connection. The saved page links to squareup.com and App Store ID 335393788.
It described a merchant receiving a card payment through a phone or tablet. Its quoted charges, eligibility statements and card-acceptance promises were period claims, not current Square terms.
Follow the transaction from beginning to end
The historical idea was to bring payment acceptance to the point where a seller and customer met. That involved more than attaching a reader: an account, a supported payment method and a completed transaction all belonged to the workflow.
When evaluating a payment system, distinguish entering a payment from receiving a confirmed outcome. The interface needs to make clear which stage has been reached so that an incomplete attempt is not mistaken for a successful one.
The hardware is only one part
A convenient reader does not answer every question about the surrounding service. Current fees, availability, supported devices and account conditions must come from the provider’s current documentation for the relevant location.
This article deliberately avoids republishing the old post’s broad “anywhere” language or its simplified fee description as present advice.
Square’s appearance in the archive records an important interface idea: allowing an ordinary mobile device to participate in a merchant payment workflow. The restored page preserves that historical subject without promising that the original accessory or commercial arrangement remains usable today.