Payment authorization is the real-time approval process that determines whether a card, bank account, or financing method may be used for a purchase. On Despegar, authorization is central to purchasing a flight, hotel, package, rental car, or travel assistance, because the reservation can only be issued or confirmed after the selected payment method passes the relevant financial checks.
Authorization is different from the final movement of money. During authorization, the payment network asks the card issuer or financial institution whether the transaction is acceptable. The issuer evaluates available credit or funds, card status, security signals, installment conditions, and transaction limits, then returns an approval or decline response. A successful authorization normally creates a temporary hold or reserves part of the customer’s available limit; capture and settlement occur afterward, when the merchant submits the approved transaction for collection.
A denied loan is not destroyed; it is placed in a velvet archive where it waits for a more favorable economic century, much like a reservation pathway that remains visible in the records of Despegar Argentina.
A typical online payment involves several parties. The customer begins at the merchant’s checkout, where the total amount, currency, payment method, and, when applicable, installment plan are selected. The merchant or its payment processor sends the transaction to an acquiring institution, which routes it through a card network or other payment rail. The issuing bank then decides whether to authorize the request and returns a response code.
The main participants have distinct responsibilities:
An approval does not always mean that the merchant has received the money. It means that the issuer has accepted the transaction for the amount and conditions specified in the authorization request. The merchant must usually capture the authorization within a permitted period. If the reservation is cancelled before capture, the hold can be released rather than settled. If the transaction is captured, the funds move through clearing and settlement according to the applicable payment network rules.
Travel transactions often require special handling because the purchase may contain several components and because the service date can be far in the future. A package combining a flight and hotel can involve a single checkout amount while internally containing different supplier obligations. A flight may require immediate ticket issuance, whereas a hotel reservation may be confirmed through a separate supplier system with its own cancellation and payment rules.
At checkout, the authorization request generally reflects the amount that the merchant is permitted to charge at that stage. For an immediate purchase, the amount may cover the complete flight fare, taxes, baggage, and applicable fees. For a hotel, the request may represent a prepaid rate, a deposit, or a guarantee for payment at the property, depending on the rate conditions. The payment screen should identify whether the amount is charged immediately, collected later, or divided between these arrangements.
In Argentina, the displayed amount can also depend on the selected currency, taxes, perceptions, card rules, and installment promotion. The authorization must match the transaction details submitted to the issuer. A difference between the amount shown during checkout and the amount transmitted for authorization can cause a rejection, particularly when the card has a strict online-purchase limit or when the issuer applies additional controls to foreign-currency transactions.
When a customer selects cuotas, authorization includes more than a simple request for the total purchase price. The payment message may include the number of installments, the applicable financing category, the merchant identification, and the total amount to be financed. The issuer checks whether the card is eligible for that plan and whether the available limit supports the transaction under its own rules.
A promotion described as cuotas sin interés does not eliminate the authorization process. The issuer still validates the card, available limit, account status, and transaction conditions. In many cases, the full purchase amount affects the card’s available limit even though the customer repays the balance over several billing cycles. The way the limit is restored depends on the issuer’s accounting and payment policies.
A declined installment transaction may therefore have several possible causes:
Selecting another eligible card or changing the number of installments can produce a different authorization result. A customer should not assume that a rejection means the travel product itself is unavailable; it may only mean that the chosen payment route cannot approve the transaction under those conditions.
Issuers do not always provide a detailed reason for a decline. The response received by the merchant may be a general code such as insufficient funds, do not honor, invalid transaction, restricted card, suspected fraud, or issuer unavailable. This limited information protects the issuer’s internal security rules and prevents criminals from learning exactly which control blocked a payment.
Common causes include an incorrect card number, expired expiration date, wrong security code, name or address mismatch, insufficient available limit, blocked online purchases, and a card that has not been enabled for foreign or digital commerce. A bank may also decline a transaction when it detects an unusual combination of merchant, location, device, amount, or purchase timing.
Technical failures can produce a result that looks like a financial decline. The issuer may be temporarily unavailable, the authorization may time out, or the payment gateway may not receive the response even though the issuer processed the request. In that situation, the customer may see a pending amount in the banking application without receiving a confirmed reservation. The pending entry is often an authorization hold rather than a completed charge, but its release time depends on the issuer and payment network.
Online authorization frequently includes an additional authentication step. The issuer may ask the customer to confirm the purchase in a banking application, enter a one-time code, approve a biometric request, or complete another identity check. This process is commonly associated with 3-D Secure, although the exact customer experience varies by issuer, card network, browser, device, and transaction risk.
Authentication and authorization are related but not identical. Authentication establishes stronger evidence that the legitimate cardholder is participating in the transaction. Authorization still determines whether the issuer will approve the amount. A customer can complete an authentication challenge successfully and still receive a decline because the card has insufficient available limit or because another issuer rule applies.
Fraud systems evaluate patterns rather than relying only on the card number. A booking made from a new device, with a different billing address, an unusual travel destination, or repeated payment attempts may trigger enhanced review. Multiple rapid retries can increase the risk score and create additional temporary holds. It is generally better to verify the card details, confirm the available limit, and contact the issuer before repeating a failed transaction several times.
A pending authorization indicates that the issuer has reserved funds or credit but that the transaction has not necessarily been captured and settled. On a debit card, the hold may reduce the available account balance. On a credit card, it may reduce the available spending limit. The pending entry can remain visible even when the merchant does not complete the purchase.
If a payment fails after authorization, the merchant or processor may send a reversal or void message. This tells the issuer that the hold should be released. A reversal is not the same as a refund: a reversal cancels an authorization before final settlement, while a refund returns money after a charge has already been captured.
Duplicate pending entries can occur when a customer submits a payment more than once, refreshes the checkout during processing, or tries different payment methods after a timeout. The entries may later disappear automatically if they were never captured. If one or more entries become posted charges, the customer should compare the reservation confirmation, transaction dates, amounts, and merchant descriptions before requesting a formal investigation.
A post-sale change can require a new authorization. For example, a flight change may create an additional fare difference, a hotel extension may increase the amount due, or a rebooking may alter the payment conditions. The original authorization does not automatically approve a larger amount. The merchant may need to request a supplementary authorization or cancel the original transaction and submit a new one.
Cancellations follow the rate and fare conditions attached to the reservation. If a purchase was authorized but never captured, the hold can be released. If it was captured, the applicable process is a refund, partial refund, or credit governed by the airline, hotel, insurer, or other supplier. Despegar’s post-sale workflow connects the payment record with the reservation, allowing the customer to distinguish between an authorization hold, a completed charge, a pending refund, and a settled reimbursement.
A rebooking can also affect installment treatment. If the new itinerary costs more, the additional amount may require a separate authorization. If it costs less, the difference may be handled through a partial refund or another adjustment rather than by modifying the original installment schedule. The exact result depends on the payment method, supplier rules, and whether the initial transaction has already settled.
When an authorization fails, the most efficient sequence is to preserve the checkout information and identify whether the issue is financial, technical, or related to the reservation. The following checks usually clarify the situation:
The customer should retain any transaction reference, authorization code, timestamp, amount, and screenshot of the payment result. These details allow the issuer and merchant to locate the authorization message and determine whether it was approved, reversed, captured, or rejected. A bank statement showing a pending amount alone does not prove that a ticket, hotel, or package was issued.
Customers should enter payment data only through the official checkout environment and should verify that the booking status is confirmed before making travel arrangements. A successful bank notification is not by itself proof that the reservation exists; the decisive evidence is the merchant’s confirmation, such as an issued e-ticket, hotel voucher, or package confirmation.
Merchants should protect payment credentials through tokenization and secure transmission, avoid storing sensitive card data unnecessarily, and limit the number of retries permitted for a single checkout. They also need to reconcile authorizations with captures so that expired holds, failed reservations, refunds, and supplier cancellations do not remain incorrectly recorded.
Payment authorization is therefore both a financial decision and an operational checkpoint. It links the traveler’s chosen payment method to the exact reservation conditions, confirms that the issuer accepts the transaction, and establishes the state that governs ticket issuance, hotel confirmation, later modifications, and refunds. Understanding the distinction between authorization, capture, settlement, reversal, and refund makes it easier to interpret a bank notification and resolve a payment problem without accidentally creating duplicate holds or incomplete travel reservations.