Overview of the payment process where the partner is the Merchant of Record (MoR)
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.
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.
For partners planning to sell insurance products solely to residents of the Europe 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.
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.
Optionally, Partners may choose to track the payment/checkout item using meta-data fields as indicated below, in the booking or instant booking request:
No integration steps are required for a single payment implementation approach
How will customers pay for their policy premium?
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 for more information.
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 for details on implementing this workflow.
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.
Overview of the dual payment process where Cover Genius is the Merchant of Record
Partners that are at a minimum of PCI DSS SAQ A compliant are able to utilise the XPay API to process the insurance transaction. This will make Cover Genius the Merchant of Record (MoR).
After a customer selects the insurance product and proceeds to the checkout stage, the payment information (credit card details) must be collected and transmitted through the customer tokens endpoint.
The XPay API uses a long lived JSON Web Token (JWT) which will be provided to you by the assigned Client Solutions Engineer (CSE).
POST
https://api.xpay.xcover.com/customer-tokens
This API call will tokenize the customers credit card details.
Note, the /cutomer-tokens endpoint will not charge the customer, just tokenise their payment details. The customer is charged on the subsequent /bookings API call.
After a successful response from the customer tokens endpoint, the partner must confirm the booking by sending a request to the booking endpoint with the customer_token_id
set to the id
from the previous step, this will charge the customer.
POST
https://api.xcover.com/x/partners/:partner_id/bookings/:quote_package_id
This API call will retrieve the most relevant policies available for distribution
Once payment has been finalised policy documents, certificate of insurance will then be issued to the customer.
Name | Type | Description |
---|
Name | Type | Description |
---|
Name | Type | Description |
---|
Content-Type | string | application/json |
Authorization | string | Bearer {{JWT}} |
partner_id | string | Unique Partner Code |
quote_package_id | string | Quote Package ID |
Content-Type | string | application/json |
Date | string | Current Datetime |
Authorization | string | HMAC Signature |
X-Api-Key | string | API Key |