# Authorization vs capture: what is the difference?

URL: https://www.paydude.io/resources/what-is-authorization-vs-capture
Type: Guide
Published: 2026-09-02 · Updated: 2026-09-02
Summary: Authorization reserves funds; capture takes them. When to separate the two, how long an auth lasts, and what happens if you never capture.

**Authorization checks that a card is valid and reserves the funds; capture is what actually moves the money.** Most integrations perform both in a single call, but they are separate steps and separating them deliberately is sometimes the right choice.

## Summary

Authorization reserves funds; capture takes them. An authorization typically expires after about 7 days. Separate them when there is a real gap before fulfilment. Combine them for instant digital delivery.

## What each step does

**Authorization versus capture**

|  | Authorization | Capture |
| --- | --- | --- |
| What happens | Card validated, funds reserved | Funds actually transferred |
| Customer sees | A pending charge | A completed charge |
| Money moved | None | Yes |
| Reversible by | Voiding the auth | Refunding |
| Expires | Yes, typically ~7 days | No |

The distinction matters because a pending authorization can be voided cleanly, while a capture can only be refunded — and a refund usually costs you the processing fee and appears on the customer''s statement twice.

## When to separate them

- **Physical goods.** Authorize at checkout, capture when the item ships. Many jurisdictions expect this, and it avoids refunding orders you cannot fulfil.
- **Manual review.** Hold a suspicious order, verify it, then capture or void.
- **Variable final amounts.** Hotels, car hire and fuel authorize an estimate and capture the actual total.
- **Limited stock.** Confirm availability before taking the money.

> **Authorizations expire:** If you authorize at checkout and capture three weeks later, expect failures. The hold has lapsed and the funds have returned to the customer. For long fulfilment windows, either re-authorize before capturing or capture at order time and refund if you cannot deliver.

## The customer-experience trap

A voided authorization does not always disappear from the customer''s statement immediately. Depending on the issuer, a pending charge can linger for days after you have voided it, which generates support tickets — and occasionally [retrieval requests](https://www.paydude.io/resources/what-is-a-retrieval-request) — for money that was never actually taken.

If you authorize and void frequently, say so at checkout. It is much cheaper than explaining it one customer at a time.

**Auth and capture, separately or together** A payments API that does not force the choice on you. — [See the API](https://www.paydude.io/pricing)

## Frequently asked questions

### How long does an authorization last?

Typically 7 days for card-not-present transactions and up to 30 for some categories, though issuers vary. After that the hold expires and the funds return to the customer's available balance — capturing later may fail.

### Does an authorization take money from the customer?

No, it reserves it. The amount is deducted from their available credit or balance so they cannot spend it elsewhere, but no money moves until capture. Customers often see it as a pending charge and mistake it for a real one.

### Can I capture less than I authorized?

Usually yes, and it is common in ecommerce when part of an order is out of stock. Capturing more than authorized generally requires a new authorization.

### Should I separate authorization and capture?

Separate them when there is a real gap between the order and fulfilment — physical goods, manual review, or availability checks. For instant digital delivery, combining them is simpler and avoids expired-authorization failures.