# Payment Process ## Single Payment Most XCover partners operate their own shopping cart, checkout, and payment collection processes. \ From a customer experience perspective, a single itemised purchase transaction is preferable (for example a travel booking along with the insurance policy). Please refer to the [Single Payment page](/xcover/purchase-workflow-overview/payment-process/single-payment.md) for more information. ## Dual Payment In rare circumstances, Partners and XCover may agree to operate a dual payment integration approach. \ This results in two transactions against the same payment method of the user in quick succession. \ \ The merchant of record for the product/service remains the Partner, and the merchant of record for Insurance remains XCover. \ \ If this is your preferred integration method, please speak to your Partnerships manager or Client Solutions Engineer. Please refer to the [Dual Payment page](/xcover/purchase-workflow-overview/payment-process/payment.md) for details on implementing this workflow. ## Split Payment In some circumstances, Partners may choose to integrate split payments (by using an approved payment provider) to split the transaction after payment collection, ie. One payment, two merchants (Partner and XCover), and two settlements (Partner and XCover). \ \ If this is your preferred integration method, please speak to your Partnerships manager or Client Solutions Engineer. --- # Agent Instructions: 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: ``` GET https://docs.covergenius.com/xcover/purchase-workflow-overview/payment-process.md?ask= ``` The question should be specific, self-contained, and written in natural language. 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.