Why travel disputes are different
Most card-not-present disputes arrive within a few weeks of the sale. Travel disputes arrive on a different schedule, for four reasons that compound each other.
- The delivery gap. The charge happens at booking or enrollment; the service happens at departure, which may be six months or a year later. For a "services not provided" dispute, the cardholder's clock does not start at the charge. It starts at the date the service was supposed to happen.
- Recurring fees. Membership dues, payment plans and autoship-style benefit programs bill again and again. Each cycle is a fresh opportunity for "I cancelled this" or "I did not know it was recurring", and a dispute on one cycle tends to bring the others with it.
- Third parties. The cardholder bought from you but flew on an airline, slept in a hotel and was driven by a transfer company. When any of them fails, the dispute lands on the merchant of record.
- Emotion and money. A cancelled holiday is a large amount and a disappointment. People dispute things they are upset about, even when the terms were clear, and issuers are sympathetic.
The result is a dispute ratio that lags the sales it relates to. A strong quarter of enrollments shows up as disputes two quarters later, after the deposits are spent. Acquirers know this, which is why travel and membership merchant codes carry reserves, rolling holds and tighter thresholds than a plumber's account.
The reason codes and their clocks
Five dispute types account for almost everything a travel business sees. The time limits are the cardholder's, counted in calendar days, and the "expected service date" rule is what catches travel merchants out.
| What the cardholder claims | Visa | Mastercard | Time limit (cardholder) |
|---|---|---|---|
| Services not provided / not received | 13.1 | 4855 (now under 4853) | 120 days from the date the service was expected, up to 540 days after the transaction |
| Cancelled recurring transaction | 13.2 | 4841 (now under 4853) | 120 days from the disputed charge |
| Not as described or defective | 13.3 | 4853 | 120 days from the transaction or from receiving the service |
| Cancelled merchandise or services | 13.7 | 4853 | 120 days from the transaction, or from the expected service date |
| Fraud, card not present | 10.4 | 4837 | 120 days from the transaction; the issuer may file faster |
Mastercard consolidated most cardholder disputes under reason code 4853 with sub-conditions; the older codes are still used in acquirer reporting. Time limits are summarised from the network rules at the time of writing.
Read the first row again. A membership sold in January for a trip in October can be disputed as "not provided" until the following February, and the deposit installments charged in between each carry their own clock. Your records need to survive that long and be findable by the amount, the last four digits of the card and the date, because that is how the dispute arrives.
The evidence that wins each one
A dispute is decided on documents. The issuer's analyst has minutes, not hours, so the evidence that wins is the evidence that answers the exact claim on the first page.
| Claim | What wins | What does not |
|---|---|---|
| Not provided | Proof the service was delivered or made available: booking confirmations, e-tickets, check-in records, or proof the cardholder cancelled outside the refund window under terms they accepted. | A copy of your terms with no proof the cardholder saw them; a statement that "the trip was available". |
| Cancelled recurring | Proof the subscription was active and not cancelled before the charge: the consent record with timestamp, the receipts sent each cycle, your cancellation log showing no request, or the request dated after the charge. | Arguing the cardholder should have cancelled sooner when your cancellation path is a phone line open on weekdays. |
| Not as described | The signed agreement or the itinerary the cardholder accepted, with the hash and timestamp, and correspondence showing what was delivered matched it. | Marketing material that describes the best case. |
| Cancelled services | The cancellation policy as presented at purchase, the cardholder's acceptance of it, and the date and channel of the cancellation request relative to the policy. | A policy that was only in a PDF nobody opened. |
| Fraud | 3-D Secure authentication on the original payment (liability shifts to the issuer), AVS and CVV matches, device and IP data, and any evidence the cardholder used the service. | A signature on a form; delivery to a billing address. |
Two documents do most of the work: the e-signed agreement captured at enrollment, with IP address, user agent, timestamp and a hash of what was shown, and the receipt sent on every charge, naming the business, the amount, the membership or trip and the descriptor that will appear on the statement. If your platform keeps both attached to the payment record, representment is an export. If it does not, it is an afternoon of searching per dispute.
Prevention: the habits that remove most disputes
Make the charge recognizable
The single largest category of card-not-present disputes is "I don't recognize this", and it is almost entirely self-inflicted. The statement descriptor should be the name the customer knows, not the holding company. The receipt should say the same name, the amount, and what it was for, and it should go out on every cycle, not only the first. A customer who gets "Sunward Travel Club dues $89.00" by text on the 1st does not call the bank on the 15th.
Disclose recurring terms the way the networks require
Both Visa and Mastercard have rules for subscriptions and recurring billing that go beyond the law: express consent to the recurring terms at enrollment, the terms (amount, frequency, how to cancel) on the confirmation and receipt, an online cancellation method that is at least as easy as sign-up, and a reminder before the charge when billing is less frequent than every six months or when a trial converts to paid. A merchant who follows these can defend a "cancelled recurring" dispute; one who does not usually loses it regardless of the facts.
Make cancellation real
A cancellation that takes effect the same day, confirmed by message, ends the dispute before it starts. A cancellation that requires a call during office hours and takes effect "at the end of the billing period" produces a dispute on the next charge and a loss when it is filed. Suspending the subscription immediately costs one cycle of dues; the dispute costs the dues, the fee and the ratio.
Authenticate the enrollment
3-D Secure on the first payment shifts fraud liability to the issuer for that transaction and documents that the cardholder, not a fraudster, enrolled. For a category where enrollment fees run to four figures, it is worth the small friction. Store the card with the stored-credential consent so that later dues are flagged as recurring and carry the original transaction ID; mis-flagged recurring charges are declined more often and disputed more easily.
Tie the booking to the payment
For the "not provided" dispute you need to show what was delivered against what was paid. If confirmations, tickets and vouchers are filed with the payment record, you can answer in minutes. If they are in a supplier portal under a different reference, you cannot.
Alerts: refunding before the dispute files
Prevention reduces disputes; it does not eliminate them. For the ones that still happen, the issuer-side alert networks give you a window to refund before the dispute becomes a chargeback that counts against your ratio.
- Ethoca (Mastercard) and Verifi CDRN (Visa) notify enrolled merchants when a cardholder contacts the issuer to dispute a charge, typically within hours. The merchant refunds, the issuer closes the inquiry, and no chargeback is filed.
- Visa RDR (Rapid Dispute Resolution) goes further: for disputes matching rules you set (amount, reason code), the refund is issued automatically at the network and the case is resolved before it reaches you.
What the alerts cover: only issuers participating in each network, which is most large US issuers but not all, and only the dispute at hand, not the fraud or dissatisfaction behind it. What they cost: a per-alert fee that is usually less than the chargeback fee it avoids, and the refunded sale. For a travel business the economics are simple: a refund inside the alert window is a lost sale; a chargeback is a lost sale, a fee, and a step toward the monitoring programs.
The operational requirement is matching. An alert arrives with an amount, the last four digits, a descriptor and a date, and has to be matched to the original payment and refunded through the gateway that took it, quickly, every hour of every day. Platforms that own the payment ledger can do this automatically; businesses that bolt alerts onto a gateway they cannot query end up matching by hand.
The ratio, and why the alerts matter so much
Card networks run monitoring programs that measure each merchant's disputes against its sales. Cross a threshold for consecutive months and the acquirer receives notices, then fines, and eventually the instruction to terminate. Travel merchants, already classified as higher risk, have less room than most, and acquirers often apply their own tighter internal thresholds to the category. The practical target is to keep disputes comfortably under one percent of transactions by count, and to keep fraud-coded disputes far lower than that.
Two features of the programs matter for travel specifically. First, the ratio is calculated on the month the dispute is filed against the sales of that same month, so a seasonal business with a quiet month and last season's disputes arriving can breach a threshold on a handful of cases. Second, alerts resolved by refund are generally not counted as chargebacks, which is why an alert program is not an optional nicety in this category; it is how the ratio is managed.
Keep the general chargeback guide at hand for the mechanics of fees, timelines and representment; this one is about why travel gets there faster.
A checklist for travel and membership merchants
- Set the statement descriptor to the name customers know, and put it in every receipt.
- Present the membership or booking agreement at checkout and capture an e-signature with IP, timestamp and a hash of the document.
- State recurring terms (amount, frequency, cancellation method) at enrollment, on the confirmation and on every receipt.
- Send a receipt on every charge, by text or email, naming the amount and what it was for.
- Offer online cancellation that takes effect immediately, and confirm it by message.
- Use 3-D Secure on enrollment payments and store cards with stored-credential consent so dues are flagged as recurring.
- File booking confirmations, tickets and vouchers against the payment record.
- Enroll every merchant ID in Ethoca, Verifi CDRN and Visa RDR, and automate the match-and-refund.
- Watch the dispute ratio by month of filing, not month of sale, and plan for seasonal lag.
- Keep every record for at least 540 days after the service date.
Where FloPay fits
FloPay captures the e-signed agreement at checkout with the audit trail described above, bills dues as subscriptions with the recurring stored-credential flags and retries, sends a receipt on every charge with the statement descriptor, and pulls Ethoca, Verifi CDRN and Visa RDR alerts hourly, matching them to the original payment and refunding automatically. Because the card vault is provider-agnostic, a travel business that has to change processors keeps its members' cards. See the travel clubs page for how the pieces fit together.
Keep membership billing off the chargeback ratio
Signed agreements at checkout, receipts on every cycle, correctly flagged dues and alerts refunded automatically. See how FloPay sets it up for travel clubs.
See Travel Club Payments