> For the complete documentation index, see [llms.txt](https://partner-docs.covergenius.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://partner-docs.covergenius.com/offers/guides/payment-process/single-payment.md).

# Single Payment

Partners operating in markets that allow the collection of insurance premiums by non-insurance companies may use this method of premium collection. This is the most common approach for XCover partner integrations, and offers significant efficiency, process, and approval rate benefits.

### Regulatory Considerations

#### United States of America

If you are planning to sell insurance products to residents of the United States of America then it is likely the integration would use the **Dual Payment** method unless the insurance products are travel or warranty related, in which case you might be eligible for a Travel Retailers or general warranty exemption. Please contact your assigned Client Solutions Engineer (CSE) for more information.

#### European Union

For partners planning to sell insurance products solely to residents of the European Union you might be eligible to become an Approved Representative of Cover Genius allowing you to collect premium. Otherwise you must use the **Dual Payment** method. Please contact your assigned CSE for more information.

#### Other Markets

For partners planning to sell insurance products to residents elsewhere please contact your assigned CSE for more information on how to collect premiums if you wish to remain the Merchant of Record.

### Implementation

**No integration steps are required for a single payment implementation approach.** The partner collects payment for both the main product and insurance in a single transaction.

### Workflow

1. **Create Offers** - Request insurance product offerings using the Create Offers endpoint
2. **Customer Reviews** - Display insurance products and pricing to the customer
3. **Checkout** - Customer proceeds to checkout with main product + insurance
4. **Payment Collection** - Partner collects payment for the entire transaction (product + insurance)
5. **Confirm Offer** - Partner calls the Confirm Offer endpoint to provision the insurance policy

### Tracking Payment Information (Optional)

Partners may choose to track the payment/checkout item using metadata fields in the **Confirm Offer** request:

```json
{
  "quotes": [...],
  "policyholder": {...},
  "partner_transaction_id": "XZY123",
  "payment_details": {
    "provider": "stripe",
    "transaction_id": "ch_1234567890"
  },
  "partner_metadata": {
    "trip_name": "Holiday trip",
    "primary_contact": "Dana Skulky",
    "primary_contact_number": "+123123123",
    "primary_contact_email": "dana_skulky[themail.com",](cci:4://file://themail.com",:0:0-0:0)
    "custom_platform_transaction_reference": "XZY123"
  }
}
```

### Important Notes

> **Payment Before Confirmation:** You must collect payment from the customer BEFORE calling the Confirm Offer endpoint. The endpoint records that payment has been collected but does not process payments.

> **Partner as Merchant of Record:** In single payment integrations, the partner remains the merchant of record for the entire transaction, including the insurance premium.

> **Settlement:** XCover will invoice the partner for collected insurance premiums according to the agreed settlement terms.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://partner-docs.covergenius.com/offers/guides/payment-process/single-payment.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.