Pending, Authorized, or Settled? What Those Card Payment Statuses Actually Mean

TL;DR

• Visa’s VisaNet Connect Acceptance Docs define credit card processing as a sequence of authorization, clearing, and settlement, establishing that an approved payment is a series of events rather than a single moment. 
• Authorization reserves the customer’s funds but does not move money to you. Standard operational procedure dictates waiting for capture before delivering goods or services. 
• Capture is your instruction to finish collecting. Visa’s acceptance documentation states that a capture request initiates clearing and settlement for an authorization previously approved by the issuer, thereby cementing “authorized” as an intermediate state. 
• Captured is not the same as settled. Standard accounting practice clearly distinguishes a payment sent for settlement from one that is fully settled, and separately categorizes payable amounts held for the next batch. 
• Before capture, void or cancel. After capture, refund. Industry rules dictate that a captured authorization cannot be voided and must be handled through the refund process instead. 

 

Why Card Payment Statuses Vary Across The Payment Lifecycle 

Every business that accepts cards eventually stares at a transaction list and wonders what the labels actually mean. One order says authorized. Another says captured. A third says sent for settlement. A customer calls insisting they were charged twice, and the dashboard shows a single approved sale. Meanwhile, the bank deposit does not match today’s total.

 

None of that means something broke. It usually means you are looking at different points in the same payment lifecycle.

 

Payment processing is a multi-stage process that moves money from a cardholder’s issuing bank to a merchant’s account through authorization, capture, clearing, settlement, and, finally, merchant funding. 

 

In modern payment processing, each stage produces its own status label, and those labels are not standardized across gateways, processors, and acquirers. That is why two providers can describe the same event with two different words.

 

As a trusted payment partner at Digitech Payments, we have spent 15 years helping merchants across Canada and the US read these statuses correctly, and the same handful of misunderstandings show up in nearly every support conversation. This guide translates the vocabulary into plain English, explains what happens behind the scenes at each step, and provides a repeatable process for investigating a transaction that appears stuck.

 

How Do Credit Card Payments Work From Tap To Deposit? 

How do credit card payments work? A card payment moves through five distinct stages: authorization, capture, clearing, settlement, and merchant funding. Each stage involves different parties, and each one can produce its own status in your reporting.

 

Visa’s VisaNet Connect Acceptance Docs lay out the framework clearly, stating that a transaction is authorized, then cleared, then settled. That ordering matters more than it sounds. A payment marked “approved” on your dashboard has cleared only the first hurdle. 

• Stage 1: Authorization. After authentication, the transaction is sent to the issuing bank, which evaluates available funds, account status, and risk indicators to approve or decline the payment in real time. The VisaNet acceptance framework outlines these mechanics: the merchant-side client sends a request to Visa; Visa routes it to the issuer; the issuer returns a decision; and Visa relays that decision back to the client.

• Stage 2: Capture. This is the merchant-side action that actively submits the previously approved transaction for completion and collection.

• Stage 3: Clearing. Visa’s Glossary defines clearing as a post-authorization process in which transaction information is collected from the merchant and sent to another network participant for validation and financial assessment.

• Stage 4: Settlement. The same glossary defines settlement as the point when funds are officially transferred from the cardholder’s issuing bank to the merchant’s acquiring bank. The merchant is not a direct party to this transfer, as it occurs strictly between the two banks.

• Stage 5: Merchant Funding. This final step occurs when a processor or acquirer makes the settled proceeds available in your merchant account. Funding is a separate reporting and timing event governed entirely by your specific account arrangement.

 

The single most useful sentence to keep in mind: an approved card payment is a sequence of events, not a single event. Almost every confusing status question resolves once you identify which event you are looking at. 

 

What Happens When A Customer’s Card Is Charged? 

A customer’s card charge is a chain of messages and decisions, not an instant transfer of money: 

• Initiation: The customer taps, dips, or submits an online order.
• Verification: Payment details and risk checks are verified.
• Routing: The request travels to the card network and on to the issuer.
• Decision: The issuer approves or declines the transaction.
• Return: The decision travels back through the network.

 

Only then does the terminal or checkout page show a result. 

 

At that moment, no money has moved to the business. In payment processing, authorization is defined as the stage after payment details and risk checks are successfully verified, proving that funds for the payment are reserved. This means that an authorization hold reserves the buyer’s funds but does not actually transfer the money. 

 

This is where most merchant confusion begins, because a customer’s banking app often shows something. The confusion stems from the fact that some issuers and payment-method interfaces do not clearly distinguish authorizations from captured or settled payments. The customer sees a line item and reads it as a charge. The merchant sees an authorization and reads it as approved. Both are correct, and both describe different things. 

 

For in-person retail, where goods change hands immediately, authorization and capture typically occur together, so the operational gap is minimal. Visa’s VisaNet Connect Acceptance Docs describe a “sale” as appropriate when goods or services are delivered immediately. 

 

For e-commerce, service businesses, hospitality, and anything with delayed fulfillment, the gap between approval and collection can last hours or days, and that gap is where the status questions live. 

 

The practical takeaway for any support team: when a customer calls about a charge, do not answer from memory. Open the transaction, review the event history, and determine whether they are viewing: 

• A reserved amount
• A completed collection
• A cancellation in progress
• A refund in progress

 

Answering the wrong question can create a second support call and, sometimes, a dispute.  

 

How Does Card Authorization Work, And What Does “Authorized” Really Mean? 

Authorization is the issuer’s real-time approve-or-decline decision on a specific transaction, made after evaluating available funds, account status, and risk indicators. When it succeeds, the issuer typically reserves the funds. It does not send them to the merchant.

 

Visa’s VisaNet Connect Acceptance Docs outline exactly that evaluation. The issuer reviews the account and the risk profile, then answers yes or no. That answer is a point-in-time payment decision, which is an important qualifier. An approval is not a fraud guarantee, not an authentication result, and not immunity from a later dispute. 

 

Authorization vs. Authentication 

Authentication is a separate concept that can occur before authorization. Visa’s 3-D Secure insights position authentication as a preceding step and authorization as the later payment decision. For e-commerce merchants discussing cardholder verification, 3-D Secure, and fraud controls, keeping those two words apart prevents a lot of muddled internal conversation. 

 

Authorizations also expire. Industry mechanics dictate that an authorization is valid for a set period during which you can capture or cancel the payment; if it is not captured within that period, it automatically expires. The applicable window depends on the payment method and network rules, which is why merchants must confirm the window for their own setup and card mix rather than memorizing a default number. 

 

The operational rule that follows is blunt: do not treat authorization as the signal to ship. The standard operational rule is to wait for capture before delivering goods or services. Visa’s documentation explains why a subsequent capture request is required to enable clearing and settlement of an approved authorization. Authorized is an intermediate state, not a synonym for paid out. 

 

Only the processing merchant can actively cancel an authorization hold. A cancellation, also called an authorization reversal, is an active request made by the processing merchant. The issuer cannot independently cancel that authorization or change its expiration timeline. 

 

If a merchant promises a customer that their hold will drop off at a specific hour, that promise concerns something outside the merchant’s control. Explain the action taken, not the issuer’s posting behavior. 

 

Why Are Pending Transactions The Most Misunderstood Status In Transaction Processing? 

Pending transactions are the most misunderstood status because “Pending” does not have one universal meaning, which is why reading it as a single condition leads teams to the wrong corrective action. Depending on the provider, it typically means one of two materially different things: 

• The issuer has not answered yet. An “open” or pending status often indicates that an authorization request has been sent, but the issuer has not responded yet in an asynchronous flow. 
• The issuer already said yes: Other providers display a successful authorization as pending until capture or settlement is complete, meaning the payment is simply waiting for a later step.

 

That ambiguity is why merchant teams should stop interpreting the word and start reading the event trail. To find out what actually happened, look at the following: 

• Status history and timestamps
• Merchant order reference
• Processor transaction ID
• Authorization code (where available)
• Payment-event or failure-reason fields

 

The trail tells you what happened; the label only tells you what a provider decided to call it. 

 

Pending transactions on the customer side add another layer of complexity. Because some issuer interfaces do not clearly distinguish between an authorization and a captured payment, a customer may see a pending entry that looks exactly like a charge. Incremental authorizations complicate it further. Standard incremental authorizations follow this timeline:  

• Before capture: An incremental authorization appears as an additional pending entry on a customer’s statement.
• After capture: The pending entries are removed, and the total captured amount appears as a single final entry.

 

That is a concrete, non-speculative explanation to give a customer who is certain they were billed twice. 

 

For merchants in hospitality, fuel, equipment rental, and service verticals where the final amount can change after the initial approval, this pattern is routine rather than exceptional. Training front-line staff on it once noticeably cuts duplicate-charge complaints.

 

Documenting in writing what each status in a specific gateway means for a specific account reduces recurring support tickets more than any other fix because it replaces guesswork with a clear definition.

 

What Does “Captured” Mean In Credit Card Processing? 

Captured means an approved authorization has been submitted for completion. In credit card processing, capture is the merchant-side instruction that moves a reserved amount toward clearing and settlement.

 

Visa’s VisaNet Connect Acceptance Docs define its capture request as initiating clearing and settlement for a previously approved authorization. In plainer terms: authorization holds funds to confirm the buyer can pay, while capture moves funds from the buyer to the merchant account.  

 

Automatic vs. Manual Capture 

Whether anyone manually triggers capture depends entirely on your gateway configuration. Gateways generally support two primary models: 

1. Immediate (Automatic) Capture: Most gateways default to an immediate capture that occurs automatically after authorization. This is known as an authorization-and-capture flow that happens together. Visa’s documentation matches this framing exactly, defining a “sale” as appropriate when goods or services are delivered immediately.
2. Manual (Authorize-Then-Capture): Certain payment methods support manual, delayed, and partial captures. An authorize-then-capture model separates the stages so a merchant can verify inventory, complete a service, review an order, or otherwise decide whether to proceed. A classic example is a hotel stay: the merchant authorizes a hold before the guest arrives, then captures the final amount at checkout. 

 

Many merchants run automatic capture for years without knowing the setting exists, which works for immediate-fulfillment retail but becomes a real liability for anything else. Having the right hardware and gateway configuration is crucial for this step, so exploring reliable payment products ensures your capture settings match your fulfillment model. 

 

Capture is also not guaranteed to succeed. Most gateways incorporate a specific status for failed captures and require merchants to inspect the recorded failure reason in the transaction events. 

 

This detail breaks the comfortable assumption that an approval makes every later step inevitable. It does not. An authorization can be approved, but the capture can still fail, leaving fulfilled goods and no collection unless someone notices. 

 

That is the exact scenario where proactive service earns its keep. Capture failures rarely announce themselves. They sit in a report until a reconciliation catches them or a month-end total comes up short. Building a habit of reviewing failed captures weekly, rather than quarterly, is one of the cheapest risk controls available to a growing business. 

 

How Long Does It Take For Card Payments To Settle, And What Is A Batch Settlement? 

How long card payments take to settle depends on the payment method, card network, acquirer, and merchant setup, so there is no single universal answer. What can be described precisely is the sequence, because it determines the timing.

 

Settlement in the network sense is the interbank completion stage. Visa’s Glossary identifies the payer-side issuing bank and the merchant-side acquiring bank as the institutions completing the transfer. 

 

What is a batch settlement? 

In standard transaction processing, batch settlement is the process of submitting and settling transactions in batches on a schedule rather than individually. Visa’s VisaNet Connect Acceptance overview details that Visa performs end-of-day settlement to the acquirer and sends daily reports to the acquirer, the client, or both. 

 

That end-of-day cadence explains a lot. Reporting, batching, and deposits do not update at the precise moment a shopper taps a card or submits an online order, because the settlement and reporting cycle runs on its own clock.

 

Then there is the gap most merchants trip over: money settled in a platform’s flow is not the same as money available in a bank account. Standard finance reporting distinguishes a payment marked as settled from an amount marked as payable, meaning funds are held until the next settlement batch.  

 

The completion process follows a clear set of definitions: 

• Capture: Initiates the completion process.
• Settlement: Confirms that funds have been received in that platform’s money flow.
• Payout: Occurs when a partner makes proceeds available to the merchant.

 

A “Sent for Settlement” status acts as the practical midpoint, proving that: 

• A request to transfer funds has been sent to the financial institution.
• The payment can no longer be canceled.
• The platform is still awaiting the funds.

 

For a support team, that status is a definitive decision cutoff: past this point, a void is off the table, and a refund is the required tool.  

 

If you want to know your own funding timing, the honest answer comes from your account arrangement rather than a blog post. If your current timeline is disrupting your cash flow, exploring customized payment solutions can help you secure funding schedules, batch cutoffs, and setups tailored to your specific business model. 

 

Why Is My Deposit Delayed When My Sales Look Approved? 

A delayed deposit usually comes down to three questions: did the payment settle, is the amount payable, and what adjustments hit the same period? A deposit that looks short is often a reconciliation problem, not a missing payment.

 

Start by auditing your pending transactions. If transactions are sitting in sent-for-settlement, capture-failed, or authorization-only, they will never land in that deposit. There is a distinct meaning for each of those states, and each one requires a different response. 

 

Next, check payable versus settled. Because a platform can hold a settled amount as payable until the next settlement batch, a transaction can be fully complete in network terms yet still be pending the next payout cycle.

 

Then look at what else is in the period. American Express’s Explore Payments Default View documents settlements, submissions, transactions, chargebacks, and other adjustments within the merchant payments view. This is the single most common cause of a deposit that “doesn’t match.” Merchants compare gross sales to a bank deposit, find a gap, and assume something is broken, when refunds, chargebacks, credits, and adjustments are all moving through the same window. 

 

The fix is a reconciliation habit rather than a reconciliation panic. Do not match gross sales against a bank line and expect them to agree. Instead, match your deposits against the full spectrum of account activity: 

• Completed transactions
• Processed refunds
• Issuer chargebacks
• Credits and other platform adjustments

 

Where a deposit is genuinely stuck, escalate to a processor, acquirer, or broker with complete evidence. Vague escalations bounce, but documented ones get answered. Be sure to provide: 

• Payment references and timestamps
• The full status history
• Order and fulfillment proof
• Customer correspondence

 

This is the moment that tests whether a payments relationship is actually a relationship. Funding delays are stressful; they often surface on a Friday, and a support queue that treats a merchant as a ticket number can make a manageable timing issue feel like a crisis. 

 

Our position at Digitech Payments is that this is precisely when a payments partner should be present, not automated. With more than 1,000 reviews and a 4.4 out of 5 rating, and the track record of the Digitech parent brand behind us, being reachable during funding, dispute, and fraud situations is the part of the job we take most seriously.

 

Void, Cancel, Expire, Or Refund: Which Action Fits Which Status? 

Void, cancel, expire, and refund are four different corrective actions, and picking the wrong one either fails outright or creates a second problem. The governing rule is simple: before capture, cancel or void the authorization. After capture, issue a refund.

 

Pre-Capture Actions: Voids and Cancellations 

Voiding means canceling an authorized payment before capture, which releases the buyer’s held funds. A captured authorization cannot be voided and must instead be processed as a refund. That is the cleanest available line between the two actions. 

 

Platform-side corrective actions and inactions fall into two highly distinct statuses: 

• Canceled (Active Cancellation): This status confirms a payment cancellation that prevents funds from being transferred. However, the customer’s bank still controls the release of the reserved amount on the customer’s side. A merchant can confirm the cancellation occurred, but cannot dictate when the customer’s issuer actually releases the reservation.

• Expired (Inaction): This is a final status in which the authorization’s validity period has ended, making capture impossible and requiring a new payment authorization. For merchants with long fulfillment cycles, custom orders, or backorders, expired authorizations are a quiet revenue leak because the collection window closes before the goods finally ship.

 

Certain situations mandate a prompt void: canceled orders, out-of-stock items, failed fraud review, and cancellation during fulfillment. Promptness matters for the customer experience as much as accounting does. A held amount on a customer’s account for an order that will not be fulfilled is a preventable source of complaints. 

 

Post-Capture Actions: Refunds 

Refunds carry their own tail. Industry dispute monitoring programs often mandate that issuers report potential fraud for a captured payment, even if it is later refunded, whereas a reversed authorization avoids that requirement entirely. If there is a credible fraud concern, acting before capture is materially better than capturing and refunding. 

 

Partial Captures, Incremental Authorizations, And Split Fulfillment 

Partial capture, incremental authorization, and split fulfillment are advanced cases in which merchants most often assume a capability they do not actually have. Each one is available only if the payment method, gateway, processor, and network rules support it.

 

Partial capture allows collecting less than the amount originally authorized when the setup allows it. This capability comes with strict operational rules: 

• The Mechanism (Automatic Release): A partial capture automatically releases the remaining, uncaptured portion of the authorization. This action proves useful when a merchant fulfills part of an order or finalizes a lower total than was reserved.
• The Warning (Single-Capture Limitation): For most payments, only one capture can be made against an authorization. After a partial capture, no further capture of the remaining amount is possible.

 

This limitation costs merchants money. If a workflow assumes staged captures as shipments go out, that assumption needs to be verified first. Otherwise, the second shipment leaves with no funded collection behind it. 

 

While partial captures allow you to collect less than originally approved, two other advanced capabilities handle different fulfillment variations: 

• Incremental Authorizations (Increasing the Hold): This is a way to increase an existing authorization before capture. This fits industries where the final amount changes after the initial approval, such as hospitality, rentals, service work, and fuel. As noted earlier, this produces a multiple-pending-entry pattern on a customer statement that collapses into a single final entry upon capture.
• Multiple Clearing Records (Split Fulfillment): Visa’s Core Rules and Visa Product and Service Rules permit a single authorization to have multiple clearing records under defined circumstances, including specific split-shipment scenarios for card-absent merchants that meet stated disclosure requirements. However, a rule pathway existing at the network level does not mean a given gateway or processor actually supports it. Always confirm provider support before designing a workflow on top of it.

 

Linkage is mandatory when using these tools. Mastercard’s Transaction Processing Rules command the acquirer to use identifiers from the original approved authorization in additional authorization requests and to include those identifiers in the clearing record. 

 

Practically, that means systems must preserve transaction IDs, authorization codes, timestamps, and order references. Sloppy record-keeping here does not just complicate reporting. It undermines the validity of the additional authorization itself. 

 

Does An Approval Protect You From Fraud Or A Dispute? 

An approval does not protect a merchant from fraud or a dispute. Authorization includes risk evaluation, but it is a point-in-time payment decision, not a guarantee. This is the most consequential misunderstanding in the entire lifecycle, because it shapes how much review a merchant builds into the process.

 

In the payment lifecycle, authorization happens definitively after the verification of payment details and risk checks. Visa’s VisaNet Connect Acceptance Docs confirm issuers consider risk indicators when deciding whether to approve or decline. Both establish that risk assessment happens. 

 

However, neither states that an approval settles the question of fraud, and the broader process treats fraud checks, authentication, settlement, refunds, and disputes as separate parts of the payments lifecycle. 

 

Settlement does not close the door either. American Express’s Merchant Reference Guide illustrates a flow in which the merchant submits a charge for settlement, the payment settles, the cardmember receives a billing statement, and a dispute case still opens afterward. A settled transaction is not permanently beyond post-transaction issues. 

 

That reality is exactly why the authorize-then-capture model is a fraud tool and not just an accounting preference. 

 

Risk management best practices recommend combining separate authorization and capture with review rules. If a suspicious authorization is identified and reversed before capture, it will not be reported as a captured payment in the fraud-monitoring context. Compare that with the refund path, where issuers are required to report possible fraud for a captured payment even if it is later refunded. 

 

Read those two statements together, and the operational conclusion is hard to miss. The window between authorization and capture is the cheapest place in the lifecycle to catch a bad order. Once capture happens, the options narrow and the exposure changes.

 

For e-commerce merchants shipping across Canada and the US, that means the review step deserves a real process: who reviews flagged orders, on what schedule, against what criteria, and with what authority to void. A review queue nobody checks until Monday is not a control.

 

Fraud and dispute handling is also where merchants feel most alone. Teaser arrangements that looked simple at signup tend to leave the merchant holding the risk, with thin support exactly when a chargeback pattern emerges. Due diligence before signing matters more than any single term on the page.

 

Comparison: Which Payment Approach And Which Corrective Action Fits Your Business? 

Choosing between immediate capture and authorize-then-capture is a fulfillment decision before it is a technical one. If goods or services leave with the customer at the moment of sale, capturing immediately matches reality. If a merchant verifies inventory, completes a service later, reviews orders for fraud, or fulfills on a delay, separating authorization from capture provides a decision window that immediate capture does not.

 

The corrective actions follow the same logic. A void or cancellation is the tool while an authorization remains uncaptured and valid. A refund is the tool after capture. Mixing them up produces failed attempts and confused customers.

 

The table below summarizes the four approaches, what each does to the customer’s funds, where each fits, and the risk each carries. Every row reflects the documentation cited throughout this guide. 

 

Use it as a reference when a team is deciding what to do with a specific transaction rather than as a policy applied identically to every transaction, because the right answer genuinely depends on the fulfillment model, the payment methods, and how the account is configured.

Dimension	Immediate sale / automatic capture	Authorize, then capture	Void or cancel before capture	Refund after capture
What happens first	Authorization and capture occur together in the payment flow	Authorization occurs first; capture is submitted later	An existing authorization is actively canceled	A captured payment is returned to the customer
Customer-funds effect	Payment progresses directly beyond approval toward collection	Funds are reserved while the merchant decides whether and when to capture	The authorization hold is released through cancellation processing	Payment was already captured; a separate return of funds is initiated
Best fit	Goods or services delivered immediately	Inventory verification, service completion, delayed fulfillment, fraud review, pickup verification	Order cancellation, inventory failure, failed fraud review before capture	A post-capture return, cancellation, or adjustment
Can you still stop the original collection?	Depends on how far the payment has progressed; review status promptly	Yes, while the authorization is uncaptured and valid, via a supported void or cancellation	The authorization is canceled and cannot then be captured	No; a refund is the applicable action after capture
Primary merchant risk	Fewer chances to review before collection	Authorization can expire if not captured or canceled in the validity period	Customer-facing hold-release timing still depends on the issuer and payment method	Refund processing and later disputes remain separate considerations

 

Checklist: How To Investigate A Pending, Authorized, Captured, Or Settled Payment 

• Record exact status wording verbatim. Avoid translating labels directly to “paid” or “not paid,” as provider-specific terminology holds the key clue to the underlying event.

• Identify the underlying payment event. Determine whether a label refers to authorization, capture, clearing, settlement, payout, refund, cancellation, or dispute activity to choose the correct resolution step.

• Pull the full transaction event history. Inspect timestamps, order references, processor IDs, auth codes, failure fields, and customer communications rather than relying on a single dashboard status.

• Confirm authorization success. If a transaction was declined or never authorized, stop chasing settlement; unapproved transactions are unfunded orders that cannot be collected.

• Verify capture status before fulfillment. An uncaptured authorization is only a temporary hold. Standard operational procedure dictates confirming capture before releasing goods or services. 

• Check authorization validity. Capturing against an expired authorization will fail; request a new payment authorization instead of retrying a lapsed approval. 

• Void uncaptured orders immediately. For unfulfilled, out-of-stock, or suspicious orders, Best practices advise issuing a prompt void to stop collection and release the customer’s held funds. 

• Confirm capture success during fulfillment. Inspect provider failure codes immediately when a capture fails to prevent uncollected fulfilled orders from slipping through to month-end reconciliation.

• Distinguish “in process” from “available funds”. Statuses like “sent for settlement” mean funds are locked in the payout pipeline and can no longer be canceled, even if not yet deposited.

• Reconcile deposits against all account activity. Match net payouts, including transactions, refunds, chargebacks, and adjustments, to bank lines rather than expecting gross sales to match, in line with American Express reporting practices. 

• Use refunds (not voids) for captured payments. Attempting to void a captured payment will fail and clutter the audit trail; always issue a refund once the payment is captured.

• Review suspicious orders before capture. Canceling an uncaptured authorization avoids the fraud-monitoring impacts associated with refunding a captured sale. 

• Communicate clearly without making bank timing promises. Explain whether an entry is a hold, charge, pending cancellation, or refund, but never guarantee posting dates controlled by the customer’s issuing bank.

• Escalate issues with complete documentation. Provide processor IDs, timestamps, status logs, fulfillment proof, and customer records to ensure fast support resolution without back-and-forth delays.

 

Your Next Best Move 

Understanding the fundamental question, ‘How do credit card payments work?’, becomes much simpler once you accept that payment statuses describe stages rather than verdicts. Authorized means approved and usually reserved. Captured means submitted for completion. Settled means the transfer is finished. Funded means the money is finally yours. Four different facts, requiring four different actions.

 

Writing these definitions down for your specific gateway, training your front-line team on the “void-before-capture” rule, and reconciling adjustments rather than gross sales will resolve most status problems before they ever become disputes. 

 

When things do go wrong, the quality of your support relationship decides how your week goes. If you want a payments partner built to be reachable in those exact moments, with transparent pricing, zero ballooning teaser rates, and a 15-year track record of reliability, let’s talk. Connect with our team at Digitech Payments for a customized review of your payment setup and funding schedule. 

 

Frequently Asked Questions

1. What happens when a customer’s card is charged?

When a customer’s card is charged, the transaction is verified and routed to the card network and issuing bank, which checks available funds, account status, and risk indicators before approving or declining in real time. On approval, the issuer typically reserves the funds rather than transferring them. Money moves toward the merchant account only after capture, clearing, and settlement. Visa’s acceptance documentation frames card processing as authorization, then clearing, then settlement, proving an approval is the first step in a sequence rather than the finish line. 

 

2. How does card authorization work?

Card authorization is the issuer’s approve-or-decline decision for a specific transaction at a specific moment. After authentication, where applicable, the request reaches the issuer, which evaluates the account and risk picture and answers in real time. A successful authorization usually reserves the customer’s funds and remains valid for a limited period, during which the merchant can capture or cancel the authorization. Industry rules dictate that an authorization not captured within that period expires, and the applicable window depends on the payment method and network rules. 

 

3. How long does it take for card payments to settle?

How long card payments take to settle depends on the payment method, card network, acquirer, and merchant setup, so there is no single universal timeframe. Visa’s documentation specifies end-of-day settlement to the acquirer with daily reports, which is why reporting and deposits do not update the instant a card is tapped. Settlement in the network sense is also separate from payout. For a specific funding schedule, talk to your broker for a customized quote and account review. 

 

4. What is a batch settlement?

Batch settlement is the settlement of grouped transactions in a processing cycle rather than one transaction at a time. Visa’s network overview details that Visa performs end-of-day settlement to the acquirer and sends daily reports to the acquirer, the client, or both. A platform can also hold a settled amount as payable until the next settlement batch, which standard accounting separates from a settled status. That is why a completed transaction can still be waiting on the next payout cycle. 

 

5. Why is my deposit delayed?

A deposit usually looks delayed for one of three reasons: the transactions have not settled yet, the settled amount is payable and waiting for the next batch, or refunds, chargebacks, credits, and other adjustments landed in the same period. American Express’s Payments View groups chargebacks and other adjustments alongside transaction data, requiring merchants to reconcile all of those against deposits rather than matching gross sales. If it stays unresolved, escalate with references, timestamps, and status history. 

 

Works Cited

• American Express. Merchant Reference Guide. American Express, 2021. 
• American Express. Explore Payments Default View. American Express Merchant Support Center, n.d. 
• Mastercard. Transaction Processing Rules. Mastercard, 2025.
• Visa. Visa Core Rules and Visa Product and Service Rules. Visa Corporate, 2026. 
• Visa. 3-D Secure. Visa Corporate, 2025. 
• Visa. Glossary. Visa Developer, n.d.-a. 
• Visa. VisaNet Connect Acceptance. Visa Developer, n.d.-b. 
• Visa. VisaNet Connect Acceptance Docs. Visa Developer, n.d.-c.