Integrated vs. Semi-Integrated Payments: What's the Difference?
Semi-integrated payments keep card data off your POS. See how they compare with integrated setups on PCI scope, reconciliation and processor lock-in.
Photo: Pixabay
On this page 6 sections
Key takeaways
- Ask your software vendor one question first: does card data ever pass through our computers? The answer tells you which setup you have, whatever the brochure calls it.
- Semi-integrated setups shrink PCI scope, but you still validate compliance every year. Typing card numbers into your software brings the scope right back.
- Stored card tokens are usually tied to one processor, so recurring plans and card-on-file balances are often the most expensive part of switching.
- Before you sign a processing contract, get your software vendor's list of supported processors or terminals in writing.
The difference comes down to where card data travels. In a fully integrated setup, card data passes through your POS or practice-management software on its way to the processor. With semi-integrated payments, your software only sends the sale amount to the card terminal. The terminal reads the card and talks to the processor directly, and your software gets back the result along with a masked card number. That one design choice decides how much of your office falls under PCI DSS. It also shapes how cleanly payments post to invoices and how hard it will be to change processors later.
A third option, the standalone terminal, has no connection to your software at all. Most businesses that run industry software end up choosing between the two connected options, so those get most of the attention below.
Defining Each Setup by Who Touches the Card
A standalone terminal works on its own. A front desk employee keys the total from the software screen into the terminal and runs the card. Marking the invoice paid is a separate, manual step, because the two systems never talk to each other. It's cheap and simple, and it's where most posting errors start.
A fully integrated setup builds payments into the software itself. The card reader is a peripheral attached to the workstation, and the software handles the card data and sends it to the processor through its own payment connection. All-in-one systems, where the software company is also the payment provider, are a common modern version of this, with hardware and software sold as one product.
A semi-integrated terminal sits in between. It connects to your software, usually over the office network or a cloud link, but keeps the payment itself separate. Your software tells the terminal how much to charge, and the terminal handles everything after that.
Vendors don't use these labels consistently. Plenty of companies market a semi-integrated setup as "integrated payments," because the front desk sees no difference between the two. So don't trust the label. Ask the vendor directly whether raw card data ever reaches the computer running their software. If you're still deciding whether you need software at all, our comparison of credit card terminals vs. POS systems covers that earlier decision.
| Standalone | Fully Integrated | Semi-Integrated | |
|---|---|---|---|
| Amount entry | Keyed by staff | Sent by software | Sent by software |
| Who handles card data | Terminal | Software and workstation | Terminal only |
| Result posted to invoice | Manually | Automatically | Automatically |
| PCI scope | Small | Largest | Small |
| Processor flexibility | High | Often lowest | Depends on certified terminals |
How Card Data Flows in Each Setup
In a standalone flow, staff key the amount and the customer taps or inserts a card. The terminal sends the sale to the processor and prints a receipt. The software knows nothing about it until someone records the payment by hand.
In a fully integrated flow, the software builds the transaction and the reader captures the card. In many older or simpler designs, the card data then crosses the workstation and your office network before it leaves the building. The processor's response comes back to the software, which posts it to the invoice.
The semi-integrated flow keeps the card away from your computers entirely:
- Your software sends the amount to the terminal.
- The customer taps or inserts a card, and the terminal encrypts the card data as it reads it.
- The terminal sends the encrypted transaction straight to the processor or gateway.
- Your software gets back the outcome, such as the approval code and the last four digits. If you chose to save the card, it also receives a token.
That token matters more than it looks, and it comes up again under lock-in. For now, note that in a semi-integrated design your software stores a stand-in value, never the card number.
How Semi-Integrated Payments Shrink PCI Scope
PCI DSS is the card industry's data security standard. It's a network requirement enforced through your processor, not a federal law. Your scope covers any system that handles cardholder data, plus anything connected to those systems. A bigger scope means more controls to maintain and a longer annual self-assessment. Our plain-English guide to PCI DSS compliance covers the basics.
PCI scope for a POS depends on which design you run. In a fully integrated setup where card data passes through your workstations, those computers and the network they share can fall in scope. For a dental office whose network also carries imaging equipment and patient Wi-Fi, that's a big footprint. Network segmentation can shrink it, but someone has to design it and keep it working.
A semi-integrated setup keeps card data inside the terminal, encrypted at the moment of capture. Your practice software never sees a full card number, so the computers running it generally stay out of the cardholder data environment. A standalone terminal keeps scope small for the same reason: nothing else touches the card.
The most common misunderstanding is that semi-integrated means "no PCI." You still validate compliance every year, and you still inspect terminals for tampering. Which self-assessment questionnaire applies depends on how the terminal connects and whether its encryption is formally validated, so confirm it with your processor or a qualified security assessor. Merchants who skip validation often end up paying a monthly PCI non-compliance fee without knowing why.
A second trap catches a lot of offices. If staff type card numbers into a notes field or a card-on-file screen in the practice software, the scope you saved comes right back. Card-on-file should go through the terminal or a gateway that returns a token.
Reconciliation and Reporting Differences
Both integrated and semi-integrated setups post payments to the invoice automatically, and that's the main reason to connect payments to software at all. The differences show up in the edge cases.
Here is an illustrative example built entirely on assumptions, not measured data. Say a veterinary clinic on a standalone terminal runs 60 card payments a day, and each takes about 20 seconds to re-key into the practice software. That's 1,200 seconds, or 20 minutes a day. Over 22 working days, it adds up to 440 minutes, a little over seven hours a month. The math leaves out the time spent hunting for a payment that was keyed with two digits swapped. Put in your own counts. The point is that double entry has a cost you can measure.
Semi-integration removes most of that work, but not all of it. The biggest gap is anything done at the terminal itself. If someone voids or refunds a sale directly on the device, the software never hears about it. Many terminals can lock those functions behind a manager password, so turn that on. Also test whether tips and split tenders, such as part card and part insurance, write back to the invoice correctly.
Expect two reports on two timelines. Your software lists the day's transactions, while your processor reports batches and deposits. Settlement timing and fees mean they won't match line for line, so reconcile against the batch report rather than against bank deposits.
Fully integrated and all-in-one systems usually report best, because payments and software share one database. That convenience is real, and it's also part of what makes them hard to leave.
Processor Lock-In and Switching Costs
Every integration is built against a specific processor or gateway, or certified on particular terminal models. This is where the standalone terminal vs. integrated decision pays off or costs you.
A standalone terminal gives you the most freedom, since almost any processor can supply one. Fully integrated and all-in-one systems usually give you the least. Many industry software vendors support only their own payments partner or charge more if you bring your own processor. Changing processors can mean changing software too.
Semi-integrated setups land in the middle, and people tend to overestimate the freedom they offer. Your software is certified with certain terminal models or a certain gateway. A processor that can board those will work, and one that can't won't. Ask for the list.
Then there are stored cards. When a dental patient enrolls in a payment plan or a vet client signs up for a wellness plan, the saved card is usually a token issued by your current processor or gateway. Tokens generally don't work anywhere else. Moving them requires the old provider to cooperate with a card data migration, if one is possible at all, so ask what it costs before you commit. Combine stranded tokens with an early termination fee on your merchant account and switching gets expensive fast.
Before you sign anything, ask your software vendor these four questions in writing:
- Does raw card data ever touch our workstations or network?
- Which processors, gateways, or terminal models is your payment integration certified with?
- Is there an added fee for using a processor other than your payments partner?
- If we change processors, what happens to stored cards and recurring plans?
Which Setup Fits Practice-Management and Industry Software
Medical and Dental Practices
Front desks collect copays at check-in and then bill patient balances after insurance pays, sometimes months later. A semi-integrated terminal fits that pattern well. Each payment posts to the right patient ledger, and the scheduling and records system stays out of PCI scope. Payment plans are where tokens matter most, so ask the token question first. See how MannyPay works with medical practices.
Veterinary Clinics
Clinics take deposits before surgery and bill wellness plans monthly. Emergency visits bring large tickets at odd hours, often from stressed clients who want a fast checkout. Refunds need to tie back to the original transaction, and tip prompts should be off. A common layout pairs a countertop terminal at checkout with a second unit for exam rooms. More on payment setups for veterinary clinics.
Auto Repair Shops
Shop-management software builds a repair order that can change after inspection, and payment usually happens at pickup. Semi-integration closes out the repair order at the moment of approval. Check fleet card support carefully, because some shop systems handle fleet prompts differently. Our guide to accepting fleet cards at your shop covers those prompts, and our auto repair payments page covers hardware.
Retail Stores
Retailers often get the most from a full POS, because inventory and returns live in the same system as payments. If you already run separate inventory software, a semi-integrated terminal can sit beside it. The retail industry page and the POS systems MannyPay offers show the options.
MannyPay sells smart terminals and PIN pads from Clover, Valor, Dejavoo, and PAX. Whether a given model will semi-integrate depends on your software's certifications, not on the terminal brand alone.
Start with the four vendor questions above. Then bring the answers, along with your software name and version, when you request a free processing quote. A MannyPay specialist responds within one business day and can tell you which terminals and processing options fit the integration you already have.
This article is for general educational purposes and is not legal, tax or financial advice. Card network rules and state laws change; confirm current requirements for your business.
