Pre-Authorization Payments — How It Works – Paystand Help Center

The Process — Two Steps, Authorize Now, Charge Later

Pre-Authorization separates the payment process into two distinct stages. The card is verified and funds are reserved at checkout; the actual charge only occurs when your team is ready to collect.

Step 1 — Authorization: Reserve the funds Paystand checks that the payer's card has sufficient funds and places a temporary hold. The card is tokenized. A Pre-Authorization record is created in Paystand and linked to the invoice. No charge occurs at this stage.

Step 2 — Capture: Transfer the funds Once your team is ready — order fulfilled, service completed, shipment confirmed — a capture transfers the authorized funds. A payment record is created, your ERP invoice updates to Paid, and the GL is posted.

Payer experience: The payer experience at checkout is identical to a normal credit card payment. The payer sees a confirmation that their payment method has been accepted. They are not charged until your team performs the capture.

Capture Options — Full, Partial, or Multiple

Full Capture Capture the entire authorized amount in one action. The pre-authorization closes and the invoice marks as Paid.

Partial Capture Capture less than the authorized amount — useful when an order ships partially, a line item is cancelled, or the taxable amount changes after checkout.

Multiple Captures Make successive partial captures against a single authorization — ideal for wholesale orders shipping in multiple batches over several days, or service milestones billed incrementally.

Void an Authorization Cancel the authorization before capture. The hold releases immediately — far cheaper than a refund, with no payment record created and no GL impact.

When to Use Pre-Auth

Pre-Auth is designed for businesses where the final charge cannot be confirmed at checkout — whether due to inventory, fulfillment complexity, or post-checkout adjustments.

Industry Why Pre-Auth fits
B2B / Wholesale Orders placed before inventory is confirmed; amount may change before shipment
E-commerce Fulfillment Avoid recognizing revenue until goods ship; flexible for tax jurisdiction adjustments
Freight & Logistics Final charge depends on weight, distance, or fuel surcharges confirmed after pickup
Field Services Authorize on-site; capture after work is completed and final scope is confirmed
Hospitality / Reservations Reserve funds at booking; capture the actual amount at checkout or completion
Subscription / Milestones Authorize upfront; capture incrementally as services are delivered

Authorization Status Lifecycle

Each pre-authorization moves through a defined set of statuses. Understanding these helps your team know when a payment can still be modified.

Expiration window: Authorizations expire automatically per card network rules — typically 7 days for standard transactions, up to 30 days for certain merchant categories. Once expired, a new authorization must be created.

ERP & GL Behavior

Event Payment Record Created ERP Posted GL Impact
Authorization created No No No
Partial capture Yes Yes (Partially Paid) Yes
Full capture Yes Yes (Paid) Yes
Authorization voided No No No
Authorization expired No No No

While an active pre-authorization exists on an invoice, Paystand blocks all additional payment attempts against that invoice to prevent duplicate charges. Payment capability is restored once the authorization is fully captured, voided, or expired.

Key Facts

For questions about Pre-Authorization Payments, contact Daniel Salinas at dsalinas@paystand.com paystand.com

Prev Next

Table of contents

Pre-Authorization Payments — How It Works