Voice authorization is one of the oldest fallback mechanisms in card payment processing, predating electronic terminals by decades. When standard electronic channels fail — whether due to terminal outages, network errors, or issuer-triggered referrals — merchants can still complete a sale by calling the issuer's authorization center. Understanding how this process works, and where it breaks down, is essential for any payment professional managing high-availability transaction flows.
How Voice Authorization Works
The voice authorization process follows a strict sequence of steps that must be completed in order. Skipping any step creates compliance gaps and increases the likelihood of a chargeback or failed settlement at batch close. The result of the process — a verbal approval code — must be manually recorded and entered into the payment system as a force capture to settle correctly.
Electronic Authorization Fails or Is Unavailable
The merchant's terminal attempts a standard electronic authorization and receives either a network timeout, a "refer to issuer" decline code, or cannot reach the acquirer due to an outage. The terminal may display the voice authorization phone number at this point, or the merchant can find it in their acquiring agreement.
Locate the Voice Authorization Center Number
Each card network publishes a dedicated voice authorization phone number. For Visa and Mastercard, this number is typically printed on the back of the card or documented in the merchant's processing agreement. The merchant dials from the point of sale — speed and accuracy here prevent queue abandonment.
Provide Transaction Details to the Issuer
The issuer's automated system or live agent requests the merchant identification number (MID), the card number, expiration date, transaction amount, and — for keyed entries — the cardholder's billing ZIP code. The agent may request additional identity verification on high-value or flagged transactions before proceeding.
Receive and Record the Approval Code
If the issuer approves the transaction, the agent provides a six-digit alphanumeric authorization code verbally. The merchant must write this code down immediately along with the time of call and the agent ID if one is provided. There is no electronic record of this approval in the card network's system at this stage.
Enter the Code as a Force Capture
The merchant enters the approval code into the terminal or back-office payment system as a force capture, not a standard sale. This signals to the acquiring processor that authorization has already been obtained outside the electronic channel, preventing a duplicate authorization attempt that would double-hold funds on the cardholder's account.
Settle the Batch
The transaction is included in the normal daily batch settlement. The force capture record, containing the voice authorization code, travels through the card network for clearing. The issuer matches the code against their internal records and releases the held funds to the merchant's settlement account.
Why Voice Authorization Matters
Terminal outages and issuer-side referrals are far more common than most merchants anticipate. For high-volume environments such as hospitality, fuel retail, and large-format grocery, even a brief processing outage can affect hundreds of transactions during peak hours, and without a voice auth fallback, every one of those sales is lost.
The financial stakes are significant. Industry infrastructure benchmarks from the Ponemon Institute estimate that unplanned point-of-sale downtime costs merchants an average of $5,600 per minute in lost sales across all retail categories. The Federal Reserve's 2023 Payments Study found that approximately 0.3% of card transactions in the United States require some form of manual intervention during processing — translating to tens of millions of transactions annually where voice authorization may be the only compliant path forward. Additionally, Visa's merchant dispute guidelines make clear that transactions settled without any authorization code are nearly indefensible in a chargeback representment, meaning voice auth is not just a convenience fallback but a legal and financial necessity.
Referral Is Not a Decline
A "refer to issuer" response code is not a hard decline — it is a request for additional verification before the issuer commits to approval. Merchants who treat referral codes as automatic declines and abandon the transaction are losing approvable revenue every time. Always attempt voice authorization when the terminal returns a referral code.
Voice Authorization vs. Electronic Authorization
Both voice and electronic authorization serve the same core purpose — obtaining the issuer's approval to charge a card — but they differ significantly in speed, security coverage, and operational complexity. Understanding these trade-offs helps merchants and developers decide when voice auth is worth the friction and when it creates unacceptable risk.
| Dimension | Voice Authorization | Electronic Authorization |
|---|---|---|
| Speed | 2–5 minutes per transaction | 1–3 seconds |
| Fraud screening | Manual, agent-assessed only | AVS, CVV, velocity rules, 3DS |
| Approval code delivery | Verbal, manually recorded | Electronic, auto-logged in system |
| Network record at auth time | None — created at force capture | Created immediately at request |
| Chargeback defensibility | Moderate (code required, no full trail) | High (complete electronic audit trail) |
| Availability | Any phone line, no network required | Requires internet or dedicated line |
| Operational cost | Higher (staff time, potential surcharge) | Standard interchange processing |
| Card-not-present suitability | Very low — no AVS/CVV/3DS | High when combined with 3DS2 |
Types of Voice Authorization
Not all voice authorizations are triggered by the same condition, and the correct merchant response varies by type. Identifying the specific scenario before calling the authorization center reduces call time and prevents missteps during the approval flow.
Referral Voice Authorization occurs when the issuer's electronic system returns a referral response code — typically code 01 or 02 on Visa and Mastercard networks. The issuer's fraud engine has flagged the transaction for human review, often due to an unusual amount, a new merchant relationship, or geographic anomaly. This is the most common type encountered at the point of sale.
Terminal Outage Voice Authorization is initiated proactively by the merchant when the POS terminal or network connection fails entirely before an authorization attempt can complete. The merchant must still obtain an approval code before delivering goods; a floor limit exception may apply for small-ticket amounts depending on the merchant category code and acquiring agreement terms.
Stand-In Processing Override applies when the card network's stand-in processor has approved a transaction during an issuer outage, but the merchant or acquirer needs verbal confirmation for a high-value sale. This scenario is rare and typically requires direct acquirer guidance before proceeding.
High-Value Transaction Voice Authorization is required by some issuers for transactions exceeding a defined amount threshold, regardless of terminal status or network availability. The issuer's risk or fraud team conducts a manual review before issuing the code, and call wait times are typically longer for this type.
Best Practices
Voice authorization introduces manual steps into an otherwise automated workflow. Getting those steps right every time requires clear operational procedures for merchant staff and precise technical implementation for the developers building the payment systems they use.
For Merchants
Keep the voice authorization phone number posted prominently at every POS terminal — do not rely on staff to find it on the back of a card during a stressful outage. Require all cashiers to record the authorization code, time of call, and agent ID on a paper log before closing the transaction; this log is your primary evidence in a chargeback dispute. Train staff to distinguish between a referral code and a hard decline, because abandoning a referral without calling costs direct revenue. Reconcile all force capture transactions daily against the paper log to catch entries where the code was not recorded or entered correctly before the batch closes. Never attempt a second electronic authorization after obtaining a voice auth code — this creates duplicate holds on the cardholder's available balance.
For Developers
Build explicit support for the force capture transaction type in your payment integration — do not assume all approved transactions flow through the standard auth-capture path. Store the authorization code as a discrete field in your data model and validate that it is populated before allowing a force capture to submit to the acquirer. Implement manual key entry fallback flows that prompt the operator to enter the voice auth code as a required step in the transaction UI, not an optional field. Log the authorization source (electronic vs. voice) on every transaction record for dispute and compliance auditing. When integrating with an orchestration layer, handle referral response codes as distinct, actionable events — not generic errors — and surface them to the operator with clear instructions.
Common Mistakes
Treating referral codes as hard declines. Referral response codes signal that the issuer wants additional context before approving, not that the transaction is rejected. Merchants who configure their systems to auto-decline on referral codes forfeit a meaningful percentage of approvable transactions every month.
Entering the force capture as a standard sale. This is the most operationally damaging mistake in voice auth workflows. Running a standard sale after a voice auth triggers a second electronic authorization attempt, which may succeed and result in the cardholder being charged twice. Always select force capture explicitly and populate the authorization code field.
Failing to record the authorization code. Without the code, the force capture cannot be submitted correctly, and the transaction is indefensible in a dispute. If a cashier loses or misreads the code, the issuer's voice center must be called again — a second hold cannot be avoided.
Using voice auth for card-not-present orders. The absence of AVS, CVV, and 3DS verification makes CNP voice auth transactions extremely vulnerable to fraud. Chargeback liability shifts entirely to the merchant, and most acquiring agreements explicitly prohibit this practice for remote commerce.
Settling outside the authorization hold window. Voice authorization codes carry the same expiration window as electronic codes — typically 7 days for most consumer cards. Batches held past this window may find the authorization expired at clearing, resulting in failed settlement and potential loss with no recourse after goods have been delivered.
Voice Authorization and Tagada
Payment orchestration platforms must handle voice authorization scenarios without collapsing referral codes into generic failures — because every referral discarded as a decline represents recoverable revenue that never makes it to settlement.
How Tagada Handles Referral Codes
Tagada's orchestration engine parses issuer response codes in real time. When a referral code is detected, the transaction is held in a pending-manual state and surfaced to the merchant dashboard as an actionable item — not silently discarded. Once the merchant completes the voice auth call and enters the approval code, Tagada submits the force capture to the correct acquirer using pre-negotiated routing logic, ensuring the transaction settles on the optimal rail without triggering duplicate authorization attempts. Every voice auth event is logged — approval code, timestamp, acquirer, and operator ID — creating the audit trail needed for chargeback representment.
This matters particularly for merchants using Tagada across multiple acquirers, where referral thresholds and voice authorization phone numbers vary by card network and issuer country. Tagada centralizes this configuration, eliminating the operational risk of staff dialing the wrong authorization center or misidentifying the card network during a high-pressure outage scenario.