How to Take Card Payments on POS with Stripe Terminal
A separate card machine means the till and the card terminal never quite agree
The cashier rings the sale in one system and charges the card in another, so totals are re-keyed by hand at the busiest moment of the day.
A transposed digit is only discovered at close, when nobody remembers which sale it belonged to.
Card takings, bank deposits, and processor fees arrive as three unrelated numbers that finance reconciles manually.
Why this happens
- Recording a card tender as a note rather than charging the card from the till.
- Sharing one card machine across several registers, so payments cannot be attributed to a till.
- Capturing the card before the sale is recorded, leaving charges with no matching sale.
- Treating processor fees as a bank charge discovered weeks later.
Biznsbook addresses this through card-present checkout, reader paired to a register, authorise then capture when the POS module is licensed — terminal and back-office checkout share unified SaleBill posting.
Finance teams lose days each month reconciling versions that should never have diverged. Naming Biznsbook screens as the system of record — and closing periods when agreed — prevents silent edits that auditors flag immediately.
Step-by-step: Take Card Payments on POS with Stripe Terminal
Built for retailers who need a fast till, float discipline, and the same INV-* sale bill in stock and GL — not a standalone cash register.
- Enable the connector. Management → Integration hub → Stripe Terminal. Tick Enable this connector and save. Nothing changes at the till until setup is finished.
- Connect your Stripe account. Press Connect with Stripe and approve Biznsbook. You keep your own account and your own rates; Biznsbook never holds the funds.
- Choose the payout bank account. Pick the ledger account Stripe deposits into. Payouts are not posted until this is set, rather than guessing the wrong account.
- Add a location. One Stripe location per shop, with its street address. Readers belong to a location, so add it before the reader.
- Register the reader. On the reader, Settings → Generate pairing code. Enter that code in Biznsbook with a label your staff recognise, and choose the location.
- Pair the reader to a register. In the Readers table set Paired register. One reader per POS register, so every payment is attributable to a till.
- Take a payment. Ring the sale, choose Card, press Confirm Card Payment, let the customer tap, then Complete Sale. The receipt prints brand, last four, and authorisation code.
Review results after the first full weekly cycle. Adjust roles, mappings, or approvals where the same exception repeats.
Screen-level flows live in the Help Center. This guide focuses on the business process; help articles cover click-by-click navigation.
Common mistakes to avoid
- Mistake 1: Recording a card tender as a note rather than charging the card from the till. Repeating this each month usually shows up first in cash reconciliation and till speed.
- Mistake 2: Sharing one card machine across several registers, so payments cannot be attributed to a till. Repeating this each month usually shows up first in cash reconciliation and till speed.
- Mistake 3: Capturing the card before the sale is recorded, leaving charges with no matching sale. Repeating this each month usually shows up first in cash reconciliation and till speed.
- Mistake 4: Treating processor fees as a bank charge discovered weeks later. Repeating this each month usually shows up first in cash reconciliation and till speed.
Track recurring exceptions in month-end notes; each should map to a control above.
Best practices that hold up as you scale
- Enable the connector — Management → Integration hub → Stripe Terminal.
- Connect your Stripe account — Press Connect with Stripe and approve Biznsbook.
- Choose the payout bank account — Pick the ledger account Stripe deposits into.
- Add a location — One Stripe location per shop, with its street address.
- Register the reader — On the reader, Settings → Generate pairing code.
Teams that open on a named register, park holds, and close with expected cash keep variance disputes short.
How Biznsbook supports this workflow
card-present checkout is documented in Biznsbook POS capabilities. Use it as part of a controlled finance process — posting, review, and period close — not as an isolated export. When Sales, Purchase, Inventory, Taxation, Expense, or Finance Management modules are enabled, related documents can post through the central accounting posting service with double-entry validation.
reader paired to a register is documented in Biznsbook POS capabilities. Use it as part of a controlled finance process — posting, review, and period close — not as an isolated export. When Sales, Purchase, Inventory, Taxation, Expense, or Finance Management modules are enabled, related documents can post through the central accounting posting service with double-entry validation.
authorise then capture is documented in Biznsbook POS capabilities. Use it as part of a controlled finance process — posting, review, and period close — not as an isolated export. When Sales, Purchase, Inventory, Taxation, Expense, or Finance Management modules are enabled, related documents can post through the central accounting posting service with double-entry validation.
Sessions, barcode, split tender, X/Z reports, and receipt branding are covered in Docs/POS — use Help Center for click-level screens.
Suggested implementation timeline
- Week 1: Document current process gaps and configure card-present checkout with finance owner sign-off.
- Weeks 2–3: Pilot on one month or one entity; post all test transactions through Biznsbook; freeze parallel spreadsheet journals.
- Week 4: Run first trial balance or report tie-out; fix mapping and permission issues.
- Month 2–3: Roll out to full team; add approvals and period close cadence from this guide.
- Ongoing: Monthly review using test before hardware arrives and leadership dashboard.
Metrics to track monthly
- Open sessions with a selected POS terminal
- Cash sales with ClientRequestId retries that stay single INV-*
- Parked bills resolved before close
- X-reports run mid-shift without closing
- Terminal Z generated per register/day
Start with three metrics; trend direction matters more than a single point-in-time snapshot.
Spreadsheet / manual books vs integrated ERP
Compare typical manual finance work with Biznsbook card-present checkout and related capabilities.
| Capability | Manual / Spreadsheet | Biznsbook |
|---|---|---|
| Charging the card | ❌ Separate machine, re-keyed total | ✅ Amount pushed to the reader from the till |
| Attribution | ❌ One machine, many tills | ✅ One reader paired to one register |
| Order of operations | ❌ Charge, then hope the sale saves | ✅ Authorise, post the sale, then capture |
| Card details on receipt | ❌ Second slip from the terminal | ✅ Brand, last four, auth code on the POS receipt |
| Split payments | ❌ Two systems, manual maths | ✅ Cash at the till, card on the reader, one sale |
| Processor fees | ❌ Found on the bank statement | ✅ Posted automatically at payout |
Test before hardware arrives
Tick Use simulated readers and register a simulated reader with the pairing code simulated-wpe. The whole flow — authorise, decline, capture, refund — can be rehearsed in Stripe test mode before a physical reader is unboxed, and no real money moves.
Document this in your finance SOP and revisit each quarter as transaction volume or entity structure changes.
Frequently asked questions
Does Biznsbook take a cut of card payments?
No. You connect your own Stripe account and keep your own Stripe rates. Money goes from Stripe to your bank; Biznsbook never holds it and charges no application fee.
Can Biznsbook see card numbers?
No. Stripe readers are encrypted end to end. Card data never reaches your browser or Biznsbook servers, so the application stays out of PCI scope.
Which readers work?
Internet-connected models such as BBPOS WisePOS E and Stripe Reader S700. Bluetooth-only readers are not supported because they need native mobile apps.
What happens if the browser refreshes mid-payment?
Reopen the sale. Biznsbook finds the payment already in progress by the same request id and resumes it rather than charging the card a second time.
Can I take card payments offline?
No. Cash sales queue offline and sync later, but a card has to be charged at the time, so card sales need a live connection.
How this differs by industry
Retail
Boutiques and convenience stores run one reader per till so every card sale is tied to the register that took it.
Wholesale & distribution
Trade counters take card payments for walk-in collections without leaving the counter sale screen.
Manufacturing
Factory outlet shops take card payments on finished-goods sales without raising a wholesale invoice.