How SaaS Payment Processing Works and What It Costs Your Business
What SaaS payment processing is and why it matters to your cash flow
SaaS payment processing means using cloud-based software to accept, route, and settle customer payments instead of running everything through your own servers or a traditional merchant account. The software sits between your customer, your bank, and the payment networks (Visa, Mastercard, ACH). It handles the technical work of encrypting card data, checking for fraud, and moving money into your account—usually within one to three business days.
The difference from older systems: you do not own or maintain the infrastructure. You pay a monthly fee or a per-transaction fee (or both) to the SaaS provider, who handles security updates, compliance with payment card standards, and the integration with your website or point-of-sale system. Your job is to connect your bank account, set up your pricing, and let the software do the routing.
This matters to your cash flow because the fees, settlement timing, and fraud rules directly affect how much money actually lands in your account and when. A SaaS processor that settles in one day but charges 3.5% per transaction will move money faster but cost more per dollar received than one that settles in three days at 2.9%. Understanding both the fee structure and the settlement schedule tells you what your real take-home is.
Key Takeaways
- SaaS payment processors charge either a percentage of each transaction, a flat per-transaction fee, a monthly subscription, or a combination—and the combination you choose directly affects your profit margin.
- Settlement time (how long before money lands in your bank account) ranges from same-day to three business days depending on the processor and your account history.
- Fraud detection and chargeback handling are built into the software, but you remain liable for certain types of fraud—knowing which ones protects you from unexpected losses.
- PCI compliance (the security standard for handling card data) is managed by the processor, but you still need to understand what data you can and cannot store yourself.
- Most SaaS processors lock you into a contract or charge early termination fees, so comparing total cost over 12 months (not just per-transaction rates) shows the real price.
How fees stack up: percentage, flat rate, and monthly charges
SaaS processors use three main fee models, and most combine them. A percentage-based fee (often called an interchange-plus markup) charges you a percentage of each transaction—typically 2.2% to 3.5% depending on the card type, your industry, and your processing volume. A Visa credit card might cost 2.9%, but an American Express card might cost 3.5%, because American Express sets its own rates and passes them to the processor, who passes them to you.
A flat per-transaction fee is a fixed amount per payment—usually $0.25 to $0.50—added to the percentage. So a $100 sale at 2.9% plus $0.30 per transaction costs you $3.20 total. The flat fee hurts more on small transactions (a $5 sale at 2.9% plus $0.30 costs you $0.45, or 9% of the sale), which is why some processors offer lower flat fees if you process high volume.
A monthly subscription ranges from $10 to $300 depending on features and processing volume. Some processors waive it if you hit a monthly volume threshold; others charge it regardless. The subscription covers access to the dashboard, fraud tools, and customer support. When comparing two processors, add up the monthly fee plus the per-transaction costs over a full year to see which one actually costs less.
Settlement timing and how it affects your working capital
Settlement is when the processor actually moves money from the payment network into your bank account. Same-day settlement deposits funds the same calendar day you process the payment (usually by evening). Next-business-day settlement deposits the following business day. Two-to-three-day settlement is the standard for many processors and smaller merchants.
The timing depends on three things: the processor's agreement with your bank, your account history and processing volume, and the time of day you process the payment. If you process a payment at 11 p.m. on a Friday, most processors will not settle it until Monday or Tuesday, even if they advertise same-day settlement. High-risk industries (like e-commerce or subscription services) often get slower settlement—sometimes five to seven days—because the processor wants to hold the money in case chargebacks come in.
This matters because if you process $10,000 on Monday but do not see the money until Thursday, you have a three-day gap where you cannot spend it. If you have payroll due Wednesday, you need a line of credit to cover the gap. Processors know this and sometimes offer reserve accounts—they hold back 5% to 10% of each settlement as insurance against chargebacks. That money sits in their account, not yours, and you get it back only after 90 to 180 days with no chargebacks.
Fraud detection, chargebacks, and who pays when something goes wrong
SaaS processors include fraud detection tools that flag suspicious transactions—unusual card-not-present activity, mismatched billing and shipping addresses, velocity checks (too many transactions from one card in a short time). The processor can decline the transaction automatically or flag it for you to review. This protects you from processing a stolen card, but it is not foolproof.
A chargeback happens when a customer disputes a charge with their bank and the bank reverses the payment. The processor deducts the full transaction amount from your account, plus a chargeback fee (usually $15 to $100). You have the right to dispute the chargeback by providing proof of delivery or proof the customer authorized the charge, but the burden is on you. If you lose, you lose the money and the fee. If you win, you keep the money but not the fee.
You are liable for chargebacks in most cases, which is why fraud detection matters. The exception is if the processor failed to follow security standards—for example, if they stored unencrypted card data and got hacked. In that case, the processor's insurance may cover it, but you should read your contract to know what is actually covered. Some processors offer chargeback protection insurance for an extra monthly fee, which reimburses you for chargebacks above a certain threshold.
PCI compliance: what the processor handles and what you have to do
PCI DSS (Payment Card Industry Data Security Standard) is the security requirement for anyone handling card data. The processor handles most of it—they encrypt data in transit, store it in secure vaults, and manage access controls. But you still have responsibilities. You cannot store the full card number, expiration date, or security code on your own servers, even encrypted. You cannot store them in email or spreadsheets. You cannot log them in plain text anywhere.
What you can do: store a tokenized version of the card (a unique code the processor gives you that represents the card but is useless if stolen) so you can charge the same customer again without asking for their card number. You can store the last four digits and card type for your own records. You can store the customer's name and billing address. Everything else stays with the processor.
If you handle card data incorrectly, you are liable for fines from the card networks (up to $100,000 per violation) and for any breach that results. The processor's insurance does not cover your mistakes. Most SaaS processors provide a PCI compliance checklist and training, but you have to actually follow it. If you are unsure whether something is allowed, ask the processor in writing before you do it.
Contracts, lock-in periods, and how to avoid surprise termination fees
Most SaaS payment processors require a contract—usually 12 months, sometimes 24 or 36 months. If you cancel early, you pay an early termination fee, typically $250 to $500 or a percentage of your average monthly processing volume. Some processors charge the fee only if you cancel within the first 12 months; others charge it anytime. A few charge no termination fee but raise your per-transaction rates if you leave.
Before signing, ask the processor three questions in writing: (1) What is the contract length? (2) What is the early termination fee, and when does it apply? (3) Can I cancel month-to-month after the initial term, or does it auto-renew? Write down the answers and keep them with your contract. If the processor's website says one thing and the contract says another, the contract wins in court.
Some processors offer month-to-month terms with no contract, but they charge higher per-transaction fees to offset the risk that you will leave. Calculate the total cost over 12 months for both a locked-in contract and a month-to-month option. Often the locked-in contract is cheaper even with the termination fee, because the per-transaction rates are lower. But if you think you might switch processors within a year, the month-to-month option might save you money despite the higher rates.
Comparing processors: what to look at beyond the headline rate
Processor websites advertise rates like "2.9% + $0.30" or "as low as 1.99%", but those numbers hide the real cost. Here is what to actually compare:
- Your mix of payment types: If 80% of your sales are online credit cards and 20% are ACH transfers, you need the processor's rates for both. Online credit cards cost more; ACH costs less. A processor with a low credit card rate but a high ACH rate might cost more overall if you take a lot of ACH payments.
- Monthly volume and transaction count: Processors offer volume discounts. If you process $50,000 a month, you might negotiate a lower rate than the published rate. Ask what volume tier you fall into and what the rate is at that tier.
- Settlement speed and reserve accounts: Same-day settlement costs more than three-day settlement. If the processor holds a reserve, ask how much and for how long. A 10% reserve on $50,000 a month is $5,000 tied up.
- Chargeback and fraud tools: Some processors include advanced fraud detection and chargeback protection; others charge extra. If chargebacks are a problem for your business, the extra cost might be worth it.
- Integration and support: If you use Shopify, WooCommerce, or a custom system, make sure the processor integrates with it. If integration requires a developer, that is a hidden cost. Ask whether support is email-only or phone-available, and whether there is a charge for technical support.
Build a spreadsheet with your actual transaction data (volume, card types, average transaction size) and run it through each processor's fee calculator. Most processors have one on their website. The total annual cost, not the headline rate, tells you which processor is actually cheapest.
Frequently Asked Questions
What is the difference between a SaaS processor and a traditional merchant account?
A traditional merchant account is a bank relationship where you own the processing infrastructure or lease it from a bank. A SaaS processor is cloud-based software you rent. SaaS is faster to set up (hours instead of days), has lower upfront costs, and handles compliance for you. Traditional accounts give you more control and sometimes lower per-transaction rates if you process very high volume, but they require more technical knowledge and ongoing maintenance.
Can I switch processors without losing my customer payment history?
You can export transaction records from your old processor, but you cannot transfer the tokenized card data. Customers will have to re-enter their payment information in the new processor's system, or you can use a payment gateway (software that sits between your website and multiple processors) so customers only enter their information once and you can switch processors behind the scenes. Gateways cost extra but make switching easier.
What happens if a customer disputes a charge months after the transaction?
The customer can file a chargeback up to 180 days (six months) after the transaction, depending on the card network and the reason. The processor will deduct the full amount plus a chargeback fee from your account. You have 7 to 10 days to dispute it by providing proof of delivery, proof of authorization, or proof the customer received the service. If you miss the deadline or cannot prove it, you lose the money and the fee.
Do I need a separate gateway if I use a SaaS processor?
No. A SaaS processor includes a gateway—the software that encrypts and routes your customer's payment information. You only need a separate gateway if you want to use multiple processors or if your processor does not integrate with your website platform. Most SaaS processors integrate directly with Shopify, WooCommerce, and other common platforms, so a separate gateway is not necessary.
What should I do if my processor goes out of business?
Your money in their settlement account is protected by FDIC insurance (up to $250,000) if they hold it in a bank account. Your customer data is usually transferred to another processor automatically, but you should have a backup processor set up before this happens. Read your contract to see what the processor promises to do if they shut down. Most require them to notify you and transfer your data within 30 days.