Also called: Capture Only, Force Post, Post-Auth, Pre-Authorization Settlement, Prior Authorization Capture, Prior Authorized Sale, Prior-Auth
What Post-Authorization (Force Sale) is
A force sale, also called a force post, submits a card transaction with an approval code you already received. Instead of getting authorization through the terminal at that moment, you enter the prior approval details to complete the sale. A merchant terminal guide describes the function as manually entering a prior authorization number. A phone-based payment menu uses “force post” for finalizing an authorization.
The terms “capture only” and “post-authorization” are not used consistently across payment systems. In a standard flow, authorization approves the charge and sets funds aside; a later capture submits it for payment. A force sale is a specific way to submit a transaction with an approval code from outside the normal terminal flow. It is not approval to charge a card that was declined or never authorized.
An approval code is not the payment; the sale still has to be submitted and settled.
How it works
You first receive approval, for example through a voice authorization when your terminal or connection is unavailable. You record the approval code, then enter it with the transaction details using your terminal or another supported payment system. The system submits the sale for processing. The code ties the submission to the approval, but it does not guarantee that the transaction will settle.
Authorization and payment are separate steps. After capture, card settlement generally takes 1 to 3 business days. An authorization also has an expiration window set by the network and issuer, so a delayed submission can fail or require a new authorization.
What it means for your business
A force sale helps you complete an already approved card payment when your normal checkout flow did not record or submit it in the usual way. That can help keep a sale from being missed during a temporary terminal or connectivity problem. It does not speed up settlement or guarantee funds.
The research available for this term does not establish a separate force-sale fee or a standard statement descriptor. Expect the transaction to be part of your card processing, and check the batch and deposit records to confirm it was accepted and paid. Do not assume the approval code alone proves the transaction was captured.
Where force sales go wrong
Entering the wrong approval code, amount, or transaction details can leave the sale unmatched or uncollected. Submitting the same sale twice can create a duplicate charge. A missed capture can also leave you with a pending approval but no completed payment, which complicates order records and customer support.
Treat the approval as time-limited and use the force-sale function only for a transaction that received approval. If you cannot verify the approval or the terminal rejects the submission, do not keep retrying with altered details. Use your normal authorization process or arrange another payment method.
What you can actually change
- Record the approval. Keep the approval code with the order record, along with the approved amount and transaction time. Do not store sensitive card authentication data.
- Submit it once. Enter the approved transaction through the force-sale function your system supports. Match the submitted amount to the approval and avoid duplicate attempts.
- Reconcile the batch. Compare the submitted transaction with your batch report and bank deposit. Follow up on a missing or rejected sale before treating the approval as collected revenue.
Frequently asked questions
Is a force sale the same as a regular card capture?
Both submit a card transaction for payment after authorization. A force sale uses an approval code received outside the usual terminal authorization flow, while a regular capture typically follows the authorization record in your system. The names and exact steps differ across payment systems.
Can I use a force sale without an authorization code?
No. A force sale is for submitting a transaction that already received approval. It does not bypass a decline or replace authorization. If you cannot verify the approval, run the transaction through your normal authorization process or use another payment method.
Does a force sale cost more?
The available research does not establish a standard additional force-sale fee. The transaction still goes through card processing, so confirm how it was recorded in your batch and compare any fee line against your processing agreement and statement.