How Retail Payment Processing Works—From Card Swipe to Your Bank Account
What happens when a customer swipes or taps a card at your register
When a customer pays with a card at your register, the transaction moves through four separate systems before the money reaches your bank account. First, the card reader captures the card data and sends it to your payment processor—the company you contract with to handle transactions. The processor routes that data to the card network (Visa, Mastercard, American Express, or Discover), which checks with the customer's bank to confirm the funds exist and the card is valid. The bank approves or declines the transaction in seconds. Once approved, the processor sends a confirmation back to your register, the customer sees the charge, and you hand them a receipt.
The money does not move immediately. Instead, the transaction sits in a queue called a batch. At the end of your business day—or at a time you set—your processor bundles all approved transactions together and sends them to the card networks and banks for final settlement. This is when the actual money transfer begins. The customer's bank deducts the amount from their account, the card network takes its cut, and the remainder lands in your merchant account (usually within one to three business days, depending on your processor and bank).
Key Takeaways
- A card transaction takes seconds to authorize but one to three business days to settle—the money does not appear in your account on the same day the customer pays.
- Your processor, the card network, and the customer's bank all take a fee; the processor's cut is usually 2 to 3 percent of the transaction amount plus a per-transaction fee.
- Batching—bundling transactions at the end of the day—is when money actually moves; if you do not batch, transactions stay pending and you do not receive the funds.
- Chargebacks happen when a customer disputes a charge with their bank; you lose the money and pay a chargeback fee unless you can prove the transaction was legitimate.
- PCI compliance means your payment system must meet security standards set by the card networks; failure to comply can result in fines or loss of your ability to accept cards.
The fees that come out of every transaction
Every card payment you accept costs you money. The largest cost is the interchange fee, which goes to the customer's bank and the card network. This fee varies by card type—a rewards credit card costs you more than a debit card—and by how you process the payment. Swiping or inserting a card costs less than keying in the number manually, because the card networks charge more for "card-not-present" transactions (mail, phone, online) because they carry higher fraud risk.
On top of interchange, your processor charges its own fee, usually 2 to 3 percent of the transaction amount plus a flat fee per transaction (often $0.10 to $0.30). Some processors offer flat-rate pricing (a single percentage, like 2.9 percent plus $0.30 per transaction), while others use tiered pricing (different rates depending on the card type). A few offer interchange-plus pricing, where you pay the actual interchange fee plus the processor's markup; this is usually cheaper if you process high volume, but requires more detailed invoices to understand.
You also pay monthly fees: a statement fee, a batch fee (sometimes), a gateway fee if you process online, and a PCI compliance fee. Some processors bundle these into their per-transaction rate; others list them separately. Always ask for a full fee schedule in writing before signing a contract, because the difference between processors can be hundreds of dollars per month.
How batching works and why it matters
Batching is the process that actually moves money from the customer's bank to yours. At the end of your business day, you tell your payment terminal or system to "close the batch." This bundles all the transactions you processed that day and sends them to your processor for settlement. The processor then sends the batch to the card networks, which send it to the customer's banks. Each bank deducts the money from the customer's account and sends it through the network back to your processor, which deposits it into your merchant account.
If you do not close the batch, the transactions stay in a pending state. The customer sees the charge on their statement, but you do not receive the money. This is why some small businesses that forget to batch at the end of the day do not see deposits for several days—the transactions are waiting for the next batch to be sent. Most modern systems batch automatically at a set time each day, but you should confirm this with your processor and know how to manually batch if the system fails.
Batching also affects chargebacks and disputes. Once a transaction is batched and settled, it is harder for a customer to reverse it through their bank. Before batching, you can usually void a transaction with a single keystroke. After batching, you have to process a refund, which takes another one to three business days to appear in the customer's account.
Chargebacks: what they are and how to prevent them
A chargeback happens when a customer disputes a charge with their bank instead of asking you for a refund. The customer tells their bank the transaction was unauthorized, fraudulent, or not as described. The bank reverses the charge, pulling the money back out of your merchant account. You lose the sale amount, and you also pay a chargeback fee (usually $15 to $100 per dispute, depending on your processor). If chargebacks exceed a certain percentage of your total transactions, your processor can terminate your account or raise your rates.
The most common reason for chargebacks is a customer forgetting they made the purchase or not recognizing the name your business appears under on their statement. The second most common is a customer receiving a damaged or wrong item and not bothering to contact you first. The third is actual fraud—a stolen card or account compromise. You can contest a chargeback by providing evidence: a signed receipt, a delivery confirmation, an email exchange with the customer, or a photo of the item as delivered. If you can prove the transaction was legitimate, the bank may reverse the chargeback and return your money.
To prevent chargebacks, use clear business names on statements (so customers recognize the charge), send order confirmations and tracking numbers, and respond quickly to customer complaints. If someone says an item did not arrive or is damaged, refund them immediately rather than waiting for a chargeback. The cost of a refund is always less than the cost of a chargeback.
PCI compliance and what it means for your security
PCI DSS (Payment Card Industry Data Security Standard) is a set of rules created by the card networks to protect customer card data. If you accept cards, you must follow these rules or face fines from your processor or the card networks. The rules cover how you store data, who can access it, how you encrypt it, and how you monitor your systems for breaches.
The specific requirements depend on how many transactions you process per year. If you process fewer than 20,000 card transactions per year, you are usually in the lowest compliance tier and only need to use a PCI-compliant processor, keep your systems updated with security patches, and not store full card numbers. If you process more, you may need to complete a self-assessment questionnaire, conduct security scans, or hire a third-party assessor. Larger merchants may need a full audit.
The easiest way to stay compliant is to never handle raw card data yourself. Use a payment processor that is PCI-certified, use a point-of-sale system that is PCI-certified, and never store card numbers in email, spreadsheets, or text files. If you do store customer data, encrypt it and limit who can access it. Your processor should provide guidance on what you need to do; ask them directly what compliance tier you fall into and what steps you need to take.
Different ways to process payments in a retail setting
You have several options for how to accept and process card payments, each with different costs and security implications. A traditional point-of-sale (POS) terminal sits on your counter, reads cards, and connects to your processor via an internet connection or phone line. These are reliable and widely used, but they require a dedicated device and a contract with a processor. A mobile card reader plugs into a smartphone or tablet and lets you process payments anywhere in your store or on the go; these are cheaper to set up but may have higher per-transaction fees. A virtual terminal is a web page where you log in and manually enter card details; this is useful for phone or mail orders but carries higher fraud risk because the card is not physically present.
Some processors offer integrated payment systems that combine your POS software, inventory management, and payment processing in one platform. These are convenient because your sales data flows directly into your accounting, but they lock you into one processor and can be expensive to switch away from. Others offer payment gateways, which are software that connects your online store or website to a processor; you choose the gateway and the processor separately, giving you more flexibility.
The choice depends on your business type and volume. A retail store with a physical counter usually benefits from a traditional POS terminal. A service business that visits customers on-site might prefer a mobile reader. An online store needs a gateway. Ask your processor what options they offer and what the total cost is for each, including setup fees, monthly fees, and per-transaction fees.
Settlement timing and why deposits take days
After you batch your transactions, the money does not appear in your account instantly. Settlement takes time because multiple banks and networks have to process the transaction. On the day you batch (Day 0), your processor receives the batch and sends it to the card networks. The networks route it to the customer's banks, which deduct the money from customer accounts (Day 1 or 2). The money then flows back through the networks to your processor, which deposits it into your merchant account (Day 2 or 3).
Most processors offer "next-day" or "same-day" settlement, but this usually means the money arrives the next business day after batching, not the same calendar day. Weekends and holidays extend the timeline. If you batch on Friday evening, the money may not arrive until Tuesday. Some processors charge extra for faster settlement; others offer it as a standard feature. Ask your processor what their standard settlement time is and whether they charge for expedited deposits.
Settlement timing matters for cash flow. If you process $5,000 in sales on Monday but do not receive the deposit until Wednesday, you may not have enough cash on hand to pay suppliers or payroll on Tuesday. Some businesses use a line of credit or merchant cash advance to bridge this gap, though both come with fees and interest. The best approach is to forecast your cash flow based on your processor's actual settlement time and keep a reserve for slow days.
Frequently Asked Questions
Can I negotiate my processing fees?
Yes, especially if you process high volume or have been with a processor for years. Call your processor and ask what rates they can offer, or get quotes from competitors and show them to your current processor. Switching processors takes time and effort, so many will lower their rates to keep your business. Always get any rate change in writing before accepting it.
What happens if a customer's card is declined at my register?
The customer's bank rejected the transaction, usually because of insufficient funds, a fraud alert, or an expired card. Ask the customer for a different card or payment method. Do not retry the same card multiple times in a row, because each attempt is a separate transaction and multiple declines can trigger a fraud hold on the customer's account. If the customer insists the card should work, suggest they call their bank to check their account.
Do I have to accept all card types?
No. You can choose to accept only certain card networks (Visa and Mastercard but not American Express, for example), though this may hurt your sales. You cannot legally refuse a card based on the customer's identity or the reason for the purchase, but you can refuse a specific card if it is declined or if you suspect fraud. Most processors charge different rates for different card types, so some businesses choose not to accept premium cards to save on fees.
What should I do if I think a transaction is fraudulent?
Contact your processor immediately and report the transaction. Do not process a refund on your own, because the processor needs to investigate first. If the transaction was truly fraudulent, the processor can reverse it and protect you from a chargeback. If you refund it yourself, you lose the money twice—once as a refund and again if the customer disputes it with their bank.
Can I process payments offline if my internet goes down?
Most modern terminals can store transactions temporarily and send them when the connection is restored. However, you should confirm this with your processor before relying on it. Some older terminals cannot process offline at all. If your internet is frequently unreliable, ask your processor about a backup connection option, such as a cellular connection built into the terminal.