“The payment went through” can mean several things. A card was approved, the merchant captured the charge, a processor recorded the funds or a payout reached a bank account. Those events do not have to happen together.
When a payment appears delayed, first identify which stage has completed and which balance you are looking at. Otherwise, the customer, merchant and payment provider can all report different statuses without describing the same event.
Authorization reserves the possibility of payment
A card authorization checks whether a transaction can proceed and may place a hold on available funds or credit. It does not necessarily mean the merchant has collected the final amount.
A merchant can authorize before the purchase is complete. Hotels, for example, may need an estimated hold before the final bill is known. Other merchants separate authorization from capture while preparing an order.
Stripe’s payment-hold documentation explains that an authorization has an expiry and must be captured within the applicable window. The precise timing depends on the transaction and payment arrangement.
Capture is a separate event
Capture instructs the payment system to collect the authorized payment. Some systems perform it automatically; others require the merchant to trigger it.
If a merchant never captures an authorization, the hold can expire or be released. The customer’s available balance may then change without a completed purchase appearing. A pending entry is therefore not always a final debit.
For a merchant investigating missing funds, “authorized” and “captured” are the first statuses to distinguish. Repeating a charge without checking can create a second payment rather than repair the first.
A processor balance is not a bank payout
After a payment is captured, the merchant’s provider may show it in a pending balance before it becomes available for payout. The payout itself follows the provider’s schedule and the receiving bank’s processing.
Account reviews, reserves, payment-method differences and operational issues can affect availability. A provider’s normal schedule is not a guarantee that every payment will follow it.
Check the provider’s transaction record and payout record separately. A payout can combine multiple payments and adjustments, so its amount may not match any one sale.
Bank posting adds another view
The recipient bank may show an incoming payment at a different time from the sender or processor. Business-day schedules and cut-off times can matter on some rails, while other systems operate continuously.
Do not apply a card-payment explanation to every bank transfer. Instant account-to-account payments, conventional bank transfers and card transactions have different processes. Identify the actual rail before interpreting a delay.
The same distinction applies to refunds. A merchant’s refund confirmation can establish that it initiated the return, while the customer’s bank still needs to display the credit.
Investigate with the right records
Collect the payment reference, amount, currency, date and current status. For a merchant, include the capture and payout references if they exist. For a customer, keep the receipt and distinguish pending from posted entries.
Ask the provider a specific question: has the payment been captured, has a payout been sent, or has the receiving bank credited it? That is more actionable than asking whether the payment is “complete.”
Avoid sharing full card numbers or private account credentials when seeking help. The provider should have a defined support process for locating the transaction with appropriate reference information.
Plan around availability, not the approval screen
If you need funds for a deadline, use the availability estimate for the actual route and account. A successful checkout is not a cash-flow forecast.
Our contactless payment explainer follows the actors involved in a card purchase. For cross-border payments, our transfer cost guide adds the effects of conversion and intermediary charges.
