Cancel For Any Reason (CFAR)

Workflows and request samples for Cancel for any reason integrations

Claims Submission For "Cancel For Any Reason" (CFAR) protection products is commonly operated by direct partner integration. This is due to these key factors:

1. Security / Risk management The core product (ticket, itinerary, booking) must be cancelled and invalidated (it can't be resold, shared, or reused by the claimant or another party), or re-allocated/resold by the partner or Cover Genius services. This ensures cancellation and real-time claims can be acheived.

2. UX Customer experience improvement by allowing a single "cancel and claim" process directly with partner front end.

3. Automation The usual process of a claim submission commonly requires input from a user to explain a situation or accident. Given a claim "For any reason", we do not need this input from a user, so XCover.com input optimisations should not be required.

The process overview for XClaim API claim submission workflow is shown below:

Request and API requirements in the above workflow

1. Get Booking: XCover API

2. Create Claim: XClaim API

3. "Premium Refund": XClaim Webhook

4. "Claim Paid": XClaim Webhook

Environments

For end to end quote, booking & claim submission testing in a CFAR implementation, a set of staging credentials will be provided to partners for testing booking to claim end to end (These are shared in addition to the standard production test credentials, which themselves should only be used for distribution build (quote and booking) and testing, and not claims).