On June 11, 2019, Stripe made Terminal generally available to its users in the United States. The product combines software development kits, application programming interfaces and pre-certified card readers so businesses can add in-person payments to an existing Stripe integration. The announcement was limited to the US; people elsewhere could request a notice when service reached their country. [shared-2f565a290f4d0f22faa3df731d5646cfbb260be3bc2110bc216752108a247a08]
For a shop selling both online and at a counter, Stripe said Terminal could bring customer and sales information from both channels into one view, making reporting and reconciliation easier. Subscription businesses could connect it with Billing; platforms and marketplaces could use Connect to let their accounts take in-person payments. Stripe also described dashboard tools to manage reader fleets and ship readers to connected accounts. These are stated product capabilities, not measured savings. [shared-2f565a290f4d0f22faa3df731d5646cfbb260be3bc2110bc216752108a247a08]
The trade-off is practical: businesses must build a sales interface, connect the app to a reader through Terminal’s SDK, then pair the device and take a payment. A combined system may simplify oversight, but it does not remove the work of fitting checkout into daily operations. The announcement offers no independent evidence about time saved or who bears ongoing support costs. For smaller merchants, does one reporting view outweigh the labour of implementation and maintenance? [shared-2f565a290f4d0f22faa3df731d5646cfbb260be3bc2110bc216752108a247a08]