Gary 609 384 4881 web20promotions@gmail.com

Table of Contents

Last Updated: October 16, 2026

What Is Authorization and Settlement in Credit Card Processing?

Authorization and settlement are the two core stages of every card payment. Authorization is the moment a card network asks the cardholder’s bank to approve a transaction.

What happens over the next day or two decides when that money lands in your business bank account.

This guide walks through the full credit card authorization process, the credit card settlement process, and everything in between.

Authorization: Getting the Green Light

Authorization is the approval step. The card network checks that the card is valid and that the cardholder has enough available credit, then sends back an approval or a decline.

Nothing moves at this point. No funds leave the cardholder’s account.

That distinction matters. A declined card is not a failed payment forever. And an approved card is not a completed sale.

Settlement: Moving the Money

Settlement is the transfer of funds from the cardholder’s issuing bank to the merchant’s acquiring bank. It happens after the merchant submits a batch of captured transactions, usually once a day.

Authorization reserves the money. Settlement delivers it.

Between those two moments, several parties touch the transaction, and each one takes a processing fee. That is why your payout is smaller than your sales total.

The Credit Card Authorization Process, Step by Step

Here is the full credit card authorization process, from the moment a customer pays to the moment you get an answer. The whole loop usually takes seconds.

Small business owner using a tablet point-of-sale system to manage credit card authorization and settlement.
Small business owner using a tablet point-of-sale system to manage credit card authorization and settlement.
  1. The cardholder taps, inserts, or enters their card at your point of sale or online payment page.
  2. Your payment gateway encrypts the payment information and sends an authorization request to your payment processor.
  3. The processor routes the transaction request to the card network.
  4. The card network passes it to the issuing bank, the customer’s card issuer.
  5. The issuer checks the account: is the card valid, is there available credit, does the transaction look suspicious?
  6. The issuer returns an authorization response, either an approval or a decline, back through the network.
  7. Your terminal or checkout page shows the result.

An approval means the funds are reserved. It does not mean you have been paid yet.

If the issuer declines, the transaction stops there. Common reasons include insufficient funds, an expired card, or a fraud flag from the card issuer.

Pro Tip
Watch your authorization rate, not just your sales. A high decline rate often points to a data problem, like a mismatched billing address or a gateway setting that flags too many good cards as risky. Fixing that raises approvals without changing your pricing.

Credit Card Capture vs Authorization: What’s the Difference?

Capture is the step where you claim an authorized transaction and send it for settlement. Authorization reserves the funds. Capture turns that reservation into a real charge.

Some transactions capture automatically. A retail swipe at the counter authorizes and captures in one motion, so the customer never sees the gap.

Others capture later, and that is where merchants get into trouble:

  • Delayed capture: You authorize now and capture when the order ships. Common for custom orders and backordered items.
  • Partial capture: You authorize the full amount but capture less, because part of the order was unavailable.
  • Reversal: You void the authorization before capture, releasing the funds hold.
  • Expiration: The authorization hold expires if you never capture it. Timelines vary by card network and issuer, so check your processor’s guidance rather than assuming a fixed window.

The practical rule: capture as soon as the sale is final. Every day you wait is a day the hold can expire or the customer’s available credit can change.

Get Started Today →

Action What Happens When to Use It
Authorization only Funds reserved, no charge yet Pre-orders, hotel check-ins
Auto capture Reserved and charged together In-person retail sales
Delayed capture Reserved now, charged at fulfillment Shipping, custom work
Partial capture Less than the authorized amount charged Split or reduced orders
Reversal or void Hold released, no charge Canceled orders

The Credit Card Settlement Process and Who’s Involved

Settlement is not one event. It is a short sequence of file exchanges and net fund movements that runs after you close your batch. Understanding the sequence is what lets you trace a missing deposit instead of guessing.

The parties and what each one actually does

  • Cardholder: The customer whose account funds the purchase.
  • Merchant: Your business, which accepts the payment and holds a merchant account.
  • Issuing bank (the issuer): The cardholder’s bank. It approves the authorization, places the hold, and later releases funds for clearing.
  • Acquiring bank (the acquirer): Your bank or the bank sponsoring your merchant account. It receives funds on your behalf and is the party that can debit you for chargebacks.
  • Payment gateway: The software that encrypts card data at the point of sale or checkout page and forwards it to the processor.
  • Payment processor: The back-end that routes messages, stores the batch, and submits it to the network.
  • Card network: The system (for example, Visa, Mastercard, American Express, or Discover) that connects issuers and acquirers and sets the rules both sides follow.

The message flow, step by step

A single purchase generates several distinct messages. Naming them makes the process easier to follow:

  1. Authorization request. Your gateway sends the transaction to your processor, which routes it to the card network, which forwards it to the issuer. The issuer responds with an approval code or a decline.
  2. Authorization response. The approval travels back through the network to your terminal or checkout page. The issuer places a hold on the cardholder’s available credit for the authorized amount.
  3. Capture. When the sale is final, you (or your system) capture the authorization. Capture converts the hold into a charge that is eligible for settlement.
  4. Batch close. At the end of your business day, you close the batch. The processor packages all captured transactions into a settlement file.
  5. Clearing. The network passes the transaction detail to the issuer so the issuer can post the charge to the cardholder’s account. Clearing is where the transaction becomes a real line item on the cardholder’s statement.
  6. Settlement. The network calculates what each bank owes the other across all transactions in the cycle and moves net funds between the issuer and the acquirer. Interchange and network fees are netted out at this stage.
  7. Payout. The acquirer deposits the net amount into your business bank account, minus the processor’s fees and any reserves.

Why the number you receive is smaller than your sales total

Your payout is a net figure. Interchange (paid to the issuer), network assessments, processor markup, and any monthly or statement fees are subtracted before the deposit lands. Refunds and chargebacks from prior days are also netted against the batch. That is why a payout almost never equals the gross sales shown on your terminal report, and why the difference is not an error.

Pro Tip
Ask your processor for a sample settlement report that shows gross sales, interchange, network fees, processor fees, and net deposit on one page.

Visa’s rules on interchange and settlement

How Long Does Credit Card Settlement Take?

The authorization is nearly instant. Settlement is the slow part, and the delay is structural, not a sign that something is broken. Most card transactions settle within one to three business days after you close your batch, but the exact date your money lands depends on a handful of variables you can actually control.

What determines your deposit date

  • Batch close time. Your processor has a daily cut-off, often in the late afternoon or evening local time. Transactions captured after the cut-off roll into the next business day’s batch.
  • Business days, not calendar days. Weekends and federal bank holidays do not count. A batch closed Friday evening typically funds Monday or Tuesday, and a batch closed the day before a holiday can slip an extra day.
  • Card type and channel. In-person debit and credit transactions often settle faster than card-not-present e-commerce transactions, which carry more fraud review.
  • Your acquirer’s posting schedule. Some banks post incoming ACH deposits same-day; others post once in the morning. The settlement date and the posting date are not always the same.
  • Reserves and holds. If your merchant account carries a rolling reserve, a percentage of each batch is withheld for a set period (commonly 90 to 180 days) to cover potential chargebacks. That money is yours, but it is not in your account yet.
  • Payout schedule. Daily, weekly, and twice-weekly schedules are common. A weekly schedule means your batch settles daily but your payout only releases on the scheduled day.

A realistic timing example

Say you run a retail store and close your batch at 9:00 p.m. on a Thursday, before your processor’s 10:00 p.m. cut-off.

  • Thursday night: batch submitted.
  • Friday: clearing runs; the issuer posts the charge to the cardholder’s account.
  • Friday or Monday: the acquirer receives net funds, depending on the network’s settlement cycle.
  • Monday or Tuesday: the deposit posts to your business bank account.

If you had missed the cut-off and closed Friday morning instead, the same sale would likely fund Tuesday or Wednesday. That is the entire cost of a missed cut-off: not a lost sale, but a delayed deposit.

Reconciling payouts against batches

Reconciliation is where most small teams lose hours, and it is also where errors get caught. A simple method:

  1. Export your daily batch report showing gross sales, refunds, and voids.
  2. Export the corresponding settlement report showing interchange, network fees, and processor fees.
  3. Match the batch total to the deposit line on your bank statement, using the settlement date, not the sale date.
  4. Note any reserve withholding as a separate line so it does not look like a missing deposit.
  5. Investigate any deposit that does not match within one business day.
Watch Out
Missing your processor’s batch cut-off pushes the whole batch to the next business day. Do that on a Friday before a holiday weekend and your money may not land until the middle of the following week. If your terminal does not auto-close, set a daily reminder.
Key Takeaway
Authorization reserves the money. Settlement moves it. Everything that goes wrong in between comes down to timing, so treat your daily batch close as a fixed appointment, not an afterthought.

Exceptions, Disputes, and Failed Settlement

Settlement does not always go cleanly. A handful of exceptions cause most of the headaches.

  • Chargebacks: The cardholder disputes the charge. The issuer pulls the funds back and your acquiring bank debits your account, often with a fee.
  • Failed settlement: A batch can fail if account details are wrong, if the merchant account is frozen, or if the processor hits a technical fault. Your sales show as captured, but no deposit arrives.
  • Expired authorizations: Capture too late and the hold is gone. You may need to re-authorize the card, and the customer may have moved on.
  • Refunds and reversals: These reduce your next payout rather than pulling from your bank account.

The pattern across all of them is the same. Speed protects you. Capture promptly, close batches daily, and reconcile every deposit against its batch.


Local Credit Card Processing helps you take control of both, with free equipment, easy integration into the systems you already run, and transparent pricing. Our team provides dedicated local tech support and 24/7 customer support, so a failed batch or a stuck terminal never leaves you waiting on hold.

Frequently Asked Questions

What is authorization in credit card processing?

Authorization is the moment a cardholder’s bank (the issuing bank) approves or declines a transaction. The merchant’s payment terminal sends a request through the payment processor and card network to the issuing bank, which checks available credit and fraud signals. If approved, the bank places a hold on those funds. This typically takes seconds, but the money hasn’t moved yet.

What is settlement in credit card processing?

Settlement is the actual transfer of funds from the issuing bank to the merchant’s account. After a transaction is authorized and captured, the merchant’s acquiring bank submits a batch of transactions to the card network. The network coordinates the transfer, and the funds are deposited into the merchant’s business bank account, usually within one to three business days.

What is the difference between authorization and settlement?

Authorization verifies that the card is valid and the cardholder has enough available credit or funds. Settlement moves the money from the cardholder’s bank to the merchant’s account. Authorization happens in seconds at the point of sale; settlement occurs later, often overnight or within a few days. An authorized transaction is not final until it settles.

Can a credit card transaction be authorized but not settled?

Yes. If a merchant captures an authorization but never includes it in a settlement batch, the transaction remains unsettled. The cardholder’s funds stay on hold until the authorization expires, typically within a few days. Merchants should capture and settle promptly to avoid expiration and ensure they get paid.