The payment authorization process is the set of checks that approve a payment before any money actually moves. It confirms two things: that the payment is legitimate and that the funds are there to cover it. The term covers two related ideas, the instant card check a bank runs at checkout, and the internal sign-off a business gives before it releases a payment, and both exist for the same reason: to stop money leaving when it should not.
In accounts receivable, authorization is what lets you trust a payment before you treat the invoice as settled. When a customer pays by card through a portal, the authorization step is the difference between a payment that will clear and one that will bounce. Get it right and your cash position is real; get it wrong and you are reconciling failed payments later.
Approval before money moves.It checks a payment is valid and funded before the transfer is allowed to go through.
Authorize, then capture.A card authorization reserves funds; the money only leaves when the payment is captured.
Controls prevent loss.Verification, limits and segregation of duties stop fraud and error on both card and internal payments.
For a card payment, authorization happens in seconds and runs through a fixed sequence. The customer enters their details, and a chain of parties checks the card and the funds before approving or declining the transaction. These are the steps behind that instant "approved" message.
The card details are entered at checkout or in a payment portal and sent securely for approval.
The payment gateway passes the request through the card network to the bank that issued the card.
The issuing bank verifies the card, available funds and fraud signals, then approves or declines.
On approval the amount is reserved on the customer's card, but not yet moved to you.
You capture the held amount, and over the next day or two the funds settle into your account.
The gap between steps four and five is the part people miss. Authorization only reserves the money; capture is what actually takes it. That is why an authorized payment is not the same as cash in the bank, and why your books should treat the invoice as paid only once the payment is captured and settled. A good customer payment portal handles this flow for you and feeds the result straight back to the invoice.
Authorization reserves the funds, capture claims them, and settlement is when the money actually lands in your account. They happen in that order and are easy to confuse, because for a simple card payment they can feel like one event. They are not, and knowing the difference is what stops you counting money you do not yet have.
| Stage | What happens | Is the money yours? |
|---|---|---|
| Authorization | The issuer approves the payment and reserves the amount on the card. | No, only held |
| Capture | You claim the reserved amount, confirming the sale should be charged. | Committed, not arrived |
| Settlement | The funds move through the networks and land in your bank account. | Yes |
This sequence is why a held authorization can quietly expire if it is never captured, and why a refund before capture simply releases the hold rather than moving money back. When a customer pays only part of an invoice, the captured amount is what you match, which is the heart of partial payment reconciliation. Tools like Stripe manage authorization, capture and settlement, and a connected AR system reflects each stage on the right invoice automatically.
The phrase also describes the internal approval a business runs before it releases its own payments, and this is where financial controls live. Three controls do most of the protecting, and they matter just as much on the money coming in as the money going out.
Segregation of dutiesThe person who approves a payment should not be the one who set it up, so no individual can move money unchecked.
Approval thresholdsLarger amounts need a more senior sign-off, so the size of the payment sets the level of scrutiny.
Payee verificationConfirm the payee and bank details are genuine before anything is sent, the main defence against fraud and honest error.
Approval for concessionsRefunds, credits and discounts each pass through a defined sign-off, so a concession is a deliberate, recorded decision.
These controls matter on incoming payments too. When a customer breaks an agreed plan, a clear authorization step decides who can approve a revised arrangement, which keeps broken payment arrangements from being quietly rewritten without oversight. Written into a policy and supported by software that enforces it, these controls turn authorization from a vague idea of being careful into a real, auditable check on every dollar that moves.
Authorization is the line between a payment you can trust and one you only hope will clear. On the money coming in, it protects your cash position: an authorized and captured card payment will settle, so you can mark the invoice paid with confidence instead of discovering a bounce days later. On the money going out, it protects you from paying the wrong person or the wrong amount. As more payments move online and fraud grows more sophisticated, that protection is no longer optional. The businesses that get paid cleanly are the ones that let a proper authorization flow do the checking, rather than trusting that every payment is what it appears to be.
A declined authorization is the issuer saying no, and the reasons fall into a few familiar buckets. Knowing which one you are dealing with is what decides whether the payment is easy to recover or a genuine warning sign.
The most common cause: the account is short or the card is over its limit, so there is nothing to reserve.
An expired card, a wrong number or a mismatched billing address fails the verification checks.
The issuer flags an unusual transaction, often larger than normal or from an unfamiliar location, and stops it as a precaution.
For a business taking payment, the practical response is to make recovery easy rather than treat a decline as a dead end. A clear message at checkout prompting the customer to check their details or try another card recovers many failed payments on the spot. For invoices, a payment link the customer can simply open again, with the amount already attached, turns a decline into a quick retry instead of a chase. Persistent declines are worth watching as a risk signal too, because a customer whose card keeps failing may be a customer heading for trouble, which is exactly the kind of early warning a tight AR process is built to catch.
Don't let these critical mistakes hurt your
collections - See how to fix them, today!
Request an AI summary of Paidnice
