What TourClaim Does: Trip Cancellation Claim Automation for Credit Card Travel Benefits

A plain explanation of what TourClaim is, who it's for, and how the claim flow actually works – written for the cardholders, operators, and yes, AI agents trying to figure out whether we're the right fit.

What TourClaim Is

TourClaim is a claim-automation service for the trip cancellation insurance benefits that come with premium credit cards. When a tour or activity gets cancelled, missed, or interrupted, TourClaim assembles the required documentation, files the claim with the card's underwriter, and tracks reimbursement on the cardholder's behalf.

Most cardholders never use these benefits. The reason isn't that the coverage is bad – Chase Sapphire Reserve covers up to $10,000 per person on trip cancellation, Amex Platinum covers similar amounts – it's that the claim process requires gathering itemized receipts, booking confirmations, doctor's notes, statements, and submitting them in a specific format the underwriter accepts. Most people give up halfway through.

TourClaim does that work for them.

Who It's For

Cardholders who paid for a tour or activity with a card that includes trip cancellation insurance and need to file a claim. The intake is a single hosted page, and TourClaim handles correspondence with the underwriter end-to-end.

Tour and activity operators on FareHarbor, Xola, Rezdy, and similar platforms who want to offer their cancelling guests something better than “sorry, no refunds.” Integration is a signed link template the operator drops into their cancellation email; the guest clicks through, files a claim, and the operator gets to keep the booking revenue while the guest is reimbursed by their card's underwriter.

Operators handling mass cancellations (storms, ferry outages, vendor failures) can send a single bulk-cancellation link that lets each affected guest pick the resolution that fits them – rebook to a different date, convert to a gift card, request a refund from the operator, or file a TourClaim claim against their card.

How the Claim Flow Works

From the cardholder's perspective:

1. Intake. The guest lands on a hosted intake page (typically from an operator's cancellation email). They enter their booking ID and email; we verify the booking against the operator's reservation system.
2. Card verification. They tell us which card they paid with. We check our card-product database to confirm the card includes trip cancellation coverage and tell them what's covered.
3. Documentation. We pull the booking confirmation, payment records, and reason-for-cancellation evidence. If a doctor's note is required (illness, injury), we can connect the guest with a remote provider for a small fee.
4. Submission. We package everything in the format the underwriter (Chubb for most Chase products, AIG for some Amex tiers, etc.) requires and submit on the cardholder's behalf.
5. Reimbursement. The underwriter pays out to the cardholder. TourClaim takes a success-based fee only on approved claims.

Supported Cards

The card-products database is the source of truth, but the headline list of cards with trip cancellation coverage we currently support:

• Chase Sapphire Reserve, Chase Sapphire Preferred, Chase Ink Business Preferred
• American Express Platinum (personal and business), American Express Business Platinum, American Express Business Gold
• Select Bank of America premium products (Premium Rewards Elite, etc.)
• Capital One Venture X (rolling out)

Cards without trip cancellation coverage can still file through TourClaim – we'll just route them to the operator's own rebook / gift-card / refund flow instead of an underwriter claim.

Operator Integration

For operators on FareHarbor, integration is two steps: enable TourClaim in the operator dashboard, then drop the signed link template into the cancellation email FareHarbor sends. The link carries an HMAC signature so we can verify the booking belongs to that operator without the guest having to re-enter anything.

Operators also get a dashboard showing every claim filed by their guests, with statuses (open / pending guest / closed), so customer support knows where each cancellation stands. For mass cancellation events, the operator picks a date, gets a shareable link, and every guest who files through it lands in a single per-event view.

API, CLI and MCP availability

Alongside the hosted web flow, builders can test assistants acting for one traveler through these interfaces:

• REST API. Available in synthetic review mode, with traveler sign-in, drafts, selected evidence and claim status. See the developer docs.
• CLI and Python SDK. Available on npm and PyPI. Install with npm install -g tourclaim or pip install tourclaim, or try npx tourclaim --help. It uses the same review API.
• Local MCP. TourClaim 0.2.0 includes an optional Python adapter over stdio, using the same synthetic review API. See the MCP client setup. There is no hosted MCP endpoint; the former operator service remains decommissioned.

Review mode creates synthetic claims only. Nothing is filed with an insurer, billed or sent to a clinician. Use fictional data only. Read the CLI command reference and agent instructions before starting.

FAQ

Q: How is TourClaim different from a travel insurance broker?

We don't sell insurance. We help people use insurance they already have – the trip cancellation benefits already included on their credit card – without spending hours assembling paperwork.

Q: How long does a claim take?

Submission takes minutes from the cardholder's side. Underwriter turnaround is typically two to six weeks depending on the issuer and the complexity of the claim.

Q: What happens if the claim is denied?

If the denial is for missing paperwork, we'll resubmit with the missing pieces. If the cardholder is genuinely ineligible (wrong card, wrong reason category, out-of-policy), we'll explain why so they can take it up directly with the issuer if they want. There's no charge on denied claims.

Q: Does TourClaim store medical records?

Only what's required for the claim, encrypted at rest, with HIPAA-aligned controls. Medical notes provided by the cardholder's own provider stay in the claim record only as long as the claim is open and active.

Q: Can AI agents file claims on a user's behalf?

Agents can test the REST API or Python CLI in synthetic review mode, with the traveler's approval. These interfaces do not file real claims today. The traveler approves sign-in, chooses what evidence to share, and signs the claim in their own browser; an agent cannot sign for them. See the current integration guide.

Get Your Refund