Payments

Authorization

An authorization is the card bank's yes or no to a payment. When it says yes, it holds the amount on the customer's card before the money is actually collected.

By Mike Akop, founderUpdated 5 min read

On this page
  1. How an authorization works
  2. Types of authorizations
  3. A worked example
  4. Where it usually goes wrong
  5. Tips for owners
  6. How MazalPOS handles authorization
  7. Common questions

In short

  • An authorization is a hold on the customer's card, not money in your bank account yet.
  • Capture is the second step that turns the hold into a real charge you get paid for.
  • An approved card can still end up unpaid if the hold expires, is reversed, or the sale is disputed later.
  • Pending charges that stay on a customer's statement for a few days are usually authorizations waiting to settle.

How an authorization works

When a customer taps, inserts or types a card, your register sends a request to the card network, and the network passes it to the customer's bank. The bank checks a few things: is the card real, is the account open, does the customer have enough money or credit, and does anything look like fraud. A few seconds later the bank sends back a yes or a no. That answer is the authorization.

A yes does not move any money yet. It sets aside the amount on the customer's card so they cannot spend it somewhere else. The customer sees it on their banking app as a pending charge. Your store only gets paid after the next step, called capture, when the sale is finalized and the amount is sent to be settled. For most retail sales, authorization and capture happen together in the same moment, so you never notice two steps.

The bank also sends back an approval code. That code is your proof that the bank said yes. If a dispute ever comes up, the code and the time of the request are part of the record.

Types of authorizations

Not every authorization looks the same. These are the ones a store meets most often.

  • Full approval: the bank approves the whole amount. This is the normal case.
  • Partial approval: the bank approves less than you asked for, for example a prepaid card with only $40 left on a $65 sale. You collect the rest another way.
  • Decline: the bank says no. The reason is often vague on purpose, such as "do not honor", so the customer usually has to call their bank.
  • Pre-authorization: a hold placed before the final amount is known, common at hotels and for deposits. The final charge can be the same or lower.
  • Zero-dollar check: a $0 request that only asks whether the card is valid, used when saving a card for later.

A worked example

This is an example, not real data. A customer books a facial for $120 and adds a $38 serum. The cashier rings up the sale at $158 plus 8% sales tax.

  1. Tax is $158 x 0.08 = $12.64, so the total is $170.64.
  2. The customer taps their card. The register asks the bank to authorize $170.64.
  3. The bank approves and puts a $170.64 hold on the customer's account. The register prints the receipt.
  4. The sale is captured. The card network settles it, and after the processor's fee comes off, the remaining money arrives in the store's bank account in a payout a few days later.

Where it usually goes wrong

  • Treating approved as paid. A yes from the bank is a promise to hold money, not cash in hand. If the sale is never captured, or the hold expires first, you have given away the service or product for nothing.
  • Running the card again after a slow response. If the screen freezes and the cashier taps the card a second time, the customer can end up with two holds. Check the first result before trying again.
  • Saying a decline means the customer is broke. A decline can come from a travel flag, a wrong zip code, a daily limit or a bank fraud rule. Stay polite and offer another card.
  • Ignoring partial approvals. If only part of the amount is approved and the cashier does not notice, the receipt can show a paid sale that is actually short.
  • Not explaining pending charges. Customers who see a hold on their statement for several days may call to complain. A short line on the receipt or at the counter prevents that.

Tips for owners

When a card is declined, ask for a different card or offer to split the sale across two cards. Never tell the customer what you guess the reason is, since you do not know it. Let them contact their bank.

If you take deposits for appointments or special orders, tell the customer in plain words whether it is a real charge or a hold that will drop off. For services where the final price changes, such as a color service that takes longer than planned, capture only the final amount.

Once a week, compare what the register says was approved with what actually landed in your bank account. A gap between the two is usually a timing issue, but a gap that stays open is worth a call to your processor. The guides on approved cards that do not pay and why payouts get held cover the usual causes. Also read about pending charges and payouts to see the full path from tap to bank.

How MazalPOS handles authorization

Payments in MazalPOS run through your own Stripe account, so the approval comes straight from the card network and the bank to your store. The register shows the result right at checkout, and sales made while the internet is down sync when the connection is back. If a card later turns into a dispute, you can look it up as a chargeback, and the manager app shows your Stripe payouts so you can match approvals to deposits.

Common questions

It depends on the customer's bank and the card network. If the hold is never captured, the bank releases it by itself after a few days. Customers can usually see it as a pending charge in the meantime.

No. The authorization holds the money on the card, and the capture is the step that actually charges it. For most in-store sales they happen almost at once, so they feel like one thing.

One is usually the pending authorization and the other is the final captured charge. The pending line normally disappears on its own once the sale settles. If both stay on the statement, check for a duplicate sale.

Yes, before it is captured you can void the sale, and the hold is released back to the customer. After capture it becomes a refund instead, which can take a few days to show on the customer's side.

ChargebackRefundProcessing feePoint of sale (POS)

Want the full guide? Read Card Approved but Not Paid? A Front Desk Checklist.

Written by Mike Akop, founder of MazalPOS. We build and support the register, online store and staff app that stores from Las Vegas to Honolulu run on. Questions about this term? Talk to a real person.

Not sure where to start?

Talk to a real
person today.

Tell us how your store works and we will show you MazalPOS with your own products.

14 days free. No card. Cancel anytime.