In-person payments connected to your software — not a separate system.
Stripe Terminal bridges the point-of-sale and the software system. Card-present transactions that flow through the same Stripe account as online payments, with the unified payment history, reporting, and customer records that separated systems can't provide.
Business that takes both in-person and online payments with no connection between the systems — separate merchant accounts, separate reporting, and no unified customer payment history
Businesses with both in-person and online sales typically use separate payment systems — a standalone POS terminal for in-person and Stripe for online. The cost of this separation:
Separate reporting. In-person revenue tracked in the POS system; online revenue in Stripe. No unified view of total revenue, no reconciliation without manual work.
Separate customer records. A customer who buys online and in-store is two separate customers in two separate systems. No unified purchase history, no cross-channel loyalty, no understanding of total customer lifetime value.
Duplicate payment infrastructure. Two merchant accounts, two sets of processing fees (potentially), two systems to manage.
Stripe Terminal solves this by enabling card-present transactions through the same Stripe account. The in-person payment flows through Stripe, appears in the same Stripe dashboard, and can be linked to the same customer record as online transactions.
The integration requires:
- A Stripe Terminal reader (BBPOS WisePOS E, Stripe Reader S700, or similar)
- The Terminal SDK integration in the application
- A connection token endpoint on the backend
- Payment intent creation with card-present configuration
Stripe Terminal integration with in-person card-present transactions connected to the software — same Stripe account, same customer records, unified payment reporting
Connection token endpoint
Backend Route Handler that creates and returns Stripe Terminal connection tokens. The client uses this to authenticate with the Terminal SDK.
Reader management
Reader registration and management. Reader discovery in the application.
Payment flow
Terminal SDK payment intent creation. Card-present reader interaction. Payment confirmation and receipt.
Unified customer records
Terminal payments linked to customer records. Cross-channel purchase history.
Offline capability
Terminal readers support offline card capture — transactions stored on the reader and processed when connectivity returns.
One honest number to start.
Fixed-scope, fixed-price. The number below is the starting point — final scope is built from your brief.
Stripe Terminal integration with in-person card-present transactions connected to the software — same Stripe account, same customer records, unified payment reporting
Three steps, every time.
The same repeatable engagement on every project. No surprises, no mystery, no billable ambiguity.
Brief & discovery.
We send you questions, then get on a call. Output: a written scope with every step, feature, and integration listed.
Build & ship.
Fixed schedule, weekly reviews. No scope creep unless you change the scope — and if you do, we reprice it transparently.
Warranty & retainer.
30-day warranty on every launch. Most clients stay on a monthly retainer for ongoing features and maintenance.
Why Fixed-Price Matters Here
Terminal integration scope is defined by the reader type and the POS workflow. Fixed price.
Related engagements.
Stripe billing is more complex than the docs suggest. The edge cases are where revenue leaks.
Read more02Build a custom POS system — built for your specific retail or service operation.
Read more03The brick-and-mortar business that builds digital infrastructure keeps customers competitors can't reach.
Read moreQuestions, answered.
The Stripe Reader S700 (touchscreen, $299) for full POS use cases. The BBPOS WisePOS E ($249) for simpler tap/chip/swipe scenarios. The BBPOS WisePad 3 ($49) for mobile or peripheral use cases. Reader choice depends on the physical environment and workflow.
Cash transactions aren't a Stripe capability (Stripe processes card payments). The application can record cash transactions separately for reporting purposes — but the Terminal itself is card-only.
Terminal integration is part of the POS application build. Full POS from $28k. Fixed-price.
Tell Ryel about your project.
Describe what you’re building and what outcome you need. You’ll have a written, fixed-price scope within the week.