For the complete documentation index, see llms.txt. This page is also available as Markdown.

Product / Retail

Product Insurance or Warranties

Retail platforms and marketplaces can seamlessly present relevant warranty and insurance policies in the purchase path. Commonly, partners will integrate XCover using two key purchase process API calls: create offer and confirm offer. Depending where the offer of insurance is provided (at product page, cart page, or between as a product is added to cart), a single product offer or bundled offer can be used. 💡 See a collection of common requests for this integration type, by contacting your CSE. Most integrations follow the below high-level flow of events:

1. User browses product options and; 2. Selects a product to cart (or arrives at a product page etc.) 3. Partner platform sends an offer payload to the create offer endpoint 4. User selects offer products 5. User pays for product/s and offer at checkout 6. Payment collection 7. Partner sends a confirmation request to the confirm offer endpoint 8. XCover sends confirmation email including policy details, Partner sends purchase confirmation and tax invoice.

In-Store CG Portal Process

For in-store purchases, sales associates can utilize the Cover Genius Portal on an iPad or similar device. The online form requires a few details about the product and some customer and payment information to protect a customer's purchase(s).

Post sale processes

Cancellation Should a partner need to facilitate policy cancellation (for example, a product return, or order cancellation), the below workflow should be referenced.

Opt-out process

In circumstances where a customer chooses to purchase products, but not the insurance offer. An opt-out request is used to notify XCover of a non-opted insurance offer. This assists with pricing and product offer data analysis and ultimately improved offers and sales results.

Last updated

Was this helpful?