Payment Processing Software: Which Type Do You Need?
Payment Processing Fundamentals

Payment Processing Software: What It Does and Which Type You Need

Payment processing software comes in five types. See what each one does, how it's priced and which fits the way your customers pay you.

Smiling advisor holding a tablet shakes hands with a woman across an office desk as a man beside her gestures

Photo: Pixabay

On this page 8 sections
  1. Match Payment Processing Software to How Money Reaches You
  2. Who Prices Your Transactions Depends on the Software
  3. Virtual Terminals and Payment Links for Orders You Never See
  4. Gateways: How the Checkout Page Is Built Changes Your PCI Work
  5. Subscription and Invoicing Software Must Follow Stored-Card Rules
  6. Embedded Payments: Put a Dollar Figure on the Convenience
  7. Features That Decide Whether the Software Saves You Time
  8. Separate the Software Bill From the Processing Bill

Key takeaways

  • If you embed a gateway's payment form in an iframe, you still have to protect the checkout page around it from malicious scripts to use SAQ A. Redirecting shoppers to a hosted page doesn't carry that condition.
  • Visa's 0.10% Embedded Payments Acquirer Fee applies to virtual cards that business software uses to pay suppliers. It doesn't apply to a client paying you through your booking app.
  • Get the card-vault export policy in writing before you store any customer cards. Tokens work only inside the provider that issued them.
  • Built-in payments make sense only when the time they save is worth more than the rate gap. Do the math with your own volume and staff costs.

Payment processing software takes a customer's card or bank details and sends them to your processor for approval. It comes in five types. A virtual terminal, often paired with payment links, handles orders taken by phone or email. A gateway sits behind a website checkout, and a POS app runs at the counter. A billing platform handles subscriptions and invoices, and some industry software, such as a booking or practice-management system, has payments built in. Choose the type by how money reaches you. Then find out who sets your processing rate, because the software you pick often decides that too.

Match Payment Processing Software to How Money Reaches You

How Money ArrivesSoftware Type That FitsTypical User
Staff key card numbers from phone or email ordersVirtual terminalProfessional services, B2B order desks
Customer pays by a link sent by text or emailPayment link toolContractors and consultants
Customer checks out on your websiteGateway with checkout integrationE-commerce stores
Customer is charged on a scheduleSubscription billing platformMemberships and SaaS
Buyer pays an invoice on net termsInvoicing software with card and ACHB2B and wholesale
Customer pays at a counter or tablePOS app and terminalRetail and restaurants
Payments run inside scheduling or practice softwareEmbedded paymentsClinics and salons

Most businesses need more than one row. A plumbing company might tap cards in the driveway on a handheld terminal for field payments. It might also text payment links for jobs quoted by phone and key in a property manager's card at the office. That's three channels, and each one costs something different.

Who Prices Your Transactions Depends on the Software

Here is the path a card payment takes. Software captures the card, and a gateway carries it to the processor. The processor sends the authorization request over the card network to the cardholder's bank, and approved funds settle into your merchant account. One company can supply every layer, or each can come from a different provider.

A common mistake is assuming that picking software sets your processing rates. With an all-in-one provider, it does. Other tools only connect to a merchant account you arrange separately. That split decides who prices your transactions, who holds your customers' stored card data and how hard it will be to leave. Ask which arrangement you're buying before you compare features. Our explainer on how a payment gateway gets online payments approved walks through the full path.

A virtual terminal for keyed card payments is a secure web page where staff type in the card number, expiration date, security code and billing ZIP. It fits an accounting firm collecting a retainer or a distributor's desk taking a phone reorder. It needs only a browser and a login.

Keyed sales are card-not-present transactions, and the networks price them that way. Visa's published interchange table, the Visa USA Interchange Reimbursement Fees, lists card-present and card-not-present fee programs separately. A phone order falls under card-not-present even when the customer is a regular. Fraud risk is higher too, because nothing proves the card was there. Turn on address and security-code checks, and decide in advance what staff should do with a partial match. Our guide on handling AVS and CVV mismatches covers those calls.

Payment links work the other way around. The customer enters their own card on a page hosted by the payment provider, so your staff never see the number. That shrinks your PCI DSS scope and ends keying errors. Links suit customers who pay on their own time. When the order has to close during the call, a virtual terminal is faster.

Gateways: How the Checkout Page Is Built Changes Your PCI Work

An online store needs a gateway, the software that encrypts card data at checkout and passes it to the processor. Shopify and WooCommerce stores connect through a plugin, and custom sites connect through an API. A hosted payment page sends the shopper briefly to the gateway's own page to pay. Our article on gateway integration options compares the approaches.

One PCI DSS rule is widely misread here. Many small online sellers fill out SAQ A, the shortest PCI self-assessment questionnaire. They often assume a hosted form takes them out of scope entirely. Effective March 31, 2025, the PCI Security Standards Council removed two script-security requirements (6.4.3 and 11.6.1) from SAQ A.

In their place is an eligibility condition: the merchant must confirm its site isn't open to script attacks that could affect its e-commerce systems, according to SecureTrust's summary of the PCI DSS v4.0.1 changes. The same summary cites PCI SSC FAQ 1588: the condition applies to sites that embed the processor's payment form in an iframe.

It does not apply when you redirect shoppers to the processor's hosted page.

So the choice matters. An embedded form keeps shoppers on your site, but you're responsible for securing the page around it. You can protect that page yourself. Or, as Report URI's SAQ A FAQ explains, you can get confirmation from your PCI-compliant gateway or processor that its solution protects the payment page from script attacks. A full redirect leaves you the least PCI work. Beyond PCI, picking a gateway comes down to compatibility:

  • A supported plugin for your cart platform, or a documented API if your site is custom.
  • Fraud filters you can adjust yourself, such as velocity limits and country blocks.
  • A card vault, if you plan to save cards for repeat buyers.
  • Reports your bookkeeper can reconcile against bank deposits.

MannyPay supports online payment gateways including Authorize.Net and NMI, plus cart integrations for Shopify, WooCommerce, BigCommerce and Magento. For a structured side-by-side, see how to choose a payment gateway provider.

Subscription and Invoicing Software Must Follow Stored-Card Rules

For recurring revenue, the billing logic matters more than capturing the card. A membership gym and a bookkeeper on retainer both need software that stores the card as a token and charges it on schedule. It should retry failed charges sensibly and warn customers before access lapses. An account updater service from the processor refreshes cards that expire or are reissued. Ask whether yours includes one and what it costs.

Storing a card is governed by network rules. Visa's Stored Credential Transaction Framework has been part of the Visa Rules since October 12, 2018. It requires merchants to get the cardholder's consent before storing card details for future use and to keep that agreement for as long as the consent lasts, according to Moneris's overview of the framework. Visa Acceptance's developer documentation adds three more duties.

You must tell customers how the card will be used and notify them when the terms change. Each authorization must also be flagged so the card's issuing bank knows the card is stored. Visa's own framework summary covers the case where the first authorization isn't approved. The card then doesn't count as stored, and you can't use it for later charges.

Good subscription software sets those transaction flags automatically. Confirm with your processor that yours does. You still write the consent wording, the change notices and the cancellation process.

B2B billing works differently. Invoices are larger, buyers expect net terms and many pay with corporate or purchasing cards. Good invoicing software lets the buyer choose card or bank transfer and matches each payment to the right invoice. Some tools send extra line-item detail with the transaction, which can qualify commercial cards for lower interchange. The networks change those programs and their fees, so confirm current eligibility with your processor. Our guide to accepting corporate and B2B cards goes deeper. For large invoices, compare cards with ACH payment processing before you choose which one to steer customers toward.

Embedded Payments: Put a Dollar Figure on the Convenience

Practice-management systems and salon booking apps often come with their own payments. Payments post straight to the client record, and you have one login and one support line. The trade-off is price. The software company sets your rate and earns a share of every transaction, so you may pay more than you would with a separate merchant account. Get real quotes for both before you decide.

Illustrative example. Every number here is an assumption chosen for the arithmetic, not a quote from any provider. A consulting firm collects $60,000 a month by card. Its practice software's embedded payments cost an all-in 3.0% of volume. A separate merchant account, gateway fees included, would cost an all-in 2.5%.

The gap is half a percentage point. On $60,000 a month, that comes to $300 a month, or $3,600 a year. Suppose the firm's bookkeeper earns $30 an hour. For the built-in option to be worth it, it would have to save the bookkeeper 10 hours a month of matching payments and re-entering card numbers. A firm sending a few dozen invoices a month won't spend that long on them, so the separate account wins. A clinic running hundreds of small visits through its scheduling system may come out the other way, because the integration saves a little time on every visit.

One network fee causes confusion here. Visa's Embedded Payments Acquirer Fee is 0.10%, effective October 2026. It applies to eligible Visa Commercial Solutions virtual card transactions that Visa flags as embedded payments, according to Fiserv's Fall 2026 card brand update notice. Merchant Cost Consulting's October 2026 rundown explains which cards those are. They're virtual cards created inside business software, such as ERP, procurement and accounts-payable systems, to pay suppliers. Despite the name, the fee doesn't apply when a salon client pays through booking software. It matters if you sell to businesses whose accounts-payable software pays you by virtual card. See our coverage of Visa's new embedded payment charge and accepting virtual card payments.

Before planning a switch, ask whether your industry software lets you connect an outside processor. Some vendors allow it, some charge a fee and some refuse.

Features That Decide Whether the Software Saves You Time

Deposit Reports That Tie to Sales

You need the fee for each sale and a deposit report that ties each bank deposit to the sales inside it. If your bookkeeper has to build spreadsheets to match them, the software is costing you hours. A direct QuickBooks integration or a sync with your accounting system removes most of that work.

A Card Vault You Can Take With You

Tokenization replaces the card number with a stand-in value, so your systems never hold real card data. It also ties you to the vendor, because a token works only inside the provider that issued it. Moving stored cards to a new provider requires a secure transfer that the old provider must agree to. Get the export policy in writing before you store a single customer card. Without it, a subscription business can't switch providers without asking every customer to re-enter a card. Our piece on how gateways handle tokenization and fraud screening covers the security side.

Dispute Evidence in One Place

Find out how chargeback notices arrive and where transaction records are kept. Response windows are short, and if gathering evidence is slow, you lose disputes you should win. Our chargeback rebuttal letter template shows what to gather.

Separate the Software Bill From the Processing Bill

Quotes for payment processing software mix two kinds of cost. Software fees cover the subscription, the gateway and add-ons like account updater. Processing fees include interchange and network assessments, which the card networks set, plus the processor's markup.

Pricing models differ in how much they show you. Flat-rate pricing charges one percentage on every card. It's easy to read, but your cheaper debit transactions end up covering the cost of expensive rewards and commercial cards. Interchange-plus passes the network cost through and adds a disclosed markup, which makes it the easiest model to audit. Tiered pricing sorts transactions into buckets the processor defines, which makes it hard to compare quotes side by side. Our line-item breakdown of gateway fees shows what to look for on a quote.

Some merchants offset card costs with a cash discount program, dual pricing or surcharging where it's permitted. Card network rules and state laws limit how these programs can work. Confirm current requirements with your processor and a qualified advisor before you change prices.

Before you shop, pull your last three monthly processing statements and split your volume by channel: in person, keyed, web checkout and recurring. Bring that split to every vendor and ask for software fees and processing fees on separate lines. To have MannyPay review your mix, request a free processing quote. A specialist responds within one business day.

Sources

  1. Visa USA Interchange Reimbursement Fees
  2. Visa: Improving Authorization Management for Transactions With Stored Credentials
  3. Moneris: Visa Stored Credential Transaction Framework Overview
  4. Visa Acceptance Developer Center: Introduction to Credentialed Transactions
  5. SecureTrust: PCI DSS 4.0 Requirements, Key Updates and What They Mean
  6. Report URI: PCI DSS 4.0.1 SAQ A and Client-Side Security FAQ
  7. Fiserv: Fall 2026 Card Brand Updates
  8. Merchant Cost Consulting: October 2026 Interchange and Network Updates

About the author

Adrian Reyes

Adrian Reyes is Senior Payments & Fintech Editor for Beyond the Swipe, covering credit card processing, merchant accounts, payment technology and processing fees.

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.

Related reading