The short answer
A partial authorization is an issuer response approving only part of a requested auth amount, because the cardholder's available balance can't cover the full request. Most common with prepaid cards (gift cards, government benefit cards, GPR cards) where the balance is finite. The merchant can accept the partial and request the remaining amount on another payment method — a "split-tender" checkout — or cancel and decline entirely.
Typical partial-auth scenarios
- Prepaid gift card with $30 balance hitting a $50 order. Issuer approves $30, returns "partial approval" response. Merchant prompts customer for a second payment method for the remaining $20.
- EBT card at grocery checkout. Customer has $40 in SNAP benefits, rings up $75 in food. $40 approved on EBT, customer pays $35 in cash or debit.
- Store-branded gift card with partial balance. Retail gift cards often allow partial redemption.
- Prepaid payroll card at end of pay period. Cardholder has $X loaded, order is >$X. Partial approval, customer pays remainder.
How it works in the auth flow
- Merchant sends auth request for full $50.
- Issuer responds with response code indicating partial approval + amount approved ($30).
- Gateway surfaces the partial approval and amount to the merchant app.
- Merchant app either (a) captures the partial + prompts for second tender, or (b) reverses the partial auth and declines the transaction.
- If second tender captured, each tender is a separate auth + capture in the transaction log.
What operators need to know
- Gateway support is opt-in. Most gateways default to "auto-decline on partial" — you have to explicitly enable partial-auth support. Stripe, Adyen, Worldpay all support when configured.
- Card-present vs CNP. POS retail systems commonly support partial auth out of the box. E-commerce checkout flows often don't — adding split-tender UX is a meaningful build.
- Regulated by Visa/MC rules. Partial-auth support is required on specific MCCs (supermarket, gas, retail). Optional elsewhere. The issuer can return partial on any card but the merchant chooses whether to accept.
- Important for prepaid-heavy verticals. If your customer base has significant prepaid-card use (gaming, digital goods, benefits-adjacent), enabling partial auth recovers 5-10% of attempted transactions that would otherwise decline outright.
- UX design challenge. Customer experience around "your card only covered $30, please add another $20" is sensitive. Clear messaging ("Gift card balance applied: $30. Remaining balance: $20 — please enter another payment method") beats generic "declined."
- Reversals if not completed. If the customer abandons at the second-tender step, reverse the first partial auth immediately (auth reversal). Leaving the $30 hold stranded on a prepaid card is poor UX and may draw complaints.
- Reporting complexity. One order = two transactions in your logs. Reconciliation and refund flows need to handle both legs independently.